[Nook HD/HD+] REPIT: enlarge /system and /data partitions without wiping your data

[Lanchon]

you can now use REPIT to increase the size of the /system partition on the Nook HD/HD+ to 1 GiB to support the newest roms with gapps. while you do this, you can optionally also add 0.5 GiB of free space to /data. the extra space is repurposed from partitions that go unused in custom roms.

see the details here:
https://github.com/Lanchon/REPIT/issues/59

full doc for REPIT is here, please read it:
https://github.com/Lanchon/REPIT

additionally, this note can be interesting for users and rom developers alike:
https://github.com/Lanchon/REPIT/issues/56

this is for Nook HD+ only, but HD owners can request a port of REPIT by following the instruction in the doc page.
UPDATE: a port request was submitted by BultoPaco and now REPIT supports the Nook HD too.

thanks!

 

[ajislav]

you can now use REPIT to increase the size of the /system partition on the Nook HD+ to 1 GiB to support the newest roms with gapps. while you do this, you can optionally also add 0.5 GiB of free space to /data. the extra space is repurposed from partitions that go unused in custom roms.

see the details here:
https://github.com/Lanchon/REPIT/issues/59

full doc for REPIT is here, please read it:
https://github.com/Lanchon/REPIT

additionally, this note can be interesting for users and rom developers alike:
https://github.com/Lanchon/REPIT/issues/56

this is for Nook HD+ only, but HD owners can request a port of REPIT by following the instruction in the doc page.

thanks!

This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.

 

[Lanchon]

This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.

added to the github note.

 

[king200]

Following the guide \https://github.com/Lanchon/REPIT/issues/59 to increase /data,

"you can also add approximately 0.5 GiB to /data"

Does it make difference if the Ovation is 16gb or 32gb model

 

[Lanchon]

Following the guide \https://github.com/Lanchon/REPIT/issues/59 to increase /data,

"you can also add approximately 0.5 GiB to /data"

Does it make difference if the Ovation is 16gb or 32gb model

this was made and tested with the 16GB version. in all other devices REPIT has been smart enough to adapt to these differences automatically. it should work with the 32GB version. but if there's anything strange or too different, REPIT will bail instead of messing up your device.

 

[prsa01]

Ext4 only?

Mine returns an error not able to read superblock on data even if I am only trying to expand system. my data and cache are f2fs. Is that the problem? I'll cut/paste the log here when I'm back on my ovation.

This with the 3.0.2 twrp currently in experimental folder

Update: OK, went back and reread the general instructions. Looks like doesn't work for f2fs. I did convert cache to ext4 and set data=same, but still returned error.

 

[acr123]

Using Android 7 and latest TWRP on Nook HD+. Downloaded repit file zip, renamed as per instructions & downloaded delete stock rom zip. Flashed delete stock rom in twrp w/o problems. Flashed renamed repit file and Got error 1 after flashing. Told to reboot and flash from tmp folder and also got error 1. The error related to unable to reload partition table and unable to mount all partitions. Info from file manager shows using 5.11 GB out of 27.01 GB of internal storage
Any ideas???.

 

[tsoheq]

I just did this today.

I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.

This is how I got around the issue:
I went into TWRP's Advanced menu and open up Terminal. Then I did
umount -a
There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.
Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).

Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.

Hope that helps.

 

[gascomm]

I just did this today.

I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.

This is how I got around the issue:
I went into TWRP's Advanced menu and open up Terminal. Then I did
umount -a
There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.
Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).

Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.

Hope that helps.

I tried following this unsuccessfully - any chance of an idiot's walkthrough?

I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong

 

[tsoheq]

I tried following this unsuccessfully - any chance of an idiot's walkthrough?

I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong

What was the partition size when you do a "df" in a terminal? If it did expand, then the df command should show you the expanded /system partition size.

 

[Lanchon]

Mine returns an error not able to read superblock on data even if I am only trying to expand system. my data and cache are f2fs. Is that the problem? I'll cut/paste the log here when I'm back on my ovation.

This with the 3.0.2 twrp currently in experimental folder

Update: OK, went back and reread the general instructions. Looks like doesn't work for f2fs. I did convert cache to ext4 and set data=same, but still returned error.

