I'll try and keep this short and to the point, any other info you require to help me out i'll add.
My Z5c is running 32.4.A.1.54, unlocked bootloader and rooted using rootkernel which adds TWRP.
Straight after rooting and after initial setup of the phone I started TWRP and created a backup, all available partitions were selected and the back completed. I then copied it to my PC.
Anyway, no the problem. I was messing with the phone and then after every boot of the phone i kept getting some app crashes. No problem i thought i'll just restore my backup in TWRP. I selected to restore the system and data partion ONLY, then wiped cache & dalvik and rebooted.
It didn't reboot, just the sony logo then a loop back to the sony logo and then into TWRP again. What did I do wrong?
So i decided to restore all partitions except the TA one and that resulted in the same problem. So recover i just flashed stock with flashtool and all is well.
My question is regarding TWRP and restoring a backup. Which partitions do you have to restore? All of them? What is safe to omit when doing a restore?
andybog said:
I'll try and keep this short and to the point, any other info you require to help me out i'll add.
My Z5c is running 32.4.A.1.54, unlocked bootloader and rooted using rootkernel which adds TWRP.
Straight after rooting and after initial setup of the phone I started TWRP and created a backup, all available partitions were selected and the back completed. I then copied it to my PC.
Anyway, no the problem. I was messing with the phone and then after every boot of the phone i kept getting some app crashes. No problem i thought i'll just restore my backup in TWRP. I selected to restore the system and data partion ONLY, then wiped cache & dalvik and rebooted.
It didn't reboot, just the sony logo then a loop back to the sony logo and then into TWRP again. What did I do wrong?
So i decided to restore all partitions except the TA one and that resulted in the same problem. So recover i just flashed stock with flashtool and all is well.
My question is regarding TWRP and restoring a backup. Which partitions do you have to restore? All of them? What is safe to omit when doing a restore?
Click to expand...
Click to collapse
The old TWRP in rootkernel had a backup problem if i remember correctly. Use a newer TWRP.
Thanks, i'll use 'your' TWRP from here.
Related
Edit for anybody who finds this through searching: I fixed it by restoring to stock in Odin, flashing CWM then flashing a new rom. For some unknown reason it bootlooped after the ODIN restore, despite passing md5 checks and being for the correct device, but I could access recovery and used adb to push the files I needed across. Maybe the new rom fixed it, maybe restoring in ODIN did, I don't know!
Hi,
My wifi 8.9 galaxy tab won't complete nandroid backups. I have 3.3gb space (more than enough) and after successfully backing up the boot image, recovery and /system partitions, when it reaches /data it appears to freeze. Around 30s later it reboots to whatever state the device was in. If it was off and turned on to recovery it'll turn on, if I chose "reboot to recovery" from the advanced power menu it reboots to recovery.
I have wiped /cache and delvik cache but this didn't help. The backups created are around 200mb.
I've made nandroids previously with no problem. Updating didn't help (now at 6.0.0.8, I had 5.5.0.4). Current rom is AOKP-5.
Any ideas? I want to flash cm10 but until I get a good backup I don't want to proceed!
Thank you
Hi, I recently bought an unlocked HTC One X+ from Mobicity, it didn't have UK/US English installed. In HBOOT it states that it's unlocked at the top of the screen.
I then took a full backup that is still on the SD card (as well as a copy on my pc), and then installed OrDroid 3.2.1 - this completed successfully but when I rebooted it just hung at the white HTC logo screen.
I left it there for ages, no joy - everytime I'd reboot same thing. I went into CWM Recovery and restored the backup I previously took. This completed successfully but now when I reboot it just keeps going back into CWM Recovyer (5.8.4.0).
I tried using Hasoon2000's utility and this will flash CWM to a later version (6.0.2.7?) and I then retry the restore but upon reboot, it goes back into the previous version of CWM?
I've searched the forums for an Asia RUU/rom but the links to external sites aren't working any more, basically, I'm stuffed - I'll keep trawling through these forums but I could really do with some clear idea of how to fix this?
Thanks very much...
Make sure you're manually flashing the correct boot.img for your rom (this will need to be done with the "fastboot flash boot" command). If you ever restore from a backup, you'll also need to flash your old boot.img manually (this can be found in the backup folder).
NasaGeek said:
Make sure you're manually flashing the correct boot.img for your rom (this will need to be done with the "fastboot flash boot" command). If you ever restore from a backup, you'll also need to flash your old boot.img manually (this can be found in the backup folder).
Click to expand...
Click to collapse
Hi, thanks very much for the reply - so there should be the correct boot.img in the backup I took on the phone (that I copied to my pc as a precaution)? What are the correct steps to restore the backup - do I need to flash the boot.img before or after the restore, and then do I need to clear any caches? Basically, I'm a little unclear on the correct order - I thought I'd been good by taking a backup first, but I've spent ages trying to restore it but haven't been successful.
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
NasaGeek said:
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
Click to expand...
Click to collapse
Thanks again, will try that later and let you know how I get on!
NasaGeek said:
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
Click to expand...
Click to collapse
:laugh::good:
It's easy when you know what you're doing - I cannot thank you enough NasaGeek, that worked perfectly and now I don't have an irate wife any more!!!!! ARGH!! :silly: Anyway, thanks very much for that info - I flashed the boot.img that was in the backup folder, restored my backup and now have a working phone again!
I mistakenly wiped the system files in twrp mode and when I tried restoring the nandroid backup I previously made, it got stuck and only boot and data[excl storage] are getting restored. Now even the nandroid backup has no system files in it. After that, I tried almost every method I knew. I flashed the full fastboot rom via mi flash. After that, it is showing the message as "the system is destroyed".What should I do?
The twrp I am using is twrp -3.2.1-0-mido.img
krunch7520 said:
I mistakenly wiped the system files in twrp mode and when I tried restoring the nandroid backup I previously made, it got stuck and only boot and data[excl storage] are getting restored. Now even the nandroid backup has no system files in it. After that, I tried almost every method I knew. I flashed the full fastboot rom via mi flash. After that, it is showing the message as "the system is destroyed".What should I do?
The twrp I am using is twrp -3.2.1-0-mido.img
Click to expand...
Click to collapse
Did you try installing a custom rom?
krunch7520 said:
I mistakenly wiped the system files in twrp mode and when I tried restoring the nandroid backup I previously made, it got stuck and only boot and data[excl storage] are getting restored. Now even the nandroid backup has no system files in it. After that, I tried almost every method I knew. I flashed the full fastboot rom via mi flash. After that, it is showing the message as "the system is destroyed".What should I do?
The twrp I am using is twrp -3.2.1-0-mido.img
Click to expand...
Click to collapse
Flash the fastboot rom through ADB commands using this method it works https://forum.xda-developers.com/xiaomi-redmi-3s/help/to-flash-stock-rom-miflash-easy-mi-t3678148
This shouldn't happen...i always wipe system partition before flashing any rom...I even wiped system partition during the installation of xiaomi.eu rom once...and it didn't do any harm...
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
Backups and restore on the TWRP with some phone models does not work correctly either because it does not decrypt or is too old compared to the rom or you try to restore an older rom version on a more recent rom and sometimes the reverse also does not work (because of the system).
Try a more recent Twrp (just in case) but anyway the restoration will not be done with a more recent Twrp.
If you are on MIUI micloud works relatively well but obviously you can only restore the data not the system.
https://androidfilehost.com/?w=files&flid=318277
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
try flashing miui 12 rom first, then restore twrp back up (format data also before restoring)
and chose the latest version of twrp for android 11 or 12 (depends on your Rom)
maybe it will work