438 replies to this topic

[bokajay]

I remember there used to be leaked flashable .zips for other Moto devices that would downgrade leaked SOAK builds. So basically somewhere out there (on a [certain desert app] server) maybe there are two files named: Blur_Version.6.14.84.XT912.Verizon.en.US.zip and Blur_Version.6.14.85.XT912.Verizon.en.US.zip ??

[xlightwaverx]

I remember there used to be leaked flashable .zips for other Moto devices that would downgrade leaked SOAK builds. So basically somewhere out there (on a [certain desert app] server) maybe there are two files named: Blur_Version.6.12.84.XT912.Verizon.en.US.zip and Blur_Version.6.12.85.XT912.Verizon.en.US.zip ??

6.14.xx

X

[VantenKiest]

I tested on 2 razrs just used RSD 748 when i tried it.. one failed and one worked used the exact same process .. however i tried to repeat this SAME EXACT PROCESS.. and it failed the 2nd time.. so im guessing its just a variable chance that causes it to succeed but not one you the user has control over. Trust me when i say this.. DEVS ARE WORKING THEIR ASSES OFF TRYING TO FIX THIS..
your best bet it to be patient and not try too many things.. once we have a method it may or may not work for everyone due to what you try.. so please for the love of your beautiful device.. dont go insane with it..
I know how frustrating it must be being stuck but at least its a working system.

[bokajay]

6.14.xx

X

fixed

[PWn3R]

I was about to pull the trigger on a set of Razr's with broken glass on Ebay and use them to guinea pig and see if i can find a way off this. I wish i had more time to read up on android stuff because given some of the other stupid things i've figured out in the world of IT (in my day to day job) i have little doubt that I could eventually find a solution.

[tucstwo]

Question, the part of the fastboot file that freaks out. What happens if you replace the .bin file with a working one from .75 or .181 and bring the md5 with it for the xml file? Question 2: do Nandroid back ups benefit anything? Question 3. I have read time and time again that when people were on the .75 leak and they would RSD back to .744 that their kernel # would change to what it was on GB. But me, every time I went from .75 to .744, my kernel version would stay the same. Why is that?

[tucstwo]

Back in the day, I mentioned that I had this issue going on in this post

Please Login or Register to see this Hidden Content

Other people said when they reflashed .744 or .173 that their kernel changed back to 2.6.35.7-g6133522 mqr374@nj05lnxdroid05 #2 but for me, I ALWAYS stayed on 3.0.8-g6f89f34hudsoncm@il93lnxdroid54 #1. Since I went to .75, I never ever ever had my GB kernel version back. And I don't know why. My phone would boot up and run perfect as well. The current kernel version is similar to .75 an it's 3.0.8-gc895fbehudsoncm@il93lnxdroid52 #1.

[tucstwo]

I've seen a few, but no one has posted steps, and most of them were on other forums and were a person making a single post on an account that was brand new.

These are some posts of people who were able to restore back from .84/.85. The last one includes Step by Steps

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

[tucstwo]

Opps, last thing, I promise. Does anyone know how they did it with the Bionic when this happened to them? And what they did to fix it? I remember the Path Fixer which manually flashed the fastboot files but ignored the cdt.bin or somehow repaired it an they were able to restore their Bionics

See here

Please Login or Register to see this Hidden Content

[PWn3R]

P3Droid has looked at this already, but I don't think he found anything helpful yet.

[PWn3R]

These are some posts of people who were able to restore back from .84/.85. The last one includes Step by Steps

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

I looked through these posts including the post from the guy who rolled back to .75. He may have successfully gotten himself back to .75 on the phone (which i find unlikely) but it doesn't fix the fact that the CDT is still wrong (which is why i doubt it worked) and he didn't fastboot back successfully.

I'm not sure that we are going to find a way out of this one without someone knuckling down and buying some phones to guinea pig this on. I may yet do that and see what I can come up with,

[xiinator]

Looks to me that, while able to technically flash back to .75, they didn't really resolve the bootloader, thus they were still stuck, just in a different version.
I'm just going to wait for a sure and definitive solution. Thank goodness my phone is at least working with no issues.

Sent from my DROID RAZR using Tapatalk 2

[joeyx2]

Maybe it has to be something with .181. You can roll back from .75 which people were on .173 and you can't roll back from .84/.85 and they came from .181

[bryan77]

Can someone explain what is in the cdt.bin and why it hangs? Does it contain the bootloader? If not which .bin or .img file does? And , could it be the simple fact that it can be upgraded but not downgraded? If that is the case, can the older bootloader be modified with a build number that is newer or equal to the .84/.85 bootloader? Just thinking out loud...

Sent from my DROID RAZR using Tapatalk 2

[nailbomb3]

I remember there used to be leaked flashable .zips for other Moto devices that would downgrade leaked SOAK builds. So basically somewhere out there (on a [certain desert app] server) maybe there are two files named: Blur_Version.6.14.84.XT912.Verizon.en.US.zip and Blur_Version.6.14.85.XT912.Verizon.en.US.zip ??

I wondered about this too. What do they do for the soak testers do if a flasb goes wrong or to keep them ON path. Hrmmmmm

Sent from my DROID RAZR using Tapatalk 2

[joeyx2]

I wondered about this too. What do they do for the soak testers do if a flasb goes wrong or to keep them ON path. Hrmmmmm

Sent from my DROID RAZR using Tapatalk 2

Give them a new phone? I'm pretty sure they don't test it out on hundreds of thousands of devices so they can afford to just give them a new one then just fix the one they send in.

[orcsbane13]

I wondered about this too. What do they do for the soak testers do if a flasb goes wrong or to keep them ON path. Hrmmmmm

Sent from my DROID RAZR using Tapatalk 2

I'm sure the people testing these roms are using devices with unlocked bootloaders so they can restore out of any bad update. Have to remember, these leaks were never supposed to be installed by anyone except select Motorola testers.

Sent from my ADR6425LVW using Tapatalk 2

[tucstwo]

If Moto had testers with a bootloader unlock tool, that tool would have most definitely been leaked...I strongly believe that if there's a group of people who aren't moto employees just regular general public testers, somewhere in there would be a mole who would leak the tool.

[tucstwo]

Can someone explain what is in the cdt.bin and why it hangs? Does it contain the bootloader? If not which .bin or .img file does? And , could it be the simple fact that it can be upgraded but not downgraded? If that is the case, can the older bootloader be modified with a build number that is newer or equal to the .84/.85 bootloader? Just thinking out loud...

Sent from my DROID RAZR using Tapatalk 2

I also would like to know if anyone actually knows what the cdt.bin file is, what it does? Why can't it be replaced when manually flashing a system version? And if the bootloader is the problem, where does it get flashed? Can it be examined? What's the differences on a code level? This stuff is somewhat over my head as I do not know how to open a bin file and examine it.

[spollock]

I have received a phone via eBay that is on .173 still. It is for my wife. Is there anything useful I can extract from it to help us? It is wanting to update to .181 but I have not accepted it yet.

Cheers