Restore backup from TWRP doesn't work - Xiaomi Mi 5 Questions & Answers

Hello everybody,
When i try to restore a backup made with TWRP version 3.0.2-0 i have a bootloop. I have this problem with ROM from xiaomi.eu and global ROM. (I don't use compression in parameters of TWRP).
I want to know if someone have this problem too? Or, how to fix it.
Thank you

Did you wipe caches after the restore? (dalvik at least)

Thank you so much, it worked

Related

Restoring STOCK (or other) BACKUP after CM

Hi,
I hope that my experience could help other persons that fall in my situation.
After a try of CM, I couldn't restore my stock backup anymore, the phone hanged up in the lg boot screen.
There were no problems about ext4 partition or wiping or fixing permission.
I was thinking to do a NVflash procedure, but i gave another try: using old modaco CWM recovery. I overwrited CWM 4.2.0.2, performed a wipe, installed the modaco zip ext4->ext3 (i didn't remember if i was ext 3 or 4) and then restore my STOCK backup: EVERYTHING WAS FINE!!!
Maybe there's a problem in the newest CWM during restore a backup, i don't know, but in this way i could restore my original firmware.
Hope that this could be usefull.
Did you do your stock backup with modaco CWM? It has different MD5 checksum than the CWM. Might be the case why you can't restore your backup.
No, I did the stock backup with the original CWM.
I think that the problem is in the restore procedure of the original CWM (4.2.0.2), in fact also the CM restore is impossible, only if you install the zip immediately after the restore. Instead... hangs up.
I find when that happens the best method is to reflash the rom your restoring and just restore the data from your nandroid backup. Always works for me.
confirm this issue with cm & nandroid restore
-----------
This is true, restore and then install the rom. But how if your restore is the stock rom? NVflash? It's not the same.
Fortunally, Modaco CWM solve it without this procedure.
Thanks!!
This solve my problem with my stock nandroid restore. I downgrade CWM to 3.1.4 (did the backup with 3.2.8 version) and now works perfect!!
Finally i could restore my stock rom.
my solution was...
1. nandroid backup of mcr
2. full wipe & installed cm7
3. nandroid restore of mcr
4. installed mcr without wipe (this solved bootloop after restoring)

Various problems, including Recovery, Market and mobile shut off

Hi
I'm experiencing these issues during last days:
-Market doesn't download or actualize nothing (Error 492)
-Phone shuts off randomly
-I cannot load CWM recovery
These are my phone specifications:
-V20o Official Leaked Rom
-Horsepower extreme 24BPP RC11 Kernel
-Hp v20o tweaks
-Fast Dormancy Logging fix
-Scrolling Cache Disabler for smoother scrolling
-CWM Touch Custom Recovery installed flashing a zip encountered on xda
I'm experiencing these problems after I installed CM9 beta-rom (and the proper google apps) and then I went back to the V20o doing three wipes and restoring a previous Nandroid Backup
Any suggestion?
Thanks
The problem is I think touch recovery. It contains a bug when your wiping cache. The problem is that after wiping it, it won't rebuild, so this will crash your market and may also cause the other problems.
What you could do is change your recovery.
Thank you very much
So I should not wipe cache when i run a Nandroid restore?
I ask you this 'cause when, after installing CM9 (doing three wipes procedure), i rebooted into recovery to restore Nandroid backup and it seemed to work well. I began to experience problems when I loaded Rom after it.
Anyway is there any chance to reinstall old version CWM without reinstalling the Rom?
scompiani said:
Thank you very much
So I should not wipe cache when i run a Nandroid restore?
I ask you this 'cause when, after installing CM9 (doing three wipes procedure), i rebooted into recovery to restore Nandroid backup and it seemed to work well. I began to experience problems when I loaded Rom after it.
Anyway is there any chance to reinstall old version CWM without reinstalling the Rom?
Click to expand...
Click to collapse
The problem occurs after every cache wipe, because it should rebuild after every wipe and that's the problem.
The easiest way to reinstall a CWM version is using ROM Manager and restore to CWM version 5.0.2.0. I know it's kinda old, but it'll do good enough.
EDIT: If you for some reason really don't like CWM 5.0.2.0, look at this thread: http://forum.xda-developers.com/showthread.php?t=1478995
You can find a flashable zip somewhere of CWM 5.0.2.7
Touch Recovery i had was flashed from that .zip file you're telling me! Anyway i tried to install old CWM version in Rom Manager but it didn't resolve the problem.
I will manage to reinstall everything.

[Request] Brazilian 4.4.2. CWM nandroid after wipe

Hello,
Any fellow Brazilian to do a 4.4.2. clean (after wipe) nandroid for me?
It is easy, you just need to do a nandroid of your current rom with your softwares, wipe and do another nandroid with the wiped rom!
I will try to do a flashable of it so we can make it available to everyone.
Thanks!

[Q] Questions before flashing custom ROM

I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.

[Q] problem with nandroid backup, pleas help me :)

guys I have a problem with restoring the nandroid backup on MI 8 Global
I have the TWRP 3.2.3-3, I made the complete nandroid backup of weekly rom 9.8.1 (system, vendor, image system, efs etc ... etc .. etc. ..) .... after executing the wipe data , dalvik, system and cache I tried to install another rom (not old miui firmware but AOSP resurection remix) but it returned error 7 and I then gave myself the restore .... I tried to restore the complete nandroid backup excluding only efs (system, vendor, image system etc ... etc .. etc. ..) but the phone no longer starts the miui but restarts continuously (it is not brick but no longer loads the rom)
for greater clarity I write the various steps performed
entered recovery
resurection remix installation but gave me the error 7
I redid the advanced wipe for system, data, dalvik, cache
I did the full restore except for EFS and recovery (boot, system, vendor image etc .....)
reboot
bootloop
where would I have gone wrong and in particular how can I correctly restore the nandroid backup ?????
pollopopo said:
guys I have a problem with restoring the nandroid backup on MI 8 Global
I have the TWRP 3.2.3-3, I made the complete nandroid backup of weekly rom 9.8.1 (system, vendor, image system, efs etc ... etc .. etc. ..) .... after executing the wipe data , dalvik, system and cache I tried to install another rom (not old miui firmware but AOSP resurection remix) but it returned error 7 and I then gave myself the restore .... I tried to restore the complete nandroid backup excluding only efs (system, vendor, image system etc ... etc .. etc. ..) but the phone no longer starts the miui but restarts continuously (it is not brick but no longer loads the rom)
where would I have gone wrong and in particular how can I correctly restore the nandroid backup ?????
Click to expand...
Click to collapse
Xiaomi.eu ? If yes, install 9.8.1, restart to system, restart to twrp and restore only data. Change old twrp to the latest 3.3.1.1
mar.ur said:
Xiaomi.eu ? If yes, install 9.8.1, restart to system, restart to twrp and restore only data
Click to expand...
Click to collapse
before installing the 9.8.1 I have to do a full wipe (system, data, dalvik etc.) or just a soft wipe (without system)
a curiosity I have the xiaomi.eu for a long time, the xiaomi.eu has the rool back or not ?? why resureciont remix gave me error 7 using 9.8.1 by first running a full wipe or simply not having to delete system ??
because nandroid backup not working correctly??
pollopopo said:
before installing the 9.8.1 I have to do a full wipe (system, data, dalvik etc.) or just a soft wipe (without system)
a curiosity I have the xiaomi.eu for a long time, the xiaomi.eu has the rool back or not ?? why resureciont remix gave me error 7 using 9.8.1 by first running a full wipe or simply not having to delete system ??
Click to expand...
Click to collapse
Do a full wipe.The old twrp probably caused error 7 when you installed RR. Try 3.3.1.1. Besides that firmware 9.6.20 is the best for almost all custom roms based on Pie
mar.ur said:
Do a full wipe.The old twrp probably caused error 7 when you installed RR. Try 3.3.1.1. Besides that firmware 9.6.20 is the best for almost all custom roms based on Pie
Click to expand...
Click to collapse
ok, thaks for the advice i resolve for bootloop and i test the old firmware 9.6.20 with the 3.3.1.1 TWR
I offered you a cup of coffee :good:
pollopopo said:
before installing the 9.8.1 I have to do a full wipe (system, data, dalvik etc.) or just a soft wipe (without system)
a curiosity I have the xiaomi.eu for a long time, the xiaomi.eu has the rool back or not ?? why resureciont remix gave me error 7 using 9.8.1 by first running a full wipe or simply not having to delete system ??
because nandroid backup not working correctly??
Click to expand...
Click to collapse
Not exactly about NANDroid backup but about TWRP.
a) some twrp versions won't restore and backup properly. The suggested twrp above has no issues.
b) you can't use NANDroid backups with different versions of TWRP. You need to restore it using the version you had the backup, so your backup is probably trashed now.

Categories

Resources