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.
Related
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app
ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.
:thumbup:
I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...
daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota
doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.
y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.
rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption
Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked
Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?
DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow
Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.
-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone
Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Why would you want to do this?
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes
Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.
jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry
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
Hey, is it possible to get rid of this message when booting?
Would be nice
Sure, just re-lock your bootloader. Presto. ?
thedrizzle said:
Sure, just re-lock your bootloader. Presto. ?
Click to expand...
Click to collapse
Probably a stupid question but im rooted, will it still boot up?
Macblack1991 said:
Probably a stupid question but im rooted, will it still boot up?
Click to expand...
Click to collapse
No, it's likely that your device will brick. Please don't do so
veatesia said:
No, it's likely that your device will brick. Please don't do so
Click to expand...
Click to collapse
Okay thanks for the reply
Dead end thread, there have been many many many many many posts about that since oneplus introduced that a couple of years ago
THERE IS NO WAY TO GET RID OF THAT WHILE UNLOCKED
period
and there's a thread about it here. been following this from the start and apparently it's next to impossible to achieve.
https://forum.xda-developers.com/oneplus-6t/development/wip-dissecting-bootloader-aka-rid-t3878470
veatesia said:
No, it's likely that your device will brick. Please don't do so
Click to expand...
Click to collapse
I have experience doing that. Yes your device will definitely get BRICKED!!! Just ignore that boot screen, do not attempt to do anything to get rid of it. It just takes time to accept it. I use to think about getting rid of it as well when i was using my Oneplus 3. I re-locked the bootloader and got bricked. I couldn't do anything and had to send it back to Oneplus to fix it.
There have been other devices where they are able to replace the image with another, such as a blank image to hide the warning. I've also seen people load custom ROMs signed with their own signature so they can relock their bootloader after loading a custom OS. So there are things that can be done, but it's not something to just play around with, as mentioned, mess it up, and you'll brick something.
Thanks for the replies. Well I guess its just how it is, nit a big issue, was just wondering because most videos of custom roms I saw this part was cut out lol.