So here's my major problem. I factory reset my N5 for my dad to use since I got a 1+1. It was rooted so i went into the settings for supersu and hit full un-root. Well that just broke everything and when I try to boot, I get a bootloop. So at this point i'm like, okay. I've fixed this before. My process. power off>fastboot>recovery>recovery settings>wipe cache/partition>done>factory reset>done.>reboot. Still get bootloop so I thought, okay ****. Flash a factory image and start a-new. I start up fastboot, and plug the phone into computer(Win7 32-bit) and do all this jazz. I realize i factory reset and wiped it so usb debugging won't be checked, so of course my computer doesn't list the device. ****. I check Device Manager and the Android setting shows up so I see it has the "ADB Bootloader Interface" as the driver. Kinda weird since I thought I used "ADB Composite Interface" last time. But my Nexus must be showing up at least in the drivers. So essentially, here's the compounded issues.
1. Bootloop
2. Can't boot so no USB debugging is checked
3 .Can't flash a stock image if device doesn't show up on computer for fastboot stuff.
4. Drivers are all messed up. I got them directly from google too.
5. ****.
I think I'm screwed on this unless I can somehow enable USB debugging from fastboot without the device itself being recognized, or something. Pls help.
My dad thinks i'm a failure now.
You don't need USB debugging for fastboot. It might be a driver issue if fastboot doesn't see it. Maybe try installing them again.
Sent from my Nexus 5 using XDA Premium App
Download some program to wipe all android drivers from the system. Restart the computer. Boot the device to bootloader. Connect the device to the PC. Go to device manager. Manually update those drivers. The drivers are the same for fastboot or adb, it's just that you need to feed Windows the same drivers twice: one when device is in bootloader, another when the device has adbd (adb daemon/server) running. Adbd doesn't run when the device is in bootloader - it's an Android thing.
a maguro wrote this.
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
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 >
Greetings, everyone!
Okay so a few days ago I fell asleep while using my phone, a Moto G 2014 (XT1068). At one point I wake up to see a window saying something along the lines of 'Updating X of X Apps" on a black screen. I put my phone on my bedside table and fall asleep again. When I wake up, the phone's off so I assumed it was done doing whatever it was doing (which I now think it was some sort of system update), so I turn it on only to find out it gets stuck in the Motorola logo loading screen. I've left it like that for maybe an hour and it's just stuck there. I've accessed Fastboot to try the Recovery option but it just returns a 'Boot Up Failed' message and if I choose the 'Factory' option (which I assume is a factory reset), it also gets stuck in the Motorola logo loading screen. The other options are 'Normal PowerUp', 'Barcodes' & 'BP Tools', none of them doing anything either. Upon some research, I figured it was probably some sort of update that crashed down the whole thing and that apparently a way to solve this would be to flash the phone with the Stock ROM, which I've already acquired (and hopefully it's the right one). Now, thing is, I need to connect my phone to the computer, which is running Windows 10, while on the Fastboot menu. This is where the problem comes in. I never enabled USB Debugging in the settings. I've also installed the Motorola Device Manager from the Motorola website because apparently it installs the drivers for the phone, but after installing the MDM countless times, I just don't see drivers anywhere. I've checked the Device Manager on Windows and there's no track of my phone's drivers in there whatsoever. There's no 'Other Devices' tab anywhere and my PC doesn't do that "device was plugged in" sound effect when you connect something through USB. I've downloaded ADB Drivers and different versions of Motorola Drivers but nothing seems to work. I've tried 6 different cables in 10 different ports, still nothing. The phone charges but it's like the PC doesn't detect it. While on the Fastboot menu, according to a few videos I've watched, it is also supposed to say a USB Cable is connected when you connect the phone to the computer, but even though my phone is connected to my PC, that never shows up. I don't know if this is because the drivers might not be installing on my computer or if it's because I never enabled USB Debugging in the settings. I've seen some people say it doesn't need to be enabled while in Fastboot but I don't know if that's true or not. So I'm pretty much out of ideas at this point, do you think something might be done?
Thank you in advance,
- Nervly
Hello, did you try typing in `fastboot devices` while in fastboot ?
-Hope- said:
Hello, did you try typing in `fastboot devices` while in fastboot ?
Click to expand...
Click to collapse
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Nervly said:
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Click to expand...
Click to collapse
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
<link>
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
I'm off to a job interview right now but I will try the disabling drivers signature method you suggested once I get back.
As for the device manager, showing hidden drivers still doesn't list the phone's drivers or the 'Other Devices' tab, sadly. Perhaps after I disable the drivers signature enforcement and try to install the phone's drivers again it will work. I'll keep you updated!
Thank you for the help thus far!
-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Nervly said:
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Click to expand...
Click to collapse
Fastboot drivers aren't same as USB drivers
They differ so if you want to work with fastboot you need fastboot drivers
Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)