Relocked Bootloader--Cant unlock it back again....?? - HTC Desire 510

Hey guys Ive ben having an issue with unlocking bootloader on my HTC Desire 510. I had already unlocked it but I accidentaly relocked it using the Windroid App. Ive flashed the Unlock code given to me from HTCDEV.COM through CMD -- the Unlock window appears but after selecting Unlock bootloader all I get is the red lettering on top warning about 'its for Developer use only'... Also Ive tried to flash boot img and recovery.zip and this is what I get every time - - - sending 'recovery' (20918 KB)... OKAY [ 2.132s] writing 'recovery'... (bootloader) signature checking... FAILED (remote: signature verify fail) finished. total time: 4.716s - - any suggestions??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

soLo1Blue said:
Hey guys Ive ben having an issue with unlocking bootloader on my HTC Desire 510. I had already unlocked it but I accidentaly relocked it using the Windroid App. Ive flashed the Unlock code given to me from HTCDEV.COM through CMD -- the Unlock window appears but after selecting Unlock bootloader all I get is the red lettering on top warning about 'its for Developer use only'... Also Ive tried to flash boot img and recovery.zip and this is what I get every time - - - sending 'recovery' (20918 KB)... OKAY [ 2.132s] writing 'recovery'... (bootloader) signature checking... FAILED (remote: signature verify fail) finished. total time: 4.716s - - any suggestions??
Click to expand...
Click to collapse
If you haven't already done so, go back through the process and generate new tokens to get new unlock.bins, then it should work. Also, if you're gonna post screenshots, don't use Drive. You didn't allow them to be viewed publicly, just use imgur or something similar.

dip_spit said:
If you haven't already done so, go back through the process and generate new tokens to get new unlock.bins, then it should work. Also, if you're gonna post screenshots, don't use Drive. You didn't allow them to be viewed publicly, just use imgur or something similar.
Click to expand...
Click to collapse
Thank you dip_spit I did what you mentioned but unfortunetly I keep getting the same result... =/ . An currently sending an email to a reply I got from HTCDEV.COM. Hopefully they can assist if no one elsa has had this same issue...

soLo1Blue said:
Thank you dip_spit I did what you mentioned but unfortunetlly I keep getting the same result... =/ . An currently sending an email to a reply I got from HTCDEV.COM. Hopefully they can assist if no one else has had this same issue...
Click to expand...
Click to collapse
...
Forget it... Issue resolved...

Mind sharing your solution?

Related

htcdev unlock step 9

For some reason after sending my htc one in for the camera repairs, i think htc reset my phone back to factory setting. They relocked it and everything.
Now i am trying to unlock it again but i can't seem to get it to work
im stuck on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ive tried it many times and it won't show me the next step on my phone where it asks me if im sure about unlocking my phone. Can someone help?
Windows 8.1? Hboot version?
Windows 7. Hboot 1.55 or 1.54.
Sent from my HTC One using xda app-developers app
I have the same problem, which existed already when i brought the phone. I extensively searched the net but found nothing. There are some post from others with the same problem but they never got an answer
I tried it with HBoot 1.54 and 1.55 - Windows 7 x64, Ubuntu x64 and x32.
vietkangta said:
For some reason after sending my htc one in for the camera repairs, i think htc reset my phone back to factory setting. They relocked it and everything.
Now i am trying to unlock it again but i can't seem to get it to work
im stuck on this
Ive tried it many times and it won't show me the next step on my phone where it asks me if im sure about unlocking my phone. Can someone help?
Click to expand...
Click to collapse
Exactly the same problem... Does it give an error about unable to load splash if you try again?
I set mine back to stock for a repair, and since having it back i can't unlock it.
Either something we used to lock the boot while s-off has corrupted a partition, OR the repair place has made it so we can't unlock it.
When you first booted your phone, did you get the green recovery logo come up as if it was installing something? I did I think the repair centre has locked it down.
Hboot 1.55.
Definitely not a driver/ Windows issue.
Looking at other forums, the evo had the same issue which is fixed by running an ruu, butthe one ii want isn't out. (3.62.401.1).
I've tried flashing just firmware to no avail.
backfromthestorm said:
Exactly the same problem... Does it give an error about unable to load splash if you try again?
I set mine back to stock for a repair, and since having it back i can't unlock it.
Either something we used to lock the boot while s-off has corrupted a partition, OR the repair place has made it so we can't unlock it.
When you first booted your phone, did you get the green recovery logo come up as if it was installing something? I did I think the repair centre has locked it down.
Hboot 1.55.
Definitely not a driver/ Windows issue.
Looking at other forums, the evo had the same issue which is fixed by running an ruu, butthe one ii want isn't out. (3.62.401.1).
I've tried flashing just firmware to no avail.
Click to expand...
Click to collapse
I didnt get anyhting special. And mines was never s-off. But ive been searching and people say it might be related to the 4.4 update.

Verizon prepaid Desire 626 LOCKED BOOTLOADER

