Database Info

Question: Will flashing stock and relocking the bootloader get my warranty back?

I can't seem to find the answer to this question anywhere on the moto g forum, so that means I'll have to ask you guys myself.
I purchased this device after having an s3 mini. On the s3 mini I was able to install the TWRP recovery and some custom roms like cyanogenmod. But if anything would go wrong I would just flash the stock rom and bring it over to the store for repairs.
But after looking on this forum, it seems that whenever you unlock the bootloader on the moto g3 your warranty is permanently voided. So here's my question:
If I unlock the bootloader and flash TWRP, cyanogenmod, etc. and my device breaks. Would flashing stock and relocking the bootloader get my warranty back? ( i don't know if it makes any difference but i live in the Netherlands )
I hope you guys will be able to help me answer this question because i really want to root my device and get cyanogenmod on it.

Warranty is legally void the moment you submit the unlock code to Motorola. They will update their database with your unlock code and provide you the unlock key.
So relocking bootloader or flashing stock rom won't restore your warranty legally. But if lucky, the motocare engineer might proceed to repair your phone by seeing stock rom on board. So keep stock while visiting motocare. But legally it doesn't renew your warranty.

The answer is simple and easy to find... No, once you accept Motorola's T&C for unlocking the bootloader, which are crystal clear if you even glance at them, and receive your unlock token your warranty is void, period. You don't even have to actually unlock the bootloader, just accepting the T&C is enough. At this point your serial number/IMEI are flagged as warranty void in Motorola's database. The actual state of your device doesn't even matter.
BTW, technically what you did with your S3 should have voided the warranty, but depending on who handled the warranty (carrier or Samsung) and their thoroughness, many got through anyway. To the best of my knowledge the only devices you can modify significantly and not void the warranty are Nexus devices.
Sent from my MotoG3 using Tapatalk

acejavelin said:
The answer is simple and easy to find... No, once you accept Motorola's T&C for unlocking the bootloader, which are crystal clear if you even glance at them, and receive your unlock token your warranty is void, period. You don't even have to actually unlock the bootloader, just accepting the T&C is enough. At this point your serial number/IMEI are flagged as warranty void in Motorola's database. The actual state of your device doesn't even matter.
BTW, technically what you did with your S3 should have voided the warranty, but depending on who handled the warranty (carrier or Samsung) and their thoroughness, many got through anyway. To the best of my knowledge the only devices you can modify significantly and not void the warranty are Nexus devices.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I've already been to the motorola site for unlocking the bootloader before (xda won't let me post the URL) and I have followed the instructions up until step 6: "Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
After that I did NOT click the "REQUEST UNLOCK KEY" button. Is my warranty voided because of following the steps up until step 6?
(because if it is voided, I might as well just root it already)

Djurre2709 said:
I've already been to the motorola site for unlocking the bootloader before (xda won't let me post the URL) and I have followed the instructions up until step 6: "Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
After that I did NOT click the "REQUEST UNLOCK KEY" button. Is my warranty voided because of following the steps up until step 6?
(because if it is voided, I might as well just root it already)
Click to expand...
Click to collapse
No, not yet... I don't remember the step #, but Until you accept the T&C and request the unlock token, your warranty is good.
Sent from my MotoG3 using Tapatalk

acejavelin said:
No, not yet... I don't remember the step #, but Until you accept the T&C and request the unlock token, your warranty is good.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help!
I have desided to request the key, I'll be rooting my device very soon.

Djurre2709 said:
Thanks for the help!
I have desided to request the key, I'll be rooting my device very soon.
Click to expand...
Click to collapse
I'm facing the same problem as you. What made you choose to unlock it?
Envoyé de mon MotoG3 en utilisant Tapatalk

