Related
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Looks like I'm not the only one I have the same issue and nothing works
AndrewZorn said:
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Click to expand...
Click to collapse
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
psybill said:
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
Click to expand...
Click to collapse
Yeah I think that's what I may have done too. I was just trying to go back to 100% stock (ignoring 5.1 even).
And of course NOW the 5.1 image is up on Google's page.
Have the same situation: flash 5.1 OTA and then wiped system
Now I can't unlock bootloader (as system just cant boot) and can't flash stock image (as system.img can't be flashed with locked bootloader)
I do not want to believe this is a brick, but it is very likely it
Sadly I've just done the same thing. ADB updated from 5.0.1 to 5.1, and the system.img didn't copy correctly. Phone wont boot past the Google splash screen, and I can't flash a factory image to recover the phone, because in order to unlock the bootloader I have to enable the option in developer settings, which I can't get to because the phone wont boot!
I understand the purpose of having an extra layer of security to prevent malicious types from trying to flash factory images onto stolen devices, but surely any system that allows a user to brick a device simply by leaving a setting unchecked (in a hidden menu, no less!) is asking for trouble? Particularly on a developer orientated device like a Nexus.
It seems crazy that a developer can ADB the official Google Android OTA zip, using the official Google Android SDK, onto the official Google Android flagship device, and the simple corruption of one of the sent files can cause the device to become totally unusable. Surely, say, providing an option in the developer option settings to PIN protect the bootloader, rather than just preventing it from being unlocked all together, would be a more sensible choice?
For what it's worth, I explained my situation to Google, and they are replacing the phone under warranty. This is probably your best (or only) option at this stage.
Good luck, and please let me know if you do manage to find a work-around/ solution to your woes!
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
rootSU said:
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
Click to expand...
Click to collapse
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It depends what you're expecting in future. If you want OTA, you'll need everything to be 100% stock and the right version. If you don't care about that, minimum is system.img and boot.img.
i tried to downgrade my bootloader through fastboot from 5.1's bootloader to 5.0.1 and fastboot throws an error from moto saying it cant be downgraded.
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
freebee269 said:
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
Click to expand...
Click to collapse
I had been running Chroma 5.02 with the 5.1 bl and radio. I reverted the radio because of issues with TMo, but the bl seemed fine. FWIW, I made all my changes via fastboot.
kenbrownstone said:
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It resets on boot. Check it boots before relocking
rootSU said:
It resets on boot. Check it boots before relocking
Click to expand...
Click to collapse
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
naresh2990 said:
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
Click to expand...
Click to collapse
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
naresh2990 said:
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
Click to expand...
Click to collapse
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
pwned3 said:
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Konfuzion said:
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
rootSU said:
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
Click to expand...
Click to collapse
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
the_rooter said:
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
Click to expand...
Click to collapse
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
the_rooter said:
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
Click to expand...
Click to collapse
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said after a reboot it goes unchecked so if i check it and then reboot to recovery wouldnt that uncheck it again?
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.
I got my H9L 2 months back and had rooted it (and unlockedd bootloader). Im having a big battery issue battery drains too fast. I want to get it to service centre as waranty is not over.
I've read posts saying if I relock bootloader I'll get waranty back but some says I won't get back warranty even if I relock bootloader.
Can someone sort this out please
IF you've unlocked the bootloader and rooted the device you have no warranty in the eyes of the manufacturer, it states this in the terms and conditions when you get your bootloader code from them.
See when you unlock the bootloader you get a warning screen upon booting the device and relocking the bootloader will not get rid of that warning.
However have you tried to see if the battery issue is intact an software issue. I.e have you wiped caches, checked if an app such as Google assistant WhatsApp Facebook is running in the background. Do you have the same issue when booting android into safe mode????
Sent from my SHIELD Tablet K1 using Tapatalk
hacktrix2006 said:
IF you've unlocked the bootloader and rooted the device you have no warranty in the eyes of the manufacturer, it states this in the terms and conditions when you get your bootloader code from them.
See when you unlock the bootloader you get a warning screen upon booting the device and relocking the bootloader will not get rid of that warning.
However have you tried to see if the battery issue is intact an software issue. I.e have you wiped caches, checked if an app such as Google assistant WhatsApp Facebook is running in the background. Do you have the same issue when booting android into safe mode????
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
That's strange. I've relocked it today after flashing compete stock using HuRupdater tool.
I'm not having the warning screen I had earlier when my bootloader was unlocked.
So does that mean I'll be able to claim my waranty now?
And I've tried different ROMs the issue persists.
If they ask if I've unlocked the bootloader(since I've given my product number they might know) I'll just tell that I took the unlock code just in case, as they were shutting it down and that I haven't used it. Well at least that's the plan
So will they know that I've unlocked it earlier if there is no warning screen? As I've told I have complete stock firmware including kernal and recovery like @Fredin_ told.
Please reply fast.
If your no longer showing that Warning message after going back to stock then you can try and claim warranty if you wish, however they might have other ways to finding out if the bootloader has been unlocked.
So put your claim in and see what they do, they will either honor the Warranty or not Honor the Warranty and give you a quote for the work.
Personally if i unlock my bootloader and root it i'd just put up with the issue as i fully knew that the warranty went when i unlocked the device.
But i will leave it upto you how you go about it.
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 Disabled​For 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 Disabled​For 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