Develop Bugs

[Q] Re-unlock bootloader?

Already unlocked via HTCdev.
Locked it back for OTA.
I want to reunlock it. Do I have to fastboot flash unlocktoken Unlock_code.bin or can I just oem unlock as it's already been unlocked before?

So far i know
U have to flash the token again untill we have S-Off

You gotta re-flash the token.

TheMathMan said:
Already unlocked via HTCdev.
Locked it back for OTA.
I want to reunlock it. Do I have to fastboot flash unlocktoken Unlock_code.bin or can I just oem unlock as it's already been unlocked before?
Click to expand...
Click to collapse
You can unlock and relock many times, relock with the file sended by htcdev and relocked by: fastboot oem lock

I locked my boot loader with CWM installed

I am stuck....can not install the original recovery....can not run RUU....says not the correct rom update utility...
tried to reunlock bootloader and that fails now with:
has anyone a clue on how to proceed.
Thanks

You need to fastboot stock recovery then run ruu
Watch this http://m.youtube.com/#/watch?desktop_uri=/watch?v=SZuAjz4PIjU&v=SZuAjz4PIjU&gl=GB
Sent from my HTC One X using xda premium

you unlock again then flash stock recovery, then relock, then RUU
not with fastboot oem unlock
but with fastboot flash unlocktoken unlock_code.bin
as you first did when you unlocked

bootloader won't unlock (Too many links)

