Related
I flashed my stock. 2.1 Milestone (rooted) preparing it for froyo. Apparently the .sbf was corrupt or wrong;
GOT_TELUS_2_2_1FULL.sbf
I am told the correct sbf is;
BL_9078_GOOD_sholes_HS_Consumer_replacer.sbf\BL_9078_umts_sholes_HS_Consumer_replacer.sbf.
- Now It’s stuck in bootloader mode
-RSD Lite seems to recognize phone but the “Start” button remains disabled, grey, it can’t be pushed (with either .sbf file.)
-I’ve loaded a fresh copy of RSD Lite v5.0 (previously had v4.7). Both behave the same; the start button is disabled.
I want to save this phone and am looking for alternative tools or methods to ultimately flash the proper .sbf…Help please!!!
BOOTLOADER SCREEN BELOW
PHP:
Bootloader
90.74
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
RSD LITE SCREEN BELOW
PHP:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x009074
DRM Version: N / A
AP Die ID: 06a0010c60720304000000000400
BP Die ID: 0000000000000000000000000000
AP Public ID: 4bd4854c5cb58e173025f2751e09441b44fa681f
BP Public ID: 0000000000000000000000000000000000000000
-----------------------------------------------------------------------
Model Port No Port Type IMEI/ESN/MEID Status
S Flash OMAP3430 1 USB N/A connected
(I’ve successfully flashed my other Millstone an many other phones)
Any help is greatly appreciated,
PK
The greyed out start button is an error in RSD. What you want to do is rename that really long sbf file to a one letter name such as a.sbf
If you are planning on rooting, you can flash the VR from android.doshaska.net/rootable but I would not try it until those bootloader errors get corrected. Be careful on the site I gave you, one sbf is for bootloader version 90.78, the other is for yours (90.74)
Hope that helped.
Sent from my Milestone using XDA Premium App
Thanks skadude66
That kinda worked, I renamed it “A” and also had to put it in the root on my C; drive. The button worked.
The bad news is it wouldn’t take. I got the following error message:
PHP:
Device Properties
EMEI/ESN: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
PHP:
Status
Failed flashing process Failed flashing process (0x7100); phone connected.
(I also discovered by hunting around that I almost tried to flash the wrong ver of.sbf, 90.78 instead of 90.74. It didn’t make any difference though.) Failed.
Regards, PK
pk2 said:
Thanks skadude66
That kinda worked, I renamed it “A” and also had to put it in the root on my C; drive. The button worked.
The bad news is it wouldn’t take. I got the following error message:
PHP:
Device Properties
EMEI/ESN: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
PHP:
Status
Failed flashing process Failed flashing process (0x7100); phone connected.
(I also discovered by hunting around that I almost tried to flash the wrong ver of.sbf, 90.78 instead of 90.74. It didn’t make any difference though.) Failed.
Regards, PK
Click to expand...
Click to collapse
Try using the latest version of Motorola USB drivers, your phone might not be completely recognized.
EDIT: http://androidforums.com/droid-all-...hing-process-0x7100-rsd-lite.html#post1274587
I used that to help me out when I had that error as well. It worked for me, it should for you as well.
Thanks. good read so far. Nice to know I'm not alone and there may be a way. I think the trick when I did this on my other Milestone was copying the sbf here there and everywhere. Haven't updated the latest usb drivers.
Regards, PK
Well crap,
I downloaded v.5 moto usb drivers from moto. One self installing program. RSD doesn't see the phone at all now. Tried twice. Uninstalled drivers with program "total uninstaller" (normally very good), still nothing in RSD.
Seem to recall having to manually install either HTC or moto drivers. Guess I got to hunt around and find out what the moto trick is.
crap.
Regards. PK
Finally new Moto Drivers (v5.0) installed, start button in RSD "start" button works but when pushed, RSD reads "Flash Failed"
Any help? PK
try RSD v4.7, maybe its the RSD problem.
Have you check out your system hardware manager to see if the Milestone was recognized completely?
Hi,
i got same problem 2 days ago.
at my point i just had to install a new rom.
if you get in Open Recovery try to install miui oder CM.
I got the same error when i tried to install CM7. So I installed MIUI and voila everything worked.
Thanks for the reply's!
I tried all of above and it still "failed" to flash.
I can't get into open recovery or the stock "recovery" utility (this phone was stock when this all started).
The phone shows up in "devices and printers" as "unspecified-S flash omap3430a" not as Milestone
Regards, PK
I was having a similar problem. How are you getting into the bootloader? I was using the volume button.
For whatever reason, when I got into the bootloader using the D-pad, RDS Lite found the phone.
I still can't seem to flash anything properly, but it found it.
It pretty much jumps straight to boot loader mode all by itself after powering up. No button combination takes me anywhere but the boot-loader. There's no way to get out of it either.
Thanks, pk
Stuck in boot loader milestone usb drivers
Man I've tried all of above.
The one thing someone mentioned is "is the phone was recognized by win764" . Not really, It only shows up Under "Devices & printers" as "unspecified":
S Flash OMAP3430
I have tried every Moto. USB Driver set I can find. None do anything different. I can not find any manually installable drivers.
(My working hacked milestone_eu shows up as "unspecified" ) to.
Makes me think Maybe my drivers ar screwed. How can I put them in manually without an install a pckage I wonder. Anyone had this prob?
I can't do anything with the either phone, from the computer, when tied together with USB (I.E. access sd card, portal, etc.)
Thanks PK
bump -please
Just to clarify, you have two Milestone's, one is stuck in bootloader mode, the other works. Connecting either to your computer show 'unspecified'. Is that correct?
First, the bootloader version doesn't matter, I've had 90.73, 90.74 and 90.78 on my milestone at diferent times, doesn't make any diference.
The error code you got in bootloader mode (ending in 27) means one of the signed partitions failed the signature check, probably the result of a bad flash. Reflashing usually fixes that.
Your problem sounds like a problem with your USB on your PC, either drivers or a hardware problem (most likely drivers). Fixing your pc should allow you to reflash your milestone correctly.
When connecting a Milestone in bootloader mode to RSD lite, RSD cannot extract the IMEI info etc, the display you pasted is what I would expect when connecting in bootloader mode. If you connect to RSD when the Milestone is booted up (running android), it will show the IMEI etc. All you need to check is that RSD says its connected and its usually ready to flash..
Things you can try:
1: Try flashing from another computer
2: Dual boot Ubuntu on your PC, then try flashing with sbf_flash (google it), no additional drivers are needed, should work straight out the box.
3: Uninstall EVERYTHING on your pc from motorola, then in system/device manager uninstall all the windows USB drivers, reboot and let windows reinstall the USB drivers, then try re-installing the motorola USB drivers and RSD lite.
4: Try a diferent USB cable, also try a diferent USB port. Connect directly to the computer, do not use a USB hub.
Hope this helps.
So I wanted to FXZ back to .902 with rsd lite. I downloaded the latest Motorola USB drivers, and rsd lite 5.7, but for some reason when I start the program it won't recognize my phone is plugged in. I start it in Fastboot AP and even waited 10 min, and nothing. The only thing I have done with the phone was update to .905, root, installed safestrap, and eclipse 3.0. I'm running in unsafe mode in safestrap right now. Any suggestions? This is driving me insane, I just want to get back to stock .902.
Are you using a notification cable? Not all usb cables are created equal, maybe try with a different one.
Sent from my DROID BIONIC using Tapatalk
linuxgator said:
Are you using a notification cable? Not all usb cables are created equal, maybe try with a different one.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Definitely this. I've seen way too many threads that show that RSD Lite and/or Moto devices are very picky about their USB cables. Try another one to see if it's detected.
Failing that, go peek in your device manager (Start > Run > devmgmt.msc) and see if the phone even shows up in there. You could be having larger issues with USB device detection.
linuxgator said:
Are you using a notification cable? Not all usb cables are created equal, maybe try with a different one.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Omg if you were here I would kiss you. I had not even thought that the usb cable that came with the Bionic would be the issue, but sure enough I used my cable that came with my Incredible 2 and IT WORKED. thanks so much
Mine is recognized when I use the command 'lsusb', but doesn't show up on RSDLite. I will try another cord but wouldn't it make more sense that if it's being recognized it is a software issue?
psychonot said:
Mine is recognized when I use the command 'lsusb', but doesn't show up on RSDLite. I will try another cord but wouldn't it make more sense that if it's being recognized it is a software issue?
Click to expand...
Click to collapse
Which version of RSDLite are you using? There's a newer version out, 6.14 I think it is, that doesn't work all that well. Right now 5.7 is still the recommended version. The cable thing still sometimes is the issue, even if it is recognized in other modes sometimes it just doesn't work right. You can also try flashing with moto-fastboot as a command line program. There are both windows and linux versions available.
Working Atrix HD
Worked after installing ADB Driver thanks!
Still no joy
so I have a high-speed USB 2.0 cable, ADB driver displays in the Device Manager, and Rsd Lite 6.15 still does not display my Moto X.
Any other suggestions?
Droid razr m - can't flash/fix with rsd lite 5.7
I can't get my Droid Razr M off the boot screen, endless boot loop happening with the startup screen.
I downloaded the RSD Lite 5.6 (then 5.7) and tried both. Neither is recognizing my device.
I downloaded the AdbDriverInstaller.exe for Android. Did not even recognize my device - the device is plugged in, I'm looking at the AP Fastboot Flash Mode (S) on my phone. Says Device is Locked (whatever that means). Status Code: 0. Transfer Mode: USB Connected. So it recognizes that there is a USB plugged into it.
I ran ALL of these firmware versions from this website through the RSD Lite - sbf . droid - developers . org - NONE are working.
I keep getting Status: Failed Flashing Process: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I saw some forums that said within the actual firmware XML file, to delete these lines of code, so I did (note: I tried running them before and after the file edit):
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="oem" var="fb_mode_clear" />
SOMEONE HELP!
Droid Razr Maxx
amandafrat said:
I can't get my Droid Razr M off the boot screen, endless boot loop happening with the startup screen.
I downloaded the RSD Lite 5.6 (then 5.7) and tried both. Neither is recognizing my device.
I downloaded the AdbDriverInstaller.exe for Android. Did not even recognize my device - the device is plugged in, I'm looking at the AP Fastboot Flash Mode (S) on my phone. Says Device is Locked (whatever that means). Status Code: 0. Transfer Mode: USB Connected. So it recognizes that there is a USB plugged into it.
I ran ALL of these firmware versions from this website through the RSD Lite - sbf . droid - developers . org - NONE are working.
I keep getting Status: Failed Flashing Process: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I saw some forums that said within the actual firmware XML file, to delete these lines of code, so I did (note: I tried running them before and after the file edit):
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="oem" var="fb_mode_clear" />
SOMEONE HELP!
Click to expand...
Click to collapse
I am having the same problem with my Droid RAZR Maxx (XT912). I rooted it, then flashed CM 10.1.2. with Safestrap. Since then, I've had all
sorts of trouble. I've been trying to get it back to the factory ROM, but me being a total noob at the time, somehow made the mistake of backing
up my factory ROM in a CWM format instead of TWRP, meaning that I never could access it from Safestrap, and Safestrap would not uninstall
no matter what I tried. This was a long time ago, I have been researching all over the interwebs to fix my problem since. I tweaked my phone to
the point that it worked well for everything I needed, even though I was still stuck with CM.
It worked just fine... Until now. My phone went dead one day, and when I tried to charge it and reboot, it woke up stuck in bootloop. I have no idea why it decided to get stuck in bootloop, but I need to get it back ASAP. I have done hours and hours of research, set up adb and RSD Lite v5.6, got all the driver software I needed, and then found the firmware to take it back to Android v 4.0.4. My problem is that neither adb, nor RSD Lite will recognize my device. My computer recognizes the device as a Mot single adb interface, but that is the only recognition I get from my computer. My phone is saying the same thing as the quoted post above
Phone is Locked, Status Code: 0, Transfer Mode: USB Connected.
I have tried a few different USBcables, but I don't have the original factory cable from Motorola because my dog decided she wanted it more. I have an LG factory cable, but it still won't work with that.
tl;dr: My phone (Motorola droid RAZR Maxx XT912) is stuck in bootloop, adb and RSD Lite won't recognize it, but my computer will.
I'm in need of a wee bit of assistance, does anyone have any advice to offer?
Anonymous Assassin said:
I am having the same problem with my Droid RAZR Maxx (XT912). I rooted it, then flashed CM 10.1.2. with Safestrap. Since then, I've had all
sorts of trouble. I've been trying to get it back to the factory ROM, but me being a total noob at the time, somehow made the mistake of backing
up my factory ROM in a CWM format instead of TWRP, meaning that I never could access it from Safestrap, and Safestrap would not uninstall
no matter what I tried. This was a long time ago, I have been researching all over the interwebs to fix my problem since. I tweaked my phone to
the point that it worked well for everything I needed, even though I was still stuck with CM.
It worked just fine... Until now. My phone went dead one day, and when I tried to charge it and reboot, it woke up stuck in bootloop. I have no idea why it decided to get stuck in bootloop, but I need to get it back ASAP. I have done hours and hours of research, set up adb and RSD Lite v5.6, got all the driver software I needed, and then found the firmware to take it back to Android v 4.0.4. My problem is that neither adb, nor RSD Lite will recognize my device. My computer recognizes the device as a Mot single adb interface, but that is the only recognition I get from my computer. My phone is saying the same thing as the quoted post above
Phone is Locked, Status Code: 0, Transfer Mode: USB Connected.
I have tried a few different USBcables, but I don't have the original factory cable from Motorola because my dog decided she wanted it more. I have an LG factory cable, but it still won't work with that.
tl;dr: My phone (Motorola droid RAZR Maxx XT912) is stuck in bootloop, adb and RSD Lite won't recognize it, but my computer will.
I'm in need of a wee bit of assistance, does anyone have any advice to offer?
Click to expand...
Click to collapse
This is a really late reply, but I just went through this. Try a different USB port on your PC. My usb 3.0 port wouldnt recognize my Photon Q
boxes said:
This is a really late reply, but I just went through this. Try a different USB port on your PC. My usb 3.0 port wouldnt recognize my Photon Q
Click to expand...
Click to collapse
Well, I actually fixed this a long time ago, but thanks for the suggestion. I ended up using mattlgroff's Droid RAZR Utulity to restore my phone to factory default. If anyone ever has any trouble with your RAZR, try using that, it'll make your life a lot easier.
If you don't mind, please swing by and give Matt some thanks, he really deserves it.
same issue with an XT926
So, i would use the utility mentioned above, except it's for a xt912, and i have the xt926. I've tried RSD Lite 6.15 and 5.7 and both with different USB cables. I downloaded ADB and the SDK Tool Kit and went through the instructions at visualgdb.com[slash]KB[slash]usbdebug-manual (sorry for the '[slash]'... noob not allowed to post links) to get "a USB driver" to install when i connect the phone. I've also downloaded a ROM file, VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml , but i've been to so many sites at this point, i can't remember where i got that file. When i open/decompress this file in RSD Lite, the software version description has 'VANQUISH" in the name. If I attempt to "Safely Remove Hardware and Eject Media", then the phone shows up as "Fastboot VANQUISH S". So i think i have the right file.
Also, i downloaded ADB and opened it. It launched a command prompt. I used the command "adb devices" to list my phone and it returns nothing.
The phone is in the AP Fastboot mode (with "Device is LOCKED. Status Code: 0" and "Transfer Mode: USB Connected", yada yada yada).
Anybody got any further ideas? Is this easier done in Linux?
Change to USB 2.0
Change to USB 2.0
As the title says my milestone (90.78) is stuck at bootloader, I tried to flash it with RSD light but when I plug in the phone it wont recognize it
Be sure that the cable is in good conditions and the same for the usb port. Than update to last version RSD lite, if this doesnt help, try unistalling the device from device manager of Windows
Sent from my Milestone using xda app-developers app
I figured what the problem was, as I use windows 7 I had to run RSD in compatibility mode for xp
Try to use a newer version of RSD Lite. Newer versions are totally compatible with Windows 7.
may try this Version of RSD Lite: http://droid-world.bplaced.net/load.php?file=download/tools/RSDLite5.7.zip
for me it works perfectly on windows7, but remember to run RSD Lite as Admin on windows7
Ok so I got the same errors that everyone is getting with the utility n RSD on my pc... I had the drivers and all the correct flashes and programs.
What went down is that every single time I tried to flash any method it failed, what was wrong? I wasnt using one of the back USB ports of my computer... as soon as I plugged my usb cable to the back ports RSD made it out perfectly with firmware 144 with the modified XML. So for anyone having this problem maybe you should try using a back usb port!
I was trying to flash the lollipop kdz to my phone and was having problems with drivers but then one time it apparently was working but it still gave me an error popup so I unplugged it and now it always boots into firmware update mode :crying: Now I can't get the drivers to install. It shows 3 devices: Mtp device, LGE Android phone, and CDC Serial port (this is just from memory so the actual names might be slightly different). The MTP device always gives the error "Failed to start" and the other 2 say no driver found. I have tried different pcs and driver versions with the same results. I tried this but it says no drivers found. Does anyone know of a fix for this? Is there a way to manually specify the drivers to use or something?
I updated the drivers to the version from LG's website and now the drivers seem to be working except for the mtp one. Now when I try to flash it give the error "Connection to server failed, try again in a moment" and if I click retry it fails with the message "Upgrade stopped due to an error". Anyone have suggestions on how to fix?
Update: I tried the tot method as well and it fails with an error getting model name.
jonmast said:
Update: I tried the tot method as well and it fails with an error getting model name.
Click to expand...
Click to collapse
Make sure that you have the correct drivers installed. For Verizon they should be the LG_VZW_United_WHQL_v2.20.0 one. Use the lg flash tool 2014 http://forum.xda-developers.com/showthread.php?t=2797190 and a kdz file. I believe that you can update to lollipop directly with the lg flash tools. I could not install the lollipop kdz as I kept receiving the same issue "cannot connect to server" so I installed stock 4.4.2 that my device came with and updated to lollipop ota. If you install the the same stock software that your phone shipped with it will still say "cannot connect to server" but it will indeed update your software. I believe that the key is to making sure you install the same stock software your device shipped with for it to actually update to your phone in my experience.
I am using the drivers you mentioned. Do you know if the mtp driver failing is an issue? Also, I tried 3 different kdz versions with the same results.
Do you have a custom recovery like TWRP or CWM?
mach01 said:
Do you have a custom recovery like TWRP or CWM?
Click to expand...
Click to collapse
No