Database Develop

Relock Droid Turbo Bootloader

What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.

mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.

According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.

Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk

SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.

TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?

You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571

Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse

droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.

Guide SIM UNLOCK T-MOBILE version all type of IMEI supported

I was trying to sim unlock bad IMEI (financed) all services refused to unlock I managed to sim unlock very easy
1 you need to convert to international version follow this thread By AnonymousTipster ( great thanks ) (https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 )
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
thats all
you can also backup modemst1 and modemst2 files before this steps
you won't loose imei or have some problem phone works without any problem just tested

Congrats bro
Alright bro, I thought this was an early April fool's joke at first but it's apparently not. Congrats n sorry for the early doubts... I had just read your posts about trying a sim unlock thru some company and it being successful but the tmo app wasn't working so I figured that's where your sim got unlocked it had just carried over to the international version but apparently not. It's crazy that this is how easy it is to bootloader unlock & unlock your sim. Definitely backup your modemst with readback mode in msm

I can help you do what you need as I've done it before. pm me.

gigilie said:
No guide ends with the user deleting their modem. I mean come on man dont mess with people. You've been all over the forum last few days with a stolen phone with a bad imei trying to get it unlocked. U just said blowfish finally came thru n u got it unlocked. How r u gonna claim someone elses work tell everyone it does something it really doesn't do (which is sim unlock the device!) And then have them delete their modems and ask for a donation.... Too funny April fool's ISN'T for a week dude.
Click to expand...
Click to collapse
1 phone is not stolen its financed ordered from ebay as unlocked I was scammed was not able to return from oversies
2 you can backup your modems and then try deleting with this commands they are not deleting I tryed 2 times
3 after blowfish confirmed that phone was unlocked opened unlock app > permanent unlock was receiving same error delleted app data same error factory reset - same error reflashed firmware same error after that this commands worked

all unlock services included blowfish unlock cellunlocker few one from ebay . tyed many of them they refunded money (blowfish returned credits to account) main reason wan device was not active 40 days this services can unlock bad imei phones but if device was not active 40 days they can't more than month I was trying to unlock but only this commands worked if you think you will loose modems to backup try this method
Download & Open up Terminal Emulator on your phone
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
Code:
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048

Deleted doubting post #2 lol

gigilie said:
Bro ur funny we use magisk n we don't dd modems thru terminal to back anything up.... Tell me technically what sense would it make to delete your modem how would that unlock your sim? See if u really did unlock ur sim n bootloader for free by flashing to international and then deleting ur modems (lol) then you would have put twrp on and actually rooted upgraded to beta 7 or flashed an aosp (at least that's what I'd assume cause that's what we unlock the bootloader for) so post some screenshots of whatever ROM ur on or a video of the process with u proving ur not lying. Cause as far as I know absolutely no information regarding the devices unlocked sim state reside in the modem. Imei in Efs maybe or on the board in the phone but not on a piece of a stock rom that some of the best developers on here just overlooked but u magically figured it out.... Quit it dude go home
Click to expand...
Click to collapse
Yes bro I was very funny looking when this worked Im using non T-Mobile sim my number is not covered txt me for for instructions One guy from my country have same phone tmo locked I will take video for you

Hi, I believe you, and I want to try this method... but where are the source of your information? How did you know puting those comands will work?
Thank you!!!

robbie1104 said:
Hi, I believe you, and I want to try this method... but where are the source of your information? How did you know puting those comands will work?
Thank you!!!
Click to expand...
Click to collapse
40+ days I was trying everything Don't know how this phone survived

nika_bego said:
40+ days I was trying everything Don't know how this phone survived
Click to expand...
Click to collapse
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??

robbie1104 said:
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
Click to expand...
Click to collapse
I didn't backup modems copied this first found instructions for annoying users ?

robbie1104 said:
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
Click to expand...
Click to collapse
Before phone turned on I was searching modem files I was ready that phone doesn't turns on. But everything was good i don't lost my imei and phone is sim unlocked

nika_bego said:
Before phone turned on I was searching modem files I was ready that phone doesn't turns on. But everything was good i don't lost my imei and phone is sim unlocked
Click to expand...
Click to collapse
Some people I know discovered this work around in November if u make a modemst back up of both modems first, use msm readback to backup imei, then wipe modem, then sim unlocked, restore modem files and imei with msm readback mode. It's just very risky. So if u know how to use msm readback mode and smt mode then go for this, @nika_bego you are correct. For the haters, grow up man, u are incorrect, this man is correct. There are multiple ways to do things in android. I was part of the initial team that first achieved root with this phone with a locked bootloader via aging kernel. Which then led to wiping the modems..we had to keep it between ourselves or chaos would erupt on xda. Plus the mods get so upset if u talk about hacks, modded apps, imei anything and restoring stuff.
Thanks, good job man

