Related
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
Also, what does it mean when in bootloader mode it says Device is UNLOCKED. Status Code: 3. What is the status code 3?
Cozume said:
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
I have a verizon unlocked dev ed. Also, what does it mean when in bootloader mode it says Devide is UNLOCKED. Status Code: 3. What is the status code 3?
Click to expand...
Click to collapse
It gives you the stock recovery, the stock system image with all the applications, and the ability to update over the air (OTA). People re-flash the factory images either when they think they messed up their phone, or when they want the latest update via OTA instead of waiting for a SBF package. In short, it returns the phone to the default/non modded status.
I am fairly certain that a SBF will be made for 4.4.2, it just is taking a bit longer this time, maybe they are busy, especially since there is no new updates around the corner any time soon. Since you have already updated to 4.4.2 (like myself) there is no way to go back to stock unless you have made a recovery image in TWRP/CWM. Then all you have to do to update, is reflash the stock recovery image and then you can take a system OTA.
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
mastarifla said:
In short, it returns the phone to the default/non modded status.
Click to expand...
Click to collapse
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
mastarifla said:
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Click to expand...
Click to collapse
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
mastarifla said:
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
Click to expand...
Click to collapse
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Cozume said:
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
Click to expand...
Click to collapse
If you are already on 4.4.2 then you can flash the 4.4.2 "factory image" when it is released and it should be fine/back to normal.
Cozume said:
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
Click to expand...
Click to collapse
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Cozume said:
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Click to expand...
Click to collapse
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
mastarifla said:
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Click to expand...
Click to collapse
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
mastarifla said:
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
Click to expand...
Click to collapse
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Cozume said:
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
Click to expand...
Click to collapse
Sadly corporate security is much less of a concern to them and actually something else entirely (see Samsung's encryption protocol for enterprise - SAFE). Motorola doesn't want to bother with supporting people on lower firmwares, and this prevents them from having to worry about it because they will always require you to be on the latest firmware for support, this eFuse system basically prevents people from using exploits in previous versions of the system (aka getting root on a non-unlocked phone, etc).
Cozume said:
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Click to expand...
Click to collapse
If you have your EFS files backed up then you are okay, you can just restore it and you are good to go again. However, the IMEI is a secure file, so you cant make a new one if its gone (nor can your cell company), this system in effect prevents people stealing phones and changing the IMEI in order to not be blacklisted. This system is in place for a very good reason, while not perfect (try selling a used phone to someone who understands this), its the best deterrent against theft currently available.
mastarifla said:
If you have your ESF files backed up then you are okay, you can just restore it and you are good to go again.
Click to expand...
Click to collapse
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Cozume said:
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Click to expand...
Click to collapse
There are tools available to backup your EFS partition in case a nandroid doesn't work correctly. Some CWM/TWRP versions do EFS partition backups, some don't, be sure to read through the threads and make sure. Asking a question goes a long way.
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
rootSU said:
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
Click to expand...
Click to collapse
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It depends what you're expecting in future. If you want OTA, you'll need everything to be 100% stock and the right version. If you don't care about that, minimum is system.img and boot.img.
i tried to downgrade my bootloader through fastboot from 5.1's bootloader to 5.0.1 and fastboot throws an error from moto saying it cant be downgraded.
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
freebee269 said:
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
Click to expand...
Click to collapse
I had been running Chroma 5.02 with the 5.1 bl and radio. I reverted the radio because of issues with TMo, but the bl seemed fine. FWIW, I made all my changes via fastboot.
kenbrownstone said:
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It resets on boot. Check it boots before relocking
rootSU said:
It resets on boot. Check it boots before relocking
Click to expand...
Click to collapse
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
naresh2990 said:
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
Click to expand...
Click to collapse
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
naresh2990 said:
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
Click to expand...
Click to collapse
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
pwned3 said:
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Konfuzion said:
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
rootSU said:
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
Click to expand...
Click to collapse
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
the_rooter said:
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
Click to expand...
Click to collapse
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
the_rooter said:
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
Click to expand...
Click to collapse
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said after a reboot it goes unchecked so if i check it and then reboot to recovery wouldnt that uncheck it again?
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.
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
darkprime said:
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
Click to expand...
Click to collapse
You wont be able to flash anything if your bootloader is locked...its an xt1095 unlock the bootloader. There are many posts on how to do this for the xt1095 you basically get a code from moto that you apply through adb fastboot. After you unlock bootloader you can flash stuff BUT NEVER EVER EVER EVER EVER try and downgrade the gpt or bootloader EVER. Just the system and boot images.
just to be sure you got it NEVER TRY TO DOWNGRADE THE BOOTLOADER OR GPT .
adm1jtg said:
You wont be able to flash anything if your bootloader is locked...its an xt1095 unlock the bootloader. There are many posts on how to do this for the xt1095 you basically get a code from moto that you apply through adb fastboot. After you unlock bootloader you can flash stuff BUT NEVER EVER EVER EVER EVER try and downgrade the gpt or bootloader EVER. Just the system and boot images.
just to be sure you got it NEVER TRY TO DOWNGRADE THE BOOTLOADER OR GPT .
Click to expand...
Click to collapse
I thought the system image is supposed to be flashable even when not locked. Motorola's instructions for returning something to stock has the bootloader and partition flashed - what's the point in doing that if you can't downgrade it?
Anyways, I have tried to unlock it, but since it is running android 5.1, it requires me to set the OEM Unlock option in Android Developer's Settings. Unfortunately, when the phone boots up, I cannot get into any settings without entering the google account information that was used to protect the phone in the first place. So I'm stuck - 5.1 won't let me get far enough to set the setting to unlock so I can't unlock bootloader to revert back to an earlier system version.
darkprime said:
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
Click to expand...
Click to collapse
Try flashing the 5.1 images. I don't know if that will work but it seems like it might since you're not technically downgrading which would require an unlocked bootloader. Just follow all the commands on Motorola's website.
Sent from my XT1095 using Tapatalk
There is nothing you can do. This is an anti-theft protection. You need to contact the seller and have him login to the account... then after that, the account can be removed. If the seller does not help you, then sorry to say but you have a paperweight because there is absolutely no way around this.
Sent from my XT1095 using Tapatalk
AGISCI said:
There is nothing you can do. This is an anti-theft protection. You need to contact the seller and have him login to the account... then after that, the account can be removed. If the seller does not help you, then sorry to say but you have a paperweight because there is absolutely no way around this.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Not quite...I got motorola to accept it under warranty to replace it. The IEMI says the phone was bought in Feb. 2015, so it still has a chunk of warranty left on it.
That surprises me... so if I steal a motorola phone that still has warranty they will send me a replacement that is unlocked just because it is under warranty? Seems like that is a huge problem.
Sent from my XT1095 using Tapatalk
AGISCI said:
That surprises me... so if I steal a motorola phone that still has warranty they will send me a replacement that is unlocked just because it is under warranty? Seems like that is a huge problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Is that really a huge problem? They will know who claimed the warranty and I'm sure can notice if anyone is abusing that. Not perfect, but not terrible either. Besides, when the phone is turned in for a warranty, how does Moto know that the reason it's locked out is not due to my own google account?
Supposedly the warranty is only with proof of purchase, which you don't have since you bought it from someone else on ebay. That is a big issue because that undermines the whole reason for having this option on the phone.
Sent from my XT1095 using Tapatalk
AGISCI said:
Supposedly the warranty is only with proof of purchase, which you don't have since you bought it from someone else on ebay. That is a big issue because that undermines the whole reason for having this option on the phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The person on ebay ran a storefront and I have a receipt from it - I did buy it. The warranty doesn't say you can't buy it from a 3rd party, nor does it say you have to to be the first end-user.
darkprime said:
The person on ebay ran a storefront and I have a receipt from it - I did buy it. The warranty doesn't say you can't buy it from a 3rd party, nor does it say you have to to be the first end-user.
Click to expand...
Click to collapse
Mototola's warranty:
https://www.google.com/url?q=https:...6FUuSQ&usg=AFQjCNEGjgEU48cZkqSs2Y72u8W2SgI-mw
The very first thing it says is that it is for the first owner only and is non transferrable.
Sent from my XT1095 using Tapatalk
AGISCI said:
Mototola's warranty:
https://www.google.com/url?q=https:...6FUuSQ&usg=AFQjCNEGjgEU48cZkqSs2Y72u8W2SgI-mw
The very first thing it says is that it is for the first owner only and is non transferrable.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok, I stand corrected, but Moto doesn't know if I was the first end user or not. I'm sure I wasn't, but good businesses will honor warranties even when technically against the agreement, terms, or expiration.
Anyways, back on topic - if someone knows of something else I can try while I still have the phone, I would like to hear it.
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