f2fs partitions cannot be resized without wiping on planet earth. if there exists an f2fs resize tool, only aliens have it.

you can can wipe data (not recommended) or you can flash the standard repit to simply grow /system with /cache if you want. /data will not be enlarged of course.


f2fs on /cache is stupid, don't ever do it!!! only /data should be f2fs.

 

[Lanchon]

Using Android 7 and latest TWRP on Nook HD+. Downloaded repit file zip, renamed as per instructions & downloaded delete stock rom zip. Flashed delete stock rom in twrp w/o problems. Flashed renamed repit file and Got error 1 after flashing. Told to reboot and flash from tmp folder and also got error 1. The error related to unable to reload partition table and unable to mount all partitions. Info from file manager shows using 5.11 GB out of 27.01 GB of internal storage
Any ideas???.

this has been explained to death now, read the REPIT docs for the solution. create a github issue WITH THE REQUIRED INFO (as detailed in the docs) if you need official support.

 

[Lanchon]

I just did this today.

I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.

This is how I got around the issue:
I went into TWRP's Advanced menu and open up Terminal. Then I did
umount -a
There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.
Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).

Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.

Hope that helps.

you didn't need to reflash system of course, REPIT keeps the data as explained in the docs. glad it worked.

btw, it is enough to follow the docs about unmounting partitions using the TWRP UI.

 

[Lanchon]

I tried following this unsuccessfully - any chance of an idiot's walkthrough?

I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong

read the docs, everything is there. you can't be helped if you don't provide the REPIT log. (that is also stated in the docs, btw.)

 

[asksmity]

Can confirm this works on 32gb ovation. Just finished after a bit of fighting. As always, YMMV but this was the process I followed:

• Ran the delete file. Success.
• Ran the resize file, errors.
• Ran the resize file from tmp, errors.
• Ran "umount -a" from terminal then reran resize from tmp, errors.
• I found both my data and cache partitions were f2fs. Formatted both back to ext4 since f2fs cannot be resized. This was easy for me as I had all the important stuff backed up but be sure to back your data up before doing this, it will wipe the partition.
• After the wipe I loaded one file on to the data drive, the renamed resize file.
• Tried running the resize file. Unmount errors and the run from tmp message.
• Went into terminal, ran "umount -a" 3 times. The first I got several errors, the second and third only one.
• Went into tmp and ran the file. After realizing the process was working and was going to take a while, I plugged up the charger (wall, not pc) and let it set overnight.
• Came back this morning to one error, the fstab error. No unmount errors though.
• Remounted the drives in twrp and ran "df" in terminal. 1gb system.
• Rebooted and ran through the setup
• Reloaded my roms/gapps folder manually via USB
• Rebooted to TWRP and ran opengapps pico. Completed succesfully.
• Rebooted and had play store in apps. Logged into gapps.

Thank you Lanchon, this helps bring life back to an old love.

 

[Lanchon]

Can confirm this works on 32gb ovation. Just finished after a bit of fighting. As always, YMMV but this was the process I followed:

• Ran the delete file. Success.
• Ran the resize file, errors.
• Ran the resize file from tmp, errors.
• Ran "umount -a" from terminal then reran resize from tmp, errors.
• I found both my data and cache partitions were f2fs. Formatted both back to ext4 since f2fs cannot be resized. This was easy for me as I had all the important stuff backed up but be sure to back your data up before doing this, it will wipe the partition.
• After the wipe I loaded one file on to the data drive, the renamed resize file.
• Tried running the resize file. Unmount errors and the run from tmp message.
• Went into terminal, ran "umount -a" 3 times. The first I got several errors, the second and third only one.
• Went into tmp and ran the file. After realizing the process was working and was going to take a while, I plugged up the charger (wall, not pc) and let it set overnight.
• Came back this morning to one error, the fstab error. No unmount errors though.
• Remounted the drives in twrp and ran "df" in terminal. 1gb system.
• Rebooted and ran through the setup
• Reloaded my roms/gapps folder manually via USB
• Rebooted to TWRP and ran opengapps pico. Completed succesfully.
• Rebooted and had play store in apps. Logged into gapps.

Thank you Lanchon, this helps bring life back to an old love.

you are welcome!

lol! why not read the docs???

