Hello. I wanted to try out some custom ROMs for this phone few weeks ago but before flashing anything I did a backup of stock ROM in TWRP on external SD card. I used this backup once back then and it was working but now, after few weeks on custom ROM, I can't restore it properly anymore. Restoring process in TWRP goes as expected, without any errors, but when I want to boot system it goes into bootloop.
Anything can be done to fix it assuming the backup itself isn't corrupted? I don't know what else details might be relevant here.
Related
I made a backup of the stock ROM using CWM but had issues getting certain ROMs to work until I changed the recovery to TWRP. Is it possible to restore the backup made in CWM with TWRP?
I was planning on backing current ROM with TWRP, going back to CWM; restoring stock ROM, installing TWRP and recreating backup with TWRP but I'm just wondering if it's possible.
Thanks!
EDIT: I found the answer myself not 10 seconds after posting this. I hate it when that happens!! FYI, the answer is No.
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
Played with too many ROMs today. Soft bricked the phone. Had to put 10g back on, root it and then in recovery do a restore. I did the backup with Phil but the restore with CWM but it says Philz. Said that it fail to mmap aboot. And there was an error loki-ifing the boot image.
It has now been restoring for over 4 hours, so I am not sure it is restoring correctly. Suggestions?
Just decided to pull the battery, install Bountyman's ROM and go from there.
Still can't see SD card, so I decided to load the restore. Can't get it to go past the logo screen. I can install several lollipop ROMs but none see the SD card. Other than going to restore the 10g to file and taking the upgrade to KK, are there any other things I can try?
I tried the russian B907 stock rom but now I want to put a backup back that I made in TWRP 2.8.0.1 by BangL. which I downloaded this evening.
As it turned out, the backup must have been made by TWRP 2.8.0.1 "red clown" and now the backup does not want to boot.
Does anyone have a copy for me to download from somewhere? the original on a russian site is gone...
Solved.
It was impossible to put part of the backup back.
I installed B907 again and then reinstalled twrp by BangL again and used that to do a fresh carbon rom (which was the backed up rom) install.
Then in twrp I put the data backup back, nothing else.
Phone is back up and running as it was before trying B907.
I have a problem with my TWRP (3.2.0-0) backups on my le1 pro (us model).
I'm on Cuoco92's ROM 5.5.014S. I saw BetaHydri's CM12.1 and wanted to try it.
First I made in TWRP a backup of my current Cuoco92 ROM. Then I installed CM12.1, gapps and the phone booted, and played a little with it.
I made a TWRP backup of this CM12.1 so I can get back to it and test it later.
I restored the backed up Cuoco92 ROM.
Later I got back into TWRP to restore CM12.1 and after a successful restore and reboot the phone gets stuck on LeEco logo. I tried to wipe/factory reset but without success.
Fortunately the backups of Cuoco92 ROM get restored without problem and the phone boots normally.
Does anyone know what could be the problem? Why do I get stauck on LeEco logo when I restore the CM12.1 backup but not when I restore the Cuoco92 backup?
I got same problem, in my case I wanted to restore the stock Rom but the phone restart to TWRP before restore ends then I tried to restore the CM12.1 backup, I stuck on LeEco logo.
Luckily, after many reboots, the original recovery restored (I don't know how) and I could flash the 11s clean again.
Really its a weird phone!