hello every one plyze i need help every time i trying to root my ze500kl it said only waitting for device and do nothing
Mohamed elkholy said:
hello every one plyze i need help every time i trying to root my ze500kl it said only waitting for device and do nothing
Click to expand...
Click to collapse
It's probably a problem with drivers. It's common in Windows. Search in the forum for these keywords: ADB Windows driver problems
I resolved using a Linux distro (Debian Sid, but Ubuntu is OK and more friendly too), no problems with drivers anymore.
but when i type adb device i found my device but when
he enter to the fastboot mode it said waiting for device
do you can help me please how do you have fixed it
mohamedelkholy said:
but when i type adb device i found my device but when
he enter to the fastboot mode it said waiting for device
do you can help me please how do you have fixed it
Click to expand...
Click to collapse
Do you run the command prompt as Administrator (right clic on the Command Prompt icon > Run as Administrator)?
Do you run fastboot devices before to check if the phone is recognized by fastboot?
i have run the cmd as an admiristratore but how to reconized it
mohamedelkholy said:
i have run the cmd as an admiristratore but how to reconized it
Click to expand...
Click to collapse
with the command:
Code:
fastboot devices
if the phone is recognized, it should respond with
Code:
random123 fastboot
if nothing happens, you have to check your adb drivers (uninstall and reinstall for example).
Related
Computer stuck dead while running "15 seconds ADB Installer"
For the purpose of flash new recovery to my Nexus s ,I searched and used the tollkit from
http://forum.xda-developers.com/showthread.php?t=2588979
And when I CmD the command line
fastboot flash recovery recovery.img
My computer stuck to dead! Though,fortunately the phone weren't bricked at that moment.
1 ,And where did u guys get the proper functional revision of fastboot.exe and adb.exe?
2, Does the "15 seconds ADB Installer" contain some torjan? (as u know it made PC dead)
BTW my phone is nexus s
faraway001 said:
Computer stuck dead while running "15 seconds ADB Installer"
For the purpose of flash new recovery to my Nexus s ,I searched and used the tollkit from
http://forum.xda-developers.com/showthread.php?t=2588979
And when I CmD the command line
fastboot flash recovery recovery.img
My computer stuck to dead! Though,fortunately the phone weren't bricked at that moment.
1 ,And where did u guys get the proper functional revision of fastboot.exe and adb.exe?
2, Does the "15 seconds ADB Installer" contain some torjan? (as u know it made PC dead)
BTW my phone is nexus s
Click to expand...
Click to collapse
This the best and the easiest guide to install adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2141817
In my opinion, it is always good to type commands and manually setup everything than using 1-click installers. This helps in debugging and avoiding issues.
Probably your PC needs a Startup repair. Start it and press F8 continuously to get repair options. Let me know how it goes.
smit.sanghavi said:
This the best and the easiest guide to install adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2141817
In my opinion, it is always good to type commands and manually setup everything than using 1-click installers. This helps in debugging and avoiding issues.
Probably your PC needs a Startup repair. Start it and press F8 continuously to get repair options. Let me know how it goes.
Click to expand...
Click to collapse
Hey I am back...
As for your reply ,thanks but what I wanna say is the first,my PC has purely good configured and not any system deformity.
And I haven't found any working adb.exe/fastboot.exe version before I one day surfed a board and droped with a working bundle.
The bunldle included adb and fastboot which had the different md5 from the ones in "15 seconds ADB Installer".
*15 sec
81d188a849c8768e8f3694eb1c0e6086 adb.exe 800k
2782d10e7d3370cfefbadae0e8eaaa35 fastboot.exe 157K
**working version
8ae827f316e4fd4500c8d5b2845bcbe9 adb.exe 2400k
6bbf05d97585c3c515bdb172eb9e7d12 fastboot.exe 969 K
What's the difference between the "15 sec" and the working version. Weren't they coming from the same Google adt-bundle？
Or has somebody compiled the origin fastboot.exe and twisted it in order to make it work straight out there.
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results. Different USB cable/port?
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
dextroamphetamine said:
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
Click to expand...
Click to collapse
cmstlist said:
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Click to expand...
Click to collapse
Correct.
cmstlist said:
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results.
Click to expand...
Click to collapse
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
cmstlist said:
Different USB cable/port?
Click to expand...
Click to collapse
Tried every cable and port I have. Different computers even.
cmstlist said:
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
Click to expand...
Click to collapse
NONE of the fastboot commands work except "fastboot devices"
dextroamphetamine said:
Correct.
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
Click to expand...
Click to collapse
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
cmstlist said:
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
Click to expand...
Click to collapse
Got any sources on that info?
WOW
weird! really weird!
I really don't know what the issue, the fact that it happens on Linux and on Windows makes me think to an hardware realted issue, unfortunately..
As long as I know adb and fastboot do not use exactly the same drivers, but you download and install them together, so it should n not be a problem, this one..
The only think I can suggest you atm is to try with Linux by logging in as superuser (su). On my slackware with my "normal" user adb works as usual, but if I try to use fastboot the terminal says me No permissions..
I hope someway your distro has the same issue, even if your fastboot devices success!
So login as superuser and try to use fastboot. If you do not install it in /bin partition you should have to locate its directory and then use
./fastboot devices
or any other command but with ./fastboot instead of fastboot..
hope it helps.. I really hope!!
For that matter, on a whim... when you open a command prompt in Windows to adb to your device, try running Command Prompt as an Administrator. Sometimes Windows is weird like that.
Please keep questions in the Q&A section. Development sections are for development only.
Thread moved to Q&A.
Thanks,
Darth
Forum Moderator
Dear all,
1st sorry for my horrible English
Guys I am having issue while unlocking the bootloader.
I have installed adb driver for my LG G5 H850 it works on adb command "adb devices" its show me the my phone also the phone in device manger like "LGE Mobile ADB Interface".
But after restarting the cell phone into fastboot mode system show device in device manger as "Kedacom USB device=>Android Bootloader Interface" while on "fastboot devices" command system dose not show anything and on "fastboot oem device-id" command system show <waiting for device>. :crying:
Please help me thanks in advance!!!!!
Try installing LG suite so you have the drivers. Tip: Fastboot didn't worked for me on Windows, I switched to Linux with no problem. You have to use sudo Fastboot on Linux.
einhuman197 said:
Try installing LG suite so you have the drivers. Tip: Fastboot didn't worked for me on Windows, I switched to Linux with no problem. You have to use sudo Fastboot on Linux.
Click to expand...
Click to collapse
May I add to his? If you don't wanna install linux use Ubuntu live disc
Sent from my LG G5 using XDA Labs
Install drivers from lg site
Hi, i was playing with my yota2 and think i messed up the radio files, now the phone is dead, no vibration no screen light, nothing.
i tried some methods and was able to get the phone recognized as 'Qualcomm HS-USB QDLoader 9008' but dont know what to do. btw i opened up the phone, is there anyway to revive it or should i just order another one?
Thanks alot
Try flashing it with yotaflasher. Post any errors if they occur.
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
yotafree said:
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
Click to expand...
Click to collapse
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
i had a hardbrick yotaphone2 also. only qualcomm 9008 detected. had tried all the way to flash it back due to wrong rom being flashed. please advice....no fastboot, tried power off and volume down, tried kick out from EDL mode...tried qualcomm flasher which support EDL flashing but downloaded rom cannot flash due to only img and bin file, there is no rawprogram xml file.....anybody have dumped rom for this phone?
Thank you but did you forget to add the link which command to run ??
Parmo100 said:
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
Click to expand...
Click to collapse
Thank you but did you forget to add the link which command to run ??
My redmi 3s prime is not detected by command prompt, in Fastboot mode. Any solution
Ushubh Singh said:
My redmi 3s prime is not detected by command prompt, in Fastboot mode. Any solution
Click to expand...
Click to collapse
Install proper drivers and check. Always open command prompt in adb folder for successful recognition of fastboot devices.
william.johhn7! said:
Install proper drivers and check. Always open command prompt in adb folder for successful recognition of fastboot devices.
Click to expand...
Click to collapse
Ya I try all ways but still not recognized
Ushubh Singh said:
Ya I try all ways but still not recognized
Click to expand...
Click to collapse
Try Asus drivers. They're basically universal. Make sure you install adb files.
william.johhn7! said:
Try Asus drivers. They're basically universal. Make sure you install adb files.
Click to expand...
Click to collapse
Kk, can u send me Asus driver link. If possible
Ushubh Singh said:
Kk, can u send me Asus driver link. If possible
Click to expand...
Click to collapse
Sorry. I don't remember from where I downloaded it. You could give it a try by googling it.
william.johhn7! said:
Sorry. I don't remember from where I downloaded it. You could give it a try by googling it.
Click to expand...
Click to collapse
Kk thnx... Bro
Step 1:-
Open CMD and type fastboot if it says not a internal/external command then u need to flash drivers. If many texts appears like fastboot commands etc then follow next step
Step 2:-
Connect your phone in fastboot to your computer
Right click my pc go to device manager then you can see Android with (!) Mark then double click update drivers choose manually then again set to android:> Android bootloader interface and done