Develop Bugs

After Nandroid Backup Crashing

Has anyone had any problems with a Nandroid Backup?
I have tried twice and had same results - when running unrEVOked 3.21 on my desire, it roots - I go into Clockwork recovery and run a Nandroid Backup which completes successfully.
I then boot up my phone and it hangs on the HTC screen and/or boot loops to the HTC screen again.
I've not actually needed the backup yet as I've flashed custom roms that I'm happy with (like now) and set up as normal and/or ran RUU to go back to stock, which I did the first time it occurred...
Just thought it was an oddity that I'd mention in case I am doing something wrong.
Cheers

Nah, I am seeing this a lot. Quite common for some weird reason. Just ignore it really. When ever I get a hang or bootloop, I just flash the thing again.

That's fine then - just thought it was me - the first time I rooted and backed up it all worked fine - just since then..

Lothaen said:
That's fine then - just thought it was me - the first time I rooted and backed up it all worked fine - just since then..
Click to expand...
Click to collapse
Similar problem here. I had done S-off with Alpharev and found that i could not backup any ROM. i had to install new roms but could not backup any. if i did backup, the phone just freezes at backing up system and thsn nothing worked. pulled battery out and rebooted, my phone just freezes at splash image. finally, i tried flashing the recovery image from CWM ver 4.0.0.5 and all seems working fine now. you should give it a try.

so update CWM and it will work?
mine was s-on by the way.
cheers

Clockworkmod: Error while restoring /data!

I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!

I've discovered the log function under Advanced of CWM. This is what the log is ending with:
tar: can't remove old file data/system/packages.xml: Operation not permitted
#92997temp.dumpefs1.binefs2.binefs3.binS30edt_perms.logzipalign.log.cid.info.psm.info.mac.infoentropy.datbatterystats.binuiderrors.txtusage-20120304usage-20120305usage-20120229usage-20120301usage-20120302usage-20120303packages.xmlError while restoring /data!
Click to expand...
Click to collapse
I Googled around, and came up with this:
http://forum.xda-developers.com/showthread.php?t=1461658
Again, the Galaxy Nexus, with the same problem being this data/system/packages.xml file, and the same solution being Fastboot.
What the heck is going on? Is it possible for us to use Fastboot on our T989's?

manekineko said:
I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
Click to expand...
Click to collapse
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««

raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?

manekineko said:
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
Click to expand...
Click to collapse
Of course it is lol.
»»DARKSIDE««

Thanks for the fix, same thing happened to me. I had the Optimus T before this so I whent flash happy 12 hours after I unboxed this beautiful phone. I've only had this phone a week, you saved my life lol.

this is just now happening to me, this threat is old but very help full lol

