Hello, I am having some Technical Difficulties with getting my Bootloader to Unlock after running the AT&T 2.20 RUU from the HTC Website. I have tried almost everything just short of smashing the Device with a hammer any ideas or fixes for this? Listed below are the steps i have tried so far.
fastboot oem lock - Response: Bootloader is already Locked
Ran the 2.20 RUU - Result: Successful
Skipped through the Device Set-up, Unchecked Fast boot in the Power Settings, Enabled USB Debugging in Developer Options
Rebooted into Bootloader, selected fastboot and Plugged in my USB Cable and let all the drivers load
Opened a CMD window and typed "fastboot getvar cid" - Result: CID 111111
proceded to flash Unlock Code - Result: C:\platform-tools>fastboot flash unlocktoken Unlock_code.bin sending 'unlocktoken' (0 KB)... OKAY [ 0.149s] writing 'unlocktoken'... (bootloader) unlock token check successfully OKAY [ 0.022s] finished. total time: 0.200s
selected Yes on the Confirmation Screen - Result: Device wiped all user data and rebooted
Shipped Setup, Disabled Fast boot, and Checked USB Debuging again. Typed in the CMD "adb reboot bootloader"
Bootloader booted and the Device still says ReLocked
My Device Info:
HTC One X AT&T S4 Varient (Evita)
HW VER: 002
Android 4.0.4 Build 2.20.502.7 710RD
HBOOT: 1.14.0002
RADIO: 0.19as.32.09.11_2
RevolutionaryPC said:
Hello, I am having some Technical Difficulties with getting my Bootloader to Unlock after running the AT&T 2.20 RUU from the HTC Website. I have tried almost everything just short of smashing the Device with a hammer any ideas or fixes for this? Listed below are the steps i have tried so far.
fastboot oem lock - Response: Bootloader is already Locked
Ran the 2.20 RUU - Result: Successful
Skipped through the Device Set-up, Unchecked Fast boot in the Power Settings, Enabled USB Debugging in Developer Options
Rebooted into Bootloader, selected fastboot and Plugged in my USB Cable and let all the drivers load
Opened a CMD window and typed "fastboot getvar cid" - Result: CID 111111
proceded to flash Unlock Code - Result: C:\platform-tools>fastboot flash unlocktoken Unlock_code.bin sending 'unlocktoken' (0 KB)... OKAY [ 0.149s] writing 'unlocktoken'... (bootloader) unlock token check successfully OKAY [ 0.022s] finished. total time: 0.200s
selected Yes on the Confirmation Screen - Result: Device wiped all user data and rebooted
Shipped Setup, Disabled Fast boot, and Checked USB Debuging again. Typed in the CMD "adb reboot bootloader"
Bootloader booted and the Device still says ReLocked
My Device Info:
HTC One X AT&T S4 Varient (Evita)
HW VER: 002
Android 4.0.4 Build 2.20.502.7 710RD
HBOOT: 1.14.0002
RADIO: 0.19as.32.09.11_2
Click to expand...
Click to collapse
I am in the same boat you are, however i just wanted to downgrade from a jellybean rom/kernel back to factory default...so i am also looking for the solution, absolutelygrim had made some suggestions in my thread but none of them helped so ill be keeping a close eye on this thread and see if anyone has a solution
Sometimes this can take a few tries. I can recall people having to do it 20 times or more when 1.85 came out.
Try this: Unplug your phone and power off. Reboot your computer. Restart phone, plug into different USB port. Try pushing the unlock token again. This worked for me when I moved up from 1.73.
iElvis said:
Sometimes this can take a few tries. I can recall people having to do it 20 times or more when 1.85 came out.
Try this: Unplug your phone and power off. Reboot your computer. Restart phone, plug into different USB port. Try pushing the unlock token again. This worked for me when I moved up from 1.73.
Click to expand...
Click to collapse
thanks, worked like a charm
iElvis said:
Sometimes this can take a few tries. I can recall people having to do it 20 times or more when 1.85 came out.
Try this: Unplug your phone and power off. Reboot your computer. Restart phone, plug into different USB port. Try pushing the unlock token again. This worked for me when I moved up from 1.73.
Click to expand...
Click to collapse
This also worked well for me. Thank you!
Related
hello, earlier today i had to downgrade from the rogers jb software to the 2.20 ICS ruu and when trying to re unlock the bootloader it will not re unlock.
Steps:
i ran the xfactor exploit result > CID already changed
in fastboot i reflash my unlock code result> unlock bootloader screen comes up i select yes, it reboots.
when device boots up i skip setup go and enable usb debugging then reboot to bootloader via adb
when the bootloader comes on it still says *** RELOCKED*** am i doing something wrong or....
Device: HTC One X (EVITA)
Hboot: 1.14.0002
Radio: 0.19as.32.09.11_2
Rom: 2.20.... 710 RD
any help is appreciated
fastboot erase cache
then unlock it again
absolutelygrim said:
fastboot erase cache
then unlock it again
Click to expand...
Click to collapse
alright, i will try that, i will report back and let you know how that goes
Update: I Tried that command and to no avail... heres the output on the CMD
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>fastboot
erase cache
erasing 'cache'... OKAY [ 0.125s]
finished. total time: 0.125s
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>fastboot
flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.140s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.140s
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>
any ideas?
fastboot flash unlocktoken Unlock_token.bin
Or whatever you have the filename as. I think its case sensitive
Sent from my One X using xda app-developers app
Factory reset then unlock
DvineLord said:
Factory reset then unlock
Click to expand...
Click to collapse
Nope that didn't work either
Sent from my HTC One X using xda app-developers app
USB debugging is enabled?
absolutelygrim said:
USB debugging is enabled?
Click to expand...
Click to collapse
yes, for all intents and purposes it does everything it is supposed to even shows the Unlock Bootloader screen where it says the warranty disclaimer and asks to choose yes or no, i choose yes the phone resets i speed thru the setup enable usb debugging then adr reboot bootloader and it still states "RELOCKED" if i could i would do a logcat but i dont know how or if it's even possible to logcat the unlock process or any fastboot process for that matter...
I was having trouble with my phone, so I ran the 2.20 RUU and got everything back to stock. Now when I try to unlock the bootloader, it doesn't work, and only will say "relocked". I've gone through all of the steps without error (using the all in one toolkit). I tried using "fastboot erase cache". I don't know what my next move should be.
seaneschen said:
I was having trouble with my phone, so I ran the 2.20 RUU and got everything back to stock. Now when I try to unlock the bootloader, it doesn't work, and only will say "relocked". I've gone through all of the steps without error (using the all in one toolkit). I tried using "fastboot erase cache". I don't know what my next move should be.
Click to expand...
Click to collapse
Don't bother with the toolkit. Register on htcdev and go to the page where you submit token. In fastboot, simply shoot the command "fastboot oem get_identifier_token"
Mark it before the arrows and paste it in htcdev. The rest is pie
Sent from my One X using Tapatalk 2
InflatedTitan said:
Don't bother with the toolkit. Register on htcdev and go to the page where you submit token. In fastboot, simply shoot the command "fastboot oem get_identifier_token"
Mark it before the arrows and paste it in htcdev. The rest is pie
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I've got the unlock_code.bin file already. When I flash it, I get this in command prompt:
Code:
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.150s
Then I select Yes, unlock bootloader, and my phone reboots. No red text on the HTC screen. Once everything's loaded, it's a fresh version of android. If I load up the bootloader, then, it still says "relocked".
Unplug your phone, power off, boot into bootloader, and plug it back it. This is a common error. No idea why, but it seems to fix it.
iElvis said:
Unplug your phone, power off, boot into bootloader, and plug it back it. This is a common error. No idea why, but it seems to fix it.
Click to expand...
Click to collapse
That did it! Thank you.
seaneschen said:
That did it! Thank you.
Click to expand...
Click to collapse
I wish I knew why it matters, but it does. Go figure.
My dads HTC one mini is stuck in the bootloader menu. I cannot access recovery. it is locked. I have tried To flash a custom recovery but since its locked it wont work. I tried to unlock it with
HTCdev unlock bootloader but i cant get the phone to react when i do (fastboot flash unlocktoken Unlock_code.bin.) the cmd prompt looks like it works but i don't get a screen to approval unlock on the phone. I have been at this for hours now and any help would be great. I'll check back in tomorrow
Unit3 said:
My dads HTC one mini is stuck in the bootloader menu. I cannot access recovery. it is locked. I have tried To flash a custom recovery but since its locked it wont work. I tried to unlock it with
HTCdev unlock bootloader but i cant get the phone to react when i do (fastboot flash unlocktoken Unlock_code.bin.) the cmd prompt looks like it works but i don't get a screen to approval unlock on the phone. I have been at this for hours now and any help would be great. I'll check back in tomorrow
Click to expand...
Click to collapse
Does fastboot say "fastboot usb"?
What happens when you type fastboot devices? This should return your serial number.
Are you on Windows? Which version?
jollywhitefoot said:
Does fastboot say "fastboot usb"?
What happens when you type fastboot devices? This should return your serial number.
Are you on Windows? Which version?
Click to expand...
Click to collapse
sorry it took so long for me to get back. so Yes it says "fastboot USB" . fastboot devices gives me HT38EWA03720 fastboot. I am on Windows 7
That's really strange.
Can you confirm the unlock token is in the same directory you're running your fastboot command from in command prompt? Can you post the output from the fastboot unlock command?
Hi
i have the same issue
the htc one mini is stuck on fastboot.
when trying to go recovery it just reboot back to fastboot
bootloader is locked, i tried to unlock it - this is the fastboot text:
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.157s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.020s]
finished. total time: 0.183s
but im not getting the disclaimer on the phone to continue
i have win 8 (also have win 7- same thing there)
the device shown in the device manager as 'my htc"
reviving the dead ...
Anyone found a solution yet?
Anyone found a solution yet?
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i
GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.
meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?
I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/
Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )
Go to an independent repair shop. They have the equipment to flash on the motherboard.
So 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.
Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.