Related
Is there any work being done for a temporary Root option? I ask because it seems that I only need Root for certain issues!
Scenario: Access my hosts file, Tor...etc!
TIA
What is the benefit to only being rooted temporarily? Honestly there isn't a huge security benefit to it, and usability suffers because you have to root it when you want to do anything in your scenarios.
Why not just use SuperUser.apk and not have it remember any associations? That way you only authorize root privileges when you need them, but can stay rooted.
Temp rooting shouldn't even be released for this since we have a permroot so either root your xoom and leave it that way or stay stock
I wouldn't mind a temp root because I haven't rooted from the start, waiting for the 4G upgrade, and because fastboot oem unlock requires a wipe, I don't want to do it, then restore, then do it again. A temp root would be perfect.
I actually have to second Archon810's post. I also would like a temp-root solution so that I could backup my Xoom BEFORE fastboot oem unlock, due to the wipe. I moved all my games off my G2, and started playing further on the tablet screen. However, now I'm gonna lose all those save games. Kinda sucks...
flamingblue8z said:
I actually have to second Archon810's post. I also would like a temp-root solution so that I could backup my Xoom BEFORE fastboot oem unlock, due to the wipe. I moved all my games off my G2, and started playing further on the tablet screen. However, now I'm gonna lose all those save games. Kinda sucks...
Click to expand...
Click to collapse
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Not getting what the issue is here either. With superuser you have full control over what app has root access and which not. Root access can be granted and revoked at any time. So certain "things" can have root access, certain not...
cwizardtx said:
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Click to expand...
Click to collapse
I believe people want something like the "temp" root achieved for Sensation: http://forum.xda-developers.com/showpost.php?p=15260896&postcount=1; it works quite well for me (no unlock required, one can disable unwanted apps, Titanium works).
"Temporary", since after rebooting updated parts of a locked NAND are overwritten and the changes lost.
This would be useful if you wanted to watch movies from the Market but still wanted to use other things that required root access. Reboot clean, watch movies, run root app, make backups.
My wife's MyTouch 3G Slide had a temporary root app that she only needed when she needed to use the phone as a WiFi Hotspot.
JohannFaust said:
I believe people want something like the "temp" root achieved for Sensation: http://forum.xda-developers.com/showpost.php?p=15260896&postcount=1; it works quite well for me (no unlock required, one can disable unwanted apps, Titanium works).
"Temporary", since after rebooting updated parts of a locked NAND are overwritten and the changes lost.
Click to expand...
Click to collapse
The only reason this is out, is because they don't have real root. And yes you can disable apps...but they are still there.
Sent from my PG86100
I still think a temp root solution would have been nice. Because I just rooted (which is less root, more NAND unlock) so I could upgrade to 3.2 and have full root functionality from MyBackup Pro. Some stability issues, but I will try reflashing in a bit. Would have really been nice to back everything up first, though.
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
playya said:
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is also why the first thing you should do is fastboot oem unlock. You haven't rooted and all apps will still work. But if you decide to root later, you will not loose anything.
playya said:
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
No no, I have my apps already backed up by MyBackup Pro. Its my APP DATA, the save games n'at, that I was trying to back up. Its a moot point now, for me, since I already bit the bullet and rooted, but it would have been valuable to others.
bwcorvus said:
The only reason this is out, is because they don't have real root. And yes you can disable apps...but they are still there.
Sent from my PG86100
Click to expand...
Click to collapse
Not true at all. The Droid X could get permanent OR Temp Root from Z4root, as could MANY phones on froyo. It could Temp root 99% of phones on froyo or earlier according to the developer and the numerous people chiming in that it worked for htem. Some things i just want temp root, so i can backup or access some file. Otherwise, i don't need root full time on this tablet, didn't need it full time either on my Galaxy tab, which i also could Temp root with Z4Root. And did numerous times with ease and no problems
Some of us don't need permanent root. Why is that so hard to understand. I have full root on my X, don't need that on my tablet. Biggest reason is for what was listed, don't want ot have to wipe the whole device. That is just overkill and silly to me. If you want root with a Xoom you realy need to do it from day 1 so you lose nothing.
cwizardtx said:
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Click to expand...
Click to collapse
No offense but by saying that you don't know how linux works... If you are on the command line in Linux and type SU or SUDO plus a command after it you gain TEMPORARY ROOT for that command once you put in the password. It is TEMP, after that command passes you are normal user again. Yes you can root yourself full time, but that is a silly thing to do on a linux system and removes a lot of security. Not hard to plug in a password the few times you need to access stuff or edit things
Legato Bluesummers; said:
don't want ot have to wipe the whole device. That is just overkill and silly to me.
Click to expand...
Click to collapse
that's my point, if I can root my HTC EVO without wiping why should I have to do that with my xoom?
Guys
Mybackup Root Androidcommander Titanium Backup can all put your rom back to where it was in minutes. It takes longer to.read why you don't want to root than it would take to restore IMO. Don't root of you don't want to but really do t use the my programs line..
No disrespect though just think with what we have today restoring is not that not big of a deal and after you root clockwork and nandroids are your best friends
Sent from my EVO rocking Evervolv Gingerbread
IceCreaMan said:
that's my point, if I can root my HTC EVO without wiping why should I have to do that with my xoom?
Click to expand...
Click to collapse
Yup thats holding me back, too. Unlike my phones (Hero and Desire) I have not rooted my Xoom on the first day just because I was unsure if I would keep it. Now I am stuck in this mess while one side of me wants to root and install 3.2 and the other side doesn't want to lose all the progress made in the apps/games/whatever...
I wasn't going to root my phone but this "its on" app is killing half my battery now, so I guess its time. Can someone point in in the right direction for a tutorial that can root after the 4.4.4 update? also, does anyone know if there's a way to root without erasing the phone? I don't want to reinstall everything, I really just want to get rid of the its on app. Its unbelievable that sprint hasn't fixed this in over a month.
The method to root is the same as it is with previous Android versions on this device. Unlocking your bootloader factory resets the device, but you can connect your phone to your PC and backup whatever you need to beforehand. HTC backup also works great for backing up apps, ringtones, etc. I've used it in the past and it works quite well. As far as the ItsOn garbage, you'll need to flash a ROM that removes it from the device, as it's not simply an app that you can delete.
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
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 am going to install Arrow os with microg. I am confused if I should root. Would love to hear your suggestion and why!
Do not quote me on this, but apparently unlocking the bootloader on your Redmi phone does not void your warranty. Your warranty is void only if your phone is damaged due to you tampering with it. So, manufacturing defects must be covered. This was my main concern
Another potential problem is that custom roms don't com with Widevine L1 support. This means that you can only stream SD videos instead of HD on streaming services like Netflix and Primevideo (youtube should be fine). If you are fine with this you could go ahead and root it.
BUT BE VERY CAREFUL
Ujwal2000 said:
Do not quote me on this, but apparently unlocking the bootloader on your Redmi phone does not void your warranty. Your warranty is void only if your phone is damaged due to you tampering with it. So, manufacturing defects must be covered. This was my main concern
Another potential problem is that custom roms don't com with Widevine L1 support. This means that you can only stream SD videos instead of HD on streaming services like Netflix and Primevideo (youtube should be fine). If you are fine with this you could go ahead and root it.
BUT BE VERY CAREFUL
Click to expand...
Click to collapse
I don't care about warranty. Warranty is void if you install a custom rom anyways.
Roms DO come with L1 support and arrow os comes with it too.
My question was whether should I root, meaning are there features/apps/modules ill be missing out or should I not root as there are alternatives or they pose security risk, and not about if I should flash a custom rom.
The main reason to unlock a Redmi phone phone would be to remove the annoying ads completely and use stock android. Personally I hate MIUI.
I don't use many apps or modules that need root. I mainly use YouTube Vanced. It works without root, but you can't ask the assistant to play music.
Some apps don't work with an unlocked bootloader, so you might need to root it
Again, I am talking about magisk, not custom rom. And you are wrong again. The MAIN reason to unlock bootloader is to get rid of that piece of crap rom. And you are wrong about the apps not working too. If you don't have enough knowledge, it's okay to just read the conversation, and not give advice. You are doing more harm than good.
The question is - what do you want to gain from rooting?
There are a bunch of advantages that come with rooting. Off the top of my head - Ad blocking without any VPN business (read: adaway), better equalizer (viper), tracker blocking with no VPN (warden), serial ROM hopping (need to backup with stuff like ObackupsX)
This is IMO the normal use cases for rooting. If you had more/ bigger demands, you wouldn't be asking this question in the first place.
Now for the downsides of rooting - its a bit of a cat and mouse game with safety net (especially with the 'new plan' of hardware attestation and whether topjohnwu can continue to support magisk) and risk of breaking apps like banking apps or games like pubg, fortnite, Netflix etc.
Also you won't be able to relock your bootloader
Much of the " normal " use cases can be done with some adb magic.
In essence there is a lot to gain via rooting if you know what you want. And you must be prepared to do some homework for it
For me it is important to always have an unlocked bootloader. Everything else (install recovery, install root, install other ROM) is not important and can be done at a later time.
You need unlocked bootloader to:
- Do NANDROID backup (temporarily boot TWRP and do backup/restore)
- Access data you can't see with locked bootloader (eg WIFI passwords, or app data)
- Install root to do Titanium backup/restore of single apps
The main problem is, if you do not unlock and you need some of these functions, you need to erase all data on your device to access the data which is now deleted. If the bootloader already is unlocked, you are fine. You can do everything else later when it is needed, because no data loss is involved anymore.