Hey all,
not trying to rehash a "solved" thread but Im having this issue and then some.
First, I tried Darksides wipe script and tried to restore the boot and install a new rom, then install the backup, all to no avail. I tried everything. When you get this error, it seems (at least from my experience) that your only hope is to restore from the stock 4.02 google image and then restore from the nandroid. This first happened to me when my phone dropped and off the couch and the battery came out. It seemed to have corrupted the sdcard, or, at least that was my guess.
However, upon redoing everything to stock and restoring the nandroid (even upgrading to the latest ver of clockworkmod recovery), the problem comes back. Im worried about permeneant damage, possibly, but it makes no sense that I would be able to revert to stock and have it working fine. When I reverted and restored from my nandroid, everything worked flawlessly. Then, today, I turned off my phone (which is a rarity, if ever) and it wouldnt boot back up a few minutes later. Bootlooop and the dreaded "error while restoring data!" message. Im going to revert to stock again and start completely from zip, no nandroid. Its possible that the nandroid is corrupted I suppose but i dont believe it would let me restore it than. Any ideas? Could this be from me leaving my phone on practically all the time, without ever turning it off? or the battery coming out while in use? (which makes sense in theory but I've done a battery pull countless times and never had a problem like this). Would there be a way I could determine, for sure if its a hardware problem? Verizon Nexus (hardware ver 9 I believe) now running JB Sourcery 2.0 (from team sourcery...an AWESOME rom, so I dont believe it to be that.)
Cheers!

raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Wow thanks so much for this! Just happened to me on my note 2 and after doing some googling I came across this post and it worked perfectly, first try. thanks again!

i had this problem now.. my hearth stopped to work.. but this guide helped me ! thanx ! so it is working in year 2014 too

raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
plz help me :crying: i am new to this here is my situation i hav a galaxy s4 i9500 i rooted my device 2 days ago and i backed up during the back up it showed no .android_secure found. skipping backup of applications on external storage andalso root error fix . i google it and found its not a big deal so i factory formatted it but when it restored it and restored it all the applications started showing error msg so i formatted sd card and replaced backup folder and tried to back up it showed md5 mismatch so i editted nanroid.md5 with notepad++ and tried to reboot again now its showing recovery data error . what to do?

G3 won't boot @all anymore [Resolved]

So I've bricked my phone. And I can't make it work. Yesterday I finally had some time to thinker with the phone and decided to install Fulmics Rom 6.0. I had already downloaded it a while ago but first now had the time to install it. I made a post in the Fulmic's thread but with their new 6.5 fulmics just out, so my post got berried so quickly so I got no replies.
I started in TWRP with doing a backup, then a wipe and then started the install.
It seemed install was going fine, I even got the Fulmic's GUI midways and selected appropriate model, D855. I tried to keep things as vanilla as possible and chose to not uninstall anything and keep stock temperature throttle back.
But when the install completed I got one error: set_metadata_recursive: some changes failed
Phone wouldn't boot. I had however made a backup before I started and I was able to restore from backup from within TWRP.
Then phone booted and it seemed all was fine. But as I had my mind set on the Fulmics ROM I had one more go, just ti be sure I didn't mess up and chose something bad in the Fulmic install GUI. Also I did a wipe first, then I wiped the cache/dalvik as I once read that could make install easier. And result same as before. set_metadata_recursive: some changes failed.
Tried to reboot but I get flash screen with LG loge and powered by android on the bottom, and then when screen changes to only LG logo it gets stuck'd. No matter how long I wait, and I tried to wait for hours remembering wiping dalvik/cache makes boot take longer time. Stucked on the boot load. Notification light changes from green to blue. And the Lg logo is there.
Worst part is that now I can't even restore it to my backup from yesterday.
Here is my phone:
Lg G3 D855 16 GB 2 GB RAM
Android 6.0 stock LG update.
TWRP 3
Rooted
For now I would settle for a working phone. That is my main priority. Truth be told I got scared now and I don't know if I will take my chances putting a custom ROM onto the phone. After all my android 6 was working nicely, phone was rooted and adaway was working nicely. I guess I got greedy and wanted more

It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.

joppy said:
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
Click to expand...
Click to collapse
Downgrade to twrp 2.8 and flash again hope you are good too to go....

For me , if i have problem.
Replace sdcard , format data on twrp and flash .kdz (not after 30x.0426.kdz) , usually LGup can made download mode it self.
If can booting , make temporary root and get twrp.

Ok I had TWRP v2.8.7.0 laying around. I've used it before with success, so I know it works with my Lg G3.
But still not possible to boot.
I will try to read up on the .kdz as I never even heard of that before. Maybe if I am lucky that will save the day.

Hehe what do you know. TWRP v2.8.7.0 worked!
I dismissed it too fast, turned out it didn't get stuck'd on boot, boot just took a while because I had wiped everything.
Now I can see android is upgrading apps, and also when I think back to the first reboot with twrp v2.8 it was fulmics logo on the bottom part of the screen not android I guess my mind did not pay any attention as I was truly expecting to be stuck in boot loop this time too
Fingers crossed it is working now, I guess I didn't pay much attention when I tested twrp v2.8 and pointed to the fulmics ROM 6.0 and it seems it will work whoha

Finally I've got a working phone, and I also got Fulmics 6.0 as I sat out to get.
Don't know what went wrong or what caused the boot loop, but twrp v2.8 seemed to be the working solution.

IT seems everything works except I lost root. Which is fine for now, I will root another day.
Now I just need to use the dang phone

Deleted for your own safety

Btw, as the phone must be rooted to install custom ROM's it does seems strange that phone after installing Fulmics 6.0 appears to NOT have root, according to RootChecker. Could it be that the custom ROM is confusing RootChecker or did root somehow get revoked?
Is there a manual way I can check to see if phone is rooted? Cos there is, terminal
I took the chance tp get the latest KingRoot v4.9.6 over my previous v4.5.6. And run the APK.
Seems there must have been some issues with SuperSU, I had v2.54 and BETA v2.65. None of them kept root after install.
Found the latest stable that was superSU v2.78 and that fixed my issues.

TWRP ver 3.x messed my phone up too. Thought I had a good EFS backup, but when I needed to restore it, it didn't work. I will not be using ver 3.x again for a long time. Ended up losing my IMEI because of it.

Any issues using TWRP to reload backed up images?

Hi Guys,
I have used TWRP many times in the past to take a snapshop of everything on the phone for backup and also right before I do an upgrade.
This is the first phone I have dealt with that has encryption enabled by default and does make things in TWRP a little tricky.
So the question is with the encryption enabled can I still take a image backup of my working system (9.6.8.0) and then upgrade to MIUI 10. If MIUI 10 doesn't work correctly I want to be able to easily flash right back to the old image and be up and running again.
Thanks!

A/B partitions out of whack

So, I tried some custom roms out there it has caused some really odd issues on this device. The first one I tried was CalyxOs, then lineage, and Proton. All are good roms, but not what I am looking for. But somewhere along the way things got wonky to say the least. Now, I am not blamming any rom or dev for "breaking" my device. I flashed these roms knowing there is a risk, and the roms listed above work for others. I'm pretty confident, there is something I did along the way that screwed things up. Some of the issues I have ran in to:
Before I flash anything, I learned a long time ago, make a backup and transfer all data on sdcard to your pc.
I generally use TTBU. But recently, when I tried to manually drag/drop my sdcard backup to my device, not all files gets transferred over. Basically all the .apk.gz files. Which happens to be the core of the the backup for the apps.
I started using another backup program, oandbackup, which transfers fine. But my apps/data only gets properly restored about 20% of the time. I say 20% because out of 10 flash back to stock and restores, only 2 will successfully work.
When flashing the rom I have been working on, I use lingeage recovery. But what worked yesterday, fails tomorrow. My method has been, flash lineage recovery, flash rom, boot, test rom, flash back to stock, restore. However, it doesn't always work out that way. Sometimes, it will flash fine, I reboot back to recovery and flash gapps, boot system and the loops begin. Flashing a different kernel fixes the bootloop. Oddly though, the stock kernel booted fine on the last flash (mind you, no changes in kernel or rom code). There is a slew of roadblocks and walls I have slammed in to, but this is just to give you an idea as to what I've been trying to work with.
Now, after flashing a custom rom and then flashing back to stock, I always wipe data. But the most recent issue I have encountered, I flashed back to stock. I was on "b" partition. After the initial flash, it boots to fastbootd. Oddly, I was stuck in stock recovery with the little android guy laying on his back. I hit power then vol up and got in to recovery where I selected fastboot and the fashing process continued. After my phone booted, I rebooted back to bootloader, switched to "a" partition, rebooted bootloader, and ran the stock flash script. This way, in my hopes, I would get a fresh and clean flash all the way around. Again, the whole recovery thing happened again, and I resolved it the same way. But when the rom rebooted, bootloops which eventually kicked me back to bootloader. I switched to slot "b" and the rom booted, went thru setup and restored my data, but most apps failed. Luckily, the 1 game I cared about restored this time.
So, yesterday, I wanted to check out stock recovery a little closer, and see if I could use adb. When I tried adb pull <random file on sdcard>, adb did not connect. So, I tried to reboot. Unfortunately, I got stuck at the google boot splash. To recover the device, I had to flash my boot.img.
This morning, I set out on a mission to try and get things fixed back up. I know slot "a" is not bootable, so I figured I would start there. I went to stock images and instead of downloading, I used the online flash tool. nSince I was on slot "b", it flashed to "b" even though I choose to wipe data and force flash all partitions. I tried booting slot "a" but it failed. So, I manually switched to slot "a" and ran the online flasher again. Now slot "a' and "b" both boot successfully. Then I started restoring my sdcard. It is 4.2gb of data. Honestly, not a lot IMO. But it took an extremely long time to restore it. After restoring my sdcard, I ran oandbackup, but I only restored data for 4 apps, which was successful. Everything seems to be running smoothly, and I was able to flash a custom kernel, root, etc with no issues. I guess, when I flash the final beta of my rom, I will see if I got things fixed up or not.
As I write this, I can't help but wonder, what is the root cause of all these issues? One thing I thought of was my cable. I was using one of the usb cables for my oneplus 6t. I switched to the stock cable to test things. I wiped all my data from the sdcard and then restored it with the stock cable. Things went A LOT quicker 928 minutes with op6t cable/2 minutes on stock cable). Since I have things to do today, I have to put this aside for now. But I wanted to get everyone's thoughts and input on this. Have I done something terribly wrong along the way that has caused these issues? Could the cable I was using be the root of all evil in this case? Is this just that wonky of a device, that it has happened to others and a great deal of patience is needed when trying to work on the pixel 4a 5g?