Cannot restore backup in TWRP 3.5.2_9.0 - Xiaomi Redmi Note 5 Pro Questions & Answers

Hello. I am currently on TWRP 3.5.2_9.0, and my phone gets stuck while restoring my system partition. The same problem has persisted over many ROMS and even iwhile using Orangefox Recovery. Any help will be great. Thanks.

0Ananta0 said:
Hello. I am currently on TWRP 3.5.2_9.0, and my phone gets stuck while restoring my system partition. The same problem has persisted over many ROMS and even iwhile using Orangefox Recovery. Any help will be great. Thanks.
Click to expand...
Click to collapse
Are you backing up both system and system image and trying to restore both? Try backing up system image alone and restore (not system).

TNSMANI said:
Are you backing up both system and system image and trying to restore both? Try backing up system image alone and restore (not system).
Click to expand...
Click to collapse
Yes. I have been backing up system and other partitions in the same zip. I will try your method and report when I need to restore again. Thanks

And there is update for TWRP...ver3.6.0_9-0

0Ananta0 said:
Yes. I have been backing up system and other partitions in the same zip. I will try your method and report when I need to restore again. Thanks
Click to expand...
Click to collapse
EFS may also give issues while restoring. So backup everything else you want except system and EFS and try restoring.

Related

[Q] seriously need help

I accidentally deleted some system files from my phones. I want to ask that will restoring my ROM will bring me back those files or is there any other way so you can tell that as well.
The files I deleted were related to sound so now there is no sound on my mobile phone now. I also want to tell you that I am using stock android 4.2.1 rom.
Restoring is your best bet. If you have CWM you can also restore a nandroid, reflash, or factory reset.
If you have a backup to restore that should work. Factory resetting the device will not as it just formats /data & /cache leaving /system the same as it was before. If you dont have a backup you can fastboot flash the /system image from a Google factory image.
thanks
Thank you for the reply.
didn't work
The restore option didn't work. What should i do now?
fallu said:
The restore option didn't work. What should i do now?
Click to expand...
Click to collapse
Did you factory reset before restoring the backup? Yes?
Then you need to start fresh = flash stock through fastboot.
Sent from my i9250

TWRP Restore Issue

Hi guys,
I seem to have this problem where my nandroid backup from TWRP won't boot. I can only get it to boot after flashing the Rom over again after the store (this doesn't erase the data and all my file are still there, I just have to make sure I'm flashing the same Rom version as was part of the backup to avoid issues . But I was wondering if there is something else I should be doing here. I've used TWRP in the past and was just able to back up and restore no problem.
When I back up I make sure my system partition is mounted and I usually backup the default selections (boot/data/system, EFS) . My feeling is somehow the boot partition gets corrupted and won't allow the phone to continue booting, but I'm not sure why?
Any ideas? I'm using TWRP version 3.0.2-0. This happens when restoring nandroid for any rom (so far tried with oxygen/hydrogen/miui and cm14).
Thanks in advance.
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
borijess said:
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
Click to expand...
Click to collapse
Standard factory reset on TWRP will erase data, cache and Calvin cache without wiping internal SD card. That's what most people use.
piotrus22 said:
Hi guys,
I seem to have this problem where my nandroid backup from TWRP won't boot. I can only get it to boot after flashing the Rom over again after the store (this doesn't erase the data and all my file are still there, I just have to make sure I'm flashing the same Rom version as was part of the backup to avoid issues . But I was wondering if there is something else I should be doing here. I've used TWRP in the past and was just able to back up and restore no problem.
When I back up I make sure my system partition is mounted and I usually backup the default selections (boot/data/system, EFS) . My feeling is somehow the boot partition gets corrupted and won't allow the phone to continue booting, but I'm not sure why?
Any ideas? I'm using TWRP version 3.0.2-0. This happens when restoring nandroid for any rom (so far tried with oxygen/hydrogen/miui and cm14).
Thanks in advance.
Click to expand...
Click to collapse
I don't have any solution for you but I can certainly concur. I've seen this behaviour as well but not as consistently as what you are describing. About 1/3rd of the time my restores don't work as you mentioned and I have to dirty flash the rom to get it to boot. Sometimes the restore even errors out while restoring the System partition in which case I just dirty flash. This is like my 9th or so Android device since Samsung released the SGS1 in whatever year that was and this is the first phone I've ever had this problem with. On previous phones it would happen rarely but nothing like it does on the OP3.
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
borijess said:
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
Click to expand...
Click to collapse
You can either not wipe internal storage (that is what I do usually) or you can buy an OTG adapter. I think TWRP supports it for our device. You can always copy off your backups via USB then wipe internal then copy your backups back too I think.
Did you for once try wiping the complete device after backing up nans on external storage and thn trying restoring? That would make a difference
Dr-Hack said:
Did you for once try wiping the complete device after backing up nans on external storage and thn trying restoring? That would make a difference
Click to expand...
Click to collapse
What?
piotrus22 said:
What?
Click to expand...
Click to collapse
I think he is asking to do below procedure -
1.Copy your nandroid backup and other imp stuff to computer
2.boot into TWRP
3.wipe all partitions including internal storage
4.copy nandroid backup to phone
5.restore backup through TWRP
Did you mount system to restore backup?
null0seven said:
Did you mount system to restore backup?
Click to expand...
Click to collapse
Yep of course.
JumboMan said:
I think he is asking to do below procedure -
1.Copy your nandroid backup and other imp stuff to computer
2.boot into TWRP
3.wipe all partitions including internal storage
4.copy nandroid backup to phone
5.restore backup through TWRP
Click to expand...
Click to collapse
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
piotrus22 said:
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
Click to expand...
Click to collapse
its one time procedure. Subsequent restore will be fine.
May be different versions of TWRP will help you with this problem
is this issue had been resolved? because i have also the same problem.. whats the fix for this?
piotrus22 said:
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
Click to expand...
Click to collapse
How did you fix your problem? I cant restore my backup also..
it says restore complete but stock in boot logo after... any fix?
toto_vanir said:
How did you fix your problem? I cant restore my backup also..
it says restore complete but stock in boot logo after... any fix?
Click to expand...
Click to collapse
Hey man. No I never fixed it. Just flash your Rom over it and it should boot fine.

