Related
[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
How about looking around a little bit. Come on man
uncalex said:
[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
Click to expand...
Click to collapse
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
eksasol said:
For rooting the Moto X it is a bit difficult compared to the Nexus. You need to realize that the Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently (hardware) brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. When I had the Moto X 2013 version, it is possible to brick the phone by downgrading the phone to an older version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update patch for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone image you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory image of the phone.
Click to expand...
Click to collapse
Thank you for being so nice and providing this information
eksasol said:
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
Click to expand...
Click to collapse
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
uncalex said:
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
Click to expand...
Click to collapse
I never use that. The safest thing is to do what is tested and available for that device, so use the current available method here:
http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
Generally. I don't do any of these, because I do the default Nexus root method which is:
1. Unlocking bootloader
2. Flash TWRP recovery: fastboot flash recovery twrp.img (not yet available for this phone, but soon will be, check the development sections.)
3. Then copy the Chainfire's SuperSU.zip (link in my signature) into the phone and flash while in TWRP recovery.
You shouldn't worry about bricking the device provided if you don't mess around, just stick with rooting and flashing factory firmware if you are new. As long as you don't flash a rom / firmware made for a different phone, or mess with the CID partition or something like that. Or downgrading the firmware after you've already update, which should be fine with a Nexus, but it did kill some Moto X when they downgraded to a firmware that is too old.
If you ever run into issues, you can flash the factory firmware, which is not available yet, but will eventually show up here: http://sbf.droid-developers.org/phone.php?device=37
You will have to download the correct version since there are different variations, but flashing incorrect ones should not brick your device. You can use these instruction to flash the firmware, this is for the Moto G, but the steps are the same: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657. After you install stock firmware, depend on if you were having issues, you can access the phone's Recovery and do a factory reset, this will wipe all your data, but also clear all the settings which may be required for the phone to boot correctly.
Normally, if your phone is rooted, when you received an over the air update, the first thing I would do before applying that update is to flash the system.img and recovery.img partition of the device back to stock, this will ensure the OTA gets updated successfully, afterward you can re-root the phone. Some people avoid this and flash the OTA's zip file using TWRP recovery, but it is not the official way and not guarantee to work all the time.
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.
I wanted to share my experience with working with a T-MO G4 (H81120i) that I had rooted, unlocked the bootloader, and had a custom ROM. My goal was to return it to stock so that I can turn it in(to jump). I tried:
The 2014 LG Flash tool. It failed out multiple times with a "Cannot connect to server" error.
LG Bridge tool which failed multiple times too. The device was not recognized.
LGUP which was reccommended by someone. I have no idea how you would flash or restore wit hthat tool. So, that was a dead end.
So, what worked?
I downloaded the flashable complete zip for the stock t-mo G4(20i) and then left it at that. Its still showing bootloader unlocked on startup so I asm wondering about setting going into fastboot and OEM locking or relocking. The question is...is this last step necessary?
gpmartinson said:
I wanted to share my experience with working with a T-MO G4 (H81120i) that I had rooted, unlocked the bootloader, and had a custom ROM. My goal was to return it to stock so that I can turn it in(to jump). I tried:
The 2014 LG Flash tool. It failed out multiple times with a "Cannot connect to server" error.
LG Bridge tool which failed multiple times too. The device was not recognized.
LGUP which was reccommended by someone. I have no idea how you would flash or restore wit hthat tool. So, that was a dead end.
So, what worked?
I downloaded the flashable complete zip for the stock t-mo G4(20i) and then left it at that. Its still showing bootloader unlocked on startup so I asm wondering about setting going into fastboot and OEM locking or relocking. The question is...is this last step necessary?
Click to expand...
Click to collapse
its only if you want to send to LG... so they wont noticed it was bootloader unlocked.... if you relock it will you .. take a video of it...
someone claim it can be relocked... mines locked... so if it can be relocked then i would unlock it..
but it will be nice to see a video that it can be done...
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
Hey guys, I have an lm-v405ua unlocked from at&t. Software version is 30e but I am hoping to install TWRP and lineage OS.
What root methods will work for this configuration? Also, without a pc, how do I ensure an unlocked bootloader?
Thanks in advance.
I dont now open .
I need my chave u now after am going... maybe
I dont now open .
I need my chave u now after am going... maybe
Bill W 466 said:
Hey guys, I have an lm-v405ua unlocked from at&t. Software version is 30e but I am hoping to install TWRP and lineage OS.
What root methods will work for this configuration? Also, without a pc, how do I ensure an unlocked bootloader?
Thanks in advance.
Click to expand...
Click to collapse
I don't think there's any way to replace the basic 'fastboot oem unlock' command. Which is done with a pc (with fastboot / adb installed) connected to the device (and it's in fastboot mode, which for the v40 requires a pc with qfil to flash the v35 eng abl).
That I think is the roadblock for doing any of the other things, without an unlocked bootloader... then it's full stop. Can't go farther.
AsItLies said:
I don't think there's any way to replace the basic 'fastboot oem unlock' command. Which is done with a pc (with fastboot / adb installed) connected to the device (and it's in fastboot mode, which for the v40 requires a pc with qfil to flash the v35 eng abl).
That I think is the roadblock for doing any of the other things, without an unlocked bootloader... then it's full stop. Can't go farther.
Click to expand...
Click to collapse
I apologize for my duplicate posts. Can you direct me to a thread with detailed instructions for flashing the necessary v35 image. I should have a new laptop coming in a few days.
I am not a total noob as I've used fastboot, adb, and in fact lgup (had a v20 a while back.) it's been a couple of years since I've done any of this as I've been away for a bit.
Thanks again...
Bill W 466 said:
I apologize for my duplicate posts. Can you direct me to a thread with detailed instructions for flashing the necessary v35 image. I should have a new laptop coming in a few days.
I am not a total noob as I've used fastboot, adb, and in fact lgup (had a v20 a while back.) it's been a couple of years since I've done any of this as I've been away for a bit.
Thanks again...
Click to expand...
Click to collapse
Yes, this is the thread to follow to unlock the BL. Most of that is up to date, except maybe the part about getting twrp, but I can help with that when u get to that point.
Some important info you may or may not know, with prior experience: Some carriers make thier kdz available, some don't. So the ones that don't, it means it's imperative you make a backup of any partition first, before changing it (because if u don't, and u mess up, you'll have no way to 'get back').
Also, if you decide to do 'cross-flashing' be sure to backup the specific partitions that contain your imei and s/n, as those can get messed up in the process and without the backups the missing imei may be unable to make a call.
You might also notify a Moderator (see mod list in ea thread) and ask them to del the threads you started in Guides and Roms, because unfortunately, when new people see one person do it, then they do it also, then it just turns into a hella mess.
cheers
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