Howdy folks! New to android/honor 8 and I've been fiddling with it some. So far I've rooted, installed TWRP, SU and Xposed successfully. I've been trying to make a nandroid before completely ****ing up my device, but each time I try I get errors before completion...mainly at the end of the backup I get an error 255 or an error opening the backup directory (internal).
Anyone successfully back up their honor 8 with TWRP?
Appreciate any advice!
I have a copy of my stock rooted ROM with Xposed. What error are you getting? I'm backing mine up to the External SDcard.
Ascertion said:
I have a copy of my stock rooted ROM with Xposed. What error are you getting? I'm backing mine up to the External SDcard.
Click to expand...
Click to collapse
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
fauxfive55 said:
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Click to expand...
Click to collapse
Try backing up to external SD.
Sent from my Galaxy Tab 3 using XDA Labs
I have the same issue. I can't do a backup with TWRP. System, data and boot. It always ends with an error.
I have tried every storage, internal, SD, and OTG drive. Reflashed TWRP. Nothing seems to do any difference. Drives me crazy. Any solution?
just flash stock recovery then flash again TWRP . format SD throw recovery only then try backup should work . happened with me before ! .
Romiui said:
just flash stock recovery then flash again TWRP . format SD throw recovery only then try backup should work . happened with me before ! .
Click to expand...
Click to collapse
Unfortunately that didn't work. Tried flashing stock recovery and back, same thing. Then I flashed latest firmware (total reset), unlocked bl, flashed official TWRP and latest SuperSU. No success. ?
The issue is (or seem to be) data partition fail to mount, or does unmount during backup.
Can't be just me and OP struggling with this.
its really rare issue . i got that problem but honestly it get fixed after that solution !
Backup all other partitions except for the one that fails for now then as that is all you need to fix a bootloop etc and use Ti backup to get the apps etc
Hello,
I'm experiencing the same error when trying to backup to internal memory. I haven't yet tried to flash stock recovery back and after flash TWRP again to check if it solves the problem though.
RM
fauxfive55 said:
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Click to expand...
Click to collapse
I think this has been suggested already but I'm not certain:
Since the only error you're showing us (and maybe getting) is on /system partition Target (backup target), then how about trying unchecking that and doing the backup and seeing if you can get the same error (or not) on the other two (/data and /boot). ? Another thing maybe worth a shot is a completely benign partition like /cache and it's small for a quick test, maybe just give that a try. It'd be good to know that anything at all can be backed up in your version of TWRP.
Just want to see if it's something special about /system [target]. Also have you told us here which version from which thread you got TWRP from? Just curious. For Honor8 there seems to be so many TWRP authors that aren't too sure of their versions of TWRP (yet). Good luck.
hachamacha said:
I think this has been suggested already but I'm not certain:
Since the only error you're showing us (and maybe getting) is on /system partition Target (backup target), then how about trying unchecking that and doing the backup and seeing if you can get the same error (or not) on the other two (/data and /boot). ? Another thing maybe worth a shot is a completely benign partition like /cache and it's small for a quick test, maybe just give that a try. It'd be good to know that anything at all can be backed up in your version of TWRP.
Just want to see if it's something special about /system [target]. Also have you told us here which version from which thread you got TWRP from? Just curious. For Honor8 there seems to be so many TWRP authors that aren't too sure of their versions of TWRP (yet). Good luck.
Click to expand...
Click to collapse
This is interesting, because I have the same problem as well. I've tried backing up to internal as well as SD. I've also tried doing a full reset, flashing back to TWRP and same issue. No matter what partition I try, it always fails with the same error 255. I followed this thread exactly: http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946.
Doesn't seem as rare of an issue as initially thought. Any ideas?
joesee said:
This is interesting, because I have the same problem as well. I've tried backing up to internal as well as SD. I've also tried doing a full reset, flashing back to TWRP and same issue. No matter what partition I try, it always fails with the same error 255. I followed this thread exactly: http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946.
Doesn't seem as rare of an issue as initially thought. Any ideas?
Click to expand...
Click to collapse
It looks like only 2 of the replies in this thread show any hint of success, and even they didn't specifically say they'd done a backup and recovery. I'd kind of like to see a log from a successful backup & recovery before spending much time on this version of TWRP. If it just doesn't work and from every TWRP thread I've read, lots of people are having problems on this phone, so it might not work. I still don't know which version of recovery you all are using and am wondering if it's the official one from twrp.me site? Also, I suppose you'd have to be on android 6 for that to work.
Anyway, I just got mine today (H8), and am seeing if I can live with the size (I really like the 4.6" form factor better), but I really like how things function so far. If I get to the point where I've got Nougat installed without rooting it and still haven't decided to get a refund, then I'll go ahead and do all this stuff and see if I can help. I worked on a bunch of variants of Philz recovery long ago (and it could be completely irrelevant) so I need to look at the TWRP code and try another take on it. For me, one of the best things about rooting is the custom backup and recovery where it actually does those two things perfectly. I guess with the different CPU that there's still a lot of flailing in development land.
One of the few things I really recall being possibly relevant from Philz was how often people who were writing for various devices screwed up the only path to the root of the target by picking one that was either a) a soft link with bad permissions or b) not exactly the right spot. Just because TWRP says "external SD" (or whatever it says) doesn't mean much it's not pointing to something you can write to. I was using a Synology app named DS files today to get some stuff on the H8 and it wouldn't let me put them on the sdcard because it thought I hadn't given permissions to the DS File app. Does that make any sense? I just navigated around until I found a better path to the sdcard that had permissions because there was no way to give sdcard permissions to that app.
Has anyone pointed this out to @LastStandingDroid ?
those were all the same problems I had.
clsA said:
Has anyone pointed this out to @LastStandingDroid ?
those were all the same problems I had.
Click to expand...
Click to collapse
I found LSD seem to be aware about this in his nougat 3.0.2.0 recovery.
He wrote something about data partition unmounting being fixed.
Not sure if this is a known Marshmallow issue though.
Hello!
I've followed the suggestion of flashing stock recovery and after that TWRP but it did not made any difference, same error while backing up DATA.
But, after that I tried disabling compression and it worked OK. I've made a second try and it worked again. After this second successful run, I've tried a third time, but this time with compression enabled again, result.. Error...
Not a very scientific test, but it suggests the error has something to do with the compression.
RM
omartins said:
Hello,
I'm experiencing the same error when trying to backup to internal memory. I haven't yet tried to flash stock recovery back and after flash TWRP again to check if it solves the problem though.
RM
Click to expand...
Click to collapse
Currently there is no data partition backup support
Sent from my KIW-L22 using Tapatalk
I've not tried to restore the backup I've made supposedly successfully with compression disabled, but, I didn't get any error during the backup operation...
RM
Thanks
Thanks Boss love u
Hi there!
Today I've used TWRP Data backup to restore app settings, using TiBu. I can confirm the backup was useful, hence well successfully made.
RM
Related
Hi,
I unlocked and installed TWRP recovery yesterday, and then I flashed CM10.2. All went without problems.
Now I tried to make a backup from within TWRP (2.6.3.0), but it always ends with an error;
Backing up System is fine.
Backing up Data is fine.
But, when Backing up Boot...it ends with the error:
E:Backup file size for '/data/media/0/TWRP...........
I'm 100% sure I installed the correct recovery (-4,2-version)
I also see this on the terminal screen in TWRP:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Any ideas?
realgreef said:
Hi,
I unlocked and installed TWRP recovery yesterday, and then I flashed CM10.2. All went without problems.
Now I tried to make a backup from within TWRP (2.6.3.0), but it always ends with an error;
Backing up System is fine.
Backing up Data is fine.
But, when Backing up Boot...it ends with the error:
E:Backup file size for '/data/media/0/TWRP...........
I'm 100% sure I installed the correct recovery (-4,2-version)
I also see this on the terminal screen in TWRP:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Any ideas?
Click to expand...
Click to collapse
I always have gotten those last two error and I thought the latest TWRP was supposed to have fixed them.
Make sure you have the correct filesystems mounted before starting the backup and you have enough space free on them.
I'm having a similar issue but with restoring any backups. The "boot" partition fails the recovery, but if I choose to restore the other three positions (system cache and data) it goes through.
In "mount" the only options are system (default unchecked), cache, data, Micro SDcard, and SD-Ext (unchecked).
Even with all checked (except sd-ext, which is not able to be checked) /boot partition size is not found.. twrp 2.6.3.0 was on grimlock cm10.2 and got bootloop tried flashing, wiping caches.
I flashed cm 10.2 over the partial restore and got it to work. Flashed twrp again, but the boot and recovery errors remained, thinking of going down to 2.6.1.0, maybe.
Anyone have a solution or idea?
DaringDomino3s said:
I'm having a similar issue but with restoring any backups. The "boot" partition fails the recovery, but if I choose to restore the other three positions (system cache and data) it goes through.
In "mount" the only options are system (default unchecked), cache, data, Micro SDcard, and SD-Ext (unchecked).
Even with all checked (except sd-ext, which is not able to be checked) /boot partition size is not found.. twrp 2.6.3.0 was on grimlock cm10.2 and got bootloop tried flashing, wiping caches.
I flashed cm 10.2 over the partial restore and got it to work. Flashed twrp again, but the boot and recovery errors remained, thinking of going down to 2.6.1.0, maybe.
Anyone have a solution or idea?
Click to expand...
Click to collapse
Instead of restoring the boot partition, you could flash the target ROM to the the boot partition you want and the restore the data and cache and system.
I am having this problem on my tf300t with twrp 2.6.3.0 running cm-10.2. Is there a more recent version that fixes this for this unit?
Also, with 2.6.3.0 (if there is no tf300t upgrade) can I install cm-11?
kmoffat said:
I am having this problem on my tf300t with twrp 2.6.3.0 running cm-10.2. Is there a more recent version that fixes this for this unit?
Also, with 2.6.3.0 (if there is no tf300t upgrade) can I install cm-11?
Click to expand...
Click to collapse
Unofficial twrp 2.6.3.2 has this fixed and can install cm11. 2.6.3.0 will not work with kitkat ROMs; look in scannos omnirom thread for the twrp download.
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4
fixed backup problem
I saw a post elsewhere that has fixed my backup problem. Uncheck data, run backup (success) then recheck data, run backup (success!)
Thought to share.
QUOTE:
Walter DeMoss
• 22 days ago
−
I have asus tf300t with twrp 2.6.3.0-4.2 and cm10.2 stable. All works well but backup fails every time. Backup of system and data seems to go well and generate the MD5 sum. But then immediately it fails.
Have tried backing up to internal and external. Same every time. What am I doing wrong?
Thanks in advance.
•
Reply
•
Share ›
Avatar
Jason Lenz Walter DeMoss
• 9 days ago
−
I was having the same issue trying to backup the stock rom and it was driving me crazy. When I went to backup and left the default partitions selected (System and Data checked with Cache unchecked) it tried to backup three partitions!? It looks like the third partition it was trying to backup was the Boot partition and it was getting some sort of zero file size error at the end of the backup process. I'm not sure why it was trying to backup Boot. Anyway I retried backup only checking the "System" partition, and it correctly backed up only 1 partition. I then tried again selecting System and Data (same as what showed up with the original default) and this time it correctly backed up two partitions. Must have been some leftover spurious setting that was correctly updated when I started manually selecting the partitions. Hope that helps.
1
•
Reply
•
Share ›
Avatar
Walter DeMoss Jason Lenz
• 9 days ago
−
Jason,
Thanks, that was exactly it. Well done.
Walt
UNQUOTE
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
http://teamw.in/project/twrp2/97
ebildude123 said:
Unofficial twrp 2.6.3.2 has this fixed and can install cm11. 2.6.3.0 will not work with kitkat ROMs; look in scannos omnirom thread for the twrp download.
Click to expand...
Click to collapse
Sorry, pretty new... So, I would need to flash this using fastboot? but the format is different when I unzip it. I see a "recovery.img" file in the unzipped folder, along with a META-INF folder containing files. Do I just use fastboot to flash the "recovery.img" file? Do I need to move this to a folder containing fastboot files? Should I rename it to twrp-2.6.3.2?
Also, to revert I would need to flash 2.6.3.0 first?
Thanks again!
kmoffat said:
Sorry, pretty new... So, I would need to flash this using fastboot? but the format is different when I unzip it. I see a "recovery.img" file in the unzipped folder, along with a META-INF folder containing files. Do I just use fastboot to flash the "recovery.img" file? Do I need to move this to a folder containing fastboot files? Should I rename it to twrp-2.6.3.2?
Also, to revert I would need to flash 2.6.3.0 first?
Thanks again!
Click to expand...
Click to collapse
You flash the img file via fastboot or you can flash the zip file in an older version of TWRP, both assuming your bootloader is up to date. To flash old JB ROM, reflash 2.6.3.0 TWRP.
Thanks! (no thanks button in tapatalk....)
Sent from my TF300T using Tapatalk
kmoffat said:
Thanks! (no thanks button in tapatalk....)
Click to expand...
Click to collapse
There is!
Just select the post by touching it, then use the thumb-up icon on the top-right of the screen.
Sent from my TF300T using Tapatalk
I've spent quite a few hours trying to searching for answers tonight and can't seem to find a resolution. I was previously running Cromi-X which i flashed using TWRP. My device is unlocked and rooted. Today I installed Rom Manager and installed the newest touch recovery from CWM (via in app purchase) so that i could load CM or CMB because of my desire for Kit Kat. Initially i was getting an abort as status 7 which i resolved with the help of this post http://forum.xda-developers.com/showthread.php?t=2302599&page=2 however now when i try to install it aborts (trying to flash from SDCard)
I have pulled the log in CWM:
-- Installing: /sdcard/<ROMNAME>.zip
Finding update package...
I: Update location: /sdcard/<ROMNAME>.zip
Opening update package...
Installing update...
Installation aborted.
I: Can't format unknown volume: /external_sd
I: Can't partition non-vfat: datamedia
I ran a full factory wipe before trying to flash any ROMS as well as looked into unmounting/remounting partitions. This is only my second ROM installation and the 1st one was easy enough but now i seem to have prevented myself from flashing anything. I'm curious if the device thinks the external SD is actually the internal SD card since it is named sdcard and if that is causing the issue. Any of you veterans have any ideas as to what might be causing the issue?
TheOnlyBS said:
I've spent quite a few hours trying to searching for answers tonight and can't seem to find a resolution. I was previously running Cromi-X which i flashed using TWRP. My device is unlocked and rooted. Today I installed Rom Manager and installed the newest touch recovery from CWM (via in app purchase) so that i could load CM or CMB because of my desire for Kit Kat. Initially i was getting an abort as status 7 which i resolved with the help of this post http://forum.xda-developers.com/showthread.php?t=2302599&page=2 however now when i try to install it aborts (trying to flash from SDCard)
I have pulled the log in CWM:
-- Installing: /sdcard/<ROMNAME>.zip
Finding update package...
I: Update location: /sdcard/<ROMNAME>.zip
Opening update package...
Installing update...
Installation aborted.
I: Can't format unknown volume: /external_sd
I: Can't partition non-vfat: datamedia
I ran a full factory wipe before trying to flash any ROMS as well as looked into unmounting/remounting partitions. This is only my second ROM installation and the 1st one was easy enough but now i seem to have prevented myself from flashing anything. I'm curious if the device thinks the external SD is actually the internal SD card since it is named sdcard and if that is causing the issue. Any of you veterans have any ideas as to what might be causing the issue?
Click to expand...
Click to collapse
Further information, it appears the issue is around the /data partition. I'm unable to mount it, here is the log:
Error mounting /data!
Reserved block group size: 31
Created filesystem with 11/27932 inodes and 3534/109568 blocks
Formatting /sd-ext...
Formatting /sdcard/ .android_secure...
I: Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete
W: failed to mount /dev/block/mmcblk0p8 (invalid argument)
Error mounting /data!
I: Can't format unknown volume: /external_sd
I: Can't partition non-vfat: datamedia
TheOnlyBS said:
Further information, it appears the issue is around the /data partition. I'm unable to mount it, here is the log:
Error mounting /data!
Reserved block group size: 31
Created filesystem with 11/27932 inodes and 3534/109568 blocks
Formatting /sd-ext...
Formatting /sdcard/ .android_secure...
I: Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete
W: failed to mount /dev/block/mmcblk0p8 (invalid argument)
Error mounting /data!
I: Can't format unknown volume: /external_sd
I: Can't partition non-vfat: datamedia
Click to expand...
Click to collapse
Jeez! Consider yourself lucky you haven't hard bricked - yet! Ditch ROM Manager please! So many users have bricked using it on the TF700!
If you want to try KitKat (CM11) on this tablet you have to be on the 10.6.1.14.10 bootloader and flash CWM 6.0.4.4 or .6 (not available in ROM Manger AFAIK) in fastboot. You have to do a clean install moving from CROMi-X to CM and I hope you made a nandroid, because I expect you to want to move back to CROMi-X in no time... CM11 is still pretty raw (as in: too many things not working) for me at least....
berndblb said:
Jeez! Consider yourself lucky you haven't hard bricked - yet! Ditch ROM Manager please! So many users have bricked using it on the TF700!
If you want to try KitKat (CM11) on this tablet you have to be on the 10.6.1.14.10 bootloader and flash CWM 6.0.4.4 or .6 (not available in ROM Manger AFAIK) in fastboot. You have to do a clean install moving from CROMi-X to CM and I hope you made a nandroid, because I expect you to want to move back to CROMi-X in no time... CM11 is still pretty raw (as in: too many things not working) for me at least....
Click to expand...
Click to collapse
Looks like i need to figure out how to load a new recovery without the ability to launch a ROM. I'll be doing some research tonight. I'm on bootloader 10.6.1.14.10. The reason i used ROM manager is because i couldn't find a good set of instructions on how to flash a recovery on my own.... I'm still relatively new to this.
TheOnlyBS said:
Looks like i need to figure out how to load a new recovery without the ability to launch a ROM. I'll be doing some research tonight. I'm on bootloader 10.6.1.14.10. The reason i used ROM manager is because i couldn't find a good set of instructions on how to flash a recovery on my own.... I'm still relatively new to this.
Click to expand...
Click to collapse
Check out this guide I wrote a little while back. You'll find the instructions on how to install a custom recovery there.
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
Sent from my K00C using Tapatalk
TheOnlyBS said:
The reason i used ROM manager is because i couldn't find a good set of instructions on how to flash a recovery on my own.... I'm still relatively new to this.
Click to expand...
Click to collapse
For a starter you could read the official CM installation guide...
http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t#Flash_a_Custom_Recovery
_that said:
For a starter you could read the official CM installation guide...
http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t#Flash_a_Custom_Recovery
Click to expand...
Click to collapse
But that would make sense... why would i want to do something that made sense? No really i just used google to get started and google is a finnicky B if you don't word your searches right
berndblb said:
Check out this guide I wrote a little while back. You'll find the instructions on how to install a custom recovery there.
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Hey man that guide was fantastic, thanks a lot for your help.
berndblb said:
Check out this guide I wrote a little while back. You'll find the instructions on how to install a custom recovery there.
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I was able to fulfill my desire for kit kat using TWRP based on your guide. Thanks for all of your guys' help salvaging my TF700
TheOnlyBS said:
I was able to fulfill my desire for kit kat using TWRP based on your guide. Thanks for all of your guys' help salvaging my TF700
Click to expand...
Click to collapse
How are you finding CM11? I used it for a day yesterday and found it a bit slow...... I am using it on ROM2SD though and didn't try it on internal so am interested to hear if it runs better?
sbdags said:
How are you finding CM11? I used it for a day yesterday and found it a bit slow...... I am using it on ROM2SD though and didn't try it on internal so am interested to hear if it runs better?
Click to expand...
Click to collapse
well last night after I posted that after i thought it flashed successfully because TWRP said successful. But I've tried CM and CMB and both get stuck on the initial loading screen. So i don't have a clue yet :laugh: I'm going to try and flash Cromi-X back today but TWRP seems unable to clear my dalvik cache or complete the factory reset so I'm going to dig through the log and see what i can figure out.
TheOnlyBS said:
well last night after I posted that after i thought it flashed successfully because TWRP said successful. But I've tried CM and CMB and both get stuck on the initial loading screen. So i don't have a clue yet :laugh: I'm going to try and flash Cromi-X back today but TWRP seems unable to clear my dalvik cache or complete the factory reset so I'm going to dig through the log and see what i can figure out.
Click to expand...
Click to collapse
Did you upgrade your twrp to 2.6.3.2? That is the only one that works with cm11 based Roms. If you are still stuck give me a shout.
sbdags said:
Did you upgrade your twrp to 2.6.3.2? That is the only one that works with cm11 based Roms. If you are still stuck give me a shout.
Click to expand...
Click to collapse
Yea i made sure of that before i got started, I'm re-downloading Cromi right now so i can try to get my tab back into a usable state. Once i get there and make a nandroid I'll start playing with CM flashes. I accidentally formatted my SDcard and wiped everything a few days ago.
Cromi was able to reinstall, i'll let you know after i try to reinstall CM.
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
Click to expand...
Click to collapse
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Are you using latest 2.8.6.0/2.8.6.1?
davebugyi said:
Are you using latest 2.8.6.0/2.8.6.1?
Click to expand...
Click to collapse
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
I am using 2.8.6.1 (latest version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
trionic said:
I am using 2.8.6.1 (last version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
Click to expand...
Click to collapse
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
real_pac said:
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
Click to expand...
Click to collapse
I installed again with TWRP Manager and everything works perfectly now (no error message). Thanks again
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
[...]
Click to expand...
Click to collapse
I faced this error once on twrp 2.8.6.1 a week ago. I wanted to restore my nandroid and the error repeatedly happened while restoring data-partition. I then booted the system and deleted some files from internal storage (which was about half full at the time the error occurred). Afterwards I rebooted to twrp and could successfully restore my complete nandroid. It's a bit shocking if you face this error when restoring a nandroid, because the restore process wipes the data partition first and then begins the restore.
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
That tip worked for me (i9192), I just install the last TWRP (I think this is not needed) and wipe /Data with ext4, wipe again to F2FS and restore, thank you.
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!
Lanchon said:
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!
Click to expand...
Click to collapse
This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.
ajislav said:
This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.
Click to expand...
Click to collapse
added to the github note.
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
king200 said:
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
Click to expand...
Click to collapse
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.
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.
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???.
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.
tsoheq said:
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.
Click to expand...
Click to collapse
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
gascomm said:
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
Click to expand...
Click to collapse
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.
prsa01 said:
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.
Click to expand...
Click to collapse
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.
acr123 said:
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???.
Click to expand...
Click to collapse
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.
tsoheq said:
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.
Click to expand...
Click to collapse
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.
gascomm said:
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
Click to expand...
Click to collapse
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.)
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.
asksmity said:
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.
Click to expand...
Click to collapse
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!
Lanchon said:
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!
Click to expand...
Click to collapse
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!
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
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.
Jazviper said:
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.
Click to expand...
Click to collapse
read:
https://github.com/Lanchon/REPIT/issues/56
tl;dr: you can fix this by pressing the resize partition button on twrp.
hey, something similar happened to me and I am already very frustrated, I had done the whole process of installing the havoc os ROM and everything was going well, until when installing the MagisK from TWRP, it remained on the loading screen (a white circle and It started again and it did not start), I went back to TWRP and reinstalled the backup but when the process is going to finish the following appears: "failed to mount '/ product' (structure needs cleaning), it does not allow me to swipe, install, literally nothing process because it tells me that at the end. I need help, I already fixed the mount system but I haven't found anything for this ...
Did you backup that partition too?
Nvm I just remembered.
The /product partition in Android 9 is an extension of the /system partition
Try format it then mount it again then restore the backup.
Kenora_I said:
Nvm I just remembered.
The /product partition in Android 9 is an extension of the /system partition
Try format it then mount it again then restore the backup.
Click to expand...
Click to collapse
I lost the backup and it does not allow me to carry out any process literally, in the end it throws me that error, the only thing I did was format from the pc, reinstall another version of HavocOs and it came out the same, but I connected it to my pc and it showed me the Havoc battery charging animation, but fails to get past samsung home screen, again ...