Related
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!
Please for the love of god help me. I've tried everything.
I have a developer edition. I have the newest drivers, the newest phone updates. Everything. It is recognized by ADB when I'm on the home screen, but when I am in fastboot mode itself it will not recognize the device. I can't unlock the BL because of this. It's VERY frustrating and I'm about 12 hours from selling this device and buying an HTC M8.
I have Windows 7 64 bit. I'm on the newest moto drivers, the newest FW for the X. I've uninstalled and re-installed and restarted my machine countless times. With no luck. With the drivers installed I booted the phone into fastboot mode, pulled up a command prompt where ADB was installed, ran adb devices and nothing. Over and over again. Please help me. I really want to keep this phone.
Navigate to where fastboot.exe is installed, and run "fastboot devices".
And make sure phone is in bootloader mode.
Does it list serial number?
I ran into the same issue last night, I just got a moto x DE for my wife, and a new laptop since last March when I unlocked my moto x DE. "adb devices" returned nothing, and I had a fresh install of the SDK and the moto drivers. Both old and new laptop on Win 7 64-bit. I googled trying to find a solution, but didn't find anything that worked. Grabbed my old laptop, hooked up to it, and it worked fine.
One suggestion I saw and didn't try was to remove/reload the moto drivers. Since I got it working and got her phone unlocked with my old laptop, I didn't pursue further.
Nitemare15 said:
....With the drivers installed I booted the phone into fastboot mode, pulled up a command prompt where ADB was installed, ran adb devices and nothing. Over and over again. Please help me. I really want to keep this phone.
Click to expand...
Click to collapse
Adb devices wont work when the phone is in Booloader/fastboot mode.
Make sure you have the latest Moto drivers from here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Follow this -> http://mark.cdmaforums.com/ADB.htm To install The Android SDK, PlatformTools, and mFastboot, and add platform tools to the Path.
once that is done.. type fasboot devices and see if you get anything. If no, look at Device Manager and make sure there are no ! or such in there.
This is what worked for me. Posting here for posterity and potential helpfulness.
yghrv said:
I hit the issue earlier and fixed it with the steps. hope will help you too.
1. connect your phone with computer
2. go to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\
3. run Motorola Driver Installer.exe, choose clean and Reinstall.
Click to expand...
Click to collapse
31337z3r0 said:
This is what worked for me. Posting here for posterity and potential helpfulness.
Click to expand...
Click to collapse
Even that wouldn't help him if he was trying to use adb while in the bootloader.
KidJoe said:
Adb devices wont work when the phone is in Booloader/fastboot mode.
Make sure you have the latest Moto drivers from here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Follow this -> http://mark.cdmaforums.com/ADB.htm To install The Android SDK, PlatformTools, and mFastboot, and add platform tools to the Path.
once that is done.. type fasboot devices and see if you get anything. If no, look at Device Manager and make sure there are no ! or such in there.
Click to expand...
Click to collapse
Thanks for clarifying. I only end up dealing with rooting something once a year or so and always forget the "ins-outs-and-what-have-yous". Once I was reminded of fastboot vs. adb all was well!
31337z3r0 said:
This is what worked for me. Posting here for posterity and potential helpfulness.
Click to expand...
Click to collapse
Thank you very much, that did the trick for me !
Hello there, after an hour of search and no useful results, i've decided to ask my question (sorry, if it's already been answered, but i didn't find anything)
I used the following procedure to flash the CWM recovery, but something goes wrong:
( http://forum.xda-developers.com/android/development/ufficial-thread-lenovo-k3-note-t3102997 )
1. "adb devices" shows the phone correctly (At this state the phone is properly shown in my windows device manager)
2. "adb reboot bootloader" pushes the phone to boot in fastboot mode
... but ...
3 "fastboot devices" doesn't find it anymore. (At this state the phone is shown as an unknown device in my windows device manager)
4. after some attempts I tried "fastboot flash recovery recovery.img" anyway, but as I expected, i was unable to reach the device, the image should be written to.
5. every the phone stucks in fastboot mode, and the only way to restart it is by pulling out the battery.
So, what is the possible reason, to loosing connection to the device after the reboot in fastboot mode? (phone drivers already installed, pc rebooted, ADB SDK installed too)
Thanks in advance for any help!
Regards!
thudrumble said:
Hello there, after an hour of search and no useful results, i've decided to ask my question (sorry, if it's already been answered, but i didn't find anything)
I used the following procedure to flash the CWM recovery, but something goes wrong:
( http://forum.xda-developers.com/android/development/ufficial-thread-lenovo-k3-note-t3102997 )
1. "adb devices" shows the phone correctly (At this state the phone is properly shown in my windows device manager)
2. "adb reboot bootloader" pushes the phone to boot in fastboot mode
... but ...
3 "fastboot devices" doesn't find it anymore. (At this state the phone is shown as an unknown device in my windows device manager)
4. after some attempts I tried "fastboot flash recovery recovery.img" anyway, but as I expected, i was unable to reach the device, the image should be written to.
5. every the phone stucks in fastboot mode, and the only way to restart it is by pulling out the battery.
So, what is the possible reason, to loosing connection to the device after the reboot in fastboot mode? (phone drivers already installed, pc rebooted, ADB SDK installed too)
Thanks in advance for any help!
Regards!
Click to expand...
Click to collapse
Hi,
I have the same problem. Any solution exists for that?
Thanks.
Same here. Some one saying it's driver issue, but I didn't have any errors installing the drivers and I tried different PCs, all the same...
Another reason I said it might not be a driver issue was that I used that PC to root the device successfully a while ago. But after updating to the newly released stock ROM, now this rooting method stuck in the fastboot mode.
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did someone tried other ways to root the K3 Note (apps etc.)?
Regards!
marskingbeatgates said:
Same here. Some one saying it's driver issue, but I didn't have any errors installing the drivers and I tried different PCs, all the same...
Another reason I said it might not be a driver issue was that I used that PC to root the device successfully a while ago. But after updating to the newly released stock ROM, now this rooting method stuck in the fastboot mode.
Click to expand...
Click to collapse
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did you tried other ways to root the K3 Note (apps etc.)?
Regards!
thudrumble said:
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did you tried other ways to root the K3 Note (apps etc.)?
Regards!
Click to expand...
Click to collapse
Hi,
I tried this method.. I can not add link. Try to find "How to root and install Google Play Store on Lenovo K3 Note" in youtube . And it did work for me. Root checker showed that root access is not fully. But I manage to install another rom.
This might help:
Go to the main thread...and jump to page 73 and read post #722
http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
For a change, you could use another method:
Lenovo K3 Note Manager by Pr1nc3V located here: http://forum.xda-developers.com/k3-note/general/tool-lenovo-k3-note-manager-t3261285
freelancer81 said:
This might help:
Go to the main thread...and jump to page 73 and read post #722
http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
For a change, you could use another method:
Lenovo K3 Note Manager by Pr1nc3V located here: http://forum.xda-developers.com/k3-note/general/tool-lenovo-k3-note-manager-t3261285
Click to expand...
Click to collapse
Thanks dude! The first method is the one, that won't work with my K3Note, but I'll try your plan B later today. Fingers crossed
cloudinio said:
Hi,
I tried this method.. I can not add link. Try to find "How to root and install Google Play Store on Lenovo K3 Note" in youtube . And it did work for me. Root checker showed that root access is not fully. But I manage to install another rom.
Click to expand...
Click to collapse
Thanks! I found the video and try this one too, if the freelancer81's method fail.
Mission accomplished
Mission accomplished? Kindly share how you were able to resolve it as I am still faced with the problem. I have tried all the recommendations here
same issues..
ADB sees the phone. but fastboot doesnt seem to connect / see it..
And no thats not the issue of not booting into the recovery as suggested, its not even able to flash the recovery.
stinvilla said:
Mission accomplished? Kindly share how you were able to resolve it as I am still faced with the problem. I have tried all the recommendations here
Click to expand...
Click to collapse
Anyone?
No one?
Lenovo k3 note stuck on logo
I want volte support in k3 note so I know the cm14 is with volte support when I am trying flash cm14 with twrp the zip file successful install. But in log show "E: unknown commad[log] two rows
After that when I power on the phone its stuck on logo.
Sorry for grammar errors
Give me solution....
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Stone. Cold said:
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Click to expand...
Click to collapse
Yes, you are going to need a fastboot cable. You can pick one up on Amazon for cheap or you can make your own by using some tutorial online. After you get the fastboot cable, use the Kindle Fire restore tool that I will link down below. Download it (it will take a while) and run it. Please read the directions because I didn't at first and I boot looped my Kindle by installing older recovery and boot image. After this is complete your Kindle will work again. I wouldn't recommend installing Magisk again because it modifies the boot loader. Sorry.
KFHD Restore tool (that tool that I mentioned): https://forum.xda-developers.com/showthread.php?t=1951254
Thank you for this, will. I will follow your instructions once I have received my fastboot cable
Again, thank you. I have left my tablet on my shelf for quite some time now and didn't really have time to fix it due to college work, and so. But I will definitely let you know the results :fingers-crossed:
I made pretty mutch the same error like you and flashed Magisk 12. I used the fastboot cable, entered fastboot and used the recovery tool to restore recovery and stock Rom with supersu and apex launcher. After following exectly the steps in 2. Bootloader and twrp. The problem I am facing is the same I faced before. After flashing linearOS 14 with twrp. I reboot from recovery. At first it showes the orange logo and the the blue. And it stays at blue logo for hours.
I don't know what to do. The strange thing is. I can boot in the recovered Amazonfire OS. But I can't flash any costum Rom.
I have no idea what I made wrong during the process. I followed all steps and repeated the procedure 3 times.
Always ending in blue logo.
Even without flashing any rom. Only following the steps to flash twrp with all the other stuff I am stuck on blue screen.
Please I need advice. Help me
An update to Android 12 has been released. Everything seems to be fine. Random reboots appeared.
I tried a full reset of nothing, then downloaded the OTA via adb sideload in the hope that it helps, but to no avail.
And it's sad that the bootloader is locked
device verizon.
Screenshot shows adb sideload error
Who knows what can be done, please tell me.
-------------------------------
After 3 long days of agonizing and torturing Google support, no help from them
Found the adb rescue install file.zip command, in their source code
Because I had coral-ota-sp1a.210812.015 firmware, I needed verizon firmware, for me coral-ota-sp1a.210812.016.a1-37be0022 didn't work, it didn't start
But with this coral-ota-sp1a.211105.002.a1-0939d2dd everything is fine
The main thing is to have the usb cable intact. And the pc connector usb 2.0
1. Go into bootloader
2. Select Rescue mode
3. type in the following words at the command line
adb rescue install file_name.zip
All should go through without errors
May help someone
Sorry for my English.