Phone: Droid Razr HD XT926, locked bootloader, was rooted, not sure now
Issue: OTAs had not worked for awhile, but I wanted to go to KitKat. So, I tried to use Matt's 1.41 utility. I may not have had the most up-to-date Motorola USB drivers when I started. The update did not work. Now, I just get the "Motorola Logo and Dual Core Technology text", but phone then goes black. I am able to get to AP fastboot screen, but all attempts to re-try Matt's 1.41 utility, or the House of Moto 4.1, or RSD Lite 6.2.4 are unsuccessful. All of them show <waiting for device>.
Any ideas why I can't get past <waiting for device>?
Fastboot screen:
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
Assuming you've updated the drivers at this point, are using the stock usb cord and following all the details in the op to a T? Might try another USB port...
grnsl2 said:
Assuming you've updated the drivers at this point, are using the stock usb cord and following all the details in the op to a T? Might try another USB port...
Click to expand...
Click to collapse
You are correct on those assumptions except the stock usb cord. The cord I am using was fine when I first started my adventure. USB debugging was on and plugging in the phone+cord caused PC to recognize the phone. But, now my PC does not even flinch when I plug the phone+cord into the USB port. Should the PC be flinching (recognizing the phone) when all are plugged in? If it is not, any recommended tricks to encourage PC and phone to play nice together?
I have tried two different ports. I will check documentation and verify they are 2.0. I will also see about finding a motorola OEM cable just to rule that out.
Thanks for the response!
Additional info:
- Motorola USB drivers I used (USB Driver.6.4.0.2014-10-24): [droidrzr website] /index.php/topic/57858-motorola-tools-rsd-lite-usb-driver/
I used to do a lot of flashing from various laptops to different phones with mixed results. Certainly strange when sometimes one works and the other does not. Hard to pinpoint why with so many variables. In your situation, working at one point then bam...
grnsl2 said:
I used to do a lot of flashing from various laptops to different phones with mixed results. Certainly strange when sometimes one works and the other does not. Hard to pinpoint why with so many variables. In your situation, working at one point then bam...
Click to expand...
Click to collapse
Update: Decided to give it another shot today. Went back to original cord (when I had success prior to bad flash). Booted to fastboot. Plugged into USB port. Today, my PC decided to try and recognize it! Windows failed once trying to find drivers for "Fastboot VANQUISH S". So, I decided to disconnect and try again. This time, drivers found! Fastboot screen changed to include the "usb connected" message below the "Fastboot Reason: Boot menu selected" message.
Using House Of Moto, I was able to successfully flash 4.4.2 183.46.10. Phone is charging up now in preparation for rooting and unlocking.
Good news there!
Related
I have put the phone into bootloader. Used both, Volume up when booting, or even in Terminal emulator "reboot bootloader". So it reads:
Code:
Bootloader fastboot mode
80.89
Battery OK
Ok to program
Transfer mode:
USB
At this point if I fire up RSD Lite, it reads "Model: S Flash OMAP3430 IMEI: N/A Status: Connected". But doesn't show anything in device properties. If I choose a SBF and hit "Start" it prepares and fails with an error message "flashing failed".
If I connected to a linux box and tried sbf_flash instead, it complains "Reboot phone into bootloader!"
Any suggestion how can I flash a stock SBF back? I remember doing it successfully when I installed J.Y.Daddy's rom CM 7 in early december last year.
Hm. Someone else was having trouble with sbf_flash recently too... So I redownload to check. The latest sbf_flash doesn't seem to work for me, either.
This is how I've configured udev for android:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
The one that works for me (attached):
8418ec2de4d7f3cfa3751fbc2ae2a6e0 sbf_flash
The one I just downloaded that doesn't work:
db8afd24f7a0dc6d3d78556dec811694 sbf_flash.new
Edit: Wha... I tried again and it worked? I'm going to reboot my computer. I'll try a few times and see if maybe it's just not sporadic.
1.make restall USB drivers.
2.restall RSd lite.
What sbf are trying to flash.
Sent from my Milestone XT720 using xda premium
mchlbenner said:
1.make restall USB drivers.
2.restall RSd lite.
What sbf are trying to flash.
Click to expand...
Click to collapse
I've done (1) and (2) multiple times before I asked here, unfortunately no success. I tried multiple SBFs, mainly STR_U2_01.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBRTINT_P029_A014_HWp3_1FF.sbf (Singapore) because this is the one I installed before updating to JYDaddy's CM7.
Somehow I have a feeling in bootloader mode the phone is not responding correctly. As both sbf_flash and RSD Lite fail to flash, they can't even communicate to the phone. And it wasn't the case 2 months ago. Maybe some update caused the problem. But again as I understood, bootloader is sacred, and if it were touched, it won't load any further.
If anything else rings a bell, I'm all ears.
No, your bootloader is still 80.89, should be fine. If the bootloader rejects stuff, it tells you that.
Just some rambling ideas: Maybe try a different USB cable if you haven't already -- perhaps the bootloader detects USB because of the 5V power line, but some of the other lines are damaged or one of the contacts is dirty. Plug unplug on the computer side, too. Does SD card access/adb work?
Mioze7Ae said:
Just some rambling ideas: Maybe try a different USB cable if you haven't already -- perhaps the bootloader detects USB because of the 5V power line, but some of the other lines are damaged or one of the contacts is dirty. Plug unplug on the computer side, too. Does SD card access/adb work?
Click to expand...
Click to collapse
Ok, changing USB cable is the last resort. I have to borrow one from a friend. It didn't strike me as SD card export works (copied a file), so does ADB (logcat). And they work from all ports of my laptop, whether running Windows (vista) or Linux (Mint 11). Still I may give it a try. If I damaged some pin required for bootloader only (and not data transfer), I'll be surprised. There can't be anything like that.
make sure ur in bootloader mode not in fastboot bootloader i had that problem before better to manual boot to bootloader
Oh, good eye! I missed the "fastboot mode" detail in the first post. That's the fastboot bootloader for booting custom kernels.
Regular bootloader: hold volume up and camera while powering on.
lol mioze i was in the regular bootloader, and sbf flash didnt work for me, so i decided to boot into windows via virtual machine to use rsdlite - was a great relief that it worked haha
thats good to hear man enjoy flashing custom roms
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.
DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.
Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.
In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.
If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.
OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.
These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk
We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.
Always nice to hit the Thanks button for those who've helped.
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk
ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.
LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >
I have an at&t LG G3 D850
It was stuck with a McAfee lock and kill switch after letting someone borrow it.
I finally found a guide that let me get into download mode.
That guide wanted me to use LGUP but it would not recognize my phone it just kept saying unknown even though the phone shows in my device manager.
So now I am trying LG Flash Tool. But it seems to be stuck in the "ready" position.
I've heard that it doesn't work well with win10 but I am not sure. I only have this laptop and one with win8 on it. I was getting an error "milky way not connecting" but set the compatibility to win7 and that stopped.
Any idea why it is stuck in the ready position?
LilNerd1 said:
I have an at&t LG G3 D850
It was stuck with a McAfee lock and kill switch after letting someone borrow it.
I finally found a guide that let me get into download mode.
That guide wanted me to use LGUP but it would not recognize my phone it just kept saying unknown even though the phone shows in my device manager.
So now I am trying LG Flash Tool. But it seems to be stuck in the "ready" position.
I've heard that it doesn't work well with win10 but I am not sure. I only have this laptop and one with win8 on it. I was getting an error "milky way not connecting" but set the compatibility to win7 and that stopped.
Any idea why it is stuck in the ready position?
Click to expand...
Click to collapse
Your using a USB 2.0 port correct? USB 3.0 won't work. And you've changed the LG/Android com port to com41 in device manager?
If so have you tried unplugging and replugging the phone? Remember each time you attempt to flash you need to reboot the device. (Make sure your in download mode)
About the mcafee thing. I do know it blocked download mode, since you said you found away around it. I don't think flashing will remove the mcafee lock. But it's still worth a try!
Sent from my iPhone using Tapatalk
hyelton said:
Your using a USB 2.0 port correct? USB 3.0 won't work. And you've changed the LG/Android com port to com41 in device manager?
If so have you tried unplugging and replugging the phone? Remember each time you attempt to flash you need to reboot the device. (Make sure your in download mode)
About the mcafee thing. I do know it blocked download mode, since you said you found away around it. I don't think flashing will remove the mcafee lock. But it's still worth a try!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes, USB 2.0 and I have tried unplugging and replugging the phone. COM41. I just rebooted and tried again but it is still stuck at ready. I am in download mode.
I tried it about an hour ago and read to disconnect the USB and reconnect to "jump start" the flash tool. At the time when I disconnected it gave me a "waiting for connection" message. When I reconnected it was starting to work but my cat unplugged the USB and I haven't been able to get it to work since.
LilNerd1 said:
Yes, USB 2.0 and I have tried unplugging and replugging the phone. COM41. I just rebooted and tried again but it is still stuck at ready. I am in download mode.
I tried it about an hour ago and read to disconnect the USB and reconnect to "jump start" the flash tool. At the time when I disconnected it gave me a "waiting for connection" message. When I reconnected it was starting to work but my cat unplugged the USB and I haven't been able to get it to work since.
Click to expand...
Click to collapse
You'll just need to keep retrying. But yeah need to unplug and replug sometimes to get it to work. Have you rebooted your computer? Also what sort of USB cable are you using? The oem LG one?
If you've changed USB ports etc each time make sure you check device manager as it can change the com port back.
Sent from my iPhone using Tapatalk
hyelton said:
You'll just need to keep retrying. But yeah need to unplug and replug sometimes to get it to work. Have you rebooted your computer? Also what sort of USB cable are you using? The oem LG one?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Using the cable that came with the phone.
I will give restarting my computer a shot.
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.
bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.