So I can't tell if this question is moronic and totally obvious, or just not possible at the moment. I'm out of date with everything right now, as I'm just getting back into bricking my phones after taking a break. Months back, I bumped my G3 and am currently running TWRP with CM12 (latest nightly).
My question is, how do I gain root access? I've read about the various current methods, but I'm unable to find one that works. Is it just not possible at the moment on 5.0.2? Why I remember this being easier? Root level attaches to the ROM correct? am I making this up that I thought root was a part of CM flashing in the past? and wasn't in addition too?
jacksheadache said:
So I can't tell if this question is moronic and totally obvious, or just not possible at the moment. I'm out of date with everything right now, as I'm just getting back into bricking my phones after taking a break. Months back, I bumped my G3 and am currently running TWRP with CM12 (latest nightly).
My question is, how do I gain root access? I've read about the various current methods, but I'm unable to find one that works. Is it just not possible at the moment on 5.0.2? Why I remember this being easier? Root level attaches to the ROM correct? am I making this up that I thought root was a part of CM flashing in the past? and wasn't in addition too?
Click to expand...
Click to collapse
I'm not sure why it's not built in, but I do know if you flash the zip then root will come.
http://download.chainfire.eu/695/SuperSU/UPDATE-SuperSU-v2.45.zip
That was my first thought as well, and I had flashed SuperSU, but no root. I forget the version tried, so maybe that is the issue.
That worked. Now that I'm thinking of it, I may have just installed it locally and not flashed it previously.
jacksheadache said:
So I can't tell if this question is moronic and totally obvious, or just not possible at the moment. I'm out of date with everything right now, as I'm just getting back into bricking my phones after taking a break. Months back, I bumped my G3 and am currently running TWRP with CM12 (latest nightly).
My question is, how do I gain root access? I've read about the various current methods, but I'm unable to find one that works. Is it just not possible at the moment on 5.0.2? Why I remember this being easier? Root level attaches to the ROM correct? am I making this up that I thought root was a part of CM flashing in the past? and wasn't in addition too?
Click to expand...
Click to collapse
Check under development options. I thought CM disabled root as a stuck setting. It's on the user to enable it.
Sent from my VS985 4G
maximusmullivan said:
Check under development options. I thought CM disabled root as a stuck setting. It's on the user to enable it.
Sent from my VS985 4G
Click to expand...
Click to collapse
That's correct. It has to be enabled.
The built-in root has to do with permissions thing they added to CM. It's stupid because flashing a nightly wipes out SuperSU. I have CyanDelta set to flash SuperSU as well, and I believe I've been fine after that. However, if you flash a nightly and don't flash SuperSu also, you WILL loose your SuperSu settings, which was quite annoying for me...... I haven't bothered to test out the build in root permissions.
Related
Do we know a root procedure that will work after the 4.3 update?
I too am curious to know!
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Shane_pcs said:
Just root? The old way works. If you want full R/W access to the system folders then as far as I know thats not working right without a customer kernel.
Click to expand...
Click to collapse
Does it matter if mine is s-off?
Alright, I got mine rooted with no problems.
Just install TWRP, CWM, or CM2 for the recovery and then install SuperSU to get the root.
If you do TWRP like I did, when you go to reboot the system for the first time, it will say that you aren't rooted and ask if you want to run SuperSU to root. Pretty straight forward.
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
I rooted mine specifically to disable updates. I'm not so much afraid of root exploits getting patched as I am any potential bootloader exploits being patched. I came from the galaxy s3, which got a bootloader update mid way through that was never cracked, so I'm little worried about that if I wait to long I can never unlock the bootloader. So far I've installed titanium backup, root explorer, and the kit kat sd card fix (no need for hotspot hack since I don't have unlimited data). I'm holding off on anything too major until the bootloader is unlocked and I can do a nandroid first.
I rooted the day I got my g3. I rooted and installed custom roms on my g2 and can't wait to do the same on my g3
Sent from my LG G3
I actually got a demo model from VZW, rooted that one, just to see how hard it was going to be, When I got my permanent one a few days later I rooted it out of the box, before installing anything else.
rooted and uninstalled what I could installed xposed tweaked to my liking and waiting for bootloader recovery and roms
Sent from my VS985 4G using Tapatalk
I rooted mine before I even set it up.
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
As with most of my phones, my G3 was rooted as soon as the battery was charged, and usually before being activated. Now if we could just get a bootloader unlock. :fingers-crossed:
bkhorn said:
Had my G3 a couple of days before I rooted it. It was so simple to do. one of the 1st things I did was get it setup as a hotspot.
Click to expand...
Click to collapse
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
tu3218 said:
Just wanted to see if everyone is diving in and rooting their devices or not. As of right now, I'm still running stock. Haven't found much of a reason to root but would be to nice to have wifi tether and adblock. With one click root, I'm so tempted but still holding off in case any updates. So, have you gone ahead and rooted your new G3 yet?
Click to expand...
Click to collapse
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
tu3218 said:
which method are you using for the hotspot? That's a main reason I'd want to root but I believe the method in the dev. section, based on reading peoples comments, it's still not that reliable and requires extra steps to get it working.
I want to root just don't want to screw up my brand new phone. I've always rooted my phones but past couple phones I didn't cause they were locked down so I'm weary to jump back into it lol Everyone using stump root? Seems pretty straightforward with that method for us Verizon guys.
Click to expand...
Click to collapse
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
tech_head said:
You honestly asked that on XDA???
The question is not "who rooted", but who didn't root?
Me?
1. Out of the box.
2. Activated enough with no SIM to get to ADB
3. Root.
4. Turn off and remove bloat (includes de-activating OTA).
5. Now activate normally and use phone.
My phones go from box to root in under 5 minutes.
Click to expand...
Click to collapse
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
bkhorn said:
I went off of this: http://forum.xda-developers.com/verizon-lg-g3/development/mod-verizon-g3-hotspotmod-g2-apk-t2852152 but with a twist after I read the directions. I used Root Explorer to change the names and copy files. Post #15 helped me a lot.
1, download HotspotProvisionVsG3Mod.apk from 1st post and rename to HotspotProvision.apk
2, search for HotspotProvision.apk and HotspotProvision.odex in /system/app. I added .bak to both of them.
3, now copy HotspotProvision.apk that you remaned to /system/app. Change permission's to rw-r-r-
4, reboot
5, JOY
Click to expand...
Click to collapse
Great thanks! If I root, I'll be sure to follow your instructions.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I used "ioroot". Stump root did not exist when I got my phone.
tu3218 said:
True. But I'm sure there are a fair share of people who don't root and just follow all the other stuff. Did you use stump root to root?
Great thanks! If I root, I'll be sure to follow your instructions.
Click to expand...
Click to collapse
I also used IORoot and it's very easy, Stump wasn't out when I rooted mine but from what I've read Stump is super easy and reliable.
I walked out of Best But, phone activated and Battery at like 70% and hopped on my laptop which I had with me and rooted the phone right there in the parking lot so that I could freeze System Updates right away.
Although Verizon is so slow with OTA updates anyways I really could have waited lol
Root that thing then remove all the Verizon junk and use Greenify... You'll be even more happy with how your G3 runs after doing that and it's quite easy to do.
- Tapatalked from the G3
nrage23 said:
I rooted mine before I even set it up.
Click to expand...
Click to collapse
yup me too
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
tu3218 said:
Becoming more tempted everyday lol My only fear is if the bootloader unlock takes longer than expected, and no recovery access is created so if Verizon releases an update, even if someone pulls the update we won't be able to install because our modded phones and of course, no rom due to no recovery. Maybe I'm thinking too much into it. It's been awhile for me.
Click to expand...
Click to collapse
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
bobcat987 said:
The flip side of that is the first update could lock out all root methods and any potential bootloader exploits. There are a lot of smart people on this board, so I'd wager someone will find a safe way to update if no bootloader unlock is discovered by the time it's released.
Click to expand...
Click to collapse
Yeah I've seen some remarkable things done my fellow members.
spotmark said:
You could always flash back to stock.
http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
Click to expand...
Click to collapse
Very true. Thanks for that link. I'm just afraid of my screwing up my brand new toy haha Not sure why though, it seems stump root is really straight foward. I just know once I do it, I'll start messing with xposed a lot. I know when I had my S3, I was flashing roms like once a day. My gf thought I was crazy.
Build KOTH49H.G900TUVUANE1
There's some update saying it brings VoLTE, and I think there are more updates after that? Not sure since I'm still on 4.4.2. What's the proper procedure for upgrading and keeping root/being able to re-root?
I'm rooted currently using towelroot. Have not got around to custom recovery yet, because I wasn't sure what's available, and haven't had time to sit down and do my research yet. So whatever I need to maintain root, I am ready to "listen" (read carefully) and am familiar with ADB and Odin.
..
Well I figured as much for roms. But as of right now, I'd like to keep stock until I can repair my girlfriends s4 cause we are sharing right now.
I will see if there's information about this specific update, but that's why I didn't blindly hit accept.
What I wanted was to be up to date and still rooted, so I can install custom recovery later.
zero computing said:
build koth49h.g900tuvuane1
there's some update saying it brings volte, and i think there are more updates after that? Not sure since i'm still on 4.4.2. What's the proper procedure for upgrading and keeping root/being able to re-root?
I'm rooted currently using towelroot. Have not got around to custom recovery yet, because i wasn't sure what's available, and haven't had time to sit down and do my research yet. So whatever i need to maintain root, i am ready to "listen" (read carefully) and am familiar with adb and odin.
Click to expand...
Click to collapse
you can retain root if you use mobile odin pro to upgrade
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.
Hello all, new here. Having a hard time figuring out what my options here are. At one time I had root, unrooted for reasons that escape me, accidentally upgraded... Kinda never messed with it much and did a couple factory data wipes...
Current build 0c1.
Thanks for any help, sorry for being n00bz0rz.
Your bootloader is probably locked, but you can root with king root (Not kingo) and switch to SuperSU. SuperSU is better. Google how to make the transition. That way you'll at least have root.
Thanks @Airsoftjunky
I should have been more clear... I got the kingroot and supersu swap method to root.
BUT
Keep finding info for of1 king root and supersu swap, change kernel to 0c1 and do something so stops spitting out error message....
My question was ment to be, what rom options do I have? Do have any baseband/radio options? Kernel?
So, I don't needed to need mess with kernels right? And can run some mods like hyperdrive? Have to be 5.0 roms, correct?
So, just to be clear, you've rooted with Kingroot, but can't switch to SuperSU? (Where is the error, and what is it exactly?)
Compermised said:
Thanks @Airsoftjunky
I should have been more clear... I got the kingroot and supersu swap method to root.
BUT
Keep finding info for of1 king root and supersu swap, change kernel to 0c1 and do something so stops spitting out error message....
My question was ment to be, what rom options do I have? Do have any baseband/radio options? Kernel?
So, I don't needed to need mess with kernels right? And can run some mods like hyperdrive? Have to be 5.0 roms, correct?
Click to expand...
Click to collapse
Your safest bets are 'Touchwiz' based ROMs as your bootloader is locked on lollipop and there is no fix for that. Search forum for "Albe95'" or Stang5itre roms