Database Users

how to remove bootloader unlocked warning

Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds ?

romeoh said:
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds
Click to expand...
Click to collapse
You can't, you would have to modify the bootloader to get rid of it, which is pretty dangerous and could hard brick your phone.

awsomjgp said:
You can't, you would have to modify the bootloader to get rid of it, which is pretty dangerous and could hard brick your phone.
Click to expand...
Click to collapse
Ok, but as I know the only version that doesn't contain this warning screen is B20, so If I started from the very beginning by flashing back the B20 then removing the bootloader from the next versions (B27,B29,B15,B19) and flashing them from twrp would that work? ?

romeoh said:
Ok, but as I know the only version that doesn't contain this warning screen is B20, so If I started from the very beginning by flashing back the B20 then removing the bootloader from the next versions (B27,B29,B15,B19) and flashing them from twrp would that work? ?
Click to expand...
Click to collapse
If you are going to try that then just flash the b20 stack first and see if it boots.
Not completely sure whats in the bootstack zips but I've always assumed it is bootloader and modem.
Pretty sure 6.x bootloader will not work on 7.x but you can always try it out.

lafester said:
If you are going to try that then just flash the b20 stack first and see if it boots.
Not completely sure whats in the bootstack zips but I've always assumed it is bootloader and modem.
Pretty sure 6.x bootloader will not work on 7.x but you can always try it out.
Click to expand...
Click to collapse
Tbh I don't have the courage to try it that's why I'm asking may be one of our good developers knows the right way to do it ?

Saw this in post #496 of Full Updates / Back to Stock Files via TWRP
.......[snip] ......
"EDIT : managed to work fastboot and get rid of the bootscreen as in attachment :
Just refollow the steps in this guide to unlock bootloader (even if you think/thought you were unlocked (you are but has to be 'rewritten"), just do it again to flash the proper aboot...)
https://forum.xda-developers.com/axo...flash-t3517379
I had permission denied in 8) so i retried in twrp recovery.
All went fine.
And also the annoying boot screen ("that your device is corrupted due to unlock state...") is GONE too...."

I actually find the unlocked bootloader convenient. Rather than try to remember which buttons to press to get into recovery/fastboot, I can just do it from that screen so long as one of the volume buttons is depressed during the first 5 seconds of booting. I don't find it intrusive or bothersome at all.
If yours is taking 20 seconds to start booting then there is some other problem. It should start within ~5 seconds.

romeoh said:
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds
Click to expand...
Click to collapse
u can give me the method for unlock bootloader for 7.1.1

mr.mgmg said:
u can give me the method for unlock bootloader for 7.1.1
Click to expand...
Click to collapse
I was already unlocked when I updated to 7.1.1. You can try this method it's so simple and easy. Tbh I'm not sure if it will work on 7.1.1, but I think all what you need to do is to revert back to 7.0 then unlock bootloader, take the ota update and flash twrp from fasboot and from twrp flash SuperSu 2.79 for root. http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page25

romeoh said:
I was already unlocked when I updated to 7.1.1. You can try this method it's so simple and easy. Tbh I'm not sure if it will work on 7.1.1, but I think all what you need to do is to revert back to 7.0 then unlock bootloader, take the ota update and flash twrp from fasboot and from twrp flash SuperSu 2.79 for root. http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page25
Click to expand...
Click to collapse
thanks for help
but im a fried if this method brick my phone

A few questions for rooted Sprint users

I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!

williamvito said:
I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
Click to expand...
Click to collapse
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method

me2151 said:
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
Click to expand...
Click to collapse
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
Click to expand...
Click to collapse
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?

williamvito said:
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
Click to expand...
Click to collapse
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.

me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
You're the man, thanks for the quick reply! I will give this another go tomorrow.

me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?

williamvito said:
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
Click to expand...
Click to collapse
Once youve started the dirtysanta method it installs a new bootloader. you can access bootloader(fastboot) by holding VOL- and plugging iin the phone when powered off

Little help need for H910 (AT&T Update)

Hi guys,
I just recently bought LG V20 H910 and its stucked on December 1, 2016 update Now the simple thing i want is to remain on stock and update the software.
The thing that i learned is we need AT&T sim which is not possible for me and the second thing is Bootloader unlock.
Now guide that what should is do, i know dirty santa's FM problem i dont want that also the boot time is longer .
It would be helpful if anyone guide to simple update without further modifications or root.

If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian

runningnak3d said:
If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian
Click to expand...
Click to collapse
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?

runningnak3d said:
If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian
Click to expand...
Click to collapse
If I have AT&T SIM but I am not in the US. Will I get the update?

Mastermind_hassan said:
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?
Click to expand...
Click to collapse
If you use the dirty santa root you'll still have the corrupt warning screen and slightly longer boot time, static on display can be eliminated by flashing a custom kernel

cnjax said:
If you use the dirty santa root you'll still have the corrupt warning screen and slightly longer boot time, static on display can be eliminated by flashing a custom kernel
Click to expand...
Click to collapse
What are other methods for H910 bootloader unlocking that dont have that corrupt warning screen and longer boot time

Mastermind_hassan said:
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?
Click to expand...
Click to collapse
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
nirvikkhanal said:
If I have AT&T SIM but I am not in the US. Will I get the update?
Click to expand...
Click to collapse
I have no idea.
-- Brian

runningnak3d said:
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
I have no idea.
-- Brian
Click to expand...
Click to collapse
okay thank you please give me the link to get started

runningnak3d said:
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
I have no idea.
-- Brian
Click to expand...
Click to collapse
Just one last question, i have completed everything now i just wanted ask like for example if i wanted to sale my phone what things should i do to make that fizzy bootloader screen gone? because when i sell it to seller he will think there is some kind of fault in the screen

Mastermind_hassan said:
Just one last question, i have completed everything now i just wanted ask like for example if i wanted to sale my phone what things should i do to make that fizzy bootloader screen gone? because when i sell it to seller he will think there is some kind of fault in the screen
Click to expand...
Click to collapse
The only way to get rid of the boot screen is to go back to completely stock and locked boot loader, search the v20 forums there are threads around on how to do it.

Back to Stock with Oreo possible?

Hello my friends.
I bought my U Ultra in December 2017.
Now I decided to flash LeeDroid Oreo on my phone.
It works great.
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Now my question.
Is it possible to go for going to stock when I recover it all?
Can I lock the bootloader after that?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
My System Version was 2.21.401.1 and my region is Europe/Germany.
Regards

inFiniTyz_Z said:
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Is it possible to go for going to stock when I recover it all?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
Click to expand...
Click to collapse
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
inFiniTyz_Z said:
Can I lock the bootloader after that?
Click to expand...
Click to collapse
Kind of. You can make OEM lock but it won't be the factory lock. It will be relock. And if you have a custom ROM at that point the phone may not let you boot up.

QDT said:
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
Click to expand...
Click to collapse
In case when I flash the stock recovery too?

inFiniTyz_Z said:
In case when I flash the stock recovery too?
Click to expand...
Click to collapse
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).

