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.
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
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
Hi Guys,
I got into a problem here, and I need help! I have a milestone 2 with the latest Endlees CyanogemMod, Android 2.3.7.
I was trying to follow the steps into using the internal memory as a SD card (link http://forum.xda-developers.com/showthread.php?t=948887), but I wasn't successful.
Here cames what I did:
First I tried to follow the steps:
1- create a file image in /data and a folder in /sdcard
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=5242880 (1024x1024x5 --> 5Gb)
busybox mkfs.vfat /data.storage.img
But that didn't work, the terminal emulator just said that the directory couldn't be found.
Then I downloaded Busybox from Android Market, and installed it. But when I executed the program, the installation wasn't done because it was insisting that Busybox wasn't able to access the folder, and didn't have superuser access to root. Even with the permission on Superuser OK!
So after that, I tried to reboot my milestone 2, and now it won't even get to the boot screen of android (screen with the rotating square)
I tried to use the boot recovery tool, and wipe all system data, and reboot, mas it isn't working. Something I noticed on Recovery Tool is that apear a messagem saying "E: Can't Open /cache/recovery/command" and "E: Can't Open /cache/recovery/caller.
Even the battery light won't turn on. If turn off the cell and try to recharge it, appears a image of the battery with a "?" on it... I tried to connect the cellphone to the PC with the usb cable, but it isn't recognized...
I hope someone can help me, I just can't afford to lose this phone.... Thanks
Look in this topic http://forum.xda-developers.com/showthread.php?t=1344740 it should help you solve this problem
in general: firstly you need to charge your battery in another working Milestone 2 or in some universal battery charger (because bricked Milestone 2 is not able to charge battery) and then you need to flash SBF and it should be ok
Anonymous_ said:
Look in this topic http://forum.xda-developers.com/showthread.php?t=1344740
in general: firstly you need to charge your battery in another working Milestone 2 or in some universal battery charger (because bricked Milestone 2 is not able to charge battery) and then you need to flash SBF and it should be ok
Click to expand...
Click to collapse
I read somewhere else that even if the MS 2 is bricked the battery charges. Very very slowly, but it charges.
thanks for your tip... I read the entire topic, but there is a problem. My battery must be around 30% or something, but when a connect the milestone 2 with the pc via usb cable, the lateral light won't even lit... And the pc won't even recognize it...
edit: when I connect the cellphone to the pc, the light lit for 30s more or less, the appear the Motorola logo with the rabbit on the side, but then the light turn off and I get stuck in the same situation...
carpet55 said:
I read somewhere else that even if the MS 2 is bricked the battery charges. Very very slowly, but it charges.
Click to expand...
Click to collapse
I don't know, maybe it is possible, but I as far as I know, everyone, who had bricked M2, charged the battery outside his phone...
So he can try it in the bricked phone, but he can't be 100% sure it will charge, right?
colucci.ti said:
thanks for your tip... I read the entire topic, but there is a problem. My battery must be around 30% or something, but when a connect the milestone 2 with the pc via usb cable, the lateral light won't even lit... And the pc won't even recognize it...
edit: when I connect the cellphone to the pc, the light lit for 30s more or less, the appear the Motorola logo with the rabbit on the side, but then the light turn off and I get stuck in the same situation...
Click to expand...
Click to collapse
Yes, thats why I said here and even in the topic I referred to, you have to charge battery in another non-bricked Milestone 2 or in universal battery charger. When your M2 is bricked, it wont charge any battery (or maybe it will, but very very slow according to carpet55's post ).
So now you have to get some universal charger or working M2 (or another battery).. This is your step no. 1. Then you can flash it via RSDLite by SBF file.
ok Anonymous_!
I'm going to find a way to charge the battery and do what are you saying.
But RDS Lite can flash the android even if windows it isn't recognizing the cell phone on the usb?
thanks again! I'll return with more info when I get my battery fully charged..
After you will have charged battery, you will have to boot into bootloader by holding Power+Volume Down+Camera button, then windows should recognise it (maybe you will have to install drivers too) and then you can use RSDLite (don't forget to run it with administrator rights).
Anonymous_,
final question of the day... Where do I get the SBF file?
I'm from Brazil, so should be the brazillian version of this link?
and-developers.com/sbf:milestone2
You are on the right path
Grab Brazil 2.2 version from http://and-developers.com/sbf:milestone2 and it should be ok.
I can confirm that no, the battery does not charge when bricked. I left mine going for over 24 hours and nothing -_-. So ended up using a universal ac adapter set to 5 volts and some wires directly to the + and -. This didn't work after half an hour so I upped it to 7v and about ten minutes later, all good.
During my research to find how to fix it, someone was saying the charge sequence software in in the system or boot data, and since it was all corrupt - no charge.
But you perhaps allready have enough juice in there to load up bootloader successfully, so try what anon said and hold d-pad up and power on until the screen flashes blackish grey and let go. Then it'll tell you if the battery has enough charge to flash a sbf
Sent from my A953 using xda premium
Guys,
I'm thankful to everyone who tried to help me, especially Anonymous_!
Yesterday, in the same day I bricked my phone, I flashed it even without charging to 100%... and everything has gone well, but it was a close call, because my battery had only 5% left when the milestone returned to live!
Good to hear!
Sent from my A953 using xda premium
Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!
http://droid.koumakan.jp/wiki/SBF
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!
ezsbf has helped a lot of people
Sent from my MB870 using xda premium
so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas
Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2
did you try wiping cache or data?
delete this
jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up
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