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?
Related
Hi guys. I want to remove this warning message when i boot up my phone. Can anyone help me? Thanks!
being able to do this would be great! I tried all the fastboot commands that work on different devices to re-lock the bootloader, flashed the bootloaders again...downgrade to Android 5, uncheck enable EOM unlock in the developer options..tried fastboot commands.. all was in vain...
Any other ideas?
rigocalin said:
being able to do this would be great! I tried all the fastboot commands that work on different devices to re-lock the bootloader, flashed the bootloaders again...downgrade to Android 5, uncheck enable EOM unlock in the developer options..tried fastboot commands.. all was in vain...
Any other ideas?
Click to expand...
Click to collapse
I don't want to relock my bootloader. My goal is just removing this message. Because if the bootloop issue happen to me, sellers will not know that i've unlocked my bootloader. So they will repair my phone for free.
please can any mod close this? Has already been asked and answered. it's not possible! Do a damn search before!
there is not mention of this as far as I sow it anyways...
If you have it then post the link here so we can see it also .
PS: under the same logic we would not try to find a root or bootloader unlock and talk about it because its not currently possible.
5nickers said:
please can any mod close this? Has already been asked and answered. it's not possible! Do a damn search before!
Click to expand...
Click to collapse
If your in the EU and phone is still under warranty, LG will repair defected devices regardless if BL is unlocked as its a known defect. Read this thread.
http://forum.xda-developers.com/g4/help/g4-bootloop-lg-officially-admits-t3301629
awes0me1 said:
If your in the EU and phone is still under warranty, LG will repair defected devices regardless if BL is unlocked as its a known defect. Read this thread.
http://forum.xda-developers.com/g4/help/g4-bootloop-lg-officially-admits-t3301629
Click to expand...
Click to collapse
I live in asia region. I talked with the seller where that i bought (third party shop) and they said that unlocking BL void warranty. That is why i want to hide this message
Then it's a no...you cannot remove message when booting.
awes0me1 said:
Then it's a no...you cannot remove message when booting.
Click to expand...
Click to collapse
There are marshmallow boot animation in forums for g4. But i am not sure if it can hide this message or not.
xdaorxan said:
There are marshmallow boot animation in forums for g4. But i am not sure if it can hide this message or not.
Click to expand...
Click to collapse
No, as the message appears before the bootanimation.
davebugyi said:
No, as the message appears before the bootanimation.
Click to expand...
Click to collapse
That's awful
I read about a guy saying something like changing the I-M-E-I (dont want to get banned or something) to something else, reboot and then restore it, you should have a relocked bootloader..
it sounds a bit shady but maybe this can actually work...depending on how this unlock is done.
https://www.youtube.com/watch?v=DZBFc2Da83E
This guy actually relocked the bootloader nice
I want custom rom, root and exposed,
But there is the warning of the unlocked bootloader on every boot.
What is the most I can get without this warning?
Thanks a lot.
Nothing wrong.. Tbh I really like that warning since you can easily navigate to recovery, Fastboot etc. Just ignore that warning.
yossi787 said:
I want custom rom, root and exposed,
But there is the warning of the unlocked bootloader on every boot.
What is the most I can get without this warning?
Thanks a lot.
Click to expand...
Click to collapse
DON'T relock the bootloader as long as your system is modified in any way (custom rom, root ...).
Don't care about the warning, without it you can get absolutely nothing, but using the unrooted stock firmware.
This warning is shown on every thread describing how to unlock the bootloader - if you lock the bootloader with anything that isn't the stock ROM/recovery, then you will brick your device
I personally, have never had any problems with the adb command to lock and unlock the bootloader. The bootloader actually operates independently of the software running. However, why would you want to relock the bootloader, particularly if you intend to flash other ROMs.
jim262 said:
I personally, have never had any problems with the adb command to lock and unlock the bootloader. The bootloader actually operates independently of the software running. However, why would you want to relock the bootloader, particularly if you intend to flash other ROMs.
Click to expand...
Click to collapse
I don't like the idea that everyone can wipe my device. I have little brothers and they can do that by accident...
yossi787 said:
I don't like the idea that everyone can wipe my device. I have little brothers and they can do that by accident...
Click to expand...
Click to collapse
That doesn't depend on a locked bootloader. You CAN'T protect android phones from beeing wiped.
LS.xD said:
That doesn't depend on a locked bootloader. You CAN'T protect android phones from beeing wiped.
Click to expand...
Click to collapse
Of course, but from this warning that can happen by accident...
Hi everyone,
Well my doubt it's really simple as you can see.
I tried to search on forum and internet, but I didn't found nothing solid.
Only achism (Incluing Mi official Forum)
It's really simple to Lock/Unlock the bootloader on Mi 5s, a simple command on promt and it's DONE. You lose nothing, no need to flash NOTHING.
I heard about bootloop, but does it real? Anyone here already tried it?
Why Am I asking it?
Well, if my bootloader is unlocked, I dunno why, but even with magisk Applications can detect some incoherence in my smartphone.
Even passing all steps of SafetyNet, the apps detect.
I think it's some flag on build.prop or another option available on MIUI Rom (and ofc they will read it to check everything).
My GF has magisk and custom recovery (Unlock Boot) and the same apps don't detect on her phone and works normally. (I configured both)
So I would like to know if it's really possible use a Custom Recovery and Magisk and just block the Bootloader again...
If you have the original bootloader from the original rom you can lock it. If you don't, the phone will stop booting with lock and custom bootloader.
patoberli said:
If you have the original bootloader from the original rom you can lock it. If you don't, the phone will stop booting with lock and custom bootloader.
Click to expand...
Click to collapse
No. Even using stock ROM after unlock bootloader and Install TWRP and lock again we got a message "the system has been destroyed" on Mi 5/5s/5x.
It's a Soft Brick, but if anyone on future want to try it and before do it, found this post so, stay away.
TWRP = different bootloader.
patoberli said:
TWRP = different bootloader.
Click to expand...
Click to collapse
Read the post again and if you don't understand, read again.
Thank you.
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.
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