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.
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...
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!
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 I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
CinemaGFX said:
So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
Click to expand...
Click to collapse
So what you need to do is. Supercid your phone to 11111111 an go to htcdev.com an unlock your bootloader. Then once that is done. You need to downgrade to 1.55 so then you can lock your bootloader turn s-on an ruu the encrypted ruu that posted. Do NOT TURN S-ON till you find this ruu that's posted an understand it completey an ask dottat any question in that thread. Once you r downgraded locked an s-on an run the encrypted ruu your phone should be all stock an lock an s-on no tampered no nothing.
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
CinemaGFX said:
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
Click to expand...
Click to collapse
I think he specifically said do NOT turn s on. You cannot do anything unless you s off again. What Rom do you have loaded? Turning s off is the LAST step because it's like locking the door and throwing away the keys
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
CinemaGFX said:
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
Click to expand...
Click to collapse
Well. We got something else to try. What version os are you on?
Hello!
I have a small problem. A week ago died my phone when i unlocked the lockscreen one evening. Thought that the battery was empty, i put it on the charger and started up the phone a few hours later and the only thing that happens is that Google logo is displayed, then it starts over again. I can go into recovery and fastboot, but it does not matter what i do there. Managed to get it to be connected as a USB drive so I got out the pictures from it. But if you make a complete factory reset including data and restarts there everything left! Tried to run "fastboot format cashe" but it only return "FAILED (remote: flash write failure) "
The phone is rooted and bootloader is unlocked, i had a custom rom installed, and it had worked since beginning of summer.
Have you already tried to reflash stock rom with fastboot? Maybe that will help to get your partitions working properly...
i followed a guide on androidrootz dot com, "how-to-unroot-nexus-5-complete-stock" but directly when i try to flash bootloader i get a error message.
Does the bootloader remain unlocked? What error are you getting when flashing stock?
audit13 said:
Does the bootloader remain unlocked? What error are you getting when flashing stock?
Click to expand...
Click to collapse
Yes! It remains unlocked! Heres the "print screen"
C:\UnrootNexus5>fastboot flash bootloader-hammerhead-HHZ11d.img
unknown partition 'bootloader-hammerhead-HHZ11d.img'
error: cannot determine image filename for 'bootloader-hammerhead-HHZ11d.img'
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
g90814 said:
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
Click to expand...
Click to collapse
I Have tried that also, here is the print from that:
Connectivity Status: Fastboot Device Connected
Flashing bootloader-hammerhead-HHZ11d.img to BOOTLOADER partition...
fastboot flash bootloader "C:\UnrootNexus5\bootloader-hammerhead-HHZ11d.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
But when it boots up again its still unlocked...
fastboot flash bootloader bootloader.img
Oh! I missed one word. Will try it tonight!
Nope.... Doesnt work either....
C:\UnrootNexus5>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.256s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.457s
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
audit13 said:
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
Click to expand...
Click to collapse
Damn! thats what im afraid of....
ChocholateMaster said:
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
Click to expand...
Click to collapse
The telephone is unlocked, the lock is open when i reboot the phone.
C:\UnrootNexus5>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
I don't know how it got damaged. One day, ti started bootlooping and the bootloader had re-locked on its own even though I unlocked it straight out of the box. I booted into fastboot, unlocked the bootloader, and it only too a few seconds to erase everything. I immediately rebooted in fastboot and the bootloader was locked again. This unlock/relock happened over and over.
I booted into recovery and tried a factory reset but recovery could not mount cache or data to perform the erase.
My phone just kept getting stuck at the Google logo or bootlooping.
ChocholateMaster said:
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
Click to expand...
Click to collapse
I have tried that also, when im just type "FASTBOOT OEM LOCK" it lookes like this:
C:\UnrootNexus5>fastboot oem lock
...
OKAY [ 0.054s]
finished. total time: 0.054s
PERFECT!?!? But when i reboot its still unlocked.... if i do first lock, then unlock without rebooting, i get a new meny on the phone where i have to chose if i want to unlock my device. and if i chose yes it will reboot and its the same again....
How do i download that file??? I just got an EXE file, and i dont want to run that!
If it's not sticking on a reboot, that means the memory is most likely gone bad. I guess you could try using the diagnostic tool, which would confirm if the memory is bad.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
ChocholateMaster said:
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
Click to expand...
Click to collapse
after flashing it can take up to 15 mins to turn on because of first boot
@kardanmannen any news?
I'm getting more and more sure that the memorymodule is faulty in the phone. If you reboot in Recovery and select filemanager, for example you remove a directory with files, if you restart the phone, the directory is there again! And when you start it up in recovery and connect it to the computer, theres a few directorys you can write/delete/. Similarly, if you run "fastboot oem lock" and reboot it, its locked the first time it is started up and then the second time it is unlocked again.
Lost hope a little there and went off and ordered a Nexus 6P, hoping it will arrive on Wednesday.