if you wanted to change the file system in /data to ext4 all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe
which is the same as:
-cache=32M+wipe+ext4-data=max+wipe+ext4
given that ext4 is the default fs for /data and /cache.

using -data=max+wipe would have been so much faster than moving a huge empty partition around!!! it would have finished the operation in around a minute. not to mention adding less wear and tear to the emmc of your aging device.

the file system in /cache was never a problem, you did not need to change it back to ext4. you were using -cache=32M+wipe which means that REPIT would resize/move the partition without keeping its contents (wiping) and without regard for the previous file system type and state (ie, whether it had errors, etc).

if you wanted to enlarge /data AND ALSO KEEP /DATA AS F2FS, all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe+f2fs

f2fs cannot be resized, but it can be moved/resized while wiping. (ie, the partition can be recreated from scratch with the new size, if data retention is not required.) this is all explained in the docs, seriously lol...
https://github.com/Lanchon/REPIT#partition-types

using an f2fs /cache partition is dumb and completely useless. all who have f2fs /cache are adviced to change /cache back to ext4 and leave it that way.

regarding the umount stuff, maybe your TWRP has an issue, but i'm willing to bet that if you followed instructions to the letter, you wouldn't have needed all that. the guy that requested the ovation port of repit (look for the github issue (closed now)) and first ran the test version did not have any of this issues. the TWRP he used is documented in the port request.

anyway, thank you very much for documenting what worked for you!

 

[asksmity]

you are welcome!

lol! why not read the docs???

if you wanted to change the file system in /data to ext4 all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe
which is the same as:
-cache=32M+wipe+ext4-data=max+wipe+ext4
given that ext4 is the default fs for /data and /cache.

using -data=max+wipe would have been so much faster than moving a huge empty partition around!!! it would have finished the operation in around a minute. not to mention adding less wear and tear you the emmc of your aging device.

the file system in /cache was never a problem, you did not need to change it back to ext4. you were using -cache=32M+wipe which means that REPIT would resize/move the partition without keeping its contents (wiping) and without regard for the previous file system type and state (ie, whether it had errors, etc).

if you wanted to enlarge /data AND ALSO KEEP /DATA AS F2FS, all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe+f2fs

f2fs cannot be resized, but it can be moved/resized while wiping. (ie, the partition can be recreated from scratch with the new size, if data retention is not required.) this is all explained in the docs, seriously lol...
https://github.com/Lanchon/REPIT#partition-types

using an f2fs /cache partition is dumb and completely useless. all who have f2fs /cache are adviced to change /cache back to ext4 and leave it that way.

regarding the umount stuff, maybe your TWRP has an issue, but i'm willing to bet that if you followed instructions to the letter, you wouldn't have needed all that. the guy that requested the ovation port of repit (look for the github issue (closed now)) and first ran the test version did not have any of this issues. the TWRP he used is documented in the port request.

anyway, thank you very much for documenting what worked for you!

Very good info above!

I could have done that as well, and probably should have. But there was conformation in the thread that the options I renamed to worked. So for me being a "part timer" I wanted to make sure that I was not the reason for the issue (ie: fat fingering an extra letter in one of the options or misplacing an option). I have a bad habit of screwing things up.

As a recommendation, it might be a good idea to include some of these sample options in you main thread and explain what they do. I know I know, docs docs docs but it helps us roughians and would probably keep the issue posts down.

Thanks again for the tool and the feedback!

 

[BultoPaco]

I read all the docs and used Lanchon's tip above to wipe /data and retain f2fs file structure. Got an error running it from my SD card but, when I ran it from the internal tmp folder (as instructed), it worked perfectly. Thank you @Lanchon! I'm going to request a Hummingbird version so I can have both of my Nooks optimized?

Sent from my Nook HD using Tapatalk

 

[Jazviper]

Is this supposed to provide more space for Gapps? I ran this and it worked with no errors, but I can't install any different sized gapps than nano.

EDIT: nano is still too big too.

 

[Lanchon]

Is this supposed to provide more space for Gapps? I ran this and it worked with no errors, but I can't install any different sized gapps than nano.

EDIT: nano is still too big too.

read:
https://github.com/Lanchon/REPIT/issues/56

tl;dr: you can fix this by pressing the resize partition button on twrp.