Hello.
I own a Moto G (Global GSM) running CyanogenMod 11 rooted with TWRP recovery and the bootloader is unlocked. I have been trying to go back to the stock firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2542219 but I have a problem. The adb drivers for my device work fine when I am in the system or in the recovery, but don't work in the bootloader. I am able to type "adb reboot bootloader" when I'm in the system/recovery and it will follow the command, but once I get into the bootloader it stops. When I type "adb devices" a line saying "List of devices attached" comes up with nothing underneath it.
I am completely lost and would greatly appreciate any help. Also I am new to XDA.
Thank you
derekokelly said:
Hello.
I own a Moto G (GSM) running CyanogenMod 11 rooted with TWRP recovery and the bootloader is unlocked. I have been trying to go back to the stock firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2542219 but I have a problem. The adb drivers for my device work fine when I am in the system or in the recovery, but don't work in the bootloader. I am able to type "adb reboot bootloader" when I'm in the system/recovery and it will follow the command, but once I get into the bootloader it stops. When I type "adb devices" a line saying "List of devices attached" comes up with nothing underneath it.
I am completely lost and would greatly appreciate any help. Also I am new to XDA.
Thank you
Click to expand...
Click to collapse
When you are in bootloader you have to use fastboot. Type 'fastboot devices' and you'll see the connected device. Refer this guide "[Guide] How To Setup And Use Fastboot" for more info: http://forum.xda-developers.com/showthread.php?t=2277112
***********************************************************************************************************************************************************************
Hit the "Thanks" button if you think I helped!
Type 'fastboot devices' and you'll see the connected device.
Click to expand...
Click to collapse
When I do this, a blank line comes up underneath "List of devices attached". I don't know what I'm doing wrong.
derekokelly said:
When I do this, a blank line comes up underneath "List of devices attached". I don't know what I'm doing wrong.
Click to expand...
Click to collapse
Have you enabled 'USB Debugging' in Settings and allowed your computer to access it?
PhaseBeta said:
Have you enabled 'USB Debugging' in Settings and allowed your computer to access it?
Click to expand...
Click to collapse
Yes, I did. It has something to do with the ROM that I was on. For some reason, it won't recognise my device anymore, no matter what ROM I use. It doesn't really bother me though, there's plenty of ways to do things nowadays.
USB Debugging nor the rom have anything to do with fastboot.
Are you using a Windows PC? If so, when in bootloader mode, check your Device Manager and see if the driver is loading correctly. If it isn't, it'll have a yellow exclamation symbol next to it. If that's the case, you'll just need to manually load the driver from there.
Related
bluepojo's post
For those who are having the same issue:
Turns out on Ubuntu, you need root permissions. Run the commands with sudo and all is well.
Click to expand...
Click to collapse
I'm using Windows cmd with adb and fastboot do my work. My device is an ideaUSA CT702 - MID A777 running a rooted 4.0.3 ICS. adb devices shows my device id under "List of Devices", but fastboot devices command shows nothing during normal boot. After booting into bootloader, which is a completely black screen (is this a problem, or is it ok because all devices are different. This forum post says it's ok to have a blank screen google this: I can't post links: forum.geeksphone.com/index.php?topic=1830.0). The forum also says it's ok to have this show up after typing fastboot devices in bootloader mode "? fastboot", which is exactly what I have.
However, the forum also says that there should be a string after this, and most other forums I've seen say that you should get your device ID. Did I do anything wrong?
Hi,
I'm trying to unlock my Huawei Ascend Y300 but I'm stuck in fastboot.
I followed this guide: (not allowed to post outside links but you can find the guide by looking for "Free Huawei bootloader unlock tutorial"), but got my unlock code sent from Huawei by mail since the dc-unlocker tool didn't work as well (probably the same problem as with fastboot).
When the phone is turned on I can see it with "adb devices" but once I'm in fastboot mode (pink screen) no device can be found with "fastboot devices".
When the phone is in fastboot mode and being plugged into the computer it is recognized by Windows.
I tried two kinds of Huawei Drivers: "Huawei_U8680_U8730_U8800_U8860" and "Huawei_Android_driver" (for the last one: see the guide stated above). I also tried three different computers.
I'm using Windows 7 64bit if that helps.
Edit:
Same problem in Ubuntu, found in "adb devices" but not in fastboot mode.
Any idea anyone?
Thanks,
Patrick
Anybody?
SirBelial said:
Anybody?
Click to expand...
Click to collapse
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Maurice5813 said:
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Click to expand...
Click to collapse
SirBelial said:
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Click to expand...
Click to collapse
does you phone have a bootloader?
Maurice5813 said:
does you phone have a bootloader?
Click to expand...
Click to collapse
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
SirBelial said:
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
Click to expand...
Click to collapse
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Maurice5813 said:
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Click to expand...
Click to collapse
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
SirBelial said:
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
Click to expand...
Click to collapse
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Maurice5813 said:
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Click to expand...
Click to collapse
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Enable USB Debugging
SirBelial said:
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Click to expand...
Click to collapse
I encountered this but then started the phone and enabled USB debugging and it then found the phone.
did u get this going? im having exactly the same issue. cannot get the phone detected in fastboot, either in Linux or windows
I had the same issue. Took my hours, different Systems, Cables... Try the following:
Code:
adb reboot-bootloader
.
Hope this helps! Your phone should stay at the Huawei Logo (no pink screen!)
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "
I unlocked the bootloader and went to root. on the first reboot after rooting it's stuck on the boot animation. When i plug the device into my PC and use the cmd prompt "adb devices" it won't see it. I help the power button and vol down to get to fastboot and my pc still won't see it. i've tried to factory reset though fast boot, says erasing, then reboots and still stuck. I updated everything in adb and still nothing. Everything went fine with unlocking the bootloader, but rooting it totally messed something up.
I can't seem to figure out how to get my PC to see this thing again. It's kind of a crap tablet to begin with, and now i brick it? totally frustrated.
Thanks
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Sent from my Nexus 9 using Tapatalk
Adb can do almost nothing when your device is in fastboot mode. Use fastboot to see if your device is connected to your computer if you didn't do so.
try "fastboot devices".
corkiejp said:
try "fastboot devices".
Click to expand...
Click to collapse
I just got "waiting for any device". I have the path set up to "C:\android-sdk\tools;C:\android-sdk\platform-tools". I haven't changed anything since i unlocked the bootloader so i'm just confused.
kacang87 said:
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Click to expand...
Click to collapse
The safely removed hardware icon does show up in the task bar. When i got to printers and devices there is an "android".
https://www.dropbox.com/s/a5chez6r9cuxjzo/Capture.JPG?dl=0
Can i use that port to force adb to see it? Not sure if this helps
gotta run to work, i'll mess with it this afternoon. Thanks guys.
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
corkiejp said:
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
Click to expand...
Click to collapse
I tried uninstalling the drivers from device manager and that didn't seem to do it. I went into the sdk and deleted them from the sdk then reinstalled them through the sdk and that seemed to work. I feel like i should have thought of that! duh. flashing CM13 now! hope i can get this to work haha jeeze.
thanks for the help guys
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
There are call recording apps on playstore. Along with the rooting is so simple I did it the same day I got my v10 T-Mobile variant
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
First things first, you don't need root to record your phone calls. Like Wadamean said, there are call recording apps in the play store. I personally use "Call Recorder ACR", but you can use whatever you prefer. Most call recorders won't require root access.
As for rooting, if you type the adb command and it says that it's waiting for your device, the most likely cause is that you do not have the proper drivers installed on your computer. An easy way to check this would be to type the command "adb devices" and make sure that your V10 appears under "List of devices attached". If you don't see your h901 device listed, your computer doesn't know that the V10 is connected, and it'll be difficult for your computer to issue commands to a device it can't see
Follow each step in this guide. That doesn't mean click this link, skip to the downloads, and then proceed to root like you've always done. It means click this link, READ THE POST, then once you have finished reading it, read it again to make sure you didn't miss anything. It will guide you through setting up adb with a universal driver. It will also guide you through doing things like enabling USB Debugging, which is required for issuing adb commands.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
If you are still having issues after reading this guide and FOLLOWING THE INSTRUCTIONS, post there to let them know where you're getting stuck at and someone will help you out.
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
dillonorden said:
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
Click to expand...
Click to collapse
No worries, that's why we're here :good:
If you can see your V10 listed on the ADB devices list, then something else is up. Make sure that USB Debugging and OEM Unlock are checked in Developer Options... What command are you getting stuck at?
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
dillonorden said:
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
Click to expand...
Click to collapse
Ahh, sounds like you aren't in fastboot mode. Make sure that your USB connection type is set to PTP rather than MTP or charge only. Before you issue ANY other adb commands, run "adb devices" and make sure that you see your v10. It should read something like this:
List of devices attached
LGH901blahblah device
Click to expand...
Click to collapse
See it on the list? Good. You should be able to run "adb reboot bootloader". At this stage, your phone should reboot to a mostly dark screen. Once in the bootloader, you should be able to run "fastboot oem unlock". Be forewarned that it can take a few minutes. If you see "waiting on device," you're either not in the right mode (your phone won't acknowledge fastboot commands if it's not in Bootloader mode) or the drivers on your computer are screwy and need to be reinstalled. If you can issue adb commands but not fastboot ones, you probably need additional drivers - more info here: http://android.stackexchange.com/questions/46142/fastboot-doesnt-see-device
This should get you started in the right direction, feel free to PM or post in the guide if you're still having trouble. :good:
ok so i followed the guide, reinstalled the LG drivers. and re setup the ADB system wide. I put my phone in usb ptp and ran command ADB devices. It listed my device, so i ran the ADB reboot bootloader and it rebooted. the screen i get is the LG boot screen but in the top left corner it shows fastboot mode and list the commands to unlock the bootloader. I run command fastboot oem unlock and I get the same waiting on device and waited an hour and got nothing. I even tried unplugging it restarting command prompt held the vol down button when i plugged my device back in to make it boot into FASTBOOT mode. i run the command fastboot oem unlock and still get nothing.
What am I doing wrong? I follow the guide to the very T and still get nothing. Could I possibly get someone to make a file with everything done and flash it using Odin? Im not new to this and dont understand why this V10 H901 is giving me so much trouble. Ive rooted a Motorola OG droid, Droid 2, Bionic, Samsung Note 2, 3 and Grand Prime and never had this much trouble. I really enjoy having root privileges but this is getting ridiculous but I also refuse to give up. If anyone can help me I would much appreciate it. Also Thanks to the ones who have tried helping me so far, this is why I enjoy XDA so much
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
dillonorden said:
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
Click to expand...
Click to collapse
Are you the administrator of the pc? What OS are you using?
I am administrator and im using windows 7 so i dont see where im having an issue at