212 replies to this topic

[xlightwaverx]

So now everyone is trying to do what I have been trying to do one week ago? You guys gotta catch up


I was thinking, .181 boot.img and cdt.bin, and .85 dev_tree.bin and system.

But we'll have to design it the OTA way using WinMerge and .75 OTA vs .85 OTA.

There's lots of lines of code that needs to be changed, specially for cdt.bin but we can just use .75 cdt.bin, renamed to one of the .85s (8g, 16g) so devtree.bin works.

Kabeesh?


X

[cconcepts]

So now everyone is trying to do what I have been trying to do one week ago? You guys gotta catch up


I was thinking, .181 boot.img and cdt.bin, and .85 dev_tree.bin and system.

But we'll have to design it the OTA way using WinMerge and .75 OTA vs .85 OTA.

There's lots of lines of code that needs to be changed, specially for cdt.bin but we can just use .75 cdt.bin, renamed to one of the .85s (8g, 16g) so devtree.bin works.

Kabeesh?

I too have been thinking about the same for awhile myself but no test phone to try it on....the cdt8g has the exact code as the gb cdt.bin in all otas....the 16g has the same code but also contains a few more lines of code.....so im thinking 16g is our main culprit...... maybe rename 16g to just cdt.bin and replace the one from .181 in the fastboot file?


X

Sent from my DROID RAZR using Tapatalk

[xlightwaverx]

Sent from my DROID RAZR using Tapatalk

I am not sure which one is used, but i found the update script in the .85 ota and .75 ota and there is a script that deciphers which cdt.bin to use on the .85 and renames it to cdt.bin. Hence, we can use use old cdt.bin from .75 and use the old code in the new update script of .85. I am thinking about creating a drop box account for this process so i can have some collaboration on this. Maybe Drive since it has more security.

X

[xlightwaverx]

I am not sure which one is used, but i found the update script in the .85 ota and .75 ota and there is a script that deciphers which cdt.bin to use on the .85 and renames it to cdt.bin. Hence, we can use use old cdt.bin from .75 and use the old code in the new update script of .85. I am thinking about creating a drop box account for this process so i can have some collaboration on this. Maybe Drive since it has more security.

X

Also if we use the old cdt.bin, we would have to use the old bootloader as well. But this is where issues supposedly arise but the vets should be able to comment on that.

[xlightwaverx]

Also if we use the old cdt.bin, we would have to use the old bootloader as well. But this is where issues supposedly arise but the vets should be able to comment on that.

Anywho, I am going to get started on this after today. Big dance recital for the fam, and I need to focus on that. Then I might try with the above projections. By the end of the day today we should have some more ideas and comments going on to what will and wont work.

X

[StealthFox13]

Ok so i tried going back to .173 from .84 again and it did not work. is this what i do to get rid of my funk and get a working phone again? (nOObing it up again)

[kboss805]

Ok so i tried going back to .173 from .84 again and it did not work. is this what i do to get rid of my funk and get a working phone again? (nOObing it up again)

Can you provide some details on the errors you received?

[StealthFox13]

locked at the boot animation. when i run utility it tells me that cdt.bin, devtree, boot, recovery, and cdrom all say INFOPreflash validation failure

[mattlgroff]

locked at the boot animation. when i run utility it tells me that cdt.bin, devtree, boot, recovery, and cdrom all say INFOPreflash validation failure

Yes, they will. You have to upgrade to 84/85 from the Recovery... read the OP.

[StealthFox13]

so will this work with utility 1.42?

[thearchie]

Hey whats up...Im glad you came up with this process. I need the Blur_Version.6.14.181.XT912.Verizon.en.US.zip. It was taken off the site due to everyone bricking. Thats the file I need to complete the process. I already ran the phone through the utility and Im just stuck in trying to get the right blur version. I have the 6.12.181 and I keep getting errors. Is there still a way to get the Blur_Version.6.14.181.XT912? Well let me know and thanks again.

[kboss805]

Hey whats up...Im glad you came up with this process. I need the Blur_Version.6.14.181.XT912.Verizon.en.US.zip. It was taken off the site due to everyone bricking. Thats the file I need to complete the process. I already ran the phone through the utility and Im just stuck in trying to get the right blur version. I have the 6.12.181 and I keep getting errors. Is there still a way to get the Blur_Version.6.14.181.XT912? Well let me know and thanks again.

Goto the following thread:

Please Login or Register to see this Hidden Content

At the end are the files you are looking for.

[kboss805]

so will this work with utility 1.42?

Read through the first post. But the easiest way is to use Matts v1. 6 utility to get to a pseudo .181. Then you can OTA to 6.14.84 from the recovery console

Sent from my DROID RAZR using Tapatalk 2

[JungleKing76]

I was bored tonight so i decided to go ahead and see if my device was one of the few lucky ones that could fastboot with rsd. Of course like many others rsd failed at step 6. However, instead of looking for a solution to fix my now sift bricked phone i decided to play tech dr and figure it out on my own. And...my phone is back up and running like normal with root. It was sooooo much easier than this thread described.

Here is what i did.

Once i was soft bricked, i powered phone off. Pressed both volume buttons while powering on to bring me back to the menu with recovery, ap fastboot, etc. Then i simply moved down to the second to last option that said something like "HW....AP BOOT". Selected this and let the phone do its thing and it repaired itself. I am back to normal and still have my root.

Sent from my DROID RAZR using Xparent Purple Tapatalk

[TwoBuells]

I was bored tonight so i decided to go ahead and see if my device was one of the few lucky ones that could fastboot with rsd. Of course like many others rsd failed at step 6. However, instead of looking for a solution to fix my now sift bricked phone i decided to play tech dr and figure it out on my own. And...my phone is back up and running like normal with root. It was sooooo much easier than this thread described.

Here is what i did.

Once i was soft bricked, i powered phone off. Pressed both volume buttons while powering on to bring me back to the menu with recovery, ap fastboot, etc. Then i simply moved down to the second to last option that said something like "HW....AP BOOT". Selected this and let the phone do its thing and it repaired itself. I am back to normal and still have my root.

Sent from my DROID RAZR using Xparent Purple Tapatalk

did it take the phone back to 6.14.84?

[wyld]

Just asking for any info and updates on getting us unstuck from .84/.85 and back on path? Any progress?

Sent from my DROID RAZR using Tapatalk 2

[20ripley]

works great thanks to everbody to make it happen will i ever be back on upgrade path

[cconcepts]

Im curious as well.....

Sent from my DROID RAZR using Tapatalk

[0rion_black]

Yeah this works great.. I softbricked today and this had me up and running in about 20mins..