Okay, so i was just scrolling through my apps, then my phone randomly restarts, and wont go past the HTC Beats screen, and when it does, the screen is just black.
So i restart into bootloader, and it says "Locked" at the top, so it appears its relocked itself?
WHAT DO I DO? WAS rooted and running Revolution HD-9.8 ROM.
Thanks
Edit: Tried unlocking the bootloader again, no result, got error message "FAILED (status read failed (Too many links))
finished. total time: 6.219s"
Edit: Battery is 3970mv, and i cannot get into recovery (i flash RUU HELP PLEASE.)
my friend Mr Hofs said to me your bootloader may unlock and only show locked !
i try to install CWM recovery !
C:\adb-Fastboot>fastboot flash recovery CWM.img
sending 'recovery' (5742 KB)...
OKAY [ 0.754s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.960s
i run CMD in ADMINISTRATOR
hey when i flash RUU phone reboot and go to bootloader and i try to reboot (not anything happend only after 3sec show HTC logo and go to bootloader (recovery and factory rest like this)

The most important thing you didn't tell is that the RUU flashed successfully, and that the phone didn't boot up. And that your bootloader goes from unlocked to LOCKED instead of relocked as it should......
The failed status error is normal, its confirmed everywhere on xda

Mr Hofs said:
The most important thing you didn't tell is that the RUU flashed successfully, and that the phone didn't boot up. And that your bootloader goes from unlocked to LOCKED instead of relocked as it should......
The failed status error is normal, its confirmed everywhere on xda
Click to expand...
Click to collapse
my phone after (rom crash and ..) unlocked ==> locked
i don't see relocked status in my life !!

RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed
now it's running (RUU)
wait........

"Fingers crossed and burning a candle"
and when it ends up successful you plug out the cable before you reboot !

ERORR [159]:IMAGE ERROR
The rom update utility canot update your android phone.
please get the correct rom update utility and try again
now try ICS ruu

And are you sure the fastboot command
Fastboot getvar version-main
Gave the the 2.17.707 number and not the 2.14.707 number ?

View attachment 1672111
Mr Hofs said:
And are you sure the fastboot command
Fastboot getvar version-main
Gave the the 2.17.707 number and not the 2.14.707 number ?
Click to expand...
Click to collapse
sorry ! screen shot in zip file

Seen the picture .. its freakin bizar ! Ruu matches and the bootloader is locked, ruu runs succesfull but the phone does not boot up..... Unlocking the bootloader is succesfull but the bootloader remains locked !
:banghead: i cant seem to understand this !

Is your recovery CWM or stock? If you were running ARHD I suppose you had a custom recovery aswell?
As far as i know RUU won't work until you flash stock recovery.
Hope this helps

basd43 said:
Is your recovery CWM or stock? If you were running ARHD I suppose you had a custom recovery aswell?
As far as i know RUU won't work until you flash stock recovery.
Hope this helps
Click to expand...
Click to collapse
Yes that's an option, but i tested a ruu once with custom recovery,kernel and rom and it worked flawlessly ! The main problem at this moment is that he flashes the .bin code and that the bootloader remain locked ! The commands are correct, but it refuses to unlock ......

Mr Hofs said:
Yes that's an option, but i tested a ruu once with custom recovery,kernel and rom and it worked flawlessly ! The main problem at this moment is that he flashes the .bin code and that the bootloader remain locked ! The commands are correct, but it refuses to unlock ......
Click to expand...
Click to collapse
Did he try to flash a custom rom despite the fact the boorloader says locked? Maybe it just says locked but is actually unlocked? Happend to me once and after rebooting into bootloader after flashing it said unlocked... dont ask why, just happened...

Yes i believe he tried that too, got faile attempt remote not allowed error.....he rebooted the bootloader a couple of times and it said unlocked indeed, maybe that's the solution....keep rebooting the bootloader untill it says unlocked and then start flashing directly
Its giving me a headache ..... Been thinking about this for 2 days already

basd43 said:
Is your recovery CWM or stock? If you were running ARHD I suppose you had a custom recovery aswell?
As far as i know RUU won't work until you flash stock recovery.
Hope this helps
Click to expand...
Click to collapse
You don't need to flash anything to use an ruu. The only thing that you need is a locked bootloader.
As the other user said. It may be reporting status wrongly. If you're going to try the ruu again. I suggest running fastboot OEM lock first just to make sure
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
You don't need to flash anything to use an ruu. The only thing that you need is a locked bootloader.
As the other user said. It may be reporting status wrongly. If you're going to try the ruu again. I suggest running fastboot OEM lock first just to make sure
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes .... But can you tell me why the ruu ended up as successful ? I just dont seem to get that ?
Another thing ! If you bootloader says LOCKED you should also have full warranty !! If nothing else helps its best to go to the htc service center

[HELP] How can I unlock Bootloader while S-OFF (without su) - HTC One m7 4.4.3

I'm in a situation with my HTC One m7 4.4.3 Verizon where:
- I'm S-OFF
- Bootloader is locked
- Stock Recovery
- su no longer available due to OTA upgrade
Does anyone know how I can once again unlock my bootloader?
I have tried following methods but none of them worked:
1. reset lock status. It doesn't work because I don't have su anymore and I don't know how I can install it with stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475914
2. flash custom recovery TWRP using fastboot, but I'm getting FAILED (remote: not allowed) error, probably due to I'm still in locked bootloader.
3. tried running Sunshine, but it thinks that I'm already rooted and is looking for su.
http://forum.xda-developers.com/showthread.php?t=2792487
so, the challenge is: how do I get my unlock bootloader back while on S-OFF without su installed?
Any help is much appreciated.

smallwei said:
I'm in a situation with my HTC One m7 4.4.3 Verizon where:
- I'm S-OFF
- Bootloader is locked
- Stock Recovery
- su no longer available due to OTA upgrade
Does anyone know how I can once again unlock my bootloader?
I have tried following methods but none of them worked:
1. reset lock status. It doesn't work because I don't have su anymore and I don't know how I can install it with stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475914
2. flash custom recovery TWRP using fastboot, but I'm getting FAILED (remote: not allowed) error, probably due to I'm still in locked bootloader.
3. tried running Sunshine, but it thinks that I'm already rooted and is looking for su.
http://forum.xda-developers.com/showthread.php?t=2792487
so, the challenge is: how do I get my unlock bootloader back while on S-OFF without su installed?
Any help is much appreciated.
Click to expand...
Click to collapse
s-off > unlocked bootloader. you dont need the bootloader unlocked to flash recovery. If you are s-off you have full control of phone.
what command are you using to flash recovery? when you do "fastboot devices" in bootloader what does it say?

Hi, thanks for the quick response. Here is the command and output:
fastboot flash recovery openrecovery-twrp-2.7.1.1-m7wlv.img
C:\temp\Android_Root\htc_one>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7wlv.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.276s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.311s
Here is the fastboot devices output:
C:\temp\Android_Root\htc_one>fastboot devices
FA37TS911824 fastboot

What's the output when you type "fast boot devices"
Sent from my iPhone 6 using Tapatalk

Here is the fastboot devices output:
C:\temp\Android_Root\htc_one>fastboot devices
FA37TS911824 fastboot

smallwei said:
Here is the fastboot devices output:
C:\temp\Android_Root\htc_one>fastboot devices
FA37TS911824 fastboot
Click to expand...
Click to collapse
cool so fastboot is seeing the phone.
follow this post and see if you can flash recovery via RUU:
http://forum.xda-developers.com/showpost.php?p=52987867&postcount=2

Thanks much.
If I understand it correctly, flash RUU will wipe out the phone completely, is it true?
I'm holding this method off as the last resort to try after I exhaust all other options.

smallwei said:
Thanks much.
If I understand it correctly, flash RUU will wipe out the phone completely, is it true?
I'm holding this method off as the last resort to try after I exhaust all other options.
Click to expand...
Click to collapse
if you do a full firmware it will wipe. this should be JUST recovery. But i would recommend backing up internal storage. I have not tried this method.

Gotcha. Thanks again. I'll give it a shot.

It works! Thanks so much synisterwolf! You're genius!
I used the Recovery RUU from the following link:
http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643

smallwei said:
It works! Thanks so much synisterwolf! You're genius!
I used the Recovery RUU from the following link:
http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
Click to expand...
Click to collapse
now i wonder if you can do the "fastboot flash recovery" way.
anyways, you can now unlock bootloader if you chose too by following the original guide you posted. Let me know if you need anymore help.
:victory:

synisterwolf said:
now i wonder if you can do the "fastboot flash recovery" way.
anyways, you can now unlock bootloader if you chose too by following the original guide you posted. Let me know if you need anymore help.
:victory:
Click to expand...
Click to collapse
Yes, fastboot flash recovery also works after I changed bootloader to unlocked.

smallwei said:
Yes, fastboot flash recovery also works after I changed bootloader to unlocked.
Click to expand...
Click to collapse
I think you're correct on having hboot unlocked. I'm used to engineering hboots from the past. Where it was required to unlock before flashing recovery. With the standard hboot, I guess you need to flash the insecure boot IMG, so you write to system then install su to unlock. Glad you got it working though.
Happy flashing.
Sent from my iPhone 6 using Tapatalk

The other way that I have success by using temp root Towelroot. After rooted I use scooty menthod to lock/unlock bootloader without htcdev. From ADB with code from Scooty I can get unlock bootloader. From this step I can flash TWRP and SuperSU. Zip

[Q] couldnt flash stock recovery

i want to flash stock recovery because i want to update ota i already have re locked my bootloader but when i try to flash stock reocvery i get following error in command prompt
C: \ fastboot> fastboot flash recovery recovery.img
sending 'revocery' (16384 KB) ...
OKAY [2.114s]
writing 'revocery' ...
(Bootloader) signature checking ...
FAILED (remote: signature verify fail)
finished. total time: 2.120s
i am sure i m flashing right stock recovery plz help me i need this stock recovery
i have s-on

Hmm check the recovery again, the usual recoveries are 14 mb or 24 mb .... Haven't seen a 16+ mb one

Mr Hofs said:
Hmm check the recovery again, the usual recoveries are 14 mb or 24 mb .... Haven't seen a 16+ mb one
Click to expand...
Click to collapse
if recovery is from older version of rom is this also might be a reason of remote signature fail?

n70shan said:
if recovery is from older version of rom is this also might be a reason of remote signature fail?
Click to expand...
Click to collapse
ok i have tried recovery from same rom version but still it says remote signature fail..... please help i need stock recovery ... what options do i have now?

n70shan said:
ok i have tried recovery from same rom version but still it says remote signature fail..... please help i need stock recovery ... what options do i have now?
Click to expand...
Click to collapse
i already have re locked my bootloader but when i try to flash stock reocvery i get following error in command prompt
Click to expand...
Click to collapse
unlock your bootloader, how do you want to flash a recovery if your bootloader is locked.

BerndM14 said:
unlock your bootloader, how do you want to flash a recovery if your bootloader is locked.
Click to expand...
Click to collapse
i m trying to flash stock recovery... is it necessary to have an unlocked bootloader for stock recovery as well?

All things regarding flashing needs to be done with an unlocked bootloader. Except ruu files on a s-on system.