Super noob here, need help with adb - Honor 9 Lite Questions & Answers

I installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??

What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.

Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)

Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.

It finally worked, thanks a lot brother :laugh:

Related

[Q] adb "waiting for device"

I spent a good part of the day reading through all the steps to get my new device (just arrived, 4.4) rooted. I've had several rooted devices before, but always used tools to do it.
Never used adb before, but managed to get the SDK installed and have been playing around with it. That's as far as I got, however.
On my mac, using terminal, I can get adb to see my device (type ./adb devices and it lists it as connected).
When I go through this guide
http://forum.xda-developers.com/showthread.php?t=2446515
to do any fastboot commands, I always get "waiting for device." Previously I got some kind of pipe error. Yes, usb debugging is on.
I think I'm pretty close to getting flashed down to 4.2.2, just can't get the adb to work.
tl;dr - adb gives me "waiting for device" forever. any ideas how to fix?
Thanks very much!
motoxuser said:
I spent a good part of the day reading through all the steps to get my new device (just arrived, 4.4) rooted. I've had several rooted devices before, but always used tools to do it.
Never used adb before, but managed to get the SDK installed and have been playing around with it. That's as far as I got, however.
On my mac, using terminal, I can get adb to see my device (type ./adb devices and it lists it as connected).
When I go through this guide
http://forum.xda-developers.com/showthread.php?t=2446515
to do any fastboot commands, I always get "waiting for device." Previously I got some kind of pipe error. Yes, usb debugging is on.
I think I'm pretty close to getting flashed down to 4.2.2, just can't get the adb to work.
tl;dr - adb gives me "waiting for device" forever. any ideas how to fix?
Thanks very much!
Click to expand...
Click to collapse
if your phone is turned on when it is connected to the computer then you can't run fastboot commands. you can only run adb commands. If your phone is in "fastboot mode" / bootloader screen, then you can run fastboot commands but not adb commands. Not sure this is your issue but based on your info it is my best guess at where you are having problems.
jayboyyyy said:
if your phone is turned on when it is connected to the computer then you can't run fastboot commands. you can only run adb commands. If your phone is in "fastboot mode" / bootloader screen, then you can run fastboot commands but not adb commands. Not sure this is your issue but based on your info it is my best guess at where you are having problems.
Click to expand...
Click to collapse
that sounds about right! thanks!
how do I get the phone into fastboot mode/bootloader screen? or better yet, when i'm doing this whole process, in what mode should the phone be and how do I get it there?
motoxuser said:
that sounds about right! thanks!
how do I get the phone into fastboot mode/bootloader screen? or better yet, when i'm doing this whole process, in what mode should the phone be and how do I get it there?
Click to expand...
Click to collapse
adb reboot bootloader in terminal
you can you my tool kits to help you.
http://forum.xda-developers.com/showthread.php?t=2591875
mjphillips1981 said:
adb reboot bootloader in terminal
you can you my tool kits to help you.
http://forum.xda-developers.com/showthread.php?t=2591875
Click to expand...
Click to collapse
great! I'll do that - actually, I just sent you a PM - i'm trying to work my way through the mac tool now and got stuck. appreciate it!

[Q] Bootloader Troubles

Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html

Motorola Droid Turbo Fastboot Issue

Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
ChazzMatt said:
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
Click to expand...
Click to collapse
Thanks man. Will try this method too.
ahm259 said:
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
Click to expand...
Click to collapse
Have you tried just connecting to your pc, enable 'Transfer Files'/mtp mode, and using PhotoRec to scan it as attached storage? The video should not have been anywhere you would need root to access, so this should work. I personally haven't used PhotoRec on a phone in several years, but in the past it worked great. It's free software from CGSecurity (often bundled with TesDisk).
http://www.cgsecurity.org/wiki/Phot...data_from_my_phone.2Fdisk.2Fusb_key.2F..._.3F
Just remember, everytime you use the device you risk rendering the video totally unrecoverable. At best you'll get the whole thing back. More than likely if you're lucky, you'll only get part of it and it will be enough that video software can recognize and play what's left. (based on my own experience). It just depends on how large the video was (data-wise) and how many blocks were overwritten by other data.

A guide for flashing TWRP?

I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
1xcalibur1 said:
I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
Click to expand...
Click to collapse
First, you need your bootloader to be unlocked. It's pretty easy if you have that done already.
You'll need ADB and Fastboot. It can be tricky to get the right drivers. The driver used when your phone is connected in normal mode is not the same when connected in fastboot mode, in my experience anyway. You'll want the 15sec ADB driver and you'll need to update the driver when it is in fastboot mode.
Next, get the correct twrp img and put it in the ADB folder(you'll need a different one based on flashing a pie rom or a q rom). You may want to rename it so it's easier to type in fastboot.
To enter fastboot mode, hold volume up and plug in the usb cable. The LED should light up blue.
Open a command prompt and navigate to wherever you've installed ADB(mine is on C:\ so it's really easy).
Type "fastboot devices" to double check if the driver is installed and your phone is connected in fastboot mode.
------It should show something like: BH9090808E fastboot
Then type "fastboot flash recovery twrp.img" - or whatever you've named the file. It will take less than a few seconds.
Then type "fastboot reboot" and let your phone reboot.
Done
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
1xcalibur1 said:
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
Click to expand...
Click to collapse
My apologies. It's been so long since I've started from scratch, I must've gotten the drivers mixed up. The 15sec ADB is for the phone connected in normal mode.
I'm pretty sure this one is the fastboot one:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If not, I'm sorry because that's all I have.
I nailed it eventually!
For anyone that comes across this thread,
this video will solve all your problems with adb drivers:

Question [Resolved] No connection with pc in fastboot mode.

Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!

Categories

Resources