Hi,
When i received my Zuk Edge few months ago I unlocked the bootloader and flash a custom ROM. But it was buggy and i prefered to returned to the stock ROM.
So im now back in Stock ZUI Rom, no root, no custom recovery, no custom rom/firmware... The only thing remaining "unofficial" is the bootloader, which i "unlocked".
How can I lock the bootloader of the Zuk Edge ? (i mean relock it)
Cause i didn't find any post on that subject
Thank you all
I found the answer actually on ZUK Fans Forum.
You have just to :
/!\ Be on Stock ROM (ZUI Official) /!\ (otherwise, you'll brick the phone)
- Go to fastboot mode (adb reboot bootloader)
- Type this : fastboot -i 0x2b4c oem lock
Then the device will restart (it will be a bit long, no worries)
The bootloader status won't be unlocked unfortunately, but "relocked".
Hi,
but with "relocked" bootloader, OTA Updates are not able. I made same step/mistake and unlocked the bootloader with the aim to get OTA Updates, but now there is no way cause of the really bad description I followed... (
Is there any solution to lock the bootloader again? Maybe editing the 'unlock_bootloader.img'?
Sincerely yours
LacyOne
Related
Hello,
I want to relock the bootloader and go back to stock.
I tried flashing stock firmware using fastboot.
fastboot oem lock begin
flashed stock firmware
fastboot oem lock
But Bootloader is still unlocked.
I got message as first flash full stock system. Something like that. Don't remember as I tried this a week ago.
Any help will be highly appreciated.
Thank you in advance.
Edit : I also tried the Windows tool provided by one of the members but it failed too.
I used the same to unlock in the first place.
I think it depends on what you want to achive. While you might be able to re-lock the bootloader (which means it can't be flashed without being unlocked again), you will never ever get rid of the unlock message again. This - to my understanding - is an efuse which is permanently set. If you want to remove the unlocked bootloader boot message, I'd stay unlocked and would just flash a different boot logo (logo.bin) where the unlocked gfx are replaced with the standard gfx thus showing the standard boot logo.
I would like to relock the bootloader altogether.
I don't think you can. You can lock it but you can't remove the warning that it has been tampered with.
I don't care about the warning.
I just want to re-lock it.
Flashing the Official firmware for my Country - India did the job.
Last time I tried with firmware for ASIA.
I don't see any reason for that to fail but you never know.
Thanks for replying.
hey can you give me the link for that rom im also using the indian version but unable to lock the bootloader
several questions in no particular order:
Does the "OEM Unlocking" toggle do anything on the XT1572?
If I issue the fastboot OEM LOCK command after having sucessfully unlocked the device before, do I need to go through the full data wipe+send oem data+flash unlock code process again?
Lastly, I was able to flash the MM firmware for my Single SIM AISA model XT1572 despite having the bootloader locked (I think).
Is that normal that I can flash the official moto firmware using just fastboot without having to tweak with anything else?
I presume that since the digital signatures are correct the bootloader has no issue accepting the MM files.
Not quite the end of the world if I have to wipe everything and start over (it's only been a day) but I regret not knowing earlier. Nor did I expect to get this far with a relocked boot loader. Was trying to add SuperSU and found that while I can overwrite flash the stock recovery I cannot flash TWRP.
psyvenrix said:
several questions in no particular order:
Does the "OEM Unlocking" toggle do anything on the XT1572?
If I issue the fastboot OEM LOCK command after having sucessfully unlocked the device before, do I need to go through the full data wipe+send oem data+flash unlock code process again?
Lastly, I was able to flash the MM firmware for my Single SIM AISA model XT1572 despite having the bootloader locked (I think).
Is that normal that I can flash the official moto firmware using just fastboot without having to tweak with anything else?
I presume that since the digital signatures are correct the bootloader has no issue accepting the MM files.
Not quite the end of the world if I have to wipe everything and start over (it's only been a day) but I regret not knowing earlier. Nor did I expect to get this far with a relocked boot loader. Was trying to add SuperSU and found that while I can overwrite flash the stock recovery I cannot flash TWRP.
Click to expand...
Click to collapse
As far as I am concerned relocking the bootloader wont wipe your data and yes about the question regarding the stock firmware
PS: Dont relock your bootloader once you unlock it the warranty doesnt come back even if you lock it again
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
dhenewar said:
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
Click to expand...
Click to collapse
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
echo92 said:
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
Click to expand...
Click to collapse
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
dhenewar said:
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
Click to expand...
Click to collapse
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
echo92 said:
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
Click to expand...
Click to collapse
Thanx bro I will try it out .. yep bro I got it in service center n they told me .. No way of fixing it .. Aahh n that's it ? .well there was option change of hardware price was half of the phone cost ..better to buy new one ?
Hi, i have some questions about LeEco x651.
I've got the device with EUI 5.9.028S (build KGXCNFN5902710271S).
I want achieve two things:
1) install the latest official multilanguage build for the device
2) ROOT the device
I initially wanted to ROOT this build flashing magisk from a temp TWRP (using "fastboot boot twrp.img"), but this wasn't a good idea. After I unlocked the bootloader using the "fastboot oem unlock" command (debug usb enabled, oem unlock enabled) i lost the baseband (and the IMEIs). I panicked a little, but fortunatly everything fixed itself after I re-locked the bootloader ("fastboot oem lock") without doing anything else, so I never booted in TWRP or flashed Magisk.
Can someone explain me why unlocking the bootloader made me lose the baseband? I never had a really "chinese" android phone (the most "chinese" phone I ever had was a Xiaomi Mi A1) but I have unlocked many bootloader and never had this problem. And can someone help me to update the phone to the latest build and ROOT it? I'm downloading this ROM (http://bug.letv.com/cn/download/phone/78) right now, but the download is very slow and I don't know if the ROM is multilanguage (I need italian language because the phone is a gift to my little sister).
Thanks.
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
tin2001 said:
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
Click to expand...
Click to collapse
Seriously? No one reads thread online?! I quote to NEVER, EVER, FLASH OREO/NOUGAT ROMS AFTER UPDATING TO PIE!!!
I downloaded the latest OFFICIAL ROM when it was already bootlooping.... Seriously? I'm supposed to go searching online for 3rd party information rather than the official?
Now how about people with useful information instead of arrogance?
If I'm not wrong you just need to boot into bootloader and fastboot oem unlock. With unlocked bootloader, go fastboot mode and flash official stock pie fastboot rom