Related
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.
Hi,
I have a problem with my Huawei P9 that I bought used. I realized during the reset that the Google account is blocked, but I no longer have the number of the person to whom I bought the phone.
I tried the videos to bypass frp, but I do not have access to the menu "help & feedback" (3:20 in the video)
https://www.youtube.com/watch?v=qSLJchfjQkM
I think that rom includes a new patch security :crying:
I'm looking for a way to install TWRP to change the rom and go Cyanogen to bypass FRP or attempt a downgrade of the official rom.
The concern is that my computer is not detecting the phone. A warning message tells me that the usb device is not recognized. I think it's a security of Huawei not to have a user use adb or other commands to change rom.
I think the bootloader is lock.
Do you know a way to bypass frp on huawei phones with the latest security update or is there a way to change rom with a bootloader lock phone and no possibility to go into the settings to allow the enable usb debbugging (since I'm stuck when I start the phone)
Thanks
Can you boot in system?
Aymericl31 said:
Hi,
I have a problem with my Huawei P9 that I bought used. I realized during the reset that the Google account is blocked, but I no longer have the number of the person to whom I bought the phone.
I tried the videos to bypass frp, but I do not have access to the menu "help & feedback" (3:20 in the video)
https://www.youtube.com/watch?v=qSLJchfjQkM
I think that rom includes a new patch security :crying:
I'm looking for a way to install TWRP to change the rom and go Cyanogen to bypass FRP or attempt a downgrade of the official rom.
The concern is that my computer is not detecting the phone. A warning message tells me that the usb device is not recognized. I think it's a security of Huawei not to have a user use adb or other commands to change rom.
I think the bootloader is lock.
Do you know a way to bypass frp on huawei phones with the latest security update or is there a way to change rom with a bootloader lock phone and no possibility to go into the settings to allow the enable usb debbugging (since I'm stuck when I start the phone)
Thanks
Click to expand...
Click to collapse
install or change to other model number firmware like EVA-AL10 to your device also check this https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849 .
albelushi7 said:
install or change to other model number firmware like EVA-AL10 to your device also check this https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849 .
Click to expand...
Click to collapse
How could he flash with the locked FRP?!
Btw, once you are (already) on AL10 Oreo, you don't have OEM Unlock option in Developers menu.
But to rebrand by HWOTA7, you needed FRP and Bootloader unlocked.
Moreover, even on AL10, if you boot to Fastboot you would see that FRP is unlocked.
And there is an attribute in one of the system XML files, if you enable it (root required for editing) you will unleash the previously hidden OEM Unlock option in Developers menu (ie, then you would have OEM unlock option in Developers menu just like in Nougat)
---------- Post added at 10:42 PM ---------- Previous post was at 10:30 PM ----------
Aymericl31 said:
Hi,
I have a problem with my Huawei P9 that I bought used. I realized during the reset that the Google account is blocked, but I no longer have the number of the person to whom I bought the phone.
I tried the videos to bypass frp, but I do not have access to the menu "help & feedback" (3:20 in the video)
https://www.youtube.com/watch?v=qSLJchfjQkM
I think that rom includes a new patch security :crying:
I'm looking for a way to install TWRP to change the rom and go Cyanogen to bypass FRP or attempt a downgrade of the official rom.
The concern is that my computer is not detecting the phone. A warning message tells me that the usb device is not recognized. I think it's a security of Huawei not to have a user use adb or other commands to change rom.
I think the bootloader is lock.
Do you know a way to bypass frp on huawei phones with the latest security update or is there a way to change rom with a bootloader lock phone and no possibility to go into the settings to allow the enable usb debbugging (since I'm stuck when I start the phone)
Thanks
Click to expand...
Click to collapse
Look at this thread
https://forum.xda-developers.com/p9/help/bought-phone-ebay-registration-wizard-t3840803
Similar case with the second-hand P9, where previous owner did not remove his Google account before removing his SIM card and giving the phone.
Read post #1 and then post #7 till the end - solution was DC Unlocker/Phoenix with the price of 15 Euros credits.
PS:
- When doing Factory Reset you should either had original SIM from the previous owner, or he had to remove himself his Google account(s) from the phone
This way phone reacts as if it was stolen (with the SIM card protected by PIN, and when the thief then removes original SIM and tries to bypass Google and FRP protection)
zgfg said:
How could he flash with the locked FRP?!
Btw, once you are (already) on AL10 Oreo, you don't have OEM Unlock option in Developers menu.
But to rebrand by HWOTA7, you need FRP and Bootloader unlocked.
Moreover, even on AL10, if you boot to Fastboot you would see that FRP is unlocked.
And there is an attribute in one of the system XML files, if you enable it (root required for editing) you can unleash the previously hidden OEM Unlock option in Developers menu (ie, then you would have OEM unlock option in Developers menu just like in Nougat)
---------- Post added at 10:42 PM ---------- Previous post was at 10:30 PM ----------
Look at this thread
https://forum.xda-developers.com/p9/help/bought-phone-ebay-registration-wizard-t3840803
Similar case with the second-hand P9, where previous owner did not remove his Google account before removing his SIM card and giving the phone.
Read post #1 and then post #7 till the end - solution was DC Unlocker/Phoenix with the price of 15 Euros credits.
PS:
- When doing Factory Reset you should either had original SIM from the previous owner, or he had to remove himself his Google account(s) from the phone
This way phone reacts as if it was stolen (with the SIM card protected by PIN, and when the thief then removes original SIM and tries to bypass Google and FRP protection)
Click to expand...
Click to collapse
Thank you everyone for your reply !
I do not understand how this paid service will solve the problem and not me (with all the knowledge available to xda volunteers)
Does DC Unlocker have privilege to unlock the bootloader with Huawei?
Aymericl31 said:
Thank you everyone for your reply !
I do not understand how this paid service will solve the problem and not me (with all the knowledge available to xda volunteers)
Does DC Unlocker have privilege to unlock the bootloader with Huawei?
Click to expand...
Click to collapse
Apparently their tool knows a back-door hook into the Bootloader
zgfg said:
Apparently their tool knows a back-door hook into the Bootloader
Click to expand...
Click to collapse
Ok thanks, I'll try their tools and I'll come back to post on this tread the result for the community
It works
Great !
The software is easy to use and i pay 15€ for unlock my Huawei P9.
I click on the unlocking button after putting my phone in fastboot mode and immediately, the phone reboot and makes a factory reset low level.
I think DC unlocker find system flaw that they alone know.
I do not know which version of android had the phone and which version of the security level but for this rom the security level of android is February 1, 2017 and the android version is 7.0 with EMUI 5.0.
Knowing that I could not bypass with 2018 methods found on youtube or xda, the phone downgraded to another version of android.
I think that their software finds a flaw for downgrade with the bootloader lock and that remove the frp protection
Thank you zgfg
Aymericl31 said:
Great !
The software is easy to use and i pay 15€ for unlock my Huawei P9.
I click on the unlocking button after putting my phone in fastboot mode and immediately, the phone reboot and makes a factory reset low level.
I think DC unlocker find system flaw that they alone know.
I do not know which version of android had the phone and which version of the security level but for this rom the security level of android is February 1, 2017 and the android version is 7.0 with EMUI 5.0.
Knowing that I could not bypass with 2018 methods found on youtube or xda, the phone downgraded to another version of android.
I think that their software finds a flaw for downgrade with the bootloader lock and that remove the frp protection
Thank you zgfg
Click to expand...
Click to collapse
Thank you for confirming and reporting your experience, it might be useful for somebody else (in that another thread I gave you link in the previous posts, it also worked for another user)
Btw, now when you opened FRP and Bootloader, did you upgrade to the relevant latest Nougat, or do you consider going for AL10 Oreo?
zgfg said:
Thank you for confirming and reporting your experience, it might be useful for somebody else (in that another thread I gave you link in the previous posts, it also worked for another user)
Btw, now when you opened FRP and Bootloader, did you upgrade to the relevant latest Nougat, or do you consider going for AL10 Oreo?
Click to expand...
Click to collapse
This is my second phone and I am looking to stay on a stable system and get used to EMIU. If i like EMIU, it will become my main smartphone.
I will make the OTA update that Huawei offers and stay on Nougat
Aymericl31 said:
This is my second phone and I am looking to stay on a stable system and get used to EMIU. If i like EMIU, it will become my main smartphone.
I will make the OTA update that Huawei offers and stay on Nougat
Click to expand...
Click to collapse
Ofc. I actually also like EMUI
Btw, EVA-AL10c00 b535/b539 is also EMUI
Stock firmware already contains international languages, just few patches are needed to get
Mob NW working
Playstore installed
and then can optionally come
Magisk root
Face unlock (n/a on Nougat)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Open Kirin Treble ROMs O and P (that can be installed over) are for those who want AOSP based experience
zgfg said:
Ofc. I actually also like EMUI
Btw, EVA-AL10c00 b535/b539 is also EMUI
Stock firmware already contains international languages, just few patches are needed to get
Mob NW working
Plaaystore
and then optionally
Magisk root
Face unlock (n/a on Nougat)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
Ok I'll watch this !
Thanks for all
On gurus Unlock you can found the solution instant and fast
The guide to unlocking the bootloader on the newer Samsung tablets seems to cause confunsion about what the OEM Enable switch does. First of all, the OEM switch has no direct bearing on the Bootloader lock. That switch has been around for quite a while but the Bootloader lock is a fairly new addition with a different purpose. Personally, I think OEM Enalble is mislabeled. I should read FRP Enalble. In the early days of Android, if your tablet was stolen, all the thief had to do to get around your lock screen, was to boot to recovery and perform a Factory Reset. To stop this, Google came up with the Factory Reset Prevention (FRP) lock. With that lock in place, if the tabet is Factory Reset, the thief would have to know the Google Account login and password in order to use the tablet.
The Bootloader lock serves an entirely different purpose. Google assumes that any software that they haven't vetted, poses a security risk. Not just for that tablet, but possibly others as well. (IMO, they also think it poses a risk to most users of bricking the tablet.) So they added the Bootloader lock to make installing custom ROMs more difficult. You can't use Odin to flash anything but stock ROMs so long as the bootloader is locked.
Now here is where the confusion comes in. The instruction say to enable Dev mode and OEM mode. You DO need Dev mode enabled in order to flash. But enabling OEM mode only means you don't have enter the Google info after flashing. And the instuctions say to skip adding a Google Account when you first reboot. And without a Google Account, there can be no FRP lock, so OEM Enable is now greyed out. IT ISN"T NEEDED!!!!!
What is FRP (click)
How to disable FRP (click)
*** you maybe need to click on the right side on the cross above the photo to see the content ***
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.
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