A way back to stock from leaks

[Mikeymaxima14]

.I was curious about how to do it exactly vs a backup in CWM? Or do you mean that a stock backup is in CWM and there isn't another way to do it through 'stock'?

Sent from my DROID BIONIC using Tapatalk

 

[thetingster]

WARNING. BE careful after installing 901 I hear you will brick the phone if you install a rom right now. A custom rom that is.

 

[reminon]

U can't in stock recovery, yes it is in clockwork.

Sent from my DROID BIONIC using DroidForums

 

[jntdroid]

Given that a small amount of users took 5.9.901 (or whatever it was) that was actually pushed out, just by mistake, my *hope* is that when they get to the final release, they'll allow it to update no matter what you're coming from... I don't see why that would be a problem from their standpoint. Worst case scenario they put a warning that says something like, "If you're not coming from 5.*.*, this could wipe more than normal, but it's your own fault, except for those of you on 5.9.901, which is our fault..."

 

[nh2123]

Will this work if im on the 5.7.893 that broke webtop and makes it unusable?

Sent from my DROID BIONIC using DroidForums

 

[wil20mva]

How can you tell which version of the kernal you ACTUALLY have? I know theres the description file you can change so you can change the "About phone" page and i can even make it seem like i have 3.X.X version android OS. And romming does change the text for the 5.x.xxx because i went from rommed 893 to 886 and back to 893 after a rom change, without doing the sys file update. From my understanding, the kernal/system file didn't change and this is where the whole "fallout" of the regular update path came about. The different sys file along with the leaked update dont match with what the ota has as a valid device. Sooo... thanks in advance...

Sent from my DROID BIONIC using Tapatalk

 

[reminon]

The 5.x.x.x is the system, it'll change depending on what system your rom is based on. The kernel and radio...etc are what change through ota or leaked updates. If you haven't accepted an update, then you are all stock except whatever system the rom you are using is based on. The part about the update path. While trying to find files to unlock the bootloader by scanning the Moto dev servers, people stumbled upon some leaked updates. we were able to flash them in order from stock->X->X...etc. each update looks for a certain "system, radio, kernel, and webtop" version from the previous update. The problem is that the ota updates are looking for all stock, so alot of us were stuck with whatever we had until the bootloader is unlocked, but now we have a chance to get back on the right path.


Sent from my DROID BIONIC using DroidForums

 

[wseyller]

Will this work if im on the 5.7.893 that broke webtop and makes it unusable?

Sent from my DROID BIONIC using DroidForums

The 5.6.893 update you installed before going to 5.7.893 is what breaks webtop.

Using releaseroot 2.1 to flash your system back to. 886. Cant remember if this step also restores the webtop. If not then you afterwords could use moto fastboot commands to flash the webtop image

Sent from my DROID BIONIC using Tapatalk

 

[Lakilaulea]

This is awesome. I've been searching for a way back for weeks and now I'm finally back on path.

 

[Dave12308]

Given that a small amount of users took 5.9.901 (or whatever it was) that was actually pushed out, just by mistake, my *hope* is that when they get to the final release, they'll allow it to update no matter what you're coming from... I don't see why that would be a problem from their standpoint. Worst case scenario they put a warning that says something like, "If you're not coming from 5.*.*, this could wipe more than normal, but it's your own fault, except for those of you on 5.9.901, which is our fault..."

The only real problem from their standpoint would be that a universal update by definition would have to be a complete install, and not just a differential patch update. This would increase the size of the OTA download by quite a bit. I am not sure how large the entire software load for the Bionic is, but i'd guess in the neighborhood of 200+ MB as opposed to the ~60MB size of the updates we've seen so far (893 and the accidental 901).

The problem with this is that the OTA download counts against your data allotment. If you happen to be on the carrier network when the OTA decides to download, and also happen to be on a 2GB tiered data plan; well there goes 10% of your data allotment for the month. It would also put a huge load on their OTA infrastructure.

 

[mikespe]

OK guys...I'm planning on doing this in a little bit. I have all the files on my computer. But I need to make a back up for what I have now just in case. I have SafeStrap installed but I'm thinking that won't be the best to make a backup. Should I uninstall Safestrap & then install Bootstrap? Or is there a better way to make a complete back up? also, can I just uninstall Safestrap or do I need to go into safestrap & wipe the "partition" it created for ICS4Bionic which is what I installed with Safestrap? Just trying to dot my "I's" & cross my "T's" before taking this on!

Thanks

 

[reminon]

I just made a backup with safestrap , downgraded from 5.7.893, to the first ota, made sure i was forever rooted and flashed 5.9.901, and restored my backup. After that i used the files from dhacker i believe for the. 901 radio. I didnt uninstall safestrap, this method reverts back to stock, then to 5.5.893. So everything will be deleted unless you did a backup.

Sent from my DROID BIONIC using DroidForums

 

[mikespe]

I just made a backup with safestrap , downgraded from 5.7.893, to the first ota, made sure i was forever rooted and flashed 5.9.901, and restored my backup. After that i used the files from dhacker i believe for the. 901 radio. I didnt uninstall safestrap, this method reverts back to stock, then to 5.5.893. So everything will be deleted unless you did a backup.

Sent from my DROID BIONIC using DroidForums

Thanks but I just want to get back to 5.5.893 so I am back on the OTA path...I'm finished being a guinea pig with these updates...I just want normal with root...and of course a unlocked bootloader but that's in the future! LOL

 

[reminon]

Thanks but I just want to get back to 5.5.893 so I am back on the OTA path...I'm finished being a guinea pig with these updates...I just want normal with root...and of course a unlocked bootloader but that's in the future! LOL

You can use safestrap, make a backup, use the method from rootzwiki. And you will be on stock rooted 5.5.893. Then of you want to restore your backup then do so.

Sent from my DROID BIONIC using DroidForums

 

[mikespe]

You can use safestrap, make a backup, use the method from rootzwiki. And you will be on stock rooted 5.5.893. Then of you want to restore your backup then do so.

Sent from my DROID BIONIC using DroidForums

Won't restoring my backup cause force closes with apps? I figured I would have to reinstall everything fresh?

Plus it looks like P3Droid has created a streamlined version of the Rootzwiki method...he should be posting a one click script soon..