Am trying to unlock the bootloader on HTC One M8 through the HTCdev page. The problem am having with adb lately and in general is that whenever I input whatever I need to or flash stuff the adb window flashes for less than a second and it then disappears. Yes. the results appear but disappear quickly. Can anyone please advise. Thanks
Just to confirm adb is installed correctly on my Windows 10 64bit as well as HTC USB drivers. It used to run fine except for the last 2 weeks. I've not done any Windows update or any other changes.
Related
I have read and searched but cannot find a solution so kinfd of find posting is the only way.
I have been watching here a while and used this forum to hard spl my wifes htc hd2.
I just got an unlocked vodaphone magic, a 32b, 1.33.0004.
I am following the wiki to root it using method 2 but I cant seem to get the adb driver installed as when typing adb devices I get an empty list. I have looked for usb driver issues and tried them to no avail. I have tried on my 64bit win7 pc and now my wifes 32 bit win 7 with same results.
Can someone help me out as just wanna get rid of all the voda branding and have something more vanilla android.
Cheers
Simon.
simon go on unlckr.com and follow the gold card method exactly i had the same specs and same problem, but it works now
www.theunlockr.com
not unlckr.com just figured you might want the right address if you didnt know
Thanks both will go look now. Its doing my head in. I have adroid composite adb device showing in device manager now but still adb devices show an empty list, but fastboot shows the device.
Adb device id shows if I do the same command while the magic is turned on normally but nothing in fastboot. Very strange so I will go try the method you link to, just hope I dont brick it
Unfortunately I do not have a spare 2gig mcro sd, just the 1 gig in the phone. I am waiting for an 8gig to arrive next week.
Still dont get why the adb devices lists the magic while turned on normally but not in fastboot mode? Just empty list. Been trying since lunch today with this driver for adb and getting it to see it. Gonna go against the wall soon lol.
Nope. Tried every way possible to get adb to see the phone but still empty device list. It says adb is installed in device manager and it lists fastboot devices and shows adb device when phone on normally but not in fastboot so stuck.
Spent about 6 hours lol just trying to get adb installed so not got any further. Shame as the phone is a bit crippled when you cant install progs to the mem card really especially with such a small internal memory.
you wont get abd to work without rooting. Wait for the other 8GB memory and do the goldcard method as described.
after that get in fastboot mode, and test exacly as unlocker.com you'll be fine. i also followed their video
Of course adb works without root!
You problem might be that the Windows actually uses different drivers when the phone is awake, in recovery or in fastboot and you have not set up the right drivers for fastboot!
connect your phone to USB, boot it into fastboot and find it in device manager, from there update the driver...
I've been trying to s-off my phone but its giving me the waiting for device status, after hours of googling i am stumped. I installed the latest SDk/drivers etc. adb devices detects my phone, i've even gone and installed pdanet just to see if it will connect and yes it does. HTC sync detects my phone, but revolutionary doesn't which i find very very odd and stressful. I am running windows 7 64 bit and yes i ran the program as admin. If there is anyone with any insight I will gladly appreciate it.
T.I.A!
MODS PLEASE LOCK THIS THREAD UP SOLUTION FOUND!!
I managed to figure it out by replacing AdbWinApi.dll with the newest one from the sdk. Now I am stuck on fastboot as adb doesn't detect it out now. reinstalled fastboot drivers, but nothing happens.
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
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:
As mentioned, I need to go back to stock in order to unlock my phone but it has been a very long time since I have done anything techy to this phone. I know I needed an RUU file (which one?) and drivers but I also read about it failing in Windows 10. Can anyone advise how I can unlock my Rogers evita device?
I should also note that after a bit of research, I am trying to flash the RUU (using the command 'astboot flash zip PJ83IMG.zip' without quotes) but it just says 'waiting for devices' even though fastboot is red and says fastboot usb... Is this the result of having Windows 10 (drivers do not work)?
I have installed the drivers and HTC sync/adb from, the following:
http://forum.xda-developers.com/showthread.php?t=2588979
It is still not useful. I should also note when trying to sync via fastboot, in device manager I see under USB (device failed enumeration).
I know it's a few months later, but if it can help someone, here is how I got ADB-Fastboot (especially Fastboot) working under Windows 10 64bit.
I'm pretty sure I remember correctly doing just that, after messing for days without success.
If you're not successful, I might be forgetting something.
(of course, I cleaned my PC removing any HTC driver and any ADB-Fastboot solutions I had installed before doing the 3 steps below, also cleaning the Windows Registry)
1. Download and install latest HTC Sync Manager, then uninstall Sync Manager keeping only the drivers installed.
2. Find and Install latest Minimal ADB and Fastboot.
3. Download and install latest Java SE Development Kit 32bit version (even for Windows 10 64bit).
Connecting phone to PC was recognized, started Minimal adb-fastboot and then typed adb devices, worked fine.
Rebooted the phone to Bootloader then put it in fastboot usb mode and typed fastboot devices, worked fine.