QDT said:
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
Click to expand...
Click to collapse
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?

inFiniTyz_Z said:
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
Click to expand...
Click to collapse
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.

QDT said:
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
Click to expand...
Click to collapse
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.

inFiniTyz_Z said:
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
Click to expand...
Click to collapse
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.

QDT said:
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
Click to expand...
Click to collapse
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?

inFiniTyz_Z said:
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
Click to expand...
Click to collapse
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.

QDT said:
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
Click to expand...
Click to collapse
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!

inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.

QDT said:
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
Click to expand...
Click to collapse
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?

inFiniTyz_Z said:
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
Click to expand...
Click to collapse
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".

QDT said:
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
Click to expand...
Click to collapse
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"

inFiniTyz_Z said:
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
Click to expand...
Click to collapse
And to my knowledge it will be like that. You have flashed unlocked (from HTC but always) bootloader and this has to be noted. It is not that drastical as KNOX for Samsung, doesn't influence the phone functioning.

inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
When you say you followed the procedure, which exactly do you mean? Can you please help me by giving me a quick summary of the steps?

I would like to know the procedure as well.

Hi! I've installed a custom ROM, now I would like to go back to the stock ROM, I don't have a nandroid backup, what can I do?

Not receiving software updates

I purchased a pre-owned Galaxy S10+ from Best Buy. It has One UI 3.1 with the September 1st, 2021 security patch on it. I can't get it to update to One UI 4. Every time I check for updates on the phone it says the software is up to date when it isn't. Is this normal? Will I get the One UI 4.0 update eventually? I am on Google Fi if it matters. The phone appears to have previously been on Sprint.

Is it rooted or modified Ina my other way? Is the phoen supposed to get oneui 4?

Arealhooman said:
Is it rooted or modified Ina my other way? Is the phoen supposed to get oneui 4?
Click to expand...
Click to collapse
Not that I know of. It does not appear to be rooted. I have not modified it in any way myself. Since it is a pre-owned device I don't know the history of it. I have read in numerous places that the S10 series is supposed to get One UI 4 and it started rolling out around the end of 2021.

Do you get a unlocked bootloader warning when unlocking device?

Arealhooman said:
Do you get a unlocked bootloader warning when unlocking device?
Click to expand...
Click to collapse
No, I don't.

sega dude said:
No, I don't.
Click to expand...
Click to collapse
reboot into the download mode by turning off the phone, waiting 5 secs, then pressing bixby + volume down button for 6 secs and then connecting the usb cable phone x pc.
after that, check for Know warranty or Warranty Bit or Knox Bit or Knox Trip or anything related. If it says 0, your device has never been rooted and knox isn't tripped. but if it says 1 or 0x003 it is tripped

I es gonna say that, but it’s to complicated for most people, and if BL locked that means they are stock, so ota shoudl work. @sega dude if ur tech savvy, unlock BL, flash latest firmware thru Odin then relock BL (or keep unlocked).