I have a Desire without OS, it can boot into fastboot. Is there any way to know if USB debugging was switched on from here? I tried to unlock the bootloader, im on S-ON, but keep getting errors:
C:\Users\Alienanihilator\Desktop\Roms\HTC Roms\HTC One X\HTC_fastboot_files>fast
boot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Maybe has to do with USB debugging not being turned on before?
DrSmartphone said:
I have a Desire without OS, it can boot into fastboot. Is there any way to know if USB debugging was switched on from here? I tried to unlock the bootloader, im on S-ON, but keep getting errors:
C:\Users\Alienanihilator\Desktop\Roms\HTC Roms\HTC One X\HTC_fastboot_files>fast
boot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Maybe has to do with USB debugging not being turned on before?
Click to expand...
Click to collapse
You can't unlock the bootloader if it's not version 1.03.0001.
Flash the 2.3 RUU:
http://www.htcdev.com/process/legal_download/152
abaaaabbbb63 said:
You can't unlock the bootloader if it's not version 1.03.0001.
Flash the 2.3 RUU:
http://www.htcdev.com/process/legal_download/152
Click to expand...
Click to collapse
Thanks for the tip, I just did that, but still it keeps freezing when booting. Maybe some issue with the hardware I guess.
Related
hi,,,
my htc desire stuck in htc logoo , is s off and i try to flash with ruu.exe( RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865 )
flashing done.... but no booting....stuck on htc logooo...
i try to bootloader unlock but err
C:\adb>fastboot getvar cid
cid: HTC__E11
finished. total time: 0.000s
C:\adb>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
how to unlock bootloader ???
i need help....
Are you s-on now?
Then download the 2.3 ruu in my sig, put it on the root of your sd-card, boot in hboot, and select "yes" when prompted.
Don't change the zip name.
After flashing is complete, you can continue with the s-off process by using revolutionary.
ck.sufail said:
hi,,,
my htc desire stuck in htc logoo , is s off and i try to flash with ruu.exe( RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865 )
flashing done.... but no booting....stuck on htc logooo...
i try to bootloader unlock but err
C:\adb>fastboot getvar cid
cid: HTC__E11
finished. total time: 0.000s
C:\adb>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
how to unlock bootloader ???
i need help....
Click to expand...
Click to collapse
hold on a min.. wtf. u ended ur post with how to unlock bootloader. u started ur post with ur s-off. why did u try run ruu? if ur s-off then u dont need to unlock bootloader. what exactly r ya trying to do? what does it now say in bootloader?
unlocking the bootloader the easy way http://forum.xda-developers.com/showthread.php?t=2133336
good place to start http://forum.xda-developers.com/showthread.php?t=696189
also confused on what you want to do with your phone,
I had lollipop running without real issues for a while. After a complete battery drain, I put it on the charger. Upon trying to turn the device on, it hung on the Google screen showing an unlocked padlock at the bottom.
I tried to see how far I could go, and can boot into fastboot but no further.
I thought I would start the usual flashing process from the start by bringing it back to stock and then back to root. Initially the device was unlocked. I locked it with "fastboot oem lock" the rebooted to bootloader. Now when I run "fastboot oem unlock", the unit freezes up when I select Yes to confirm unlocking the bootloader.
Code:
C:\Android>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 898.264s
Previously, before I locked it, when I tried to flash recovery & bootloader, I received "FAILED (remote: flash write failure)" and "fastboot FAILED (remote: Partition table doesn't exist)" errors. Now, I cannot try to reflash because I can't get unlocked ("FAILED (remote: Bootloader is locked.)")
Current status:
Code:
C:\Android>fastboot-toolkit oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.016s]
finished. total time: 0.016s
integramodder said:
I had lollipop running without real issues for a while. After a complete battery drain, I put it on the charger. Upon trying to turn the device on, it hung on the Google screen showing an unlocked padlock at the bottom.
I tried to see how far I could go, and can boot into fastboot but no further.
I thought I would start the usual flashing process from the start by bringing it back to stock and then back to root. Initially the device was unlocked. I locked it with "fastboot oem lock" the rebooted to bootloader. Now when I run "fastboot oem unlock", the unit freezes up when I select Yes to confirm unlocking the bootloader.
Code:
C:\Android>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 898.264s
Previously, before I locked it, when I tried to flash recovery & bootloader, I received "FAILED (remote: flash write failure)" and "fastboot FAILED (remote: Partition table doesn't exist)" errors. Now, I cannot try to reflash because I can't get unlocked ("FAILED (remote: Bootloader is locked.)")
Current status:
Code:
C:\Android>fastboot-toolkit oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Same exact thing happened to mine last week. I've followed the exact same steps as you with no luck..Maybe some has recovered from this?????
zerocool00 said:
Same exact thing happened to mine last week. I've followed the exact same steps as you with no luck..Maybe some has recovered from this?????
Click to expand...
Click to collapse
So was this a Google OTA update that caused this?
integramodder said:
So was this a Google OTA update that caused this?
Click to expand...
Click to collapse
Anyone else have any suggestions?
I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
THC Butterz said:
I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
Click to expand...
Click to collapse
Go to bootloader mode?
Sent from my SM-G935T using Tapatalk
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
THC Butterz said:
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
Click to expand...
Click to collapse
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
dottat said:
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
THC Butterz said:
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
Click to expand...
Click to collapse
Yeah I still believe that a fully flashed matching Ruu will clear that flag. Can you try flashing again and see if the dev flag clears?
Sent from my SM-G935T using Tapatalk
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
lazye53 said:
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
Click to expand...
Click to collapse
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
sagarc88 said:
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Click to expand...
Click to collapse
For 5.8.021S, go to page 26 ....
sagarc88 said:
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
Click to expand...
Click to collapse
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
mchlbenner said:
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
You need to flash 2 files via adb first, then run the unlock command.
I did it successfully for 021s
Sent from my LEX727 using Tapatalk
kukuteku said:
For 5.8.021S, go to page 26 ....
Click to expand...
Click to collapse
This worked perfectly!! Thank you very much.
Flashing Critical Locked
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
MAHawbs said:
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
Click to expand...
Click to collapse
What did locked ability flash abootd it d relock bootloader.
What did you ?
Sent from my SM-A730F using xda premium
Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)".
Is there a workaround for this?
Thanks for your help!
I also have this issue.
Same thing here. I loaded LineageOS and have decided to go back to factory. I can't figure it out either. Here are my results.
fastboot flashing lock
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.022s
fastboot flashing unlock
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
fastboot flashing get_unlock_ability
(bootloader) 0
OKAY [ 0.020s]
finished. total time: 0.020s
Ok all, I finally figured it out.
I had to download factory image 6.0.1 (MXB48J) go thru the instructions to flash this image.
Started up in android went thru the min setup to get into Settings and Developer Options. Turn on USB debugging and the OEM Unocking.
adb reboot bootloader
flashboot flashing lock
Prompted me about wiping the device.
Everything is good.