vinz244 said:
I'm facing the same problem as you. What made you choose to unlock it?
Envoyé de mon MotoG3 en utilisant Tapatalk
Click to expand...
Click to collapse
I decided to root my device because on my other devices I use cyanogenmod as a daily driver. Because of this I'm used to the advantages it has, and the freedom you have over your device. I don't have my warranty anymore, but the fact that my s3 mini actually faced the same problems and I was able to get it repared by just flashing stock made me think that the risk isn't that big. Also the other dude said that by flashing stock the device might stil be repaired. So I decided to take the risk and root my device. After that I flashed cyanogenmod on it and now I use this as daily driver on my Moto G 2015 too.
So the chances are that eventhough my warranty is voided legally, they might stil fix my device if broken. Because of the fact that they did this with my other device once I thought it wouldn't do any harm to root this device too.
Some tips if you do decide to root your device;
go over to the FAQ tab on this forum to find yourself the link to the TWRP recovery. This is as far as I know the best custom recovery for the Moto G 2015.
Also on the beginning of the FAQ it says you need to find out what device you have (personally I've got the XT1541), look this up for your own case and do your research before you start unlocking the bootloader.
After you've unlocked the bootloader your device will be factory reset, so make sure you back up all your data.
When you have installed the TWRP, make sure to make a 'nandroid backup' from your stock rom in case you fail to install any other rom (might you intend to do so). Keep this nandroid backup stored on your computer too.
If you decide to install cyanogenmod (certainly as a beginner) I would recommend to install a snapshot instead of a nightly. Also don't install an unofficial except if your absolutely shure you want to do this.
For the original download page of cyanogenmod go to download.cyanogenmod.org and search for the device 'osprey'
When you install gapps I strongly suggest to install the nano package (the other packages didn't work for me)
Go to opengapps.org and select ARM - 5.1.1 (or 6.0 depending on the android version) - nano
Just a few tips for you ( unfortunately I had to find out some of these things the hard way, so that's why I thought I would leave them here for you )
Good luck with whatever you intend to do with your device and I hope my opinion and knowledge might help you to decide what you want to do with your device

Djurre2709 said:
I decided to root my device because on my other devices I use cyanogenmod as a daily driver. Because of this I'm used to the advantages it has, and the freedom you have over your device. I don't have my warranty anymore, but the fact that my s3 mini actually faced the same problems and I was able to get it repared by just flashing stock made me think that the risk isn't that big. Also the other dude said that by flashing stock the device might stil be repaired. So I decided to take the risk and root my device. After that I flashed cyanogenmod on it and now I use this as daily driver on my Moto G 2015 too.
So the chances are that eventhough my warranty is voided legally, they might stil fix my device if broken. Because of the fact that they did this with my other device once I thought it wouldn't do any harm to root this device too.
Click to expand...
Click to collapse
(Sigh)... Of course they will fix your device, just not under warranty and not for free. I don't know how much clearer Motorola can be, if you accept the T&C and get the unlock token, your warranty is void. Period.
Your ESN & serial number are flagged in Motorola's database as no warranty, the actual state of the device is not relevant, they don't care, even if you never actually unlock or modify the device... This is not Samsung, LG, HTC, or any other company, this is Motorola and it's how they do it. They are very clear and don't try to hide it or fudge it, it just is and they make sure you know it.
But at the same time, the failure rate of the Moto G is extremely low, so your probably fine anyway.
Sent from my MotoG3 using Tapatalk

Djurre2709 said:
I decided to root my device because on my other devices I use cyanogenmod as a daily driver. Because of this I'm used to the advantages it has, and the freedom you have over your device. I don't have my warranty anymore, but the fact that my s3 mini actually faced the same problems and I was able to get it repared by just flashing stock made me think that the risk isn't that big. Also the other dude said that by flashing stock the device might stil be repaired. So I decided to take the risk and root my device. After that I flashed cyanogenmod on it and now I use this as daily driver on my Moto G 2015 too.
So the chances are that eventhough my warranty is voided legally, they might stil fix my device if broken. Because of the fact that they did this with my other device once I thought it wouldn't do any harm to root this device too.
Some tips if you do decide to root your device;
go over to the FAQ tab on this forum to find yourself the link to the TWRP recovery. This is as far as I know the best custom recovery for the Moto G 2015.
Also on the beginning of the FAQ it says you need to find out what device you have (personally I've got the XT1541), look this up for your own case and do your research before you start unlocking the bootloader.
After you've unlocked the bootloader your device will be factory reset, so make sure you back up all your data.
When you have installed the TWRP, make sure to make a 'nandroid backup' from your stock rom in case you fail to install any other rom (might you intend to do so). Keep this nandroid backup stored on your computer too.
If you decide to install cyanogenmod (certainly as a beginner) I would recommend to install a snapshot instead of a nightly. Also don't install an unofficial except if your absolutely shure you want to do this.
For the original download page of cyanogenmod go to download.cyanogenmod.org and search for the device 'osprey'
When you install gapps I strongly suggest to install the nano package (the other packages didn't work for me)
Go to opengapps.org and select ARM - 5.1.1 (or 6.0 depending on the android version) - nano
Just a few tips for you ( unfortunately I had to find out some of these things the hard way, so that's why I thought I would leave them here for you )
Good luck with whatever you intend to do with your device and I hope my opinion and knowledge might help you to decide what you want to do with your device
Click to expand...
Click to collapse
Thanks I still need time to decide but interesting! My best experience with support is probable with Archos. I sent them my phone bricked 3 times because of bad flashed rom and they would send me a new one
Envoyé de mon MotoG3 en utilisant Tapatalk

Question Relocking the bootloader shows different message than stock in fastboot.

So, I have a Moto G9 Power, and I unlocked the bootloader to fool around with root access. Then I realised, that root access wasn't all that powerful as it was on older Android versions.
You simply do not have access to the root partition on Android 10, it is mounted read-only, and it ignores all commands to remount it as read-write.
Also, the location of the Boot animation zip of this phone is wierd, it is in /product/media, not /system/media, which effectively renders all Boot animation Magisk modules or apps useless.
Plus, the battery drain once unlocked and rooted was so much more than when on stock. And other stupid idiosyncrasies made being root not all that powerful.
So I decided to un-root and relock the bootloader.
The thing is, when it was stock, in fastboot mode, it showed
Code:
oem_locked
Now after relocking it by
Code:
fastboot oem lock
it shows
Code:
flashing_locked
I'm pretty sure the difference between the two is enough for the service center to deny my warranty (which I voided by unlocking it in the first place, I know, I know. But reverting back to stock should make the service guys not notice) if something happened to the phone.
Is there any way I can get the original message back? Am I permanently screwed? Please respond, anyone.

mistersmee said:
So, I have a Moto G9 Power, and I unlocked the bootloader to fool around with root access. Then I realised, that root access wasn't all that powerful as it was on older Android versions.
You simply do not have access to the root partition on Android 10, it is mounted read-only, and it ignores all commands to remount it as read-write.
Also, the location of the Boot animation zip of this phone is wierd, it is in /product/media, not /system/media, which effectively renders all Boot animation Magisk modules or apps useless.
Plus, the battery drain once unlocked and rooted was so much more than when on stock. And other stupid idiosyncrasies made being root not all that powerful.
So I decided to un-root and relock the bootloader.
The thing is, when it was stock, in fastboot mode, it showed
Code:
oem_locked
Now after relocking it by
Code:
fastboot oem lock
it shows
Code:
flashing_locked
I'm pretty sure the difference between the two is enough for the service center to deny my warranty (which I voided by unlocking it in the first place, I know, I know. But reverting back to stock should make the service guys not notice) if something happened to the phone.
Is there any way I can get the original message back? Am I permanently screwed? Please respond, anyone.
Click to expand...
Click to collapse
As far as I know anything with custom unlocks voids warranties the thing is that message likely changes to keep people from changing it back, I'm not sure what type of checks they do or how much your providers know about the device you have but considering they don't care as long as its relocked when you turn it in you may be alright. Its not like it couldn't be unlocked by them for various other reasons like flashing stock fw if it need to be fixed in that form unless they have someway of restoring that message themselves someone on our end would have to replicate it and that would take some dedicated development to do so.

Mr.Conkel said:
As far as I know anything with custom unlocks voids warranties the thing is that message likely changes to keep people from changing it back, I'm not sure what type of checks they do or how much your providers know about the device you have but considering they don't care as long as its relocked when you turn it in you may be alright. Its not like it couldn't be unlocked by them for various other reasons like flashing stock fw if it need to be fixed in that form unless they have someway of restoring that message themselves someone on our end would have to replicate it and that would take some dedicated development to do so.
Click to expand...
Click to collapse
Oh. Ok, cool. Cheers, mate, thanks!

mistersmee said:
Oh. Ok, cool. Cheers, mate, thanks!
Click to expand...
Click to collapse
I mean Motorola G Power devices are fairly popular here, wait around and keep an eye on your devices thread considering it can be unlocked with enough time you should be given a custom rom like LOS or Crdroid. The G7 power has tons of custom access as well as other G series device from Motorola so it is very likely to get something, which would very likely enable the custom access your looking for with modifications as it will be built normally.
Cheers!

Many Android devices set a "tampered" flag - which is responsible for voiding warranty of the devices - within the bootloader what can get queried by service centers.

jwoegerbauer said:
Many Android devices set a "tampered" flag - which is responsible for voiding warranty of the devices - within the bootloader what can get queried by service centers.
Click to expand...
Click to collapse
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?

Mr.Conkel said:
I mean Motorola G Power devices are fairly popular here, wait around and keep an eye on your devices thread considering it can be unlocked with enough time you should be given a custom rom like LOS or Crdroid. The G7 power has tons of custom access as well as other G series device from Motorola so it is very likely to get something, which would very likely enable the custom access your looking for with modifications as it will be built normally.
Cheers!
Click to expand...
Click to collapse
Will do.

mistersmee said:
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Click to expand...
Click to collapse
IDK.

jwoegerbauer said:
IDK.
Click to expand...
Click to collapse
Ok, cool. I'll search around.

mistersmee said:
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Click to expand...
Click to collapse
No nothing like that for Moto devices.
Generally, Motorola doesn't enforce the voided warranty issue.
If the device has a factory flaw and still would be under warranty, they will cover it.
At least this is based on posts on the forum.

sd_shadow said:
No nothing like that for Moto devices.
Generally, Motorola doesn't enforce the voided warranty issue.
If the device has a factory flaw and still would be under warranty, they will cover it.
At least this is based on posts on the forum.
Click to expand...
Click to collapse
Oh. Ok, that's a relief.

How To Guide Rooting the SM-F711B (on Version F711BXXU2AUI4) working

First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx

When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.

@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2

MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.

naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?

Press the power and volume down buttons for about 7 seconds and it will reboot

beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted

Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/

twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.

d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.

twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.

d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?

twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons

d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.

I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?

david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.

Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now

david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)

I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.

david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.

Risks of having an unlocked bootloader

Hello guys, This is my first thread on XDA forum.
I just bought Xiaomi device (Poco X3 Pro Global) a few days ago.
So this is my first time to try custom rom, I searched what I'm trying to do, I'd like to make sure whether what I understand is correct or not since I'm totally new on custom rom.
the sources I mainly referred to:
source1
source2
Basic assumption:
1. Only flash custom rom without rooting
2. All unlocking bootloader and flashing custom rom process done perfectly, and all resouces (recovery, rom, ADB tool etc...) used during process are 100% clean and genuine.
3. No cold boot attack (source2) happens on me.
Q1. source1 is really helpful, but it's from 2012, is this still valid today?
Q2. source1 is posted on Galaxy Nexus forum, but is this applied to all android based devices, right?
Q3. This threat model assumes attacker has physical access to device, then I guess unlocking bootloader itself is 100% totally irrelevant to software level security risks like malware or OS vulnerability, is this right? (assuming no rooting and 100% genuine rom and resources)
Q4. From source1 you can choose between [device encryption] and [relocking bootloader] to protect security, which methods do you recommend using?
I feel I'm much more inclined to try device encryption method since I don't know if it's possible to relock bootloader safely after migrating from Global stock rom to xiaomi.eu rom. (Can anyone confirm this?) I fear it become bricked during relocking process.
Q5. So if I set device encryption with strong password and turn off USB debugging mode, I need not too worrysome?
Are there any other points in terms of security to bear in mind if you use device with unlocked bootloader?
Thank you for reading my thread

[INFO] Understanding the risks of having an unlocked bootloader
While unlocking the bootloader on a Galaxy Nexus unleashes the full potential of the bootloader, it also poses a security risk. Even with your lockscreen protected with a pattern/PIN/password, not having flashed a custom recovery, having an...
forum.xda-developers.com

jwoegerbauer said:
[INFO] Understanding the risks of having an unlocked bootloader
While unlocking the bootloader on a Galaxy Nexus unleashes the full potential of the bootloader, it also poses a security risk. Even with your lockscreen protected with a pattern/PIN/password, not having flashed a custom recovery, having an...
forum.xda-developers.com
Click to expand...
Click to collapse
that's what I linked in thread (source1)

Only a side-remark:
An Android Smartphone bootloader is processor-specific and every OEM has its own version of bootloader specific for the hardware present in its environment.
It's the primary task of every bootloader to verify the Android OS to be loaded is genuine means signed by OEM to ensure the Android OS ( it's by nature a Custom ROM ) works flawlessly as it can be expected by user. People who use a phone as a tool and not as a toy probably never come up with the idea to unlock the bootloader because they know about the strengths and weaknesses of the phone when they bought it, they can expect that OEM did their best with regards to a phone's performance - OEMs are certainly not dumber than generally claimed by the modder / hacker scene.
My POV: Unlocking a phone's bootloader is an unnecessary action at all. If people do so they indirectly admit that they have purchased a phone that does not meet their expectations - they have made a wrong purchase.

Thanks for comment.
I understand your POV.
I realized later Global rom can't do call recording, that's the main reason why I try to flash xiaomi.eu rom and other optimazations are second reason.
And this phone will be my main phone so I wanted to make sure about security risk before I will change rom.

cromcromc said:
Thanks for comment.
I understand your POV.
I realized later Global rom can't do call recording, that's the main reason why I try to flash xiaomi.eu rom and other optimazations are second reason.
And this phone will be my main phone so I wanted to make sure about security risk before I will change rom.
Click to expand...
Click to collapse
Having an unlocked bootloader doesn't need to be a risk whatsover as long as you're not flashing untrusted ROMS and other components to the device and critically control anything being flashed to the device. If you're flashing a signed ROM from the manufacturer as it sounds like is your plan, there is nothing to worry about. You can even lock the BL again after flashing & optimizing if you absolutely wish to although usually not recommended.

BL unlocking/custom ROM Question: What is permanently lost if I do that?

Hi,
Just grabbed an Xperia 5 II on a great deal and I'm loving this device. It's an A002SO. I have noticed in other threads that there is some loss with original functionality of the phone (maybe Dolby or some other features are broken even if phone is restored to stock). Is it true? And if so what features are broken.
I noticed that Xperia camera software are available for other roms too which is great but what about device fingerprint and BL unlock sensing protection for banking apps? (I am not interested in rooting the phone after flashing lineage/AOSP roms but more concerned about the broken safety net in-case I go custom ROM route)
Also, is there a risk of losing IMEI with all this process? Not talking about crossflashing here but would love an AIO guide about BL unlock > recovery > ROM and the Back to stock locked bootloader guides if there are any.
Thank you!

dark_prince said:
Hi,
Just grabbed an Xperia 5 II on a great deal and I'm loving this device. It's an A002SO. I have noticed in other threads that there is some loss with original functionality of the phone (maybe Dolby or some other features are broken even if phone is restored to stock). Is it true? And if so what features are broken.
I noticed that Xperia camera software are available for other roms too which is great but what about device fingerprint and BL unlock sensing protection for banking apps? (I am not interested in rooting the phone after flashing lineage/AOSP roms but more concerned about the broken safety net in-case I go custom ROM route)
Also, is there a risk of losing IMEI with all this process? Not talking about crossflashing here but would love an AIO guide about BL unlock > recovery > ROM and the Back to stock locked bootloader guides if there are any.
Thank you!
Click to expand...
Click to collapse
I have a different model, but I recently went from stock to Lineage OS, then back to stock. I haven't had any issues. Dolby works, my data/LTE works, and I can still use my banking app just fine. Fingerprint detection was a bit more finnicky with Lineage OS, though.
I should also note, I'm currently rooted with my bootloader unlocked, and still no issues.

SomeRandomGuy212 said:
I have a different model, but I recently went from stock to Lineage OS, then back to stock. I haven't had any issues. Dolby works, my data/LTE works, and I can still use my banking app just fine. Fingerprint detection was a bit more finnicky with Lineage OS, though.
I should also note, I'm currently rooted with my bootloader unlocked, and still no issues.
Click to expand...
Click to collapse
I gave up in the end because my device is Japan Softbank with bootloader unlocking not allowed. Crossflashing instructions have alot of "you can", "I think" but no definite root-to-fruit guide so I may convert it to global model and BL unlock without losing imei / 4G. Thank you for taking time to write the clarification.

dark_prince said:
I gave up in the end because my device is Japan Softbank with bootloader unlocking not allowed. Crossflashing instructions have alot of "you can", "I think" but no definite root-to-fruit guide so I may convert it to global model and BL unlock without losing imei / 4G. Thank you for taking time to write the clarification.
Click to expand...
Click to collapse
I don't actually know if that would work... I don't mean to give you another indefinite answer, but I tried that once on a Japanese Xperia 10 II. I know it's a different device, but it may still apply in your situation. I would still try it, though. Worse case scenario, you have to use Sony's repair tool to get back to stock.
(Also, if you're interested in a non Japanese model, I am currently selling my 5 II.)

SomeRandomGuy212 said:
I don't actually know if that would work... I don't mean to give you another indefinite answer, but I tried that once on a Japanese Xperia 10 II. I know it's a different device, but it may still apply in your situation. I would still try it, though. Worse case scenario, you have to use Sony's repair tool to get back to stock.
(Also, if you're interested in a non Japanese model, I am currently selling my 5 II.)
Click to expand...
Click to collapse
I am from Pakistan so it's gonna cost me double the actual price to pay customs taxes and get it cleared for use in-country. Our country has a rule about only the devices which are approved after paying hefty taxes, are permitted on Pakistan's cellular operators.

This was discussed before, in short you seem to lose out certain manufacturer keys and your phone remembers you have unlocked its bootloader before. As for functionality, iirc they seem to come back after relocking.
More info: https://forum.xda-developers.com/t/closed-delete.4177209/post-87242833