Database Develop

[Q] Am I screwed? Warranty with Motowpnomo

So a loong time ago I diabled write protection using Motowpnomo, slap, and whatever else it took (cant remember, it was a long time ago).
From what I remember, disabling write protection using motowpnomo was irreversable. That still seems to be the case from what I read in the forums. But I am trying to see what my next steps can be with my issue. FYI - Verizon told me that they could tell that my phone was rooted just from talking over the phone??!?! Weird FYI I disabled write protection a long time ago and then my phone had an OTA a few months ago that I accidentally installed. After the OTA my phone still worked properly and SU still worked. But that is the state that my phone is in right now. I have a Verizon Moto X with a locked boot loader. I am on 4.4.2 build kxa20.16-1.25.2
So Saturday my GPS stopped working. I'm not sure if its an app conflict or something else. If Verizon gives me the option to send it in for warranty, is there anything I can do to get the phone back to stock (or close to it) or re-enable write protection?
Also, will my phone still work right or be soft bricked if I just factory reset my phone using the phone itself? I would like to see if I factory data reset if the GPS issue goes away.

Yes. Verizon can tell if you rooted. Yes this can void the warranty. There is a clause in there about altering from manufacturer specs, etc... which they can try to use against you. There was argument about this in another thread, so I'm not going to get into that.
IF the root method you used replaced factory recovery, then doing a factory reset via the phone's menus likely wont work as it would reboot into recovery to try and wipe the phone. But you can try using mfastboot to erase data and cache.
As for returning the phone under warranty option, that is another matter. You can download the 4.4.2 SBF and use RSDLite to flash it. That will remove the effects of MotoWpNoMo, SlapMyMoto, RockMyMoto, PwnMyMoto, etc. And get you to a fresh out of the box state. It could fix your problem too.

KidJoe said:
Yes. Verizon can tell if you rooted. Yes this can void the warranty. There is a clause in there about altering from manufacturer specs, etc... which they can try to use against you. There was argument about this in another thread, so I'm not going to get into that.
IF the root method you used replaced factory recovery, then doing a factory reset via the phone's menus likely wont work as it would reboot into recovery to try and wipe the phone. But you can try using mfastboot to erase data and cache.
As for returning the phone under warranty option, that is another matter. You can download the 4.4.2 SBF and use RSDLite to flash it. That will remove the effects of MotoWpNoMo, SlapMyMoto, RockMyMoto, PwnMyMoto, etc. And get you to a fresh out of the box state. It could fix your problem too.
Click to expand...
Click to collapse
Mark, my brother dropped his moto x and broke the glass. It was running 4.4 rooted locked bootloader verizon phone. If I run 4.4 sbf http://sbf.droid-developers.org/phone.php?device=0 from the link, using rsdlite will that remove any indication it was rooted so it might be covered by the warrenty. and if i get a new phone with 4.4.2 or newer preinstalled, would I be able to run rsdlite and 4.4 sbf to get root again?
thanks

doitinthedirt said:
Mark, my brother dropped his moto x and broke the glass. It was running 4.4 rooted locked bootloader verizon phone. If I run 4.4 sbf http://sbf.droid-developers.org/phone.php?device=0 from the link, using rsdlite will that remove any indication it was rooted so it might be covered by the warrenty. and if i get a new phone with 4.4.2 or newer preinstalled, would I be able to run rsdlite and 4.4 sbf to get root again?
thanks
Click to expand...
Click to collapse
I should have been a little clearer. While flashing the SBF with RSDLite or mFastboot would remove any trace from the phone itself, that might not address what Verizon has in their system.
If Verizon has already noted the account that your phone is rooted, they may not accept warranty claim even if you unroot. I don't know their full policy. I don't know when they "check" if your phone is rooted. Is it an on-going "automatic" thing, or just a "when you call for issue with the phone" type of thing.
As for downgrading from 4.4.2... There are many posts already warning that once 4.4.2 is on the phone, DO NOT attempt to downgrade. There are many reports of bricks or other issues from downgrading to 4.4 and below when you have 4.4.2 already on the phone. Enough bricks, potential bricks, and other flaky issues that it is advised to NOT DOWNGRADE once 4.4.2 is on your phone.

KidJoe said:
I should have been a little clearer. While flashing the SBF with RSDLite or mFastboot would remove any trace from the phone itself, that might not address what Verizon has in their system.
If Verizon has already noted the account that your phone is rooted, they may not accept warranty claim even if you unroot. I don't know their full policy. I don't know when they "check" if your phone is rooted. Is it an on-going "automatic" thing, or just a "when you call for issue with the phone" type of thing.
As for downgrading from 4.4.2... There are many posts already warning that once 4.4.2 is on the phone, DO NOT attempt to downgrade. There are many reports of bricks or other issues from downgrading to 4.4 and below when you have 4.4.2 already on the phone. Enough bricks, potential bricks, and other flaky issues that it is advised to NOT DOWNGRADE once 4.4.2 is on your phone.
Click to expand...
Click to collapse
Thank you for the thorough and fast response.

