Evening all.
I've spent about three hours this afternoon verbally lubricating my phone and computer over this "Rooting" thing.
Now, when it comes to technology, I'm reasonably savvy, but this is really starting to grate a bit. I've found various ways of doing it, all involving unlocking the hidden menu via "Volume down" and "Power" which isn't a problem.
After that, I open the DOS prompt and input the unlock command to get it to do the whole code generation thing. Except my phone doesn't respond, even though I have HTC Sync installed. I also uninstalled all the drivers for the phone through Device Manager, turned debugging off, and connected it as a total noob might to add music to it to allow the computer to reinstall the drivers it thinks it needs.
I still haven't had any success with it at all, and being at my wits' end, a guy I know pointed me in the direction of this site.
I also see that when I access the hidden boot menu on the phone, at the top of the screen it says "Locked". All the youtube videos I have seen on the subject have phones that say "Unlocked" at the top of the screen - I'm guessing this is one of my problems as well. Can someone kindly help me out with this please??
Thanks folks.
R
Just re-read the thread and realised I didn't actually say what phone it is!! I have the HTC Desire 300 on Tesco. (which in reality is o2) The machine I'm trying to do it on is running Windows 8.1, sadly, although I am unsure if that makes a difference.
Firstly, addressing the 'Locked' status in boot-loader.
All phones (mostly) come with a locked boot-loader. The phones in the Youtube videos already have the 'Unlocked' status simply because they have unlocked their boot-loader already, which is what you're trying to achieve.
I assume the command you are trying is 'fastboot oem get_identifier_token' and the problem is your PC wont detect your phone. Try the command 'fastboot devieces', it will show all connected devices or an empty line if no devices are detected.
Here is a list of solutions which will most likely fix your problem
Make sure you are using a usb2 port and not a usb3 port
In the boot-loader menu make sure you have selected the 'FASTBOOT' option and that it says 'FASTBOOT' inside of a red box and not 'HBOOT'
Try re-download Fastboot from this thread http://forum.xda-developers.com/showthread.php?t=2588979
Tried all of your solutions. As I understand it, the issue is the fact that the machine is running Windows 8.1. The issue lies with the ADB drivers and the fact that they don't like the OS. I can get the DOS shell to run no problem, but because I cannot get the correct drivers for Windows 8, it just comes up with "waiting for Device", and I have to force stop it through the Task Manager menu.
Related
Hello again. I've posted this problem in another thread and didn't get very far so I'm re-rolling the issue and posing it another way. Ok, here goes:
Tablet is a generic Chinese tablet. Klu by Curtis model number LT7052. This is a password locked unit that the original owner could not fix and has since abandoned the unit. I'm attempting any method for working around this problem and have gone through all the normal procedures. USB debugging is off. I can access recovery mode, however no combination of button pushing will yield the actual menu, you just see Andy, lying on his back with a red triangle and exclamation point hovering above him (maybe some kind of added caution screen, maybe corrupted recovery?). When I attach it to the computer at this point, load the Android ADB drivers, and type in "adb devices" I get:
"0123456789ABCDEF recovery"
"abd shell" yields the "No such file or directory <2>" error. Not really surprising as USB debugging is off.
When I use the "reboot fastboot" command and then reinstall the appropriate drivers the device is not found. Again, locked, no debugging, not really a huge surprise. I've even tried the wipe command from fastboot and it just sits there waiting for the device, again not a huge surprise since it cant be found.
I was able to locate the original firmware on the manufacturer's website and downloaded it, but I'm not sure what options I have at this point. It's really just a fun project for me trying to figure this out, but having the tablet operational would be a plus. If anyone has any ideas on how to proceed at this point I'd be willing to try just about anything, no matter how "off the cuff" it may seem. Any way to force feed this tablet the original OS without shell access? Thoughts? Suggestions? Thanks a ton for reading.
Bump for another look. Thanks!!
I have a Nexus 7 2013 that wont boot. USB Debugging was not enabled. At this point, I am just trying to wipe the machine with a stock image, but I am having trouble.
I have installed the sdk and drivers (so many drivers!)
Recovery mode fastboot does not recognize the device.
ADB recognizes the Nexus, but I cant seem to get it to do anything with it.
e: failed to mount anything.
I have read through so many forum threads that I'm just overwhelmed, and they all seem to require the machine being in USB debugging mode before any changes can be made.
Please help or tell me what pertinent information I have omitted.
Thank you
I think USB debugging only matters in ADB, which is when the device is actually booted into Android OS. You probably want fastboot, which is a different "application" and set of commands in a command prompt.
Code:
fastboot devices
Does that give you anything when the tablet is in fastboot mode? It should list the serial number of the device, similar to "adb devices" does. If not, it could be drivers, or another issue with the device.
Have you tried unlocking the bootloader? This will induce a factory reset of the current firmware version, which may allow you at least boot normally and take any available OTA updates.
Hello,
fastboot devices lists nothing, while adb does show the serial number.
I have used so many tutorials and a couple of toolkits that now I have no idea what is happening with my drivers.
Unlocking the bootloader to force a factory reset sounds amazing, but all the information I can find says I need to have USB debugging enabled to do so. I can not boot into the system to enable it.
Is there a way to force a reset without USB debugging?
Thank you
Usb debugging is irrelevant. Forget about it, it's only used when the system is booted.
You need to get fastboot devices to recognize the tablet.
Uninstall any and all toolkits and drivers. Redownload the sdk. Boot to the bootloader and plug it in, the drivers should install automatically. If not install the google usb drivers from the sdk manager in the sdk.
Try fastboot devices again. If it doesn't work try a different usb cord/port/computer.
You are in the bootloader when running this command right? Not the recovery? I think with the tablet off it's volume down and power. The screen that says start in big green letters at the top and has device info in the bottom left is what you want.
Edit: Did you boot to recovery and select the options to wipe data and cache? Sometimes thats all thats needed.
Also booting to recovery and performing a factory reset may be sufficient.
ADB will indeed function in recovery. I don't think you have to enable USB debugging to get this to work though.
Are you typing fastboot devices while booted in recovery? Typing fastboot devices while in recovery or booted into Android will do nothing.
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
helpmynexus said:
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
Click to expand...
Click to collapse
I have the same problem .. Have You reslove it?
bikicviki said:
I have the same problem .. Have You reslove it?
Click to expand...
Click to collapse
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------
Troops42 said:
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
Click to expand...
Click to collapse
Tried to edit but anyway:
After re..re, rereading your post, and responces. Have you tried the old fashioned way
Hold down the (down volume) button at the same time the (power) key.."Together" If you get anything that pops on your screen let go of the keys, one tap at a time tap the volume up or down key ONLY, until it says (START), its in green type. if you get there you should be ok, to move along
I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.
Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.
I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me
Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
FinnSanity7 said:
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
Click to expand...
Click to collapse
If you had used adb before and the phone was recognised earlier, then there shouldn't be an issue. If not, then when issuing adb commands, there will be a popup on the phone asking you to enable authorisation and to make it permanent. In your current scenario, you will not be able to grant authorisation. Your drivers might be installed properly but because of this "authorisation" issue, the phone might not be recognised properly.
Search for methods to pull data from the phone. I had read about a couple of methods where you can mirror your screen on the PC which will solve the problem for you. Unfortunately I am not able to recollect where I read that.
EDIT: Enter fastboot mode on your phone and connect it to the PC. Then using 'fastboot boot twrp.img' you can boot into TWRP on the phone and access the files and copy them using adb commands. This requires the TWRP in the same folder as your adb tools or vice versa and renaming the file as TWRP. I don't know whether this also requires 'authorisation' but try it any way.
So my buddy gave me this Nexus S 4G, since I like to collect phones. Unfortunately, it appears to be stuck on 4.0 ICS. I tried to check for an update to 4.1 ICS, but for some reason, it reports that my phone is up to date??? Wtf. So I tried doing it manually, I can't flash this random OTA which may or may not (probably is) Jelly Bean in stock recovery, but it fails. I tried doing it even more manually using fastboot, but for some reason, I can't get the USB drivers to work. My next step is to use a Macintosh, as they seem to work better with Android, but I don't have access to it yet. In the mean time, is there any other way to get this phone updated or, at the very least, rooted and ROM'd?
@Dr. Hax
I'm assuming you are using windows? If so burn a Linux iso, Mint or Ubuntu are both great. You can make a bootable iso using a thumb drive or CD. Then set up your pc for dual boot. You'll never have a driver issue on Linux.
I'm sure you probably know this but how I have gotten windows to work and see my device is install the fastboot and adb 15 second installer from here: https://forum.xda-developers.com/showthread.php?t=2588979
Then reboot of course. And when I plug my device in have developer options enabled and usb debugging enabled and be watching phone for the little box pop up that you just checkmark really quick so your pc can communicate with the device... Also if you scroll down on the phone in developer options to "default usb configuration" and change that to "file transfer", that will usually bring the little box up on my devices to check mark so they can communicate..It only shows for a second then it's gone. But if it hasn't popped up yet then open terminal and type sudo adb devices (hit enter) and again be watching your phone because that little box should then come up that you must quickly check mark on phone so pc and phone can communicate.
I always uninstall and reinstall drivers on windows and reboot afterwards. Also make sure check device manager and see what's there. But that 15 second fastboot adb installer for windows is a life saver and makes it all super easy!! On Linux none of this happens. Ever! ? You just plug in your phone and the model of your device shows up on the computer screen. IDK if this makes sense much but I tried to word it where it did best I could. Hopefully this helps or you already got it going.