Database Info

[Q] problem with rooting and drivers

Hi,
I'm kind of a noob at this rooting stuff. I've looked ariund, done my research and everything but it never seems to go smoothly??..
I think the main problem is with the drivers. After following instructions the android drivers still said 'Android 1.0'. So I installed Pda net and then I got 'Android ADB Interface' drivers. Soo the thing is, after searching for 'adb devices' in cmd prompt, It says 'list of devices' but there's nothing in the list....?
For some reason it won't do any commands like 'adb reboot bootloader' or 'fastboot oem lock'. It says not found. I have installed all the sdk and packages...
Would really appreciate some help from you guys. I didn't think rooting would be so complex??...
Thanks

can you post screenshot??

Ok for some reason, after starting the cmd again today and typing adb devices, it has listed my device. But when I type 'fastboot oem lock' (because my bootloader is already unlocked) it says not found as shown in the screenshot.
Am I doing something stupid??...

70 views?... cant anyone help ... please..

soulja786 said:
70 views?... cant anyone help ... please..
Click to expand...
Click to collapse
If adb devices lists your device you're not in the boot loader, the ONLY place fastboot will recognize your device and function or you have a driver issue. You're either in recovery or booted up. Reboot into the boot loader to use fastboot.
If you get into the boot loader and fastboot still doesn't show your device it's a driver issue. Update the driver manually and point it to the SDK USB driver provided with the SDK.
For reference....
Booted into boot loader:
Fastboot OK
ADB NO
Recovery / Fully booted
Fastboot NO
ADB OK

Hi guys,
I really do think this is a driver issue... any idea on how to solve it? I do have PDA Net installed... ?
@krohnjw ... could you please clarify.. Im a bit lost.
Thanks!

Did you try something like oneclickroot?
http://forum.xda-developers.com/showthread.php?t=1138755

Well I also had a lot of issues trying to root my i9020t so let me try to help..
Phone will be recognized with ADB when u select enable debug on developer options. You ll see "Android ADB Interface" on SYS DRV.
On other hand , when U start phone on fasboot mode, it should install something like "Android Bootloader Interface " , if U keep seeing "Android ADB Interface" , its wrong, but took some time to realize that.
That happened to me when I was using WinXP x32 to root my phone, ironically thinking it would be more compatible an less prone to bugs... When done it on W7 x64 , my fastboot driver was discovered correctly (Android bootloader Interface) using x64 PDA drivers, and all went good then!
Hope this may help!

ADB does not work in recovery

It works when booted into the OS but in recovery ADB is not recognized.
What drivers are you all using ?

stanglx said:
It works when booted into the OS but in recovery ADB is not recognized.
What drivers are you all using ?
Click to expand...
Click to collapse
On my mac ADB would not work in the stock recovery but it would work in CWM and fastboot. Think it is a driver issue.

I cant get it work anywhere and now I cant get stock recovery to work!

OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS

stanglx said:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
Click to expand...
Click to collapse
Thank you so much for this, I was pissed that I couldn't sideload.
On another note, does anybody see their device without the driver as "wx_un_mo"? I didn't think this was a valid model number considering the post at http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116 says it's a modem/wifi version.

Yes.. it was showing up as this for me too when in recovery but when in android OS it was fine... that is just the device ID . I kept uninstalling it until it showed as shield tablet with an ! in front of it. Now I think that was over kill.
Make sure your using the Nvidia Windows driver... There are two drivers that load
1. Bootloader driver
2. ADB Composite Driver
1 loads in fast boot only (bootloader)
2 loads in andorid OS (no issues typically) but when in recovery you have to force the driver install. If it doesnt work when in android OS (ie Lollipop, etc.) then do the same.. pick ADB composite driver.
MidgetMob said:
Thank you so much for this, I was pissed that I couldn't sideload.
On another note, does anybody see their device without the driver as "wx_un_mo"? I didn't think this was a valid model number considering the post at http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116 says it's a modem/wifi version.
Click to expand...
Click to collapse

stanglx said:
Yes.. it was showing up as this for me too when in recovery but when in android OS it was fine... that is just the device ID . I kept uninstalling it until it showed as shield tablet with an ! in front of it. Now I think that was over kill.
Make sure your using the Nvidia Windows driver... There are two drivers that load
1. Bootloader driver
2. ADB Composite Driver
1 loads in fast boot only (bootloader)
2 loads in andorid OS (no issues typically) but when in recovery you have to force the driver install. If it doesnt work when in android OS (ie Lollipop, etc.) then do the same.. pick ADB composite driver.
Click to expand...
Click to collapse
Yea I figured out the driver install fortunately, I was just curious as to why it was showing up as such. I didn't think that the specific model number was valid and was curious if anyone else had the same thing.

Device not detected in ADB after rebooting to fastboot

I tried asking this in the forum for my specific phone (Sony Xperia XZs) but I'm having little luck over there so I'm gonna ask here.
I'm trying to unlock the bootloader hoping that I can root and install a custom ROM.
When the device is on, the computer can see it just fine, but when I reboot it into fastboot mode, it can no longer see it. I have all the necessary drivers as far as I know.
It still appears in device manager as 'S1boot Fastboot'. I seem to have no luck updating drivers there either if that is the issue. I choose to select manually and it narrows down under 'Android Device' to:
Android ADB Interface Version
Android Bootloader Interface Version
Android Composite ADB Interface Version
(None of them worked when I tried, unsurprisingly)

f-03g root

I have docomo tab arrows f-03g with android 4.4.4 .I want to root it .I have done following steps but failed to root .Tried king root ,kingo root ,iroot and some others with pc and without pc but no sucess .tried to unlock bootloder but tablet not going to fastboot mood by cmd command "adb reboot bootloader" just simple restart. I can go to recovery by key combination but recovery have two option 1 update and 2 factory reset .I treid many combination but cannot go to fastboot if someone knows any other method then tell me. tried magisk but need to unlock bootloader.Now is this the dead end or or something more can be done please guide me.

Your phone is based on Qualcomm chipset, hence you have to download and install the matching "Android USB Driver" too:
Download Qualcomm USB Drivers For Android (Latest Version)
Here you will find the latest Qualcomm USB Drivers for your supported Android device, which are compatible with all Windows versions.
usbdriverspie.com

jwoegerbauer said:
Your phone is based on Qualcomm chipset, hence you have to download and install the matching "Android USB Driver" too:
Download Qualcomm USB Drivers For Android (Latest Version)
Here you will find the latest Qualcomm USB Drivers for your supported Android device, which are compatible with all Windows versions.
usbdriverspie.com
Click to expand...
Click to collapse
thanks, for your answer but as you can see i need some kind of exploit that can bypass this tablet security because it read only system and android 4.4.4.please suggest me some kind of tutorial hat can help me

azharsafwan said:
thanks, for your answer but as you can see i need some kind of exploit that can bypass this tablet security because it read only system and android 4.4.4.please suggest me some kind of tutorial hat can help me
Click to expand...
Click to collapse
The Qualcomm driver mentioned is a driver to get installed in Wndows OS.

[SOLVED] confused noob - adb/fastboot : install or just run?

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.