fullofhell said:
Some people I know discovered this work around in November if u make a modemst back up of both modems first, use msm readback to backup imei, then wipe modem, then sim unlocked, restore modem files and imei with msm readback mode. It's just very risky. So if u know how to use msm readback mode and smt mode then go for this, @nika_bego you are correct. For the haters, grow up man, u are incorrect, this man is correct. There are multiple ways to do things in android. I was part of the initial team that first achieved root with this phone with a locked bootloader via aging kernel. Which then led to wiping the modems..we had to keep it between ourselves or chaos would erupt on xda. Plus the mods get so upset if u talk about hacks, modded apps, imei anything and restoring stuff.
Thanks, good job man
Click to expand...
Click to collapse
:good:
thanks

gigilie said:
No guide ends with the user deleting their modem. I mean come on man dont mess with people. You've been all over the forum last few days with a stolen phone with a bad imei trying to get it unlocked. U just said blowfish finally came thru n u got it unlocked. How r u gonna claim someone elses work tell everyone it does something it really doesn't do (which is sim unlock the device!) And then have them delete their modems and ask for a donation.... Too funny April fool's ISN'T for a week dude.
Click to expand...
Click to collapse
Modemst1 and 2 is settings, not modem.

fullofhell said:
Some people I know discovered this work around in November if u make a modemst back up of both modems first, use msm readback to backup imei, then wipe modem, then sim unlocked, restore modem files and imei with msm readback mode. It's just very risky. So if u know how to use msm readback mode and smt mode then go for this, @nika_bego you are correct. For the haters, grow up man, u are incorrect, this man is correct. There are multiple ways to do things in android. I was part of the initial team that first achieved root with this phone with a locked bootloader via aging kernel. Which then led to wiping the modems..we had to keep it between ourselves or chaos would erupt on xda. Plus the mods get so upset if u talk about hacks, modded apps, imei anything and restoring stuff.
Thanks, good job man
Click to expand...
Click to collapse
can confirm same.

robbie1104 said:
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
Click to expand...
Click to collapse
I don't believe this guy either. However it is actually true that converting the TMO variant to the International using this: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 will allow a simple
Code:
fastboot oem unlock
instead of having to go through OnePlus/TMO to get unlock.bin file.
Doing the conversion, then unlocking the bootloader, then rooting as normal. However I do not for one second believe that erasing the modem will unlock the SIM.
Edit: Looks like it might be possible to SIM unlock with this HOWEVER it requires MORE STEPS not only what is listed in the OP.
OP - Can you please update your post with a full, detailed list, of what to do?

nika_bego said:
I was trying to sim unlock bad IMEI (financed) all services refused to unlock I managed to sim unlock very easy
1 you need to convert to international version follow this thread By AnonymousTipster ( great thanks ) (https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 )
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
thats all
you can also backup modemst1 and modemst2 files before this steps
you won't loose imei or have some problem phone works without any problem just tested
Click to expand...
Click to collapse
It is really necessary to unlock bootloader first?? I flashed 9.0.12 and OEM unlock under Developer settings is grayed and disabled... Do i have to flash 9.0.11 to unlock OEM?? In what version of OxygenOS did you make this procedure??
Thank you!!!

robbie1104 said:
It is really necessary to unlock bootloader first?? I flashed 9.0.12 and OEM unlock under Developer settings is grayed and disabled... Do i have to flash 9.0.11 to unlock OEM?? In what version of OxygenOS did you make this procedure??
Thank you!!!
Click to expand...
Click to collapse
I flashed 9.0.11 done this steps and then locked bootloader after updated to 9.0.12

sandix said:
I don't believe this guy either. However it is actually true that converting the TMO variant to the International using this: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 will allow a simple instead of having to go through OnePlus/TMO to get unlock.bin file.
Doing the conversion, then unlocking the bootloader, then rooting as normal. However I do not for one second believe that erasing the modem will unlock the SIM.
Edit: Looks like it might be possible to SIM unlock with this HOWEVER it requires MORE STEPS not only what is listed in the OP.
OP - Can you please update your post with a full, detailed list, of what to do?
Click to expand...
Click to collapse
U gotta use readback mode on msm to back it up first. Then wipe smt wipe it then use it to restore the modemst. A and b and then u have to restore imei. A quick Google search will help u with that