Bootloop after restoring a nandroid backup

I made a backup of my 5x when it was running rooted/xposed 6.0.1 but then decided to update to 7.1.1 to try out the new features. But now I really miss a lot of xposed modules so I decided that I want to restore my 6.0.1 backup that I made a couple of weeks ago. So I flashed the 6.0.1 factory image from Google's developer website and was able to successfully boot into Marshmallow again. However after installing TWRP I tried restoring the backup (through USB OTG) after wiping system and cache and a doing factory reset but it pauses on "restoring system image" for a brief moment then proceeds to reboot by itself despite that it's only 27% complete. The reboot however does not go to completion and so the phone is stuck in a bootloop. I'm really not sure where the problem is here. Is it TWRP? Or the backup file? What can I do?
Which version of TWRP have you used? By any chance the backup also contained EFS?
marioemp2k7 said:
Which version of TWRP have you used? By any chance the backup also contained EFS?
Click to expand...
Click to collapse
I used version 3.0.2-2.
And isn't EFS supposed to be backed up anyway? I just checked the backup folder and it contains 4 files that begin with "efs". Should I delete those and try again?
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
marioemp2k7 said:
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
Click to expand...
Click to collapse
I made the backup while I was running 6.0.1 and I flashed the 6.0.1 factory image so they both should have the same vendor image.
I also tried wiping everything except for internal storage and I unchecked "EFS" when restoring the backup but the same problem still persists, the phone automatically reboots itself before the restoring is complete and gets stuck in a bootloop. I'm not sure where the problem is at this point. I guess I'll just have to start from scratch again

Flashing roms doesn't go past flashing "system"

Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe.
Click to expand...
Click to collapse
That's fine, you need to wipe system to flash a new ROM.
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Click to expand...
Click to collapse
How long does it stay stuck? Most ROMs take a lot of time in flashing system because it involves unpacking and flashing firmware. Depends on the installer, really.
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
Click to expand...
Click to collapse
Can you remember if you also selected System partition when making backups? If you did, try restoring after wiping System, data and cache.
mharis05 said:
That's fine, you need to wipe system to flash a new ROM.
Click to expand...
Click to collapse
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Simone98RC said:
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Click to expand...
Click to collapse
That is wrong in any form. There is no rom that needs oos system to be present before flashing. And its not recommended to (dirty flash over a stock rom when switching to a custom rom)
---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------
android_fury said:
Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
Click to expand...
Click to collapse
Did you allow modifications in twrp ? Try to mount system in recovery before flashing / restoring
I ended up fixing it. I went to TWRP to do a regular wipe and saw the option to format partitions. I formatted system and it allowed me to reinstall roms. I flashed CM13 and CM14 with no issues. Thank you all for the suggestions.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

TWRP Restore device is corrupt

