Database Info

[Q] Bootloader help, and phone not appearing on PC

I rooted my device (ATT HTC One XL), but now I can't seem to be able to find it in my device manager. When I plugged it in to root it using this method, it appeared just fine. However, now that it's rooted (used root checker to make sure), it isn't appearing on my computer. USB debugging is on, and I've tried multiple USB ports and PC connection types (currently using charge-only). What am I doing wrong? I also can't seem to be able to find USB connection mode options in the notification pull-down. The phone is, however, charging, and the LED light is green.
I am also trying to unlock bootloader using these instructions, but I can't find the "Unlock-Bootloader.bat" file mentioned. I'm assuming they meant the "Spoof-CID.bat" file, which I ran, but it gets stuck at "Restarting ADB."
Thanks in advance.
EDIT: Forgot to mention, I'm running 4.0.3 and 1.85. Irrelevant, but will upgrading to 4.1 or 4.0.4 conflict with root/bootloader, and how would I achieve this upgrade?

Do not upgrade to 4.0.4 before unlocking and getting g superCID. You probably need an updated driver just download it from htcdev and retry

GroovyGeek said:
Do not upgrade to 4.0.4 before unlocking and getting g superCID. You probably need an updated driver just download it from htcdev and retry
Click to expand...
Click to collapse
I can't seem to find the appropriate drivers on htcdev.com. I also tried to download the drivers here*, however since device manager doesn't recognize my phone, I can't install the drivers manually.
*since I'm too green to post links, here:
http : // onexroot . com /one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/

Bumping the thread, I want to be able to figure out the solution to be able to interact between my phone and PC, such as copying files over and the like.

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

D801 Stuck on LG Boot Logo

Unable to find a solution to my problem. Searched and read many threads on the subject and think I've about tried everything with no luck.
Have a T-Mobile D801 phone. Took the OTA update and successfully upgraded to kitkat. Did not like kitkat so I downgraded back to 4.2.2 using the LG Mobile tool and the D801110C.kdz file. This downgrade was successful and I was able to root also with success.
So I have a stock rooted 4.2.2 phone with stock recovery.
Used the phone several weeks before playing with the build.prop file. After a modification, restarted the phone and the phone now will not boot past the LG splash screen.
The phone will boot to stock recovery as well as fully boot to download mode.
Installed newest LG mobile tools as well as the drivers, and reinstalled several times.
I have tried using the standard LG mobile tools to revert to stock. When using this method, the program identifies the phone correctly as a D801 but does not list a software version and tells me that there is no upgrade available. When click on upgrade recovery, it tells me that there is nothing to fix. So, I tried clicking on upgrade recovery without phone attached and enter the imei number and connect the phone. The software downloads the update successfully but when it attempts to install, stops at 2-3% and tells me to connect the phone. Restart the phone in download mode, reconnect and attempt again with same failure. Have tried this with swapping the downloaded file with110C, 110G, and kitkat KDZ files and all fail equally at 2-3%.
Have changed and tried com ports 41, 7, and 4 as well as disable LG modem in device manager and all fail.
Have tried this method on a windows 8 64 machine, windows 7 64 machine, and windows xp 32 machine and all still yield equal results. Tried several different USB cables and ports.
Have attempted using the KDZ with the L&D method using the 110C/D and kitkat files and the 110C/D fail at 49% and the kitkat will not even start, just errors right away. Tried this method with the different computers as well as cables and com ports.
I have also tried using the LG flash tool with the D801 TOT file and dll. Will not start and gives me error that the model numbers do not match even though it says it is a D801 at the top of the program.
At a loss here for what to try next. Any help on this would be much appreciated.

FIXED
Fixed the problem. Couldn't get any of the above methods to work. Downloaded the LG Firmware Extractor and extracted the .DLL from the TOT file and used that with LGFlashTool. That worked perfectly. Up and running again.

