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.
GOOD NEWS! Unless your power button does not work, the Revolution IS unbrickable! After searching far and wide for a method to unbrick my phone from the lg boot screen, I found a way! By now you have hopefully been to all of the other threads and downloaded and installed LGNPST and all of that hoopla so I will just post links and not full directions...here we go:
1) Download and install LGNPST and associated files
forum.xda-developers.com/showthread.php?t=1337386
http://forum.xda-developers.com/showthread.php?t=1466655
2) Follow directions all the way through step 11
forum.xda-developers.com/showthread.php?t=1337386
3) Remove your battery and connect your phone via usb (the hard buttons on the bottom of the phone should blink slowly).
**Make sure battery is at least 25% charged
4) Hold down power + vol up.
5) Phone will come on and read "downloading do not remove cord" or something to that nature. Put battery back in.
6) If you followed step 2 correctly, LGNPST will now show an unknown device and will be in emergency phone book mode. Under the emergency tab it will ask you for 1) a .dll file and 2) a phone book. Click on the folder icon next to .dll file and load the VS910.dll from wherever you have it saved. Click on the folder icon next to phone book. Navigate to the folder where you have saved the correct .tot file. in the "file name" box type *.* and hit enter. If you are in the correct folder you should now see the .tot file, click on it then click "save".
7) Back on the LGNPST screen click on start. It should now say MASTERBIN and a percentage ticking up (if not you have done something wrong).
8) once completed commence re-rooting!
forum.xda-developers.com/showthread.php?t=1348557&highlight=root+v7
special thanks to:
mtmichaelson for his awesome root package!!!
jackpot08 for LGNPST
and all of those who have kept the .tot files movin'
I hope this helps!!!
Good post, this method does work as a last resort, but be warned.. flashing a tot file from the emergency download mode like this will most likely get you stuck in "test mode" -- no more usb mass storage (and possibly other problems).
And so far noone knows how to get out of test mode...
All it took was a simple google search...
https://forun.xda-developers.com/showthread.php?t=151279
https://forun.xda-developers.com/showthread.php?t=151279
Sent from my VS910 4G using XDA
un_brickable said:
All it took was a simple google search...
https://forun.xda-developers.com/showthread.php?t=151279
https://forun.xda-developers.com/showthread.php?t=151279
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
Broken link to a "fix" that is more of a bandaid than a fix, as it requires you to downgrade to froyo.
Sent from my VS910 4G using XDA
Yep.. believe me I searched... and searched and searched until my eyes almost popped out of my head
Nonetheless I'll take test mode over a bricked phone with a fresh 2 year contract any day...
Links for this AND instructions are posted in like 3 other threads lol.
Sent from my AXI0M ICS RAZR using tapatalk.
emergency download mode real way
to get the lg to work with lgnpst i had to open the program then with battery out but held to bottom with fingers ready to put in quickly hold vol up then plug usb to computer then slide battery in quickly and hold power button while still holding vol up if anyone is having problems with lg revo and lgnpst send me a message i spent a week doing everything n finally figured it out
mjollnir2012 said:
to get the lg to work with lgnpst i had to open the program then with battery out but held to bottom with fingers ready to put in quickly hold vol up then plug usb to computer then slide battery in quickly and hold power button while still holding vol up if anyone is having problems with lg revo and lgnpst send me a message i spent a week doing everything n finally figured it out
Click to expand...
Click to collapse
You do not have to go through all that if you have the proper drivers.
Sent from my AXI0M ICS RAZR using tapatalk.
Replace your lg revolution for free
Flashing to v4 froyo tot will not leave the the phone in test mode or rooted. If you can get your phone back to froyo with no test mode then you can bring the phone back, and tell them the phone will not update. I have had two phones already and for some reason they will not take the ota updates. The carrier had no idea I rooted/unrooted and flashed oh so many times. Just a suggestion for noobs who do not want to spend hours or days or maybe even weeks trying to get this phone to work correctly.
Help please
I have tried above and I cant seem to get drivers to install properly
The only one that installs properly is USB Composite device and the LGE CDMA USB does not install properly. I flashed wrong recovery from ROM Manager and stuck at LG screen. LGNPST does not capture my phone. What else should or can I do besides take it in?
drivers
i put both LGAndroidDriver_Ver_1.0_All and LG VZW_United_WHQL_v2.4.1 and they installed correctly is ur phone stuck or can it boot
unbrick Lg revo info
I downloaded the files and had an issue extracting the rom .tot file , How do I extract the .tot so I can use them with the LGNPST.
I have followed the directions and found The LGNPST program comes up blank with no phone info. I am guessing it is because of the .tot files not being "extracted " . I sure would appreciate some help on this one. My phone is bricked.
tommy_guns said:
I downloaded the files and had an issue extracting the rom .tot file , How do I extract the .tot so I can use them with the LGNPST.
I have followed the directions and found The LGNPST program comes up blank with no phone info. I am guessing it is because of the .tot files not being "extracted " . I sure would appreciate some help on this one. My phone is bricked.
Click to expand...
Click to collapse
When you download the .tot file, it should be a zip file. Just extract the zip file using WinRAR or 7zip to somewhere it's easy to find.
If it's not a zip file, then chances are it's already extracted and you don't need to do it.
If LGPNST is coming up blank even though your phone is plugged in, then you need to install the correct drivers or try a different USB cable or a different USB port because it means LGPNST can't connect to your device.
spc_hicks09 said:
When you download the .tot file, it should be a zip file. Just extract the zip file using WinRAR or 7zip to somewhere it's easy to find.
If it's not a zip file, then chances are it's already extracted and you don't need to do it.
If LGPNST is coming up blank even though your phone is plugged in, then you need to install the correct drivers or try a different USB cable or a different USB port because it means LGPNST can't connect to your device.
Click to expand...
Click to collapse
Forgot if it's in Internet Connection and USB Debugging Enabled too.
Gel Pen6 said:
Forgot if it's in Internet Connection and USB Debugging Enabled too.
Click to expand...
Click to collapse
Sure did, thank you! Yes make sure you have selected the option for "Internet Connection" and USB Debugging is enabled.
unbrick Lg revo info
I can't get it to internet connection because i can't boot into anything . It is like it is stuck at boot. also the .tot files do not extract with any zip program . I have loaded the vs910.dll and the drivers onto my computer but the LGNPST program still not recognizing any phone. for that matter the the computer has not recognized the phone , maybe due to I cannot set internet connection mode. The USB De bug was enabled before all this started.
The whole situation of not completing boot came about when I happened defrosted the astro file manager app. Help
tommy_guns said:
I can't get it to internet connection because i can't boot into anything . It is like it is stuck at boot. also the .tot files do not extract with any zip program . I have loaded the vs910.dll and the drivers onto my computer but the LGNPST program still not recognizing any phone. for that matter the the computer has not recognized the phone , maybe due to I cannot set internet connection mode. The USB De bug was enabled before all this started.
The whole situation of not completing boot came about when I happened defrosted the astro file manager app. Help
Click to expand...
Click to collapse
u gotta open lgnpst then plug your phone on to be put on emergency download mode also the .tot file is already extracted like was already said in a previous post and make sure u register the .dll
Evnoth said:
Flashing to v4 froyo tot will not leave the the phone in test mode or rooted. If you can get your phone back to froyo with no test mode then you can bring the phone back, and tell them the phone will not update. I have had two phones already and for some reason they will not take the ota updates. The carrier had no idea I rooted/unrooted and flashed oh so many times. Just a suggestion for noobs who do not want to spend hours or days or maybe even weeks trying to get this phone to work correctly.
Click to expand...
Click to collapse
I had a few issues with this namely Tots not loading right getting perm black screen, I pulled the batt, put it back in and did a hard reset (wipe) back to stock then rooted added CWM with MT's hlep of course and am now re flashing gingervolt to broken out 1.1 and still puts me back in test mode, even restoring older backups put me in test mode, only v4 seems to work....WHY?
Thanks I finally got it back running with the LGNPST , tot version 7 . The phone works now but I also am in test mode and cannot switch my usb. Question, Can I use The LGNPST and select tot version 4 and install that as before to get my usb back. And if so will I then be able to get OTA updates or will I have to return it to store for that. I hate being stuck in test. What happens with phone stuck in test ?
tommy_guns said:
Thanks I finally got it back running with the LGNPST , tot version 7 . The phone works now but I also am in test mode and cannot switch my usb. Question, Can I use The LGNPST and select tot version 4 and install that as before to get my usb back. And if so will I then be able to get OTA updates or will I have to return it to store for that. I hate being stuck in test. What happens with phone stuck in test ?
Click to expand...
Click to collapse
You'll be able to get OTAs but you'll still be stuck in test mode. To this day there is no known method (yet) to get out of test mode. Someone correct me if I'm wrong but the only difference I know of with test mode is that you can't transfer files via USB cable anymore. You have to either use adb or an adapter for your microSD card to your PC.
Sent from my DROID RAZR using Tapatalk
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
Solution here on post No 6
So, trying to sort my damn phone out and then leaving it alone.
Upgrading to official 4.1.2
Using RSD lite 6.1.4
I managed to get motogp to flash then it froze with nothing further going on.
Edited the xml to leave only the system and cdrom files. The system uses multiflash due to the large size.
First two parts go fine then on the third it freezes on download.
Ideas?
So this happens when flashing anything over 100mb via fastboot.
Finally back on my backup of official 404 but i have a feeling some items from the official 4.1 are still there.
Mainly system files that are from jb.
My smsc number keeps dropping and i can't change my network carrier.
My only temporary resolution for sending texts is to reboot which gives me about 3 minutes before the smsc disappears again.
/help
Sent from my XT890 using XDA Premium 4 mobile app
Use RSD-LITE 6.1.5. I have read in another forum, only RSD-LITE 6.1.5 will work, when u use it with win7.
Never tried 6.1.4 but can confirm that 6.1.5 works perfect on Win7 ultimate 64 bit
ICuaI said:
Use RSD-LITE 6.1.5. I have read in another forum, only RSD-LITE 6.1.5 will work, when u use it with win7.
Never tried 6.1.4 but can confirm that 6.1.5 works perfect on Win7 ultimate 64 bit
Click to expand...
Click to collapse
Thought 6.1.4 was the latest! Damn. Will give .5 a try.
Found a dl and guide here forum.xda-developers.com/showthread.php?t=2446515
Sent from my XT890 using XDA Premium 4 mobile app
So I bricked it, temporary of course. Black screen, green LED
How I did this;
Was stuck unable to erase anything, suspect - 4.1 files as I thought. Boot system thinks I have 4.1 but I have 404 due to the failed data write.
Flashed original 404 files as follows via the latest fastboot which lets you do multi on large files
radio
bos
gpt
Rebooted back to recovery, had a cr32 error. Thought screw it.
flashed boot and recovery
rebooted back
erased cdrom and system
flashed cdrom - fine
flashed system - stuck on the third write
rebooted, erased system
flashed dnx and ifwi - Now these screwed it over due to the 4.1 data
Rebooted, black screen, green LED
Used http://forum.xda-developers.com/showthread.php?t=2184877
Basically installed the driver, followed prompt turning on phone when it said and clicked ok
Installed the other software, wasn't sure if it needed it.
Dropped my dnx and ifwi files from 4.1 in there
Let the phone vibrate which signifies it's back off.
Ran the bat file (before turning the phone on)
Let it find no phone, turned phone on and it did it's magic
Turned phone on with vol key - held and let go of power soon as it vibrated and viola - back in bootloader
So, still pretty much at square one although I'm slowly downloading the 4.1 FW again to re-try with RSD lite 6.1.5
SOLVED!!!!!!!!!!!!!!!!!
USB 3 port. FFS.
Schoolboy error.
Plugged into my lesser USB 2 I didn't know I had and fastbooted the system and it went through, went back to RSD 6.1.5 and the whole thing went through with no problems, took about 9 minutes.
FINALLY ON OFFICIAL JB
SO, try other USB ports, latest driver and RSD Lite 6.1.5
**** yeah... I'm tempted to flash CWM and try a custom rom now to see if that resolves that issue with bootloops when flashing over 404 via cwm/twrp
Maybe in a week or two after a well needed holiday
Nice man, good that it is solved!!
Sent from my GT-P5110 using XDA Premium HD app