There is an annoying warning boot coming in my rooted nexus 5x which is at the start
Of the boot please help
I think there is no way of getting rid of the message, that warns you that the bootloader is unlocked, as far as I've heard.
Sidharth krishnan said:
There is an annoying warning boot coming in my rooted nexus 5x which is at the start
Of the boot please help
Click to expand...
Click to collapse
Flash this:
http://forum.xda-developers.com/showthread.php?t=3298420
Or find the thread in the apps and themes section and build your own.
Sent from my Nexus 5X using Tapatalk
granets said:
I think there is no way of getting rid of the message, that warns you that the bootloader is unlocked, as far as I've heard.
Click to expand...
Click to collapse
Correct. Just a warning.
Sidharth krishnan said:
There is an annoying warning boot coming in my rooted nexus 5x which is at the start
Of the boot please help
Click to expand...
Click to collapse
Flash this:
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
I use this, and warning is gone
Related
on my verizon galaxy nexus, i received the OTA update. afterward i unlocked the bootloader and went to root. now it is stuck in boot loop at the google screen with the unlock at the bottom.
I can boot into the bootloader and I have tried going back to stock with the google image but i get the following error:
Device version-cdma is 'I515.EK05'.
Update requires 'I515.EK01'.
any suggestions?
Just as a suggestion I wouldn't root before validating a rollback plan. I apologize that this seems assholish since I have no further help.
Sent from my Galaxy Nexus using Tapatalk
it looks like i was just attempting to flash it improperly. Found the answer in another post
http://forum.xda-developers.com/showthread.php?t=1394448
sorry for the double post
spooniemcfly said:
it looks like i was just attempting to flash it improperly. Found the answer in another post
http://forum.xda-developers.com/showthread.php?t=1394448
sorry for the double post
Click to expand...
Click to collapse
Glad disaster was averted. Thinking you bricked always sucks.
Sent from my Galaxy Nexus using Tapatalk
spooniemcfly said:
it looks like i was just attempting to flash it improperly. Found the answer in another post
http://forum.xda-developers.com/showthread.php?t=1394448
sorry for the double post
Click to expand...
Click to collapse
Sorry I have the same problem. Would you please tell me where is the solution. Thanks.
I have a L700 and it's refusing to let me re-lock the bootloader. It shows that it locks, but if I restart fastboot it shows unlocked again. if I restart the phone, it shows that it's unlocked. i've tried to flash a new build using ODIN and Fastboot but it still is acting up. Also, if i flash CWM and restart the phone, TWPR shows up which is currently on the phone. It's like updates aren't actually working!!!
Any ideas?
(It won't let me update my bootloader/radio's or recovery which is why I want to relock it, I think that might solve something)
Thanks,
Why do you need to relock your bootloader?
It's pretty much pointless.
electro` said:
Why do you need to relock your bootloader?
It's pretty much pointless.
Click to expand...
Click to collapse
I believe it will fix my issue. I feel as if I can lock it then unlock it, i'll be able to flash what I need. Since it's pointless, can you explain why my bootloader and radio's won't update?
This is going to be really stupid but did you do the command prompt relock bootloader in fastboot?
This seems kind of unusual.
Did you reflash the bootloader or anything else?
If not, try that.
electro` said:
This is going to be really stupid but did you do the command prompt relock bootloader in fastboot?
This seems kind of unusual.
Did you reflash the bootloader or anything else?
If not, try that.
Click to expand...
Click to collapse
I did relock the bootloader as stated in the OP. It goes back to unlocked with a restart or bootloader restart which shouldn't happen. I know it seems unusual. I've flashed everything (system, recovery, radio, bootloader) to no avail.
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
bk201doesntexist said:
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
Click to expand...
Click to collapse
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
Sprint GNex
bk201doesntexist said:
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
Click to expand...
Click to collapse
Way to be an anus and look like an idiot doing it. I've read other threads with the same issue, I think it's a hardware issue and I'm just out a phone.
Thanks anyway.
Sooppex said:
Way to be an anus and look like an idiot doing it. I've read other threads with the same issue, I think it's a hardware issue and I'm just out a phone.
Thanks anyway.
Click to expand...
Click to collapse
He was trying to help you.
No need to be a **** about it.
You could try the Nexus Root Toolkit by WugFresh. I think that has a bootloader relocking facility in it.
http://goo.im/devs/WugFresh/NexusRootToolkit
Edit: Whoops, sorry, didn't fully read the thread, my bad
i mean its been 10 minutes, but still stuck on bootloop any ideas?
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
Out of date ADB can cause this. I have seen it a few times reported by other people.
Try rebooting PC then reboot phone back to boot loader and use THESE adb and fastboot apps. I copied the from the latest SDK Manager
If that does not resolve then post back
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
You should probably include a screenshot of everything you did in the command prompt... boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Good point!
Scott said:
Good point!
Click to expand...
Click to collapse
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Scott said:
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Click to expand...
Click to collapse
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Agreed! But on the same note, in the OP's defense there is not a very clear Q/A thread that tells you what you need to do. Everything is scattered. However, that is not anyones fault. This device is new to "ALL" of us. The whole SLOT thing, etc. Its all new unless you had a Google Chromebook. So I cant much blame people with issues. The good thing... 99.99% of the issues posted can be fixed with some patients. :good:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Just ignore it, it's due to the unlocked bootloader
Sent from my Pixel XL using Tapatalk
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Nothing you can do about that at this time. I am sure someone will hack the aboot or hboot, which ever on an HTC device to remove it. For now wear it as a badge of pride :highfive:
iKenta said:
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
Click to expand...
Click to collapse
Could have been. I would recommend you not install TWRP at this time. Its finicky but being worked on. I know for fact it will be great soon.
I hope @Chainfire updates his Flash Fire. Easier to use than TWRP!
Hello, I have a friend who has a Pixel 2 XL. He had rooted it and was trying to unroot so he could download Android Pie OTA and somehow accidentally locked the bootloader. He isn't able to go into recovery mode at all, and when he tried it gives him an error code "No OS found". He thinks this has hardbricked his phone but he is able to turn the phone on. It just won't let him flash a factory image. [I am going entirely by what he's told me. I've never rooted or unrooted a device so apologies if I messed up any of the terminology]. Is there anything he can do to fix his phone at this point?
P.S. I tried to contact Google to see if the device could be RMA'd. However, they said they cannot because it has been rooted.
Din1905 said:
Hello, I have a friend who has a Pixel 2 XL. He had rooted it and was trying to unroot so he could download Android Pie OTA and somehow accidentally locked the bootloader. He isn't able to go into recovery mode at all, and when he tried it gives him an error code "No OS found". He thinks this has hardbricked his phone but he is able to turn the phone on. It just won't let him flash a factory image. [I am going entirely by what he's told me. I've never rooted or unrooted a device so apologies if I messed up any of the terminology]. Is there anything he can do to fix his phone at this point?
P.S. I tried to contact Google to see if the device could be RMA'd. However, they said they cannot because it has been rooted.
Click to expand...
Click to collapse
Will it boot into fastboot?
Sent from my Pixel 2 XL using XDA Labs
Triscuit said:
Will it boot into fastboot?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I just checked with him and he says yes. But he says he can't root because he can't unlock the bootloader.
He also says it's not TWRP ready and the "enable OEM unlocking" option was unavailable prior to the phone bricking.
Fatal error was relocking the phone when not bone stock.
michaelbsheldon said:
Fatal error was relocking the phone when not bone stock.
Click to expand...
Click to collapse
Yes, I believe he did it by accident. Is there anything that can be done to reverse it?
Din1905 said:
Yes, I believe he did it by accident. Is there anything that can be done to reverse it?
Click to expand...
Click to collapse
Short of returning it for an RMA, most likely not.
Alright might just have to end up trying that. Thanks everyone for responding. Although if anyone can think of any solutions please feel free to still respond!
Every time i have posted an op a moderator closed the thread.
So if you want to unlock your verizon bootloader figure it out
Why do you think your phone "bricked" after installing Magisk?
brand0nYates said:
Why do you think your phone "bricked" after installing Magisk?
Click to expand...
Click to collapse
Boot looped. Wouldn't boot system at all. Somehow whole boot looping I lost recovery. Computer wouldn't recognize fast boot
Didn't work for me, which is dissapointing considering I had to update to the August patch that I was holding out on for an exploit...
zmedhaug said:
Every time i have posted an op a moderator closed the thread.
So if you want to unlock your verizon bootloader figure it out
Click to expand...
Click to collapse
How was this done. Would you mind informing me ?
What's the loophole? I find it extremely unlikely all of a sudden something has been discovered but I was just thinking about how I miss playing with unlocked android devices and came here to look, and of course there's a post from today..
Does anyone know what is the solution? How to unlock it?