74 replies to this topic

[bilbobaggins]

Its because some systems don't like the naming setup. Rename the folder and batch, I will re-upload a renamed batch later.


As for a step by step 206 to 208....fastboot flash the 6.12.181 files from the 1.6 utility (as many as possible, lots will fail), flash the boot208.img from this unstuck, then go to recovery and install the zip for 6.16.208.

Sent from my DROID RAZR using Tapatalk 2

Thanks Matt, worked like a charm! Is there a reason why the zip in recovery seems to fail but the system updates anyway? I'm sure there is but I guess what I'm wondering is does it matter.

[chuck24]

Its because some systems don't like the naming setup. Rename the folder and batch, I will re-upload a renamed batch later.


As for a step by step 206 to 208....fastboot flash the 6.12.181 files from the 1.6 utility (as many as possible, lots will fail), flash the boot208.img from this unstuck, then go to recovery and install the zip for 6.16.208.

Sent from my DROID RAZR using Tapatalk 2

.

I think the inner noob has came out of me but when you say go to recovery and flash the zip do you mean the stock or clockwork recovery?

Sent from my DROID RAZR using Tapatalk 2

[(TSON)]

At that point you'll only be able to get into stock, so that's not really a question

Stock all the way!

[chethammer]

Why can't the 208 boot.img in the unstick tool just be flashed straight over a working 206?

[(TSON)]

It can, but the update zip is meant to patch .181's system files so trying to do those exact same changes to an ICS ROM would... make a big mess.

[chethammer]

No one answered the #12 post. Are there any improvements that make this worthwhile doing?

[chuck24]

At that point you'll only be able to get into stock, so that's not really a question

Stock all the way!

Kinda figured that. Just wanted to make sure...

Sent from my DROID RAZR using Tapatalk 2

[wyld]

Works like charm as always guys. went from .84 to .206 and now on .208 ty for all hard work!

[mattlgroff]

Changed the name and the batch name as well. The OP has been edited.

[(TSON)]

No one answered the #12 post. Are there any improvements that make this worthwhile doing?

Please Login or Register to see this Hidden Content

[dellenrules]

Using this method, would it be possible to substitute the 181 fastboot files with the VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02 fastboot files.
and the 206/208 boot image with the boot image of the incremental update that follows and flashing that OTA.

If we could do that, then it would be possible to to get back to a gingerbread image prior to 181 putting us back on the official path.

[chuck24]

if for some reason 208 is giving me problems could i use this method to roll back to. 206?

Sent from my DROID RAZR using Tapatalk 2

[JungleKing76]

Using this method, would it be possible to substitute the 181 fastboot files with the VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02 fastboot files.
and the 206/208 boot image with the boot image of the incremental update that follows and flashing that OTA.

If we could do that, then it would be possible to to get back to a gingerbread image prior to 181 putting us back on the official path.

Unfortunately the way the system is, we can never go back to GB. Not that i want to.

Sent from my DROID RAZR using Xparent Purple Tapatalk

[JungleKing76]

if for some reason 208 is giving me problems could i use this method to roll back to. 206?

Sent from my DROID RAZR using Tapatalk 2

Yes, you should be able to with no problems......in theory. Unless someone had tried it and can confirm if it fails or succeeds.

Sent from my DROID RAZR using Xparent Purple Tapatalk

[chuck24]

Yes, you should be able to with no problems......in theory. Unless someone had tried it and can confirm if it fails or succeeds.

Sent from my DROID RAZR using Xparent Purple Tapatalk

Im going to try it as soon as i get off of work today.

Sent from my DROID RAZR using Tapatalk 2

[cconcepts]

Not sure if anyone else had this issue
But i was unable to use the new unstuck utility to do this.....it wouldn't load up. So i put the 208 boot file in the older utility and renamed the script in the bat file to load 208 not 206 and success! Not sure what the issue was but after unzipping the utility when i clicked on the bat file the command window would come up and immediately close....couldn't do anything with it.
Sent from my DROID RAZR using Tapatalk

[ogrekane313]

what would you change the name to? also when you say flash the .85img to regain root do you mean the .85 in the unstuck utility? and whats the root method used or would it be the same method used in the 1.6 utility? thanks just don't wannt screw it up

[cconcepts]

what would you change the name to? also when you say flash the .85img to regain root do you mean the .85 in the unstuck utility? and whats the root method used or would it be the same method used in the 1.6 utility? thanks just don't wannt screw it up

Open the .bat file in the utility in a text editor and change where it says the command files/moto-fastboot 206 ect. Simply change the number from 206 to 208 ( dont do anything else!) And save file....put the 208 file from the new utility into the files folder of the older utility. Run the older utility like normal. It will still say 206 in the menu but but when u select it it will come up flashing the 208. And yes use the 85 boot image from the utility, boot into bp tools and root...then reflash the 208 image in the utility. Profit

Sent from my DROID RAZR using Tapatalk

[orcsbane13]

Not sure if anyone else had this issue
But i was unable to use the new unstuck utility to do this.....it wouldn't load up. So i put the 208 boot file in the older utility and renamed the script in the bat file to load 208 not 206 and success! Not sure what the issue was but after unzipping the utility when i clicked on the bat file the command window would come up and immediately close....couldn't do anything with it.
Sent from my DROID RAZR using Tapatalk

I had same thing happen. I fixed it by moving the unstuck.bat and files folder into my sdk/platform tools folder and it started working.

Sent from my DROID RAZR using Tapatalk 2

[tucstwo]

Changed the name and the batch name as well. The OP has been edited.

Wait so now we don't need to do any name changing? It'll all just work now? Cause reading this thread has made me more confused than I was to begin with.