I purchase a 1+3 a week ago. I have everything setup has i wanne but my concern if the phone goes into bootloop or something goes wrong. Would u think im ok woth a locm bootloader or unlock bootloader is a must
Unlocking bootloader is only necessary if you want/need root and other modifications. If you're satisfied with the phone in its current state and only plan to use official ROMs, you don't need to unlock it.
Bootloops an similar issues are very rare on unmodified devices, no need to worry about this.
Besides, you can always factory reset or sideload stock ROM even with locked bootloader and stock recovery.
Sent from my OnePlus 3 using Tapatalk
Hi,
I have question so my phone has an unlocked bootloader and is rooted, recently I got the notification for the pie update to Android 9. My question now can I still update without problems or should I unroot and lock my bootloader again?
Do not ever relock your bootloader. Unless you were planning on selling it.
So the update will be no problem? But won't it be noticed in the update process and cause problems?
jizang said:
So the update will be no problem? But won't it be noticed in the update process and cause problems?
Click to expand...
Click to collapse
The bootloader being unlocked had nothing to do with updating. But root might , I'm not sure I don't take OTA updates. Magisk Is a systemless root so it may work fine , I haven't ever tried.
The unlocked bootloader is fine. Worst case scenario you lose your root and have to reroot your phone, which is easy to do. I upgraded from 8 to 9 without issue with an unlocked bootloader, all I had to do was reroot the phone
Hi,
Long story short:
is it possible to install customROM without root and to (re)lock the bootloader, and are there experiences with a similar situation where Apps check for closed bootloader and root (and stop working if detected)?
=> Goal: activate WiFi-Calling as my provider tuned down 2G-transmitpower due to the 5G-advances (without having enough 3G-coverage to make calls on UMTS-net)... BUT: I'm using two banks; one uses a PhotoTAN-App, that stops working if it detects an open Bootloader, the other Bank-App checks for Root & open Bootloader, and likewise stops working if detected. I have no idea about the PhotoTAN and Magisk, but the 2nd bank confirmed they checked rooted devices with Magisk, and that it does not work with it....
Thus, if I go for a CustomROM, I need to be sure that I can run it unrooted and with a locked bootloader....
Is there a way to install a CustomROM on the 5X with (re)locked bootloader and without root?
(or, if not possible: is there a way I can activate WiFi-Calling on StockROM if said one does not have the Carrier-Entitlements?)
Thanks for the help
@theunlucky: you don't need root to flash a custom ROM, only an unlocked bootloader. IMO you can lock it after flashing ROM.
rp158 said:
@theunlucky: you don't need root to flash a custom ROM, only an unlocked bootloader. IMO you can lock it after flashing ROM.
Click to expand...
Click to collapse
Are you sure about locking the bootloader after flashing a CustomROM? I've read several threads now, and it seems a locked BL only works with StockROM?
Not sure, therefore IMO IMO a locked BL prevents flashing CustomROM, not running. Try. If it doesn't work, you unlock BL again (triggers factory reset). In the worst case you've to flash latest firmware for a clean base..
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.
Would there be a way to do one-click-root on the Motorola Moto G5 (XT1672) or another way that is easy and does not do a factory reset? Thanks!
vanhead said:
Would there be a way to do one-click-root on the Motorola Moto G5 (XT1672) or another way that is easy and does not do a factory reset? Thanks!
Click to expand...
Click to collapse
I really don't know how this is going from root very well, but as I understand it, you need to unlock the bootloader of the device (which requires a factory reset). If you already have the bootloader unlocked, try KingRoot, The truth is the only root of a click that I know, I have not really tried it on this device, but on an old phone, and it worked fine. The only problem I have had and I do not know if it is the fault of the device or KingRoot, and is that when I try to uninstall an application which I gave it the root permissions, the phone restarts, to uninstall an application I had to deny it permissions and then I could uninstall it, I repeat, I do not know if it is a problem that only happens to me
Postdata: Sorry for my english
vanhead said:
Would there be a way to do one-click-root on the Motorola Moto G5 (XT1672) or another way that is easy and does not do a factory reset? Thanks!
Click to expand...
Click to collapse
Rooting the phone does not require a factory reset but unlocking the bootloader does
So if you haven't unlocked the bootloader you will have to factory reset it during the process
If the bootloader is already unlocked you do not need to factory reset your device again in order to root it
Magisk should be the only way you should root your device - do not use other methods like kingroot as this has bloat and is not systemless (meaning it alters the system partition)
You need to root with magisk in order to maintain the system partition in its original state in order to pass basic integrity & to be able to pass cts profile (may need a magisk module) and to hide the fact you are rooted from apps that will not work if your device is rooted
TheFixItMan said:
Rooting the phone does not require a factory reset but unlocking the bootloader does
So if you haven't unlocked the bootloader you will have to factory reset it during the process
If the bootloader is already unlocked you do not need to factory reset your device again in order to root it
Magisk should be the only way you should root your device - do not use other methods like kingroot as this has bloat and is not systemless (meaning it alters the system partition)
You need to root with magisk in order to maintain the system partition in its original state in order to pass basic integrity & to be able to pass cts profile (may need a magisk module) and to hide the fact you are rooted from apps that will not work if your device is rooted
Click to expand...
Click to collapse
Thank you for your help. I tried several One-click-root, none worked, so I researched, they only work on android 7.
Could you tell me if it is possible to Downgrade from Android 8.1 to 7 without unlocking the bootloader? All the videos I find, the bootloaders are already unlocked.
vanhead said:
Thank you for your help. I tried several One-click-root, none worked, so I researched, they only work on android 7.
Could you tell me if it is possible to Downgrade from Android 8.1 to 7 without unlocking the bootloader? All the videos I find, the bootloaders are already unlocked.
Click to expand...
Click to collapse
As mentioned before - you cannot root a device without unlocking the bootloader!
Why do you want a one click root? They are buggy & full of bloatware
Magisk should be the only method you should be using to root a device - either flashing through twrp or by patching the kernel and flashing the patched image through fastboot
What ever method you choose you need an unlocked bootloader to root!
Why would you want to downgrade? You can flash all parts of a firmware image except gpt & bootloader but again you might need an unlocked bootloader to do this but I don't see the point
TheFixItMan said:
As mentioned before - you cannot root a device without unlocking the bootloader!
Why do you want a one click root? They are buggy & full of bloatware
Magisk should be the only method you should be using to root a device - either flashing through twrp or by patching the kernel and flashing the patched image through fastboot
What ever method you choose you need an unlocked bootloader to root!
Why would you want to downgrade? You can flash all parts of a firmware image except gpt & bootloader but again you might need an unlocked bootloader to do this but I don't see the point
Click to expand...
Click to collapse
In fact, since i need to unlock the bootloader to root, for now, it wouldn't be a good option for me.
But there are apps that I really need and that don't work correctly on Android versions above Nougat, if I could get Downgrade without losing data, that would help me immensely for now.
Is there a possibility that I can downgrade to android 7 with the locked bootloader ? What can go wrong? Brick?
vanhead said:
In fact, since i need to unlock the bootloader to root, for now, it wouldn't be a good option for me.
But there are apps that I really need and that don't work correctly on Android versions above Nougat, if I could get Downgrade without losing data, that would help me immensely for now.
Is there a possibility that I can downgrade to android 7 with the locked bootloader ? What can go wrong? Brick?
Click to expand...
Click to collapse
You would have to format data - it would bootloop otherwise and I've already said. Flash all parts of firmware except gpt and bootloader however it may not flash as your bootloader is not unlocked
If the flashing goes wrong and your bootloader is not unlocked you will not be able to recover the device without taking it to a repair shop
My advice just don't bother - if you want to mod your phone unlock the bootloader!
And what app doesn't work above nougat?