Related
Hi all!!!
I'm considering to buy the Moto X, I have a couple if questions though:
If I unlock the bootloader through Motorola, does root become easier (I realize that it isn't simple otherwise)
Is the bootloader relockable?
If I unlock a brand new phone, I won't lose anything, correct? You only lose what you install other than stock, is that correct?
Thanx all in advance...
shaya4207 said:
Hi all!!!
I'm considering to buy the Moto X, I have a couple if questions though:
If I unlock the bootloader through Motorola, does root become easier (I realize that it isn't simple otherwise)
Is the bootloader relockable?
If I unlock a brand new phone, I won't lose anything, correct? You only lose what you install other than stock, is that correct?
Thanx all in advance...
Click to expand...
Click to collapse
1. Yes if you unlock all you have to do is flash a custom recovery and supersu. Pwnmymoto is pretty easy too, though.
2. Yes but I don't think that will give you back your warranty
3. Unlocking will basically do a factory reset in the device. So if it's brand new and you haven't used it yet you won't lose anything. But if it's already set up and being used be sure to save anything important before you unlock.
Sent from my HTC One mini
Thanx!!! Isn't there an issue with PwnMyMoto with the camera update? Also it's safe to assume that once rooted WiFi tethering (like with FoxFi) will work, correct?
shaya4207 said:
Thanx!!! Isn't there an issue with PwnMyMoto with the camera update? Also it's safe to assume that once rooted WiFi tethering (like with FoxFi) will work, correct?
Click to expand...
Click to collapse
i would suggest replying to someone if you want them to respond to you otherwise it won't show up in their notifications if they aren't subscribed to the thread.
PwnMyMoto didn't screw up the camera update. It was built for the android OS that came stock on the phone. Maintaining root through the OTA/ camera update is difficult currently. But that is partly because all of the info on the updates haven't been released yet. As time goes on and things develop and those smarter than me decide to get things done we should be able to maintain root through the update and future updates with no problems. Also, safestrap was recently released and is working through bugs but it will be fully functional soon and we will be able to use roms through them and not take the updates.
wifi tethering only matters on vza at least if you have unlimited data. Otherwise, they don't charge to wifi tether anymore. you just can't go above your data limit. But yes, rooting allow those 3rd party tethering apps to work. They may even work without root actually. But with root you can change the stock tethering app and keep your carrier from knowing you are tethering.
@jayboyyyy Thanx!!!
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!
Hi, long time lurker here. I want to start by saying how great and informative this site is. Anyway, my nexus 6 came in from the mail like 5 hours ago, did all the updates from 5.0 to 6.0 and it's now running Marshmallow mra58n. Question is should I root it immediately and if so, are there any guides I can follow? Much love to you all, I'm not exactly pro at this kind of things but I can follow instructions since I have competently rooted my past phones which were an HTC M7, M8 and a Samsung Galaxy Note 10.1 tablet.
Thank you.
Edit: Phone is also unlocked, I currently have no SIM card
start here..
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've been looking at the Nexus Root Toolkit since I am kind of confused on how to proceed with anything at all, is that ill advised since I've read that there are problems with the USB cable disconnecting during reboot?
Also, thank you for the reply.
I used the NRT without issue. Just follow the guide step by step.
Sent from my Nexus 6 using Tapatalk
and, dont touch the usb cable while the phone is processing your commands!
j/k, never even heard of the USB cable "problem"
I just used the toolkit today to unlock and root my N6.
Sent from my Nexus 6 using Tapatalk
I rooted last night initially using manual method described in the first link provided, however after some driver issues ultimately used the 2.1.0 rootkit to uninstall and reinstall all drivers. That too alone saved me tons of time and either method is simple if you can follow instructions.
Totally recommend rooting and then experimenting with custom roms, its like getting a new phone everyone you install a new rom.
Have fun!
Kristine,
In answer specifically to your question "Should I...?" my answer is "No". It really depends on what you think you'll get from it - why do you want to do it? What specific benefits do you want?
The reason that I say "no" is that I've been rooted on all my several phones for years, and I've decided that for me the annoyance of having to manually flash ROMs outweighs the benefits - particularly now that Google are releasing frequent security updates. The moment you root your device the OTA (over the air) updates no longer work.
For me the major reason for rooting was to have a firewall. The other things (wakelock detection, double tap to wake, auto-hibernation...) were great but not showstoppers. Now that there is a non-root firewall (Netguard) I'm happy to leave my phone unrooted. I haven't had an OTA to apply yet, so if I have any problems then I might change my mind, but my advice would be to think hard about why you want root before you buy yourself into a world of tinkering...
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Dammit, are you kidding me? I just downloaded and setup everything, figured I'd do all everything else tomorrow... Oh, well I can do it again I suppose.
Kristine-N said:
Question is should I root it immediately....
Click to expand...
Click to collapse
Because I don't want a white interface, rooting is necessary. Google forces to many things, like forced encryption, useless apps and a white interface (battery drain). When rooting was impossible I would not have bought a Nexus.
Short answer: No!
Long answer: Well, it's sill no, but you can or even should do a couple of things.
First if all, allow OEM Unlocking in development settings. There are gazillion how-tos to switch developer mode on, and tick that switch. Google has borked OTAs already, and if your phone doesn't boot, and the switch is off, then you're boned, you can send it for repair. But if you can unlock you bootloader, then you can flash a custom recovery and make your phone working again.
Second, if you do plan to root your phone in the near future, you should unlock the bootloader now, while it's still new, because it will erase everything (IMHO this would be sufficient as a security measure, the Enable OEM Unlocking is overkill).
As for the main question if you don't have any specific ideas what you want the root for, then don't root your phone. It's a clear and present security risk, and you're just one too many "Allow" taps from letting someone acquire your passwords, clone your IMEI, and download your personal stuff. My motto is, if you don't know what exactly root is, what it does, then you don't know how to prevent exploits that need it to run.
Also if you modify your phone in any way, and that includes rooting, you won't receive the monthly OTAs, and will have to flash it manually.
And finally, don't use toolkits on a Nexus. Spend another hour reading about the matter and you will find out typing adb and fastboot commands is a easy as clicking buttons on toolkits. There is nothing extra in them, they just download the images to flash, and "type" these commands for you.
Unlock bootloader and don't root it for now. After some time, if you feel like you're missing some features that you can obtain only with root, then go ahead. But for now I would strongly recommend to stay stock and see how it goes...
I'm not sure where the appropriate place for this would be, and I apologize in advance if this isn't it, but I need some assistance.
For starters, I'm an absolute n00b when it comes to anything root and I don't understand the language and procedures to it, only how to do it by following instructions. Hence why I'm currently on a 4.4 untethered root.
I'm due for an upgrade this month and am torn between getting a later device with Lollipop or a newer device with Marshmallow. The deciding point is if there's any kind of walkthrough on rooting Marshmallow, preferably a dumbed-down version for nondevs like myself.
I know there's currently an experimental one provided by Chainfire, and I skimmed through it but couldn't really understand it.
So any assistance would be greatly appreciated.
@Chainfire If you could weigh in, that would be very helpful.
What are you on about untethered root this isn't IOS. Also it's just two simple steps:
Get a recovery for your device (TWRP preferably)
Use either the stable zip from this forum or beta zip thosent matter and transfer it to your device.
Flash it in the recovery done you're rooted
@Xmaster24 I appreciate the response. I was losing hope on getting an answer as I had already gone with the newer device for my upgrade.
In jcase's pie thread for the 2013 Motorola line, that's what the 4.4 root was referred to as. Wasn't confusing Android with iOS.
And I apologize for being so n00bish, but how would I go about getting TWRP recovery? I do know how to flash the zip from there as I used Safestrap on my current device (but I already needed root access for it to work).
Kodalades said:
@Xmaster24 I appreciate the response. I was losing hope on getting an answer as I had already gone with the newer device for my upgrade.
In jcases's pie thread for the 2013 Motorola line, that's what the 4.4 root was referred to as. Wasn't confusing Android with iOS.
And I apologize for being so n00bish, but how would I go about getting TWRP recovery? I do know how to flash the zip from there as I used Safestrap on my current device (but I already needed root access for it to work).
Click to expand...
Click to collapse
Depends on your device just tell me what it is and I can send you some info. Safestrap seems to be dead for at least a year thosent sound very safe lol.
Xmaster24 said:
Depends on your device just tell me what it is and I can send you some info. Safestrap seems to be dead for at least a year thosent sound very safe lol.
Click to expand...
Click to collapse
I'm getting the Samsung Galaxy S7 Edge. Considering it's not out in the US yet (I have it on preorder), I'm not sure if you'd be able to tell me anything at the moment.
Kodalades said:
I'm getting the Samsung Galaxy S7 Edge. Considering it's not out in the US yet (I have it on preorder), I'm not sure if you'd be able to tell me anything at the moment.
Click to expand...
Click to collapse
Oh dear yes it has just been released probably no rooting info available for quite some time considering samsungs stance on root and open software. Maybe check again in a few weeks or months
Xmaster24 said:
Oh dear yes it has just been released probably no rooting info available for quite some time considering samsungs stance on root and open software. Maybe check again in a few weeks or months
Click to expand...
Click to collapse
Bummer. Kinda expected something along those lines though so I'm not surprised.
Would getting TWRP or some other kind of recovery still be possible at the very least?
Kodalades said:
Bummer. Kinda expected something along those lines though so I'm not surprised.
Would getting TWRP or some other kind of recovery still be possible at the very least?
Click to expand...
Click to collapse
Flash fire could work but it requires root already. Doubt there are any easy exploits on a flagship just released phone
Xmaster24 said:
Flash fire could work but it requires root already. Doubt there are any easy exploits on a flagship just released phone
Click to expand...
Click to collapse
Makes sense. I really appreciate the help. If you happen to learn of anything more, please let me know.
Kodalades said:
Makes sense. I really appreciate the help. If you happen to learn of anything more, please let me know.
Click to expand...
Click to collapse
Guess not kingo root seems to be working :http://www.xda-developers.com/galaxy-s7-root/
Hi guys, I'm pretty new to xda community, so I don't know if my issue is solved before or not but I can't find any.
As u know, when u use an app to lock the phone screen, u can't unlock it the next time with fingerprint. Is there any way, root or no root required to make it possible? And if it's root required, could u plz tell me how to do it or give me any tutorial on it?
Thanks in advance.
nokia8user said:
Hi guys...
Click to expand...
Click to collapse
Well firstly, if no else has said so, welcome to XDA ?
Firstly, what your looking to do is definitely possible. But as you likely suspected, you will require root for it to work properly.
Once you have root access, you will just need to make sure that the app your using to lock the phone has the option to utilise root access to work.
Nova launcher for example allows you to choose root as the method of locking the phone.
As for actually rooting your phone, you will first need to unlock your phones bootloader, which although there is an official method for now, still comes with serious and permanent consequences.
I believe there are guides on how to unlock the bootloader and how to subsequently gain root and/or install TWRP, here in the Nokia 8 forums which I am sure you will be able to find yourself (rather then me redundantly providing you instructions here)
However, as a friendly warning to you (and any other users new to the forums who read this later) due to the consequences and implications of unlocking the bootloader (i.e. impact on device security, receiving OTA updates etc.) you should only proceed if:
- You 100% understand the steps involved (rather than blindly following them)
- You truely understand what they are actually doing to your device
- You are 100% aware the consequences
- You know how to, and are prepared to, recover your device if something does go wrong.
In the end, most of the issues I've seen on XDA over the years are the result of people not truely understanding what they were doing. You can never know too much.
Hopefully this answered your question?
ajgftw said:
Well firstly, if no else has said so, welcome to XDA ?
...
Hopefully this answered your question?
Click to expand...
Click to collapse
Oh god, you are so nice. I will absolutely try to follow the steps u mentioned above. Thanks so much.