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"
Related
I got S-off and unlocked bootloader. I have install Custom Recovery. I install a RUU without locking bootloader. After RUU complete, I go into bootloader again. Now the status of bootloader is unknown, meaning it doesn't say Lock or Unlock on the top of the screen but it does say S-OFF. I try to fastboot flash a custom recovery, it doesn't work. I try relock, it doesn't work either.
It give me this error, FAILED (remote: not allowed)
I try upgrade and downgrading, doesn't help.
How can I fix this problem?
seems like I can't use fastboot command anymore. I want to install custom recovery and I can't do fastboot flash recovery.
I am having this same exact issue with my Xperia Z Ultra. It is really hard to find any information on this. Anyone have some input on this?
I know this is the wrong forum for me, but the error is exactly the same. Thanks.
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.).
I tell them what happened to me, my U11 phone had it with the European version and I did s-off with sunshine without problems, I changed cid BS_US001 and mid 2PZC50000 without any problem, but try to load the ruu that you download from htc 1.28.617.3 and came out error 155 that the image was not correct, then what I did was to close the bootloader with the command fastboot oem lock, reset the phone and send me to the bootloader screen, when entering download it appeared and s-on and Bootloader Relocked , try to load the ruu again but it tells me that the image does not correspond, try to install recovery stock, TWRP, and firmware 1.28.617.3 but it does not let me do anything, when trying to enter recovery it sends me to bootloader and if I try to unblock bootloader I gives frp error, it is clear that despite being relocked the bootloader I keep appearing the screen that has been modified the phone, when entering download I appears in OS 1.28.401.7 and putting fastboot getvar all if I see the c id and mid of the American version, but I do not do anything.
Do you think it has a solution?
Waiting answer ...
Thank you ...
Hi.
There are no answers yet, because, honestly, it is difficult to understand what happened. You wrote one single phrase that is 10 lines long. Try to reformulate, using listed items, paragraphs and so on.
Just a friendly suggestion, no offense.
valvaher said:
I tell them what happened to me, my U11 phone had it with the European version and I did s-off with sunshine without problems, I changed cid BS_US001 and mid 2PZC50000 without any problem, but try to load the ruu that you download from htc 1.28.617.3 and came out error 155 that the image was not correct, then what I did was to close the bootloader with the command fastboot oem lock, reset the phone and send me to the bootloader screen, when entering download it appeared and s-on and Bootloader Relocked , try to load the ruu again but it tells me that the image does not correspond, try to install recovery stock, TWRP, and firmware 1.28.617.3 but it does not let me do anything, when trying to enter recovery it sends me to bootloader and if I try to unblock bootloader I gives frp error, it is clear that despite being relocked the bootloader I keep appearing the screen that has been modified the phone, when entering download I appears in OS 1.28.401.7 and putting fastboot getvar all if I see the c id and mid of the American version, but I do not do anything.
Do you think it has a solution?
Waiting answer ...
Thank you ...
Click to expand...
Click to collapse
Ok i may be way off base, but if the phone can boot into the OS go to developer enable usb debug and
Oem unlocking then follow the htc guide to unlock bootloader again ( not positive on that part never relocked a bootloader then unlocked) once that is done redownload the correct ruu per your cid and retry. Just my 2 cents. Hth.
you only flash full ruu 1.28.401.7
try to find in https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
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!
Hello all,
As the title suggests, I'm wondering if it is possible to root the Red Magic 7 Pro, and if there are any "consequences" of unlocking the bootloader like how Samsung shuts off Samsung Pay and OTA updates? I'm not too familiar with the Red Magic series.
Yes, it's pretty easy to unlock the bootloader and root.
AmmarHaseeb said:
Yes, it's pretty easy to unlock the bootloader and root.
Click to expand...
Click to collapse
I'm guessing for the rooting process I have to extract the boot.img from the official firmware, patch it in magisk and flash?
Yeah
AmmarHaseeb said:
Yeah
Click to expand...
Click to collapse
Baller thank you
Impossible to unlock the bootloader.
it always says "waiting for device"
{
"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"
}
Marcis-2k said:
Impossible to unlock the bootloader.
it always says "waiting for device"
View attachment 5611015
Click to expand...
Click to collapse
Did you try "fastboot oem unlock" or some other variant of the command?
Hi Soumy1234,
I've already try these commands :
fastboot flashing unlock
fastboot oem unlock
fastboot oem unlock NUBIA_NX709J
fastboot oem nubia_unlock NUBIA_NX709J
I think the EU version is lock or use a special fastboot command.
Marcis-2k said:
Hi Soumy1234,
I've already try these commands :
fastboot flashing unlock
fastboot oem unlock
fastboot oem unlock NUBIA_NX709J
fastboot oem nubia_unlock NUBIA_NX709J
I think the EU version is lock or use a special fastboot command.
Click to expand...
Click to collapse
It seems weird to have the EU version be locked, but I guess Samsung already does it with their NA versions. OEM unlocking is enabled tho right?
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Marcis-2k said:
Hi Soumy1234,
I've already try these commands :
fastboot flashing unlock
fastboot oem unlock
fastboot oem unlock NUBIA_NX709J
fastboot oem nubia_unlock NUBIA_NX709J
I think the EU version is lock or use a special fastboot command.
Click to expand...
Click to collapse
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Checking what you are doing i dont see if you went to the dev options and enabled "OEM unlocking".
After that, reboot on bootloader and you should be able to unlock it with the fastboot command.
You will need to recalibrate the fingerprint sensor (Recalibrate) and you will lose the ability to install OTAs.
I currently have the ROM version NX709J_EUCommon_v4.08 that has idle battery consumption issues and i can't install the OTA update NX709J_EUCommon_v4.12.
The stock recovery does not have the ability to use adb commands nor flash update.zip files, I'm checking how to make my own TWRP but its a first for me.
Lucas VT said:
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Checking what you are doing i dont see if you went to the dev options and enabled "OEM unlocking".
After that, reboot on bootloader and you should be able to unlock it with the fastboot command.
You will need to recalibrate the fingerprint sensor (Recalibrate) and you will lose the ability to install OTAs.
I currently have the ROM version NX709J_EUCommon_v4.08 that has idle battery consumption issues and i can't install the OTA update NX709J_EUCommon_v4.12.
The stock recovery does not have the ability to use adb commands nor flash update.zip files, I'm checking how to make my own TWRP but its a first for me.
Click to expand...
Click to collapse
By calibrate fingerprint sensor what do you mean exactly? Did you have to remove and redo the fingerprint or was there like an image file you had to flash again?
Soumy1234 said:
By calibrate fingerprint sensor what do you mean exactly? Did you have to remove and redo the fingerprint or was there like an image file you had to flash again?
Click to expand...
Click to collapse
You can check the link on my message to see the process, you will get a message when trying to use it saying that the calibration data was lost and that the sensor must be calibrated before using it.
The calibration process is a factory thing that can be accessed trough the dialer.
Lucas VT said:
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Click to expand...
Click to collapse
Is your device is 0123456789ABCDEF ?
Marcis-2k said:
Is your device is 0123456789ABCDEF ?
View attachment 5619121
Click to expand...
Click to collapse
Yep, exactly the same ID.
What is your hardware version?
Mine is NX709J_V1AMB
Lucas VT said:
Yep, exactly the same ID.
What is your hardware version?
Mine is NX709J_V1AMB
Click to expand...
Click to collapse
Hardware version : NX709J_V1AMB
Build : NX709J_EUCommun_V4.12
Explain me which command to root. I already have the patch boot_patched.img for the v4.12.
I have a NX709J_UNCommon_V3.14.
NX709J_V1AMB...
Phone says there is new version available, V3.17. but when I hit download and install it stops at 81% and says update package error..??
Any thoughts on it.??
When I go to the red magic page to try to download it manually the link takes me to..
Hi, do this method also work on Nubia Z40 PRO and Z40S PRO?