Related
UPDATE: I've discovered all of my problems seemed to be due to a FUBAR SD card. I wiped, went back to factory, did the stock-to-CM process all over again. Phone STILL either wouldn't boot or would boot but nothing would work with my 2GB card in it. So I formatted a 1GB card I had laying around with 32MB swap, 200MB ext4, and about ~770MB fat32.
Phone now works better than it ever has on any firmware since the day I bought it! It's a lot faster than it's ever been, too. This also explains why I couldn't restore my Nandroid backups. Nandroid and Backup for Root both work great now (and are lifesavers!).
I no longer have any complaints about CM!
Original:
Thank you Mikey1022 for a nice warm threat of banning me for my first post ever. Really makes a newcomer feel welcome around here. My bad for thinking something to do with CyanogenMod and Nandroid was development-related.
Anyway, as was said in my thread that was locked:
The last few times I've updated to a new CM ROM, my phone boots to the android screen, goes black, stays there indefinitely. Have to pull battery.
OF COURSE I always do a Nandroid backup before flashing a new ROM. So I think "well, I'll just revert to my backup." Right?!? No. Whenever I try to restore a Nandroid backup, I get "Error performing restore! Try running nandroid-mobile.sh restore from shell". When I run said command in adb, it tells me:
Verifying backup images...
boot.img: OK
cache.img: FAILED
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: OK
md5sum: WARNING: 2 of 6 computed checksums did NOT match
Error: md5sum mismatch, aborting
How does my cache and data images "fail?"
So I end up wiping, then re-flashing the CM update, and all is well. Except I have a wiped phone, with none of my apps or settings. I know, I know, I should wipe anyway, right? Bull****. I spend a lot of time customizing my phone, getting it just the way I like. I have tons of apps installed, set up how I like. To wipe every two weeks when CM releases a new update is absurd. I don't have to wipe my computer every time Microsoft issues a security update.
So my two questions are: Many other people report flashing the new CM ROMS without having to wipe, so why doesn't it work for me?
And why can't I restore a friggin Nandroid backup? Really, what is the point of making a backup if there's no way to restore it?
Notes: I have a brown T-mo G1 unlocked on AT&T. I just did this whole process today going from CM 4.2.3.1 to CM 4.2.4. I have CM's Recovery 1.4 installed. I have a 2GB SD card formatted as ~1.4GB fat32, ~500MB ext4, 64MB linux-swap. And I have an anxiety problem. I'm eating Xanax like candy.
I am completely with you that it is inconvenient to wipe and flash and have to put all your settings back together. I've also been lurking for a little while and learned that most people are dickbags about posting in the right forum, rather than just helping someone out. Don't take it personally.
The best thing I have found to do is get Backup for Root. I'd recommend MyBackup Pro as well, to be safe. Backup with both before wiping and flashing a new rom, and usually Backup for Root will restore your desktop and settings. Reboot a couple times if things don't come back instantly.
If I were you, I would just take some time out, copy the files on the SD to a hard drive, reformat the card, wipe the device, and reload everything fresh. But that's just me. Good luck
You can flash the restore through fastboot....
take the data.img and
fastboot flash userdata data.img
though if the md5 is messed up...its probably not a good idea, though at the worst you can wipe
B-man007 said:
You can flash the restore through fastboot....
take the data.img and
fastboot flash userdata data.img
though if the md5 is messed up...its probably not a good idea, though at the worst you can wipe
Click to expand...
Click to collapse
What he said. Put all your .img files in the tools of the sdk. In order, the fastboot commands would be:
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Cache and misc don't really matter that much. This will manually restore your nandroid backup.
Thank you very much, FaJu. That is exactly what I needed to know. I will try that next time if I can't get Nandroid to restore.
I also started backing up with Backup for Root, as drspanklebum suggested, so hopefully one way or another I'll make damn sure I can restore my apps and settings if need be!
UPDATE: I've discovered all of my problems seemed to be due to a FUBAR SD card. I wiped, went back to factory, did the stock-to-CM process all over again. Phone STILL either wouldn't boot or would boot but nothing would work with my 2GB card in it. So I formatted a 1GB card I had laying around with 32MB swap, 200MB ext4, and about ~770MB fat32.
Phone now works better than it ever has on any firmware since the day I bought it! It's a lot faster than it's ever been, too. This also explains why I couldn't restore my Nandroid backups. Nandroid and Backup for Root both work great now (and are lifesavers!).
I no longer have any complaints about CM!
I have a new LG Optimus L90 (D415) with stock 4.4 ROM, and TWRP 2.8.0.0 (and previously, Philz 6.58.7) for recovery. Obviously, the phone is rooted and now has an unlocked bootloader....
My problem is that neither recovery will back up (or even mount) "/data". Note that I put that in quotes because, without having "/storage/sdcard" or something in front of it, I presume that it's an internal folder and not something to do with the external SDcard.
My first guess would be a problem with encryption, because both the phone and the external SD are using it -- and I never get asked for the password. Either way, the actual error in TWRP says "E: Unable to mount 'data'", while Philz says it can't access /data/philz-touch for the .ini file.
I've made several Google expeditions to find the answer, and have come up empty-handed with all of them. I've seen all kinds of fixes, from claims that I have to run chkdsk against the SDcard, to backing up the entire /data partition with a tar file and reformatting it with command line nightmares.
I'll do what I have to in order to fix this, but I'd rather not embark on an experimental goose chase. Any ideas?
I have this same problem. But only for wiping and flashing.
I have no idea for fix if backup also not working !! (Noob)
1.TWRP click backup. Select all except SDcard.
Finish backup.
2.go to Wipe menu.>advanced wipe>select all except System and Sdcard.
Wipe.
(It will skip the error files)
3.Install menu. Select ROM to flash.
Was what I did.
fear2433 said:
I have this same problem. But only for wiping and flashing.
Click to expand...
Click to collapse
I'm not flashing anything, yet. First I need to make a backup of the entire phone (not including the SDcard). That way, if something goes wrong, I can just restore my old, working configuration -- all at once -- and start over.
I can back up and restore apps individually, using Titanium Backup. But what I need here is a Nandroid-type backup... and that generally has to be done from the recovery partition. There is one other way to backup everything, using a laptop/PC and ADB. But I've never tried it, and it wouldn't protect against a ROM meltdown.
Solved, somewhat...
So I did some further experimentation concerning this error. I did a test run to install CyanogenMod, and I found that I couldn't even factory reset certain partitions because of these "Unable to mount /data/" type errors.
What was ultimately the problem? The encryption. Once I decrypted everything, TWRP was able to see, mount, and backup, those partitions.
But I was under the impression that TWRP handles encryption, e.g. asking for the password, or some such. I mean, how can you do a Nandroid-type backup on a phone, if no recovery can mount those kinds of partitions?
So, for the record: "E:Unable to mount" was definitely due to the encryption being turned on for my internal storage. Thus the solution (so far) is to decrypt storage. A wretched solution, but at least it works for the time being.
BTW, In furtherance of this research, I formatted my internal SDcard to NTFS, just to make sure it wasn't misaligned or whatever when it was just FAT32. And I discovered that NTFS takes forever to format (32GB on the order of a couple hours)., FWIW.
The plot thickens. It may not be sufficient just to undo encryption, there may be something wrong with the way that partition was created, or otherwise is constructed.
Even though I now am able to mount /data, I'm not able to format it.... in TWRP it says something like "unknown filesystem 'auto'".
But there is a thread here that describes using Philz recovery to unmount and then format this mess, and I'm about to try it, I just have to flash Philz in place of TWRP. Now let's hope this version works without issues, because I'd have little recourse if things go bad there.
My TWRP nandroid backups started to fail out of nowhere with the following error message:
Code:
E:createTarFork() process ended with ERROR=255
And this appeared when doing any type of operation:
Code:
Updating partition details...
E:Unable to stat '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1'
After looking at the log, this is the full info when the error happens:
Code:
I:addFile '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1' including root: 1
E:Error adding file '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1' to '/sdcard1/TWRP/BACKUPS/ZX1C622JHV/2015-07-22--01-07-04_cm_thea-userdebug_5.1.1_LMY48B_ef0c42eec8_t//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/sdcard1/TWRP/BACKUPS/ZX1C622JHV/2015-07-22--01-07-04_cm_thea-userdebug_5.1.1_LMY48B_ef0c42eec8_t/data.info'
E:createTarFork() process ended with ERROR=255
This happened all of a sudden. I did not change anything at all, except for flashing a new CM version in between this and the last successful backup, 2 weeks ago.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Just thought I'd give you a heads up in case anything like that happens to someone else, not sure what the best approach is here, probably do some regular backups of your internal storage, but that's kind of tedious...
Did you try removing corrupted file? (/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1)
Couldn't start up the phone anymore. And don't know how to do it via adb. I only saw that error when I went into recovery after the phone froze and wouldn't boot up anymore.
Hmm, I could have probably used the TWRP filemanager, right?
It was very weird though, at one point even TWRP was not working reliably anymore, after 3-4 reboots it didn't even start up...
using condor.. moto e twrp 2.8.6.0 and same problem for me
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Pranz... said:
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Click to expand...
Click to collapse
using motox xt1092 with twrp3.0.0.0 same problem
Pranz... said:
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Click to expand...
Click to collapse
Same Same : oneplus2 TWRP 3000
ericcostes said:
using motox xt1092 with twrp3.0.0.0 same problem
Click to expand...
Click to collapse
Hi try use TWRP (2.8.7.1) Link
Nexus 7 2012, CM 12, TWRP 3.0.0.0 - same problem
Oppo R7 Plus with the same problem, I´ve tried TWRP 3.0.0. and 2.8.7.
Someone solve this problem?
Note 4 / twrp 3.0.2.0 same problem
Might be a bit late for some, but I just ran into part of this problem myself ...
I did not have the trouble with recoveries, but I was getting the error 255 on backup operations. I am only trying to backup /data.
I was trying to backup to a 128GB USB OTG device, formatted to exFAT, on a OnePlus One.
The backup completed on the stick using the official TWRP, but before I wiped my data I wanted a second backup from a different recovery to ensure I was well covered. I installed TugaPower TWRP and that's when problems started.
Tried a few things, reverted back to 2.8.6 TWRP and wasn't getting anywhere.
Then I took out the stick and using a OTG adaptor I am now running a /data backup to a 32GB micro SD card, also exFAT. It hasn't completed yet, but the older ones would always stop quickly. 15% now ...
Short story ... check the media you are backing up to, there might be an incompatibility there rather than an issue with your device or the recovery.
I will try and do a backup with the TugaPower TWRP on the 32GB card after, too. If that works, then I know that some recoveries have OTG issues.
How to fix error 255 .
I cannt great back up and back up ended with error 255 plz help
Sent from my Le X820 using Tapatalk
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Venrun said:
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Click to expand...
Click to collapse
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Ok. At least I got my biggest problem now.
I think my roblem is wipe data/factory reset does not do job it is supposed to do.
I still see folders and files in internal memory after factory reset. I think that is why install aborts and crashes even after successful install.
I think my problem is that wipe data/factory reset does not do its job
It gives me message it is formatting data cache and stuff. And last day they gave me data wipe complete. But the problem is, in internal memory, I can still see old folders and old files.
I think he should be gone if it is formatted. Where do I get the meaning of factory reset wrong?
Its not what is wrong with me. And how can I make factory reset work
And second question is that I tried to install B&N original operating system from cwm-based recovery. I tried a few different versions of
nookHDplus-factory-2.1.1-plain-stock.zip
However it always fail to install. Install aborted for some reason.
Thanks. It seem helpful.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Venrun said:
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Click to expand...
Click to collapse
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
thanks
leapinlar said:
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
Click to expand...
Click to collapse
trying it. hope it works.
did not work
for about deleting internal data, I went to 'mounts and storage'. used 'format /sdcard' and 'format/ data and/ data/media (/sdcard), but still has stuff in internal memory.
and to my surprise , I have been using CWM-6028. so far. I thought its name was 'NookHDplus-bootable'.
hell. stupid me.
Anyhow, CWM-6028 has been giving me troule
so, I would try other versions.
So far, I have done
1. made boot sd by burning image.
2. copy 'NookHDplus-factory-2.1.0-plain-stock' files and other versions.
3. Insert SD in device and boot CWM.
4. choose zip from sdcard.
5. install factory plain stock.
then I get message 'Failed to retouch 'system/lib/libemoji.so' (WTF is libemoji? and it is always this same file.)
E: error in sdard/nookHDplus-factort-2.2.1-plain-stock.zip(status7)
Installation aborted.
hell. And I tried every factory zip.
Am I doing something wrong?
Failed tp retouch '/system/lib/libemoji' is error message I get
Everytime I tried to install factory stock.
I tried every version of stock files. And I tried all CWM. And even tried TWRP, but it is always the same message what the hell is that emoji?
And what can I do with it?
What frustrates me the most is the fact that it installed 99% in a minute without trouble and stays there 410 minutes until it fails to install. It's driving me crazy
Does CM makes Factory reset by power button and home button does not work either.
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
It is possible you have a bricked emmc. When bricked it looks like it is writing but is really read only and nothing takes. If you still have media files after a successful format data and datamedia then it is bricked. Probably best to get rid of it. You can buy a refurbished unit very cheaply these days.
Sent from my SM-T707V using XDA Premium HD app
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
Assuming that your EMMC is shot, you can try running off SD card this no-emmc version of CM11 ROM: https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/. It's best to use a card with fast randomized block read/write (which is what Class 4 cards are typically best at).
Thanks guys. By the way, what is emmc?
Is it part of CM software?
Does not sounds like hardware.
If I had factory resetted a day earlier, I would not have had problems.
Well. That is the way it is.
I finally kind of got nook working. I am running it on SD card now.
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
digixmax said:
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
Click to expand...
Click to collapse
Thanks a lot. That sounds I can do it.
how you did it
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Please tell how you made SD card work.
thanks.
rkgarg2000 said:
Please tell how you made SD card work.
thanks.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Please confirm if my problem has any other solution
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting. Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
thanks.
digixmax said:
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Click to expand...
Click to collapse
rkgarg2000 said:
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting.
Click to expand...
Click to collapse
Does it boot-loop to recovery?
If so, see http://forum.xda-developers.com/showpost.php?p=55582281&postcount=1459 for potential causes and solutions.
Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
...
Click to expand...
Click to collapse
CWM v6.0.4.6 is not compatible with CM10.x, you need to flash back to the CWM version you previously used.
I am using TWRP 3.0.2-7 which was working fine until yesterday i got this "extracttarfork() error:255" while restoring a backup. I have restored that backup many times before too and didnt tamper with it in any way.
Now i have 5 huge backups on my sd card, none of which can be restored properly, i am saying properly because that error only shows up when the data partition almost finishes restoring. I can restore system and boot without any problem(basically any partition other than data)
According to the information i gathered from net, this error should occur when i am running low on storage which isnt the case. So totally confused
The log is in the zip
Any help will be appreciated, thanks