Related
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
rvrzl said:
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
Click to expand...
Click to collapse
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
clsA said:
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
Click to expand...
Click to collapse
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
rvrzl said:
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
Click to expand...
Click to collapse
Install the drivers included in the All in one kit or install HTC sync (not recommended)
Sent from my TouchPad using xda app-developers app
[RESOLVED!]
For anyone else who might be having this problem
1. I was finally able to resolve this by downloading the archive provided by Esau Silva, which (I'm assuming) had updated versions of adb, and fastboot for Mac/OSX: http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx
2. I booted to the bootloader (power + volume down for 10 seconds), went to the Fastboot option, then plugged my phone into my Macbook; enabling Fastboot USB.
3. I opened terminal, CD'd into the directory containing adb/fastboot, and then ran "./fastboot devices" to see if it recognized my device. Sure enough, with Fastboot USB on and the updated adb, it recognized the device.
4. Then I ran "./fastboot erase cache" which allowed me to boot back into the bootload, and then properly boot into recovery, finally seeing ClockworkMod Recovery again.
5. From CWMR I erased the cache again, erased the dalvik cache, and then did a full wipe/factory reset.
6. Then I booted back into CWMR once again, and chose sideload. Then back on my Macbook I was able to run "./adb devices" to make sure adb could see my HTC One. Once I confirmed it could see it, I ran "./adb sideload nameofrom.zip"
After the sideload was complete, I was back up and running.
Big thanks to clsA who got me Googling fastboot a bit more. Hopefully this helps someone else!
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!)
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.
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
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 "