doitinthedirt said:
If I run 4.4 sbf http://sbf.droid-developers.org/phone.php?device=0 from the link, using rsdlite will that remove any indication it was rooted so it might be covered by the warrenty.
thanks
Click to expand...
Click to collapse
Once you are rooted, they can tell. The phone's bootloader has an indication of root state.
If you see “qe 0/0″ you are running a device that has never been rooted.
If you see “qe 0/1″ you are running a device that was at one time rooted, but currently is not.
If you see “qe 1/1″ like in the picture above, you are running a device that is currently rooted.

mandrsn1 said:
Once you are rooted, they can tell. The phone's bootloader has an indication of root state.
If you see “qe 0/0″ you are running a device that has never been rooted.
If you see “qe 0/1″ you are running a device that was at one time rooted, but currently is not.
If you see “qe 1/1″ like in the picture above, you are running a device that is currently rooted.
Click to expand...
Click to collapse
What picture?

mandrsn1 said:
Once you are rooted, they can tell. The phone's bootloader has an indication of root state.
If you see “qe 0/0″ you are running a device that has never been rooted.
If you see “qe 0/1″ you are running a device that was at one time rooted, but currently is not.
If you see “qe 1/1″ like in the picture above, you are running a device that is currently rooted.
Click to expand...
Click to collapse
Yeah, what picture?
and my X doesn't show QE... it shows "Device is Unlocked. Satus Code: 3" for my unlocked bootloader. A default LOCKED bootloader would say "Device is LOCKED. Status Code: 0" And I think RELOCKED is status code 2.
But it doesn't show root status.
Are you thinking of Samsung maybe?

KidJoe said:
Yeah, what picture?
and my X doesn't show QE... it shows "Device is Unlocked. Satus Code: 3" for my unlocked bootloader. A default LOCKED bootloader would say "Device is LOCKED. Status Code: 0" And I think RELOCKED is status code 2.
But it doesn't show root status.
Are you thinking of Samsung maybe?
Click to expand...
Click to collapse
Oops. I meant stock recovery.
It looks like this: http://www.droid-life.com/wp-content/uploads/2012/08/rootcheck1.jpg

mandrsn1 said:
Oops. I meant stock recovery.
It looks like this: http://www.droid-life.com/wp-content/uploads/2012/08/rootcheck1.jpg
Click to expand...
Click to collapse
Ok, after flashing stock recovery back on, yes I do see qe 1/1 on my rooted Dev X.

KidJoe said:
Ok, after flashing stock recovery back on, yes I do see qe 1/1 on my rooted Dev X.
Click to expand...
Click to collapse
Right. Now if you SBF back to stock, it will go to 0/1. You cannot clear the second 1.

mandrsn1 said:
Right. Now if you SBF back to stock, it will go to 0/1. You cannot clear the second 1.
Click to expand...
Click to collapse
Interesting.. read this thread -> https://forums.motorola.com/posts/78f197711d
There is a post stating that the QE value changed to 1/1 on phones with the KitKat Update, even if you haven't rooted.

KidJoe said:
Interesting.. read this thread -> https://forums.motorola.com/posts/78f197711d
There is a post stating that the QE value changed to 1/1 on phones with the KitKat Update, even if you haven't rooted.
Click to expand...
Click to collapse
Yes, I was under the impression that these QE values were determined to be unrelated to rooting, since completely stock users who received OTAs are suddenly showing 1/1
https://forums.motorola.com/posts/759ad51d8f
http://forum.xda-developers.com/showthread.php?t=2649483
(This rather irritated user insists "qe values don't mean JACK for root")...although I don't know how much trust I would put into that having read the conversation.

samwathegreat said:
Yes, I was under the impression that these QE values were determined to be unrelated to rooting, since completely stock users who received OTAs are suddenly showing 1/1
https://forums.motorola.com/posts/759ad51d8f
http://forum.xda-developers.com/showthread.php?t=2649483
(This rather irritated user insists "qe values don't mean JACK for root")...although I don't know how much trust I would put into that having read the conversation.
Click to expand...
Click to collapse
OK. so my phone came with 4.4 and i rooted via slapmymoto.. so if I do the factory restore if that's an option? and than just ship it back to moto for the warranty replacement... wonder if that will work out or not?

doitinthedirt said:
OK. so my phone came with 4.4 and i rooted via slapmymoto.. so if I do the factory restore if that's an option? and than just ship it back to moto for the warranty replacement... wonder if that will work out or not?
Click to expand...
Click to collapse
I suggest you flash the entire 4.4.2 SBF first. The instructions are in the "Return to Stock" thread. I suggest the manual method. Everything you need is in that thread, including links to the SBF Files themselves. Be sure to flash the appropriate SBF for YOUR carrier.
These instructions assume that you intend to return the phone and no longer care about being able to root it. Flashing the 4.4.2 SBF WILL render your device 'unrootable' except for the partial-root "PIE".
This is your safest bet.
Good Luck
Also, may I ask what the problem with the device is? SBFing back to stock can fix many issues - of course hardware failures are the obvious exception here. Just curious...

