So I rooted, using one click method, backed up stock .886 and installed blurry 2.0, based on .893. I know now that the kernal and radios are changed from .886. Does this render my stock back up of .886 useless? Also, what if the OTA update coming in November is actually different than .893, will I be able to update to what ever that may be?
stevessvt said:
So I rooted, backed up stock .886 and installed blurry 2.0, based on .893. I know now that the kernal and radios are changed from .886. Does this render my stock back up of .886 useless? Also, what if the OTA update coming in November is actually different than .893, will I be able to what ever that may be?
Click to expand...
Click to collapse
I would take an educated guess and say yes your 886 backups are trash, but don't take my word on that.
If you made those backups through ROM Manager, you're in luck.
https://market.android.com/details?...wxLDEsImNvbS5oYW5keWFuZHkuYXBwZXh0cmFjdG9yIl0
That app can extract apps, contacts, and SMS/MMS from Nandroid backups done through ROM Manager.
Tivo7 said:
I would take an educated guess and say yes your 886 backups are trash, but don't take my word on that.
If you made those backups through ROM Manager, you're in luck.
https://market.android.com/details?...wxLDEsImNvbS5oYW5keWFuZHkuYXBwZXh0cmFjdG9yIl0
That app can extract apps, contacts, and SMS/MMS from Nandroid backups done through ROM Manager.
Click to expand...
Click to collapse
Im loving blurry just fine and see no reason to go back, but I just hope I didnt cut off my nose to spite my face in regards to future updates.
So I did a data reset in bootstrap, and reinstalled my stock .886 back up, and it installed fine. Rebooted and everything worked as it should.
stevessvt said:
So I did a data reset in bootstrap, and reinstalled my stock .886 back up, and it installed fine. Rebooted and everything worked as it should.
Click to expand...
Click to collapse
Awesome.
10char
If you just install 2.0 over stock, you do not get the .893 radio or kernal. You only get the system. To get the radio and kernal you need to to go back to stock, do the permanent root method, install the cheesecake app, then update to .893 through cheesecake, and then flash 2.0. If at that point you flash .886 again, you would have the .893 radio and kernal, and the .886 system. Because the bootloader is locked, you cannot flash a new kernal or radio via cwm.
Sooooo by flashing blurr3y 2.0 in cwm I never got .893 radio/kernel?
stevessvt said:
Sooooo by flashing blurr3y 2.0 in cwm I never got .893 radio/kernel?
Click to expand...
Click to collapse
Correct.
Sent from my DROID BIONIC using xda premium
lawtalking said:
If you just install 2.0 over stock, you do not get the .893 radio or kernal. You only get the system. To get the radio and kernal you need to to go back to stock, do the permanent root method, install the cheesecake app, then update to .893 through cheesecake, and then flash 2.0. If at that point you flash .886 again, you would have the .893 radio and kernal, and the .886 system. Because the bootloader is locked, you cannot flash a new kernal or radio via cwm.
Click to expand...
Click to collapse
Following this will do the trick.
http://forum.xda-developers.com/showthread.php?t=1320414
Tivo7 said:
Following this will do the trick.
http://forum.xda-developers.com/showthread.php?t=1320414
Click to expand...
Click to collapse
Thanks for putting that guide up Tivo. I figure when the next update comes out, you might have to be back with the .886 and I was wondering whether there was a way to downgrade the radio and kernal to stock after going to .893.
lawtalking said:
Thanks for putting that guide up Tivo. I figure when the next update comes out, you might have to be back with the .886 and I was wondering whether there was a way to downgrade the radio and kernal to stock after going to .893.
Click to expand...
Click to collapse
The next update IS 893, I've already gotten confirmation of that.
Rootable?
Tivo, will the new bionics being shipped with .893 be rootable? Will they need to be rolled back per the method you detailed here ?
anarchy4sale said:
Tivo, will the new bionics being shipped with .893 be rootable? Will they need to be rolled back per the method you detailed here ?
Click to expand...
Click to collapse
We will have to wait and see what root methods work after the ota is released. Painfully to wait, I know.
Sent from my DROID BIONIC using xda premium
It will revert you back to system 886, but your kernel/radio will stay with whatever update you installed. I currently have a hybrid going on. 5.5.893 system and 5.6.893 kernel.
Sent from my DROID BIONIC using xda premium
Related
tried to restore stock with one click and it wont flash the boot.img . Said something like INFOPreinstallaton error. Cant root either. What to do?
Well, first off, your question is in the wrong thread...it will most likely be moved soon...
second....did you update to .893?
Edit: if so and your bootlooped.... this is the one you want http://rootzwiki.com/topic/7801-roo...v10-linuxwindows-get-root-after-893-ota-oops/
ill move my questions. Sorry! Yes and no. Did forever root, flashed update, flashed liberty rom. Then i noticed the version was back to 886 so i tried the oneclick instead of backup and thats when the error for boot.img showed but everything else flashed. My phone is running but i cant root it shows an error as well. thanks for the reply.
antonioj78 said:
ill move my questions. Sorry! Yes and no. Did forever root, flashed update, flashed liberty rom. Then i noticed the version was back to 886 so i tried the oneclick instead of backup and thats when the error for boot.img showed but everything else flashed. My phone is running but i cant root it shows an error as well. thanks for the reply.
Click to expand...
Click to collapse
when you flashed liberty, you flashed .886 system, but the .893 kernel and radio remained. not sure which one click you used to lose root, are you sure you lost root? if, so.... this is just my opinion and what i would do....I would run th3orys and dhackers fix above and flash 2.1 when it comes out.
i will try that. Thanks for the info.
I tried updating from the leaked 5.5.893 to this new 5.9.901 with no luck. Has anyone have any luck with this? If so how did you do it?
Throw it on the sd card, use stock recovery. What method did you use and what error are you getting?
I put it on the sd card. Tried from stock recovery and its failing at the verification. Tried to install as a zip.
Then I don't believe you're on 5.5.893. You're SURE you're not on 5.7.893? Cause if you're on 5.7.893 then you're stuck like the rest of us.
If you are on the leaked 5.5.893 and not the official OTA version, then it is possible that the checksums are different between the two versions and it fails the asserts in the updater-script.
The important thing to note is that the error messages are very specific and will tell you which file is failing. Then you can fix it, if at all possible, dependent on what was changed and how.
cellzealot said:
If you are on the leaked 5.5.893 and not the official OTA version, then it is possible that the checksums are different between the two versions and it fails the asserts in the updater-script.
The important thing to note is that the error messages are very specific and will tell you which file is failing. Then you can fix it, if at all possible, dependent on what was changed and how.
Click to expand...
Click to collapse
I thought someone checked the CRC's for the leaked vs OTA and they were identical?
Not sure if anyone has seen or tried this yet, but the error I get (running 5.7.893) regards two attributes in the build.prop file. Gonna try modding them to see if the update takes afterwards.
GeoMandell said:
Not sure if anyone has seen or tried this yet, but the error I get (running 5.7.893) regards two attributes in the build.prop file. Gonna try modding them to see if the update takes afterwards.
Click to expand...
Click to collapse
Don't bother. I spent a lot of time on this last night. I went so far as to put 5.5.893 *system* on and tried to flash from that. (Obviously with boot image from 5.7.893 still). It got past the build.prop error and gave me a boot error. Meaning it fails asserting the boot image. No chance for this update to work for us I'm afraid.
I am on the leaked 5.5.893. I'm on the liberty rom. Would I have to put my phone all the way back to stock? Then start from there? At one time I had restored my phoned and did the 43v3r root and my system version went from the 5.5.893 to 5.5.886. Is that my culprit right there? Even though my radio and kernel is still from 5.5.893?
djr4x4 said:
I am on the leaked 5.5.893. I'm on the liberty rom. Would I have to put my phone all the way back to stock? Then start from there? At one time I had restored my phoned and did the 43v3r root and my system version went from the 5.5.893 to 5.5.886. Is that my culprit right there? Even though my radio and kernel is still from 5.5.893?
Click to expand...
Click to collapse
Woa woa woa. Slow down. You're trying to apply this over a custom rom? Is that what you're saying? That definitely won't work. It has to be stock system for the version that the update is made for. So, in this case, you need stock 5.5.893. The kernel and radio are fine as a custom rom can't touch those. But you will need to restore stock 5.5.893 if you want to apply the update to get the new kernel and radio. Then you can put your rom back on. Hope that helps!
Do I need to reflash the original bionic stock ROM with RSD lite, then flash the leaked 5.5.893 and then flash to 5.9.901?
If you made a nandroid backup of your clean 5.5.893 installation then restoring that would be the easiest method to get the 5.5.901 to install properly.
If you have changed anything at all in your system beyond simply rooting and mount-ext3.sh for permanent root, then the update will fail.
No don't do that. For sure don't do that as it will not work. You didn't make a backup of the stock rom when you did the 5.5.893 update before putting a custom rom on?? UGH. If that's the case and you don't have a nandroid backup of 5.5.893 then this is going to be a pain. Not impossible but will cause you some headaches. First thing's first. Go make a nandroid backup of your existing rom install. I'll see if I can put some steps together that'll get you upgraded.
---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------
cellzealot said:
If you made a nandroid backup of your clean 5.5.893 installation then restoring that would be the easiest method to get the 5.5.901 to install properly.
If you have changed anything at all in your system beyond simply rooting and mount-ext3.sh for permanent root, then the update will fail.
Click to expand...
Click to collapse
But not with RSD using the FXZ now that he's on 5.5.893, yea? That'd be...bad.
---------- Post added at 03:45 PM ---------- Previous post was at 03:38 PM ----------
1) http://rootzwiki.com/topic/5484-r3l...he-bionic-v21/page__view__findpost__p__127684
Get that, unzip it, run it, and choose option 1. That will put you back on 5.5.886 stock *system* but will not touch anything else. And will of course, will install permanent root.
2) http://www.multiupload.com/0ZEN69NGO2
Get that, throw it on the SD card, and boot to stock recovery. Flash it.
3) Now you are ready to try flashing 5.9.901 again
4) NANDROID THAT THING
Then restore your custom rom and you should be good to go. CZ, did I miss anything?
I've lost my nandroids backup. . I have made a new nandroid backup of this current setup incase I screw something up.. I am unable to restore back to fully stock at this time which I'm rather upset about.. Am I screwed?
djr4x4 said:
I've lost my nandroids backup. . I have made a new nandroid backup of this current setup incase I screw something up.. I am unable to restore back to fully stock at this time which I'm rather upset about.. Am I screwed?
Click to expand...
Click to collapse
Make sure you have a nandroid of your current (custom, apparently) rom. Then do the steps I outlined above.
Just to reiterate, this will not work for those of us on 5.7.893, correct?
GeoMandell said:
Just to reiterate, this will not work for those of us on 5.7.893, correct?
Click to expand...
Click to collapse
No it will not. Nothing will at this point in time.
awesome. It worked. I am now 5.9.901!!!! Thanks for the help... And I kept root!!!
Grumble grumble lucky jerk... J/K I'm sincerely glad that worked for you. *NANDROID*.
WHAT?!!
I am on 5.7.893
You guys mean to tell me that even if I nandroid back, to my clean back-up of 5.5.893... This 901 update will still fail??!!
Is it checking the kernel also? I have a nandroid that is completely stock so if I flash back to that this 901 update should go unless it checks the kernel version too.
After getting back on the update path and updating to 5.9.901 I found someone tweaked eclipse to be compatible with it. I just noticed that my system version is back to 5.7.893, is this just because eclipse is actually 893 based? Or did something go wrong and it should say 901?
Sent from my DROID BIONIC using XDA App
Eclipse is based off of 5.7.893. That is all. You still have the 901 radio's etc. When a new OTA comes out, you will need to go back to stock ROM that shows 901 etc to get it.
Thanks, that's what I assumed. I'm guessing the 5.5.893 update wouldn't be able to get me back to the stock OTA, right? I stupidly forgot to make a backup to get back to it for updates.
I'm guessing just do what you originally did to beable to get back on the OTA update path. I'm not sure about that.. I have 5.5.893.
What are the risks involved? I might want to upgrade to Eclipse 3.0, but am concerned about how the unsafe update migbt affect future Verizon OTAs processing.
With the quick avaible way to FXZ your way back to the 902 stock path I would think it would be worth a shot. Check out the link posted below. Currently I think Verzion wouldn't be applying anything soon so there is a great chance to run the leak 905 while you wait for a official update. Had to use this FXZ process just yesturday due to some radio issues with any rom I had on my Bionic. Currently still only Stock and rock solid. Good Luck and let me know how it goes I might jump to the 3.0 update to as long as the Market will fully update to the new Play Store.
http://www.droidhive.com/forums/index.php?/topic/87-902-bionic-pathsaver-for-windowslinuxmac/
ronaldheld said:
What are the risks involved? I might want to upgrade to Eclipse 3.0, but am concerned about how the unsafe update migbt affect future Verizon OTAs processing.
Click to expand...
Click to collapse
At this point, I'd say the risks are pretty much none
another problem is the only ROMs on .905 is Eclipse, so upgrading to that eliminates trying ICS ROMs.
Anyone know when the .905 OTA will start?
ronaldheld said:
another problem is the only ROMs on .905 is Eclipse, so upgrading to that eliminates trying ICS ROMs.
Anyone know when the .905 OTA will start?
Click to expand...
Click to collapse
It has started already.
I just went to Verizon Support and could not find the 905 update...If I go back to stock, will I get an OTA update??
Will this update brick my rooted phone which currently has version 902 on it?
Is it possible to upgrade from 904? Flashing the zip through stock recovery hasn't worked for me. Keep getting an error message.
Sent from my DROID BIONIC using Tapatalk 2
lhkjohn said:
Is it possible to upgrade from 904? Flashing the zip through stock recovery hasn't worked for me. Keep getting an error message.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
It's not possible to go from .904 to .905. The update.zip for .905 looks for system files from .902 before doing anything. It's supposed to fail for you until you FXZ back to .902
lpfas29 said:
Will this update brick my rooted phone which currently has version 902 on it?
Click to expand...
Click to collapse
It shouldn't brick, but you may lose root. Also if you've frozen and/or removed bloatware the update will fail.
ronaldheld said:
another problem is the only ROMs on .905 is Eclipse, so upgrading to that eliminates trying ICS ROMs.
Anyone know when the .905 OTA will start?
Click to expand...
Click to collapse
I was surprised at how well ICS ROMs played with my phone when I was on .904. It may be worth it to try on .905 too. Even then, the devs will probably make updates soon to accommodate the new kernel in .905.
rosystreasures said:
I just went to Verizon Support and could not find the 905 update...If I go back to stock, will I get an OTA update??
Click to expand...
Click to collapse
OTA updates are made for stock phones. The .905 update only updates phones that are running completely stock .902 phones. The OTA updates fail on anything that is not stock. OTA updates are built to expect a certain existing revision of the software. If that is not present, the update will fail. You must revert to stock 5.9.902 if you want .905 to install.
I, too, am getting an error msg about the xml not being correct, or I am missing certain image files. I haven't removed any of the bloatware.
I had 902. Rooted and ROM'd with Eclipse 2.2. Installed CoreDroid_Eclipse_2.2. Curious, will Core Droid not work with Eclipse 3.0?? (IF I ever get the 902 stock again...)
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.