I got received a Nexus 6 the other day and can't unlock it because it wants the last account user to sign in. But know one knows what it is. I tried to wipe data/factory reset from what motorola support said but it still brings me into the screen asking for the email address. Any way to bypass this?
Factory Reset Protection is what you're dealing with. It's virtually impossible to bypass, meaning you have to know the information for the last account used on the device. Don't ask Google for help, because they won't provide any.
Strephon Alkhalikoi said:
Factory Reset Protection is what you're dealing with. It's virtually impossible to bypass, meaning you have to know the information for the last account used on the device. Don't ask Google for help, because they won't provide any.
Click to expand...
Click to collapse
So there is absolutely nothing at all that can be done? The only thing I don't have is the account info so there must be something that can just completely wipe it of its memories.
Masonator_89 said:
So there is absolutely nothing at all that can be done?
Click to expand...
Click to collapse
Correct. Unless you know the account info, you will be unable to access the device. As for completely wiping the memory, that can't be done via software otherwise FRP would have no teeth.
Strephon Alkhalikoi said:
Correct. Unless you know the account info, you will be unable to access the device. As for completely wiping the memory, that can't be done via software otherwise FRP would have no teeth.
Click to expand...
Click to collapse
Alright, thanks.
Can't he install a custom ROM then NOT flash gapps? Hoping it wouldn't come up with setup, then tick OEM unlock that way it wontask for FRP.
Twiggy000b said:
Can't he install a custom ROM then NOT flash gapps? Hoping it wouldn't come up with setup, then tick OEM unlock that way it wontask for FRP.
Click to expand...
Click to collapse
His bootloader is locked, and as such he can't flash anything. If the bootloader was unlocked, FRP would have been disabled and this discussion wouldn't have taken place.
Strephon Alkhalikoi said:
His bootloader is locked, and as such he can't flash anything. If the bootloader was unlocked, FRP would have been disabled and this discussion wouldn't have taken place.
Click to expand...
Click to collapse
Isn't the boot loader the little menu with the tons of technical data/options?
@Masonator_89: Yep.
What do you mean it is locked? Like it is operational and everything.
@Masonator_89: The bootloader being locked doesn't prevent the bootloader from functioning, but does prevent you from making changes to the device. Take a careful look in the bootloader data at the bottom of the screen. It reports its status (locked or unlocked).
To unlock the bootloader you have to boot into Android, dig into the hidden developer options menu in settings, toggle the OEM Unlocking switch, then enter the bootloader to actually unlock the bootloader. Since you are dealing with FRP, you can't get into Android to toggle OEM Unlocking so the bootloader can be unlocked.
With an unlocked bootloader FRP is disabled. Since FRP is functioning, the bootloader must be locked.
Strephon Alkhalikoi said:
@Masonator_89: The bootloader being locked doesn't prevent the bootloader from functioning, but does prevent you from making changes to the device. Take a careful look in the bootloader data at the bottom of the screen. It reports its status (locked or unlocked).
To unlock the bootloader you have to boot into Android, dig into the hidden developer options menu in settings, toggle the OEM Unlocking switch, then enter the bootloader to actually unlock the bootloader. Since you are dealing with FRP, you can't get into Android to toggle OEM Unlocking so the bootloader can be unlocked.
With an unlocked bootloader FRP is disabled. Since FRP is functioning, the bootloader must be locked.
Click to expand...
Click to collapse
Thanks for clarifying!
Incorrect information. I unlocked my bootloader on Day 1. I have had this situation arise after a year when I did a reset and this is what I did to bypass it (may not work for everyone). Haven't tried this on Nougat but it worked previously and saved me lots of headache. I factory reset phone again and when setup came up, I tapped the 4 corners to bypass setup. Then I just added an account. Like I said, your mileage may vary. Unlocking a bootloader does not necessarily prevent this from happening. I think it's stupid af. I had to change my dang password because google told me via email that someone tried to log into my account from california or some shizzz. BAM! locked out. Hope this helps
If you do some google searching... It says a few places that OEM unlocking disables any google locking... So, just to clarify I'm pretty sure it is possible with our devices. Not so much for my mothers G4.
buschris said:
Incorrect information. I unlocked my bootloader on Day 1. I have had this situation arise after a year when I did a reset and this is what I did to bypass it (may not work for everyone). Haven't tried this on Nougat but it worked previously and saved me lots of headache. I factory reset phone again and when setup came up, I tapped the 4 corners to bypass setup. Then I just added an account. Like I said, your mileage may vary. Unlocking a bootloader does not necessarily prevent this from happening. I think it's stupid af. I had to change my dang password because google told me via email that someone tried to log into my account from california or some shizzz. BAM! locked out. Hope this helps
Click to expand...
Click to collapse
I dispute your assertion that the information is incorrect, especially as other members have reported that FRP was disabled when the bootloader was unlocked.
As for the old (Android 2.x-era) trick of bypassing setup, I seriously doubt Google would have left that unpatched. If that were true then Rootjunky would have never needed to post "how-to-bypass" videos, none of which utilize that trick.
@Masonator_89
This has worked for me in the past. But i cant remember if i needed an unlocked bootloader or not.
https://www.youtube.com/watch?v=YjulfoWDnuM
older way to bypass FRP
http://forum.xda-developers.com/nexus-6/general/guide-frp-bypass-solution-usb-otg-t3261846
SynisterWolf said:
@Masonator_89
This has worked for me in the past. But i cant remember if i needed an unlocked bootloader or not.
https://www.youtube.com/watch?v=YjulfoWDnuM
older way to bypass FRP
http://forum.xda-developers.com/nexus-6/general/guide-frp-bypass-solution-usb-otg-t3261846
Click to expand...
Click to collapse
That first video link (which showed me another more in depth video) really actually absolutely helped!!!! I'm absolutely amazed! Very much thanks to you (and everyone who said it couldn't be done)
@Masonator_89: Since there was no way to know what version of Android was on the device, I have to assume the latest version, which is pretty well nailed down. You've reminded me however not to get involved in Factory Reset Protection discussions in the future.
XDA moderators and staff don't agree with my stance on this, but bypassing FRP only encourages thieves instead of discouraging them. I do not believe discussion of how to bypass FRP should be permitted on site, as the entire intent of FRP is to prevent what you accomplished: getting into the device so it can be reset. Since it's impossible to know whether the person asking is on the up and up, I have to assume that the person asking doesn't actually own the device.
The only legitimate methods of defeating FRP are to have the seller remove the account from the device, or for the seller to provide you with the username and password used to get into the device. Providing any other method of accessing the device when FRP is in play opens up the poster to being an accessory to a potential crime.
I understand that this position will lead to a lot of "collateral damage" since perfectly honest people like you seem to be will get caught in the crossfire. I apologize for that, but it is a cost I'm willing to pay to ensure my ethics remain intact in spite of XDA's policies on the matter.
Related
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Welcome to the club!
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
wtherrell said:
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
Click to expand...
Click to collapse
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
freeman_g said:
Welcome to the club!
Click to expand...
Click to collapse
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
If you want to update to the newest OTA you dont need to lock the bootloader back up. The bootloader can remained unlocked when doing this. Its been posted all over XDA about not having to do this. The only time you may want to relock the bootloader is when selling it to someone or trading it in. Thats it.
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3053497.
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
wtherrell said:
http://forum.xda-developers.com/showthread.php?t=3053497.
Click to expand...
Click to collapse
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
necroside007 said:
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
Click to expand...
Click to collapse
well not to come off rude but number one rule for xda before u post is search, and as you can tell there are multiple threads on this exact same topic.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
AndrewZorn said:
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
Click to expand...
Click to collapse
returning to stock and relocking the bootloader dont go together. You can return to stock and not lock the bootloader. Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
the_rooter said:
Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
Click to expand...
Click to collapse
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
rootSU said:
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
Click to expand...
Click to collapse
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
the_rooter said:
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
Click to expand...
Click to collapse
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal. I don't care if there's something about the bootloader unlocked that you find valuable. I got tired of the tinkering and decided I just wanted my Nexus 6 to be back the way it was - completely.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
Click to expand...
Click to collapse
If guides don't say that at the moment, they definitely should now. I'll look at ours here and ask the OP's to update.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal.
Click to expand...
Click to collapse
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
the_rooter said:
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
Click to expand...
Click to collapse
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
AndrewZorn said:
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
Click to expand...
Click to collapse
its not laughable. unless u buy an extended warranty the warranty is up after a year so you would have to figure the work yourself. If you are in the boat where u locked it back up and took the ota and bootlooping or whatever. your stuck till there is a solution. if u want to return to stock . Just return to stock but dont lock the bootloader back up, and flash. its that simple.
Edit: we are not arguing. Its just i have my way on repairs and you have yours. its a debate i guess
Edit: this issue has been brought up and is being researched. i was talking about the returning to stock for repairs dont try and put words in my mouth saying i know a fix.
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
clairez said:
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
Click to expand...
Click to collapse
Well its your choice. I recommend not locking it. However, if you do lock it and end up bricked, at least we know its the locking that causes the loop and not the flash but.... Is it worth it?
If your organization is supplying the device ( or the money for the device) you have no business unlocking it. At my organization people are fired for such things.
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Sent from my Nexus 6
And if it is the unlocking/locking that causes the boot loop (hard brick) then any flashing operation that requires unlocking the bootloader will require that the system remain unlocked forever. A penalty that will afflict a portion (large?) of the Nexus 6 community. Was this an issue before 5.0? Makes one wonder if this is by design or accidental.
DebianDog said:
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Click to expand...
Click to collapse
Yes we totally can. If you work for my company and decide you would rather use your own device for corporate email and data, that data is ours. You may use your own device but we will manage it. If it gets stolen, we will wipe it. You will adhere the same policies for corporate owned data as you will with a phone supplied by us. You will have lock screen, you will be unrooted. You will keep your bootloaders locked. Or you can use this sh*tty Nokia.
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
This post was not meant to be an organizational ethics discussion, just a request for guidance. If anyone can give me input on the original questions, I would greatly appreciate it. Especially the wipe side effect of the lock operation. Do not want to spend a lot of time configuring the device if it will be erased.
Thanks in advance
clairez said:
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
Click to expand...
Click to collapse
Yep. Absolutely.
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
rootSU said:
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
Click to expand...
Click to collapse
Good point. That's why more heads are better than one. I still think my theory would work, but yet I wouldn't be willing to risk my N6 on it, wouldn't suggest others do either.
Sent from my Nexus 6 using XDA Free mobile app
clairez said:
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
Click to expand...
Click to collapse
1. Unsure at this point. If everything is stock (including recovery), I would suspect that it would be OK, but it has not been verified yet.
2. After you flash the bootloader, radio, boot, system and recovery images, and format data and cache, then would be the time to re-lock and then boot into Android.
3. Yes. But based on what I gather, the process of wiping on an N6 (when unlocking or locking the bootloader) is done via the stock recovery. So, if you have a custom recovery when you lock, I suspect that it will give you a boot loop.
4. I don't know.
Update - Success
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
clairez said:
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Click to expand...
Click to collapse
Interesting. And you were 100% stock?
Perhaps the loop isn't caused by the lock itself then. Good to know, though still people need to be cautious
androiduser2011 said:
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
Click to expand...
Click to collapse
A few question, for understanding:
Rooted?
Stock or TWRP recovery?
Encrypted?
Thanks
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
This happened to me literally tonight. I tried to lock the boot loader which was successful, from there the device would start to root into teamwin recovery. So from there I tired to flash a fully stock rom but the bootloader was locked. And then because you need permission from the OS to unlock the bootloader I was stuck. What I did is from the locked bootloader I ran the stock oem flash from a fresh download and check from wugs with the force flash enabled (make sure everything is right) miracles of miracles it worked and came back to me.
I learned my lesson. Never shall my bootloader be relocked unless my phone is out of my possession. I'm spending the rest of the time making sure that nobody can get to my data. I love the phone, but that data is my life.
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1 per official instructions from Google. If it can be determined that having TWRP recovery installed is the cause of bricks then users can be instructed to be sure stock recovery is installed before relocking. My own thoughts are that this is a bug of sorts with the new security features of lollipop and I'm sure the talented folks here will get it figured out. I'm 100% stock on LMY47D that I sideloaded. Not sure I can afford to risk my 6 but I offer any assistance I can to help get this figured out.
Evolution_Freak said:
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1
Click to expand...
Click to collapse
Some of the "bricks" happened after fully flashing stock, i.e they had stock recovery. They had a locked bootloader, an OS that didn't boot and a recovery that couldn't flash anything. If they had TWRP installed, they could format data and flash a rom.zip no problem.
hi all,
Just having a thought (might not work but thought i'd ask)
Some OTA's / Firmwares which you can install from the bootloader have the ability to re-lock the device, would the same be possible for the other way around?
I mean i'm on a locked bootloader now cos of the crap i installed which updated me to 9.1, it relocked the bootloader, I can turn on OEM unlocking (FRP) but obviously it remains unlocked.
Would there be a way to repackage a firmware package so that it does the opposite to re-locking?
I think everyone has pretty much given up on Huawei devices, I was just trying to disable zRAM and i can't.
Any thoughts ? Is this a possible avenue? or is this simply not going to work?
I'd guess the latter but thought i'd ask.
Which firmware version relocked your bootloader? I can perhaps take a look at it in my free time.
dladz said:
hi all,
Just having a thought (might not work but thought i'd ask)
Some OTA's / Firmwares which you can install from the bootloader have the ability to re-lock the device, would the same be possible for the other way around?
I mean i'm on a locked bootloader now cos of the crap i installed which updated me to 9.1, it relocked the bootloader, I can turn on OEM unlocking (FRP) but obviously it remains unlocked.
Would there be a way to repackage a firmware package so that it does the opposite to re-locking?
I think everyone has pretty much given up on Huawei devices, I was just trying to disable zRAM and i can't.
Any thoughts ? Is this a possible avenue? or is this simply not going to work?
I'd guess the latter but thought i'd ask.
Click to expand...
Click to collapse
Nope, that won't work!
Aodrulez said:
Which firmware version relocked your bootloader? I can perhaps take a look at it in my free time.
Click to expand...
Click to collapse
Oh god, will have to find the bugger, 318 I think.
Pretoriano80 said:
Nope, that won't work!
Click to expand...
Click to collapse
There's no service firmware we could flash they would unlock it?
dladz said:
There's no service firmware we could flash they would unlock it?
Click to expand...
Click to collapse
Nope! DLOAD re-lock bootloader to factory condition, but there's no way to unlock the bootloader with it.
I don't think Huawei will give you the unlock code a second time, but maybe you will be lucky, who knows.
Maybe you can retrieve it from an email from them!?
Edit: You can download your HuaweiID data from Settings - > HuaweiID - > Privacy Center but i doubt you will get the bootloader code from there
Pretoriano80 said:
Nope! DLOAD re-lock bootloader to factory condition, but there's no way to unlock the bootloader with it.
I don't think Huawei will give you the unlock code a second time, but maybe you will be lucky, who knows.
Maybe you can retrieve it from an email from them!?
Edit: You can download your HuaweiID data from Settings - > HuaweiID - > Privacy Center but i doubt you will get the bootloader code from there
Click to expand...
Click to collapse
I've spoke with them, they said they've not heard of a situation like this.
Bare in mind that this is information that has been passed to me before. Which is a correspondence, they are obligated to provide it regardless.
I don't believe it was in an email and I've checked all accounts
Thanks for sharing this topic
Thanks for sharing your experiences.
Hey guys,
I've searched the forum but nobody seems to have reported the issue I'm experiencing. The way the posts are worded, unlocking the Tab S8+ is a given. I know the US S22 has no OEM Unlocking officially supported. I've followed all the workarounds to get the option to appear to no avail.
My only theory is that VZW hasn't yet unlocked my S8+ (if it was ever locked to begin with, nevertheless I've owned it less than 60 days). Can anybody confirm if this model can be bootloader unlocked by conventional means either prior or after carrier unlock?
Hi! I'm going to try to find the other user's post who enlightened me in this section, but I might have trouble finding it.
Effectively, no U.S. carrier's version of previous and current Samsung Galaxy Tabs can have the bootloader unlocked - at least that's what I remember them telling me. You have to buy the Wi-Fi only version to be able to unlock the bootloader.
Now - SIM unlock, I know nothing about on the Tabs. Normally no matter what U.S. carrier, that I'm aware of, once you pay off your device (if financed), they'll SIM unlock the device, and although you can relate the two things (SIM and bootloader unlocking), they are completely separate and it's only certain U.S. phones (not Samsung phones or tablets) that getting SIM unlock enables you to also do OEM unlocking, and therefore be able to unlock the bootloader.
Verizon never allows the bootloader to be unlocked on any kind of device, no matter what, and all U.S. Samsung carrier devices - both phones and tablets, are never able to get their bootloader unlocked. I'm not including the rare exception that there's a hack to be able to get root - but most hacks circumvent the locked bootloader - they don't often actually allow the bootloader to be unlocked, and this sort of thing is rarer and rarer anymore.
Edit: I believe this is the post, by @googlephoneFKLenAsh.
Thank you for your thorough explanation. I was expecting the Tab to be the same situation as with the U.S. Galaxy phones, I just wasn't able to find confirmation of that.
I know Verizon is hostile to bootloader unlocking (case in point Pixel). So it was either gonna be my carrier and if not that my region.
Tablets do on rare occasion are exceptions (iirc ATT doesn't carrier lock tablets) so barring an explanation elsewhere I figured I'd post and have that question answered for myself and those concerned.
I don't understand the motivation behind it given that unlocking is already a process that can't be exploited by malware/spyware and carries a myriad of drawbacks/risks.
GlitterFartzz said:
... given that unlocking is already a process that can't be exploited by malware/spyware and carries a myriad of drawbacks/risks.
Click to expand...
Click to collapse
You're welcome!
I'm not sure I understand what you're saying here, or I'm not sure if you meant to say it differently.
An unlocked (or unlockable) bootloader can definitely be exploited without our awareness.
I agree that I don't understand the motivation - at least in contrast to AT&T and T-Mobile which apparently do allow bootloaders to be unlocked once their phones are paid for and SIM unlocked. I also don't know why or if AT&T and T-Mobile would not allow Samsung tablets to be bootloader-unlocked while allowing other brands.
Overall I think the motivation is the prevention of potentially more problems that users will have and also potentially brick their device and then they wind up with an unhappy customer because the carrier won't consider the device under warranty since it had been fiddled with in a way they're not willing to support (understandably).
Additionally, root malware would potentially be using their mobile network for nefarious purposes.
GlitterFartzz said:
Hey guys,
I've searched the forum but nobody seems to have reported the issue I'm experiencing. The way the posts are worded, unlocking the Tab S8+ is a given. I know the US S22 has no OEM Unlocking officially supported. I've followed all the workarounds to get the option to appear to no avail.
My only theory is that VZW hasn't yet unlocked my S8+ (if it was ever locked to begin with, nevertheless I've owned it less than 60 days). Can anybody confirm if this model can be bootloader unlocked by conventional means either prior or after carrier unlock?
Click to expand...
Click to collapse
I have the same s8+ 5G model and I'm unable to get to the unlock option from download mode. I have however managed to turn on the OEM unlock from android. It is very fiddly to get to the OEM unlock option, and it will disappear afterward. The method I used is to quickly go to the developer's options before the tablet fully started after a reboot. It will let you toggle the OEM unlock.
I'm waiting if someone found a way to get the bootloader unlock from download mode. Obviously I have tried all other methods ( e.g> cable + up+down volume )
It's actually not possible to unlock via download mode. Download mode is only used for Odin flashing and the like.
You have to get to the bootloader which I believe is power and vol up WITHOUT using the cable afaik.
If by some catastrophic reason you can't get into the bootloader after that, you can boot the device, enable USB debugging, plug into pc, and run adb reboot bootloader or adb reboot recovery.
killerzac said:
I have the same s8+ 5G model and I'm unable to get to the unlock option from download mode. I have however managed to turn on the OEM unlock from android. It is very fiddly to get to the OEM unlock option, and it will disappear afterward. The method I used is to quickly go to the developer's options before the tablet fully started after a reboot. It will let you toggle the OEM unlock.
I'm waiting if someone found a way to get the bootloader unlock from download mode. Obviously I have tried all other methods ( e.g> cable + up+down volume )
Click to expand...
Click to collapse
Have you been able to get the OEM unlocking switch to reappear after you've already toggled it?
If so, is it still on when it reappears? If it is then there's a high likelihood the device can then be unlocked.
GlitterFartzz said:
Have you been able to get the OEM unlocking switch to reappear after you've already toggled it?
If so, is it still on when it reappears? If it is then there's a high likelihood the device can then be unlocked.
Click to expand...
Click to collapse
yes, it remains as OEM unlocked. I even tried to see if this could be false positive by flipping OEM unlock back and forth. It has shown the setting is persistence, if you set OEM unlock it will stay unlock. If you set it back to OEM lock. It stays as OEM lock.
GlitterFartzz said:
It's actually not possible to unlock via download mode. Download mode is only used for Odin flashing and the like.
You have to get to the bootloader which I believe is power and vol up WITHOUT using the cable afaik.
If by some catastrophic reason you can't get into the bootloader after that, you can boot the device, enable USB debugging, plug into pc, and run adb reboot bootloader or adb reboot recovery.
Click to expand...
Click to collapse
nope, doesn't work. I tried ADB reboot bootloader or use the recovery to boot to bootloader, still no joy. I just can't get to the bootloader option which allows me to see the "Unlock bootloader options"
killerzac said:
nope, doesn't work. I tried ADB reboot bootloader or use the recovery to boot to bootloader, still no joy. I just can't get to the bootloader option which allows me to see the "Unlock bootloader options"
Click to expand...
Click to collapse
You are supposed to boot into bootloader mode and then use the fastboot tool to trigger the unlock.
Either fastboot flashing unlock or fastboot oem unlocking. Something like that.
GlitterFartzz said:
You are supposed to boot into bootloader mode and then use the fastboot tool to trigger the unlock.
Either fastboot flashing unlock or fastboot oem unlocking. Something like that.
Click to expand...
Click to collapse
yes, that is not working ( bootloader mode - doesn't let you choose ). Fastboot doesn't work with samsung, they deliberately change their code, try it yourself.
GlitterFartzz said:
You are supposed to boot into bootloader mode and then use the fastboot tool to trigger the unlock.
Either fastboot flashing unlock or fastboot oem unlocking. Something like that.
Click to expand...
Click to collapse
These are the necessary steps on this tablet to unlock the bootloader - it doesn't involve Fastboot from the Platform Tools. I am aware that on standard Android/AOSP that it does involve Fastboot since for my phones I choose Google Pixel devices.
skrowl said:
Step 1 - Prepare your Tablet (only necessary for first install on unrooted device)
While Frija is downloading the firmware, prepare your device by doing the following:
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Turn on OEM unlocking
NOTE: If the OEM Unlocking option doesn't appear, connect the device to the internet, wait a few minutes, then try again
Power tablet completely off (Hold volume down + power button if you haven't changed the Bixby settings)
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
Press volume up again to confirm, the tablet will reboot
Unplug your tablet from USB
Go through initial setup. Don't bother copying files or installing anything.
Skip signing in to your Google account and Samsung account. You won't be using them for this step.
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Reboot the tablet
Click to expand...
Click to collapse
roirraW edor ehT said:
These are the necessary steps on this tablet to unlock the bootloader - it doesn't involve Fastboot from the Platform Tools. I am aware that on standard Android/AOSP that it does involve Fastboot since for my phones I choose Google Pixel devices.
Click to expand...
Click to collapse
Ah I wasn't aware that some devices do not require fastboot to finalize unlock and instead immediately unlock when toggling OEM Unlocking.
Is it possible to confirm the unlock by getting the bootloader vars using fastboot however?
Alternately, what's the easiest way to confirm the bootloader is unlocked?
killerzac said:
yes, that is not working ( bootloader mode - doesn't let you choose ). Fastboot doesn't work with samsung, they deliberately change their code, try it yourself.
Click to expand...
Click to collapse
According to this post, you should have your bootloader unlocked now. Could you try following the instructions listed and report back?
Could you also explain in more detail how you can get the OEM unlocking option to appear?
I seem to be having no luck. You do own a US model, correct?
roirraW edor ehT said:
These are the necessary steps on this tablet to unlock the bootloader - it doesn't involve Fastboot from the Platform Tools. I am aware that on standard Android/AOSP that it does involve Fastboot since for my phones I choose Google Pixel devices.
Click to expand...
Click to collapse
GlitterFartzz said:
Ah I wasn't aware that some devices do not require fastboot to finalize unlock and instead immediately unlock when toggling OEM Unlocking.
Is it possible to confirm the unlock by getting the bootloader vars using fastboot however?
Alternately, what's the easiest way to confirm the bootloader is unlocked?
Click to expand...
Click to collapse
Actually, although the instructions don't make it clear without the context of seeing what's on the screen, steps 5 through 7 are what unlock the bootloader. OEM Unlocking still only (normally) enables unlocking the bootloader:
5. While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
6. Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
7. Press volume up again to confirm, the tablet will reboot
Click to expand...
Click to collapse
Also, just as on the Google Pixel and many or all other devices, the easiest way to see that your bootloader is unlocked is the (IMHO) big honking stupid advertisement when you reboot or turn on your device that the bootloader is unlocked and the (paraphrasing) "hey thieves, if you just stole this device, you're in luck because you can hack into someone's account easier since this device's bootloader is unlocked" that stays on the screen seemingly forever.
I know that if they're actually technically savvy they'd be able to find that out anyway, but all this forced pre-boot screen does is punish those who unlock their bootloader. End Rant.
Ah I see what you mean, so It's been stated that US devices either resist BL unlocks e entirely or require alternative solutions.
That being said, has there been reports of UI bugs causing the option to appear on USA models under certain circumstances?
roirraW edor ehT said:
Actually, although the instructions don't make it clear without the context of seeing what's on the screen, steps 5 through 7 are what unlock the bootloader. OEM Unlocking still only (normally) enables unlocking the bootloader:
Also, just as on the Google Pixel and many or all other devices, the easiest way to see that your bootloader is unlocked is the (IMHO) big honking stupid advertisement when you reboot or turn on your device that the bootloader is unlocked and the (paraphrasing) "hey thieves, if you just stole this device, you're in luck because you can hack into someone's account easier since this device's bootloader is unlocked" that stays on the screen seemingly forever.
I know that if they're actually technically savvy they'd be able to find that out anyway, but all this forced pre-boot screen does is punish those who unlock their bootloader. End Rant.
Click to expand...
Click to collapse
GlitterFartzz said:
That being said, has there been reports of UI bugs causing the option to appear on USA models under certain circumstances?
Click to expand...
Click to collapse
No. I've read every post in this section starting from when I pre-ordered mine (February?), and the only post I've seen about being able to enable OEM Unlocking was from @killerzac.
Too bad that doesn't easily lead to actually being able to unlock, even if the OEM Unlocking aspect was widely reproducible.
killerzac said:
yes, that is not working ( bootloader mode - doesn't let you choose ). Fastboot doesn't work with samsung, they deliberately change their code, try it yourself.
Click to expand...
Click to collapse
Have you found a solution?
I'm in such a weird place. I'm in the UK my first Tab S8 Ultra unlocked originally but after relocking the bootloader I can't get the OEM Unlock to reappear. I needed an unlocked tablet so I bought another one and this one has never had the OEM Unlock option. Waited many sets of 7 days trying different Samsung accounts and Google accounts. I do notice like you that if you get to dev options quickly after boot OEM Unlock is there but it definitely hasn't loaded properly at this point and changing it does nothing. Tablet never gives the bootloader unlock option when you go through the process.
The only thing ive noticed is on both devices the KG Status is Active (Viewed in Download Mode). My S22 which has the OEM Unlock option shows it as inactive. Samsung have told me that I can send the tablet to them and they will look at it but I can't be without it at the moment. Don't know if both my tablets are wrongly reporting that they are in finance and MDM is locking it potentially following my Samsung account to the new tablet I bought.
Really annoyed with Samsung now spent hours on web chats with them where they keep making you reset the tablet and won't escalte it.
Even more annoying they won't look at my first tablet because it did unlock initially so the warrenty is void now that it won't unlock they have said they will replace the mainboard for £800.
@Jono0907 That really sucks! I'm sorry to hear about all the trouble. I "swear" - customer service these days. Someday, companies will just stop even having the (mostly) nearly useless customer service that they do now, and they just won't have any at all.
Jono0907 said:
Have you found a solution?
I'm in such a weird place. I'm in the UK my first Tab S8 Ultra unlocked originally but after relocking the bootloader I can't get the OEM Unlock to reappear. I needed an unlocked tablet so I bought another one and this one has never had the OEM Unlock option. Waited many sets of 7 days trying different Samsung accounts and Google accounts. I do notice like you that if you get to dev options quickly after boot OEM Unlock is there but it definitely hasn't loaded properly at this point and changing it does nothing. Tablet never gives the bootloader unlock option when you go through the process.
The only thing ive noticed is on both devices the KG Status is Active (Viewed in Download Mode). My S22 which has the OEM Unlock option shows it as inactive. Samsung have told me that I can send the tablet to them and they will look at it but I can't be without it at the moment. Don't know if both my tablets are wrongly reporting that they are in finance and MDM is locking it potentially following my Samsung account to the new tablet I bought.
Really annoyed with Samsung now spent hours on web chats with them where they keep making you reset the tablet and won't escalte it.
Even more annoying they won't look at my first tablet because it did unlock initially so the warrenty is void now that it won't unlock they have said they will replace the mainboard for £800.
Click to expand...
Click to collapse
Hi Jono,
I haven't look at it since and I'm pretty sure your finding is very much same as mine, Quote "Table never gives the bootloader unlock option". I gave my s8+ to my 5 years old son as his toy now. Piece of garbage without ROOTing for me. I'm reverting back to using my tabS6. You might hapend to see me on the northen line with my TabS6, very rare scene.
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening