I rooted my sister in laws Bionic months ago and have not touched since. I want to restore to stock so she can take the ICS update. I current has gingerbread and the update fails. It has safestrap 1.7, and its been so long since I touched this, I can't remember how to do anything. Can someone please help me get this back to stock.
Either use SamuriHL's HoB to apply the update / revert to stock and apply the update, or else use the ICS FXZ to do it all at one time. Since there are a lot of changes going to ICS, I'd recommend that you backup apps, SMS, etc. using Titanium Backup and then use the 6.7.246 FXZ through RSD Lite and start from pure scratch.
Related
Hey guys -
I'm a recent convert to Milestone (owned horrible WM devices over the years before just recently switching to Android). Love this community and hope it continues to grow!
A couple of quick questions:
1.) I have a rooted Telus Milestone but want to apply the latest Telus update (I believe it was released Aug. 10th). Now, I've tried doing this OTA but no luck because I'm rooted apparently (I believe I can sill do it via cable)... but if I CAN do this successfully, will I lose root?
2.) If I can't apply the update without un-rooting my phone first, I suppose that this would be my process. Can you tell me if this will work?
1. Make a nandroid backup
2. Un-root the phone
3. Apply the firmware update
4. Root the phone
5. Restore my nandroid backup.
... BUT here's my fear: I'll be restoring my nandroid backup overtop of a different OS / build... and isn't that a recipe for disaster? (I could never do this with WM devices, anyway).
Can anyone tell me if this process will work? Having a hard time finding answers here.
Really appreciate it. Thanks!
-Trevor : )
Trevor_g said:
Hey guys -
I'm a recent convert to Milestone (owned horrible WM devices over the years before just recently switching to Android). Love this community and hope it continues to grow!
A couple of quick questions:
1.) I have a rooted Telus Milestone but want to apply the latest Telus update (I believe it was released Aug. 10th). Now, I've tried doing this OTA but no luck because I'm rooted apparently (I believe I can sill do it via cable)... but if I CAN do this successfully, will I lose root?
2.) If I can't apply the update without un-rooting my phone first, I suppose that this would be my process. Can you tell me if this will work?
1. Make a nandroid backup
2. Un-root the phone
3. Apply the firmware update
4. Root the phone
5. Restore my nandroid backup.
... BUT here's my fear: I'll be restoring my nandroid backup overtop of a different OS / build... and isn't that a recipe for disaster? (I could never do this with WM devices, anyway).
Can anyone tell me if this process will work? Having a hard time finding answers here.
Really appreciate it. Thanks!
-Trevor : )
Click to expand...
Click to collapse
When you restore the nandroid backup you'll be back where you were before on the old version of 2.1.
You can get the update by flashing the newest Telus service SBF from here:
http://and-developers.com/sbf:milestone
(scroll way down to the end)
If you need to then root again you'll want to reflash the vulnerable recovery SBF from:
http://android.doshaska.net/rootable
and then apply any of the various update.zip methods for root.
Also you could go for the G.O.T. leaked version of the exact same firmware update:
http://groupoften.wordpress.com/2010/07/07/update-for-france-and-telus-released/
which skips the need to reflash the vulnerable recovery SBF. Then proceed again with a root update.zip.
I might also recommend taking a full Titanium backup before the upgrade in addition to nandroid. If any of the root mods you've made are incompatible with flashing the update via SBF, it'll give you another way to restore your data on the new OS update.
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
I think I bricked my Bionic and need help :crying:
I was running 905 perfcectly and wanted to upgrade to ICS 230 leak so I did a nandroid with bootstrap.
I followed instructions and everything went perfectly, I had my ICS running very good (with full root and all) but I wanted to go back, since I wasm't productive enough with the new layouts and stuff so I installed Bootstrap and retored my old nandroid backup... BIG MISTAKE. The restore went ok, but when rebooting it stuck in a blank screen (for 30 minutes) until I decided to reboot it. and same thing. From there I can't go ahead. I've tried to glash back to 905 and even ICS (from stock recovery) with the Status 7 error, I started in fastboot and tryied RSDLite to go to stock 902 and failed (Failed flashing process. 1/22 flash mbm "allow-mbmloader-flashing-mbm.bin" Phone returned FAILED) and nothing seems to work.
Any helps or ideas are welcomed, I think I might have bricked it bad.....
Trying to restore a Gingerbread nandroid over ICS leak is a bad idea.
Did you get your phone fixed?
If not, PM me and I will get you back on track...I hope.
eye__dea said:
Trying to restore a Gingerbread nandroid over ICS leak is a bad idea.
Did you get your phone fixed?
If not, PM me and I will get you back on track...I hope.
Click to expand...
Click to collapse
I know.. newbie mistake!!!
I did something like that my self. I have been flashing stuff since the original droid. I messed up and didnt do a backup in recovery. I ended up flashing back to stock .902 using rsd and doing the whole process again. Good luck hopefully you have it fixed by now.
Try RSDlite again with a fully-charged battery, low battery level has been the major cause of flash failures on the Bionic
Note that you won't be able to charge with a bricked Bionic, you either need a wall charger, ask someone to do it for you, or buy another battery from Verizon.
I'd say get to 100% with a wall charger, then FXZ to 902, then apply the 905 update (via OTA or from SD in stock recovery, root, backup with OTA root keeper, then apply the newest leak (232). You should have a fully working phone, but if you wanna go back to the gingerbread stuff, DO NOT flash the leak. Whatever ROMs you use must be made for whatever stock OS version you have. If it's made for 902 or 905 it won't work after you've updated to ICS. If the ROM is made for 2233 or 230 or 232 and so on, it won't work until you've updated the stock OS to one of those builds, or just an ICS build in general (most likely).
You can go back to 902 from any of the leaks.
Sent from my DROID BIONIC using Tapatalk 2. Running 232 currently.
I have had only one time bricking my bionic.
I was on a cross country flight and ran my battery down to not be able to flash. I was also unable to charge my phone because I had just deleted everything from stock recovery (my first problem). RSD would not work because I had no charge on my phone, and Nothing I did would charge my phone. I know nobody else that owns a bionic so they could charge my battery.
I went to Verizon and explained some bull**** story of my phone just not turning on and they were willing to send me a refurbished phone. I asked if it was at all possible for them to trade me batteries for my Bionic. He allowed me to trade batteries from the store model and came home flashed .902 with RSD Lite and have had no problems since.
Yesterday i flashed if i remember the 223 leak. I flashed from 905, rooted with razor ics root. I went in to sqlite and changed the setting to get the free hotspot and than rebooted. Now on my top banner the wifi icon and my signal icon stay gray! They never got to blue! I have data service but the are always gray. Also later my signal strength went noticeably lower than before i flashed! Any help would be great! ...... also i just noticed that my browser is talking! Had chrome installed, couldn't find anything in the settings so i uninstalled and went to reinstall. Play store says that NOW its not compatible with my device! And now my stock browser is talking to me! PLEASE HELP!!!!!!
Sent from my DROID BIONIC using xda app-developers app
One thing at a tine.
Browser talking - check you're accessibility settings, see if Talkback is enabled.
For the GNow, that does not come with the ICS leaks. Either you installed an unofficial leak, or you installed GNow before the leak, or you installed it after the leak. There is a thread in XDA that details how to get GNow working in ICS.
For the sqlite mod, change the string back. Foxfi is free, doesn't require root, and works.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Thanks, I FXZed back and reloaded everything no sqlite no root and everything seems good! Still lost data for a while last night but l don't have great service at home! Might root later today, we'll see!
Sent from my DROID BIONIC using xda app-developers app
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
bhp117 said:
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
Click to expand...
Click to collapse
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
What? We have a locked boot loader... can't run .235 on one side and .905 on the other lol
What he said was correct.. you cannot use RSD lite to fxz back to .902/.905 with .235 so unless you're a fool don't make the move... 232 is great
Finally Iced Out Legitimately... Bionic is back
You cannot go back to fully stock Gingerbread anything once you flash .235 so for the sake of newer users being thrown off the upgrade path and not being able to FXZ back to .905 we all should just leave it at that.
cnorman76 said:
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
I think you've gotten the gist of the info, but I'll reiterate.
You have to be on .905 to flash any of the current ICS leaks (and there is a 99% chance of that being true with any future leaks / soak tests / final OTA b/c .905 is the current official OS version for the BIONIC.
You can flash .235 off of .905, but once you are in .235, you cannot restore your phone to .905 via FXZ, and you cannot try to fool the system with a simple Nandroid backup of .905 that you restore over .235. The reason is that the update script also looks to patch several things.
First of all, no update script ever includes the boot.img of the version that is being installed. It includes a patch file that requires you to have either the boot.img of the system that you are coming from, or the system that you are going to. Any other version and it throws up an error and does not allow the update to continue. IOW, if, say, leak .241 comes out, and you're on .235, you have no way to getting .241 without using a method to make the .241 kernel. You cannot flash the .905 kernel onto a .235 system - it trips eFuse and bricks the phone. You have no .241 kernel to install b/c, as I said, the update only includes a patch file, not the full kernel.
Second, even provide that you pass that (which in theory you might as you are on a .235 leak with only .905 /system restored from a Nandroid backup, and if the new leak uses the exact same kernel you'll pass), it also verifies every file in /system that it is going to patch, along with every file in /preinstall that you are going to patch. Restoring that Nandroid backup does wonders for having the .905 /system on your phone, but the current leak you are on has already patched several files in /preinstall, so those signatures will not match, and you'll fail the verification step, and ultimately the update will fail.
For the record, a typical FXZ flashes 17 different partitions on our phones. Nandroid backups on the BIONIC typically can only make backups of 3-4 of those partitions. We have figured out ways to grab a few more of them, but we are still stuck at grabbing a couple of them, and there are 4-5 that we cannot grab from our phones at all.
Since the folks with RAZRs went through something very similar in May and June, mattlgroff figured out a way to fool the update into thinking you have all the components correct in place that need to be there, and the update proceeds. Thus far, after bricking my phone trying to FXZ back to .905 / .902, I used a script to get back on .235, then verified that the move to reinstall the .235 leak works. If another leak is found, then I can test the second part of the script, that which allows new leaks to be installed. The script does not allow any older ICS leak to be installed, and currently there is no way to go back to a previous leak nor a previous GB stock FXZ at all. Even if we had a .223X ICS FXZ or a .22X ICS FXZ or a .230/.232 FXZ, they would not work on a phone that has been updated to .235.
That is why we're saying hold off unless you're 100% positive you're willing to accept the risk - this is way beyond the risk associated with rooting your phone. If Motorola makes the next leak force the phone to have components from .905 that we cannot flash into a .235 upgraded phone, I (and several others that have taken the plunge) might be permanently stuck on .235 until an FXZ for a version of ICS higher than or equal to .235 is released. And that typically takes 6-8 weeks.
HTH
crobs808 said:
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
Click to expand...
Click to collapse
Make a guide if you will and state the proper steps to do so
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
dblkspecial said:
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i noticed that the other day when I got a text while my screen was locked. I naturally pulled the notification bar down and noticed that I didn't unlock my phone at first. Tried it just now and it's unlocking without swiping to unlock. My home button doesn't do anything howerver.
I recently rooted my bionic, then, thanks to crobbs, flashed ics .232 onto it. during this whole process i safe-strapped a recovery to my sd-ext. i then heard that ics should come out no latter than Sept. 30th.(if Motorola and Verizon come through) so i decided id go back to the stock version so i could get the ota update whenever it came out. i went back to stock using the fxz tools and im back to .905 GB stock un rooted. (or so i hope, not to sure how to tell if im on the ota)
***My main question.....since i still have my very first original safestrap recovery saved....if i was to root right now and use that original safestrap recovery, would i get everything i had from my old phone back just the way i had it when i first safe-strapped?