I backed up my phone, tossed it onto my computer, used the flashall.bat to wipe my phone, and tried to use TWRP to restore the backup. But now it says the device is corrupt. How do I fix this?
Spartan117H3 said:
I backed up my phone, tossed it onto my computer, used the flashall.bat to wipe my phone, and tried to use TWRP to restore the backup. But now it says the device is corrupt. How do I fix this?
Click to expand...
Click to collapse
What partitions did you restore from twrp?? And, did you do an Advanced wipe in twrp before you restored your backup? Were you just trying to see if twrp worked or what???
Badger50 said:
What partitions did you restore from twrp?? And, did you do an Advanced wipe in twrp before you restored your backup? Were you just trying to see if twrp worked or what???
Click to expand...
Click to collapse
Boot, system, data, vendor. No, I didn't, I don't remember needing to do that in ages with previous phones. Yeah I was troubleshooting an issue on my phone and I figured I'd just be able to restore back to my backup.
Spartan117H3 said:
Boot, system, data, vendor. No, I didn't, I don't remember needing to do that in ages with previous phones. Yeah I was troubleshooting an issue on my phone and I figured I'd just be able to restore back to my backup.
Click to expand...
Click to collapse
Boot, system, and data are ok to restore. You can get into trouble when trying to restore the vendor. The P2XL has a little bit of a learning curve, but it's doable.
Spartan117H3 said:
Boot, system, data, vendor. No, I didn't, I don't remember needing to do that in ages with previous phones. Yeah I was troubleshooting an issue on my phone and I figured I'd just be able to restore back to my backup.
Click to expand...
Click to collapse
On the pixels I always do, boot, vendor image, system image, and data.
Badger50 said:
Boot, system, and data are ok to restore. You can get into trouble when trying to restore the vendor. The P2XL has a little bit of a learning curve, but it's doable.
Click to expand...
Click to collapse
Ah. That's probably it. Back when I had the N6P you had to have a certain vendor image or else you get an error message.
I skipped the vendor and it restored just fine.
mac796 said:
On the pixels I always do, boot, vendor image, system image, and data.
Click to expand...
Click to collapse
The images take up more space, and do we still have to do vendor? Cause that was what was causing me issues.
Spartan117H3 said:
Ah. That's probably it. Back when I had the N6P you had to have a certain vendor image or else you get an error message.
I skipped the vendor and it restored just fine.
The images take up more space, and do we still have to do vendor? Cause that was what was causing me issues.
Click to expand...
Click to collapse
Yeah I wouldn't do vendor it causes problems vendor image will be okay. Also if you get corrupt device you're probably going to have to do the factory image with the w I haven't found a way around it yet. If you have a backup of stock on your phone you could try that that might get you out of it
Also if you're on stock you can just do factory reset in TWRP and just restore Boot and data that's all you really need
mac796 said:
Yeah I wouldn't do vendor it causes problems vendor image will be okay. Also if you get corrupt device you're probably going to have to do the factory image with the w I haven't found a way around it yet. If you have a backup of stock on your phone you could try that that might get you out of it
Also if you're on stock you can just do factory reset in TWRP and just restore Boot and data that's all you really need
Click to expand...
Click to collapse
Nah my restore worked after not restoring the vendor. I was just wondering if backing up the vendor is even needed anymore. I don't remember what it was for, I just remembered that if it was different from your rom version it'd give you an error. But yeah I'm on stock.
Spartan117H3 said:
Nah my restore worked after not restoring the vendor. I was just wondering if backing up the vendor is even needed anymore. I don't remember what it was for, I just remembered that if it was different from your rom version it'd give you an error. But yeah I'm on stock.
Click to expand...
Click to collapse
Yeah I back it up but on stock I never restore it there's no reason to I just restore Boot and data. Your custom kernel and root and everything will restore
Spartan117H3 said:
I backed up my phone, tossed it onto my computer, used the flashall.bat to wipe my phone, and tried to use TWRP to restore the backup. But now it says the device is corrupt. How do I fix this?
Click to expand...
Click to collapse
This happened to me when i changed the partition.
i wonder if the flash.bat image is a different version of Android than what's on the twrp backup
GridironTrenches said:
i wonder if the flash.bat image is a different version of Android than what's on the twrp backup
Click to expand...
Click to collapse
If your backing up/restoring the system, boot, and data, why would it change?? The flash-all.bat is a script anyway. Not sure I understand what your getting at????
Badger50 said:
If your backing up/restoring the system, boot, and data, why would it change?? The flash-all.bat is a script anyway. Not sure I understand what your getting at????
Click to expand...
Click to collapse
i meant the flashed OTA image could be a different version of Android than what's on the twrp backup. maybe a vendor or bootloader image is mismatched but im not sure

Categories

Resources