Database Info

[SOLVED] Relocked Bootloader.. Bricked

I messed it really seriously
So I have a rooted an HTC explorer and wanted to update to the new OTA update. I couldnt for security issues (obviously) so I decided that maybe I relock boot loader and try again.. byt simillar issue appear. now I have a locked boot loader and cannot boot phone, it just goes to the fastboot menu again. On top of it it says "RELOCKED" "Security warning"
Tried fastboot oem unlock command but this error appears:
Code:
C:\Users\me\Desktop\file>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Press any key to continue . . .
Htc standard unlocking bootloader method gives signature error.
need a solution, will donate generously if someone gives a solution.
Dont want to send it to repair!!
After some reading, maybe having a custom kernel made it brick
any way out?? no goldcard without adb..
Is it possible to create a goldcard using another HTC phone that will work on mine and flash a RUU.exe??

jaggyjags said:
I messed it really seriously
So I have a rooted an HTC explorer and wanted to update to the new OTA update. I couldnt for security issues (obviously) so I decided that maybe I relock boot loader and try again.. byt simillar issue appear. now I have a locked boot loader and cannot boot phone, it just goes to the fastboot menu again. On top of it it says "RELOCKED" "Security warning"
Tried fastboot oem unlock command but this error appears:
Code:
C:\Users\me\Desktop\file>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Press any key to continue . . .
Htc standard unlocking bootloader method gives signature error.
need a solution, will donate generously if someone gives a solution.
Dont want to send it to repair!!
After some reading, maybe having a custom kernel made it brick
any way out?? no goldcard without adb..
Is it possible to create a goldcard using another HTC phone that will work on mine and flash a RUU.exe??
Click to expand...
Click to collapse
Does the HTC DEV site have this device available for unlocking the bootloader? Just a thought
Sent via my Iced Tapatalk
Edit, you might check out this post ...
http://forum.xda-developers.com/showthread.php?p=20763212

lol, I wrote that tutorial
Found the cause, had a custom kernel and you cannot unlock the bootloader in that case. yes, unlocking bootloader is supported but not after modifiying the stock kernel., I will be phoning HTC support and I suppose will have to send them my phone for repair..
thank you for your help, by the way

jaggyjags said:
lol, I wrote that tutorial
Found the cause, had a custom kernel and you cannot unlock the bootloader in that case. yes, unlocking bootloader is supported but not after modifiying the stock kernel., I will be phoning HTC support and I suppose will have to send them my phone for repair..
thank you for your help, by the way
Click to expand...
Click to collapse
Haha. Well then guess you know what you're up against.
Facepalm for me. You're welcome. Wish I could be of more help.
Sent via my Iced Tapatalk

Unlock as you did the first time using htc de, unlocktoken is the same

That's bad luck...I didn't read this thread before. So, I can't boot my htc desire s. It only starts in the bootloader.
@jaggyjags: Do you mean, that I must take all the steps of the htc instruction?

DWolter07 said:
That's bad luck...I didn't read this thread before. So, I can't boot my htc desire s. It only starts in the bootloader.
@jaggyjags: Do you mean, that I must take all the steps of the htc instruction?
Click to expand...
Click to collapse
no, if you unlocked the bootloader using htcdev.com before just do the last step typing "fastboot oem Unlocktoken.bin" With command prompt in the folder you placed the files you downloaded.
I mispelled the command and thought I had bricked it and wrote this thread.
hope this helps other people.

jaggyjags said:
no, if you unlocked the bootloader using htcdev.com before just do the last step typing "fastboot oem Unlocktoken.bin" With command prompt in the folder you placed the files you downloaded.
I mispelled the command and thought I had bricked it and wrote this thread.
hope this helps other people.
Click to expand...
Click to collapse
Thanks, just forgot where I put the token but all good now.
From adb directory with the token,
Code:
fastboot oem lock
image,
{
"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"
}
Then shows relock with tampered,
Then RUU same image,
Will remove black Watermark "tampered"

Relock bootloader help

I have an f8331 n I didn't back up the TA. IS there any way to relock the bootloader? Or to at least remove the message that say "device has been unlocked cannot be trusted" . . It's in Android nougat version 7.0 plz help

Use flashtool
Relock bootloader
Wait for flashtool to reflash your software it takes some time to finish.
After done retart your phone the warning is gone and your ohonenstart normally but drm is gone

For the flash tool would I use sonys flash tool "Emma" or should I use the one from
karrouma said:
Use flashtool
Relock bootloader
Wait for flashtool to reflash your software it takes some time to finish.
After done retart your phone the warning is gone and your ohonenstart normally but drm is gone
Click to expand...
Click to collapse
For the flash tool would I use sonys flash tool "Emma" or should I use the one from flashtool. Net??

