I'm not sure what is up, this isn't a new thing, but people keep coming to me (1-2 a day) with this issue.
If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it.
If you are on EE UK, Verizon or another carrier blocking bootloader unlocks, and you used dePixel8 to unlock it, DO NOT relock your bootloader unless you are sure you don't want it unlocked again.
Finally, dePixel8 is UNSUPPORTED. Don't come to me if you can't get it to work, don't come to me if you used it them messed up your phone by flashing something bad or whatever. Its on you.
Great announcement. With the monthly security update out today, it is recommended that you don't install the update or have automatic updates enabled.
Related
I get this at each power off/on boot
"Your device software can't be checked for corruption. Please lock the bootloader." (Orange)
Already read https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
Not sure if this impacts the phone receiving beta updates, I did not install Android N, it was shipped to me in that mode and I simply used a gmail account to logon to accept beta thinking that is all I need to receive updates.
The message itself does not bother me, phone boots up and runs fine.
It shipped with the bootloader unlocked?. Have you tried downloading and flashing the beta with the bootloader unlocked? In my experience, the only time an unlocked bootloader stopped me from getting anything was when I had to update the HTC Thunderbolt back in the day. You should be totally fine with an unlocked bootloader when getting the beta upgrade.
xdafly said:
I get this at each power off/on boot
"Your device software can't be checked for corruption. Please lock the bootloader." (Orange)
Already read https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
Not sure if this impacts the phone receiving beta updates, I did not install Android N, it was shipped to me in that mode and I simply used a gmail account to logon to accept beta thinking that is all I need to receive updates.
The message itself does not bother me, phone boots up and runs fine.
Click to expand...
Click to collapse
You will continue to receive any and all updates. The unlocked bootloader is nothing to worry about. The OTA updates will be officially useless, only if you have made changes to the /system parition, like rooting or tweaks, etc.
Although, I am also curious. Where did you buy your 6P? And, did it come unlocked?
Did not buy the phone, it was sent to me by Google, unlocked.
xdafly said:
Did not buy the phone, it was sent to me by Google, unlocked.
Click to expand...
Click to collapse
Giveaway or something? Sorry, I still not get it.
So my safetynet checker says I failed even though I completely wiped all data! Even the sdcard data! I did a complete fastboot flash of all the system image files including the userdata file. I did not root the phone yet and I don't plan to either, I just want Android Pay.
CTS Profile Match = fail
That's what I get from the safetnet checker...My only other idea is to relock and unlock the bootloader again.
It seems you're not alone. I saw a few posts on reddit describing the same thing. The consensus is that Google may possibly be requiring locked bootloaders as well now for Safetynet.
Granted, I live in Canada and we don't have Android Pay yet. But I just won't even bother if this is the case.
It appears you are right mattkroeder...I relocked my bootloader and it passed, I unlocked it again and it failed....
Damn! I could not figure out why my Pay didn't work today. I'm stock, unlocked, custom ROM, no root. I just tried safetynet and its red. That seems like a bigger hurdle then not allowing rooted phones no pay.
It has been said all along that it was a losing battle....I just hoped that they would eventually block any and all root access at worst. Blocking the bootloader unlock I think puts a nail in the coffin of that little game. You will only be able to have Android Pay with a completely stock phone....
Looks like it is the case now. Now I'm gonna waste 2-3 hours of my precious life, reverting everything back to stock and locked.
GatorsUF said:
It has been said all along that it was a losing battle....I just hoped that they would eventually block any and all root access at worst. Blocking the bootloader unlock I think puts a nail in the coffin of that little game. You will only be able to have Android Pay with a completely stock phone....
Click to expand...
Click to collapse
I have been thinking about rooting my v20(H990DS) and I was wondering if there is way to relock the bootloader afterwards in order to receive the oreo update (if ever released). Also after relocking will I still have warranty or not? I will probably use Dirty Santas guide for rooting.
Any help?
Yes you can relock your bootloader, however, unless you want to lose root, that isn't how you would want to upgrade to Oreo if you want to keep root.
LG phones don't have a knox style indicator to show if (or how many times) the bootloader has been unlocked. I have sent various V20 phones to LG for warranty repair after I bricked them trying to root them -- take that however you like.
-- Brian
I went to switch to a different carrier, and was on cricket, and also tried tmobile both wich worked fine unlocked bootloader and rooted.
I then switched to sprint, and verizon and found out both carriers the phone would not work right. The data worked but the call and texting did not.
As a side note, I was informed by someone who was on sprint, and he said that you had to get on the network unrooted and locked bootloader, once registered you could then root and get the bootloader unlocked and be just fine.
So I then proceeded to unroot the phone ie: removing everything root, and keeping twrp with an unocked bootloader only, no sign of root. I took the phone back to the stores and tried again, and the phone still had the same issue.
After finally finding a way to finally after 6mo lock the bootloader again, and was at pure stock, locked bootloader and no root.
What this tells me is that some how verizon and sprint both some how some way detect an unlocked bootloader....how? I have no clue, I've never in my 5+ years of rooting multiple phones, never ever ever seen anything like this. The only reason I know this is what it was, is from common deduction and reasoning.........unroot = still doesn't work.....locked bl = works fine with not a single issue. Keep in mind this was all with base stock rom, not a custom rom.....everything was stock, accept for the root and un;ocked bootloader part. I rooted with magisk.
Since I had a very long time and issue with locking the bootloader, (about 6mo) after trying a ton of things, without resolve, I FINALLY got the bootloader locked.
If it's going to be anything like before trying to get it locked again to work on sprint and verzion, I really do not want to bother with unlocking it to begin with. It was an utter nightmare to get locked, no matter what I tried it just would not lock for whatever reason.
So given all that, my question is, how hard or easy is it now to unlock and lock the bootloader?
Hi all. I have been searching high and low for information on this specific question:
Will activating an unlocked Pixel 3a on Verizon disable the OEM Unlock and bootloader unlock capability?
I got a Verizon variant before I realized that there was not way to unlock the bootloader. Bummer. So, I returned it for an Unlocked version from Google, which I just received tonight. I breezed through the setup (without the SIM card) and noticed that OEM Unlock was disabled stating I needed to connect to the internet. So, I enabled WiFi and the OEM Unlock was then available. It would seem that I an now able to follow the unlocking procedure.
My goal is to unlock the bootloader and root, but do I have to do it immediately? My concern is that activating the phone with my Verizon SIM could:
1) Prevent unlocking the bootloader in the future if I don't unlock it before I activate with SIM (research seems to indicate that factory resets will undo disabling OEM Unlock if this can happen if I understand correctly)
2) Re-lock an unlocked bootloader - maybe this is not even possible?
I don't want to mess this up. All the info I am finding are discussions related to trying to unlock a Verizon variant and I cannot find good info on what happens to bootloader unlocking options on unlocked phones that are activated on Verizon. The only reason I may want to delay this process is because I dont have a lot of time at the moment and would rather not rush the bootloader unlock and root process. However, my HTC 10 is in bad shape and need a phone to get through the holidays. I was hoping that I could activate it on Verizon now, use it with its locked bootloader for a few weeks, and when things cool down after the holidays, implement the bootloader unlock and root.
If that is not advisable, what about unlocking the bootloader immediately (doesn't seem too hard and I have used ADB before), and activating without root. Then root later? Any possibility of concern #2?
Can OTA's re-lock a bootloader and prevent future unlocking?
I appreciate anyone's incite, experience, or links to the needed information for clearing this up. Thanks you!
I would advise you to unlock the bootloader asap. If you wait it will be a pain later because unlocking causes loss of data. If you don't care about that, wait as long as you like.
As far as Verizon is concerned, if the phone is unlocked, I don't see how they could possibly lock the bootloader. They may restrict your services but they can't touch the lock status of a device you purchased.
Sent from my Pixel 3a using Tapatalk