So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
shxrm_ said:
So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
Click to expand...
Click to collapse
I have the same question. According to the release notes for 21r, the purpose was to update security. It appears that this is the stagefright patch.
EDIT: Appears to still be rootable.
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
aybarrap1 said:
I have the same question. According to the release notes for 21r, the purpose was to update security. I hate to think that AT&T might have intentionally worked to prevent rooting and Bump'd. Would not surprise me. AT&T has strangely been releasing a lot of updates over the last 6 months or so which is very unlike them. I have to wonder if they have not been working to prevent rooting as rooting has become harder and harder.
Click to expand...
Click to collapse
That's literally the only reason why I'm still on 20f, and usually I would just update my phone right away to get the security. I just wanted to know if it's possible
autosurgeon said:
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
Click to expand...
Click to collapse
I see your point.
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Hopefully it works for me, cause people said root worked for them on 21q, but it never worked for me
pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Looks like I will go through the long process of unrooting now. Been avoiding the OTAs since lollipop update because of the hassle of having to unroot. I am glad to see that AT&T actually worked quickly with LG on patching stagefright. Being able to root again was a main concern.
UPDATE: Thus far, after backing up all my data and apps (I use both LGs backup and TiBu to do batch backups), I have downgraded to stock unroot, and it took 3 OTAs (21f, 21q, and 21r) to get to where I am at. The unroot method only took about 10 minutes but I already had everything set up from my previous upgrade to Lollipop. The OTA updates were painful as they took a while to download and install (700+mB, 205mB, and 23mB respectively so about 1gig of wifi data) along with the optimization of apps each time. I have now successfully rooted.
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Firebourne said:
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Click to expand...
Click to collapse
Thanks for the confirmation of root as well as the the exact method that worked for you. I will be giving this a shot this afternoon. I want to take advantage of the stagefright patch while keeping root.
UPDATE: This root method worked. Had to do it twice but got it working.
Mjengles said:
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
It still refuses to work for me. I didn't change the diag port from when I restored back to stock, and I've tried it a few times just now, all to no effect.
Edit: the thing finally worked for me! I just closed the command prompt after the "send_command" part didn't work for me, and just did that part over, and it worked!!
CAUTION!!!!
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
You don't need to start all over. Just install the Gabriel kernel in twrp and you are good.
Sent from my LG-D850 using XDA Free mobile app
---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------
Firebourne said:
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
Click to expand...
Click to collapse
That only refers to secure boot errors booting twrp not booting the phone.
Sent from my LG-D850 using XDA Free mobile app
Link please? I searched the development threads, but didn't find the kernel you mentioned
shxrm_ said:
Link please? I searched the development threads, but didn't find the kernel you mentioned
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/lollipopstockkernelgabriel5-d855-t3120893
aybarrap1 said:
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
Click to expand...
Click to collapse
Second method of rooting worked for me. Hello control.....goodbye warranty
Sent from my ASUS MeMO Pad 7 using Tapatalk
Is there a bootable zip of the lastest stock Att ROM? Thanks.
Related
Hey guys,
So I just got the G3 last week, and an update rolled out from AT&T. Me being the idiot I am thought it was the Lollipop update so I updated it. Turns out, it was just 10f.
Then when I looked for ways to root the G3, all the methods required the software to be on 10d, not f.
What should I do?
Any help is much appreciated.
Use the bruteforce method in Stump root.
see: http://forum.xda-developers.com/lg-g3/help/att-d85010f-update-stump-root-t2953063
You are certain it'll work for 10f?
sympathizer said:
You are certain it'll work for 10f?
Click to expand...
Click to collapse
100%. I rooted on 10f using stump.
In addition, if you plan on rooting a device and you know there is an update, please wait to install the update until you know a root method is found.
aybarrap1 said:
100%. I rooted on 10f using stump.
In addition, if you plan on rooting a device and you know there is an update, please wait to install the update until you know a root method is found.
Click to expand...
Click to collapse
Will do.
Thanks a lot!
Not rooting
sympathizer said:
Will do.
Thanks a lot!
Click to expand...
Click to collapse
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
esanger22 said:
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
Click to expand...
Click to collapse
You can always flash back to the older version 10d in the return to stock thread.
Sent from my LG-D850 using XDA Premium HD app
Intub8 said:
You can always flash back to the older version 10d in the return to stock thread.
Sent from my LG-D850 using XDA Premium HD app
Click to expand...
Click to collapse
This is what I would do. It is possible you got a bad OTA as well. Did you factory reset after the OTA? I have seen many cases on forums where a factory reset takes care of many issues after an OTA.
Sent from my LG-D850 using Tapatalk
esanger22 said:
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
Click to expand...
Click to collapse
I don't know man, do you have the correct app installed? Mine went through smoothly in less than 5 minutes.
I just did this - now i am trying to bump the device. So my memory is relatively fresh
Reboot for fresh start - Run Stump - it will say device not supported - try brute force - let it run - takes 5 - 7 and maybe 10 min after which it says "reboot" device - then go ahead and reboot device. Run stump again - it should say device is rooted. Next download "root checker" it will say rooted. Ofcourse if this all does not go thru - you can downgrade to a previous firmware and it'll go easier - however that's more labor intensive and you'll not be able to back up the current ROM with all your apps and setup.
Well, I ended up having to flash back to 10d as mentioned by many of you. This fixed the problem!
esanger22 said:
Well, I ended up having to flash back to 10d as mentioned by many of you. This fixed the problem!
Click to expand...
Click to collapse
Good to hear and I do not think you are missing much going back. At least I have found no difference. Just freeze "Software Update" to prevent nagging OTA update notifications.
aybarrap1 said:
Good to hear and I do not think you are missing much going back. At least I have found no difference. Just freeze "Software Update" to prevent nagging OTA update notifications.
Click to expand...
Click to collapse
I actually installed CM12...its friggin awesome.
I can report no issues here with Stumproot on 10f and I've restored back to stock multiple times.
Sounds like something was just messed up on my phone, everyone else was able to use it!
perhaps this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
works nicely, no muss, no fuss
If i revert to 10D do i have to use the BUMP method after root? Or just get TWRP/CWM Recovery like good ole days? I just don't care to have the BUMP bypass that is why I am asking.
I have the ATT G3 10F.
So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
So i rooted my s6 thinking that it would be like a jailbreak and i was wrong.. can someone give me a link to a video or some info on how to unroot it. Thanks!
http://forum.xda-developers.com/showthread.php?t=3096000
Might be a place to start.
Normally this is something you look at before rooting you device so you know how to if you run into problems
Go into super su app and choose full unroot
I second what krelvinaz said, head over to that thread and start back to stock and start fresh
bash_array said:
Go into super su app and choose full unroot
Click to expand...
Click to collapse
I was going to use the SuperSu to do the Full unroot. If I did that, then installed the current Verizon OTA, could I then re-root using pingpong? Or does this OTA disable the ability to root again? I've read so many posts and articles from various sources, some say yes, some say no. The more I dig the more conflicting info I find.
The only reason I rooted in the first place was to swap out the mixer_paths.xml file. I'm curious if the OTA will wipe that moded file out. But that's probably another discussion.
Thanks
I rooted first and a day later took ota. After ota pingpong root just needed to "download data" or whatever then root worked fine.
Sent from my SM-G920V using XDA Free mobile app
jboogie555 said:
I rooted first and a day later took ota. After ota pingpong root just needed to "download data" or whatever then root worked fine.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
Really? Bummer, mine isn't taking the update. I've tried several times and it just fails after the download and after the reboot to install. Nothing bad happens after that, it just boots up like normal. Then it harasses me again and again to do the update.
http://forum.xda-developers.com/showpost.php?p=61279830
Easy process
DAS3D said:
Really? Bummer, mine isn't taking the update. I've tried several times and it just fails after the download and after the reboot to install. Nothing bad happens after that, it just boots up like normal. Then it harasses me again and again to do the update.
Click to expand...
Click to collapse
I think what you are talking about is you were rooted and tried to take the Ota and it wouldn't install correct? If that's the case, yeah you have to unroot or Odin the new version then reboot.
Sent from my Verizon Galaxy S6
Use the verizon upgrade utility that is on your phone when it's plugged in as an installer. Make sure your battery is charged all the way too.
Sent from my SM-G920V using XDA Free mobile app
MrWicked1 said:
I think what you are talking about is you were rooted and tried to take the Ota and it wouldn't install correct? If that's the case, yeah you have to unroot or Odin the new version then reboot.
Sent from my Verizon Galaxy S6
Click to expand...
Click to collapse
Thanks a lot for your help!
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
jboogie555 said:
Use the verizon upgrade utility that is on your phone when it's plugged in as an installer. Make sure your battery is charged all the way too.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
That did the trick! Thanks so much. It worked just like it should have. Afterwards I did have to rerun pingpong, but that took about 2 seconds and I'm back to normal now with the update. Thanks a million!
I did that, as I usually do when I sell my phones.... It bricked it and I could reinstall stock.
Unrooting options
To summarize the unrooting options:
1. Unroot with SuperSu - By some reports this method does not work
2. Odin stock rom - Wipes the device and data, ?trips knox?
3. Use the Verizon Update Utility - Upgrades the devices to latest OTA
I am on 5.02 Stock (AOC3), rooted, Knox not tripped.
I am really not interested in wiping my device or updating to the latest OTA.
What I want to do is *temporarily* unroot to see if I can get Android Pay working again.
Has anyone had any luck with method 1 above? If android pay and your credit cards are activated/verified while unrooted, can you then re-root and still have Android Pay work?
I really miss using Android Pay... but not enough to lose root!!!
If you go into the superuser app and click the enable superuser to turn it off you can activate a card with android pay. You won't lose root this way.
I did that with my bank card and once my card was listed in Android pay I reenabled superuser and everything works fine.
I'm also using root cloaker but I don't know if it's needed.
Sent from my SM-G920V using XDA Free mobile app
Awesome!!! That was too easy.
Thank you, thank you, thank you!!!
@dobosininja
Is your android pay still working? I was able to use Android pay for only a short period ~1 day. Now I get the message "This card cannot be used right now" It doesn't matter what card I use or whether SuperSU is enabled. Maybe it is detecting SuperSU itself.
What app / procedure did you use for cloaking? Did it trip your knox?
Thanks!
sdpluth said:
@dobosininja
Is your android pay still working? I was able to use Android pay for only a short period ~1 day. Now I get the message "This card cannot be used right now" It doesn't matter what card I use or whether SuperSU is enabled. Maybe it is detecting SuperSU itself.
What app / procedure did you use for cloaking? Did it trip your knox?
Thanks!
Click to expand...
Click to collapse
Mine is still showing my card being attached, but I have not used it lately.
I am using root cloak plus, but I can't guarantee it works.
My knox is not tripped since I rooted with ping pong that didn't trip it.
sdpluth said:
@dobosininja
Is your android pay still working? I was able to use Android pay for only a short period ~1 day. Now I get the message "This card cannot be used right now" It doesn't matter what card I use or whether SuperSU is enabled. Maybe it is detecting SuperSU itself.
What app / procedure did you use for cloaking? Did it trip your knox?
Thanks!
Click to expand...
Click to collapse
If I'm correct, the Token needs to refresh from time to time. It may be that that process is detecting the root.
I'd try the Root Cloak he mentioned.
I recently had to odin back to stock OE2 on my device and am trying to re-acquire root access however Pingpong root keeps telling me my device is unsupported when I attempt to Download Data as per the instructions. I rooted originally with Pingpong many months ago when my device was brand new so dont understand why this is failing. I am rooted now via Kinguser but dont like it as I would prefer to have SuperSU installed so that I can use flashfire. Anyone have any ideas? Its almost like Pingpong is not downloading any updated data, I have verified that my build number is right so totally stumped. Anyone have any ideas on how to get Pingpong to work again or another means of getting SuperSU installed and the binary to update?
Additional note: I never took any OTA updates, was on OE2 ever since unboxing the phone nearly a year ago.
Attached is a screenshot of my build version.
Which version of ping pong root are you trying? Not sure if that matters though.
Tried both versions listed, beta5.1 and beta6. Both say device not yet supported. I am thinking that the pingpong app is just no longer downloading the data required.
i wonder if i make a flashfire back up of certain partitions, if you can flash my backup and get the result your wanting. Im thinking just system partition. Since its a verizon gs6, you think it would work? Obviously i wont do the efs partitions.
Fe Mike said:
i wonder if i make a flashfire back up of certain partitions, if you can flash my backup and get the result your wanting. Im thinking just system partition. Since its a verizon gs6, you think it would work? Obviously i wont do the efs partitions.
Click to expand...
Click to collapse
I cant use FlashFire since I cannot get SuperSU installed and the binary to update. I'm stuck with this stupid kingroot which I have to re-run every time I reboot the phone to get root. I need Pingpong to start working again
JM1084 said:
I recently had to odin back to stock OE2 on my device and am trying to re-acquire root access however Pingpong root keeps telling me my device is unsupported when I attempt to Download Data as per the instructions. I rooted originally with Pingpong many months ago when my device was brand new so dont understand why this is failing. I am rooted now via Kinguser but dont like it as I would prefer to have SuperSU installed so that I can use flashfire. Anyone have any ideas? Its almost like Pingpong is not downloading any updated data, I have verified that my build number is right so totally stumped. Anyone have any ideas on how to get Pingpong to work again or another means of getting SuperSU installed and the binary to update?
Additional note: I never took any OTA updates, was on OE2 ever since unboxing the phone nearly a year ago.
Attached is a screenshot of my build version.
Click to expand...
Click to collapse
I am having the exact same problem. But what is so bad about Kinguser? I haven't used that but is that the only other way to get root on OE2 if pingpong doesn't work?
flooritnfly said:
I am having the exact same problem. But what is so bad about Kinguser? I haven't used that but is that the only other way to get root on OE2 if pingpong doesn't work?
Click to expand...
Click to collapse
Nothing really I guess, other than having to re-run the root process every time I reboot my device. Not to mention I cant get Flashfire to run with it so that I can switch to one of the custom roms that are available. Really have major buyers remorse with this bloody phone.
JM1084 said:
Nothing really I guess, other than having to re-run the root process every time I reboot my device. Not to mention I cant get Flashfire to run with it so that I can switch to one of the custom roms that are available. Really have major buyers remorse with this bloody phone.
Click to expand...
Click to collapse
Hey you can download supersume app from google play it is a paid app that takes you from kingroot to SuperSU semmlessly without losing root
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
[email protected] said:
Hey you can download supersume app from google play it is a paid app that takes you from kingroot to SuperSU semmlessly without losing root
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I've used it successfully many times on the s5 verizon and I has worked 100% of the time
Sent from my SM-G900V using Tapatalk
[email protected] said:
Hey you can download supersume app from google play it is a paid app that takes you from kingroot to SuperSU semmlessly without losing root
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
I've used it successfully many times on the s5 verizon and I has worked 100% of the time
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Wow thanks for this tip! Worked like a charm for me, Just had to make sure I was on an older version of Kingroot first then Super Sume worked its magic.
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Probably the security patch.
Taken from my 920
It brings us up to 10i where T-Mobile is currently at.
Ant way to block updates on a non rooted phone?
Could we possibly finally get a stock KDZ from this?
I froze that
jetracer said:
Ant way to block updates on a non rooted phone?
Click to expand...
Click to collapse
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Edit: It failed this time.....I just got the update prompt
monke30butt said:
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Click to expand...
Click to collapse
Can you link the apk. Can only seem to find old ones
haris163 said:
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Click to expand...
Click to collapse
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
ubergeek77 said:
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
Click to expand...
Click to collapse
I willingly let it install.
AT&T Forced this update on my phone
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
haris163 said:
I willingly let it install.
Click to expand...
Click to collapse
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
mmarsie said:
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
Sorry I don't know about that. My phone is pure stock.
mmarsie said:
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
ubergeek77 said:
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
Click to expand...
Click to collapse
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
mmarsie said:
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
Click to expand...
Click to collapse
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm not rooted yet. I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
ubergeek77 said:
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
Click to expand...
Click to collapse
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
mmarsie said:
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
Click to expand...
Click to collapse
This is terrible.
ubergeek77 said:
This is terrible.
Click to expand...
Click to collapse
yeah I'm lived right now, currently with out a cellphone untill i test some of the above options another user posted. Here's hoping
Does anyone know whether a phone with this update can still use the dirtysanta exploit to root, or is that also broken by the security update?