Related
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.
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.
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631
i have bough a x4 from ebay without warranty or anyting, the problem that i have. my phone says at the begining your device has loaded another operating system and then just a line of code says verity mode is set to disabled.
but after that the device starts normally, i have tried to lock the device again, but it doesn't work , maybe you have a solution for this problem :the model is XT1900-1 Type:M2997
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
cango123 said:
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
Click to expand...
Click to collapse
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
doksch84 said:
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
Click to expand...
Click to collapse
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
another problem
jhedfors said:
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
Click to expand...
Click to collapse
thank you guys, i just try to flash TWRP image, but it hangs with bootloader logs
getvar is-logical recove
getvar:has-slot:recovery
getvar_maxdown
Sending ....... in the command line? did anyone faces that problem ?
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