[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]

Search This thread
By:
Advanced…
Clamor

Clamor

Senior Member
Sep 4, 2013
388
687
Львів
Nvidia Tegra Note 7
Nexus 7 (2013) Repartition​

No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.

This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).

Known-issues
HTML: 
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.

DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device

Backup

# Before processing further we highly recommend you backup persist and EFS using adb
# Or you might lose your IMEI/WIFI + BT mac addresses

Code: 
adb root
adb shell
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img

Now you can find 3 *.img files at path /sdcard. Copy them to your PC since internal memory will be erased.


Installation
HTML: 
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# Package is unified for flo and deb. To restore stock layout use same zip and steps as for repartition.

1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
    - In TWRP: Wipe > Format data
    - Type yes
    - Once this completes go to: Wipe > Advanced Wipe
    - Tick all the boxes and wipe. There should be no further mount errors. (Thanks [user=7694808]@mr_rubbish[/user] for corrections in formatting).
8. Install ROM which you like.
9. Enjoy better flash partition layout.

If something gone wrong - we recommend you NOT to do anything by yourself. Write here for help, else you may do only worse.

Downloads:
Repartitioning package: GitHub

Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- rlw6534 for Kingston MMC layout;
- surfrock66 for his gide for Nexus 5;

As usual, feedback is appreciated :)

XDA:DevDB Information
Nexus 7 (2013) Repartition, Tool/Utility for the Nexus 7 (2013)

Contributors
Clamor
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery


Version Information
Status: Stable

Created 2018-09-19
Last Updated 2019-01-18
 
Last edited:
  • Like
Reactions: kozmo2k4, johndaog, Mysterion1 and 79 others
Clamor

Clamor

Senior Member
Sep 4, 2013
388
687
Львів
Nvidia Tegra Note 7
Common issues and F. A. Q.

Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.

1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.

2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).

3. If you want to be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You should check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to describe what you did and enclose partition.log to your post.


FLO/DEB STOCK
Code: 
22      671088640B   1551892479B   880803840B                 system
23      1551892480B  2139095039B   587202560B                 cache

FLO/DEB MODIFIED
Code: 
22      614429696B   2187293695B   1572864000B                system
23      2187293696B  2270167039B   82873344B                  cache
...
30      2348843008B  2610987007B   262144000B                 vendor
4. After flashing most ROMs system size will reduce to stock, you need to resize /system in TWRP or use flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).

5. After returning to stock partition table you won't be able to get into the Recovery from the bootloader anymore, but when you start the tablet normally it goes straight in the Recovery. It is normal state. New partition table proposes larger /recovery size (16MB) while stock gives only 10MB. During restoring stock process, it is impossible to restore larger recovery backup into new smaller partition. Whether not to leave user without recovery excess, recovery backup restores into /boot partition. Just flash ordinary TWRP and install ROMs from it.

6. Don't install the zip file from the USB OTG. Copy them into the /sdcard. Else you will get message after flashing repartition pack.
Code: 
"Can not extract updater-script. Do you have it in package?
Updating partition details...
...done"
 
Last edited:
  • Like
Reactions: kozmo2k4, Sniffscurry_1111, djphooka and 15 others
Clamor

Clamor

Senior Member
Sep 4, 2013
388
687
Львів
Nvidia Tegra Note 7
@lollyjay No it wasnt. Package has 2 step security system. It checks if partition table was modified and in what way (by package itself, by user or it is stock). Second step is that package itself doesn't modify anything, it needs manual confirmation in terminal, else no changes will be applied.
 
  • Like
Reactions: lollyjay
lollyjay

lollyjay

Senior Member
Jul 26, 2012
3,785
1,656
Fresno
Clamor said:
@lollyjay No it wasnt. Package has 2 step security system. It checks if partition table was modified and in what way (by package itself, by user or it is stock). Second step is that package itself doesn't modify anything, it needs manual confirmation in terminal, else no changes will be applied.
Click to expand...
Click to collapse
Thanks
So do I NOT flash the modded twrp first?
Your instructions said to flash it after reboot to recovery
 
  • Like
Reactions: zentara
R

rlw6534

Senior Member
Jul 24, 2012
78
67
Clemson, SC
Nvidia Shield Tablet
nVidia Shield Android TV (2017)
R

rlw6534

Senior Member
Jul 24, 2012
78
67
Clemson, SC
Nvidia Shield Tablet
nVidia Shield Android TV (2017)
Clamor said:
@rlw6534 Every manual repartition or repartition made not by my pack needs an individual look and partition table restore.

@lollyjay here
Click to expand...
Click to collapse

