Likely a bad burn or a bad download.
This is a discussion on Linux solution to your Windows/RSD lite problems within the Droid X SBF forums, part of the Droid X Rescue Squad category; Likely a bad burn or a bad download....
Likely a bad burn or a bad download.
Allow me to share my Verizon / Motorola story with you so that you understand exactly where this gem of information sits within the whole those two completely messed up groups.
1/ I have been trying to get the 4.5.602 and ultimately the 4.5.605 update. The phone would try to load the latest (605) but crashed consistently.
2/ I tried several different ways to get this to load and finally decided the nuclear option was my only choice.
3/ I reset the phone to factory level by clearing everything off the phone, reactivating the phone and tried again. Guess what - still could not load the update.
4/ Called Verizon who walked me through a piece of crap tool via PC on Motorola website that ultimately resulted in their tool claiming there was not software update available.
-- We are now somewhere in the 4-5 hours of time committed to this simplistic task --
5/ Called Motorola and they said, send in your phone and we will update it in 3-4 weeks. And a loaner? No. So I said, right, live without my phone for 4 weeks, not going to happen.
6/ Since I am a small business customer with Verizon I went back to them.
7/ They contacted, guess who, MOTOROLA. Back to square zero.
Bottom line, I spent about 8-10 hours trying to solve until....this tread.
In about 20 min I have the ISO burned to disk, booted the PC and added the package which installed flawlessly.
Another 10 min later I have re-activated the phone and loaded the air update to 4.5.605
Now I am back to my zen thanks entirely to this post and the author of this ISO.
Just so you know, I think you are super cool and way, way, way brighter than anyone (including 3 levels up in tech support) at Verizon and Moto.
Thank you, where can I donate?
Last edited by macpro88; 10-12-2011 at 03:12 PM. Reason: MOD EDIT: Language
DroidXForums.com Supporting Member Membership
Glad you got some real help finally
"FEZ aims to create a non-threatening world rich with ambiance,
a pleasant place to spend time in."
I don't take any donations. You can contribute to the suite if you like as fez posted above. Just glad to help : D
I'm slowly growing out of r00t n00b, it's taken much time to read and learn. I see now that the Moto products provide unique challenges, especially the Droid family (X, X2, OG1/2/3, Glob). I've struggled, at times, to understand what exactly I'm dealing with whilst I spelunk about in this AOS environment. I've found many contributors whom provide clear, consistent, and (relatively) safe instructions for manipulating and maneuvering the AOS. I have much gratitude for anyone who has taken the time to provide this foundation of insight, understanding, knowledge, and data, or even links to those resources. Every time I exercise my 'Operator Headspace' too effectively, I'm relieved to know that I'm able to return to a safe AOS, albeit throttled with bloat. Every time this happened, I've used the links and resources of this thread to find my way back and reboot my DX. Thank you, thank you, thank you.
Scott -:sDs:- SscoootzZ
Need help with my bricked X, a week after gingerbread downloaded it bricked my phone. I have now tried the sbf flash method and worked the first time then phone locked up again and i got the triangle and droid. tried again did all the wipe data and cache now phone will not boot. stuck on moto red and white M.
What happened before flashing it?
it got buggy like the home button would work the volume and then screen froze and did battery pull then triangle droid screen. did the first sbf flash and worked great for about an hr, then froze again battery pull and triangle droid again re flashed now stuck on the red m screen after wipe data and wipe cache and reboot.
should i try it a third time??? what may i have done wrong
There really isn't a lot of room for user error with the iso. You could have some sort of hardware issue. I would try to flash it again, maybe try the 2.3.340 (froyo) iso and see if it stays stable.