Tech 101 said:
For the flash tool would I use sonys flash tool "Emma" or should I use the one from flashtool. Net??
Click to expand...
Click to collapse
From flastool select blue the second line , second option on the left

i did it n my device says it has failed verification and will power off

Tech 101 said:
For the flash tool would I use sonys flash tool "Emma" or should I use the one from flashtool. Net??
Click to expand...
Click to collapse
but keep in mind relocking BL will render the stock camera unusable, and you'd be getting this annoying error : "camera in use by another app"

i fix it
Tech 101 said:
I have an f8331 n I didn't back up the TA. IS there any way to relock the bootloader? Or to at least remove the message that say "device has been unlocked cannot be trusted" . . It's in Android nougat version 7.0 plz help
Click to expand...
Click to collapse
1- relock it using flash tool
2-go to xperia companion => software repair (make sure to backup what you need on pc).
3- put your device on flash mode and start (it will take 10-20 min) (it will give you android 7.1.1), dont start it yet.
4- unlock the bootloader on fasboot mode [turn it off, volume up, put usb and write the cmd code in adb folder (hold shift and right click) (fastboot -i 0x0fce oem unlock 0x(your code)) and restart it.
5-Install kernel for your device - thanks to "AndroPlus": "https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8Y1FZSmMwM1BOZDQ" download xz_andropluskernel_v23.zip, open it and put the img file in the adb folder, and flash on cmd (fastboot flash boot boot.img) then restart it.
6-now the cam will work normally, you can also flash twrp, download it , put it in the adb folder, open cmd and write (fastboot flash recovery twrp-3.1.0-0-kagura.img) and restart it.
7- you can also install supersu 2.79 from twrp and you will have root
-- you can download adb/fasboot tools from here (downloadmirror.co/29Xn/adb-setup-1.4.3.exe[

This way he will end up in exactly the same point he has started Repairing w Xperia Companion doesn't bring back DRM keys. Also, after unlocking bootloader again the message "device has been unlocked cannot be trusted" will still pop up at boot.

S1gma said:
This way he will end up in exactly the same point he has started Repairing w Xperia Companion doesn't bring back DRM keys. Also, after unlocking bootloader again the message "device has been unlocked cannot be trusted" will still pop up at boot.
Click to expand...
Click to collapse
it will always pop up, you either have it with rooted 7.1.1 drm fixed all working
or you need to lock bootloader, flash stock 6.0.1, recover the ta img and upgrad it to 7.1.1 normally with no root.

Ok, let's clarify a bit. The OP stated he don't have TA backup. So there are two ways to choose:
1) Leave bootloader unlocked and use DRM fix (eg. Androplus Kernel).
This way the message "device has been unlocked cannot be trusted" will still pop up at boot, but OP will be able to use DRM based features (super-vivid screen, sound enchantment, low-light camera).
2) Lock bootloader. This way OP will get rid of "device has been unlocked cannot be trusted" message but also will loose drm based functions. Also there is possibility, that the camera will stop working at all.
To lock bootloader you have to:
1) Flash unmodified firmware using flashtool (eg. newest Android 7.1.1) wiping all data (check all marks under "wipe")
{
"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"
}
2) Using flashtools BLU icon lock bootloader.
The phone should boot up. You don't have to downgrade to lock/unlock bootloader.
As for the failed verification error - just unlock bootloader using flashtool and start over (either with 1. or 2.).

Question How re-lock bootloader asus rog 5?

Hello.. I opened the bootloader
How do I re-lock it again?
And if I close it, can I open again?
Thank you

have u try fastboot oem lock ?

Edit: The lock command has been found.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com

twistedumbrella said:
Code:
fastboot oem asus-lock
Click to expand...
Click to collapse
I tried it. Not working error code in fastboot.. But on rog phone 3 work fine..
Any solution?

mustafa.devel said:
I tried it. Not working error code in fastboot.. But on rog phone 3 work fine..
Any solution?
Click to expand...
Click to collapse
Is there a specific error code or does it just say "error code"?

twistedumbrella said:
Is there a specific error code or does it just say "error code"?
Click to expand...
Click to collapse
I don't remember exactly. But i think says Command wrong

Edit: The lock command has been found.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
mustafa.devel said:
I don't remember exactly. But i think says Command wrong
Click to expand...
Click to collapse
Same for "lock"?
Always possible they didn't have time (or decided against) their custom command

I am getting this error whenever I try to relock my bootloader
{
"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"
}

phaw16 said:
I am getting this error whenever I try to relock my bootloader
View attachment 5388779
Click to expand...
Click to collapse
That means you are in the wrong fastboot.
There is bootloader and (userspace) fastboot. Use the one you weren't in when you got that error.
And again... You can't change your mind later. This is the third and final warning.

