Related
Let me preface this: I don't need to use this phone regularly, as my Nexus One is now my primary, but it'd be nice to get this phone back to bootable again.
I loaded up the OpenRecovery version suggested for the CyanogenMod Alpha. From there I took a nandroid backup of my existing ROM (Telus Milestone) and then successfully booted up Cyanogen. After experiencing some of the bugs I decided it was time to roll back.
So I went back into OpenRecovery and restored the full nandroid backup. Well, now I boot up and all I get is the "M". Won't go any farther than that.
So then I tried to flash the GOT version of Telus 2.1 from RSD Lite. It flashed, and then rebooted to... again, the "M", didn't boot further after several minutes. Battery pull again.
Next try - the non-service Telus firmware via RSDLite
(A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf). Rebooting... PHEW! Android bootup screen appears. And it boots, yay. Flashed the vulnerable recovery and returned to OpenRecovery. Nandroid restore but this time *only* system and data. Ick, and once again it hangs... bad backup? Trying a data wipe... it's still not happy, so I guess the system partition is the problem with my backup.
Anyways I have no idea why the backup won't boot, but I suppose I can set it aside, sleep, get done what I need to tomorrow and revisit it on the weekend.
the problem is in your backup. It happened to me twice now that I have to flash the original firmware because the backup also has a problem.
I think I've concluded what the problem is. The modded OpenRecovery that is suggested on the CM6 thread is no good at restoring the system partition. The backup I took from GOT OpenRecovery earlier in September restores fine from GOT OpenRecovery. But none of my backups restore to a bootable state from the other OpenRecovery.
So what I had to do was restore the older backup from GOT, then switch back to the modded recovery and restore only the data partition. And next time I try this I will take my final backup from GOT.
This morning, my Samsung Captivate would not boot. I used Odin 1-click to restore it back to a stock ROM. Then, I re-rooted the phone and attempted to use Clockwork ROM Manager to restore a backup from several weeks ago.
Clockwork seems to run ok. It sees my backup directory and attempts to load the backup. Then it asks if I want to reboot the phone and restore the backup. When I do, it goes directly into manual recovery mode and the backup is not restored.
What am I doing wrong?
Can you boot the phone into recovery then select backup/restore and find your backup in that list? then restore it from there. I always boot into recovery then do whatever i want from there.
Recovery doesn't give me a backup/restore option. Only Reboot, Reinstall files, etc. I thought that it was only Clockwork that has the backup/restore option?
Wait a sec. you went back to a stock rom then rerooted? did it unroot on u? some of the one click roots will unroot you phone if ran while phone is already rooted. kinda a click on click off thing. If you unrooted the phone then it would not let you do a restore. You can do a full factory reset> install clockworkmod,boot into recover and restore backup. just an idea
No, the phone is definitely rooted. The problems I'm having seem to be with Clockwork. I couldn't get clockwork 2.5.1.2 to ever restore, so I downgraded it to 2.5.1.1. I was able to restore, but when I did, I got a whole series of processes with FC loops. It appears that Clockwork did something wrong when it restored my backup.
I finally did the Odin 1 click again, and gave up on restoring. At this point, I'll just re-install everything. I'm disappointed with Clockwork. I would like to find a ROM manager that's more dependable.
woody1 said:
This morning, my Samsung Captivate would not boot. I used Odin 1-click to restore it back to a stock ROM. Then, I re-rooted the phone and attempted to use Clockwork ROM Manager to restore a backup from several weeks ago.
Clockwork seems to run ok. It sees my backup directory and attempts to load the backup. Then it asks if I want to reboot the phone and restore the backup. When I do, it goes directly into manual recovery mode and the backup is not restored.
What am I doing wrong?
Click to expand...
Click to collapse
I just ran into this with my phone..took me quite a while to figure out what I had done wrong.
I had Perception 10.2 ROM on my phone, with Voodoo Lag fix. Today, I decided to try out the official 2.2. release for the Captivate, so I made a Clockwork backup, did an Odin 1-Click back to stock, and installed 2.2. I decided I liked Perception better, so I tried to recover it.
I did another Odin back to original stock, then loaded Clockword and tried to recover my backup. It acted like it worked, unpacking everything, but then booted back to manual recovery mode, and got into an endless loop.
What I wound up doing was running another Odin back to stock, reinstalling the Perception ROM, and THEN restoring with Clockwork. The problem appeared to have been with the Voodoo Lag Fix, which uses a different filesystem.
So, try reinstalling the ROM you made the backup with FIRST, then do your recovery. Good luck!
The rom I was restoring was the same one that I already had on my phone. I think the problem might be this:
I originally had 2.1.1 which was rooted and had one-click-lag-fix installed. When my phone was borked, I used Odin to flash back the same rom. But I think the problem may have been caused because I didn't install OCLF again before I did the restore. I'm not sure, but I have a guess that it might have worked had done that.
I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
All I did was install TWRP with Odin. Then I backed up my phone, without "data" because it was unable to mount /data.
It said the backup succeeded, so I restarted. Now It won't come off the "Samsung Galaxy S7 (powered by Android) boot screen. Is this really typical of TWRP? Brick my phone for backing it up? All I wanted to do was back it up.
I can get into Download Mode and back into TWRP, but it looks like there's nothing in internal storage!!! Wtf??? The stuff on my external SD is there, including the backup. Am I supposed to restore the backup now? Why was it all deleted? What do I do???
Please help. I was backing up in order to make sure this would never happen in the first place!!
SGS7 SM-G930W8, latest TWRP
Where's the sense here? You wanna back up your phone? Sure, let's delete all your data and soft brick it. Not the same thing?
Whaat?
If I don't get a response soon I'll try restoring that backup. THE THING IS... If my data was deleted before the backup, it might only make **** worse... Maybe.
I attempted the backup. Nothing. Strangely, when I press "Restart," it seems to crash and reboot before I get to "Swipe to Restart".
What do I do???? Why is TWRP not trustworthy?!
Too late, I'm attempting to flash stock firmware to my phone now. Where do I complain to TWRP about backing up having the exact opposite effect?
Kilva said:
Too late, I'm attempting to flash stock firmware to my phone now. Where do I complain to TWRP about backing up having the exact opposite effect?
Click to expand...
Click to collapse
If you flash exactly the same version of firmware that your device had when you installed TWRP, it won't wipe your data.
The TWRP team, nor it's code are to blame here. If its an unofficial TWRP then it was built by someone that isn't a part of the TWRP and probably didn't do a good job, especially if this TWRP was ported from a similar model.
Sent from my LGL84VL using Tapatalk
Hey Kliva,
I have run into the same problem. I flashed TWRP 3.2.3 heroflte, booted into recovery and went to do a backup. I only got an error message that TWRP couldn't mount some partitions and no backup.
I tried to reboot and am stuck in boot loop.
Did you get your phone back up running? and how?
Thanks
ntbergeron said:
Hey Kliva,
I have run into the same problem. I flashed TWRP 3.2.3 heroflte, booted into recovery and went to do a backup. I only got an error message that TWRP couldn't mount some partitions and no backup.
I tried to reboot and am stuck in boot loop.
Did you get your phone back up running? and how?
Thanks
Click to expand...
Click to collapse
Flash your stock firmware via Odin.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Flash your stock firmware via Odin.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for getting back to me. I tried flashing stock through Odin several times and each time the process failed.
Out of desperation I found a different kernel and flashed it through TWRP and it worked. The phone booted and everything seems to be working ok.
Thanks again.