I've found easy way to unlock TMobile bootloader's for the oneplus 7 pro in 15 min

If anybody wants to no how I did it let me no I can spread the love takes bout 20 min of ur time
Okay so this is what u do is go download msm tool and follow his guide after that ,u go here https://forums.oneplus.com/threads/android-q-developer-preview-3-for-oneplus-7-pro-and-7.1076548/. And download lastest beta do the local upgrade and it will boot u into the new beta ROM which u will have no data don't freakout just go to settings tap build number 7 times or what not then go to developer options scroll down u will see oem uUnlocking and u can click on it to enable it then go to fastboot and unlock bootloader then u go back to the first link and download full rollback package and flash it in local upgrade to ,when it gets done ur bootloader will still be unlocked so down load twrp installer and the img , fastboot the twrp img then reboot it brings you back to twrp flash magisk n boom u got root on T-Mobile with unlocked bootloader you very welcome

How about sharing it here, unless its illegal?

Yes, a new method is known. It’ll be posted here later today. That’s the current plan, anyway. Hopefully someone doesn’t post it first; I have a way to make the method better (permanent, can relock bootloader and unlock again without redoing the method).
Just doing stuff this weekend, haven’t had time. Will have time tonight though.

Please share!

Hijacking this thread to say we (XDA Portal) have also discovered a way, which is what DTop is referring to. If any T-Mobile OP7 Pro user wants to try it, DM me.

Wish we could find faster ways to Sim unlock lol

Ok, doing this currently with wife's phone as avoiding the 7 day wait with Oneplus is ideal. Just got her device sim unlocked today so its a win overall now.
Go here - https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947 grab the two mega links using decryption codes found in second post. this will convert you to international firmware and you can follow the OP's guide.
Edit: can confirm that DP3 let me bootloader unlock without a unlock token. Thank you to @fowler82

It's been updated to 13x4 I've managed to get 13x3 through the oxygen updater app.

There was a method to unlock network on tmobile op 6t. I ve tried to do same on 7 pro. But getting fastboot error saying “flashing is not allowed for critical partition”. Anyone can help?
This method:
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Отправлено с моего iPhone используя Tapatalk

akyl001 said:
There was a method to unlock network on tmobile op 6t. I ve tried to do same on 7 pro. But getting fastboot error saying “flashing is not allowed for critical partition”. Anyone can help?
This method:
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Отправлено с моего iPhone используя Tapatalk
Click to expand...
Click to collapse
I am not a fastboot expert, but I strongly suspect running those commands will just erase your modem firmware and leave you with a non-working modem = no network connection

Jaco2k said:
I am not a fastboot expert, but I strongly suspect running those commands will just erase your modem firmware and leave you with a non-working modem = no network connection
Click to expand...
Click to collapse
On oneplus 6t, there was no problem. You re getting fully unlocked phone on both sim trays.

any news about whith that

I am pretty sure I lost the ability to use mobile sim one way or another I think after I deleted these and then like a dummy clicked in settings sim lock password or whatever it is called that locked me out and I needed to get my oil code from the carrier

Jaco2k said:
I am not a fastboot expert, but I strongly suspect running those commands will just erase your modem firmware and leave you with a non-working modem = no network connection
Click to expand...
Click to collapse
Partitions that are not marked _a or _b are never updated through any system update
In other words whatever that command does is unrecoverable and historically this command was used to erase IMEI

Hello everyone before anything I hope everyone is ok and safe in this difficult time.
Now I ask. Does this still work? My TMobile oneplus 7 pro is on the official international 10.3.2GM.21AA. if it still work is it safe to downgrade directly to the DP3 to do this?

gunfan said:
Hello everyone before anything I hope everyone is ok and safe in this difficult time.
Now I ask. Does this still work? My TMobile oneplus 7 pro is on the official international 10.3.2GM.21AA. if it still work is it safe to downgrade directly to the DP3 to do this?
Click to expand...
Click to collapse
Follow these instructions. It still works.
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/

dirty2k9 said:
Follow these instructions. It still works.
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/
Click to expand...
Click to collapse
Thank. Will try it.

It worked fast and easy on my first try. I'm on 10.3.1.GM21AA with an unlock bootloader. Now let's see if I can muster the courage to install twrp magisk and a rom.
Things have change so much since cyanogen. I'm so afraid to brick. Anyways thanks for the help.

i just poasted a moded msm i made that all you need to do is flash it then enter fastboot command

Pixel 5 Android 12 Developer Preview 3 OTA Sideload failed at 94% and now it says "Can't find valid operating system. The device will not start."

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.

Question Help, i did something stupid.

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