mojohjojo said:
Unable to find a solution to my problem. Searched and read many threads on the subject and think I've about tried everything with no luck.
Have a T-Mobile D801 phone. Took the OTA update and successfully upgraded to kitkat. Did not like kitkat so I downgraded back to 4.2.2 using the LG Mobile tool and the D801110C.kdz file. This downgrade was successful and I was able to root also with success.
So I have a stock rooted 4.2.2 phone with stock recovery.
Used the phone several weeks before playing with the build.prop file. After a modification, restarted the phone and the phone now will not boot past the LG splash screen.
The phone will boot to stock recovery as well as fully boot to download mode.
Installed newest LG mobile tools as well as the drivers, and reinstalled several times.
I have tried using the standard LG mobile tools to revert to stock. When using this method, the program identifies the phone correctly as a D801 but does not list a software version and tells me that there is no upgrade available. When click on upgrade recovery, it tells me that there is nothing to fix. So, I tried clicking on upgrade recovery without phone attached and enter the imei number and connect the phone. The software downloads the update successfully but when it attempts to install, stops at 2-3% and tells me to connect the phone. Restart the phone in download mode, reconnect and attempt again with same failure. Have tried this with swapping the downloaded file with110C, 110G, and kitkat KDZ files and all fail equally at 2-3%.
Have changed and tried com ports 41, 7, and 4 as well as disable LG modem in device manager and all fail.
Have tried this method on a windows 8 64 machine, windows 7 64 machine, and windows xp 32 machine and all still yield equal results. Tried several different USB cables and ports.
Have attempted using the KDZ with the L&D method using the 110C/D and kitkat files and the 110C/D fail at 49% and the kitkat will not even start, just errors right away. Tried this method with the different computers as well as cables and com ports.
I have also tried using the LG flash tool with the D801 TOT file and dll. Will not start and gives me error that the model numbers do not match even though it says it is a D801 at the top of the program.
At a loss here for what to try next. Any help on this would be much appreciated.
Click to expand...
Click to collapse
How did you go back to 4.2.2? can you explain please?:good:

danieldp1990 said:
How did you go back to 4.2.2? can you explain please?:good:
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/showthread.php?t=2432476 and use TOT method to go back to 4.2.2

[Q] Hard Bricked Moto G 4.4.4 Solution??

Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help

Reserved for any solutions

This could help
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
androidsatti said:
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Click to expand...
Click to collapse

langelog said:
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
Click to expand...
Click to collapse
Nope
No solution till now

Phone is not recognized by any rooting command prompt application

Hello,
I have an Xperia L that I want to root and install a custom ROM on it.
The problem is that whenever I connect the phone to my laptop, although it is recognized by the laptop, the drivers are installing, and the phone is connected without any problem, any of the rooting command prompt-based applications I have tried aren't recognizing my phone or they aren't working.
I've tried motochopper, Doomlord easy rooting toolkit, and rootkitXperiaL, all of them downloaded from this forum.
The general error and freeze is "daemon started successfully", but after that there's nothing happening at all.
My cell phone is quite old and used, and the Volume Up button doesn't work, in order to put it in Fastboot mode, if that's gonna' help at all, so is there any solution to this?
Thank you very much.

MariusIskender said:
Hello,
I have an Xperia L that I want to root and install a custom ROM on it.
The problem is that whenever I connect the phone to my laptop, although it is recognized by the laptop, the drivers are installing, and the phone is connected without any problem, any of the rooting command prompt-based applications I have tried aren't recognizing my phone or they aren't working.
I've tried motochopper, Doomlord easy rooting toolkit, and rootkitXperiaL, all of them downloaded from this forum.
The general error and freeze is "daemon started successfully", but after that there's nothing happening at all.
My cell phone is quite old and used, and the Volume Up button doesn't work, in order to put it in Fastboot mode, if that's gonna' help at all, so is there any solution to this?
Thank you very much.
Click to expand...
Click to collapse
If you just want to root your phone (using windows pc), I suggest vroot ( older version of iroot for windows). But first you should enable debugging mode in developer options . It works with just one click and simply roots Xperia L ! Then you can feel roots of your phone and use its capabilities