It seems like no matter what ROM I try to restore a nandroid of, my phone freezes during the process. For example; this morning I made a backup of Eclipse 2.2. I SBF'd to 2.3.4 to try out CM9, I decided to return to Eclipse. SBF'd again, rooted, backed up root, OTA'd to 2.3.5, restored root, flashed Eclipse 2.2, and now I'm trying to restore my nandroid and BSR is frozen at the 'lib' portion. This happened to me all the time when jumping between CM7 and BLUR while on 2.3.4. I have no idea why this always happens but my only option is to SBF and start from scratch anytime I want to try out a ROM or return to one. Why is this happening? Can I prevent it? It's extremely annoying and I never had this problem with any other device besides this one.
jaj6503 said:
It seems like no matter what ROM I try to restore a nandroid of, my phone freezes during the process. For example; this morning I made a backup of Eclipse 2.2. I SBF'd to 2.3.4 to try out CM9, I decided to return to Eclipse. SBF'd again, rooted, backed up root, OTA'd to 2.3.5, restored root, flashed Eclipse 2.2, and now I'm trying to restore my nandroid and BSR is frozen at the 'lib' portion. This happened to me all the time when jumping between CM7 and BLUR while on 2.3.4. I have no idea why this always happens but my only option is to SBF and start from scratch anytime I want to try out a ROM or return to one. Why is this happening? Can I prevent it? It's extremely annoying and I never had this problem with any other device besides this one.
Click to expand...
Click to collapse
When you say OTA do you mean the latest OTA put out or the older 2.3.5 update zip? Eclipse 2.2 runs on the latest OTA.
Sent from my MB870 using Tapatalk 2
Maybe a bad memory card? That's the only thing I can think of. Try a different one and see if the problem persists. Or try making a nandroid but using internal storage and see if that works.
Sent from my MB870 using xda premium
Thanks for the suggestion!
Sent from my DROID X2 using xda premium
Related
Just went through the entire 4 hour long process of SBFing to 2.3.3, doing the 2.3.4 OTA, rooting, updating to custom rom, then restoring all my sms/mms etc etc but not system data. I just flipped through the apps and noticed the new icons.
Its smooth as butter except (Edit: It Was... now its laggier then 2.2.2 stock), I just went into About Phone to see If I turned off the upgrader 2.3.4. Their I noticed It said I was still on 2.3.3.
As you can see the kernel is 2.3.4, the build is 2.3.3 and it's telling me to upgrade to 2.3.4. All my system apps says 2.3.4, and I'm on a custom rom (Moto-Ginger-Funk). I doubt I'd be able to install that with no errors if I wasn't. So would just like to ask, what the hell is going on here? I have no problems, a couple force closes after first restore of stuff but a reboot fixed that.
Had to Flash some stuff to the phone and just went into About Phone again and now it says 2.3.4 . Looks like I found another bug, even if it's not that big but it is weird.
It might have just been reading from old data and finally caught up. I am assuming this was after initial startup?
i think you might be using a kernel and system from seperate levels of gingerbread. like one is on 2.3.3 and one form 2.3.4. remember we cant really use a custom rom due to no unlocked bootloader so the rom your using could have system files from both.
AtLemacks said:
It might have just been reading from old data and finally caught up. I am assuming this was after initial startup?
Click to expand...
Click to collapse
No this was after rebooting about 4 times adding stuff into recovery.
^I kinda hope not since everything now says 2.3.4.
You know when I did the sbf it only took 15-20mins and I still had everything that I had when I was on eclipse 0.2.2 except for root. It had all my settings and txt messages. The only thing I had to do was root and *228. I thought sbf was supposed to get rid of everything.
Sent from my DROID X2 using XDA App
(aq) said:
i think you might be using a kernel and system from seperate levels of gingerbread. like one is on 2.3.3 and one form 2.3.4. remember we cant really use a custom rom due to no unlocked bootloader so the rom your using could have system files from both.
Click to expand...
Click to collapse
What? Dude, we have custom roms, just not custom kernels. We have root, we have everything except an unlocked BL. He didn't flash the 2.3.4 rom based on the 2.3.3 kernel, he took the OTA update. You are not very savvy in this are you?
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
densetsu86 said:
You know when I did the sbf it only took 15-20mins and I still had everything that I had when I was on eclipse 0.2.2 except for root. It had all my settings and txt messages. The only thing I had to do was root and *228. I thought sbf was supposed to get rid of everything.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
You still need to do a full data/system wipe if you plan on going back to complete stock. This is why a lot of people get stuck in boot loops because they don't wipe cache/davlik, or do a full wipe.
I did the sbf a couple of days ago and I had no problems. Hell my phone is running the best it has ever have. I used to hate this phone but after 2.3.4 I love it.
Sent from my DROID X2 using XDA App
Yea re-did it this time SBF not OTA and its running great. Before it was awful.
I just got my replacement X2. I rooted it, installed the recovery bootstrap, and tried to restore one of my last backups. It restored, I rebooted, but now it just sits at the Dual Core screen. No boot loops, just frozen.
I did have the V6 supercharger script, so I'm thinking maybe it doesn't like being re-applied through a nandroid backup? I can't think of any other reason it would do this.
I'm SBFing it already, but has anyone else run into this?
did it freeze at the dual core screen? or did it boot loop? did u install a custom rom?
It froze at the dual core screen, no boot loop. I didn't install a custom ROM, all I did was root it and try restoring the nandroid backup that I ran while I was SuperCharged.
It just finished SPFing so maybe I'll try to manually supercharge it before restoring this time.
It was also on the 2.3.4 OS, could that have something to do with it also? I'm not sure if it likes restoring to newer versions of Android or not.
Be sure your replacement is running the same sbf as the one your backup was based on. Ie. Your backup was on 2.3.4 and your new phone shipped with 2.3.3 you would need to sbf to 2.3.4 first..
Or if ya were still on 2.3.3 and that was your backup and your phone shipped with 2.3.4 you need to sbf back to 2.3.3.
Im sure this is your issue.
mastafunk said:
Be sure your replacement is running the same sbf as the one your backup was based on. Ie. Your backup was on 2.3.4 and your new phone shipped with 2.3.3 you would need to sbf to 2.3.4 first..
Click to expand...
Click to collapse
Ah ok, that's what I edited in my last reply... I figure it may not like that.
I already SBFed to 2.2, I assume I can just update to 2.3.4 normally and then root/bootstrap/restore again?
Yes. You only need to sbf once to your target version then root/install recovery and restore your backup.
Yep, that worked like a charm. Phone is back to the day it was before I sent it in. Only one app so far is broken.
Now I just need to figure out if it's Supercharged again or not.
I'm thinking about SBFing my rooted x2 back to 2.3.3 from 2.3.4 because of the terrible battery indicator, and was just wondering if I would be able to update straight to 2.3.5 (or possibly ICS) when the update comes. I don't know why this wouldn't be possible, but I just wanted to make sure before I actually SBFed the phone.
I also was wondering if my phone would still be rooted after the SBF because of the maintain-root-through-any-update mod. Any thoughts?
On a different note, if I had the x2 bootstrap, the maintain-root-through-any-update mod, and MyBackup Root, could I just backup all my apps and the system (using MyBackup Root and the bootstrap, respectively), SBF, then restore the phone by downloading the bootstrap and MyBackup Root and restoring my apps/system? Would this get my back to where I was before, or would I have to manually download each one of my apps and lose all previous data that I had on them? I'm just wondering what's the easiest way to restore my phone back to the layout that I had before I SBFed.
Thanks for your answers to any of these 3 questions!!! I definitely appreciate it.
germmeetsworld said:
I'm thinking about SBFing my rooted x2 back to 2.3.3 from 2.3.4 because of the terrible battery indicator, and was just wondering if I would be able to update straight to 2.3.5 (or possibly ICS) when the update comes. I don't know why this wouldn't be possible, but I just wanted to make sure before I actually SBFed the phone.
Click to expand...
Click to collapse
Perhaps someone elses experience proves different however, I kept 2.2.2 on my DX2 for quite some time because of similar reasons. When I decided to take the plunge from 2.2.2 and upgraded to 2.3.4 OTA, my phone needed to first upgrade to 2.3.3 before it would upgrade to 2.3.4. Thus, I had to perform two separate OTA updates.
If you're going to SBF you can SBF directly from your current version to the desired version.
germmeetsworld said:
I also was wondering if my phone would still be rooted after the SBF because of the maintain-root-through-any-update mod. Any thoughts?
Click to expand...
Click to collapse
To be honest, I'm not sure. I personally prefer to SBF to a clean DX2, wiping all settings and cache. To me I treat it like formatting my computer with a clean install of it's OS.
Perhaps someone else will have more insight with the maintain root through updates mod.
germmeetsworld said:
On a different note, if I had the x2 bootstrap, the maintain-root-through-any-update mod, and MyBackup Root, could I just backup all my apps and the system (using MyBackup Root and the bootstrap, respectively), SBF, then restore the phone by downloading the bootstrap and MyBackup Root and restoring my apps/system? Would this get my back to where I was before, or would I have to manually download each one of my apps and lose all previous data that I had on them? I'm just wondering what's the easiest way to restore my phone back to the layout that I had before I SBFed.
Thanks for your answers to any of these 3 questions!!! I definitely appreciate it.
Click to expand...
Click to collapse
What I typically do is using the X2 Bootstrap, I make a Nandroid backup and restore directly from that. Performing an SBF is only going to be necessary if the backup was on a different kernel, otherwise if you may run into boot looping.
What exactly happened and what are you trying to do? Are you trying to restore your phone to an earlier point via SBF? As in you enjoyed the phone on 2.3.3, made a backup and now you're unhappy on 2.3.4 and wish to go back?
It sounds like if you were to SBF back to your desired version (the version you made the backups on) you would then be able to apply your backups and should be back to your desired phone state.
I'm slightly confused to the details due to the way it's worded. I know it's somewhat difficult to describe but that's the basic idea I'm getting. Please feel free to correct me if I'm wrong or fill in the blanks.
Is 2.3.5 much better?
Sent from my DROID X2 using XDA App
Okay so what I did was SBF back to 2.3.3 (I did this two nights ago) and before I did that, I:
1. Renamed the bloatware back to .apk (I had the suffix's ".bak" as an alternate "freezing" method).
2. Used MyBackup Root to make a backup of all my apps+their data.
3. Made a backup of the phone using the bootstrap.
4. SBFed
5. Rooted
6. Downloaded MyBackup Root
7. Restored all my apps and data and it worked!!!
8. Celebrated! I had no faith in it working but all my apps are back! I was so impressed, I was expecting to have to redo all my games and everything. MyBackup Root is such a sweet app, or I'm just a loser.
I hoped this helped other people, I had no idea what was gonna happen, no one's ever told me how to specifically get my phone back to the layout that I wanted.
and related to reaktor's post, what I was doing was SBFing back to my desired state of 2.3.3, just because I hate the battery glitch on 2.3.4. It had nothing to do with any apps I had, sorry for the confusion.
Your last reply was a little off but that was my fault, I'm sorry for my wording haha. I just have never known how to NOT have to redownload all my apps and start over on my games' data once I restore/SBF a phone. Now I know.
BTW my phone didn't maintain its root, just for reference for others. I had to reroot.
Well... You might want to do that again. There's now a battery fix for 2.3.4 and 2.3.5 in the dev forum.
Pepperm1nt's battery fix thread @ http://forum.xda-developers.com/showthread.php?t=1350336
It works great
Greatttttt haha all that fer nuthin. I may update again, or I just might wait til I get bored with the phone again to install this. Thanks a bunch for the link though!
Sent from my DROID X2 using XDA Premium App
The battery fix works great. Just flash it over stock or any custom rom. It works perfect!
So I am trying to install the Stock Deodexed ROM and i've wiped and all but when I got to install the zip, it aborts. It says failure at line 7. I have backups of Stock 2.3.4 i can restore to, so I can get to my goal of being at 2.3.5 for the Eclipse update tonight, but I'd rather a clean install. Why is the install aborting?
UbuntuBrandon said:
So I am trying to install the Stock Deodexed ROM and i've wiped and all but when I got to install the zip, it aborts. It says failure at line 7. I have backups of Stock 2.3.4 i can restore to, so I can get to my goal of being at 2.3.5 for the Eclipse update tonight, but I'd rather a clean install. Why is the install aborting?
Click to expand...
Click to collapse
This has happen to me before. I had to sbf and then it was fine for a while. But recently I had the same iussue again but I had already made a back up of eclipse 1.3 so I am also hoping eclipse 2.0 goes ok for me as well.
Finishing up a restore of my stock, then to update. The only reason I am is because i installed the mash up rom and my signal was amazing for a day, and then today, it has picked up miniscule 3g, dropped it, and remained on low 1x.
Flashing the deodexed rom is unnecessary, all you have to do is sbf to 2.3.4, root, use rootkeeper (if you want), update, and flash eclipse when released.
Sent from my DROID X2 using xda premium
Nitro suggested I update to 2.3.5 before I go about installing the Eclipse 2.0 update this evening. Well whenever I try and flash a zip from SD card, it aborts and gives an error. It happens with the Update, and installing ROMS. I fear that I won't be able to update to 2.0 this evening because of this error. Any ideas to fix it?
Try and sbf and get a clean start. If you heave not done that then do that first. Which update did you use? .412 or. 413
Which recovery are you flashing the update from? I flash it from my external. See if that makes a difference. And as said you have to be bone stock 2.3.4 for the update to work
Sent from my DROID X2 using xda premium
CadenH said:
Which recovery are you flashing the update from? I flash it from my external. See if that makes a difference. And as said you have to be bone stock 2.3.4 for the update to work
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Updated with android recovery. The last time I tried to flash molten it aborted but I did not care since I already had backup of eclipse 1.3 I just updated to 2.3.5 with android recovery and restored root with rootkeeper app.
The best I have done is sbf the leak then flash the 213 ota from folder "1 235" in my fake mp3 http://www.mediafire.com/file/4loqisamcd4y8ya/1_to_4_235isAzip.mp3 just change it to .zip.
Ah this sucks. I flashed eclipse 2.0 and it aborted line 294 permission error crap again. So I sbf back to 2.3.4 and re rooted. Re did the update and then tried again. Same error. Man I dont understand it will flash everything else except on the roms. When I went to 2.3.5 I flashed the drop down toggles and battery fix. This only happens when I flash roms. I have work tomorrow so i guess I will sbf one more time and re root so I can get back to my back up of eclipse 1.3 and mess with this again on my next day off on Sunday. Maybe I will try to go back to 2.3.3 and do OTA updates? I am at a lost and have not heard of any fixes for this out there yet!!!
Still having the same problem here, too. I just sbf'ed to 2.2.2 instead of 2.3.4 and took all OTA's. Did a NAND on 2.3.4. Getting ready to update to 2.3.5 via stock recovery.
Well that was a fail, too. Currently on stock 2.3.5 rooted. Guess I'm not sure what to do now. I still have my nand of Eclipse 1.3 but would have to sbf back to 2.3.4 again and go through it all just to restore it. This sucks!
Just got 2.0.1 Eclipse running this morning no issues.
UbuntuBrandon said:
Just got 2.0.1 Eclipse running this morning no issues.
Click to expand...
Click to collapse
What did you do it get it to work? Did it fail last night for you also or was this your first time trying?
Well I SBF'd and factory reset from stock recovery. Then I updated to 2.3.5 from stock recovery. Then I rooted with ZergRush, and then I flashed 2.0.1 Eclipse with x2 Bootstrap.
There have been issues with Root Keeper. So if any of you are using that, dont. Follow these instructions and use these files:
http://forum.xda-developers.com/showthread.php?t=1391824
I finally got it working, too. Root keeper is the issue. Now on 2.0.1. Will be on 2.0.2 later tonight!
Sent from my DROID X2 on Eclipse 2.0.1.
Agreed. 2.0.2 will be on mine too. I vote, though, that these minor updates chill xD