I would have put this in development but I don't have permission yet.
Situation:
I'm using a Chinese tf300t
I tried to root my tablet using the cwm all firmware compatible method. you can find it on youtube as i am not yet allowed to post outside links.
unlocked my tablet. downloaded sdk and all the applications necessary. followed their directions to the letter. I go to cmd to put in the code and when I hit enter after typing: fastboot -i 0x0blah... i get: "waiting on device"
What I think the problem is:
with the sdk fastboot my computer never makes the usb found sound so i thought maybe something with the fastboot driver might be causing a problem so i looked online and someone with the same problem found that a different version of fastboot fixed his waiting problem. I tried what worked for him and now I get a weird stutter version of the usb found sound and i still get a waiting message when i enter the code in cmd. so i think that there might be a problem with the drivers, but my tablet works fine with my comp when its booted up normally.
good news is that I have always been able to reboot device and run normally.
Anybody got any sugestions?
i would like to suggest you to copy these files: fastboot + cwr into 1 new folder, then run fastboot again ( do this while your device is showing ""waiting on device", don't need to reboot it)
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
iBlameLag said:
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
Click to expand...
Click to collapse
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
exad said:
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
Click to expand...
Click to collapse
Thank you, flashed over twrp and the computer recognizes it. Thanks so much for your help!
I've been following the official Sony method to unlock the bootloader, you can see that procedure here. I have downloaded and installed the SDK Manager, then replaced the fastboot driver for Sony phones like they say, then I can also successfully put my phone into fastboot and my computer also recognizes it as "S1Boot Fastboot" but when I try to update the driver to point it to use the driver supplied to the SDK, I get this message when trying to install it (in the driver error.png). I'm not sure if it's trying to say that it won't work or something. So I proceeded to the command prompt stage (that's in cmd1.png) and entered fastboot. That worked. Then I entered fastboot devices and get a new empty line, whereas I'm supposed to get some text returned (see cmd2.png). Trying to enter the command to unlock bootloader after that doesn't seem to be doing anything (see cmd3.png).
So, anybody have any suggestions?
Update: It looks like the fault is becuase the Fastboot drivers aren't being accepted by W10... I've put the files on a USB and gonna try on the old ****ty computer... it's a dual boot so if neither W7SP1 nor W10 work I'll just resort to Linux Ubuntu. Why has it got to be so hard?
You need to disable driver signature verification in advanced setting in order to install drivers on Windows 8.1 so maybe it's same in w10.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.
bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others
dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.