My friend has a Pro and it started giving the Bootloader screen when he tried to power it on. It had to go get another phone and Verizon wouldn't touch the Pro saying it had been rooted thus the message. I can't seem to find a good fix for this. For now, all I have found was to let it charge via a wall charger for a while and try to turn it on later. Any other thoughts or reason he has this issue?
Thanks!
Try using the stock sbf file and flash back to stock using rsd lite 4.9.
Swyped from my better than life galaxy tab
Related
Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help
Bigstew33 said:
Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help
Click to expand...
Click to collapse
Looks like you'll want to SBF the device. Google search on how to SBF the Droid X and you should come up with some really good guides. Make sure you flash to 2.3.320 if you want to use the latest and greatest that Team Defuse has to offer. I would post a link to one of the guides, but I'm away from my computer today.
Sent from my DROIDX using XDA App
The only way. Into clockwork is pull battery so he says.if not send me your email to [email protected] I have the links.or download
http: market_android_com search?q=pnamerg. teamblackhat.leakloader
Its an app on marketplace call teamblackhat downloader
Sent from my DROIDX using XDA App
I have rsd lite and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf I open the RSD and choose the sbf file but RSD doesn't find the phone. there are drivers loaded says Motorola Flash Interface v. 3.2.5.0. I have it in the bootloader says ok to program transfer mode usb. Thoughts
Thanks
Windows 7 64bit pro gives some difficulty with recognizing the phone. I suggest removing the motorola drivers and downloading them again.
I got it to work by plugging my phone in, then installing the drivers immediately after. It is screwy sometimes though.
Also RSD has device ID options. change that and see if it recognizes it. I also find that sometimes if I plug in my phone after RSD is open it finds it.
wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later
Bigstew33 said:
wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later
Click to expand...
Click to collapse
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.
http://www.droidforums.net/forum/droid-x-hacks/68222-unbricking-your-droid-x.html
See code corrupt error section.
The easiest option is to charge your battery in another X.
amasse said:
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.
Click to expand...
Click to collapse
yes I charged the phone to 100% and tried again and again the battery died before it finished. the sbf file I have is 280 Mb. If there is a smaller one then maybe it will work
It's more likely that the SBF file you have is bad or there is still some sort of USB driver issue going on. Try downloading it again from wherever you got it.
The phone should not go from 100% to dead in an hour. Also the SBF flash shouldn't take nearly that long.
for now I am stuck. I can't get the phone to charge the battery any more. When I plug the phone into the wall it just goes to the bootloader screen by its self and has an error number and a message that the battery is low. So I ordered some batteries with a wall charger. Once those arrive I will try again. thanks for all the help you guys are giving me. update later date
Hello everyone!
I wanted to flash my milestone 2 with the 2.3.4 sbf file but during the process, an error occured and now, my phone is booting by himself in bootloader mode. I've got this message telling me that the code is corrupted and when i try to flash it using RSD lite, the phone is detected but the process fails every time.
I've looked a bit around on google and the only solution that i found is to boot in OpenRecovery but i can't boot with anything else than Bootloader...
If you have any ideas, i'll be happy to read them. =)
You should probably flash/reflash a Milestone 2 specific SBF file.
Sent from my Transformer TF101 using XDA App
I managed to flash my phone with a 2.2 SBF file but at the end of the process, RSD lite send a message telling me to reboot it manualy. The thing is that now, i can't even turn it on and it's not recognised anymore by my computer...
goeland64 said:
I managed to flash my phone with a 2.2 SBF file but at the end of the process, RSD lite send a message telling me to reboot it manualy. The thing is that now, i can't even turn it on and it's not recognised anymore by my computer...
Click to expand...
Click to collapse
It sounds like the battery got too low. Try using a different battery.
Sent from my DROIDX using XDA App
or by a $5 battery charger from amazon
The battery won't charge but the thing is that just before flashing with the 2.3.4, i had about 50% battery so technicaly, i should have some. I'll try with another battery, i hope it will work. =)
I have searched through the threads and none have helped. I have a droid x wich was rooted. I tried unroot and bricked my droid. I can access bootload and have tried to flash numerous sbf files with rsdlite. I keep getting a load fail and and error code 1337 510b. is there any help or am i screwed.
Your phone has to be on in boot loader mode to attempt an SBF.
If your phone won't turn on in any form, your battery may be dead. Try charging your battery via a spliced cord, or try to get your hands on a charged Droid X battery to use.
Sent from my Galaxy Nexus using Tapatalk 2
I get it into boot load. i get the usb conected. i start rsd lite some of the sbf files i load to rsd get an error image missing. when I get one to load and I flash then phone comes back with error 1337 and 510b
Redownload the sbf and check the md5 sum along with that. Then uninstall rsd lite, reboot the computer, and reinstall the newest version. I think the version I have is above 5.0 so look for something like that. Also make sure the battery is plenty charged.
You may have to try several different versions of RSD Lite to find one that works well.
Sent from my Galaxy Nexus using Tapatalk 2
I got one sbf to work. now phone boots, but goes into a new unactivated screen and tells me to call a number. also my battery is not recognized. i guess I am headed in the right direction. thanks for the advice will keep at it. stuck at activation screen
kenc18901 said:
I got one sbf to work. now phone boots, but goes into a new unactivated screen and tells me to call a number. also my battery is not recognized. i guess I am headed in the right direction. thanks for the advice will keep at it. stuck at activation screen
Click to expand...
Click to collapse
Tap the four corners of the screen to bypass the activation screen.
Sent from my Galaxy Nexus using Tapatalk 2
battery not recognized
Cool thanks, one more problem, the battery is not being recognized. Could that be the wrong .sbf? would flashing a rom fix this?
got somewhere
Here is where I am . I got a .sbf for droid x but couldn't get it to root. I flashed a milestone x sbf then rooted that with superoneclick, then installed my backup rom of liberty and I believe that I am back to where I started before I bricked. The only new problem is that my battery is showing a ? and will not charge. I spliced a usb cord to the battery to fool the phone into thinking it was charged so that I could get into bootloader. On another thread it was suggested that if you do that to your battery that it is possibly fried. Any thoughts?
Did you try wiping battery stats?
yes, if you mean by going through the recovery menu. Holding down the power+menu button and getting into that mode.
Did you try a new battery?
? battery
Not yet. that is my next option. Just wanted to send out some feelers and check my options. I will post outcome after I do. Maybe this will help someone else in there trouble shooting.
? for battery
Received new battery. Battery status still showing ?. I am out of ideas.
kenc18901 said:
Received new battery. Battery status still showing ?. I am out of ideas.
Click to expand...
Click to collapse
The battery has to be charged. It may not have arrived in fully charged state.
Sent from my Galaxy Nexus using Tapatalk 2
Battery charged still getting a ? for battery status, will not charge. led lights when I plug it in.
I've read just about every thread and no luck. I updated to a CM port by vanillaLVL, and forgot to back up.
I want to use an sbf to go back to 2.3.3 so I can start fresh with a better rom because his rom doesnt have good in call volume and messes up my bluetooth.
So far every thread about fixing RSD Lite will not work for me.
RSD Lite will not recognize my Droid pro, whether I use Bootloader, CWM, or Usb Debugging mode while phone is on. I have tried looking at every fix, but nothing works. Any tips on how to fix RSD Lite, or how to fix my phone to get it back to stock? I tried using update.zips but I always get an error in the build.prop stopping the update.
Cortal said:
I've read just about every thread and no luck. I updated to a CM port by vanillaLVL, and forgot to back up.
I want to use an sbf to go back to 2.3.3 so I can start fresh with a better rom because his rom doesnt have good in call volume and messes up my bluetooth.
So far every thread about fixing RSD Lite will not work for me.
RSD Lite will not recognize my Droid pro, whether I use Bootloader, CWM, or Usb Debugging mode while phone is on. I have tried looking at every fix, but nothing works. Any tips on how to fix RSD Lite, or how to fix my phone to get it back to stock? I tried using update.zips but I always get an error in the build.prop stopping the update.
Click to expand...
Click to collapse
When i BSF mine i used version 5.6, do you have Moto drivers installed? also just in case make sure you are using a 32 bits version of Windows
I think my windows is 32 bit, and I dled the newest Motorola drivers from the site, but still doesn't work :/ my phone can't access stock recovery either, so might that be causing the issue?
Sent from my DROID Pro using Xparent Red Tapatalk 2
Cortal said:
I think my windows is 32 bit, and I dled the newest Motorola drivers from the site, but still doesn't work :/ my phone can't access stock recovery either, so might that be causing the issue?
Sent from my DROID Pro using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Hey dude... Okay to start off ill tell you what you need... you need to download the base drivers from motorola and have a 32 bit windows computer... What you want to do from there is uninstall your previous drivers... reboot your pc then install them... reboot your pc... now comes the tricky part... take your droid and hold down the volume keys and the button on the right side of your phone and while holding all thoes down hold the power down too .. wait about 30 secs or till the lcd slightly lites up and let go a simple menu should pop up on your phone... now plug in your phone and wait for 10 min if nothing shows up unplug it and plug it in with a different cord and if nothing pops up in 5 min open rsd lite and your phone should show up... now browse to your .sbf or your .sbf.zip and start the flashing process (just click start)..... tell me if this works please!!!
Sent from my DROID Pro using xda app-developers app
Hate to sound amateur but sometimes its just the specific computer. I bricked my xprt at my friends house and tried to sbf it with his 32 win 7 laptop and the drivers kept failing.
Sent from my Nexus 7 using xda app-developers app
hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help