Hello, I have a major problem with something that should have been a minor project. I used System Recovery to do a backup of the phone. The only thing I can think of there that I might have done differently is save the backup to the external SD card, instead of internal. After the backup completed, I went to reboot the phone and it's stuck on the Motorola splash screen. I tried to pull the battery and go into that general Android Recovery in order to wipe data and try again, but I just get the Android with an exclamation point over his head. I've tried booting it without the SD card too. I was using CM7
Can anyone help please!
EDIT: A couple hours later, since it was my work phone, I had to do something. I reverted the SBF, re-rooted and tried to restore from the backup I made and the same thing happened. I'm going to try to revert to my previous backup. I have a full backup from Titanium Backup if it comes down to it. The phone was working fine, I just can't figure out why it blew up on me after I ran the backup. Grr..
iceolate said:
Hello, I have a major problem with something that should have been a minor project. I used System Recovery to do a backup of the phone. The only thing I can think of there that I might have done differently is save the backup to the external SD card, instead of internal. After the backup completed, I went to reboot the phone and it's stuck on the Motorola splash screen. I tried to pull the battery and go into that general Android Recovery in order to wipe data and try again, but I just get the Android with an exclamation point over his head. I've tried booting it without the SD card too. I was using CM7
Can anyone help please!
EDIT: A couple hours later, since it was my work phone, I had to do something. I reverted the SBF, re-rooted and tried to restore from the backup I made and the same thing happened. I'm going to try to revert to my previous backup. I have a full backup from Titanium Backup if it comes down to it. The phone was working fine, I just can't figure out why it blew up on me after I ran the backup. Grr..
Click to expand...
Click to collapse
sounds like a bad backup. i always use external sd for nandroids and it has never had issues.i would just re-flash. as for stock recovery with andy with an exclamation , push both volume keys. should work regardless of what state the phone is in. i have had it completely unusable and it still worked.
Lorenzo VonMatterhorn said:
sounds like a bad backup. i always use external sd for nandroids and it has never had issues.i would just re-flash. as for stock recovery with andy with an exclamation , push both volume keys. should work regardless of what state the phone is in. i have had it completely unusable and it still worked.
Click to expand...
Click to collapse
OK - You mean to flash cleanly with CM7 and then restore from Titanium backup instead of my previous nandroid backup?
I'm slightly confused about that System Recovery tool, because first I had ROM Manager and it says that CWM is installed, but it doesn't work. Do I have to manually install that System Recovery APK each time I do stuff like this, or does it stay installed? And if so, from a powered off state, how do you enter it? Or do you have to boot up to Android and enter recovery mode from the app? Thanks.
iceolate said:
OK - You mean to flash cleanly with CM7 and then restore from Titanium backup instead of my previous nandroid backup?
I'm slightly confused about that System Recovery tool, because first I had ROM Manager and it says that CWM is installed, but it doesn't work. Do I have to manually install that System Recovery APK each time I do stuff like this, or does it stay installed? And if so, from a powered off state, how do you enter it? Or do you have to boot up to Android and enter recovery mode from the app? Thanks.
Click to expand...
Click to collapse
yes i would try that. second, dont use rom manager. dont delete it either. but it doesnt work on our phone. the bootstrap recovery that you install would only need to be reinstalled if you delete cache in recovery. otherwise it should always work. hope this helps. im not completely sure exactly what you are asking.
try just restoring system part of backup, see if phone will boot, then restore user data
or reinstall cm7 and restore just user data
Sent from my XT862 using xda premium
sd_shadow said:
try just restoring system part of backup, see if phone will boot, then restore user data
or reinstall cm7 and restore just user data
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
I should be fine now, thanks for the advice. I don't know why that backup blew up the phone, but it was sure an inconvenience haha! I just reflashed CM completely, and now I'm gonna roll out my Titanium backup. I don't have a lot of stuff, just the essential stuff for work, so it shouldn't take too long.
Related
Hi, So im in a boot-loop, im gunna use clockworkmod recovery to make a backup reflash my phone with my current stock ROM then recover.
Will my contacts and message be on my phone when i recover???
Silly question but i have to be sure!!!
Cheers, james
jamesbebby said:
Hi, So im in a boot-loop, im gunna use clockworkmod recovery to make a backup reflash my phone with my current stock ROM then recover.
Will my contacts and message be on my phone when i recover???
Silly question but i have to be sure!!!
Cheers, james
Click to expand...
Click to collapse
Have you established what it was that caused the boot loop? It might be worth taking a minute out and trying to work that out before progressing, if it was flashing a custom ROM, perhaps you should try that again, did you wipe etc beforehand?
So you plan is to
1. enter CWM recovery
2. take full Nadroid Backup
3. Perform Wipe
4. Re-flash current ROM (I'm guessing from ZIP file on SD not RUU?)
5 go back into CWM recovery
6. restore data partition?
Sounds good in theory and yes I believe that your messages will exist if you manage to restore data, I can't see what harm it will do - as you need to progress from where you are now.
Although, as I don't know what device you have and how you were intending ro re-flash your current ROM, you need to be careful that in re-flashing if you're using an RUU that you don't lock your bootloader or loose the custom recovery or you may have more work to do!!!
This is why im in a boot-loop
http://forum.xda-developers.com/showthread.php?t=1212063
Im running 'I9000XWJVB' stock.
1. Backup with ClockworkMod Recovery.
2. Flash stock ROM with odin.
3. After my phone boots up restore the backup i made.
Sound good?
Cheers, James
jamesbebby said:
This is why im in a boot-loop
http://forum.xda-developers.com/showthread.php?t=1212063
Im running 'I9000XWJVB' stock.
1. Backup with ClockworkMod Recovery.
2. Flash stock ROM with odin.
3. After my phone boots up restore the backup i made.
Sound good?
Cheers, James
Click to expand...
Click to collapse
Ah, yes, I recall posting on that thread yesterday - shame you couldn't resolve it.
But this route does sound more hopeful. The steps do sound good. Although ensure that you only do a selective restore after the flash as you don't want to perform a full restore or you'll end up back where you are now. So I reckon that you'll only want to restore the data partition.
After restoring the data partition from the backup, I'd suggest that you wipe the cache & dalvik cache from within CWM, before you reboot.
If you use any third party messaging application you may want to install that before you restore.
ben_pyett said:
Ah, yes, I recall posting on that thread yesterday - shame you couldn't resolve it.
But this route does sound more hopeful. The steps do sound good. Although ensure that you only do a selective restore after the flash as you don't want to perform a full restore or you'll end up back where you are now. So I reckon that you'll only want to restore the data partition.
After restoring the data partition from the backup, I'd suggest that you wipe the cache & dalvik cache from within CWM, before you reboot.
If you use any third party messaging application you may want to install that before you restore.
Click to expand...
Click to collapse
So far so good just restoring data part now..............Thank god for that it worked all my stuff is there!!! Im never playing around with that build.prop again ever!!!!! Anyway i have learn abit more on CWM so its not all a loss.
Cheers, James
jamesbebby said:
So far so good just restoring data part now..............Thank god for that it worked all my stuff is there!!! Im never playing around with that build.prop again ever!!!!! Anyway i have learn abit more on CWM so its not all a loss.
Cheers, James
Click to expand...
Click to collapse
Glad to be able to help....I'll be honest I learnt there to....
Although something for the future:
1. Always take a fresh backup before making any un-tested change.
2. Always have you current ROM ZIP on SD card at all times.
3. You can probably export your messages to your SD card (just in case)
Now press THANKS. button.
I used the Root procedure, and it worked fine. Installed Superuser and Busybox, still ok. Then installed the RazrBootstrap.apk. After I powered the phone down and back on, its now caught in an endless loop showing the boot animation. I've tried powering it off, but can't (thanks to no battery removal). I was able to get into a recovery screen by pressing both volume keys and power key together, and tried to restart, but then keeps looping again.
I went back into the recovery menu and tried the factory rest. All it showed was formatting /data and /cache. It didn't look like it did a full reset. Now when I start the phone, it still boot loops, but only gets about 5 seconds into the animation and reboots.
I do have a 2nd working RAZR here if that helps.
I've been told it might be possible to do a Nandroid/CWM backup image of the good RAZR and use it to flash the broken one, but I've never done that procedure before.
Please help, if anyone knows what to do.
I'm thinking it was the RazrBootstrap that caused the problem, as it was working fine after being Rooted and having SuperUser and BusyBox installed.
Do the nandroid backup on the good phone, then use recovery to push the files from the good razr to the bad one, then do a restore of your good nandroid backup. That should do the trick
Sent from my DROID RAZR using XDA App
wrdcndn said:
Do the nandroid backup on the good phone, then use recovery to push the files from the good razr to the bad one, then do a restore of your good nandroid backup. That should do the trick
Sent from my DROID RAZR using XDA App
Click to expand...
Click to collapse
I was told something similar by someone else, but have never done a Nandroid backup and restore. I don't want to mess things up without some type of step-by-step guide.
Someone else said it might not work as the Razrs files have to be "Motorola signed" in order to work.
Too bad there's not an XML restore file for the Razr that can be pushed using RSD.
Funny because I ran into a similar situation with mine in the fact it went into boot loop after the phone had been working fine rooted, I installed TiBu and restarted and phone started looping.
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Click to expand...
Click to collapse
Any help would be appreciated.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
Are you sure you wiped data and cache. Also dalvic. I always flash miui twice also. That happened to me once before and I re flagged and all is well. The reason it is overheating is cause it stays at Max frequency ( CPU). Anyways check out the Miui thread in development if you want to try it again.
As far as your restore error, I don't know.
One time at football camp, I put my shoulder pads in my arse.
I may try miui again in the future, just want to get back where i was before. Thanks.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
creepyncrawly said:
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
Click to expand...
Click to collapse
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
gadget069 said:
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
Click to expand...
Click to collapse
sdcard/.android_secure is the hidden folder where apps2sd puts apps. It might be specific to cyanogen mod and miui, but not sure.
It happened when you first made your nandroid backup via cwm. The other day when I did a backup I watched it and saw the error skipping sdcard cause of no . android_secure . It has to do with cwm not being able to do a restore backup to our external sd. If you go in your external sdcard dir you will see the android secure file. So if next time you want your apps just move the file over for the backup and restore
Sent from my SAMSUNG-SGH-I777
Decided I better ask for help before digging a deeper hole...
I had rooted my Vibrant around September 2010 and tried some ROM at the time, don't remember which one. I didn't keep it for very long...I accepted one or two stock OTA updates thereafter, ending up with 2.1-update1/KA6.
Fast forward to yesterday, when I decided to try to go to Gingerbread so as to be able to install an app I wanted. I chose CM7.2. I presumed I wasn't rooted anymore after the OTA's, so used CWM to run the update.zip that I still had on the SD card from 2010. I did a Titanium backup. I started following the abbreviated directions, then went to the full directions here:http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
So I actually made two nandroid backups as a result of switching between the two sets of directions and getting distracted after I made the first one.
All went well, except after CM7.2 was booted and everything restored from Titanium, I had the following issues:
1. Messaging was broken
2. Most contacts were missing
3. GPS wouldn't lock
I poked around for fixes and tried some, but it was not looking promising. I decided I didn't really need that new app after all, and today tried to revert to stock. I supposed it would be a simple matter of a nandroid restore followed by a Titanium restore. Unfortunately the nandroid restore failed.
Research revealed this is a known issue with "different hboots".
I then compounded the issue by accidentally pressing the power button while in Recovery. The phone rebooted but stuck on the "Vibrant" splash screen, because of the corrupted restore attempt. No amount of 3-button resets got me back to Recovery. The phone is now connected to my laptop in Download mode.
I think what I now need to do is odin, per http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
I will then be able to do a nandroid restore and Titanium restore and be back where I started? Any additional hints, warnings, etc?
Thanks in advance.
Be careful about what you backup with Titanium on stock and then restore on CM. Did you backup your Messaging app or any system data? If you restored system apps or data from a TI backup onto CM from stock, that could cause issues.
And about the contacts, where did you store them before? On Google, SIM, or in memory?
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
m3rb said:
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
Click to expand...
Click to collapse
If you do a nandroid restore you don't need to do a TI restore as nandroid will restore all your apps and data. (Even down to which wallpaper you're using and Wifi networks)
If the KA6 modem works best for you then go for it.
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
You don't need to be rooted, you just need a way to install. For example when you install from stock, you don't need to root it, only flash the custom kernel that has CWM, and then flash, since root is a state of the ROM.
Sent from my SGH-T959 using xda premium
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Well, in our case we can use download mode + heimdall to flash a kernel that has the CWM recovery included.
Sent from my SGH-T959 using xda premium
Well I downloaded the new jellybean zip that just came out for the razr. I loaded it into sd card and then rebooted into clockword recovery. I wiped, data/cache and then tried to install the jellybean zip from the sd card. It gave me an error '"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint")... (much longer). I rebooted my machine, and since I had wiped data/cache it booted right into a fresh install of ICS.
I decided to try to reboot back into clockwork recovery and try to redo the jellybean install from the sd card in case the previous try was a fluke. I ended up getting the same error. So I just said **** it, I'll restore back to a nandroid backup I had made two days ago. During the restore it said that it was unable to restore the "/system" partition. Since this didn't work I thought I'd just wipe data/cache again and just go back to a fresh install of ICS again.
Except this time it just boots into a black screen. All the lights on the bottom of the keyboard are lit up, but nothing is displayed on the screen at all. I believe the phone is on but I do not see any display on the screen at all. Just black. When I hook it up to a computer I am able to access both the internal storage as well as the sd card.
Anybody have any ideas? Maybe I can try loading ICS on the sd card and try flashing that?
My guess would be your backup might be corrupted, system partition is where all the important stuff is, so if it wasnt flashed, your phone cant boot up. Your computer recognizing it is a good sign. Use RSD Lite to reflash a stock ROM from motorola. Some of the stuff i have read about flashing the jb zip are suggesting that anyways after (I haven't done it yet myself) In regards to your backup, you can try it again, but you may have to start from scratch..... You do have your apps backed up with titanium right?
Sent from my DROID RAZR using xda app-developers app
Draxin said:
My guess would be your backup might be corrupted, system partition is where all the important stuff is, so if it wasnt flashed, your phone cant boot up. Your computer recognizing it is a good sign. Use RSD Lite to reflash a stock ROM from motorola. Some of the stuff i have read about flashing the jb zip are suggesting that anyways after (I haven't done it yet myself) In regards to your backup, you can try it again, but you may have to start from scratch..... You do have your apps backed up with titanium right?
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
All of my apps are backed up with titanium but at this point I really just want a working phone lol. My backup got stuck on the /system partition and that is exactly where the jb rom got stuck on. So for whatever reason I can't write to it.
You only flash this in stock recovery. You must be on stock ICS .211
Luke
lukesdiesel said:
You only flash this in stock recovery. You must be on stock ICS .211
Luke
Click to expand...
Click to collapse
Damn, I was running .173 from a while ago. Never even bothered to update to .211 since .173 was running so good. RSDlite isn't even seeing my phone at all even though it is technically turned on with no display.
Edit: Nevermind. I was able to use a utility to restore back to stock ICS.