As the title suggest, I'm trying to unlock my bootloader but every time it fails because I have too many links. No idea what that means, but the more severe problem is that with other users the phone will be unlocked, but mine is still locked.. What should I do? Thanks in advance.
Related
My phone suddenly started to go into a bootloop. I'd not unlocked the bootloader or anything. I then tried a factory reset but after an hour the phone crashed and went into a bootloop again.
Then I tried Factory Reset again but it no longer works and now the phone keeps going into the recovery screen.
I thought i'd try re-flashing the stock ROM so I got an unlock bootloader code from HTC.
I get the screen saying are you sure you want to unlock, I select yes but i continually get the error message
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
And the bootloader remains locked.
Now all I have is a phone with a locked bootloader that will only go to the fastboot/hboot screen
I've looked at several suggestions on the forum but I cant seem to get any to work. This is a UK unbranded handset
Thanks in advance
If you have not unlocked, then just go to service centre as it is still under waranty.
My bootloader is re-locked. Now i want to unlock it again but it always gives an error stating "Failed (phone is already rooted)". I have tried with flashtool and cmd-fastboot method but the result is always the same. In service menu bootloader unlock allowed says yes. Is there any alternate way to unlock bootloader once again? I can't seem to find this error on Google so am really confused what to do.
So I'm out of answers currently and would like some help on this one
I installed Cyanogenmod from their website
Installed their rom, recovery
Locked the bootloader since that's what u should do
Today I tried to install a new update from cyanogenmod, it rebooted, and the recovery screen is only showing a black screen and every 5 seconds it will give a white flicker
I tried to unlock the bootloader again but it shows "FAILED (remote: oem unlock is not allowed)"
And I'm not able to get back into android, it will show "ID: xxxxxxxxxxxx" at the bottom and tries to go back into recovery
Help
why did you lock the bootloader when you aren't running the stock rom?
all the modding threads explicitly threads say to avoid doing this otherwise you'll have serious issues.
2x4 said:
why did you lock the bootloader when you aren't running the stock rom?
all the modding threads explicitly threads say to avoid doing this otherwise you'll have serious issues.
Click to expand...
Click to collapse
In all the years of being on xda. I've never seen anyone mention this
wtf... why do use lock bootloader when you arent on stock? You only possibility is to try to get fastboot access to unlock it again...
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Edit:
Tried multiple unlock keys from HTC
Tried factory reset
Booting into recovery phone image comes up with red warning icon in it and nothing happens. Need to power down and restart. Seems the recovery partition is possibly hosed.
Dissectional said:
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Click to expand...
Click to collapse
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
SacredDeviL666 said:
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
Click to expand...
Click to collapse
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Dissectional said:
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Click to expand...
Click to collapse
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
afuller42 said:
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
Click to expand...
Click to collapse
You may be right about the fingerprint scanner. I will look into that when I get it unlocked. That is the main goal right now.
If you are s-OFF the phone will show as "s-off, locked" but still, in fact, be unlocked.
the command to lock and unlock will not work.
I was confused to but when i checked the s-off thread i saw that it will ask if it should be "s-off unlocked or "s-off locked" and recomended Locked, but had no difference other then visual.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
And btw, lock status should not affect the fingerprint scanner.
Confirmed it doesn't I am s-0ff and unlocked, twrp and custom rom. Fingerprint working 100%
the exclamation on booting to recovery just indicates that you are on stock recovery...
try the steps here for recovery flashing... and unlocking again... if it might help... http://forum.xda-developers.com/showpost.php?p=66713447&postcount=1
You could try contacting Scotty, might have a way like on previous devices to lock/unlock your bootloader without htcdev.com once S-OFF (DO NOT use the codes for M7 M8 or M9)
http://forum.xda-developers.com/showthread.php?t=2470340
Shouldn't this work?
fastboot oem unlock
Are your developer options enabled right now. And did you check the box to allow bootloader unlock again?
Sent from my HTC 10 using XDA Labs
Some luck
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
glad its sorted for you and back to flashaholic mode
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
Sounds like your Environmental PATH is set to just that one folder.
Windows?
There's some good threads here on XDA,
http://forum.xda-developers.com/showthread.php?t=1161776
Glad you got it working though!
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
gercdgcat said:
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
Click to expand...
Click to collapse
Thanks for replying - could you perhaps write a guide as to exactly how you unlock your bl after using fastboot lock?
I have seen a few folks who appear stuck at that point and I and they would be happy campers if they could get around that!!!
Thanks!
EDIT: I added a comment about "correct stock" to the first post... This may be key to the folks that are having trouble...
You might look at thread
https://forum.xda-developers.com/moto-z-play/help/please-help-urgently-t3814260
But I guess I would have to call anyone who successfully locks and unlocks again their bootloader as darn lucky. Some, (many?) can't.
In the end I still have to ask "why the heck are you locking your phone" - what could you possibly gain? It's totally unnecessary. it can be a very expensive little line of code.
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
pkadavid said:
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
Click to expand...
Click to collapse
LOL - right! Thanks!!!
bump
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
IncendiaryPyro said:
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
Click to expand...
Click to collapse
How's the 2xl?
hithere
KrisM22 said:
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Click to expand...
Click to collapse
I prefer stock without modifications but sometimes when i have time to try news modifications or roms i used to unlocked the phone and after this relock again, the process that i use is very simple, i just unlock with the same code that Motorola gaves to unlock bootloader, i don't have sure but if you request unlock codes to many times can be a problem but i use the same code and works good.
Basically: relock as are specifcified in another topic in this device forum( using the last stock version that you used)
And after this unlock with code again
Obs.: Is not recommended to unlock/relock to many times.
Obs2.: I only did this three times and i don't know if has a limit
bumpsi
It is my opinion also that relocking is a bad idea. But if someone likes to do it, eg to get Google Pay working without Magisk, why do you want to warn him?
Relock only is possible in combination with flashing a complete correctly firmware. If something is wrong with the firmware you flash, relocking won't succeed. Your device won't be locked if it does not fully succeed or the firmware is not correctly signed. The unlock code is supposed to stay valid, you should be able to unlock your device as many times as you want using the same code.
a) is fine, but does not consider Android SafetyNet
b) is just wrong, and this already was written in a comment.
Please do not bump wrong warnings.