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!)
Related
I've already unlocked the bootloader and am about to flash cwd but my computer won't recognize the phone in the bootloader while plugged into USB. So when I try to enter the command "fastboot flash recovery <recovery.img>", the command prompt comes back with an error. I bet I'm missing something simple here, but it's getting pretty frustrating.
I have the HTC drivers installed and I'm using bootcamp, if that matters.
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
jonesin said:
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
Click to expand...
Click to collapse
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
feperlman51 said:
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
Click to expand...
Click to collapse
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
jonesin said:
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
Click to expand...
Click to collapse
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
feperlman51 said:
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
Click to expand...
Click to collapse
"just ran the "fastboot flash recovery" command again"
Lol thats what I said man! Glad it worked! CWM and TWRP should both work, I bet a nickel to a dime you werent actually in fastboot mode the first time! anyway happy flashing! Get comfortable with ADB and Fastboot because they will be our primary utilities for the foreseeable future!
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
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.
Hello, I have a problem, I can not use the fastboot because he can not find my phone and i get nothing with "fastboot devices" but adb work and i'm on windows 10 x64.
My devices : i.imgur.com/nPqGZDT.png
Same problem with nexus 4
You have to install the ADB drivers first: http://forum.xda-developers.com/showthread.php?t=2588979
Sangmort said:
Hello, I have a problem, I can not use the fastboot because he can not find my phone and i get nothing with "fastboot devices" but adb work and i'm on windows 10 x64.
My devices : i.imgur.com/nPqGZDT.png
Click to expand...
Click to collapse
Probably you need to go to "Settings" -> "Developer Options" and check the "Enable OEM Unlock"
Sangmort said:
Hello, I have a problem, I can not use the fastboot because he can not find my phone and i get nothing with "fastboot devices" but adb work and i'm on windows 10 x64.
My devices : i.imgur.com/nPqGZDT.png
Click to expand...
Click to collapse
I had that same problem. ADB fine but no Fastboot. I tried a different cable and all worked well. Seemed odd so I put the original cable back on and lost Fastboot. Worth a try if you haven't.
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 "