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
Related
Hi,
I've been using cyanogen mod 9 without any issues. recently i upgraded to cyanogen mod 9.1 and have been noticing minor glitches. nothing to be worried about. Recently i used Bluetooth to share files ( have used it before). when i powered off the Bluetooth it rebooted and is now stuck at boot animation. Also cannot connect to my PC. any suggestions or workaround to the problem? would be appreciated.
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
MistahBungle said:
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
Click to expand...
Click to collapse
I'm sure there is a bug in Bluetooth implementation in mod 9.1. I did a cache wipe, after that it was stuck in another kind of loop. rebooted normally, immediately Bluetooth turns on and it reboots again.
how do i reboot into recovery? previously i was using adb for that. i restored backup ( it was of mod 9) now it wont even boot.
ok. so i finally managed to get it working. i had accidentally restored mod 9 backup onto mod 9.1 so i used odin to flash ClockworkMod-Recovery_5.5.0.4 booted and now i'm back to a month older backup. Oh well since i have to restore my settings anyway why not try mod 10.1?
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.
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...
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.
Hi,
I tried to uninstall the security package in stock MIUI Rom, however I started getting bootloops after that. I made a TWRP backup just before trying this out, so I tried to restore it. However even after restore I'm still getting bootloops.
Then I tried to Wipe everything, however TWRP reports error can't mount vendor partition (structure needs cleaning). I can't mount Vendor either in Mounts. It could be restore operation is unable to bring back vendor partition that is why it is still failing ?
What can I do to fix it ? I still would want to restore my backup, don't want to flash another ROM right away..
I'm on stock MIUI 10.2 ROM with official TWRP and Magisk installed.
Apprantly I'm not the only one, it seems TWRP can't properly restore MIUI roms