Database Info

[Q] Can't unroot: ADB doesn't work in bootloader mode, but works in debug mode

The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?

You don't use adb in bootloader. You use fastboot.
Locking the bootloader does not unroot by the way.

crespo80 said:
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
Click to expand...
Click to collapse
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.

Leauwie said:
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Click to expand...
Click to collapse
This is true, I've used Wugfresh toolkit too but I had some problem...
I've Nexus S 9023, with wug toolkit I had no problem to install driver with its very complete guide, this part can solve your problem but make attention on other function, for example with it I've also unlocked my phone but when I tried to root my device freeze.
So maybe that not all toolkit function will work well on all Nexus S.

Please stop with this toolkit nonsense.
Its not a driver issue at this point. Its the user using ADB instead of fastboot.
Remove this and that when he is just using the wrong command. This is the nonsense you see when all people know is some toolkit.

Yeah, I'm an idiot, that was not a driver issue
it's just because I usually root/unroot/unlock/lock my android phones once in a while (when I first buy and when I sell them), so I always forget some basic procedures and searching through the forums is always a mess, I spent three hours doing that, before posting...
I had forgotten ADB and fastboot weren't the same... anyway, I solved with WugFresh (I didn't know it, thanks for the tip) but I could have solved even with plain fastboot commands, I know
Anyway, I'm surprised to realize that the real stock ROM is more stable than the rooted and deodexed stock ROM I was using before, now the 3G/2G/airplanemode swithing is blazing fast and the performance drops on some games are gone... I'll never figure out this Android world
Thanks for all your help :victory:

[Q] twrp manager to downgrade??

I've been reading and researching for weeks and have finally decided to unlock and install twrp recovery. I have successfully unlocked, but that is as far as I can get. For some reason, my win7 pc thinks my tf700 is a Samsung android phone. In the pc device manager, under Samsung android phone is where my asus adb interface device shows up. Clicking on properties of the Samsung phone does not produce any drivers to uninstall and uninstallation of the phone works, but reinstalls when I connect my tf700. So, I'm stuck. I'm wondering if I can use twrp manager from the playstore to install 10.6.1.14.8.zip to downgrade and then root, install twrp from goo manager ? Fastboot method of installing twrp has not worked for me either, I'm thinking because of the drivers issue. Any one have any thoughts of where I can go from here ? I'd really like to get a custom rom on my tablet.

fwuser said:
I've been reading and researching for weeks and have finally decided to unlock and install twrp recovery. I have successfully unlocked, but that is as far as I can get. For some reason, my win7 pc thinks my tf700 is a Samsung android phone. In the pc device manager, under Samsung android phone is where my asus adb interface device shows up. Clicking on properties of the Samsung phone does not produce any drivers to uninstall and uninstallation of the phone works, but reinstalls when I connect my tf700. So, I'm stuck. I'm wondering if I can use twrp manager from the playstore to install 10.6.1.14.8.zip to downgrade and then root, install twrp from goo manager ? Fastboot method of installing twrp has not worked for me either, I'm thinking because of the drivers issue. Any one have any thoughts of where I can go from here ? I'd really like to get a custom rom on my tablet.
Click to expand...
Click to collapse
Strange problem. Did you have the drivers for a Samsung phone installed prior?
It would be good if you could solve the driver issue - just so that you have fastboot access to your tab in the future.
Sure, you could downgrade to .8 and use Motochopper to root, then GooMangager to install TWRP (though I have never heard of TWRP manager to install stock firmware???), a quick search on the forums will give you the steps.
But to solve the driver issue, you may want to try to install the Universal Naked Drivers from Google, or install the Android SDK tool and through it the Platform Tools and drivers. I would prefer the latter.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Strange problem. Did you have the drivers for a Samsung phone installed prior?
It would be good if you could solve the driver issue - just so that you have fastboot access to your tab in the future.
Sure, you could downgrade to .8 and use Motochopper to root, then GooMangager to install TWRP (though I have never heard of TWRP manager to install stock firmware???), a quick search on the forums will give you the steps.
But to solve the driver issue, you may want to try to install the Universal Naked Drivers from Google, or install the Android SDK tool and through it the Platform Tools and drivers. I would prefer the latter.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
yes, I rooted, twrp'd and installed bone stock on my vzw gs3.
I have used guides to install platform tools, put them in my PATH so I could use a cmd prompt from anywhere, plus I've tried to install the naked drivers and everytime I connect the tablet it goes through the installing drivers through windows update and and says my 700 is a Samsung phone. I uninstall the drivers, don't let it use windows update for drivers, and point it toward naked drivers folder (unzipped) and it doesn't install. says I still have a Samsung phone. click on Samsung phone in device manager and have asus adb interface under it. I must be missing something. maybe I'll redo my platform tools and see if maybe I missed an important step or typed something wrong. when I connect my 700 to the pc in fastboot, it isn't recognized. what should be happening ? what should I be seeing ?

