Alright, so I've been on 3.2.7 for a while and decided to try out the community builds. Here are the steps I took.
1. Flashed eng.stk's twrp-3.0.2-1.26-oneplus3.img
2. Wiped everything except internal storage
3. Flashed community build beta 7
Now, whenever I try to restore a Nandroid backup, it being 3.2.7 (which I understand can fail) or the backup of the community build I just made, the phone is bricked and won't get past the white 1+ screen.
How can I restore data from my Nandroid backups again?
p.s. This modified recovery is warning me that there is "No OS installed! Are you sure?" after each flash or restore. I have to hard-power-off my phone, and after that it boots fine. Is this normal?
Related
My phone is in for service right now and should have a replacement in a couple of hours.
I have been installing roms for quite a while and have ultimately landed on CM9 but I have a very basic question.
When I get my new phone can I just install Clockworkmod and then restore from my nandroid backup of CM9 or must I install Clockworkmod, G Apps, flash nandroid backup, update CM9.
I have always done it the second way but I don't believe it is necessary.
Thanks
You will have to install CM 9 then you can restore from NAN. You got to convert to MTD for it to work.
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").
dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11
So, I've been using TWRP since I purchased this device. I did a TWRP backup today as usual since I wanted to flash back to TouchWiz to update my PRL. I did so, then went to restore my backup. Only part of the backup restored. Now, no matter what I do in TWRP, I get the same error:
E error opening 'data/data/com.newegg.app/share (there's more text here but it's truncated by the recovery)
E error: Not a directory
This happens when I try to wipe (any option), flash a ROM, create a backup, restore a backup, etc. I've updated from TWRP 2.5 to 2.6.3, still to no avail. I don't believe it's a recovery issue. Recoveries don't just stop working, especially after using Odin to write a new recovery partition.
My ROM is screwed up. It boots, but no apps open. The hardware keys don't work (except home).
Any ideas or suggestions? I don't really want to switch to CWM but will if absolutely necessary.
Thanks!
I would suggest doing an ODIN back to Stock. Make sure everything is working correctly. Then Root the Device again.
I did something similar. I used a flash to stock and reset counter .zip that worked. It still threw that newegg error, but once I rebooted, reinstalled twrp, rooted, flashed Slim 4.3 Stable 2 and did another nandroid, the weird error is now gone. So glad I didn't ruin my phone! Thanks!
Your welcome. Happy you got the issue resolved .
TEAM MiK
MikROMs Since 3/13/11
hello guys, yesterday, i changed rom to LOS, of course before changing rom from stock OS to LOS, i made a nandroid backup via TWRP, using adb backup --twrp. Now i want to go back to stock OS, i restore that nandroid i've made with adb restore backup.ab (the filename is backup.ab), when restoring system, it goes well, but when it says "restoring data (excl. storage)" it took long time, i've been waiting for it about 1 hour but it looks like it stuck.
Is there something wrong with my nandroid backup ? because i want my app and data back
I have found that nandriod backup with Twrp 3.6.1 does not work. Has anyone got it working? For me it ends with an error when restoring system partition backup. I have also disabled encryption and still the nandroid backup does not work. If anyone can provide instructions with any particular version of twrp, it will be helpful
I used nandroid backup for restore arrow 11 after wrong experiments with full success. I use twrp: 3.6.1_11-RedmiK40_v3.4_A12-alioth-skkk_49fc7a15.img
I have not tested the same with Android 12.1.