I'm looking for some help with relocking the bootloader on my one plus 5T I have tried everything I can think of. Once I lock the bootloader again it wont boot and a blueish white LED stays on I have also tried to sideload the firmware before and after locking the bootloader on different occasions and still no luck as soon as i unlock the bootloader it works completely fine
craigwilson9955 said:
I'm looking for some help with relocking the bootloader on my one plus 5T I have tried everything I can think of. Once I lock the bootloader again it wont boot and a blueish white LED stays on I have also tried to sideload the firmware before and after locking the bootloader on different occasions and still no luck as soon as i unlock the bootloader it works completely fine
Click to expand...
Click to collapse
hi, take a look on this thread, there you will get detailed infos!
https://forum.xda-developers.com/on...store-to-complete-stock-relock-t3712739/page5
happy flashing
EASIEST way to relock BL and full stock firmware is using 9008 qualcomm unbrick tool to reprogramme it.
or fastboot method flashing stock firmware and relock BL manually.
Related
I've tried several threads here and none is working.
I did all the downgrade, still not working.
Please help.
Try running the unofficial bootloader unlock tool... I used it on 174 update with no problems... Just remember to have developer settings active and USB debugging ticked...
Remember, unless you like the white ASUS start screen you'll need to flash the normal black bootscreen again using fastboot...
The official Asus bootloader unlock tool is also handy and I think works for newer versions, though if your phone is still under warranty, you can't hide that you've unlocked your bootloader using the official one because it contacts Asus's servers, unlike if you use the unoffical one, you may still be able to keep your warranty, but that's not guarantee. You can always flash the stock black splash screen to hide it in case you need to return your phone for repair.
You can download the official unlock tool here
http://dlcdnet.asus.com/pub/ASUS/Ze...50723.apk?_ga=1.60571305.563522865.1464012710
GroveStreetHomie said:
The official Asus bootloader unlock tool is also handy and I think works for newer versions, though if your phone is still under warranty, you can't hide that you've unlocked your bootloader using the official one because it contacts Asus's servers, unlike if you use the unoffical one, you may still be able to keep your warranty, but that's not guarantee. You can always flash the stock black splash screen to hide it in case you need to return your phone for repair.
You can download the official unlock tool here
http://dlcdnet.asus.com/pub/ASUS/Ze...50723.apk?_ga=1.60571305.563522865.1464012710
Click to expand...
Click to collapse
I just tried to unlock the bootloader and it said "unlock failed". I downloaded the tool from Asus website and made sure USB Debugging was on. I'm running 2.20. Is it possible to unlock the bootloader???
Thanks
Hey there, is there possible to remove that ugly black screen after unlocking bootloader that appears every boot and freezes 5 sec? Thanks in advance.
LaurynasVP said:
Hey there, is there possible to remove that ugly black screen after unlocking bootloader that appears every boot and freezes 5 sec? Thanks in advance.
Click to expand...
Click to collapse
Do you want to relock the bootloader or you want to let it unlocked?
I would keep it unlocked and skip the black screen if possible...
I'd like to keep it unlocked since I need root, is it possible to remove it somehow?
LaurynasVP said:
I'd like to keep it unlocked since I need root, is it possible to remove it somehow?
Click to expand...
Click to collapse
I don't think that this is possible to do, even changing the splash logo you can't do that. You could try to relock the bootloader but I never tried doing that on a custom ROM, only on the stock one. I don't remember if after relocking the bootloader with the bootloader status as relocked the initial boot menu is shown. Anyway you could try. I suggest the mauronofrio's tool if you're on Windows. If you are on Linux you have to use the adb and fastboot commands
re
DD3Boh said:
I don't think that this is possible to do, even changing the splash logo you can't do that. You could try to relock the bootloader but I never tried doing that on a custom ROM, only on the stock one. I don't remember if after relocking the bootloader with the bootloader status as relocked the initial boot menu is shown. Anyway you could try. I suggest the mauronofrio's tool if you're on Windows. If you are on Linux you have to use the adb and fastboot commands
Click to expand...
Click to collapse
I assume [re]locking your BL on custom ROM will cause hard-brick. I need root so can't lock BL
LaurynasVP said:
I assume [re]locking your BL on custom ROM will cause hard-brick. I need root so can't lock BL
Click to expand...
Click to collapse
I never tried it but at the end maybe yes. I don't think hard brick but it depends on what you exactly mean with hard brick (all the people think the hardbrick as something different lol)
DD3Boh said:
I never tried it but at the end maybe yes. I don't think hard brick but it depends on what you exactly mean with hard brick (all the people think the hardbrick as something different lol)
Click to expand...
Click to collapse
I tried this and yes it cause hard brick to my zuk z2 plus. But i somehow make my exit from hard brick.
I used to have a ZTE Axon 7 that used pretty-much the exact same warning screen as the ZUK Z2. For certain ROMs on the device you had to flash a different bootloader, as provided by developers on XDA. I remember in one of the flashable bootloaders, the developer was able to remove the warning screen somehow. So I think it is possible to do this on the ZUK as well. It just needs someone to look into it.
rajatsinghsp said:
I tried this and yes it cause hard brick to my zuk z2 plus. But i somehow make my exit from hard brick.
Click to expand...
Click to collapse
Yeah just a thing, you can now relock bootloader on z2, on specific Roms. I made a guide for it and it works 100%
DD3Boh said:
Yeah just a thing, you can now relock bootloader on z2, on specific Roms. I made a guide for it and it works 100%
Click to expand...
Click to collapse
That sounds great. Although I just went and read your guide and I noticed it says the 5-second bootloader warning will still be there. Is there no way of getting rid of the warning completely even with a locked bootloader?
Op3, stock recovery and official 9.0.2 rom.
Eveything elese is fine but bootloader is unlocked and when starting phone the dm-verity says that bootloader is unlocked.
I can go to fastboot and command fastboot oem lock and phone Will show that yes and no screen, but even If I select yes phone just boots and shows that bootloader is still unlocked.
I can not fine any info for this kind of problem or how to solve this. Anybody has any ideas how to get bootloader locked?
Have you tried selecting no, instead of yes?
When I tried the first CB, I had something similar where, with the new bootloader, the responses were inverse.
morphvale said:
Have you tried selecting no, instead of yes?
When I tried the first CB, I had something similar where, with the new bootloader, the responses were inverse.
Click to expand...
Click to collapse
Yes I did try that also but did not work.
But I know figured a way to do that. I used the MSM Download tool program. That flashed some very old software but did not lock the bootloader (like I think it should do?) But after that fastboot oem lock worked. Then I sideloaded newest 9.0.2 and now bootloader is locked and phone is completely stock and works fine. So no idea what was wrong, but luckily there is this MSM.
I also found out that newest windows10 has the qualcomm 9008 drivers so no need to install them separately like the instructions says.
You probably used MSM with 3.2.8 or similar. Newer ones also lock the bootloader.
Pie 9.0.2 cannot lock the bootloader. Potentially a bug.
Works fine on 5.0.8; simply downgrade, lock and install Pie again
Deear All,
I just bought my z2 force (t-mobile) from internet. It is an unlocked version and i can use it with my own sim card. However, i found that it cannot update via OTA as the bootloader is unlocked. I have heard that after i re-flash the firmware, the bootloader will be relocked. I am wondering, will the flashing re-activate the carrier lock?
Also, is it correct that after I flash via Lenovo Moto Smart Assistant. the bootloader will be locked again?
Is there other method to allow the phone to get OTA again?
Thanks a lot for your help.
hkguy80 said:
Deear All,
I just bought my z2 force (t-mobile) from internet. It is an unlocked version and i can use it with my own sim card. However, i found that it cannot update via OTA as the bootloader is unlocked. I have heard that after i re-flash the firmware, the bootloader will be relocked. I am wondering, will the flashing re-activate the carrier lock?
Also, is it correct that after I flash via Lenovo Moto Smart Assistant. the bootloader will be locked again?
Is there other method to allow the phone to get OTA again?
Thanks a lot for your help.
Click to expand...
Click to collapse
Unlocked bootloder won't stop an ota, but a custom logo.bin will. Chances are that the seller has also flashed a logo. When you boot you should see a warning about your bootloader being unlocked, if you don't and you just see a moto logo (or any stationary image really) then you have a custom logo which will fail otas. The easiest way to remedy this is to follow Uzephi's "How to Return to Stock' thread. Then you should get otas again. It is advised never to relock your bootloader. A good example of why would be that you have a custom logo, you relock, your phone fails to boot and you can't flash anything because you locked it. There is no real valid reason to relock your phone. As for losing carrier unlock, you shouldn't, those are usually permanent. Unless it was some hack which I doubt since I believe that is only for Spring variants. Just follow Uzephi's guide and you should be back to good.
41rw4lk said:
Unlocked bootloder won't stop an ota, but a custom logo.bin will. Chances are that the seller has also flashed a logo. When you boot you should see a warning about your bootloader being unlocked, if you don't and you just see a moto logo (or any stationary image really) then you have a custom logo which will fail otas. The easiest way to remedy this is to follow Uzephi's "How to Return to Stock' thread. Then you should get otas again. It is advised never to relock your bootloader. A good example of why would be that you have a custom logo, you relock, your phone fails to boot and you can't flash anything because you locked it. There is no real valid reason to relock your phone. As for losing carrier unlock, you shouldn't, those are usually permanent. Unless it was some hack which I doubt since I believe that is only for Spring variants. Just follow Uzephi's guide and you should be back to good.
Click to expand...
Click to collapse
Thanks a lot for your help. I will follow Uzephi's to reflash my phone. :good::good::good:
Am I just having a bunk phone or is anyone else having this issue?
Whenever I try to set up the lock screen code on the reconfirm the code screen it freezes after I put in the code and will not proceed.
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
JPower123 said:
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
Click to expand...
Click to collapse
Like no root or anything?
cabagekiller said:
Like no root or anything?
Click to expand...
Click to collapse
Yeah, it's super weird. Just unlocking the bootloader causes this. But yeah from what I understand you should be completely unrooted and with stock boot images and or init boot images when relocking.
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
mvincent2k said:
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
That is unlocked the unlock setting greys out on mine too. I got my lock screen to work as well. Super weird bug though.
mvincent2k said:
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
Only over fastootd or with msm tool (msm tool need authentication )
I just flashed the whole OS on Oneplus 11 using software called Fastboot enhance.
Actually, my op 11 was bootlooping but by using fastboot enhance software I flashed my original OS on the phone. Let everyone know, they don't need Odin or MSM for that. It's very easy and one-click process.
Same problem, was advised to lock and unlock the bootloader. I locked it and didn't realize that I had to go back to stock first and now I'm stuck in a boot loop. I can get into recovery with vol down and power, but cannot get into fastboot with vol up and power. Where do I go from here?
Sorry, I want to identify that this issue happen even I have not rooted?
PowerPC 604e said:
Sorry, I want to identify that this issue happen even I have not rooted?
Click to expand...
Click to collapse
Only when you have a convertet op11 (china ) and flash this to oos than after an oos Update you have flash back an image from coloros without this image the op 11 will bootloop
And when you have root and lock with root the bootloader than you have an bootloop