OK. Here is my partition layout. My userdata appears to be smaller than stock, but there isn't enough room on mmcblk0 to increase it to the size that your script is looking for. I have no idea how that could have been changed without bricking the tab. Everything else looks normal. Ideas?


Code: 
Model: MMC MMC32G (sd/mmc)
Disk /dev/block/mmcblk0: 30937186304B
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start        End           Size          File system  Name      Flags
 1      67108864B    156745727B    89636864B     fat16        radio
 2      201326592B   204472319B    3145728B                   modemst1
 3      204472320B   207618047B    3145728B                   modemst2
 4      268435456B   283795455B    15360000B     ext4         persist
 5      335544320B   336343039B    798720B                    m9kefs1
 6      336343040B   337141759B    798720B                    m9kefs2
 7      402653184B   403451903B    798720B                    m9kefs3
 8      403451904B   406597631B    3145728B                   fsg
 9      469762048B   471298047B    1536000B                   sbl1
10      471298048B   472834047B    1536000B                   sbl2
11      472834048B   474931199B    2097152B                   sbl3
12      474931200B   480174079B    5242880B                   aboot
13      480174080B   480698367B    524288B                    rpm
14      536870912B   553648127B    16777216B                  boot
15      603979776B   604504063B    524288B                    tz
16      604504064B   604505087B    1024B                      pad
17      604505088B   606041087B    1536000B                   sbl2b
18      606041088B   608138239B    2097152B                   sbl3b
19      608138240B   613381119B    5242880B                   abootb
20      613381120B   613905407B    524288B                    rpmb
21      613905408B   614429695B    524288B                    tzb
22      671088640B   1551892479B   880803840B    ext4         system
23      1551892480B  2139095039B   587202560B    ext4         cache
24      2147483648B  2148532223B   1048576B                   misc
25      2214592512B  2225078271B   10485760B                  recovery
26      2281701376B  2281709567B   8192B                      DDR
27      2281709568B  2281717759B   8192B                      ssd
28      2281717760B  2281718783B   1024B                      m9kefsc
29      2348810240B  2348843007B   32768B                     metadata
30      2415919104B  30937169407B  28521250304B  ext4         userdata
 
  • Like
Reactions: Clamor
You must log in or register to reply here.

Similar threads

Tk-Glitch
[KERNEL][ALL ROMS][SEP 14] Glitch for Flo/Deb - r574
Replies
3K
Views
517K
N
nalott
Dees_Troy
[RECOVERY][deb/flo] TWRP 3.1.1-0 touch recovery [2017-05-19]
Replies
760
Views
352K
M
MENINBLK
faux123
[Kernel] (020) flo/deb KK 4.4 (S2W/UV/CPU/GPU OC/Hybrid Linux 3.4+) [Aug-02]
Replies
2K
Views
373K
nokiagye
nokiagye
CarbonROM
  • Locked
[ROM][AOSP][Nightly/Release] CarbonRom JB [flo/deb]
Replies
1K
Views
187K
CarbonROM
CarbonROM
Ziyan
[ROM][AOSP][7.1/8.1/9.0 EXP][flo/deb] Unlegacy Android Project
Replies
580
Views
134K
johndaog
johndaog

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    Neffy27
    Neffy27
    eniac2000 said:
    Hello together. I am new in the forum and I think I have a similar problem with my Nexus 7. I tried to update the tablet to LineageOS 18.1 with the manual of Lineage. While the process I got an Error in the Repartition part.
    I powered off the tablet and on again but it could not boot. I can still enter the Fastboot Mode.
    I had tried to do a factory reset but I get the Error: "Partion table doesn't exists"
    Could you please help me to run LineageOS 18.1 on the tablet?
    Click to expand...
    Click to collapse
    I also messed up this process last night. There's no point in trying to run the script again expecting a different result. In the Github, the source code of the script is there. Since you're able to get to the bootloader, I manually fastboot boot twrp recovery image and manually ran the steps in the source scripts via terminal. This got me back to being able to have a good recovery and get a ROM installed.
    View
  • 82
    Clamor
    Clamor
    Nexus 7 (2013) Repartition​

    No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.

    This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).

    Known-issues
    HTML: 
    - If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.

    DO THE BACKUPs. Repartition will erase all your data
    USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device

    Backup

    # Before processing further we highly recommend you backup persist and EFS using adb
    # Or you might lose your IMEI/WIFI + BT mac addresses

    Code: 
    adb root
adb shell
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img

    Now you can find 3 *.img files at path /sdcard. Copy them to your PC since internal memory will be erased.


    Installation
    HTML: 
    # This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# Package is unified for flo and deb. To restore stock layout use same zip and steps as for repartition.

