438 replies to this topic

[tucstwo]

Ok, So if you're on system version 6.14.84.XT912 or 6.15.85.XT912 then you know as well as the rest of us that we are all currently STUCK HERE.
If you are NOT on that system, DO NOT go onto it unless you feel like joining the party.

Being that there's information about what people have tried or haven't tried spread all over this forum (and many others) I felt it would be prudent to open a topic to try and get all our heads together and attack this situation as a group.

I know there are some people who were successful in getting RSD to work and get themselves back on path. Perhaps we should find out what makes those people unique?

What methods have you folks tried?

What are our ideas?

Not that I'm counting on Moto or Big Red to give us ICS officially any time soon, I would still like to know that if I wanted to, I could still flash back.

I know a lot of people have written off the idea that there's a solution and say the only way to restore these phones is with the official fasboot files (which we may never obtain) so we gotta see what we can do together! Folks are getting complacent and building ROMS and deodexing this leak as if it's what we're all stuck with, and I refuse to admit defeat.

Let's beat Moto, people!! How's it gonna be done?


 


Update: 5/23/12
Please see 2nd post for information on how to get off this system version. No, it will not bring you back to path, but it will help move you forward to a new system version. Thanks to all involved in that, it's not my work that has made it possible.

With that being said, let's not forget the main purpose of this thread. To get back on the official path.


 

[tucstwo]

Special Thanks to Mattlgroff and everyone else involved. It appears there is now a way to GET OFF .84/.85 and at least move onto the latest ICS version which MAY actually end up being the official build from Moto. Please see this thread

Please Login or Register to see this Hidden Content

I had no hand in this, I am just trying to spread the word. Please thank those involved.

Attached Files

•  small.jpg   3.78KB   13 downloads

[spollock]

I'm on board with this. I have not tried to fastboot back at all (so I don't know if my device would brick or not) - I so want to be able to get back on path though.
Thanks for creating the thread. I am will to try a few things if needed to help find a fix.

[tucstwo]

Nice, the more people on board the better chance we have of figuring out what to do

[Memnoch73]

I know this is GSM but is there any chance this method could help us here??

Please Login or Register to see this Hidden Content

[PWn3R]

I tried to Fastboot back yesterday, and I have a friend who gets Razrs shipped to him to refurbish for a company that will remain nameless. He has received over 50 phones that were softbricked on .84, and has tried to Fastboot back on them. None of those phones have successfully returned to stock. Based on this, I am fairly certain that NO one has successfully rolled back off this upgrade unless they have an unlocked bootloader.

[tucstwo]

I tried to Fastboot back yesterday, and I have a friend who gets Razrs shipped to him to refurbish for a company that will remain nameless. He has received over 50 phones that were softbricked on .84, and has tried to Fastboot back on them. None of those phones have successfully returned to stock. Based on this, I am fairly certain that NO one has successfully rolled back off this upgrade unless they have an unlocked bootloader.

I have read a number of posts of people who claimed they were able to do it. Perhaps one of them will contribute

[superrelaxx]

Things I've tried with failed results:
1. rsd back to 181
2. Matt's utility
3. Using the stock recovery to side load an earlier version
4. Upgrade from 84 to 85 using all of the above

[leviwg]

havent tried, but if you rename this file from what your coming from, couldnt you rename .181 to like 6.14.84/85? and that would upgrade to an earlier version? or pull the file from the .apk we dont speak of? im not on that leak so i cant try any of these.

[PWn3R]

I have read a number of posts of people who claimed they were able to do it. Perhaps one of them will contribute

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.

[_base2]

havent tried, but if you rename this file from what your coming from, couldnt you rename .181 to like 6.14.84/85? and that would upgrade to an earlier version? or pull the file from the .apk we dont speak of? im not on that leak so i cant try any of these.

This alone would not be enough. The install script will check against existing system. Which of course we would fail. BUT along those lines, if we were able to spoof the files / props necessary we might be able to fool the update to install. Of course the difficulty is that we could have potentially incompatible systems. Most likely it would overwrite a lot instead of creating additional files but I'm not sure. We would need to look at the script.

Another alternative may be to build a cwm flashable zip/ ROM (odex, bone stock) on the OTA when it comes out. If the latest kernel revision is the same on the OTA (it is the same for 84/85 afaik) we would be golden.

We would still need a fastboot file compatible with the new partition tables to have a complete safety net but that would certainly be a step in the right direction.

[ BEWARE :: n00bs are afoot ]

[xlightwaverx]

I know this is GSM but is there any chance this method could help us here??

Please Login or Register to see this Hidden Content

I am thinking this may be the way as well. One of us non bricked folks could send our p18 file to one of the stuck ones. Have them Brutal force 181. Boot via Bp tools, root, install our working p18, reflash 181 again, then done.

LOL has anyone tried booting 181 after the brute force method in the unbrick method?

X
Sent from my DROID RAZR using Tapatalk 2

[superrelaxx]

I am thinking this may be the way as well. One of us non bricked folks could send our p18 file to one of the stuck ones. Have them Brutal force 181. Boot via Bp tools, root, install our working p18, reflash 181 again, then done.

LOL has anyone tried booting 181 after the brute force method in the unbrick method?

X
Sent from my DROID RAZR using Tapatalk 2

I got as far as the Droid eye in the boot animation, then it hangs there

[xlightwaverx]

I got as far as the Droid eye in the boot animation, then it hangs there

What about booting via HW Diag/Bp Boot?

X

[superrelaxx]

What about booting via HW Diag/Bp Boot?

X

Tried that as well. Then i wiped data/cache and flashed 181 again and still wouldn't boot past the eye animation

[xlightwaverx]

Tried that as well. Then i wiped data/cache and flashed 181 again and still wouldn't boot past the eye animation

I wonder if we have a way to push the file on from pc when it is in that mode.

X

Sent from my DROID RAZR using Tapatalk 2

[superrelaxx]

I wonder if we have a way to push the file on from pc when it is in that mode.

X

Sent from my DROID RAZR using Tapatalk 2

Backup assistant would pop up on the Web when connected via USB so there is some connectivity.

[PWn3R]

Does ADB work?

[xlightwaverx]

Does ADB work?

Anybody?

X