Related
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.
I have the tmobile lg v10 h901. I'm trying to unlock the boot loader. I have adb and fastboot files installed and the lg drivers. I have the oem. Unlock and usb debugging checked in the setting. I can open the command prompt and use adb devices and it sees my device. I can use adb reboot bootloader and it will take me to the fastboot bootloader unlock screen. From here the command prompt no longer sees my device. I type fastboot oem Unlock and it says waiting on device... Any one have a idea what's going on. Am I missing something?
Try booting into fastboot manually by turning off the phone and holding vol down while plugging it in,then try it but make sure you fastboot devices first to make sure its even detecting it
No that didn't work. When the phone is on adb devices it sees the phone I type fastboot devices and it does nothing. But when the phone goes to fastboot even volume down then plug the phone In it won't recognize the phone just says <waiting on device>
Yeah I keep uninstalling everything and reinstall everything fast boot threw cmd fastboot with the volume button and always get waiting on device when I get to the "fastboot oem Unlock"
So sad ...
Use nexus toolkit for it all. I did. Works great.
Exconvict said:
Use nexus toolkit for it all. I did. Works great.
Click to expand...
Click to collapse
Wugs nexus toolkit ? That will work with the v10?
cwalton4077 said:
Wugs nexus toolkit ? That will work with the v10?
Click to expand...
Click to collapse
I used Mfastboot and it worked like a champ. Could not get nexus toolkit to see my device.
Yes. It boots temp recovery,flashes recovery and root. Also used it to relock the boot loader for sh*ts and giggles. To get it to see my phone I had to download LG bridge on my computer and run it.
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
If you run Windows, you may be missing the USB driver for fastboot. If possible, use Linux where all the USB drivers are included from the start.
I'm having the same problem as well.
cwalton4077 said:
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
Click to expand...
Click to collapse
When starting all of this (essentially becoming addicted to learning rooting) I noticed that no one mentioned to make sure to enable the "usb tethering" option on their device!! Once I did that, an entire plethora of additional options opened up. That being said, this option won't necessarily make rooting possible, but I think it may help out in this particular situation.
? I really hope this works for you.
1500 years ago, everybody "knew" that the earth was the center of the universe. 500 years ago, everybody "knew" that the earth was flat. And 15 minutes ago, you "knew" that humans were alone on this planet. Imagine what you'll "know" tomorrow.
-Kay
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Glad you got it rooted
Great!
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Now can you post a YouTube vid for us who are still having this issue! ?
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 "
Hi all,
I'm here because i don't know where else to look..
I've got a nexus 9 tablet running 5.1.1, its rooted with an unlocked bootloader, running twrp custom recovery, i was trying to flash a new rom, now all i get is a constant google logo upon bootup, I can enter recovery and fastboot and all of that, but none of my computers can see the tablet in adb or fastboot when I plug it in via usb, so Im not able to flash anything from my computer, does anyone have any ideas? or have I totally ****ed my nexus 9?
I have 2 laptops running Ubuntu, and my desktop is Windows 7 with all the necessary drivers, I've never had issues connecting my devices in the past, so I'm kinda at a loss.
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
kacang87 said:
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I have tried to do that, factory reset just resulted in no change to the tablet
corkiejp said:
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
Click to expand...
Click to collapse
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Baskinmfr said:
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Click to expand...
Click to collapse
change your cable connect to computer..some cable cannot sent data..happen to me
Sent from my Nexus 9 using Tapatalk
Can you enter recovery? If you can then use your computer to copy the zip file of a rom and install it. Otherwise check your cable, I had problems with the one htc gave me.