1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
    - In TWRP: Wipe > Format data
    - Type yes
    - Once this completes go to: Wipe > Advanced Wipe
    - Tick all the boxes and wipe. There should be no further mount errors. (Thanks [user=7694808]@mr_rubbish[/user] for corrections in formatting).
8. Install ROM which you like.
9. Enjoy better flash partition layout.

    If something gone wrong - we recommend you NOT to do anything by yourself. Write here for help, else you may do only worse.

    Downloads:
    Repartitioning package    : GitHub

    Credits:
    Special thanks to
    - Unlegacy-Android team;
    - Sudokamikaze;
    - rlw6534 for Kingston MMC layout;
    - surfrock66 for his gide for Nexus 5;

    As usual, feedback is appreciated :)

    XDA:DevDB Information
    Nexus 7 (2013) Repartition, Tool/Utility for the Nexus 7 (2013)

    Contributors
    Clamor
    Source Code: https://github.com/clamor95/android_device_unlegacy_recovery


    Version Information
    Status:     Stable

    Created 2018-09-19
    Last Updated 2019-01-18
    View
    18
    Clamor
    Clamor
    Common issues and F. A. Q.

    Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.

    1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.

    2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).

    3. If you want to be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You should check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to describe what you did and enclose partition.log to your post.


    FLO/DEB STOCK
    Code: 
    22      671088640B   1551892479B   880803840B                 system
23      1551892480B  2139095039B   587202560B                 cache

    FLO/DEB MODIFIED
    Code: 
    22      614429696B   2187293695B   1572864000B                system
23      2187293696B  2270167039B   82873344B                  cache
...
30      2348843008B  2610987007B   262144000B                 vendor
    4. After flashing most ROMs system size will reduce to stock, you need to resize /system in TWRP or use flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).

    5. After returning to stock partition table you won't be able to get into the Recovery from the bootloader anymore, but when you start the tablet normally it goes straight in the Recovery. It is normal state. New partition table proposes larger /recovery size (16MB) while stock gives only 10MB. During restoring stock process, it is impossible to restore larger recovery backup into new smaller partition. Whether not to leave user without recovery excess, recovery backup restores into /boot partition. Just flash ordinary TWRP and install ROMs from it.

    6. Don't install the zip file from the USB OTG. Copy them into the /sdcard. Else you will get message after flashing repartition pack.
    Code: 
    "Can not extract updater-script. Do you have it in package?
Updating partition details...
...done"
    View
    15
    R
    rlw6534
    Flashable /system resize with addon.d support

    Here is a flashable zip that will resize the filesystem on /system back to the full partition size after a ROM install. It also includes an addon.d script that will allow upgrades/dirty flashes with persistent GAPPS and Magisk for ROMs with addon.d support (not UA). The addon.d simply resizes the filesystem before the other persistence scripts run. Note that this zip does not change or otherwise mess with the actual partition size - that needs to be performed prior to ROM installation with Clamor's script or other method.

    Simply flash after initial ROM installation. For ROMs without addon.d support (like UA), this script needs to be flashed every time before GAPPS reinstall. For ROMs with addon.d support, you only have to flash once. If you already have a ROM with addon.d support installed, flash this zip before the upgrade/dirty flash to add the addon.d script to /system.

    Thanks to Clamor for support and building the flashable zip!

    Tested on UA and AICP with multiple size GAPPS and Magisk but should work with any ROM...
    View
    7
    M
    mr_rubbish
    Wiping partitions after resize.

    In case someone else gets the same problem as me, I thought I'd share what I did to complete the process successfully.

    -I pushed the repartition.zip file to the device and executed it with TWRP.
    -It completed and rebooted.
    -When i tried to wipe the partitions they all failed with a mount error. Tried multiple times, identical results.
    -Pushed LineageOS zip to device and attempted install. It finished with an Error 7. Essentially a complete failure to install. I think it was something about being unable to mount one of the partitions.

    How I fixed it
    - In TWRP: Wipe > Format data
    - Type yes
    - Once this completes go to: Wipe > Advanced Wipe
    - Tick all the boxes and wipe. There should be no further mount errors.


    However, I wonder if things might have been smoother if the instructions recommended installing the custom TWRP image as step 3, instead of towards the end of the process?
    Anyway, I hope that someone finds these instructions useful!
    View
    4
    Clamor
    Clamor
    @L.F.B. that script is much simplier and offers less opportunities. For some device models (nexus 7 2013 for example) advanced solution is needed. Second is that I can't republish other devs work. Third is that repartition schemes are incompatible with each other and variety of them actually slows down further development. My current repartition for nexus 5 should have no problems.

    @lollyjay UA TWRP is needed to support /vendor partition. Sizes aren't that important for recovery, like for system image, although sizes of partitions are published in my device trees and can be cherry-picked.
    View

New posts