Hello. So I bought the Droid X, rooted it flashed CM9 on it, stable and worked good, noticed one bit of a problem so I read through the thread.... lots of reading... and nobody else had the same problem. I thought it might just have flashed incorrectly so I was going to re install it, I hit boot to recovery, and it got stuck in the "M" logo screen thing. Any ideas?
I am not new to flashing, I know how to use the command prompt.
Closed as per OP request.
Related
First off let me analogize for the length of this lol
Recently I SDF 3 of my families Droid X (all had OTA 2.2 on them), we switched to Rubix 1.6 and I wanted to follow what was posted from him to help with battery issues (http://www.sephtin.com/?p=172). Well I started on my finance phone I started with doing a SDF and the phone encountered a boot loop at the red eye animation. I fixed that and went on to rooting the phone then I had issues with getting the phone to go into ADB shell with # prompt (I would rather just root doing it the old fashion way with typing lol). The computer is a Windows XP machine so I decided it could be some form of an issue with the computer. The computer has SDK along with the latest Moto Connect 4.7.1. I can access everything from the phone fine. I did not install the charging drivers as it never asked for them. Anyways moved to a Windows 7 machine and decided to download all the drivers and SDK fresh so did it and installed and restarted both the computer and phone. Anyways long story short did my mom's phone and it went through SDF fine no issues and then when starting to root I again had issues getting the phone into ADB shell with # prompt. I started over on the root commands and it went fine that time. Move to mine and well I encountered red eye boot loop and the ADB issues. So my big time question is what is going on with the SDF? Am I missing some form of a driver? Is the red eye loop something that happens frequently? I have read on a different forum about an ADB driver but I have never needed it for my Captivate or anything. Also can anyone give any advice as to what would cause these SDF issues or the issues with ADB???? I have delt with ADB and Odin3 with my captivate a lot and never had any issues like this. But I know this phone's boot loader is a different so you have to do something differently. THANK YOU EVERYONE for any help you can give me with this. All the phones now have Rubix 1.6 on them but I would love to know what would cause issues like this for future reference THANK YOU
after sbf i was stuck at the red eye too. boot back into stock recovery and factory reset. it'll get you back in business.
muhcells said:
after sbf i was stuck at the red eye too. boot back into stock recovery and factory reset. it'll get you back in business.
Click to expand...
Click to collapse
Thank you man, that is what I did both times. I am just wanting to know mainly if there is a reason this happens something I am doing wrong, an incorrect driver anything lol.... My friend did his phone today and had the same thing happen so i dunno it seems kind of common for some reason.
is there any htc EVO 4g ROMS out there on internet
Maybe look in the evo forum?
how to restart
hi i had flashed my motorola defy + mb 526 with DFPRC_U_4.5.3-109_DPP-14-17_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P027_A024_HWp3a_Service1FF.sbf
After rooting it every option is working properly but
it displaying no signal and when i type *#06# it leaving me empty imei box
can any one help me?
rockzsanil said:
hi i had flashed my motorola defy + mb 526 with DFPRC_U_4.5.3-109_DPP-14-17_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P027_A024_HWp3a_Service1FF.sbf
since it is not showing signal and not getting imei number when dail *#06#
so i had applied sdf file in RSDLite5.4.4 it started and completed, my phone switched off and for about 2 mins in rsd it shows pass but my phone did not owned till now(i think it was hanged) how can i start my phone
can any one help
Click to expand...
Click to collapse
Why are you posting in the droid x forum about defy?
Sent from my MB886 using xda app-developers app
I downloaded rom manager and bootstrap on my droid x. I downloaded flyx rom and then after it was suppose to apply it after it booted, it became stuck on the logo, going from the "droid to red eye" over and over until I pull the battery. So every time I turn it on it does the same thing. I then tried to wipe my phone by putting it into recovery mode. It says can't open/cache/recovery/command. I tried to figure out the rsdlite solution but I couldn't figure out or find a good explanation on how to use it. My bootloader is 30.04. If there is an answer to this in this forum any where please point me to it.
flyx is an ancient rom for older version of android.
if doing a factory reset doesnt help, i suggest sbf. instructions here http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
Ok thanks, I thought I knew what I was doing but i'm pretty positive i failed ...I'll try this out then.
you're welcome. if you need any help with sbf or anything, dont hesitate to ask.
A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?
check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/
It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!
My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community
Hey all,
Bit of a sticky situation. Tried to flash 2.3.3 from the link below on my Droid 2, and unfortunately, it didn't go well. I installed ClockworkMod Recovery, rooted the phone, made a Nandroid backup and proceeded to flash a 2.3.3 ROM. The installation aborted and I thought hell to it, I'll just reboot into Froyo.
http://www.mydroidworld.com/forums/...id-2-gingerbread-2-3-3-release-prerooted.html
Then the trouble began.
My Droid now boots into absolutely nothingness. It has the "M" splash come up for all of a second or two and then nothing. The screen is live, but it's completely blank. Trying recovery mode (Power+X) heeds the same result. I can get into the bootloader with Power+UP, but I'm not sure what I can do? It complains the battery is too low which really stings, because I'm not sure if the Droid 2 charges its battery when off... :/ I hope it does.
Please, can anyone help here? I hope to hell my Droid 2 isn't bricked - I got this handset second hand and cannot afford another.. Clockwork Recovery has a backup somewhere, it's just a matter of recovering it. I hope?
It sounds like you bricked your phone.
Follow the instructions below on the droid-life website and you should be back up and running. I added the updated Motorola drivers and RSDLite 5.5. The SBF file on the droid life website will put you back at 2.2 so you phone will boot
http://www.droid-life.com/2011/09/0...k-to-stock-2-2-to-receive-gingerbread-update/
RSDLite 5.5 - http://www.4shared.com/file/no12cF9K/RSDLite55.html
Download the Motorola 5.2.0 Driver with Motohelper and install from the link below
Motorola Drivers - http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers?pubid=987654
Thank you for replying
I just tried what you suggested and unfortuately, I get the error "Phone is not compatible with multi-interface super-file." Having read about I cannot find a definite solution - any ideas? :/
Update!!
As events conspired against me all night I found a download for a UK British .sbf file. RSDLite took the file and flashed my phone no problem - all is fixed (I hope!!)
fatalfuryy you sir are a gent for providing those links - I thank you wholeheartedly.
Hey guys let me start by saying I have done quite a bit of searching and im not a total noob when it comes to this stuff. I have still been unable to find an answer to my questions...
So basically I have a Droid 2 and I flashed the CM9 ICS Alpha onto it had it running great (Cant wait to get past alpha ) But due to the fact that its an alpha and really nothing works I wanted to go back to my librity rom... I tried to boot into recovery and that caused a boot loop instead of booting into recovery.
So from there I went to flash the stock SBF onto the phone and it keeps just getting stuck in a boot loop even when flashing the stock SBF. What have I done! lol How do I get this thing back to a factory setup?
I would really like to figure this out but if I cant I will be putting another mobo in it as that may be the easier solution haha
Thanks for taking the time to help me with this and if you know somewhere this has already been discussed please direct me to it as I could not find it...
Nevermind lol
I was able to get it to boot by booting into recovery and running the factory reset. But I had already tried that once before posting this and it had not worked...
Well anyway all is good for me now maybe this will help someone eventually have a great day.