Ok, so heres the deal. Was on stock rooted 886 w/o permaroot, and my dumbass did the OTA 893 update. Lost root, so I used R3l3AS3DRoot and did a Restore, Root, & For3v3r root. This brought my system back to 886, but from what I've gathered, my kernel and radio are still 893? My issue is, now I cant update at all, to 893 or 901 (basically what I want to do is run Eclipse V2.0 .901 Patched thats posted Here. I've tried this and the update still fails. I've also tried updating straight to 901 due to the fact that my kernel and radio are supposedly still 893 since I did that stupid ass OTA update. Am I screwed, or is there something else I can do?
BTW, I did get the Eclipse V2.0 901 Patched to install on my safe boot partition with bootstrap recovery, but I had absolutely NO DATA. I even tried moving the 901's system/lib files and still nata. I'm assuming this is due to the fact that the kernel and radio are still 893?
try the pathsaver method by p3droid. first go your sd-ext and remove any updates that are their or it will not push the ones you need. there is a vid out there somewhere on how to but it is pretty easy just read all instructions
Related
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
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.
I may be a noob but what exactly is the point of this. I keep both update.zip's on my sd card(893,901). I just tried this. Im on stock 5.5.886 rooted. booted in stock recovery and applied both updates. Now im on .901 and still rooted. I didnt get the cdt.bin error or anything. What is BIONICPATHSAVER supposed to do?
From my understanding, its an extra string of security that keeps root open. I did the same thing and it worked. But my first attempt wasnt soo lucky. I ended up bricking my bionic. No worries though, i used my motorola limited warranty. Now i just have my verizon warranty left
Sent from my DROID BIONIC using xda premium
The point of this tool is to save your ass.
it can be and should be used to go from a pre 901 rom to a 901 rom as well as helping you unbrick your phone.
I needed it to go from liberty 2.0 to eclipse 2.1
Primarily its for people who got off the update path via cheesecake updates. It returns you to the upgrade path so that you can once again receive the OTA updates. Atleast thats my understand of it.
you will need it if you ever want to go back down to 5.5.893.
It was created for people that loaded 5.7.893 or 5.5.894 that were off the update path. If they release ICS for 5.5.893 and not for 5.5.901 at the same time, you may want to go back to get ICS.
Ok I have no idea why or what I did but I can't add a new contact, my contact storage force closes. I have not deleted any of my files that I know of and all bloat is unfrozen. Everything else works calls and changing exisitng contacts I just can't add any new contacts. So I am on .901 with 4everroot and want to reinstall the full system to see if I can fix my contacts. Since the pathsaver came out I am unsure what to use. I guess I want to go back to the full 893 then 4everroot again. Do I need to FXB to 893 then apply the forever root and update to 901. If so can you guys attach links to what I need much appreciated.
I think you could FXZ back to stock... But I am unsure.
Pathsaver should work though.
How to use pathsaver http://www.youtube.com/watch?v=ufnDSFi4glo
I don't think you can use pathsaver from 901 but my other question? does the pathsaver give you the whole file like FXZ does. I need to find out what I did to screw up creating new contacts so I figure a whole new system download will fix it. I am downloading the 856 FXZ now and going to rsd it back to stock forever root and then take the 893 update then push the 901. Does this make sense or am I complicating things.
I used the path saver to go back down and up again. Make sure you have the .886 radio file on your SD card, you'll need it. Also, you'll need the cdt.bin file (.901fix) at the bottom of the path saver link.
Have you just tried to reflash the .901? Oh, it probably won't work since it verifies the .893 system.
Thanks for the responses I figured it out and got back to 901 rooted but wasted 4 hours getting my phone set up again. But I can add contacts now so all is good. I FXZ to 893 and just put the cdt.bin from 901 in the 893 file and rezipped it Rsd lite had no problem loading it and then I manually forever rooted and downloaded the 901 file and manually installed it and kept root. Damn I wish they would unlock the friggin bootloader so we don't have to waste so much time and jump through all these hoops.
Many non Noobies seem to be running across the same problems with rooting ZV8 updates. The answers are spread across three different threads so it seemed worth putting them all in one place up front.
First, big thanks MT for putting all this up so quickly.
If you are still on ZV7, first try
http://forum.xda-developers.com/showthread.php?t=1566729
However, I and many others have not been able to get an over the air update (step 6) to succeed and/or get a lot of permission denied errors in the All in One batch processes. If you can't get an OTA update to succeed first try
Originally Posted by drt054
use a terminal emulator, type in
su <enter>
echo 'ro.kernel.qemu=1' > /data/local.prop <enter>.
OR
Use root explorer to create /data/local.prop and type ro.kernel.qemu=1 then save it.
If the OTA update works, you're good, continue with MT's instructions, but SKIP OPTION 1 "Prepare for Update"
If, like me and many others you still can't get an OTA update to succeed Alternative 2 is the LGPST method here
http://forum.xda-developers.com/showthread.php?t=1466655
Again, the key is to not loose Clockwork Recovery. As long as you have done the create local.prop step and not done the All in One Option 1 "Prepare for Update" The LGPST ZV8 push will not erase Clockwork Recovery. Then you have ZV8 with Clockwork Recovery and you can get MT"s Broken Out v 1.1 here
http://forum.xda-developers.com/showthread.php?t=1577423
Or get back to a nandroid backup or rooted ZV7 to start over
http://forum.xda-developers.com/showthread.php?t=1348637
If you loose Clockwork Recovery or otherwise run into trouble, the sure fire way to get back on track is to go back to ZV7 and start over. Personally, reading through all the forums and despite several attempts, I was never able to get an All in One batch process to root ZV8, always permissions denied. But I was just trying to ZV8 with Clockwork Recovery to get to Broken Out anyway.
UPDATE 4/3/12
Another option for regaining CWM if you use LGPST
http://forum.xda-developers.com/showpost.php?p=24411050&postcount=83
MT is looking for ZV7 testers for an easy update
http://forum.xda-developers.com/showpost.php?p=24416908&postcount=86
I'm more than a Noob, but far from an expert, so if this contains errors or doesn't deserve it's own thread, feel free to suggest removal!
Cutterstark said:
If, like me and many others you still can't get an OTA update to succeed Alternative 2 is the LGPST method here
http://forum.xda-developers.com/showthread.php?t=1466655
Again, the key is to not loose Clockwork Recovery. As long as you have done the create local.prop step and not done the All in One Option 1 "Prepare for Update" The LGPST ZV8 push will not erase Clockwork Recovery. Then you have ZV8 with Clockwork Recovery and you can get MT"s Broken Out v 1.1 here
http://forum.xda-developers.com/showthread.php?t=1577423
Click to expand...
Click to collapse
Appears that you DO lose CWM with LGNPST. I just tried your method and I no longer had CWM. Maybe you missed a step in the OP? Otherwise, I lost CWM when I pushed ZV8 TOT. Also, just so you know, I did check/test CWM just prior to pushing and it worked just fine.
-Cybie
EDIT: I wanted to clarify and emphasize "Appears" in my reply above. Your method may work perfectly fine, but I had nothing but troubles getting things to work...
is this a bad place to ask how im supposed to go back to zv7? i dont have cwm anymore....
help me out
ejammer said:
is this a bad place to ask how im supposed to go back to zv7? i dont have cwm anymore....
help me out
Click to expand...
Click to collapse
See this Link... All the tools and instructions.
http://forum.xda-developers.com/showthread.php?t=1337386
Be sure to follow the part with which LGNPST Tool Part to install first!!!
-Cybie
yes am back to zv7 now trying to figure out how to do the all in one update steps from mt. it seems in the "prepare for update" steps it fails on copying local.prop or whatev its called.
ejammer said:
yes am back to zv7 now trying to figure out how to do the all in one update steps from mt. it seems in the "prepare for update" steps it fails on copying local.prop or whatev its called.
Click to expand...
Click to collapse
That is the same problem I had. Try the copy local.prop option described above and bypassing the prepare for update.
better yet, contact MT, he is working on an easy solution and needs ZV7 testers
http://forum.xda-developers.com/showpost.php?p=24416908&postcount=86
what if I am on zv6 still?
Son's Revo asked bout v8 OTA today. Didn't want to do it as I figured it would lose root. Currently we are on v6 and rooted (via AIO). Never went to v7, and now with v8 am trying to figure out how to get to v8 and keep root.
Do I need to get to v7 first prior to trying to get to v8 while keeping root or is there a way to go directly to v8 while maintaining root?
I posted in http://forum.xda-developers.com/showthread.php?p=25188375#post25188375 about trying to get to stock v7 not working for some reason so won't go into that here, but thought I would ask about a way to get to v8 with root WITHOUT having to go to v7 first.
I have a solid nandroid (which I just had to use to get a working phone again) I can use so don't mind testing things.
Thanks for any ideas...
***EDIT***
I went ahead and went to stock v7, rooted, and followed the v7 to v8 (save root) process MT created and all is well.