Okay, I have tried three different ways to unlock my bootloader, and all of them are hanging at the same spot. I have tried fenguepays method, the htcdev method, and hasoon2000 all in one, and all of the hang while "waiting for device" when trying to get the identifier token. I have installed, and re-installed all of the sync drivers, and have tried to disable HTC sync like everyone says, but still all of this is to no avail. I was just wondering if someone could list all of the necessary drivers, and possibly tell me how to disable HTC sync, I'm not sure if I'm doing that right.
Are you in the bootloader when doing the fastboot commands? You have to be in the bootloader with the phone plugged in and it has to say fastboot usb. Also, I bet if you do a search on the method you'll find your answer...Its all over the forums.
Related
I've decided to unlock bootloader of Wildfire S (GSM). I go to www.htcdev.com and follow the steps. In one step, it shows HTC Sync as necessary to be installed. I've already installed latest version of HTC Sync but it can't detect my phone or any other HTC phones. I've tried several solutions found on the web but it's still not working. But I connected my phone to PC and use adb.exe from command line, typed 'adb devices' and it shows 'HT15CTL00668'. So I can say that my PC and phone are not loosing connectivity. What I want to know is - Is that OK to continue unlocking bootloader with 'installed but not working HTC Sync' ?
Hey,
I'm trying to get the bootloader (S-ON) to say "LOCKED" instead of "RE-LOCKED" for warranty purposes (e-bay store- random reboots down long before I unlocked/rooted it. The HTC Amaze tool from the Play store, wiping system/re-flashing ROMs, using different/stock ROM/kernels don't help). From what I've read, using "mainver error fix" with Hasoon2000's tool seems to be the key, but everytime I engage the command, it states that the "device isn't found." Android debugging is definitely on (I've checked like 5 times) and it's in "Fastboot USB" mode (hence the computer [Win7] is registering the device). What am I doing wrong? Any helped be appreciated.
Ugh, do you think they'll even care whether or not it's "Re-locked" instead of "Locked"?
==
Also, S-off doesn't seem to be possible with this phone; one of the contact points in the back of the phone (not GND) seems to be missing the brass (or brass-colored) contact points
Hello all,
I'm a little desparate with an error that occurred some time ago. My HTC One was updated and suddenly was encrypted.
Factory reset is not working and Recovery option is not working as well.
What I've done so far, after several forum messages:
1. I tried to execute the HTC dev (unlock_code.bin) hint in a way to unlock the bootloader, but with no success at all. I always get the "*** LOCKED ***" (S-ON) option enabled. Then, I saw a lot of messages in foruns regarding the HBOOT version 1.55 that is installed in my device. It seems that with this version, it's not possible to change the configuration to S-OFF.
2. No fastboot commands work, including all the flash writing options. All of them with signature failures. Again in this case it seems to be a issue related to S-ON/S-OFF.
3. I couldn't run the cellphone in USB debugging (after the boot, I'm presented with the infamous: "type password to decrypt storage", which obviously I don't have the password).
4. Runrunner didn't work.
At this very moment my device is a paperweight... Does anybody have another idea about what could be done in this case?
All my problems seem to be focused on my inability to change the option S-ON to S-OFF.
Any help is very appreciated!
Paulo
Hey Everyone,
After searching for days after a solution to my issue on this site and others I decided to get some personal feedback.
Because its my old phone and cause I want to have some fun with it i decided to root my HTC Desire X and proceeded to look for a tutorial on how. I learned that firstly I needed to unlock the bootloader thus I went to htcdev and followed the instructions all the way to the get token id part.
When I enter this into the CMD I receive a "waiting for any device" message and the PC gives me a popup saying "device unrecognised" which it doesn't do when not in bootloader.
I checked device manager and it says "device failed enumeration".
I have no idea what to do from here, I have tried installing various drivers and programs to no help and HTC Sync manager sometimes recognises the phone and sometimes not. I have heard it is a driver problem but people only say "do you have drivers" and perhaps I dont but I have no idea where to find them for windows 10.
Thanks for reading and I hope someone has an answer!
So I got this Sony Xperia X model F5121 from one of my relatives, and I ran into quite a few issues when I tried rooting it. it says Bootloader Unlock Allowed: NO, which would mean that i couldn't get into fastboot mode and unlock my bootloader but here's the very specific and weird part: I can get into fastboot mode, at least I believe so. My phone was carrier locked to Vodafone but I payed a professional to unlock that and now I can use every SIM I want. I looked online and the first XDA page said that unlocking the SIM meant that fastboot mode is unlocked as well. So I tried, I plugged my phone in while holding the volume key, a blue light popped up and it meant I was currently using fastboot mode, but when i try doing anything it says "waiting for devices" and doesnt end up working at all. Am I missing some drivers? Is it just impossible? Could one of you be kind enough to provide the needed files and some instructions for this procedure? i'm asking for a lot, I know but if there's anyone kind enough. I'm running the absolute latest version of Android 8 Sony provides.
EDIT: YEs, used adb shell, I have the ADB drivers, I tried the szuzu install or what the TWRP codename for it is, but everything just stops at "waiting for devices" and I can't do anything.
Since you are not allowed to unlock the bootloader - Bootloader unlock allowed - No, there is no way to unlock it and root it. Sorry.
even if you want to try again, make sure to force install googles drivers
instead of sonys