Related
My last phone (Nexus 4) was stolen. My new device, the Nexus 6, as you all know comes with enhanced security measures, requiring authentication even after a factory reset. Now, I had grown accustomed to playing around with wiping, rooting, custom roms, kernels, radios, etc with my Nexus 4. Now that I have had my Nexus 6 for a bunch of months, I am starting to think about rooting my device (so I can install an SSH server and have my phone automatically open a tunnel back to my server). My only hesitation is turning the OEM unlocking switch to on. See, I am a big fan of the new security measures that require authentication after a device reset, and would much prefer to keep that feature enabled. I've searched around on Google and XDA, and I haven't been able to find any definitive answers on how unlocking the bootloader in order to root the device will affect these security mechanisms.
My understanding is this: in order to root the Nexus 6, you need to enable OEM unlocking, which allows flashing pretty much any image onto the phone. If any image can be flashed to the phone, this security mechanism can be circumvented.
Two questions:
1. (pretty sure the answer to this is no) Can I root my phone and prevent flashing of images that would circumvent the security feature
2. Will rooting my phone make it easier for an unknown party to gain access to the device via another route
Unlocking the bootloader really only allows you to flash unsigned images, and root provides you with the option to grant administrative access to applications.
Neither one of those has anything to do with encrypted data, or in any way makes encrypted data readable without the key.
The bootloader unlock will make it easier for a thief to wipe all the data on the device without reading it, so he can use the device or sell it as functioning... Even then, you may be able to factory reset an encrypted device without the key anyways... At which point I would think they could make a new key for the freshly wiped partition?
Anything that is going to run unauthorised code at root level is likely going to use other exploits to achieve root on their own, like users do to gain root on devices that are locked down. You having root access doesn't give the right for anything to run as root unless you approve it (or if someone managed to find some exploit in the version of supersu your running, but this is not likely... and if we are assuming any code may have holes in it you're not safe no matter what you do). It does give you the possibility of being tricked into running malicious code that is disguised as some utility... But that is a risk your going to take running any software that isn't from a stable corperation you can take legal action against. Trust who wrote the code or don't use it.
If in question number 1 "the security feature" is encryption, then yes having and unlocked bootloader means if someone takes your phone they can flash a kernel that does not force encryption, they would then have to format the userdata partition to encrypt the phone. Without luck, guessing the password, or discovering some amazing undocumented flaw in the encryption algorithm they will not being able to read your data with out having the key, or guessing it.
@scryan
If you have unlocked the bootloader and have installed a custom recovery (TWRP), are you able to see the list of files in the file manager of TWRP, if the device is encrypted?
Nikos2k said:
@scryan
If you have unlocked the bootloader and have installed a custom recovery (TWRP), are you able to see the list of files in the file manager of TWRP, if the device is encrypted?
Click to expand...
Click to collapse
Yes. Otherwise couldn't pick a file to flash. It actually only encrypts user data. Apps, zips ect are not encrypted or we couldn't pull and modify them.
prdog1 said:
Yes. Otherwise couldn't pick a file to flash. It actually only encrypts user data. Apps, zips ect are not encrypted or we couldn't pull and modify them.
Click to expand...
Click to collapse
the user data that are encrypted include files on the sdcard folder? (e.g. pdfs, images in DCIM folder etc)
i am asking because in my device in Settings -> Security -> Encryption it shows that it is encrypted, in TWRP however i can see all the files
Can i make the custom recovery to ask for the pin? do I have to enable PIN as a screen lock?
What happens if i use an unlock pattern or just swipe for unlock?
Nikos2k said:
the user data that are encrypted include files on the sdcard folder? (e.g. pdfs, images in DCIM folder etc)
i am asking because in my device in Settings -> Security -> Encryption it shows that it is encrypted, in TWRP however i can see all the files
Can i make the custom recovery to ask for the pin? do I have to enable PIN as a screen lock?
What happens if i use an unlock pattern or just swipe for unlock?
Click to expand...
Click to collapse
TWRP will use same pin as Device lock. Only thing I have seen if you use pinlock have to convert 5x5 to 4x4. There's a way to convert it located in this forum somewhere. Swipe to unlock has no pin so TWRP is open. Unlock pattern works also. Either pin or swipe has to be converted don't remember which. I run wide open encrypted so have never played with it.
prdog1 said:
TWRP will use same pin as Device lock. Only thing I have seen if you use pinlock have to convert 5x5 to 4x4. There's a way to convert it located in this forum somewhere.
Click to expand...
Click to collapse
By pinlock you mean the pattern screen lock?
I think it is 3 x 3, not 4x4 or 5x5
And since I use this pattern screen lock, which cannot be input in TWRP, this means that I have to disable it b4 I need to enter recovery?
This makes me a bit uncomfortable since I may need to enter recovery because of a problem with the system
Nikos2k said:
By pinlock you mean the pattern screen lock?
I think it is 3 x 3, not 4x4 or 5x5
And since I use this pattern screen lock, which cannot be input in TWRP, this means that I have to disable it b4 I need to enter recovery?
This makes me a bit uncomfortable since I may need to enter recovery because of a problem with the system
Click to expand...
Click to collapse
Start with this thread. It explains TWRP.
http://forum.xda-developers.com/nexus-6/help/twrp-2-8-5-0-password-help-t3046630
prdog1 said:
Start with this thread. It explains TWRP.
http://forum.xda-developers.com/nexus-6/help/twrp-2-8-5-0-password-help-t3046630
Click to expand...
Click to collapse
thank you it worked!
scryan said:
Unlocking the bootloader really only allows you to flash unsigned images, and root provides you with the option to grant administrative access to applications.
Neither one of those has anything to do with encrypted data, or in any way makes encrypted data readable without the key.
The bootloader unlock will make it easier for a thief to wipe all the data on the device without reading it, so he can use the device or sell it as functioning... Even then, you may be able to factory reset an encrypted device without the key anyways... At which point I would think they could make a new key for the freshly wiped partition?
Anything that is going to run unauthorised code at root level is likely going to use other exploits to achieve root on their own, like users do to gain root on devices that are locked down. You having root access doesn't give the right for anything to run as root unless you approve it (or if someone managed to find some exploit in the version of supersu your running, but this is not likely... and if we are assuming any code may have holes in it you're not safe no matter what you do). It does give you the possibility of being tricked into running malicious code that is disguised as some utility... But that is a risk your going to take running any software that isn't from a stable corperation you can take legal action against. Trust who wrote the code or don't use it.
If in question number 1 "the security feature" is encryption, then yes having and unlocked bootloader means if someone takes your phone they can flash a kernel that does not force encryption, they would then have to format the userdata partition to encrypt the phone. Without luck, guessing the password, or discovering some amazing undocumented flaw in the encryption algorithm they will not being able to read your data with out having the key, or guessing it.
Click to expand...
Click to collapse
Ok, so for encryption, "Allow OEM Unlocking" allows flashing of unsigned images (such as the one used for root), which means if someone gets a hold of my phone, they can put whatever they want on it, including flashing a custom rom.
So my next question is, what about being required to sign into the last Google account used on the phone even after a factory reset (device protection / factory reset protection / not sure what it's called exactly)? Is that area of the bootloader / rom / memory / wherever it lives flashable? If you have an unlocked bootloader, is it possible to flash some image to the device that disables this? Hah, that sounds bad. Really, I want to root my Nexus 6, but I haven't decided if it would be worth giving up the anti-theft required login after reset.
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
quickdry21 said:
Ok, so for encryption, "Allow OEM Unlocking"
encryption and oem unlock ar 2 entirely different things
allows flashing of unsigned images
allows you to unlock the boottloader, which allows you to flash unsigned img's. the setting itself does nothing but enable the ability. to unlock
(such as the one used for root), which means if someone gets a hold of my phone, they can put whatever they want on it, including flashing a custom rom.
yes
So my next question is, what about being required to sign into the last Google account used on the phone even after a factory reset (device protection / factory reset protection / not sure what it's called exactly)? Is that area of the bootloader / rom / memory / wherever it lives flashable? If you have an unlocked bootloader, is it possible to flash some image to the device that disables this? Hah, that sounds bad. Really, I want to root my Nexus 6, but I haven't decided if it would be worth giving up the anti-theft required login after reset.
i think if someone were to completely wipe the phone, use a different gmail and sim, the google protection would be gone, but i could be wrong. im not positive on that one.
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
some extremely savvy person "may" be able to make a rom without the google protection, but i have never seen it tried.it may be a core feature that cant be removed.
i really wouldnt worry about that. the likelihood that someone would steal or find your device and have the skills to do all you asked above, is very remote.
Click to expand...
Click to collapse
in red above.
bweN diorD said:
in red above.
Click to expand...
Click to collapse
protection will be gone if you flash android 5.0.1. if you wipe and flash android 5.1.1, the protection will still be there and will ask for your password first.
bweN diorD said:
in red above.
Click to expand...
Click to collapse
Thanks, that does seem to make sense.
I know this comes across as overly paranoid, but I ask also because I'm a curious developer. I'm interested in understanding how android's insides work in general as well as how the new device protection fits in with rooting, custom roms, unlocking the bootloader, etc. (just how well does it prevent unauthorized use of devices)
Interesting, that says to me there is a relatively easy way to get around the reset protection if a phone has an unlocked bootloader. Albeit, relatively easy is relative.
quickdry21 said:
Interesting, that says to me there is a relatively easy way to get around the reset protection if a phone has an unlocked bootloader. Albeit, relatively easy is relative.
Click to expand...
Click to collapse
easy, yes, for one of us. but for a typical user, very hard. anyways, i dont like letting out the secret of how to bypass it, so keep it quiet please
simms22 said:
easy, yes, for one of us. but for a typical user, very hard. anyways, i dont like letting out the secret of how to bypass it, so keep it quiet please
Click to expand...
Click to collapse
Yes, agreed. I'm going to edit out that quote.
quickdry21 said:
Ok, so for encryption, "Allow OEM Unlocking" allows flashing of unsigned images (such as the one used for root), which means if someone gets a hold of my phone, they can put whatever they want on it, including flashing a custom rom.
So my next question is, what about being required to sign into the last Google account used on the phone even after a factory reset (device protection / factory reset protection / not sure what it's called exactly)? Is that area of the bootloader / rom / memory / wherever it lives flashable? If you have an unlocked bootloader, is it possible to flash some image to the device that disables this? Hah, that sounds bad. Really, I want to root my Nexus 6, but I haven't decided if it would be worth giving up the anti-theft required login after reset.
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
Click to expand...
Click to collapse
Maybe someone could figure out something?
But if your device is wiped, and basically all the partitions are re-written.... Where do you want to store the last google account information to check against?
No one is going to plan on stealing your phone, ask you if the bootloader is unlocked, then decide not to if they say no. None of the security really prevents your phone from being stolen. Nothing just looking at your phone lets a would be thief know that its encrypted and not unlocked...
The encryption and locked bootloader will not prevent your phone from being stolen. The encryption will protect your data, and the locked booloader will make it harder to reset the device (though does factory recovery have a factory reset option? I would think this would allow the device to be wiped and encryption key to be reset anyways?)
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
Click to expand...
Click to collapse
What? You keep talking about this single security device? What are you talking about?
Do you mean encryption?
encryption is just how the data is stored on the device.
Say you have the word "Duck"
And we want to store that word in a safe way. As a VERY VERY basic method, we will encrypt this by shifting each letter of the alphabet a certain number of letters. This number will be something YOU give, so that others do not know how many letters we have shifted over.
So lets say you give us "5" as your key.
so the alphabet
abcdefghijklmnopqrstuvwxyz we will shift 5 letters over, starting on the fifth letter and wrapping around...
fghijklmnopqrstuvwxyzabcde so each letter matches up with a new letter.
D is the 4th letter of the alphabet, so we will use the 4th letter of of shifted alphabet, i
u is the 21st letter of the alphabet so we will use the 21st letter of our shifted alphabet, z
ect, ect... so Duck becomes Izho, and with out knowing how many letters to shift over, know one will know what that means (ok, obviously due to the simplicity of our encryption algorithm, anyone who is smart and cares can likely try different numbers until the output is a coherent word. the actual method of encryption is significantly more complex, and the key is more then one characters
See here for more intellegent details: https://wiki.archlinux.org/index.php/Disk_encryption#How_the_encryption_works
quickdry21 said:
Yes, agreed. I'm going to edit out that quote.
Click to expand...
Click to collapse
na, it ok, you can leave it here. that way if someone really needs to, theyll find the answer here. just dont go around spreading it around i meant
scryan said:
Maybe someone could figure out something?
But if your device is wiped, and basically all the partitions are re-written.... Where do you want to store the last google account information to check against?
No one is going to plan on stealing your phone, ask you if the bootloader is unlocked, then decide not to if they say no. None of the security really prevents your phone from being stolen. Nothing just looking at your phone lets a would be thief know that its encrypted and not unlocked...
The encryption and locked bootloader will not prevent your phone from being stolen. The encryption will protect your data, and the locked booloader will make it harder to reset the device (though does factory recovery have a factory reset option? I would think this would allow the device to be wiped and encryption key to be reset anyways?)
Click to expand...
Click to collapse
I'm not expecting this "Device Protection" feature to prevent my phone from being stolen, I'm more interested in the **** you aspect to someone who tries, and maybe them returning it to me for some money.
scryan said:
What? You keep talking about this single security device? What are you talking about?
Do you mean encryption?
Click to expand...
Click to collapse
I'm not sure if you are aware, but with the release of 5.1, there is a new security feature (think it's called Device Protection, but that seems to encompass some other things) that requires you to login to the last Google account attached to the phone after a factory reset (whether done from the settings UI, or from recovery mode). If you are unable to login to a Google account that was attached to the phone, the phone becomes worthless (there have been some posts on xda about people "acquiring" a Nexus 6 and being unable to use it), some details here: https://support.google.com/nexus/answer/6172890
A quote from that link sums it up:
Important: You can enter information for any Google account that has been added to the device. If you can't provide this information during the setup process, you won't be able to use the device at all after the factory reset.
Click to expand...
Click to collapse
Now, this security feature is only available on new phones that are released with 5.1 (with the exception of the newest round of Nexus devices, which received it with the update to 5.1). This leads me to believe that some aspect is baked into the device. Separate encrypted partition maybe? Part of the bootloader software? I don't know, that's what I'm curious about.
scryan said:
encryption is just how the data is stored on the device.
Say you have the word "Duck"
And we want to store that word in a safe way. As a VERY VERY basic method, we will encrypt this by shifting each letter of the alphabet a certain number of letters. This number will be something YOU give, so that others do not know how many letters we have shifted over.
So lets say you give us "5" as your key.
so the alphabet
abcdefghijklmnopqrstuvwxyz we will shift 5 letters over, starting on the fifth letter and wrapping around...
fghijklmnopqrstuvwxyzabcde so each letter matches up with a new letter.
D is the 4th letter of the alphabet, so we will use the 4th letter of of shifted alphabet, i
u is the 21st letter of the alphabet so we will use the 21st letter of our shifted alphabet, z
ect, ect... so Duck becomes Izho, and with out knowing how many letters to shift over, know one will know what that means (ok, obviously due to the simplicity of our encryption algorithm, anyone who is smart and cares can likely try different numbers until the output is a coherent word. the actual method of encryption is significantly more complex, and the key is more then one characters
See here for more intellegent details: https://wiki.archlinux.org/index.php/Disk_encryption#How_the_encryption_works
Click to expand...
Click to collapse
Yes, I was not very clear in my original post about what security feature I was inquiring about. I'm aware of what encryption is. Part of the reason I am interested in rooting my phone is to reverse tunnel a SSH server on the phone, or possibly netcat, via SSH to my server, so I will be able to open up a shell on my phone from anywhere I desire.
Ahh yes, apologies, was unaware they implemented that feature. A bit dense this morning.
I would imagine unlocked bootloader/custom recovery would DEFINITELY negate this feature.
No one gonna give your phone back, particularly after you use this as a "**** you" While its just IMO, its better to enjoy your phone now. Screwing yourself out of features only to attempt to limit the phone once you don't have anything to do with it anymore does not seem to be particularly productive.
Hey guys,
So before I go ahead an attempt to unlock my bootloader and root my phone, just wanted to clear a couple of things up first.
This is my first Huawei device, previous one was a Sony, so I'm a little unfamiliar with a few things.
1. Is unlocking the bootloader required for root? If not, could someone point me in the direction of a guide to root only?
On the Sony, as long as I had a compatible firmware, I could root without unlocking the bootloader.
2. Will I lose any DRM Keys, proprietary features (Force Touch, Themes etc) through unlocking the bootloader and/or rooting? If so, can these be restored afterwards, while retaining root?
Again, with the Sony, unlocking the bootloader would result in losing DRM Keys related to visual enhancements, and were required to be backed up (via TABackup) prior to unlocking the bootloader. These could then be restored after root, and function as normal.
3. If you do lose features, and they can't be restored while keeping root. If I flash a stock ROM back on, losing root in the process, will these features also be restored?
Thanks
djyoshii said:
Hey guys,
So before I go ahead an attempt to unlock my bootloader and root my phone, just wanted to clear a couple of things up first.
This is my first Huawei device, previous one was a Sony, so I'm a little unfamiliar with a few things.
1. Is unlocking the bootloader required for root? If not, could someone point me in the direction of a guide to root only?
On the Sony, as long as I had a compatible firmware, I could root without unlocking the bootloader.
2. Will I lose any DRM Keys, proprietary features (Force Touch, Themes etc) through unlocking the bootloader and/or rooting? If so, can these be restored afterwards, while retaining root?
Again, with the Sony, unlocking the bootloader would result in losing DRM Keys related to visual enhancements, and were required to be backed up (via TABackup) prior to unlocking the bootloader. These could then be restored after root, and function as normal.
3. If you do lose features, and they can't be restored while keeping root. If I flash a stock ROM back on, losing root in the process, will these features also be restored?
Thanks
Click to expand...
Click to collapse
1) I used the SRK Tool (http://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999) and it showed step by step on rooting. Unlocking bootloader seems to be one of the steps before rooting. Maybe you can ask somboons about it.
2) For me, unlocking the bootloader basically resets my phone. And added a warning just before the phone bootup to android (from cold state or off state) that the bootloader has been unlocked and the phone is not trusted now. Just need to restore the apps and other data through the HiSuite backups after unlocking and rooting seems to be fine. Not sure about DRM keys, and others as didn't try those out before doing bootloader unlock. But I did lost my remote set up as it was not part of the HiSuite's data backup.
3) Do a backup with HiSuite should be able to help you. Just need to identify in the HiSuite that the apps and their data is being backed up.
prismfire said:
1) I used the SRK Tool (http://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999) and it showed step by step on rooting. Unlocking bootloader seems to be one of the steps before rooting. Maybe you can ask somboons about it.
Click to expand...
Click to collapse
Thanks mate, I did have a look at that thread as well, and another (less detailed) post. Was just wanting to confirm if there was any other method without need for bootloader unlocking. Figure the less things to modify, the less chance of something going wrong, which has worked well for me so far.
prismfire said:
2) For me, unlocking the bootloader basically resets my phone. And added a warning just before the phone bootup to android (from cold state or off state) that the bootloader has been unlocked and the phone is not trusted now. Just need to restore the apps and other data through the HiSuite backups after unlocking and rooting seems to be fine. Not sure about DRM keys, and others as didn't try those out before doing bootloader unlock. But I did lost my remote set up as it was not part of the HiSuite's data backup.
Click to expand...
Click to collapse
Any way to remove that message while retaining root? Sounds similar to the 'yellow triangle' back when I had an S2, but that was able to be removed, is this the same?
Not too worried about backing up apps & data at the moment, I haven't fully set up my phone as I realised it would most likely be lost upon rooting. But thanks for the heads up!
prismfire said:
3) Do a backup with HiSuite should be able to help you. Just need to identify in the HiSuite that the apps and their data is being backed up.
Click to expand...
Click to collapse
Sorry I was more thinking along the lines of, if any P9+ exclusive features were to be lost during root, could they easily be restored simply by flashing a stock ROM again? Apps & app data seem to be easy enough to restore via HiSuite/Titanium etc
djyoshii said:
Thanks mate, I did have a look at that thread as well, and another (less detailed) post. Was just wanting to confirm if there was any other method without need for bootloader unlocking. Figure the less things to modify, the less chance of something going wrong, which has worked well for me so far.
Any way to remove that message while retaining root? Sounds similar to the 'yellow triangle' back when I had an S2, but that was able to be removed, is this the same?
Not too worried about backing up apps & data at the moment, I haven't fully set up my phone as I realised it would most likely be lost upon rooting. But thanks for the heads up!
Sorry I was more thinking along the lines of, if any P9+ exclusive features were to be lost during root, could they easily be restored simply by flashing a stock ROM again? Apps & app data seem to be easy enough to restore via HiSuite/Titanium etc
Click to expand...
Click to collapse
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Thanks guys
prismfire said:
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Click to expand...
Click to collapse
I read ur conversation and I have been wondering if it's safe so thank you. But I still have 1 question "if I change my oem can I still use my 2 sims"?
prismfire said:
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Click to expand...
Click to collapse
So i've successfully rooted the phone, and yeah I get that 'your device has been unlocked and isn't safe' message on boot. It's not too much of a bother, besides being unsightly, but I don't really reboot my phone too often anyway.
I haven't noticed anything missing either, a few minor bugs have started to appear, but that might have to do with Xposed (I would guess).
Thanks for the advice & help!
Abdo2 said:
I read ur conversation and I have been wondering if it's safe so thank you. But I still have 1 question "if I change my oem can I still use my 2 sims"?
Click to expand...
Click to collapse
Dear Abdo2,
I'm not knowledgeable about the term oem here.
But if it is an issue of dual sim usage, I presume it's built into the ROM? What I know is all P9+ are hybrid dual sim, so it should be part of the ROM that you have.
I'm using VIE-L29C636B170. And it have the dual sim support in-built...although I've not used it yet.
See if anyone knowledgeable to your question passing by here can answer you. If not, maybe you can try the question & answer thread. Or post as another new thread if really no one got your question.
Regards.
---------- Post added at 02:39 PM ---------- Previous post was at 02:29 PM ----------
djyoshii said:
So i've successfully rooted the phone, and yeah I get that 'your device has been unlocked and isn't safe' message on boot. It's not too much of a bother, besides being unsightly, but I don't really reboot my phone too often anyway.
I haven't noticed anything missing either, a few minor bugs have started to appear, but that might have to do with Xposed (I would guess).
Thanks for the advice & help!
Click to expand...
Click to collapse
Dear djyoshii,
Good to know.
About the security message, one of it is mentioned here:
https://source.android.com/security/verifiedboot/verified-boot.html
For minor bugs, I'm not sure what you have. I've 3 games and 1 app that behaves not like when I used my previous phone (on Android 5.0). That's around 3-5% of all the apps that I used (meaning, majority works fine). Of those some of them related to Android 6.0 issue (actually the apps not updated for the Android version well). So, for me generally I would think it's marshmallow thing.
Regards.
Hi,
long time htc user (always totally unlocked) but looking to get a p9 plus for my wife (this is the important part).
can someone give me a simple answer...
if i only root the phone (for titanium backup mainly and maybe some cosmetic mods) will i be able to unroot it and return it under warranty?
phones here in Dubai are all unbranded so no problems there.
I have no need to unlock bootloader (yet )
gazzacbr said:
Hi,
long time htc user (always totally unlocked) but looking to get a p9 plus for my wife (this is the important part).
can someone give me a simple answer...
if i only root the phone (for titanium backup mainly and maybe some cosmetic mods) will i be able to unroot it and return it under warranty?
phones here in Dubai are all unbranded so no problems there.
I have no need to unlock bootloader (yet )
Click to expand...
Click to collapse
Dear gazzacbr,
From what I tried (been a while since I last did this), one will have to unlock the bootloader first before rooting. Apparently rooting is the last step of the whole process (if you are using the SRK tools). Now, to go back to the status of unrooted, I just use the superSU's total unroot option to unroot. And to go further back to bootloader, there is an option within SRK tool but my last attempt failed to relock the bootloader back. Didn't spend so much time to play around with the unlocking the bootloader after that. So, I just use as is - unlocked bootloader with no root.
One thing you need to note, for titanium backup, I end up just using their own desktop application called HiSuite. It does backup app and app data for you. Not system apps' data though. For theme customisation, MIUI do have a friendly Themer app that you can use to change the look. The corresponding theme files (*.hwt) are zipped, so you can always use 7zip to open and edit the assets inside to the one that you want.
Ok, thanks for the good info @prismfire. As long as it could be rooted sometime later then thats fine. Will pick up one this weekend.
Am going to be jealous though as I guess it's a step up from my 'old' M8
Sent from my HTC One_M8 dual sim using XDA-Developers mobile app
I unlock bootloader and root my PIxel 4 XL by Magisk . Can i relock and unroot my phone to original ?
truongcoi85 said:
I unlock bootloader and root my PIxel 4 XL by Magisk . Can i relock and unroot my phone to original ?
Click to expand...
Click to collapse
Yes
1) uninstall magisk
2) flash factory image (with or without wipe)
3) lock bootloader (this will wipe the phone)
prgopala said:
Yes
1) uninstall magisk
2) flash factory image (with or without wipe)
3) lock bootloader (this will wipe the phone)
Click to expand...
Click to collapse
Thanks you <3
truongcoi85 said:
Thanks you <3
Click to expand...
Click to collapse
Personnaly (and tested) I would prefer the OTA sideload method before relocking bootloader, this may avoid bootloop or start screen stuck.
dd66 said:
Personnaly (and tested) I would prefer the OTA sideload method before relocking bootloader, this may avoid bootloop or start screen stuck.
Click to expand...
Click to collapse
Can you give specific instructions? Does rooting cause a loss of battery life?
truongcoi85 said:
Can you give specific instructions? Does rooting cause a loss of battery life?
Click to expand...
Click to collapse
Specific instructions may be found on Google developer site, quite easy.
Regarding the battery loss, no, it won't interfere. More, I have a custom kernel (EX) which preserve it significantly.
Just a personal preference maybe but... I would say flashing the full factory image WITH wipe still enabled is your safest route. Also DO NOT toggle off the "OEM Unlocking" switch until you are super sure all is back to the should and booting properly! There is actually no reason to ever toggle that switch back off in my opinion.
If the relocking process wipes the phone (I've never done it myself), then there is zero benefit to flashing the factory image without having it do a full factory image. You need to backup your data in either case (if you have anything you want to keep). Having the phone do a full factory reset is the best way to ensure everything is back to normal prior to relocking the phone.
sic0048 said:
If the relocking process wipes the phone (I've never done it myself), then there is zero benefit to flashing the factory image without having it do a full factory image. You need to backup your data in either case (if you have anything you want to keep). Having the phone do a full factory reset is the best way to ensure everything is back to normal prior to relocking the phone.
Click to expand...
Click to collapse
Perfect follow-up to my post. You did a better job articulating the risk avoidance aspect. Lol
Better yet... Flash full October image and then take Nov ota before locking.
Sorry for the late reply to this thread, but I just went through this with my Pixel 4XL. I did a complete uninstall of Magisk and rebooted. I then went to the Google Pixel image page and used the flash feature for the latest version. I selected the option to wipe, restore partitions and lock the bootloader. It all seemed to go well until I booted the phone and ran through the setup pages and it prompted me to re-download my T-Mobile eSIM. I went into settings and deleted the eSIM and then did another factory reset on the phone just to be sure.
I have a question what happened to my eSIM if I unroot and flash the stock images? Can I use same eSIM QR Code or I have to get new QR code from my carrier. I'm using it on Middle East.
Totally stock pixel 5. Tried to sideload 12, and due to crappy instructions on XDA, that failed to mention the need to do the OEM unlock step, I ended up with a ADB sideload flash that failed at 94% and resulted in a empty A partition and a phone that failed to boot, so it switched to the backup system partition.
I'm now booted on the B partition (Android 11).
How can I fix my phone, so it's got 2 good system partitions?
Enable OEM unlocking, unlock bootloader, then use the Android Flash Tool to flash 12 Beta 5. Wiping /data shouldn't be necessary; however, if this fails and you have to force flash all partitions, a /data wipe will be required.
I highly recommend you keep the bootloader unlocked while using beta firmware, because it makes it a LOT easier to downgrade back to production firmware.
If you intend to root, don't forget to disable dm-verity and vbmeta-verification.
Detailed instructions on using the Android Flash Tool
Tip: When you get to the step of selecting which build to flash to your device, click the pencil icon to change options. Make sure you leave Relock Bootloader unchecked,
V0latyle said:
Wiping /data shouldn't be necessary
Click to expand...
Click to collapse
But unlocking the bootloader will wipe the phone.....
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
xunholyx said:
But unlocking the bootloader will wipe the phone.....
Click to expand...
Click to collapse
Correct, but it's still necessary to install the beta (and downgrade)
xunholyx said:
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
Click to expand...
Click to collapse
There is indeed. It's actually quite comprehensive.
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Chr1stOnABike said:
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Click to expand...
Click to collapse
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work. Requires unlocked bootloader
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
V0latyle said:
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work.
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
Click to expand...
Click to collapse
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Chr1stOnABike said:
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
Click to expand...
Click to collapse
Ah. Well, you can fix this, but it will require unlocking the bootloader.
You can always relock it after you're done.
Chr1stOnABike said:
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Click to expand...
Click to collapse
Don't know. Given that you can't boot into recovery, you can't sideload the OTA to test this theory. I personally doubt it. You can either wait and see, or you can just bite the bullet and fix the issue.
Chr1stOnABike said:
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Click to expand...
Click to collapse
Link to the post? You may not be the only one, but the majority of folks (including myself, I was in the Marine Corps for 9 years so you can guess my mental acuity) have been able to use the instructions to our success.
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Chr1stOnABike said:
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
Click to expand...
Click to collapse
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
Chr1stOnABike said:
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Click to expand...
Click to collapse
I have updated my phone using both of these methods and can personally confirm the instructions are correct. The only difference I would point out is that I'm comfortable enough using adb and fastboot commands that I manually type them and don't use the batch file.
It is your responsibility to understand the instructions and follow them. You flash and modify your device at your own risk. If you do not fully understand the instructions, it is also your responsibility to either find the details you need, or ask for help.
This may seem rather condescending or apathetic, but the situation is this:
- You tried to run experimental beta firmware on your device despite your concerns for the warranty
- You did not ask questions before doing so, and if you did read any of the multiple threads on this issue, you would have been acutely aware of the recommendation to unlock your bootloader before you proceed
- You are now left with few options to fix your device because you decided to ignore experienced advice and do things your own way
As I stated previously, the responsibility for fixing things is yours and yours alone. If you were that concerned with your warranty, you should have kept your phone completely stock and avoided installing the beta.
I have one last recommendation for you:
Disenroll from the beta program and wait for the OTA to take you back to A11 public release. A data wipe will be required.
You have been told in detail what you can do to fix your device. What you do now is completely up to you.
V0latyle said:
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
I have updated my phone using both of these methods and can personally confirm the instructions are correct. .
Click to expand...
Click to collapse
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
Click to expand...
Click to collapse
Yes - I unlocked and rooted my phone the day I got it, and I bought it full price direct from Google. Your point?
Chr1stOnABike said:
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
Click to expand...
Click to collapse
Yes, it's always worked for me. I've been trying to work with you here and give you options that do not require OEM Unlock or unlocking the bootloader. The reason I thought the Android Flash Tool might work is because it's literally a tool provided by Google, and though it uses ADB, I figured they might have some sort of security to allow recovery of locked phones.
What exactly is it you don't think I understand? As I've pointed out, you decided to install beta software on your device despite your concerns for warranty. As I ALSO pointed out, if warranty was that much of a concern for you, you should have stayed on stock public release firmware and not messed with anything at all.
I will admit that the guide you linked does not mention needing an unlocked bootloader. I think it's generally been assumed among us in the community that modifying your device requires an unlocked bootloader. I will talk to the mods and see if we can get a note added to the post. However, you seemed to miss the big warning that advises against using the beta on your daily driver.
Chr1stOnABike said:
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
Again, how so? If you're going to call me ignorant, you had better explain how.
OEM Unlock simply sets a flag: "unlock-ability" to 1. It's an on/off switch that corresponds to the 1 or 0 set for the "unlock-ability" flag. It has no other function.
When someone attempts to unlock the bootloader, the device checks that flag. If it's 0, the bootloader cannot be unlocked. If it's 1, it can.
Unlocking the bootloader disables security features that prevent you from flashing partitions on your phone, or booting images sent via ADB. The reason why this is important when running custom or experimental firmware is because it allows the user to reflash corrupted partitions (like in your case). It allows a lot more freedom over what you can do with your phone.
I've been doing this for years - more than 10 years in fact. I would be careful about making accusations like "you don't understand the difference" or "you don't know what you're talking about'" to someone who is trying to help you. I understand you're frustrated, but you're going to have to swallow your pride here and admit, at least to yourself, that you screwed up. It seems pretty clear to me that you either did not fully understand the risk of trying to modify your device with a locked bootloader (yes, installing the beta counts as a modification), or you ignored the risk and tried to do it anyway. Yet you come here and impugn my credibility? As they say, "check yourself before you wreck yourself". You screwed up and got yourself into this mess. You alone are to blame. No one has to help you, and believe me, I've been quite tempted to tell you to pound sand. The least you can do is show a little gratitude for someone who's trying to help, and respect for experience and knowledge far beyond your own.
I have one more option for you: Rescue mode.
Reboot your phone into bootloader (hold power + volume down, release power but keep holding volume down when screen turns off)
Use volume buttons to select rescue mode on the right side, then press power to select
Google Pixel Repair Tool
This probably won't work because the repair tool only works if the firmware on your phone is older or equivalent to the firmware the repair tool has.
Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
I haven't had time to read much of this thread yet, but why insult the one person I see who's trying to help you?
I've seen this before and other users who may know what to do, usually just walk away as they don't want to help someone who may just insult them or are clearly unappreciative of the help given.
Everyone let's all keep it civilized.
If you have issue with a post, please hit report button and walk away.
Positive vibes, all.
--andybones
@Chr1stOnABike I am indeed trying to help you, as I understand your situation is frustrating. I also understand that it may be frustrating to be told to do what you didn't want to do in the first place, but the reason why I'm telling you to do it is because it'll be of the most help to you.
Losing your data sucks. I get it. But fortunately the Pixel 5 is great about backing everything up to your Google account. Just make sure your photos are backed up and you'll be fine. Setting it back up after a wipe is a pain in the ass, but again, I'm recommending the bootloader unlock because I believe it's your best chance at recovery.
As far as that goes, I'm still trying to be flexible and provide you with different options. Be aware that if these other options don't work, you have no other choice. I'm not saying that to be rude, that's just the reality of it.
And lastly, I would very much appreciate you making the distinction between thinking I'm wrong because you have evidence to the contrary, vs thinking I'm wrong simply because you don't like my recommendations. If you sincerely believe I'm incorrect and can demonstrate how, please feel free to do so.
My only objective here is to help people the best I can with the knowledge and experience I have.
For those who ever get stuck like I did. When I got stuck in a bootloop, I realized I could 'fastboot boot twrp.img' and was able to save my internal storage from being lost by backing up to PC with TWRP, then move it back onto internal after the factory reset. Did I lost app data in these cases, yes. But that's my own fault for not regularly backup app data up with something like Swift or AppDash.
@Chr1stOnABike just checking in to see if you were able to get your problem resolved?
i just want to say, i used my device for long, i dont wanna wipe my data but i want to root it. is that possible?
THX in advance
If your bootloader isn't unlocked then doing so will wipe data. If it is unlocked you can use the latest version of Magisk. Following this guide:
Magisk Root without custom Recovery and without losing Encryption
So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption. For that reason I didn't root my phone but there is a way around...
forum.xda-developers.com
Obviously you will need the correct boot.img file relevant to your specific Redmi Note 10s device extracted from an official rom.
You'll also need to enable usb debugging in the hidden developer options and configure ADB properly on your computer.
If you don't use the correct rom for your device it will get stuck in a bootloop, or just won't boot at all, requiring a hard reset and loss of all data.
There are guides for all these things on the XDA forums.
If you haven't heard of these things before, this is your main phone, or you aren't confident in your abilities then I don't recommend doing it, but it's your choice just don't blame others if something goes wrong.
stuntdouble said:
You can use the latest version of Magisk. Following this guide:
Magisk Root without custom Recovery and without losing Encryption
So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption. For that reason I didn't root my phone but there is a way around...
forum.xda-developers.com
Obviously you will need the correct boot.img file relevant to your specific Redmi Note 10s device extracted from an official rom.
You'll also need to enable usb debugging in the hidden developer options and configure ADB properly on your computer.
If you don't use the correct rom for your device it will get stuck in a bootloop, or just won't boot at all, requiring a hard reset and loss of all data.
There are guides for all these things on the XDA forums.
If you haven't heard of these things before, this is your main phone, or you aren't confident in your abilities then I don't recommend doing it, but it's your choice just don't blame others if something goes wrong.
Click to expand...
Click to collapse
okay! i think i dont wanna root it then if you give advice to not do so
Sorry I missed out the part about the bootloader which is important and edited the post above so please re-read.
Yeah if unsure then just don't do it as you could end up losing everything very easily.
KerbMario said:
i just want to say, i used my device for long, i dont wanna wipe my data but i want to root it. is that possible?
THX in advance
Click to expand...
Click to collapse
technically there is a way to unlock the bootloader without losing data but magisk is kinda fuc*ed up on MIUI, and it can cause the phone to not boot
J6idot said:
technically there is a way to unlock the bootloader without losing data but magisk is kinda fuc*ed up on MIUI, and it can cause the phone to not boot
Click to expand...
Click to collapse
isnt unlocking bootloader an option in developer mode options?
KerbMario said:
isnt unlocking bootloader an option in developer mode options?
Click to expand...
Click to collapse
it's not as simple as that, you can register to unlock your bootloader by xiaomi from the dev options, but you still have to do the unlock though your pc with the miunlock program logged into your account. This takes 7 days to verify and the moment you do it it wipes your data.
This is the official way of unlocking your bootloader and being able to do with the device whatever you want.
There is an alternative unofficial way of doing it and that method claims to not delete data on your device, but I have no idea how well that method works since it seems to rely on some sort of workaround. here's a link to the post about that method, I just did mine the official way and copied my files back and redownloaded the apps.
[Rosemary] Instant Unlock Bootloader with no data wipe
Hi I want to share with you guys how to unlock Bootloader without waiting dan best of part is your data will no wiped I am not the programmer of this software, I just want to shares All credit goes to developer: Tapin Recovery Installer Here's...
forum.xda-developers.com
also if you do decide to unlock your bootloader one way or the other, I recommend the following Kernel if you want a less throttled gaming experience.
https://forum.xda-developers.com/t/shared-kernel-beta-genom-r-kernel.4342549/
Cryptonite26 said:
it's not as simple as that, you can register to unlock your bootloader by xiaomi from the dev options, but you still have to do the unlock though your pc with the miunlock program logged into your account. This takes 7 days to verify and the moment you do it it wipes your data.
This is the official way of unlocking your bootloader and being able to do with the device whatever you want.
There is an alternative unofficial way of doing it and that method claims to not delete data on your device, but I have no idea how well that method works since it seems to rely on some sort of workaround. here's a link to the post about that method, I just did mine the official way and copied my files back and redownloaded the apps.
[Rosemary] Instant Unlock Bootloader with no data wipe
Hi I want to share with you guys how to unlock Bootloader without waiting dan best of part is your data will no wiped I am not the programmer of this software, I just want to shares All credit goes to developer: Tapin Recovery Installer Here's...
forum.xda-developers.com
also if you do decide to unlock your bootloader one way or the other, I recommend the following Kernel if you want a less throttled gaming experience.
https://forum.xda-developers.com/t/shared-kernel-beta-genom-r-kernel.4342549/
Click to expand...
Click to collapse
+1 this works
Yes its possible to not wipe data or lose it during the process at this point in time.
Just this past week (I'm new to redmi phones ) did the same process for the note 10s and note 9.
The issue with bootloader unLocking (which normally means a data wipe) is negated with mtkclient.
A Data backup is just a good standard practice but understanding the procedures posted before and following them correctly should give no issue.
You can root it by using termux too.
To root an Android phone using Termux, follow these steps:
Install Termux app from the Google Play Store
Open Termux and run pkg install git to install Git
Run git clone https://github.com/Magisk-Modules-Repo/termux-root.git to clone the root repository
Change directory with cd termux-root
Run sh install.sh to install the root tool
Restart the phone and the phone should be rooted.
Note: Rooting a phone voids its warranty and can potentially harm the device if not done carefully. Proceed at your own risk.