I got the Verizon prepaid Desire 626 and cant root bc of the S-ON. There is NO option for "OEM unlocking". The bootloader is LOCKED by default. Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same phone. Same Problem.
Hello.
I have the same phone with the same problem. However I was able to temp-root this device but alas when you reset...it looses root. I tried to use Sunshine.apk, same problem. I was wondering though if the carrier be unlocked first then proceed to unlock the boot loader, might be able to perm root the device. IDK just brainstorming to myself. I know there is a way to unlock the boot loaders for all devices I am actually going to try a different solution called XTC2clip.
Looking at the same situation with this device right now. Most all Verizon prepaid have the Bootloader locked. But I think I might have a solution for this other than sunshine going to give it a try soon.
This is actually htc_a32wlpp. Have to get into RUU mode before you find this out.
I get this when attempting in RUU
C:\Users\User>fastboot oem get_identifier_token
< waiting for device >
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.593s]
finished. total time: 0.599s
Reading that makes me think there might be some hope.. Though I do not understand why it is giving out info about frp. As for oem unlock there is no option to turn this on at least within the OS. Going to dig around some and try a few things. Does anyone have any solution for this handset? Know if Sunshine works? Chimera? xtc2clip? I haven't checked these just yet.
I can get EDL mode as well using my cable with these Desire 626's but so far I havent been able to do anything as the 8909 loaders I have do not work on this model and don't remember right now if they did on the others either.

Unlock Bootloader Huawei P Smart 2018 (FIG) using PotatoNV

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PotatoNV Download
How to use PotatoNV
Remember to change Bootloader to Kirin 659 (B)
Huawei P Smart 2018 STF testpoint (watch this video from beginning to min 5:10)
Why open up the device when you can unlock it with DCUnlocker?
Shume said:
Why open up the device when you can unlock it with DCUnlocker?
Click to expand...
Click to collapse
Program features:
- Setting or removing the FBLOCK flag (unlocking all sections and commands, works even on EMUI 9), useful when you do not want to erase data when unlocking. + bonus: you can flash erecovery_ramdisk in fastboot.
- Writing your unlock key
- Changing (restoring) the serial number and BOARDID
- It's Free
follow
Disclaimer : I'm not responsible for any harm happen to your device
Could you please just explain to me what the test point is and how do I do it? I have a fig lx1 but I have no idea what this test point is and the videos on YouTube is only confusing me further I need to be unlocked bro like for real
Can it be used on this
G1-killeR said:
Could you please just explain to me what the test point is and how do I do it? I have a fig lx1 but I have no idea what this test point is and the videos on YouTube is only confusing me further I need to be unlocked bro like for real
Click to expand...
Click to collapse
Ignore this I figured it out
Hi! Can i relock the bootloader? I'm trying with the code that PotatoNv gave me to unlock it, but now i can't relock it
Just follow this guide it should fix you device... Im not sure if you can relock the code again cause but why would you want to do that in anycase
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
hello i own FIG LA1 4GB RAM 2018 P SMART .. POTATO NV CANT DETECT MY DEVCE BUT I CAN SEE HUAWE SERVICE DRIVER PROPERLY ON MY DEVICE LIST PLIZ HELP ME
I did the procedure and unlock the botloader, but I do not know what to do to install the custom recovery, I try through fastboot mode by turning off the phone and connecting it with volume - but it is not recognized when I write ADB devices :c, I do not know if it matters but I have the latest version of emui.
Pd: this method is easier and faster than with DC unlocker, just know how to uncover the phone without damaging anything.
cerberoxxz said:
Hi! Can i relock the bootloader? I'm trying with the code that PotatoNv gave me to unlock it, but now i can't relock it
Click to expand...
Click to collapse
Me too, i can't relock the bootloader! I don't know why!!!!
fra18061988 said:
Me too, i can't relock the bootloader! I don't know why!!!!
Click to expand...
Click to collapse
Just do this:
Open PotatoNV
Connect phone in fastboot mode
Uncheck Disable FBLOCK
Press Start
cerberoxxz said:
Just do this:
Open PotatoNV
Connect phone in fastboot mode
Uncheck Disable FBLOCK
Press Start
Click to expand...
Click to collapse
YEEEEEEEEEES!!!!!! It works!!!!! Thank's a lot!!!!!!!!!!
cerberoxxz said:
Just do this:
Open PotatoNV
Connect phone in fastboot mode
Uncheck Disable FBLOCK
Press Start
Click to expand...
Click to collapse
Sorry, but the operation only worked on one device (single sim). With the other (same model of smartphone but dual sim), once the procedure is completed, the error "Your Device Has Failed Verification And May Not Work Properly" appears. The phone gets stuck on that screen! If I repeat the procedure by checking the item "Disable FBLOCK" it works but the bootloader remains unlocked. I also tried flashing the bootloader for Kirin659 (A) and Kirin659 (B) but nothing.
How can I solve?
Good news, I solved it by downloading and installing a rom in eRecovery mode!!!! Now the bootloader is also locked in the other smartphone!
Doing this process can I change the ROM FIG-LX3 to FIG-LX1?

