Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
You have to install the rooted version first then install the deodexed zip because I believe the deodexed zip only changes some system files, I did the same thing by mistake. So unfortunately you will have to SBF but when you get back up and running just remember to flash the root only zip first then boot into recovery and you can then flash the deodexed zip, hope this helps
luigi90210 said:
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
Click to expand...
Click to collapse
This is what I did last night, just before going to sleep. Thankfully, it worked, so only thing I had to really do was re-apply the theme and 180 LCD Density. Cool that we had the same idea but I'm still concerned about the backup not working, because I definitely don't want to make a habit of SBF'ing any time I don't like a new ROM, though I'm probably going to wait for LibertyGB before I flash another, and I'm fairly certain I will like that one
Thanks for taking the time to read and comment, really appreciate it.
I tried to go back to my stock bg backup also. It went ok and started up but I got force close on all my blur apps. I couldn't get the fc's to stop so I also had to sbf and reload everything.
Related
Quick question for the gurus.
If you wipe everything, factory reset, SBF, and then immediately make a nandroid, what is left over when restoring to that point?
I've done SBF's before, without wiping everything manually, and there was still stuff saved. I've also done restores, where it would appear that some things remained.
Is it possible to have a perfectly (or extremely close) stock restore point? What exactly remains when doing a restore, and what should be done prior to the restore to ensure that it's complete?
Essentially, I would like to swap between Fission and Rubix blurry, as needed, without somehow contaminating the other ROM.
The last time I did a bit too much ROM testing, and was swapping between 5 or more builds, and in the end I found that I was starting to get a lot of force crashes, which of course led me to doing an SBF again.
Thank you,
--bb
bladebarrier said:
Quick question for the gurus.
If you wipe everything, factory reset, SBF, and then immediately make a nandroid, what is left over when restoring to that point?
I've done SBF's before, without wiping everything manually, and there was still stuff saved. I've also done restores, where it would appear that some things remained.
Is it possible to have a perfectly (or extremely close) stock restore point? What exactly remains when doing a restore, and what should be done prior to the restore to ensure that it's complete?
Essentially, I would like to swap between Fission and Rubix blurry, as needed, without somehow contaminating the other ROM.
The last time I did a bit too much ROM testing, and was swapping between 5 or more builds, and in the end I found that I was starting to get a lot of force crashes, which of course led me to doing an SBF again.
Thank you,
--bb
Click to expand...
Click to collapse
Good question. I've had different experiences with SBF, as have others. Sometimes, it does a clean wipe. Other times you need to factory reset to get to 2.3.15 OTA.
In order to do a backup, you MUST be rooted, so your backup is, by definition, not clean. In short, say you had to return your phone to stock so you could get it covered or exchanged, SBF + plus factory reset is your friend.
There is another way on the 928droid site. It's a link to the Stock OTA 2.3.15: http://928droid.com/DroidX.htm
Second link from the bottom. Bon apetit!
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
algorhythm said:
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
Click to expand...
Click to collapse
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
crawrj said:
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
Click to expand...
Click to collapse
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
algorhythm said:
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
Click to expand...
Click to collapse
Try wiping than flashing Olympus and than restore data only.
The data's part of the backup may not be corrupted.
Sent from my SPH-D700 using XDA App
Now that someone made this thread, I'll take the time and explain my issue, I have an MD5 mismatch for all 3 backups I made in the past. I know how it mismatched as well, I renamed the backups to something that actually made sense,like Eclair, EC05, & EG22, problem is, tried restoring any of them, I get mismatch, also, advanced restore also says MD5 mismatch.
P.S. To whoever made clockwork mod, you need to add the option to override the MD5 Mismatch, and also, why use MD5? Its an outdated form of Checking for the Integrity of files, there are newer methods.
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
counterfeit187 said:
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
Click to expand...
Click to collapse
Seems like that was it. Had 0 space once I booted to a new ROM.
Thanks
it would be nice if there was a way to pick the name of your backup instead of it auto generating by time/date..
Hi all... tonight I decided to try the Samurai kernel. Unfortunately, it boot-looped on me. No big deal I figured, I did a full nandroid before in ACS's CWM, so I'll just restore. Unortunately, doing so isn't working: all of my apps, data and settings are gone! It basically looks stock (although, interestingly, all the Sprint bloat I had manually removed before still seems to be gone, so the restore worked to a degree)... I've restored backups before and never had a problem so I'm guessing the kernel is somehow the culprit, but I think that got restored from the backup too so I don't know what's going on. I'm stock EI22 by the way.
Can anyone help me? I'm pretty frustrated at the moment.
Thanks,
Frank
Try restoring an older backup. If that works you can attempt an advanced restore data only from your recent backup to see if it was something in your setup.
Sent from my SPH-D700 using XDA App
That was a thought I had too... I tried TWO older backups that I still had, same problem. I also tried a factory reset and then a restore (in theory it shouldn't make any difference to factory wipe first, and sure enough it didn't, but figured it was worth a shot).
My only other thought is maybe if I odin back to stock, root & install recovery and then try the restore again... kind of a shot in the dark, really shouldn't matter, but maybe.
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
DroidApprentice said:
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
Click to expand...
Click to collapse
I was thinking the same thing D. The only other thing I can think of is bad reads from the sd card.
I tried to go from my AOKP device to a stock rooted rom I downloaded from the Development Section here, but it seemed to go horribly wrong.
I got force closes all over the shop, so I did a Factory Reset and tried again, still got Force Closes.
I tried to restore my Backup, but it seems that 4.2 puts my SDCARD data in a folder called /0/, so TWRP couldn't find them.
I have ended up downloading the Factory Image for 4.2 from Google and have decided to start from scratch. (And deleted ALL MY DATA in the process!!)
So, is there anyway I can root this stock ROM? I have just re-installed TWRP, so I am set with a custom recovery!
http://forum.xda-developers.com/showthread.php?t=1750835
This worked for me.
It might cause a boot loop.. Don't worry about it, let it sit a few..then power off
And restart.(see the last page in the thread.)
taqulic said:
http://forum.xda-developers.com/showthread.php?t=1750835
This worked for me.
It might cause a boot loop.. Don't worry about it, let it sit a few..then power off
And restart.(see the last page in the thread.)
Click to expand...
Click to collapse
Yeah, just done it! Seems to work well!
All I need now is an Extended Power Menu!!
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
shredder47 said:
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
Click to expand...
Click to collapse
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
simms22 said:
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
Click to expand...
Click to collapse
I wiped data, and I don't have a previous ROM or nandroid to go back to, because I (stupidly) wiped EVERYTHING last night, and I've been working on fixing it since then .... I'm currently booted to recovery though, and I may just push a new ROM to it and try again
says my SD card is read only? trying to remount it as rw
I ended up having to reflash all the stock images...
could be worse.
keep a copy of your latest running rom/kernel/gapps in your storage, for just in case. thats my normal procedure, if you dont want to keep a nandroid backup in your storage, because of its size. but a nandroid backup would be ideal
Having the same issue. Tried installing new Carbon nightly (with factory reset) and didn't boot past Google logo. After that I restored my nandroid, which lasted for about a day or two. Today I started getting force closes and phone won't boot. Now I'm backing up everything (ADB rules ) and will try stock image.
Dont feel bad. When twrp updated I didn't notice wipe internal as I usually wipe all but USB in bottom but it was too late. I had swiped my finger and lost everything. Worse? My computer crashed. So RMA backordered so I bought new s2 for backup. I have to fix before sending back. But its not broken. All asurion does is push files and make sure it boots. They wipe everything. So I did most of the job for them lol. I feel stupid as I've never had a problem in four years. Bam I got too far comfy and forgot the twrp updated and had no idea what was added. I will just find a computer and fix or they will get a wiped device with twrp lol not that I think they will do anything as I've heard far worse but I did it so I'll pay if they mention.
Sent from my Nexus 4 using xda premium