twistedumbrella said:
That means you are in the wrong fastboot.
There is bootloader and (userspace) fastboot. Use the one you weren't in when you got that error.
And again... You can't change your mind later. This is the third and final warning.
Click to expand...
Click to collapse
Hi sorry I'm puzzled what do you mean by this part (There is bootloader and (userspace) fastboot)
It doesn't matter for me if I lose the liberty of unlocking the boot loader in the future I just want to relock the bootloader so I can use my local apps.

phaw16 said:
Hi sorry I'm puzzled what do you mean by this part (There is bootloader and (userspace) fastboot)
It doesn't matter for me if I lose the liberty of unlocking the boot loader in the future I just want to relock the bootloader so I can use my local apps.
Click to expand...
Click to collapse
There are two interfaces for fastboot.
The one you enter when holding the volume button in the bootloader. You can get to the other using "fastboot reboot fastboot" from that one. You can also get to either using "adb reboot" and either bootloader or fastboot.
phaw16 said:
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
Click to expand...
Click to collapse
This phone doesn't have Knox, so it's unusual that apps would be able to detect something like that. Which app is it?
The standard for developers is SafetyNet attestation. That can be patched, but only if it's done right.

Hi I tried your suggestion.
1. I did adb devices to confirm if its being read by the PC.
2. I did adb reboot fastboot and after I entered fastboot mode its showing "fastbootd
3. I typed fastboot devices and it was confirmed I am on fastboot mode but then again I am on "fastbootd"
4. I tried fastboot reboot fastboot but I only got an error which is below.

phaw16 said:
Hi I tried your suggestion.
1. I did adb devices to confirm if its being read by the PC.
2. I did adb reboot fastboot and after I entered fastboot mode its showing "fastbootd
3. I typed fastboot devices and it was confirmed I am on fastboot mode but then again I am on "fastbootd"
4. I tried fastboot reboot fastboot but I only got an error which is below.
View attachment 5389425
Click to expand...
Click to collapse
My suggestion was to use the OPPOSITE of the one you tried, not to boot into it multiple ways.

So what do you mean not boot into it multiple ways?
I tried this too:
1. booted state in my normal homescreen
2. Opened adb tools and typed adb reboot fastboot.
3. tried fastboot oem lock.
fastboot oem is being read but the "lock" part is an invalid command.

FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed

Hi again, sorry if I am such a nuisance but I think I got the point here's what I did:
1. Open State - I removed my fingerprint and passcode
2. I did adb reboot bootloader
3. I tried these commands:
- fastboot oem lock (unknown command)
- fastboot oem asus-lock (unknown command)
- fastboot flashing lock (permission denied)
It's very hard to lock the freaking bootloader.

phaw16 said:
Hi again, sorry if I am such a nuisance but I think I got the point here's what I did:
1. Open State - I removed my fingerprint and passcode
2. I did adb reboot bootloader
3. I tried these commands:
- fastboot oem lock (unknown command)
- fastboot oem asus-lock (unknown command)
- fastboot flashing lock (permission denied)
It's very hard to lock the freaking bootloader.
Click to expand...
Click to collapse
Contact Asus. They should be able to help.

Seriously? I'm not warranty after tampering with my bootloader?

phaw16 said:
Seriously? I'm not warranty after tampering with my bootloader?
Click to expand...
Click to collapse
Yes, seriously.
I would ask Asus, the people who placed the lock on the device and then provided the app to remove it, the simple question "how would I lock my bootloader after it was unlocked?"

Will do thank you!

unlocking bootloader Pax M30 phone, fastboot "Not implemet."

I bought this phone because it was REAAAAAAAAAAALLY cheap: https://pagseguro.uol.com.br/para-seu-negocio/maquininhas/pagphone
I turned developers mode on, activated USB debugging, rebooted into bootloader mode, and got
[email protected]:~/Android/Sdk/platform-tools$ sudo $(which fastboot) flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
I think this means that unlocking is not available for this phone using fastboot.
Is there another way of unlocking it?
By the way, there was no OEM Unlock option on developer options on configurations.
The phone is from https://www.paxtechnology.com/m30 but customized to this payment processor on Brazil.
Also:
sudo $(which fastboot) flashing get_unlock_ability
FAILED (remote: 'Not implement.')
fastboot: error: Command failed

If OEM Unlock option isn't provided in Developer Options then it't not possible to unlock the bootloader: live with this.

Hi.
Mine has OEM Unlock option available on developer options but doesn't have the USB Debugging option.
By the way, after enabling OEM Unlock option, I accessed fastboot mode and could unlock the bootloader by using command:
"fastboot oem unlock"
"fastboot flashing unlock" command did not work.
Now I am trying to find any custom recovery that works with this phone and try to root it. No success so far.
{
"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"
}

