Related
Hey!
I recently bought a second hand Nexus in decent shape.
Im really a newbie when it comes to roms, rooting, bootloader etc and Im not really interested in it either!
So what I did when I got the handset was to google around for how to restore it to factory edition. (The other guy seamed to have used other Roms and such)
I found a tool by Wugfresh called Nexus root toolkit and used it to lock bootloader, restore factory image (I downloaded myself from google) and unroot the phone.
Now I have some questions! Is the tool safe? Since Im a complete noob I have no way of telling if the rom etc is legit, could there be spyware or such on my phone now?
Since Kitkat is comming OTA soon, would that be a good way to check if the phone is "original"? I mean, if i get OTA 4.4 from google, will that make sure my handset is completly as it was out of the box, and nothing hidden can be there?
This is a screenshot from my "About phone" maybe you can verify that this is correct?
https://www.dropbox.com/s/17b4i9wi1wypsgl/Screenshot_2013-11-14-13-04-53.png
Very thankful for your help!
I found a tool by Wugfresh called Nexus root toolkit
Now I have some questions! Is the tool safe?!
Click to expand...
Click to collapse
Why don't you ask him personally?
Toolkit being safe or not depends on who you ask. It could cause problems and sometimes it's better to learn to flash the device manually. For some its better to use toolkit since they can potentially cause more problems doing something wrong manually. If you want to flash the factory firmware manually, the instructions are in these steps: http://forum.xda-developers.com/showthread.php?t=2010312
Since Im a complete noob I have no way of telling if the rom etc is legit, could there be spyware or such on my phone now?
Click to expand...
Click to collapse
If you install the factory image from here https://developers.google.com/android/nexus/images, then its the official Google firmware. However, these OTA packages are original as well: http://forum.xda-developers.com/showthread.php?t=2145848. To tell if other third party custom roms are safe, I don't program myself, but reliable ones are open source and have the sources available to the public that you can use to compile yourself. You can use hash checking to make sure if a file is original, Google gives you the hash values for their downloads.
This is a screenshot from my "About phone" maybe you can verify that this is correct?
https://www.dropbox.com/s/17b4i9wi1wypsgl/Screenshot_2013-11-14-13-04-53.png
Click to expand...
Click to collapse
The screenshot shows you are running stock Android 4.3 with stock kernel. However a device need to run an "odexed version of the stock rom" and stock recovery too to receive updates. If the toolkit installed the factory firmware for you, then you have everythig stock and is good to go to receive the updates.
Since Kitkat is comming OTA soon, would that be a good way to check if the phone is "original"? I mean, if i get OTA 4.4 from google, will that make sure my handset is completly as it was out of the box, and nothing hidden can be there?
Click to expand...
Click to collapse
No, a better way would be to flash the factory firmware of 4.4 when it become available, which would wipe everything in the process. It's always possible for phones to have spywares if you know how to exploit it, no software are impenetrable. For example, the seller could have installed a virus that stay in your system that lives through factory resets and use it to tell your exact location, phone information, record audio or take pictures of you. I use this myself, see: Cerberus (Nothing as drastic compared to what Google or Apple does however.) However, if you have flashed the factory image then it would wipe out programs like Cerberus.
But before being too worried about malwares, I suggest reading this article on Android malware: http://www.androidpolice.com/2013/1...at-001-of-apps-evade-defenses-and-harm-users/. To stay safe, just make sure to download apps from the PlayStore. Android have the ability to sideload app, don't utilize it if you are concerned. Even if you do sideload, if the phone have Google services installed, the "Verify apps" feature will ask to scan it before installing.
For many technical reasons and depending on usages and scenarios I believe its much safer to root than being unroot, but this will lead to other discussions. (Root may be required to catch and prevent exploits or close security holes that affect unrooted devices. It's down to how you use it. Aside from the UAC checking, most people who use Windows computer runs it fully rooted without knowing.)
eksasol said:
Why don't you ask him personally?
Toolkit being safe or not depends on who you ask. It could cause problems and sometimes it's better to learn to flash the device manually. For some its better to use toolkit since they can potentially cause more problems doing something wrong manually. If you want to flash the factory firmware manually, the instructions are in these steps: http://forum.xda-developers.com/showthread.php?t=2010312
If you install the factory image from here https://developers.google.com/android/nexus/images, then its the official Google firmware. However, these OTA packages are original as well: http://forum.xda-developers.com/showthread.php?t=2145848. To tell if other third party custom roms are safe, I don't program myself, but reliable ones are open source and have the sources available to the public that you can use to compile yourself. You can use hash checking to make sure if a file is original, Google gives you the hash values for their downloads.
The screenshot shows you are running stock Android 4.3 with stock kernel. However a device need to run an "odexed version of the stock rom" and stock recovery too to receive updates. If the toolkit installed the factory firmware for you, then you have everythig stock and is good to go to receive the updates.
No, a better way would be to flash the factory firmware of 4.4 when it become available, which would wipe everything in the process. It's always possible for phones to have spywares if you know how to exploit it, no software are impenetrable. For example, the seller could have installed a virus that stay in your system that lives through factory resets and use it to tell your exact location, phone information, record audio or take pictures of you. I use this myself, see: Cerberus (Nothing as drastic compared to what Google or Apple does however.) However, if you have flashed the factory image then it would wipe out programs like Cerberus.
But before being too worried about malwares, I suggest reading this article on Android malware: http://www.androidpolice.com/2013/1...at-001-of-apps-evade-defenses-and-harm-users/. To stay safe, just make sure to download apps from the PlayStore. Android have the ability to sideload app, don't utilize it if you are concerned. Even if you do sideload, if the phone have Google services installed, the "Verify apps" feature will ask to scan it before installing.
For many technical reasons and depending on usages and scenarios I believe its much safer to root than being unroot, but this will lead to other discussions. (Root may be required to catch and prevent exploits or close security holes that affect unrooted devices. It's down to how you use it. Aside from the UAC checking, most people who use Windows computer runs it fulled rooted without knowing.)
Click to expand...
Click to collapse
Very much thanks for your post! Appriciated that you are taking time to reply.
When it comes to why I don't "ask him personally", well, if I myself developed a malicious software I would obviously not tell people it is?
When I write safe, by safe I mean free from harmful or hidden software, not safe as in bricking. I've already used the toolkit and flashed the factoryimage I downloaded myself from google, my concern was if the toolkit in some way could add harmful code when the firmware was flashed.
An "odexed version of the stock rom" is not enough to be sure the phone is fine if I interpret you correctly? Since you are saying that recieving OTA 4.4 is no guarantee that the rom, bootloader, recovery, etc is completly googlish? Guess I will consider to flash 4.4 manually then when it's out, ill be reading the thread. Thanks alot!
How do I tell if Im running stock recovery?
I've never installed anything from outside google play, and pretty much every app are from trusted sources with millions of downloads. Atleast if facebook and instagram are to be trusted
You need to understand this is XDA Developers, a community that share open source ideas, not a warez site, you've been a member for a while to know this. The community and moderators do their best to check uploads for harm, in the end of the day still your choice to use the toolkit or install something, and to do research on it (reading through the thread).
Since you are able to use the toolkit to install factory firmware, KitKat firmware image is already available, so I suggest you flash it instead of waiting for the OTA. Generally a clean install have less issues than OTA updates.
Looking at the current requirement for AP needing a locked bootloader now to function, and ARS dropping a new article on Rooting Android phones with Bitflips is now a thing, would there be any future possibility of getting Root on a Bootloader locked device?
I really wouldn't mind trying Stock Android on my 6P with the beta 7.1 builds, however the one thing I really don't want to do without, is Titanium Backup. I run too many apps that have no backup/cloud save function that TB really helps fill the gap in the complete lack of native Android Backup. (And saving my 100+ Chrome Tab sessions as well). Of course there is no guarantee we can even use AP with Root on a locked bootloader due to the checks they have been cooking into it over the past year, but I do wonder if with the change of the security of Android, will new ways to continue to have root be found even for our easily bootloader unlocked devices incase more apps start to look for bootloader unlocks as well in the near future.
I suppose the other side of the coin is to find how these apps look for the bootloaders locked/unlocked status and just block that, but outside of Chainfire's brilliance, who knows how easy/hard that task may be either.
Have you tried Helium? Some apps might not have backup capabilities though. Interesting read on that particular root method. I can assume only certain devices would work with that sort of exploit, depending how hard or easy it is to flip memory bits on the particular platform.
Also: http://www.xda-developers.com/sulta...otloader-check-on-latest-cm13-builds-for-op3/
This will be possible soon when the sources for the latest 7.1.1 kernel leak. Possible now using 6.0.1 and 7.0
There is Another one on ARS as well so it seems we may have options soon(tm).
Also I have tried Helium but it was next to useless for what I actually wanted to backup vs what it could. I'm going to dig around and see if there is any more manual method to backing up most of what I want.
What I see as a show stopper for me is the possibility to use TWRP
Other than that I would even be willing to give up adaway. For most parts I will probably find a workaround/other app to use.
Or do I need FlashFire?
I believe that this is the same update as the one in this post
https://forum.xda-developers.com/moto-x-style/general/maintenance-release-dec-2016-security-t3557903
You need full unroot, stock kernel, stock recovery and no system partition modification
lukas77 said:
You need full unroot, stock kernel, stock recovery and no system partition modification
Click to expand...
Click to collapse
could you tell me how I can do this? Is there a general guide?
Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.
acejavelin said:
Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.
Click to expand...
Click to collapse
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
ThanuTK said:
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
I hope it helps... Just remember to search around the forums or Google a bit before asking a question. I apologise if I sounded a little snappy, I had just answered some very dumb PM's that frustrated me and then this was the first open thread I saw, sorry if I was a bit abrupt.
This question has been answered a whole lot so it gets a little frustrating sometimes to see a new thread pop up for this issue. That being said and you being new to rooting, I can't stress this enough: please search and read through the threads (and know the XDA rules of course). This device has been out for a while and by now, a large majority of the questions, issues, and whatever else you may have is addressed in these forums. If you do run across anything that there is no answer for, by all means ask away.
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
Suri149 said:
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
Click to expand...
Click to collapse
Possible? Yes, but it isn't likely and I certainly don't expect it to happen. Lenovo has shown no interest in updating the Pure/Style to support Jio, or even fixing the current VoLTE issues on supported carriers for that matter.
Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?
ThanuTK said:
Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?
Click to expand...
Click to collapse
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
My thoughts exactly on the security updates. The only "evidence" I have heard about has been a couple of individuals who do not appear to understand why an app from some unknown source or dodgy websites along with crazy permission requirements might infect their phone. I acknowledge this as a human exploit though and not on the part of Android.
If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:
I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.
roaming4gnome said:
If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:
Click to expand...
Click to collapse
Dahenjo said:
I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.
Click to expand...
Click to collapse
This is actually a valid way of doing it, but with so many variables to the state of your device prior to doing this the possible outcomes vary a lot.
But @Dahenjo has pretty much the proper procedure... if I was going to try it I'd do it that way... backup, restore stock, take OTA, reroot, reflash Xposed, restore user data... 99% of everything should be intact.
acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
Real good explanation. Good balance of technological and practical
Sent from my iPhone using Tapatalk Pro
acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?
ThanuTK said:
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?
Click to expand...
Click to collapse
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.
acejavelin said:
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.
Click to expand...
Click to collapse
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451
ThanuTK said:
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451
Click to expand...
Click to collapse
The only difference in your links is one is a later build than the other one. Either one should work fine but if I had my choice, I might pick the first update and then use OTA to get to present. NOTE: I had to restore my September 1 backup with TWRP as the December 1 security patch broke my Bluetooth and I use Bluetooth all the time, it is too important to me to lose over a stupid security patch. I have since frozen the updater to avoid being nagged to death install the December 1 update again. When the next "real" OTA comes along, I will thaw the updater so I can take it and *hope* that the Bluetooth issue is solved. I will of course *always* make a TWRP backup prior to doing *any* update so I always have a way to back out of it in the event something is broken over the latest security patch OTA. HTH
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
LionLorena said:
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
Click to expand...
Click to collapse
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
prajwal2001 said:
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Nothing else only warranty
Sent from my Moto G4 Plus using Tapatalk
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Provided you're still on the stock ROM, I don't think rooting affects your anti-theft protection (I recall it's called Factory Reset Protection?). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Also, if you're logged into your device at the time, you could still locate and wipe your phone via Android Device Manager.
Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
echo92 said:
Provided you're still on the stock ROM, rooting shouldn't disable your anti-theft protection (which I recall is Factory Reset Protection). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
Click to expand...
Click to collapse
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
LionLorena said:
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
Click to expand...
Click to collapse
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
echo92 said:
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
Click to expand...
Click to collapse
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
LionLorena said:
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
Click to expand...
Click to collapse
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
zeomal said:
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
Click to expand...
Click to collapse
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
LionLorena said:
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
Click to expand...
Click to collapse
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
zeomal said:
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
Click to expand...
Click to collapse
The OTA updates are one of the reasons, yes.
And yes, from that point of view you are right.
I'm currently using some tracking solutions such as Cerberus, and disabling some features while the phone screen is locked, such as quick settings, and power off menu.
Also the extra layer of security imposed by Google version of iCloud, passes me some sense of safety.
The main thing that bothers me related to custom recovery is that the attacker can replace my software entirely.
While with stock I can have some time to recover the device using the tactics. Enabled.
And root could potentially aid me in that, I could add Cerberus to /system and etc.
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
alaindupus said:
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
Click to expand...
Click to collapse
thats why i'm thinking 3 times before doing it.
Hi, first, I am pretty new to rooting, yet I have done similar things on other devices. Second, here is the info on my android phone:
Samsung galaxy S5 model SM-G900V
Android Version 6.0.1
EMMC: 11xx...
it is a verizon phone so I'm pretty sure the bootloader is locked, and the latest towelroot throws the "this phone isn't currently supported" error on any of the modstrings I use, as well.
I am looking for some more direction on how to root this phone, and would like some help.
TimX24968B said:
Hi, first, I am pretty new to rooting, yet I have done similar things on other devices. Second, here is the info on my android phone:
Samsung galaxy S5 model SM-G900V
Android Version 6.0.1
EMMC: 11xx...
it is a verizon phone so I'm pretty sure the bootloader is locked, and the latest towelroot throws the "this phone isn't currently supported" error on any of the modstrings I use, as well.
I am looking for some more direction on how to root this phone, and would like some help.
Click to expand...
Click to collapse
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
hmm, wondering if any other new verizon android phones will be rootable since I am available for an upgrade
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
I got mine into a 4.4.2 rom and it was successfully rooted w busybox, but I can't install the SU binary or activate safestrap since it seems like I need one to get the other. is there a way around that?
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
Also, I have seen sites claim things like you can root it, such as the one below:
androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
(had to edit out the www. part of the link)
however, they all require doing stuff with odin, and I am still concerned about files being lost.
Trying to get more info on this, I would appreciate any and all help.
TimX24968B said:
Also, I have seen sites claim things like you can root it, such as the one below:
androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
(had to edit out the www. part of the link)
however, they all require doing stuff with odin, and I am still concerned about files being lost.
Trying to get more info on this, I would appreciate any and all help.
Click to expand...
Click to collapse
I find it highly suspicious that this method hasn't been trumpeted here on xda. The broken english doesn't ease my suspicion, either. Personally, I would want to have a disposable phone on hand to try it out, since it hasn't been vetted here first.
Before you do anything, read through the guide linked in my sig to get yourself familiar with the process. If you decide to tackle it, let us know how it turns out.
painiac said:
I find it highly suspicious that this method hasn't been trumpeted here on xda. The broken english doesn't ease my suspicion, either. Personally, I would want to have a disposable phone on hand to try it out, since it hasn't been vetted here first.
Before you do anything, read through the guide linked in my sig to get yourself familiar with the process. If you decide to tackle it, let us know how it turns out.
Click to expand...
Click to collapse
yea I know it seemed suspicious, so I didn't want to try it. However, would you happen to know of any newer androids that can be rooted, particularly verizon ones? I saw the guide but I don't think I can downgrade since I'm on verizon and 6.0.1, and I'm still afraid of losing my data if I do. Thanks for the help.
You can root that phone, there is a guide in the general section: [GUIDE] Root, Bootloader Unlocks, and More!
Look at the cid 11 section. It will erase all of your data though and downgrade you to lolipop. I used that guide on a marshmellow cid 11 Verizon S5 recently and it worked just fine.
Sadly, the bootloader of cid 11 Verizon S5s are still locked. I dont think there is a way yet to root Verizon S5s with cid 11 without losing your data.
Thanks for letting me know! How would I go about backing up my data for this kind of task, in that case? I am pretty sure I do not use verizons cloud services, but i do use their app for messaging.
As long as I can get root access so i can free up some space on my phone and possibly do other stuff in the future as well, it would be great if theres a way to back everything up aside from just copying the whole sd card, particularly things like contacts and text messages in that verizon app. Im fine being on lolipop, and if i can back up my data, i do have my escape method of just ditching this phone and using my upgrade.
Second question: what would be a newer verizon phone that would be rootable on the latest android?
I didn't need the data when I rooted the S5 I had, so I didnt back anything up.
There should be various apps on google play you can use to backup your text messages and contacts. You can manually backup any pictures and other media to a pc or something. I dont think there is much you can do to save your app data without root already. You can probably look up the save loactions of some of your apps and manually backup those.
I dont keep up with phone releases, so I cant reccomend anything.
Sorry I can't be of more help.
Ammalin said:
You can root that phone, there is a guide in the general section: [GUIDE] Root, Bootloader Unlocks, and More!
Look at the cid 11 section. It will erase all of your data though and downgrade you to lolipop. I used that guide on a marshmellow cid 11 Verizon S5 recently and it worked just fine.
Sadly, the bootloader of cid 11 Verizon S5s are still locked. I dont think there is a way yet to root Verizon S5s with cid 11 without losing your data.
Click to expand...
Click to collapse
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
tong6998 said:
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
Click to expand...
Click to collapse
I never said he could have root on marshmellow. Sorry if that was confusing as I never said it exactly. The linked guide says no root on marshmellow in bold near the top. Just wanted to let the OP know he could get root on the phone in some way at least.
To all:
I'm perfectly fine with downgrading. It was just the issue with backing up data which was holding me back there. However, I am still looking into doing this and appreciate the help. I think all I would need now is to know if anyone knows if there is any relatively new verizon phone that could be rooted out of box. Thanks.
If you know little about rooting, I will advice you to read more information about sm-g900v marshmallow root, like rooting with one click rooting software, just try their free trail and see if you can accept. Android Root from RenewAndroid has help me to solve this similar issue before, my device is Samsung S6.
tong6998 said:
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
Click to expand...
Click to collapse
If you compile the Greyhat Root Console for the S5 Device and use a 6.0.1 ROM still exploitable by dirtycow, there is a chance you may be able to adjust the sepolicy on your device enough, or setup supersu manually. I have yet to try this on my MM G900V. But the code is there. It is just down to the device specific commands to run.
People say dirtycow is a tethered/temporal root that only lasts until you reboot the device, but that isn't always the case if you run the right commands in the right order, or have an APP that sets up the temporal root after boot has completed automatically.
Delgoth said:
If you compile the Greyhat Root Console for the S5 Device and use a 6.0.1 ROM still exploitable by dirtycow, there is a chance you may be able to adjust the sepolicy on your device enough, or setup supersu manually. I have yet to try this on my MM G900V. But the code is there. It is just down to the device specific commands to run.
People say dirtycow is a tethered/temporal root that only lasts until you reboot the device, but that isn't always the case if you run the right commands in the right order, or have an APP that sets up the temporal root after boot has completed automatically.
Click to expand...
Click to collapse
My biggest gripe is the native emulated disk-space....I have had LL PB1 rooted on 900V S5 (CID 11) for sometime. But even with de-bloat, tons of lockups, freezing, constantly wiping cache, was hoping a move to MM (with root, hadn't checked in a while hoping bootloader was solved...) would be the savior....
Alas, it seems PB1 rooted is still the way to go as I have an additional "APPS" EXT FORMATTED partition mounted for apps that behave on it...and use APPS2SD and soft-links to keep storage balanced...but it's still a pain...
Now I have that same question, what is panacea?
If I have to get a new phone (pay exorbitant retail price or some "bargain" on ebay) which is the best root-able/boot-load-able or allows for miniSD expansion (hate the finite XXGB storage ever dictates) with space that can all be recognized for Apps+....
Replies bc or otherwise welcome
Col. P.
Adopting MM...
c0lp4nik said:
My biggest gripe is the native emulated disk-space....I have had LL PB1 rooted on 900V S5 (CID 11) for sometime. But even with de-bloat, tons of lockups, freezing, constantly wiping cache, was hoping a move to MM (with root, hadn't checked in a while hoping bootloader was solved...) would be the savior....
Alas, it seems PB1 rooted is still the way to go as I have an additional "APPS" EXT FORMATTED partition mounted for apps that behave on it...and use APPS2SD and soft-links to keep storage balanced...but it's still a pain...
Now I have that same question, what is panacea?
If I have to get a new phone (pay exorbitant retail price or some "bargain" on ebay) which is the best root-able/boot-load-able or allows for miniSD expansion (hate the finite XXGB storage ever dictates) with space that can all be recognized for Apps+....
Replies bc or otherwise welcome
Col. P.
Click to expand...
Click to collapse
I stand corrected... I now see *Storage Adoption* as part of MM, that could be the ticket for me! Obviously it formats the whole SD as EXT format...which is no big deal for me...at that point, since MM is un-rootable....do I take the leap? Will it really improve the S5?
Thanks for listening!
C0l. P.
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
Is it possible to go back to Lollypop version from 6.1
Billy7891 said:
Is it possible to go back to Lollypop version from 6.1
Click to expand...
Click to collapse
Yes
how can you that be done .It is my understanding that downgrades would be blocked. Is there another way?