I am trying to root my HTC One M7. I have done the research, and I know how to go about it. I have running into a few snags, though. I joined htcdev.com, and read the tutorial for how to unlock the boatloader, but Step 5 wants me to access the command prompt on my PC and enter a command so that I will receive my identifier token, and then I should be able to unlock bootloader, and continue the process through Kingo successfully.
But, my phone is not appearing in the command prompt on my PC, only the line for C:\Users\Username>
MTP is enabled on my phone, I believe that could be the culprit, because my computer is reading it as a mass storage device. But, I am unable to disable MTP mode, or even switch to PTP mode. I have tried every possible way.
Also, under developer options in my phone settings, there is no option to enable OEM Unlock.
Someone please help, I may be missing a simple solution, but I've been at this all day and have no dice.
Thank you
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
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Did you follow the instructions? I've also done the HTC unlock method and it's flawless. I revolutionary'd after that but that's besides the point.
Not trying to sound like a douche, but you definately missed something. Maybe you didn't enable USB Debugging.
just do the s-off/rooted thing by this forum :
http://forum.xda-developers.com/showthread.php?t=1192300
and you will succed in 1 time oh and dont forget htc sync need to be on at phone with usb debugging
Yes, I've followed the instructions
I had a similar problem. I simply rebooted the phone (while it said "waiting for device") and all went well after that.
kaustic187 said:
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Click to expand...
Click to collapse
first Enable USB debugging on phone . Boot your phone into bootloader. Connect your phone to pc via usb cable. Phone should read FASTBOOT VIA USB.
Make sure that HTC sync is off . ( Go to task manager, if you see the HTC sync is running, kill it)
Also remove anything else that may attempt to sync when you connect device.
Eg doubletwist, isyncr etc.
I'm using a 2015 Moto E 4G LTE with a locked bootloader.
I've done all the research regarding unlocking the bootloader and I'm fairly confident I can do it problem.
Where I'm having trouble though is the ADB interface does not recognize my phone. When I plug my phone into the computer it makes a beep beep sound indicating that it's connected and I can transfer files to and from via the MTP option. As soon as I put the phone into fastboot mode the beep beep sound Goes On Again indicating I've just been disconnected. When I type in commands it says "device not found".
I'm pretty sure that my internal files are corrupted. If anyone knows a way around that please let me know.
In the meantime, can I flash a kernel through the built in fastboot mode with a bootloader still locked?
BillyMumphry said:
I'm using a 2015 Moto E 4G LTE with a locked bootloader.
I've done all the research regarding unlocking the bootloader and I'm fairly confident I can do it problem.
Where I'm having trouble though is the ADB interface does not recognize my phone. When I plug my phone into the computer it makes a beep beep sound indicating that it's connected and I can transfer files to and from via the MTP option. As soon as I put the phone into fastboot mode the beep beep sound Goes On Again indicating I've just been disconnected. When I type in commands it says "device not found".
I'm pretty sure that my internal files are corrupted. If anyone knows a way around that please let me know.
In the meantime, can I flash a kernel through the built in fastboot mode with a bootloader still locked?
Click to expand...
Click to collapse
Ha ha! As soon as I submitted this, I got a notification of a software update to Marshmallow!
The irony...lets hope this irons out the wrinkles.
SOLVED!!!
Well, the OTA update to Android 6 didn't solve my problem, it was my relentless sifting through post after post on XDA and just all over the Internet in general. For anyone else facing this problem here is how mine was solved:
My attempts at unlocking the bootloader were these: I installed everything that I could find on the internet. I installed Android Studio, SDK, all kinds of different drivers, minimal ADB and Fastboot, but nothing seemed to really work. When I plugged my phone into the computer neither ADB nor Fastboot would recognize the device.
USB debugging was ON, OEM was enabled, and for some reason I had MTP set. So after hours of sifting through bug reports generated by a terminal emulator APP, and going over post after post I finally found something useful.
Before I tried it though I wanted to start fresh. So I uninstalled everything from my PC and only download 2 things. Minimal ADB and Fastboot, (found here: http://forum.xda-developers.com/showthread.php?t=2317790, and the official Motorola Device Manager (found here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481.
But the thing that really did it was something I read here on XDA . It was this: switch MTP to PTP! And it was just that simple. Everything else was set the same, USB DEBUGGING ON, OEM ENABLED, and PTP SELECTED. I didn't even boot the device into Fastboot to begin as is instructed, I just started with my phone on and plugged in to my PC as I was just finishing transferring some photos. So I opened ADB/Fastboot, typed in "$ fastboot oem get_unlock_data" and bingo!
Here are the instructions I followed on how to unlock the bootloader: http://freeandroidroot.com/how-to-unlock-bootloader-and-root-motorola-moto-e/
So thank-you XDA forum, you are an invaluable and inexhaustible resource! :thumbup::thumbup::thumbup:
~This thread can now be closed~
Model: MAH-L09C432B156
EMU: 5.0
Android Ver: 7.0 NOT ROOTED!
No access to Devlepoer options for USB Debugging
Hi I have a Huawei Mate 9 which is FRP locked, I have gained the unlocking code from Huawei and have all relevent software and instructions to unlock Bootloader and remove the FRP protecton but I am really struggling with connecting the device in CMD with adb.
I have drivers installed and have allowed connections to phone with HiSuite on device and PC, I am unable to get into Developer settings due to FRP protection bur according to what I have seen in every walkthrough shows that this should not be a problem, even though I am unable to enabe USB debugging. Anyway I did have it connected once but have not been able to since so if anone can tell me where i might be going wrong I would be grateful.
After resetting phone and following instuctions via Huawei to prepare device I hold Vol- and plug in USB to Boot into Fastboot/Recovery mode.
Open CMD and execute Adb.exe in command, after that I enter command \adb devices which gets deamon running but showing no device.
I have tried going into what settings I am able to enter and enable USB in any way possible but still to no joy.
I have looked at posts on here but not found anything that seems to help as yet or I have just not looked in correct place.
Please can someone help as this is frustrating. Thanks Stew.
If you entered fastboot already try "fastboot devices" instead of adb
Did you go into about phone and tap the "build number" 7 times to enable developer options? If so you should be able to access and enable USB debugging
Sent from my MHA-AL00 using XDA-Developers Legacy app
" I have gained the unlocking code from Huawei "
please could you tell me how did you get that frp unlocking code from stupid Huawei?
they didn't answer my emails for one month now!
jr313 said:
Did you go into about phone and tap the "build number" 7 times to enable developer options? If so you should be able to access and enable USB debugging
Sent from my MHA-AL00 using XDA-Developers Legacy app
Click to expand...
Click to collapse
frp lock doesnt matter if you dont have oem unlock permission it wont help try using HWOTA with unlock code
i am in same boat since a month now and unable to bring the device back to life as i dont have usb debugging enabled and oem unlock permission and phone is bricked through huawei own official app and firmware
Hi, I'm trying to unlock my phone so I can install Kali Linux on my A466BG. I've read a lot on the web but came to a problem. I've got Android SDK on my PC and installed platform-tools. My device shows up after entering "adb devices." I've enabled developer mode and usb debugging and OEM unlocking. My problem is...I can't unlock the bootloader and use fastboot. After pressing power and up volume I get into the menu (and I actually reset my phone to factory settings so I'll have more space) but I can't find bootloader. My phone shows up fine on my PC and under devices, but when I switch to the other menu (with reset options) it doesn't show up anymore. Not even under "adb devices." I tried entering "adb reboot-bootloader" but it just restarts and goes to the normal android phone screen. I tried "fastboot -i 0x1bbb oem device-info" and it says "waiting for device." I'm not sure how to boot into fastboot and unlock my bootloader. Or why my phone doesn't show up on my PC after pressing power and up volume. Please reply with instructions. Thank you
Hi, me again. I found a video on YouTube on how to install Kali Nethunter on Android phones. I got it and now I'm installing Metasploit. It's just the command line but that should work. Check You Tube on "Nethunter without root" if you want to know. Thanks
I'm back...Not satisfied with Nethunter on Termux. I would like to know how to root the phone and install Kali. Can anyone look at the above question and reply with how to root my Alcatel A466BG? I'll check back tomorrow. Thanks in advance!