Related
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
Deear All,
I just bought my z2 force (t-mobile) from internet. It is an unlocked version and i can use it with my own sim card. However, i found that it cannot update via OTA as the bootloader is unlocked. I have heard that after i re-flash the firmware, the bootloader will be relocked. I am wondering, will the flashing re-activate the carrier lock?
Also, is it correct that after I flash via Lenovo Moto Smart Assistant. the bootloader will be locked again?
Is there other method to allow the phone to get OTA again?
Thanks a lot for your help.
hkguy80 said:
Deear All,
I just bought my z2 force (t-mobile) from internet. It is an unlocked version and i can use it with my own sim card. However, i found that it cannot update via OTA as the bootloader is unlocked. I have heard that after i re-flash the firmware, the bootloader will be relocked. I am wondering, will the flashing re-activate the carrier lock?
Also, is it correct that after I flash via Lenovo Moto Smart Assistant. the bootloader will be locked again?
Is there other method to allow the phone to get OTA again?
Thanks a lot for your help.
Click to expand...
Click to collapse
Unlocked bootloder won't stop an ota, but a custom logo.bin will. Chances are that the seller has also flashed a logo. When you boot you should see a warning about your bootloader being unlocked, if you don't and you just see a moto logo (or any stationary image really) then you have a custom logo which will fail otas. The easiest way to remedy this is to follow Uzephi's "How to Return to Stock' thread. Then you should get otas again. It is advised never to relock your bootloader. A good example of why would be that you have a custom logo, you relock, your phone fails to boot and you can't flash anything because you locked it. There is no real valid reason to relock your phone. As for losing carrier unlock, you shouldn't, those are usually permanent. Unless it was some hack which I doubt since I believe that is only for Spring variants. Just follow Uzephi's guide and you should be back to good.
41rw4lk said:
Unlocked bootloder won't stop an ota, but a custom logo.bin will. Chances are that the seller has also flashed a logo. When you boot you should see a warning about your bootloader being unlocked, if you don't and you just see a moto logo (or any stationary image really) then you have a custom logo which will fail otas. The easiest way to remedy this is to follow Uzephi's "How to Return to Stock' thread. Then you should get otas again. It is advised never to relock your bootloader. A good example of why would be that you have a custom logo, you relock, your phone fails to boot and you can't flash anything because you locked it. There is no real valid reason to relock your phone. As for losing carrier unlock, you shouldn't, those are usually permanent. Unless it was some hack which I doubt since I believe that is only for Spring variants. Just follow Uzephi's guide and you should be back to good.
Click to expand...
Click to collapse
Thanks a lot for your help. I will follow Uzephi's to reflash my phone. :good::good::good:
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
What software channel does it have listed in about phone settings?
Here
41rw4lk said:
What software channel does it have listed in about phone settings?
Click to expand...
Click to collapse
Its here
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
41rw4lk said:
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
Click to expand...
Click to collapse
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
crpcnt.cpc said:
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
Click to expand...
Click to collapse
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
41rw4lk said:
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
Click to expand...
Click to collapse
I logged into my google account, but it doesn't enable OEM unlock yet, so the mess was big on it.
crpcnt.cpc said:
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
Click to expand...
Click to collapse
I'm in the same situation, I've tried everything, I've had several people helping me, I have the same model and variant and I can't recover at all.
Success is disgusted by some people, and will not share any files for free in the future.
If relock, how about OTA uptdate?
dungnghien said:
If relock, how about OTA uptdate?
Click to expand...
Click to collapse
yes，you can！only support CN firmware，but WW firmware upgrades are not supported. The WW version of the firmware upgrade, you need to download the update package to the root directory, restart the phone to detect the update.
Will this process factory reset or no ???
zinou213 said:
Will this process factory reset or no ???
Click to expand...
Click to collapse
YES！
Damn! I should have waited for this. Too late. I used unlock tool. Now Asus has my unlock info.
One question. Can I relock if I originally unlocked using asus unlock apk tool???
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
BakaValen said:
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
Click to expand...
Click to collapse
There are no disadvantages, the only benefit is that you can unlock your phone through EDL mode, no need to install UnlockTool.apk to apply for unlock! The ASUS server will not get your unlocked status, you can get upgrades via OTA later.
Extreme184X said:
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
Click to expand...
Click to collapse
Oh sorry, I forgot to upload the driver for Qualcomm! You can download and install this tool on your computer, and then follow the steps to unlock it! Download link:https://drive.google.com/open?id=1PRw4jcg0zQKLQnMz7gApMZtCYex1PfJM
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
BakaValen said:
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
Click to expand...
Click to collapse
By unlocking this way, you can enjoy the warranty!
had anyone tried this method on previous unlocked device? did it will regain CN FOTA? thanks!
Hi, i tried but stuck on step 3, any way to solve? tried to change the usb port but same thing happened.
on step 3:.Double click to open “1.update_image_EDL.bat”,
it said: {ERROR: WritePort:5164 Could not write to '\\.\COM10', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times
@johnny886,
Hi, I installed the Qualcomm drivers but for step 3 "1.update_image_EDL.bat”, it still prompts and closes immediately and I'm not sure how to QPST or QFIL. Are there ways to fix the bat file or provide a more detaisl on using QPST or QFIL please?
You can root without unlock bootloader?
Deleted, misread, don't think it's relevant...
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
dennis96411 said:
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
Click to expand...
Click to collapse
Hey, can you please tell me where to get the stock boot image for 1910.44?
Edit: Okay nevermind got it.
Stuck on step 1.update_image_EDL.bat
Almost all of us are stuck on step 1.update_image_EDL.bat . The CMD window just shows and closes fast, and phone doesnt enter fastboot mode. I installed all drivers. Can you post guide on how to do that step using QPST or Miflash tools?
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
binary**# said:
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
Click to expand...
Click to collapse
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
binary**# said:
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
Click to expand...
Click to collapse
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
tys0n said:
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Click to expand...
Click to collapse
tys0n said:
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
Click to expand...
Click to collapse
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
binary**# said:
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
Click to expand...
Click to collapse
Oh I see. I don't know then.
You could ask here:
https://forums.lenovo.com/t5/motorola-one-action/bd-p/motorola_one_action_en
They should be able to give a proper answer.
I got a XT2013-4 US - Unlocked boot loader, but the root method doesn't work for the US Firmware (Hear the EU Firmware works for someone in Canada) but I am unable to check for updates being fully stock, unrooted, and only an unlocked bootloader so yes if the OS can read that the bootloader is unlocked then it won't let you check for updates (At least on the US Firmware) but then we aren't Android One though on the XT2013-4
If you are on Stock Firmware, unrooted but your Bootloader is Unlocked, you'll not get any OTA despite the Motorola Support page you've posted (It might be old information, just look the phone they used on the top).
Is it possible to relock it?
ReConfirmed: Official OTA Updates is possible after Unlocked Bootloader.
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
binary**# said:
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
Click to expand...
Click to collapse
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
No, my device isn't rooted. The only modification is the unlocked bootloader. I did this when I saw enrolled users getting beta Android 10 updates for Moto One Power. Since One Action has released almost a year after Power, I thought the soak test would just be around the corner for our device as well. But here we are with One Power receiving Stable Android 10 update, and there is no news of the same for our device. I have got myself enrolled in the MFN and just keeping my fingers crossed.
binary**# said:
No, my device isn't rooted. The only modification is the unlocked bootloader.
Click to expand...
Click to collapse
Ok, thanks. That's intresting.
tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
One more doubt. I tried the root hide via Magisk for some apps like Google Pay or Pokemon Go and it worked pretty well. But could it trick OEMs as well into thinking the device is unrooted, so that the device may receive OTA updates? I guess probably not, but need some more weight on this opinion.
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
aditya7286 said:
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
Click to expand...
Click to collapse
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
arsradu said:
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
Click to expand...
Click to collapse
binary**# said:
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Click to expand...
Click to collapse
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
methuselah said:
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
Click to expand...
Click to collapse
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
arsradu said:
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
Click to expand...
Click to collapse
The issue in brief.
Well the thing is i have again flashed back stock that with blankflash file. Before april update i had locked bootloader. But now nothing is happening. As soon as i flash stock ROM(clean stock) and relock the bootloader, the phone just says it is corrupted. But at the same time when i unlock the boot loader it boots.