Question How to Change to a different region rom in locked bootloader

I flashed miui 13.0.9 global in Indian varient and mistakenly locked it, so I have camera issues (green tint) I tried to add mi account to unlock the bootloader but it show device basic verification failed, anyway to change the rom in locked state?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unlock the bootloader
Have you tried formatting data on that locked state to maybe fix that device verification? I don't know if it works but you can use the OTA update rename trick to I guess switch region on locked bootloader. I don't know if it works because I personally haven't tested it. It works in downgrading though.
BigChungus321 said:
Have you tried formatting data on that locked state to maybe fix that device verification? I don't know if it works but you can use the OTA update rename trick to I guess switch region on locked bootloader. I don't know if it works because I personally haven't tested it. It works in downgrading though.
Click to expand...
Click to collapse
Aight Imma try it but I heard that it has been patched
krxshnendu said:
Aight Imma try it but I heard that it has been patched
Click to expand...
Click to collapse
Don't. Bad idea. Never downgrade by changing and renaming the zip file after verification in updater app WHILE still being locked. Chances are you might brick your phone.
If you have unlocked before, try to run "fastboot oem unlock" in fastboot mode to unlock it again. You should be able to unlock it without needing Mi Account.
Splatink said:
Unlock the bootloader
Click to expand...
Click to collapse
That's the issue
x3r0.13urn said:
Don't. Bad idea. Never downgrade by changing and renaming the zip file after verification in updater app WHILE still being locked. Chances are you might brick your phone.
If you have unlocked before, try to run "fastboot oem unlock" in fastboot mode to unlock it again. You should be able to unlock it without needing Mi Accoun
Click to expand...
Click to collapse
x3r0.13urn said:
Don't. Bad idea. Never downgrade by changing and renaming the zip file after verification in updater app WHILE still being locked. Chances are you might brick your phone.
If you have unlocked before, try to run "fastboot oem unlock" in fastboot mode to unlock it again. You should be able to unlock it without needing Mi Account.
Click to expand...
Click to collapse
fastboot oem unlock mode like from cmd? Like (example) fastboot flash recovery?
x3r0.13urn said:
Don't. Bad idea. Never downgrade by changing and renaming the zip file after verification in updater app WHILE still being locked. Chances are you might brick your phone.
If you have unlocked before, try to run "fastboot oem unlock" in fastboot mode to unlock it again. You should be able to unlock it without needing Mi Account.
Click to expand...
Click to collapse
Not working
Alright that didn't work as expected. I noticed mi unlock flashed unlock.bin to the unlock partition at first time unlocking bl, so I assume that partition would still be intact even you have relocked it.
Try to unlock it using mi unlock and your account which use to unlock, no need to bind the mi account again since it won't work anyway.

Question Help Unlock Bootloader T-Mobile Oneplus 10pro 5G

I think I am doing everything correctly, but after it says device unlocked, it is not, and cmd doesn't do anything . I cmd fastboot unlocking, or OEM unlock and then nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Loustsoul said:
I think I am doing everything correctly, but after it says device unlocked, it is not, and cmd doesn't do anything . I cmd fastboot unlocking, or OEM unlock and then nothing.
Click to expand...
Click to collapse
That's just flashing the unlock token, after that you need to run the actual unlock command in fastboot. It's either:
fastboot oem unlock
or
fastboot flashing unlock
Can't remember which one it was, it's been awhile since I unlocked mine. But that command has to be run after using the token and it will show the bootloader unlock screen on your phone and the have to select to unlock it using the volume and power keys to confirm after.
jeffsga88 said:
That's just flashing the unlock token, after that you need to run the actual unlock command in fastboot. It's either:
fastboot oem unlock
or
fastboot flashing unlock
Can't remember which one it was, it's been awhile since I unlocked mine. But that command has to be run after using the token and it will show the bootloader unlock screen on your phone and the have to select to unlock it using the volume and power keys to confirm after.
Click to expand...
Click to collapse
I did both. That's what I meant by nothing after. My phone stays in fastboot and does not change or ask to unlock.
Loustsoul said:
I did both. That's what I meant by nothing after. My phone stays in fastboot and does not change or ask to unlock.
Click to expand...
Click to collapse
Sorry I missed that part of your post. I'm not sure then as that should bring you to the confirm screen to finish the unlocking.
You should read this..
T-Mobile 10 Pro BL unlocking
I just got the OP 10 Pro for my girl and I and I'm having some difficulty attempting to unlock the bootloader. Looks like it'll require an unlock token (bin) from OP like the previous models however on my OP 9 I didn't request an unlock token, I...
forum.xda-developers.com
I keep getting this error when flashing unlock token.bin. can anyone help? Thanks

Categories

Resources