samwathegreat said:
I suggest you flash the entire 4.4.2 SBF first. The instructions are in the "Return to Stock" thread. I suggest the manual method. Everything you need is in that thread, including links to the SBF Files themselves. Be sure to flash the appropriate SBF for YOUR carrier.
These instructions assume that you intend to return the phone and no longer care about being able to root it. Flashing the 4.4.2 SBF WILL render your device 'unrootable' except for the partial-root "PIE".
This is your safest bet.
Good Luck
Also, may I ask what the problem with the device is? SBFing back to stock can fix many issues - of course hardware failures are the obvious exception here. Just curious...
Click to expand...
Click to collapse
Mine works very nice... I bought two though and gave one to my brother... he dropped it and screen broke, gonna see if moto will work with fixing it or swapping up to a de version, thanks for the help!

[Q] Moto X Device UNLOCKED Status Code 1

I did buy an moto x from eBay couple of weeks ago and it say Device UNLOCKED Status Code 1 in the Fastboot Mode ...I cannot make any sense of it since all of the Moto X have the status code 3,not 1. Also it has on extra option in Fastboot menu Switch console [NULL: null]. othe thing is when I run Command Fastboot erase all it erases allot of partition on the phone,and not just a few like in the rest of the Moto X ...The only problem that i have is that the IMEI is missing and it cannot be used to make any kind of phone calls Does anybody knows anything about this issue and explain to me what is the deal with it? Any help is much appreciated

DejanPet said:
I did buy an moto x from eBay couple of weeks ago and it say Device UNLOCKED Status Code 1 in the Fastboot Mode ...I cannot make any sense of it since all of the Moto X have the status code 3,not 1. Also it has on extra option in Fastboot menu Switch console [NULL: null]. othe thing is when I run Command Fastboot erase all it erases allot of partition on the phone,and not just a few like in the rest of the Moto X ...The only problem that i have is that the IMEI is missing and it cannot be used to make any kind of phone calls Does anybody knows anything about this issue and explain to me what is the deal with it? Any help is much appreciated
Click to expand...
Click to collapse
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831

KidJoe said:
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
Click to expand...
Click to collapse
A picture can say a million words.. Thanks a lot KidJoe for the reply

DejanPet said:
A picture can say a million words.. Thanks a lot KidJoe for the reply
Click to expand...
Click to collapse
Exactly what model do you have? What is stamped on the back of the phone in the FINE PRINT?
Based on those shots... 161.44.25 is XT1053 4.4.2. 30.B7 is 4.4.2 bootloader.
BUT as you can see, similar to those other threads, your phone reports...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
And your IMEI and SKU are all zeros...
I'm not sure how phones are getting into this state. And I don't have a fool proof way to fix them.

it is probably one of those "motorola confidential property" tagged phones used by company staff only, it may have been leaked into market, it often has unlocked bootloader like developer edition phones. it is a pre release phone with extra functions (that are not in mass production versions)

KidJoe said:
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
Click to expand...
Click to collapse
DejanPet said:
A picture can say a million words.. Thanks a lot KidJoe for the reply
Click to expand...
Click to collapse
KidJoe said:
Exactly what model do you have? What is stamped on the back of the phone in the FINE PRINT?
Based on those shots... 161.44.25 is XT1053 4.4.2. 30.B7 is 4.4.2 bootloader.
BUT as you can see, similar to those other threads, your phone reports...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
And your IMEI and SKU are all zeros...
I'm not sure how phones are getting into this state. And I don't have a fool proof way to fix them.
Click to expand...
Click to collapse
tahwer said:
it is probably one of those "motorola confidential property" tagged phones used by company staff only, it may have been leaked into market, it often has unlocked bootloader like developer edition phones. it is a pre release phone with extra functions (that are not in mass production versions)
Click to expand...
Click to collapse
hi dears
well, i've got the same issue (device is unlocked - status code 1)
it seems it has an unlocked bootloader, but for me, the unlocked bootloader warning has never appeared
i've even flashed twrp and cyanogenmod 12.1
my question is, (1) should i unlock it with the code and all that moto.com stuff?
one last question is, (2) why can't i just add supersu from twrp 2.8.7.0?
i turn it on at system, and i swipe to root, but the icon never appears on my apps drawer, is it related to the status code 1?
please help me...

For God sake! I have the same problem here. How can I root this phone? What code 1 means?

[Q][Solved] Relocking the bootloader

Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.

May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095

I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.

Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095

Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?

Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095

These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.

Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.

juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095

juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.

AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?

Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095

AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..

The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk

Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png

Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.

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.

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