Both have advantages, which did you choose and are you happy with the choice so far?
I'm definitely sticking with root until MM can be rooted. Too many useful apps for root to give up right now.
Kickin' it on my VS990
I'm sticking with Root, waited too long for it. Lots of benefits with root, wanam, adaway, titanium, etc. MM root will come soon enough, but if it doesn't I'm ok.
I went with MM. I prefer not to root my phone since it is an emergency device and I need it to work. I also did not want to void my warranty. I have never bricked a device rooting it, but did not want my LG V10 to be the first! . The other reason was I did not have any Android devices on MM, and this will probably be the only upgrade this phone sees!
Sticking with root until marshmallow can be rooted. I'm doubting that it can be done without a bumped recovery according to sources but lollipop was finally rooted after some time. I want marshmallow due to the permissions control built into the OS but will continue to wait for a little while before I give up root. My main use for root is no more ads and some other apps such as Casper and titanium backup.
Sent from my VS990 using XDA-Developers mobile app
I'm sticking with the benefits of LP root and I am willing to upgrade to MM...provided root is found.
Xposed
I updated due to the fact that my phone was pretty slow with root.
Related
I had to send my phone back because of a defect with the power. anyways, they sent me back a refurbished S4 and i only updated it to firmware MI1, realizing i had 2 software updates available. My first thought was about rooting, because i had wanted to root my phone until i realized i had MJ7 or whatever the latest one was and wasn't fond of the ideas. My question to you guys is, should i root my S4 and stay on MI1? is there a way i can do this and bypass the warranty void in the system?
All versions are rootable, even the MK2 that came out recently. The only reason so far to stay old is for ROM loading.
I for one am totally ok with never seeing another alternate ROM again, after two years of ROMing my Galaxy Nexus and the two years before that ROMing an Incredible.
When you say ROM loading, can you elaborate? Do the benefits of rooting at this software stage outweigh the benefits of the more recent ones? are some ROMs not compatible with higher softwares? because i remember MJ7 came up as "custom" and i most importantly don't want to trip my warranty, if possible. Especially because i just got this phone and don't want them to add to the bill if they see that the warranty got tripped before they even received my original S4.
Any rooting will bring up the 'custom unlock icon.
A ROM is a completely standalone full operating system custom made by developers that know how to make them. They are usually based upon Google's Open Source Android operating system source code with customization to suit the developer. It requires the phone to be not locked down to be able to install a ROM. When the phone is not locked down, a 'Custom Recovery' can be installed. Custom recovery is needed to load a ROM into the phone. Only the originaal S4 firmware, the MDK level from back in June, can have a custom recovery.
Rooting lets you run apps requiring root, such as the popular Titanium Backup, Root Explorer, and many others.
Rooting just lets you pretty much do whatever you want within the installed OS, but just not replace the OS. As I said, all the firmware loads for the S4 to date are rootable.
JeeperDon said:
Any rooting will bring up the 'custom unlock icon.
A ROM is a completely standalone full operating system custom made by developers that know how to make them. They are usually based upon Google's Open Source Android operating system source code with customization to suit the developer. It requires the phone to be not locked down to be able to install a ROM. When the phone is not locked down, a 'Custom Recovery' can be installed. Custom recovery is needed to load a ROM into the phone. Only the originaal S4 firmware, the MDK level from back in June, can have a custom recovery.
Rooting lets you run apps requiring root, such as the popular Titanium Backup, Root Explorer, and many others.
Rooting just lets you pretty much do whatever you want within the installed OS, but just not replace the OS. As I said, all the firmware loads for the S4 to date are rootable.
Click to expand...
Click to collapse
Yeah, i just didn't want to void the warranty. I think i am going to root my s4 tonight. any suggestions?
ImportedPerfection said:
Yeah, i just didn't want to void the warranty. I think i am going to root my s4 tonight. any suggestions?
Click to expand...
Click to collapse
If sort of depends what you want to do. If you want the flexibility to run custom ROMs with Safestrap, you should stay on ME7 or MI1.
If you're on MI1 and want to root it, can you please try the rooting technique in this thread? I'm curious if it'll work on MI1.
Hi all, thanks in advance for any help on this. I have a few general s5 rooting questions. I'm an experienced 'rooter' having rooted and installed custom ROMs on many previous devices.
- I've ready that the s5 has an 'e-fuse' that gets 'blown' when the device is rooted. this then voids the warranty and prevents things like Fort Knox from running. I get that, and understand the risks. But, I've also read that the lollipop update will remove root. These two things seem to contradict themselves.
- on other devices I've rooted, I've then installed a custom ROM. I don't plan to do this with my s5. I haven't been able to find much written on the experience of a rooted s5 running the samsung stock ROM/firmware. I'd like to use something like xposed to change parts of the ROM (like the white background that's so pervasive in the s5 flavor of lollipop). I'm curious if anyone is running lollipop on an s5 that is rooted but running stock samsung firmware and xposed.
thanks!
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
thanks!
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
System runtime is different. Art for lollipop compared to dalvik.. So it's not compatible as of now
Sent from my SM-G900T using XDA Free mobile app
This does not work with lollipop
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
gspears said:
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
Click to expand...
Click to collapse
are you sure ? I have been able to downgrade. towelroot and flash lollipop and it boots but supersu does not work properly. root apps ask permission and supersu grants permission but the apps dont actually work
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
I don;t know where you heard that rooting won;'t trip Knox but I beleive you are wrong about that At least I know that Flashing cf auto root - flashing recovery or flashing custom roms all trip knox. If your phone can use Towel Root - that rooting process does not trip knox - but I am not sure if Towel Root works on Lollipop or on the S5 for that matter. (I may be wrong about Towel Root - I have never used that process so I can't say for sure)
Flashing a new rom via ODIN does not trip knox. It is just like getting an UPDATE from the carrier OTA.
BUT, If you are already rooted - you already have tripped knox - flashing Lollipop will remove root - but it will not do anything to change the fact that you tripped knox on your phone already.
As far as I know everything I have said is correct - based on what I have learned thru reading - flashing and using several different samsung phones -
finally, I see a lot of people paranoid as hell about tripping knox - and I can tell you without any hesitation that I have never had a problem getting service or replacements after rooting a phone - there have been a few times back when I first started flashing roms that I had issues with my phone and I took it in and got a replacement without any issue - once I broke my screen and got a replacement then too - both times I was rooted, running custom recovery - etc.
I hope this helps you
I used towel root on NE6. You can downgrade to that via Odin and not trip knox. As far as flashing 5.0 and losing root. I came from Alliance flash Twisted lollipop and kept root. Then used Odin to flash the bootloader and modem for OB1.
Do you still have Knox 0?
How did you flash lollipop?
I might end up switching over to here from the Galaxy S3 within the next few months and I'm concerned on the bootloader/root status. As of the latest OTA that's been pushed, would this still work to flash custom ROMs and if it does, do I literally just have to follow the thread and I'm running(for example) the latest CM12 nightly? Thanks!
DubleJayJ said:
I might end up switching over to here from the Galaxy S3 within the next few months and I'm concerned on the bootloader/root status. As of the latest OTA that's been pushed, would this still work to flash custom ROMs and if it does, do I literally just have to follow the thread and I'm running(for example) the latest CM12 nightly? Thanks!
Click to expand...
Click to collapse
Yes but I believe you'd first need to downgrade to 10b and then root in order for this to work.
What he said. And we don't have root for Lollipop on our phone yet, but some developers here are working on it. You have to downgrade to 10B and root using Stump, then you can re-upgrade to 12B, which is the latest official stock LG version of Android on our phones. Lollipop is expected to officially drop on our phone anytime from a minute from now until the end of 2015. :\
We have a leak of the 23A build of Lollipop for our phone. I like it despite not being able to keep root when upgrading, for now. 23B, according to the open source code released by LG, will be the actual official Lollipop for us.
I came from the S3, too. I loved the phone, but got bored. I haven't regretted it, I love the G3 even better. The camera is awesome, I love how it feels. The first Android phone that I haven't wanted a case for.
roirraW "edor" ehT said:
What he said. And we don't have root for Lollipop on our phone yet, but some developers here are working on it. You have to downgrade to 10B and root using Stump, then you can re-upgrade to 12B, which is the latest official stock LG version of Android on our phones. Lollipop is expected to officially drop on our phone anytime from a minute from now until the end of 2015. :\
We have a leak of the 23A build of Lollipop for our phone. I like it despite not being able to keep root when upgrading, for now. 23B, according to the open source code released by LG, will be the actual official Lollipop for us.
I came from the S3, too. I loved the phone, but got bored. I haven't regretted it, I love the G3 even better. The camera is awesome, I love how it feels. The first Android phone that I haven't wanted a case for.
Click to expand...
Click to collapse
So it's not locked down in any sort of way(minus root)? I don't wanna get a phone not be able to mess around with it
DubleJayJ said:
So it's not locked down in any sort of way(minus root)? I don't wanna get a phone not be able to mess around with it
Click to expand...
Click to collapse
The answer depends on what you're looking for. If you want to have a phone with a custom recovery on it, with or without root, then yes we have that and can flash ROMs like crazy under KitKat 4.4.2, make nandroids, flash kernels and even an older modem if you like, etc. Under Lollipop, there's no way to do anything at all until we get a hold of the full ROM KDZ file that they can extract and modify to make flashable, rooted Lollipop ROMs.
I'm liking how smooth stock LG Lollipop is, though, and LG's built-in backup option under 4.4.2 and 5.0.1 make having a clean flash of 4.4.2 and manual upgrade to 5.0.1 even less painful than restoring with Titanium Backup because LG's backup is extremely fast, includes data and also includes the system data although I have yet to see (shortly) just how much system data is restored from an older ROM to a newer one, since it warns that not all system data might be restored when having backed up under an older ROM.
FYI, technically, I think the bootloader is still locked, however they have this thing called bump which evidently tricks the phone into still accepting flashes of non-official ROMs, by way of having a "bumped" version of TWRP installed, which can be done straight from Flashify in the Play Store as soon as you root using Stump brute force under 10B (an older LG stock ROM), reboot, install SuperSU, have it install/update the binary and reboot once more.
Then you can use @autoprime's Flash2 zip files in TWRP to flash the boot.img, modem.img and system.img of stock 12B if that's what you want, and then flash the latest SuperSU.zip, or whatever ROM you want. Sorry if I'm repeating some of what I had already said before.
Good luck, whatever way you decide.
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
lexluthor said:
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
Click to expand...
Click to collapse
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
iBolski said:
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
Click to expand...
Click to collapse
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
eagle132 said:
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
Click to expand...
Click to collapse
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
iBolski said:
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
Click to expand...
Click to collapse
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
eagle132 said:
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
Click to expand...
Click to collapse
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
eagle132 said:
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
Click to expand...
Click to collapse
Did you try Magisk at all? I am on Jasmine ROM (Android 5.1.1) and would love a way to still have Root & Xposed, but be able to pass SafetyNet for PokemonGO and Wallet
Question on XDABBEB's VS985 ROM
Considering that this phone will probably see no more OTA's, I'm ready to go back to root, but I don't want to break Android Pay. Also, I'm not going to use Kingroot. Don't trust it. So, I'll TOT back to 10B to flash XDABBEB VS985 ROM. But i have some questions regarding it (I haven't ran a custom ROM in almost a year).
Does anyone know if removing SuperSU from XDABBEB VS985 ROM will allow Android Pay to work? Curious if so, otherwise, I'll probably just stick with my stock 48A unrooted phone in order to keep Android Pay.
I also miss TiBu as my backup tool. Yes, LG Backup is nice and all, but TiBu is so much more flexible, including the scheduled backups that I like to do as well as pushing to my Google Drive for backing up the files. Also, TiBu doesn't store it in one giant backup file. I really wish LG Backup would store each app as a separate file, rather than one giant, humongous file. Also, if I do upgrade to a new phone that's not LG, LG Backup won't work for me, so I'll need TiBu (and of course, I have to make sure the new phone is rootable).
Thanks!
While I have not tried this (I plan to try magisk later this week) supposedly Reddit says we can use this bump script after applying magisk in order to make everything will boot. I'm reading mixed comments about if/which certain bootloader is needed to have this work (KitKat vs Lollipop vs Marshmallow) or which ROM to start with as a base (though I saw CM 13 mentioned). If anyone tries this, let me know. I'll post my results in the coming days.
This is the bane of the Z3v in my opinion. The only way I have been able to get write access to the root partition is to run a root exploiter like KingRoot. It would be nice to just install a custom rom, but I'm not sure if I can use Paranoid Android since it is made for the Z3, not Z3v.
I'm rooted with Kingroot atm (because I couldn't figure out how to remove it. SuperSU-me didn't work.) and on 5.1.1.
I'm rooted with Kingroot atm (because I couldn't figure out how to remove it. SuperSU-me didn't work.) and on 5.1.1.
Click to expand...
Click to collapse
I am in the exact same boat. At least I am able to debloat the software a bit. KingRoot is not nice though, and Purify is the worst. Took me a few tries to get that off my system.
As far as i remember you just have to flash the pre-rooted lollipop in the section and it will remove kingroot and let u use supersu.