brizziodf said:
Hi.
Mine has OEM Unlock option available on developer options but doesn't have the USB Debugging option.
By the way, after enabling OEM Unlock option, I accessed fastboot mode and could unlock the bootloader by using command:
"fastboot oem unlock"
"fastboot flashing unlock" command did not work.
Now I am trying to find any custom recovery that works with this phone and try to root it. No success so far.
View attachment 5517433
View attachment 5517431
Click to expand...
Click to collapse
Hi, are you from Brazil? Gonna check again on mine, gonna change to english and search for OEM

brizziodf said:
Hi.
Mine has OEM Unlock option available on developer options but doesn't have the USB Debugging option.
By the way, after enabling OEM Unlock option, I accessed fastboot mode and could unlock the bootloader by using command:
"fastboot oem unlock"
"fastboot flashing unlock" command did not work.
Now I am trying to find any custom recovery that works with this phone and try to root it. No success so far.
View attachment 5517433
View attachment 5517431
Click to expand...
Click to collapse
There's no OEM unlock on mine unfortunately

papavacuo said:
Hi, are you from Brazil? Gonna check again on mine, gonna change to english and search for OEM
Click to expand...
Click to collapse
Yes, I am.
Maybe different firmware versions. My brother's phone also has no OEM Unlock Option. His version is 13.1.06.
I think they removed that option at some point onwards.

brizziodf said:
Yes, I am.
Maybe different firmware versions. My brother's phone also has no OEM Unlock Option. His version is 13.1.06.
I think they removed that option at some point onwards.
Click to expand...
Click to collapse
my version is 13.1.06, I updated it right after I opened it. That's the reason then.

Anyone knows if it's possible to extract the ROM from his phone and put on mine? Or maybe get the firmware for the older 13.1.04 version somewhere else? Flashing a signed ROM isn't a problem right? No need to unlock.

brizziodf said:
Hi.
Mine has OEM Unlock option available on developer options but doesn't have the USB Debugging option.
By the way, after enabling OEM Unlock option, I accessed fastboot mode and could unlock the bootloader by using command:
"fastboot oem unlock"
"fastboot flashing unlock" command did not work.
Now I am trying to find any custom recovery that works with this phone and try to root it. No success so far.
View attachment 5517433
View attachment 5517431
Click to expand...
Click to collapse
Hello, have you done any additional steps in order to unlock the bootloader? I have version 04 and enable "OEM unlocking" on dev settings, but fastboot oem unlock returns "unknown cmd."
There's also fastboot flashing unlock_bootloader, but this one requires oem private key, which we don't have.

lucasolivamorim said:
Hello, have you done any additional steps in order to unlock the bootloader? I have version 04 and enable "OEM unlocking" on dev settings, but fastboot oem unlock returns "unknown cmd."
There's also fastboot flashing unlock_bootloader, but this one requires oem private key, which we don't have.
Click to expand...
Click to collapse
Hi, I haven't done any additional steps in order to unlock the bootloader. Just managed to uninstalled some apps via adb.

papavacuo said:
Comprei esse celular porque estava MUITO barato: https://pagseguro.uol.com.br/para-seu-negocio/maquininhas/pagphone
Ativei o modo de desenvolvedor, ativei a depuração USB, reiniciei no modo bootloader e obtive
[email protected]:~/Android/Sdk/platform-tools$ sudo $(what fastboot) piscando desbloqueio
FALHA (remoto: 'Não implementado.')
fastboot: erro: comando falhou
Acho que isso significa que o desbloqueio não está disponível para este telefone usando o fastboot.
Existe outra maneira de desbloqueá-lo?
A propósito, não havia opção de desbloqueio de OEM nas opções do desenvolvedor nas configurações.
O telefone é de https://www.paxtechnology.com/m30 mas customizado para este processador de pagamentos no Brasil.
Além disso:
sudo $(what fastboot) piscando get_unlock_ability
FAILED (remote: 'Not implement.')
fastboot: error: Command failed
Click to expand...
Click to collapse
No meu aparece a opção. Poderia me ajudar com os comandos

Question Bootloop fastboot pro 2021? Can't unlock bootloader ? Help me

My xiaoxin pad pro 2021 snap 870 8/256 in fastboot bootloop, i do follow unlock bootloader without proper but i can't unlock it. My seri number just have 7 number : HA1C00X and when i change value of fpinfo it is already 1, i don't must to change it. i do all step but when i flash sn.img HAHAHAHA not successfull . Can someone help me please.

Are you tried command
Code:
Fastboot flashing unlock
?

f1tm0t said:
Are you tried command
Code:
Fastboot flashing unlock
?
Click to expand...
Click to collapse
Fastboot flashing unlock sn.img ? I will try

kudo2702 said:
Fastboot flashing unlock sn.img ? I will try
Click to expand...
Click to collapse
Nope! Unblocking consist from two commands:
Fastboot flash unlock sn.img -- this getting permission from Lenovo for unblocking
Fastboot flashing unlock -- this is direct unlocking for tablet, you wil see some actions on tablet's screen