fwuser said:
yes, I rooted, twrp'd and installed bone stock on my vzw gs3.
I have used guides to install platform tools, put them in my PATH so I could use a cmd prompt from anywhere, plus I've tried to install the naked drivers and everytime I connect the tablet it goes through the installing drivers through windows update and and says my 700 is a Samsung phone. I uninstall the drivers, don't let it use windows update for drivers, and point it toward naked drivers folder (unzipped) and it doesn't install. says I still have a Samsung phone. click on Samsung phone in device manager and have asus adb interface under it. I must be missing something. maybe I'll redo my platform tools and see if maybe I missed an important step or typed something wrong. when I connect my 700 to the pc in fastboot, it isn't recognized. what should be happening ? what should I be seeing ?
Click to expand...
Click to collapse
Once connected in fastboot, if you type 'fastboot devices' (without the '), you should see the serial number of your tablet. Otherwise you see: No devices found or something to the effect.

How to root LG L50 Sporty (a.k.a LG D213c)

So this is my first post on XDA, due to the lack of information on this particular device. Here I'll try to explain how I managed to root this device after trying several methods available here and all over the web. First I'll explain what didn't work:
VROOT (*)
Framaroot
Motochopper
SRS Root
MTK Toolkit
Nearly every solution on the web
After trying every method above, I noticed none of them were working. They all were giving false positives. No ROOT at all. I was kinda frustrated, 'cause I had followed every instruction possible, without success. I double checked my PC drivers, and I noticed something odd: Every time I changed the USB connection type on the L50, Windows installed different drivers for the device. I'm saying this was odd because I installed the drivers from LG drivers pack, so I was a bit confused. So, after Windows Installed the drivers for MTP, Modem, PTP and LG mode, I tried VROOT and... VOILÁ! I had ROOT:laugh::laugh:
So here are the steps I followed, and the tools I used:
Download VROOT (a.k.a. as IRoot) from w w w. mgyun. c o m / en / getvroot (without spaces)
Enable DEBUG MODE (Surf the web if you don't know on how to do it).
Plug your device to your PC and wait until Windows Installs the drivers for the connection type.
Without unplugging the device, Change the USB connection type to the next one. Wait 'till windows finishes installation.
Repeat the previous step untill you finish with all connection types.
Check Device Manager for missing drivers. If you have some missing, repeat steps above.
Open VROOT/IROOT and plug your device to the PC. Follow on-screen instructions and wait.
ENJOY!
Now, I have to find a Custom Recovery that works with L50... so if you guys know where I can get one, I'll appreciate your help.

Your Thread will be moved to appropriate Section.

So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.

someone know how i can do a nandroid backup on LG L50 ?

Thank you so much. Worked on D213AR
Can you confirm if there is a way to unlock NFC hidden option on my phone?

jam66 said:
someone know how i can do a nandroid backup on LG L50 ?
Click to expand...
Click to collapse
If you managed to get Root (with the steps described on the OP) You can use Titanium Backup.

THE Ghost2 said:
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
Click to expand...
Click to collapse
same for me i made cwm for it cant boot to it because it has locked boot loader

So is it possible to root the phone with the official rom?
Or am i missing something?

[Completed] Rooting tablet

Hello XDA member
I have a touchlet xa100 tablet running Android 4.4.2 and want to root it, but Towelroot said "device not supported" and I cant use a pc because i have no adb driver for it. After searching, I tried a guide to modify the google usb driver, but that didnt work either.
My computer is running Windows7 x64 and other devices (Samsung Galaxy Y GT-S5360 and Sony Xperia M C1905) are detected by adb decives.
I hope you can point me to the right point.

adi2500 said:
Hello XDA member
I have a touchlet xa100 tablet running Android 4.4.2 and want to root it, but Towelroot said "device not supported" and I cant use a pc because i have no adb driver for it. After searching, I tried a guide to modify the google usb driver, but that didnt work either.
My computer is running Windows7 x64 and other devices (Samsung Galaxy Y GT-S5360 and Sony Xperia M C1905) are detected by adb decives.
I hope you can point me to the right point.
Click to expand...
Click to collapse
I didn't find any report of workign root for your device on xda.
But you can try the most popular and generic rootng methods:
How to Root Any Device
How To Root Any Android Device
[TOOL] Rootx 2.2 (Rev 3 )- Root almost all android devices
[UNIVERSAL GUIDE] Root Any Android Device Manually !
Root any Android device (without pc n in one click)
[ROOT] Framaroot, a one-click apk to root some devices
...
BTW, on some devices, TowelRoot only works on an older firmware/kernel version. So if nothing else works and you know how to downgrade to an older firmware version, you might try TowelRoot again.
Good luck !

After trieng all those methods, i got superuser installed but root not useable, SuperSU cant uninstall/update the su binary, so i gave up.
From fun and trieng to find out if i could use fastboot i typed adb reboot bootloader, 10 seconds after the tablet gave up and isnt booting any more. Its stuck in the kernel splash Image.
Its detected by my pc as "Samsung Android Phone" but not by adb.
You know a trick to revive it from the death (except JTAG) or do i have a new paperweight?
I dont know if it has a recovery, but even if it has one, how can i get there? It has only 2 Buttons, Power and Back, and if i press those 2 together, the kernel splash Image appears.

adi2500 said:
After trieng all those methods, i got superuser installed but root not useable, SuperSU cant uninstall/update the su binary, so i gave up.
From fun and trieng to find out if i could use fastboot i typed adb reboot bootloader, 10 seconds after the tablet gave up and isnt booting any more. Its stuck in the kernel splash Image.
Its detected by my pc as "Samsung Android Phone" but not by adb.
You know a trick to revive it from the death (except JTAG) or do i have a new paperweight?
I dont know if it has a recovery, but even if it has one, how can i get there? It has only 2 Buttons, Power and Back, and if i press those 2 together, the kernel splash Image appears.
Click to expand...
Click to collapse
Oh no ... sorry to hear that.
You can ask in the General discussion > Questions and Answers forum.
Hopefully someone knows a "trick" :fingers-crossed:

Thread closed and thank you.

[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.