Database Info

New MyTouch 4G owner

Didn't see a General discussions thread so I hope saying hello in a new thread won't cause pain.
Just got my MyTouch 4G today after returning an HTC HD7 for lack of cell radio reception. My MyTouch is currently on Android 2.2 and am hoping it will automatically update to 2.2.1 (heads-up on the procedure is welcome).
I had a choice between this phone or the G2. I chose this one because of the front camera. Not sure but I believe this MyTouch has a faster CPU than the G2.
It feels good and solid in the hand and the battery door is metal as opposed to the flimsy plastic of the HD7.
And words of wisdom for tweaking and using this nice hardware is appreciated.

Welcome to the club! Don't think you'll be disappointed, and the MT4G at least on par with (I think better than) the G2. You can easily compare the proc specs via a Google/web search...the MT4G has a 2nd gen Snapdragon.
I got my MT4G the day after release, and had the OTA update that evening. Just got an OTA message and let the d/l and update rip. There's a thread or 2 regarding those still awaiting the OTA update, so who knows what the delay is or the logic behind when you'll get it.
Good news is the perma-root was obtained last week and hopefully we'll have new ROMs available soon.
BTW, time to change your avatar pic since you returned that HD7!

MartyLK said:
Didn't see a General discussions thread so I hope saying hello in a new thread won't cause pain.
Just got my MyTouch 4G today after returning an HTC HD7 for lack of cell radio reception. My MyTouch is currently on Android 2.2 and am hoping it will automatically update to 2.2.1 (heads-up on the procedure is welcome).
I had a choice between this phone or the G2. I chose this one because of the front camera. Not sure but I believe this MyTouch has a faster CPU than the G2.
It feels good and solid in the hand and the battery door is metal as opposed to the flimsy plastic of the HD7.
And words of wisdom for tweaking and using this nice hardware is appreciated.
Click to expand...
Click to collapse
It's a good phone and you'll definitely enjoy it.
On the update procedure: Sometime after you make your first phonecall or type *#*#CHECKIN(or 243256)#*#* into the dialpad you will automatically download it and have a popup notification saying you have an update ready to install. You click go, and that's it!
Now there are a bunch of us who haven't received their updates for various different reasons, and we would <3 you long time if you would download the "aLogcat" app from the marketplace and run it while you wait for the update. What this will allow us to do is find the HTML link to Google's servers, so we can manually update. Once you have the update, you can upload the log to this website or send me a PM and we'll make arrangements that way.

LOL...yeah...been busy. Will get on that avatar.
By the way, what material property is the screen made of, hopefully Gorilla Glass?

MartyLK said:
LOL...yeah...been busy. Will get on that avatar.
By the way, what material property is the screen made of, hopefully Gorilla Glass?
Click to expand...
Click to collapse
That's the rumor! But the official material isn't listed.

unremarked said:
It's a good phone and you'll definitely enjoy it.
On the update procedure: Sometime after you make your first phonecall or type *#*#CHECKIN(or 243256)#*#* into the dialpad you will automatically download it and have a popup notification saying you have an update ready to install. You click go, and that's it!
Now there are a bunch of us who haven't received their updates for various different reasons, and we would <3 you long time if you would download the "aLogcat" app from the marketplace and run it while you wait for the update. What this will allow us to do is find the HTML link to Google's servers, so we can manually update. Once you have the update, you can upload the log to this website or send me a PM and we'll make arrangements that way.
Click to expand...
Click to collapse
I get a "Connection problem or invalid MIMI code" message.

MartyLK said:
I get a "Connection problem or invalid MIMI code" message.
Click to expand...
Click to collapse
Should just be *#*#2462546#*#*
It won't be instant, though. On my first device, I received the update 6hrs after activation.
EDIT: realized I mistyped on the original. Sorry about that.

unremarked said:
Should just be *#*#2462546#*#*
It won't be instant, though. On my first device, I received the update 6hrs after activation.
EDIT: realized I mistyped on the original. Sorry about that.
Click to expand...
Click to collapse
Eh...no...I'm sorry, you typed correctly. I misread it. I dialed *#*#243256*#*#.

No gorilla glass on the mt4g or ANY HTC device... spoke with several corning employees, reps, and r&d folks(mfg of gg) at a conference this weekend, they said they have received 0 communication from HTC even with a interest in their product... he also said all that has to happen for us to get gg on HTC phones is have HTC pull their heads outta their asses and ask for it..

ESKIMOn00b said:
No gorilla glass on the mt4g or ANY HTC device... spoke with several corning employees, reps, and r&d folks(mfg of gg) at a conference this weekend, they said they have received 0 communication from HTC even with a interest in their product... he also said all that has to happen for us to get gg on HTC phones is have HTC pull their heads outta their asses and ask for it..
Click to expand...
Click to collapse
Any idea how scratch resistant the MyTouch 4G is? EDIT- Is it the same material as on the HD2?

? All I can say is I don't have **** on mine... naked as a jay bird... I use the tmo holster while at work which holds the device screen in...
Also never had a screen cover for my n1... absolutely nessicary on the mt3g and g1 I had tho...
Ymmv
Sent from my HTC Glacier using XDA App

lghorn said:
Welcome to the club! Don't think you'll be disappointed, and the MT4G at least on par with (I think better than) the G2. You can easily compare the proc specs via a Google/web search...the MT4G has a 2nd gen Snapdragon.
I got my MT4G the day after release, and had the OTA update that evening. Just got an OTA message and let the d/l and update rip. There's a thread or 2 regarding those still awaiting the OTA update, so who knows what the delay is or the logic behind when you'll get it.
Good news is the perma-root was obtained last week and hopefully we'll have new ROMs available soon.
BTW, time to change your avatar pic since you returned that HD7!
Click to expand...
Click to collapse
Doesn't look like I will be doing that on my MyTouch. I just read over the thread about it and, even though I had an HD2 with Android and was deep into it and could do a lot with it, directly on the device through apps like SUFSB, I have no clue about adb push/pull and have never been able to understand it because nobody ever truly explained what it is. I've searched Google about it and the resulting discussions are as vague as any other.
From what I gather there is some sorta program you put on the PC and do **** with it from there, but I've put things like adb on my PC and have no clue about what to do with it. I can click some stuff in it and nothing happens. adb shows up in my PC task manager, but doesn't seem to be doing anything beyond just taking up resources.
When I wanted to do something in my HD2 Android build, I would open SUFSB, tap the S to make it red and then copy and paste whatever I needed to, or delete whatever I didn't want. That is the extent of my knowledge.

MartyLK said:
Doesn't look like I will be doing that on my MyTouch. I just read over the thread about it and, even though I had an HD2 with Android and was deep into it and could do a lot with it, directly on the device through apps like SUFSB, I have no clue about adb push/pull and have never been able to understand it because nobody ever truly explained what it is. I've searched Google about it and the resulting discussions are as vague as any other.
Click to expand...
Click to collapse
adb is really (without a deeper technical explanation) an interface to allow you to run commands, etc. from your PC/Mac/Linux box on your phone's OS, as well as push/pull files, and what not. It's part of the Android SDK, and there are various wiki's and how-to's regarding installation, configuration, basic adb commands, etc. I'd not used it before yesterday, and got it d/l'd, installed, and running commands in <30 mins.
HOWEVER, you don't need to use adb to root. Read through the how to root & S-OFF thread in the MT4G General section (or find the video on YouTube) and follow the steps - there are adb and non-adb options. Once you get the 2 required files onto your phone, all you really need is to download the Visionary (r12) and Terminal apps. Terminal is available in the Market, and you can find the Visionary r12 apk online easily. Instead of adb from your computer you can just run the necessary commands directly on your phone using Terminal app.

MartyLK said:
Any idea how scratch resistant the MyTouch 4G is? EDIT- Is it the same material as on the HD2?
Click to expand...
Click to collapse
Don't know exactly what it is, but it appears to be pretty quality and have some scratch resistance.
I read one post on here (forget where) and the poster stated he'd run a key across his screen to show how scratch-resistant it really is (i.e. the key wouldn't scratch the screen).

lghorn said:
adb is really (without a deeper technical explanation) an interface to allow you to run commands, etc. from your PC/Mac/Linux box on your phone's OS, as well as push/pull files, and what not. It's part of the Android SDK, and there are various wiki's and how-to's regarding installation, configuration, basic adb commands, etc. I'd not used it before yesterday, and got it d/l'd, installed, and running commands in <30 mins.
HOWEVER, you don't need to use adb to root. Read through the how to root & S-OFF thread in the MT4G General section (or find the video on YouTube) and follow the steps - there are adb and non-adb options. Once you get the 2 required files onto your phone, all you really need is to download the Visionary (r12) and Terminal apps. Terminal is available in the Market, and you can find the Visionary r12 apk online easily. Instead of adb from your computer you can just run the necessary commands directly on your phone using Terminal app.
Click to expand...
Click to collapse
Thanks for the reply.
I tried to read the Wiki about adb but just scratched my head at what they were saying. It seemed the explanations were aimed at people who are already into computer programming and such. People who already knew all the terminology and lingo of various OSs.
EDIT- Just read this. It is an example of the vagueness of what I have read about adb. This about what s off and s on is.
http://forum.xda-developers.com/showthread.php?t=839267
After reading that, I can now work for Microsoft and single handedly produce their next OS.

MartyLK said:
Thanks for the reply.
I tried to read the Wiki about adb but just scratched my head at what they were saying. It seemed the explanations were aimed at people who are already into computer programming and such. People who already knew all the terminology and lingo of various OSs.
Click to expand...
Click to collapse
Yep, I'm an IT consultant & former developer, but the people who easily get this are likely Linux developers/gurus.
It's probably a nice to have/know, but you don't need adb or that knowledge to root the MT4G, install ROMs, and whatever other more basic customization you desire to do on this little beast.

lghorn said:
adb is really (without a deeper technical explanation) an interface to allow you to run commands, etc. from your PC/Mac/Linux box on your phone's OS, as well as push/pull files, and what not. It's part of the Android SDK, and there are various wiki's and how-to's regarding installation, configuration, basic adb commands, etc. I'd not used it before yesterday, and got it d/l'd, installed, and running commands in <30 mins.
HOWEVER, you don't need to use adb to root. Read through the how to root & S-OFF thread in the MT4G General section (or find the video on YouTube) and follow the steps - there are adb and non-adb options. Once you get the 2 required files onto your phone, all you really need is to download the Visionary (r12) and Terminal apps. Terminal is available in the Market, and you can find the Visionary r12 apk online easily. Instead of adb from your computer you can just run the necessary commands directly on your phone using Terminal app.
Click to expand...
Click to collapse
You have any idea how to reboot into bootloader like the rooting instructions say? I've followed the instructions and did the terminal emulator way and it said to power down and reboot into something, can't remember, but I believe it was bootloader. However, I held the power button down and chose restart but was not presented with an option for rebooting into bootloader. Nevertheless, it rebooted but root didn't take.
It said to reboot into hboot to see if s is off.

This is really irritating the **** out of me. The root doesn't take and I follow the instruction exactly like they say. The only thing is they don't say how to reboot into hboot. However, I installed QuickBoot and rebooted into bootloader and saw that S was on. I have tried 2 times to make this rooting work and it has failed each time. The root folder is on the root of the sdcard. Visionary is installed and Terminal Emulator is installed. Everything is as it should be but this crap isn't working.
EDIT - I tried the file explorer way and it still failed. I tapped the root.sh file, waited 20 seconds and rebooted into booloader and the S is still on.

First disable "Fast Boot" under Menu > Settings > Applications. Then Power Off the phone. Once its off, hold the power plus volume down button.
Did you already receive the OTA update though? There were problems rooting without.

unremarked said:
First disable "Fast Boot" under Menu > Settings > Applications. Then Power Off the phone. Once its off, hold the power plus volume down button.
Did you already receive the OTA update though? There were problems rooting without.
Click to expand...
Click to collapse
No update received yet. Not even a hint of it coming. Thinking about taking this phone back also because crap isn't working with it. I'd rather be without than frustrated.
Is there a way to download the update and do it manually rather than wait for some fat slob in some office somewhere to get done eating and ****ting before he sends the update to me?
Eh...nevermind. Phone is going back. The data doesn't work. Can't get it to work either. The H shows up and the arros light up, but I only get a data error message when going to the Market...or anything that requires data.

Adding rooted features without rooting.

Side loading
Apparently there is an update that has to be pushed to your phone from AT&T, but hardly anyone has received it yet. People in this thread are working on adding this feature without the update. This method will allow you to install non android market apps, but so far it disables your mms capability.
http://forum.xda-developers.com/showthread.php?t=1111278
Free tethering/wifi hotspot
http://forum.xda-developers.com/showthread.php?t=980591
By changing a few settings, you can have tethering/use wifi hotspot without adding a tethering plan from AT&T.
Maybe we could add future developments to this thread as they become available. I like the idea of leaving my phone stock so that it will automatically update.

Are you talking about the "silent" OTA that enables side-loading?
If so, and if by hardly anyone, you mean "hardly anyone here on XDA," it may be because they are rooted or otherwise running a custom ROM that will prevent them from getting OTA updates.
If you mean hardly anyone here on XDA that is bone stock, well, that might be true. And it also might be true that the recently discovered method of enabling sideloading will help some people, who don't mind their mms broken until some workaround fixes it.
Or they can root, and be done with it. There's nothing that will ever be OTA that I would want to get OTA anyway -- it will be available here shortly after.
The only excuse people have to not root is that it *appears* to be difficult. It really isn't. You can enjoy the same exact phone with a stock ROM, but with the added perks that rooting brings. Yes, that includes sideloading. And SIM unlock. And no more bloatware.
However, if this sideloading trick can be perfected, and it will keep people who otherwise don't have the patience to root their phones and as a result would just screw them up, causing them to further not spend the time to read and search, instead firing off 1000's of redundant "Halp Me!" posts, then that's a good thing.

ehh I would just rather use adb.... (if I was stock)

mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Or that. My friggin' rant post from hell was long winded enough for me to forgo mentioning much more.

mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).

ST3ALTHPSYCH0 said:
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).
Click to expand...
Click to collapse
The adb method for sideloading an app is already discussed in mudknot's stickied guide.

Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..

Still stock here, without the non-market update.
No issues at all using the SWM. I didn't like that whole stupid "dropbox" method mentioned. It's easier and faster to just to use "disk drive" mode to copy the apk files onto the PC.

mudknot2005 said:
Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..
Click to expand...
Click to collapse
Absolutely agreed. Your guide should be reserved for known methods that provide the desired result without sacrificing other functionality.
I really don't see what all the excitement is about, regarding this new method. I mean, side loading has been a non-issue for rooted devices from the start, now it's *officially* a non-issue, even for bone stock devices.
This new method might have been a useful workaround for stock phones before ATT changed course on sideloading, now not so much.

Root LG G Stylo Boost 6.0

root confirmed. Basically keep running kingroot. If it reboots it didnt work. It will say it failed only. When you get the root failed msg, close app and then reopen. It will ask for permission to optimize a few things..grant it. Boom rooted. Unfortunately, root is lost if you reboot. About to try supersu me when i get off work.
Update- Supersu me seems to be uneffective
http://1drv.ms/1TgZCJm

Fingers crossed !

We're gonna need someone that has been down these type of roads before to help. I got supersu in and busybox in and removed kingroot through terminal, but when I tried to put in the supersu binaries, NO GO. I still think the wide release of MM to all LG will get more people onboard.

jmacie said:
We're gonna need someone that has been down these type of roads before to help. I got supersu in and busybox in and removed kingroot through terminal, but when I tried to put in the supersu binaries, NO GO. I still think the wide release of MM to all LG will get more people onboard.
Click to expand...
Click to collapse
I wonder if Dominick has even seen this yet? Seemed like he would have said something by now. Maybe I'll shoot him a text when I get a few.

I sent him one yesterday, no response

Man hope they can get it to stay after reboot

Tapping fingers....anxiously waiting....

waiting for status update..... please devs dont leave us hanging on lol we need yall

All this stuff is getting passed around and some have made reference to a dev here on the G4 that might have some answers, and others are optimistic on androidforums. I think and I may have stated it before, that the wide spread adoption of MM on LG will provide more help. I tried to get some info on the kingroot thread here, but they really are focusing on 5.1 and lower. The kingroot that we used here is for 5.1, theoathkeeperalpha kept on keeping on an it worked as a temp. The guys on androidforum seem to think that temp root and busybox and manipulating selinux is all that might be needed, except for some expertise on manipulating selinux. We, us that know little, can only keep the convo going. It is, I'm not buying a nexus to get root.

we will keep it alive till then...... phone isnt dead yet still has potential i am still as happy with it as i was day one..even after 2 times rma lol. just wish it had unlocked bootloader this version of phone needed it soooo bad

read a post dom is gone from here for now he left due to mods or something so our hopes are starting to go away as he was only one as of lately even trying to work on this phone.

There are quite a few, with much more experience than Dominic on, http://androidforums.com/forums/lg-g-stylo.3133/ , that are knee deep in what is going on. We knew there would be an impasse from the beginning if using any phone with MM without having an unlocked bootloader. But at least with temp root through kingroot, and some say one-click root from here, you can alter your build.prop and de-bloat some of the google bundle. So it's not like we are completely blocked.
When kingroot starts doing MM exploits then maybe we'll be saved. Kingroot has only done root up to 5.1 Lollipop, so they either get out of the future of they're money making game or set to work to exploit it. It's the same with the boss here at XDA, @Chainfire. Without an exploit for MM on phones without unlocked bootloaders (the vast majority, I might add) supersu slows forward progress. So an exploit of sorts WILL materialize when demand (MM enthusiasts) aren't spending money at supersu and kingrootland.

Bricked my phone. Sent it off to LG yesterday. I got all carried away with altering the build.prop and root-uninstalling google apps. I had disabled the apps previous to the kingroot exploit, and decided that now with temp root I would be O.K. Well, I started getting this google service quitting popup continuously and it un-nerved me enough to do a factory reset. I foolishly forgot to at least try to clean out all the kingroot and supersu files etc that were in there, and when it re-booted I couldn't get beyond wi-fi setup as when it attempted to hook up with my google account, the dredded google services stopped popped up. Even after reset. So off to LG. They were nice at 2:30 am and that was pretty cool. I hope they don't give me grief, but it was factory reset and the temp root was gone. So fingers crossed. @[email protected] did you ever find out how to check your bootloader? It seems to me the times I booted into recovery (volume dwn/power) and chose restart bootloader the phone would just reboot. If the bootloader was unlocked would it go into the bootloader menu? That's where fastboot would come into play. Anyway I'm going to be skiddish about messing around if and when my phone gets returned, like everyone else.

jmacie said:
Bricked my phone. Sent it off to LG yesterday. I got all carried away with altering the build.prop and root-uninstalling google apps. I had disabled the apps previous to the kingroot exploit, and decided that now with temp root I would be O.K. Well, I started getting this google service quitting popup continuously and it un-nerved me enough to do a factory reset. I foolishly forgot to at least try to clean out all the kingroot and supersu files etc that were in there, and when it re-booted I couldn't get beyond wi-fi setup as when it attempted to hook up with my google account, the dredded google services stopped popped up. Even after reset. So off to LG. They were nice at 2:30 am and that was pretty cool. I hope they don't give me grief, but it was factory reset and the temp root was gone. So fingers crossed. @[email protected] did you ever find out how to check your bootloader? It seems to me the times I booted into recovery (volume dwn/power) and chose restart bootloader the phone would just reboot. If the bootloader was unlocked would it go into the bootloader menu? That's where fastboot would come into play. Anyway I'm going to be skiddish about messing around if and when my phone gets returned, like everyone else.
Click to expand...
Click to collapse
I stopped using the stylo before I even found the temp root. So I wasn't afraid to screw it up lol. Same thing happened to me that happened to you and I flashed the file Dom posted the untouched 6.0 and it worked for me. Still tinkering and the stylo has pretty much become the phone that's teaching me my way around adb .
I bought the Irulu V3 6.5 inch screen 16gb ROM and 2 gigs ram off amazon for 149 bucks..don't let the price fool you..damn good phone so far! If you're around WiFi all the time like me you can get unlimited talk text and 100mb of web at airvoice wireless for 20$. Make sure you have good at&t service where you live . Its like a sore peter,you can't beat it.

[email protected] said:
I stopped using the stylo before I even found the temp root. So I wasn't afraid to screw it up lol. Same thing happened to me that happened to you and I flashed the file Dom posted the untouched 6.0 and it worked for me. Still tinkering and the stylo has pretty much become the phone that's teaching me my way around adb .
I bought the Irulu V3 6.5 inch screen 16gb ROM and 2 gigs ram off amazon for 149 bucks..don't let the price fool you..damn good phone so far! If you're around WiFi all the time like me you can get unlimited talk text and 100mb of web at airvoice wireless for 20$. Make sure you have good at&t service where you live . Its like a sore peter,you can't beat it.
Click to expand...
Click to collapse
You mean you flashed Dominic's untouched 6.0 on top of a bricked 6.0? I maybe should have tried that.

jmacie said:
You mean you flashed Dominic's untouched 6.0 on top of a bricked 6.0? I maybe should have tried that.
Click to expand...
Click to collapse
Yea, flashed right over the top

Been ghosting on this site for a while now, but now I should really start putting my 2 cents in.
Anyways, I had the G Stylo for VM and bricked it when I tried to replace the Kingroot binaries with SuperSU ones. Ironically enough, before I did that, It seemed that my root permissions didnt stick until AFTER my reboot. When I bricked I stayed up all night trying to get my phone back but was unsuccessful seeing as I also factory reset :crying: But I just got my second phone back from Best Buy after I had issues with my sim. Gonna go try to get kingroot back on it. Any tips for me prior? Weirdest thing is that this phone came from the factory with Marshmallow.. Connect at VM told me the manufacture date was January 1st. Running Ubuntu 15.10 and am struggling to get ADB backup to save a file that has a size higher than 0 bytes..

I got my VM Stylo from Best Buy too. It came with 6.0 as well. kingroot has not worked on it at all. Maybe that's a good thing...
Sent from my LGLS770 using Tapatalk

KrYmSiiN said:
Been ghosting on this site for a while now, but now I should really start putting my 2 cents in.
Anyways, I had the G Stylo for VM and bricked it when I tried to replace the Kingroot binaries with SuperSU ones. Ironically enough, before I did that, It seemed that my root permissions didnt stick until AFTER my reboot. When I bricked I stayed up all night trying to get my phone back but was unsuccessful seeing as I also factory reset :crying: But I just got my second phone back from Best Buy after I had issues with my sim. Gonna go try to get kingroot back on it. Any tips for me prior? Weirdest thing is that this phone came from the factory with Marshmallow.. Connect at VM told me the manufacture date was January 1st. Running Ubuntu 15.10 and am struggling to get ADB backup to save a file that has a size higher than 0 bytes..
Click to expand...
Click to collapse
I had trouble with Ubuntu 15.10 as well. Having better luck with 11.4. Hope this helps

Realistically i'll just skip the backups til i get root. Any news of getting into the bootloader? My first one would go into what I believe to be bootloader mode but still wouldnt come up under fastboot unless im getting things mixed up. And what are we using to flash on this pile?

US Cellular Galaxy S7 Edge [SM-G935R4] Thread

Wow, I'm sorta surprised there's not a USCC-specific thread anywhere yet...unless I just missed it, like I could well have.
Oh well, just thought it'd be nice to have a thread here at XDA, especially since it's so hard to find much of anything about USCC-branded phones in general anyway.
As far as my experience so far, I can't report any real issues beyond the usual so-so signal strength that I've experienced on every US Cellular phone me or my wife have owned ever since moving to my current location in town (yet it was fine at our old house just a few blocks over!). In the six years or so I've had USC, I've never found their phones being notably loaded down in bloatware, and nor is this one, so that's nice I guess. I was hoping I'd find some unlikely, overlooked USCC-specific perk like an unlocked bootloader on their models, but I don't see that happenin'... siiigh.
As for the phone itself independent of US Cellular, eh, I'm no power user, I'm probably not the dude who should make too many hardware-based critiques because the thing's more than powerful enough to ably do anything I'll ever need a phone to do. I will say I briefly owned an S6 Edge (briefly being because it was stolen) and I can't say the S7 seems like a huge upgrade to me, not one worth full retail anyway, but obviously it's a damn nice phone anyhow. (...But I went from my stolen fancy S6E down to an old, cheap Motorola Razr M (aka Electrify M) for a little over a year before getting my S7E and I was, for the most part, totally satisfied with the Motorola's performance despite the huge discrepancy in horsepower, so what the hell do I know?)
So yeah, bring on your USCC-specific guides, thoughts, questions, complaints, opinions, etc etc!

So I'll kick things off with a bit of root discussion/issues...
I rooted my phone maybe a week or so after getting it back in July, taking the chance against my better instincts that the instructions found over in this Verizon thread would work out for USCC phones too. Much to my surprise, not only did it work, I experienced almost none of the many problems that the Verizon users kept encountering in the early weeks of that thread. Why that is, though, I still have no clue. I guess VZW's software is somehow different from USCC's in such a way that we simply weren't affected by whatever kept causing the boot loops, extreme battery-drainage and heat issues for those phones. (Mostly...)
I don't want to steal the work of thread-starter psouza4 or anyone else in that existing Verizon thread so I don't want to try and rewrite every full detail but for any future USCC S7/Edge owners who might wind up here, I guess I'll do a real basic rundown of exactly how I did mine (and also I'll do it so that maybe someone more versed in Android-tinkering than me can tell me where I may have gone wrong on certain steps). The files I used in my root/fix/debloat process are the ones listed in Bold below and all can be found on that thread - I'd link 'em directly here but I don't know how kosher that is - and what isn't there should be in the Play Store.
So, after disabling "Secure Startup" under Settings-->Lock Screen & Security (and ensuring I had the correct drivers and ADB working and such), I...
1). Flashed the Samsung_G935x_QC_Rooted_BOOT.TAR image using the Odin3_v3.12_PrinceComsy.zip variant. The Verizon thread reports that some AT&T users had recommended the Comsy version because they found it prevented boot issues that they were experiencing when flashing with the other "plain" version of Odin that was linked. As for me, I only used the PrinceComsy version because the plain version simply doesn't run on my computer for some reason. I have no idea what the difference is between the two versions, so I've got no idea if the Comsy version may be the better way to go for USCC users as well (or if it even makes a lick of difference for anyone really), but it works.
2). After successful flash and reboot, I installed SuperSU-v.2.76-S7QC.zip via the included root.bat file and waited for another reboot to finish. I can't recall if SuperSU prompted me to download a newer version of the "su" binary upon opening the now-installed SuperSu app (as the original thread indicated it might) or not, but I didn't and neither should you apparently. As of the original post in the other thread on 7/15/2016, the "2.76-S7QC" build was the most recent version for S7 models . Since that's been over a month ago, can anyone verify if the current 2.78 version of SuperSU works with S7s (and/or USCC phones), or if there's a 2.78"-S7QC" version specifically? (I'm guessing no and no, but I lost track of the Verizon thread a while back and haven't seen any specific reference to 2.78 working or not working...)
3). From there, I downloaded FlashFire (v051, I believe) and flashed the suggested S7_or_S7Edge_Fixes_Debloater_V15.zip file, which aims to, y'know, fix some stuff and debloat the thing. I didn't manually adjust any of the "fixes" applied by the patch, and many of the apps and services killed by the "debloater" part of the script don't even come on USCC-branded versions of the phone. The instructions in the thread go on to say that some users reported problems with a handful of the fixes - Lag issues, Wifi passwords refusing to save, "Unauthorized Actions" pop-ups, and problems with VoLTE icons (the last of which isn't relevant to USC really anyway). While it seemed like the majority of VZW/ATT/other-carrier users in the thread were experiencing at least one of these issues, I didn't. There was some lag, for sure, but sporadically, and the remaining steps mostly knocked it out and I didn't need to do anything extra.
4). Next I installed a couple, but not all (initially) of the programs/settings suggested in the separate . Amplify Premium 3.3.7 and L Speed 3.1.9.7 (though I updated to the current 3.1.9.8 Beta shortly thereafter with no ill effects). Now I thought I followed the thread's suggestions pretty much exactly for these two, but when I looked just now to verify, I found that I hadn't made quite a few of the recommended changes in Amplify after all. (Probably because many of them give warnings when adjusting that the other entries hadn't, and I figured I'd play it safe). Anyway, I went ahead just now and finished everything up so that it does follow that thread's suggestions - I'll report back on it if they seem to make a notable difference. Maybe worth noting here that not all of the recommended changes are valid on US Cellular phones, so no need to worry if you can't find a few of them. As for L-Speed, I did indeed have all of the thread's recommended settings for it set, except for one, "Storage IO Tweaks: Partition Remount - Enabled." Not sure why this wasn't set, guess I just didn't see it the first time. Anyway, I've enabled it now, and since it seems to be there for "giving more permissions to the SD card," it was probably irrelevant to me anyhow since I don't currently use one.
Now, the guide suggests installing Xposed when you do all of this, along with three more apps - Greenify, ForceDoze, and LeanDroid. I decided to hold off on all the above for a while when I did it, but I'd say it's plenty safe to do it all in one go if you choose to. By the time I got around to applying the L-Speed and Amplify settings and rebooting, I had been up and rooted for at least a couple hours altogether, enough to notice that I wasn't seeing the immediate disasters a lot of other posters were finding. The most common problem seemed to be bootloops and random resets, which I hadn't encountered (and still never have really, beyond a couple of unexplained reboots once or twice that had no noticeable effects other than mild annoyance). There were also a lot of complaints about some rather extreme-sounding overheating, terribly reduced battery life, and serious lag problems - these all appeared in some degree, but seemingly nowhere nearly as bad as what people were reporting from their VZW/etc-branded phones in the thread. Plus, after making the L-Speed/Amplify changes, the battery seemed to be holding up a bit better, the phone wasn't running as warm as it had been pre-tweaking, and the lag I had experienced had calmed down from "pretty minor but definitely kinda annoying" to mostly gone. I wondered why I was missing out or getting much milder versions of all the problems mentioned by others, but by that point in the thread people were beginning to suspect Xposed was the cause. Some reported their phones working well up until installing Xposed, after which they'd begin getting bootloops or other problems. Not wanting any of that headache, I decided to just wait it out a few days and see how it held up before risking the install.
The guide also suggests at this point to turn off Wifi Scanning, Bluetooth, Location and Location History. I left the Location stuff alone, but this all seems pretty optional. It's also suggested to turn off the AOD Clock, which I left alone at the time but later disabled (and am now having issues with, but more on that later). I don't think there's any need to do the recommended disabling of all animations in Developer Options either, at least for our phones. I've left those settings at their defaults and speed's been fine.
So, since I basically took a break at this point when I was actually doing all this the first time, I'll take a break here too before getting into the next stuff I did regarding debloating and how my now-rooted-but-not-yet-real-tweaked USCC phone would turn out to actually run over the next few days...

I'm looking for a firmware which has european languages any idea?

Any new news on root and roms for our phones?

HavING trouble unlocking bootloader and flashing custom rom.
Is this possible yet? I've achieved root, But failed to flash twrp or cm. Any help would be appreciated!

lugnut2099 said:
So I'll kick things off with a bit of root discussion/issues...
I rooted my phone maybe a week or so after getting it back in July, taking the chance against my better instincts that the instructions found over in this Verizon thread would work out for USCC phones too. Much to my surprise, not only did it work, I experienced almost none of the many problems that the Verizon users kept encountering in the early weeks of that thread. Why that is, though, I still have no clue. I guess VZW's software is somehow different from USCC's in such a way that we simply weren't affected by whatever kept causing the boot loops, extreme battery-drainage and heat issues for those phones. (Mostly...)
I don't want to steal the work of thread-starter psouza4 or anyone else in that existing Verizon thread so I don't want to try and rewrite every full detail but for any future USCC S7/Edge owners who might wind up here, I guess I'll do a real basic rundown of exactly how I did mine (and also I'll do it so that maybe someone more versed in Android-tinkering than me can tell me where I may have gone wrong on certain steps). The files I used in my root/fix/debloat process are the ones listed in Bold below and all can be found on that thread - I'd link 'em directly here but I don't know how kosher that is - and what isn't there should be in the Play Store.
So, after disabling "Secure Startup" under Settings-->Lock Screen & Security (and ensuring I had the correct drivers and ADB working and such), I...
1). Flashed the Samsung_G935x_QC_Rooted_BOOT.TAR image using the Odin3_v3.12_PrinceComsy.zip variant. The Verizon thread reports that some AT&T users had recommended the Comsy version because they found it prevented boot issues that they were experiencing when flashing with the other "plain" version of Odin that was linked. As for me, I only used the PrinceComsy version because the plain version simply doesn't run on my computer for some reason. I have no idea what the difference is between the two versions, so I've got no idea if the Comsy version may be the better way to go for USCC users as well (or if it even makes a lick of difference for anyone really), but it works.
2). After successful flash and reboot, I installed SuperSU-v.2.76-S7QC.zip via the included root.bat file and waited for another reboot to finish. I can't recall if SuperSU prompted me to download a newer version of the "su" binary upon opening the now-installed SuperSu app (as the original thread indicated it might) or not, but I didn't and neither should you apparently. As of the original post in the other thread on 7/15/2016, the "2.76-S7QC" build was the most recent version for S7 models . Since that's been over a month ago, can anyone verify if the current 2.78 version of SuperSU works with S7s (and/or USCC phones), or if there's a 2.78"-S7QC" version specifically? (I'm guessing no and no, but I lost track of the Verizon thread a while back and haven't seen any specific reference to 2.78 working or not working...)
3). From there, I downloaded FlashFire (v051, I believe) and flashed the suggested S7_or_S7Edge_Fixes_Debloater_V15.zip file, which aims to, y'know, fix some stuff and debloat the thing. I didn't manually adjust any of the "fixes" applied by the patch, and many of the apps and services killed by the "debloater" part of the script don't even come on USCC-branded versions of the phone. The instructions in the thread go on to say that some users reported problems with a handful of the fixes - Lag issues, Wifi passwords refusing to save, "Unauthorized Actions" pop-ups, and problems with VoLTE icons (the last of which isn't relevant to USC really anyway). While it seemed like the majority of VZW/ATT/other-carrier users in the thread were experiencing at least one of these issues, I didn't. There was some lag, for sure, but sporadically, and the remaining steps mostly knocked it out and I didn't need to do anything extra.
4). Next I installed a couple, but not all (initially) of the programs/settings suggested in the separate . Amplify Premium 3.3.7 and L Speed 3.1.9.7 (though I updated to the current 3.1.9.8 Beta shortly thereafter with no ill effects). Now I thought I followed the thread's suggestions pretty much exactly for these two, but when I looked just now to verify, I found that I hadn't made quite a few of the recommended changes in Amplify after all. (Probably because many of them give warnings when adjusting that the other entries hadn't, and I figured I'd play it safe). Anyway, I went ahead just now and finished everything up so that it does follow that thread's suggestions - I'll report back on it if they seem to make a notable difference. Maybe worth noting here that not all of the recommended changes are valid on US Cellular phones, so no need to worry if you can't find a few of them. As for L-Speed, I did indeed have all of the thread's recommended settings for it set, except for one, "Storage IO Tweaks: Partition Remount - Enabled." Not sure why this wasn't set, guess I just didn't see it the first time. Anyway, I've enabled it now, and since it seems to be there for "giving more permissions to the SD card," it was probably irrelevant to me anyhow since I don't currently use one.
Now, the guide suggests installing Xposed when you do all of this, along with three more apps - Greenify, ForceDoze, and LeanDroid. I decided to hold off on all the above for a while when I did it, but I'd say it's plenty safe to do it all in one go if you choose to. By the time I got around to applying the L-Speed and Amplify settings and rebooting, I had been up and rooted for at least a couple hours altogether, enough to notice that I wasn't seeing the immediate disasters a lot of other posters were finding. The most common problem seemed to be bootloops and random resets, which I hadn't encountered (and still never have really, beyond a couple of unexplained reboots once or twice that had no noticeable effects other than mild annoyance). There were also a lot of complaints about some rather extreme-sounding overheating, terribly reduced battery life, and serious lag problems - these all appeared in some degree, but seemingly nowhere nearly as bad as what people were reporting from their VZW/etc-branded phones in the thread. Plus, after making the L-Speed/Amplify changes, the battery seemed to be holding up a bit better, the phone wasn't running as warm as it had been pre-tweaking, and the lag I had experienced had calmed down from "pretty minor but definitely kinda annoying" to mostly gone. I wondered why I was missing out or getting much milder versions of all the problems mentioned by others, but by that point in the thread people were beginning to suspect Xposed was the cause. Some reported their phones working well up until installing Xposed, after which they'd begin getting bootloops or other problems. Not wanting any of that headache, I decided to just wait it out a few days and see how it held up before risking the install.
The guide also suggests at this point to turn off Wifi Scanning, Bluetooth, Location and Location History. I left the Location stuff alone, but this all seems pretty optional. It's also suggested to turn off the AOD Clock, which I left alone at the time but later disabled (and am now having issues with, but more on that later). I don't think there's any need to do the recommended disabling of all animations in Developer Options either, at least for our phones. I've left those settings at their defaults and speed's been fine.
So, since I basically took a break at this point when I was actually doing all this the first time, I'll take a break here too before getting into the next stuff I did regarding debloating and how my now-rooted-but-not-yet-real-tweaked USCC phone would turn out to actually run over the next few days...
Click to expand...
Click to collapse
Any updates on how this is running on USCC devices.

It's running beautifully for me. I haven't went through the entire guide for the improvements with the extra apps, but root and xposed are perfect. I am using the ForcedDoze app and it does help, without causing any issues.
Sent from my SM-G935R4 using Tapatalk

barndawg76 said:
It's running beautifully for me. I haven't went through the entire guide for the improvements with the extra apps, but root and xposed are perfect. I am using the ForcedDoze app and it does help, without causing any issues.
Sent from my SM-G935R4 using Tapatalk
Click to expand...
Click to collapse
Hello? I'm new to USC. Want to get one off ebay. Seller says AT&T works on it. Does it mean phone is sim unlocked? Considering USC is CDMA?

I'm not sure about that. Check with the USC guys over at teamuscellular.com It should be possible, but I don't want to steer you wrong.
Sent from my SM-G935R4 using Tapatalk

Yikes, sorry for never finishing that initial post, everyone. Nonetheless, most of it would be outdated by now anyway, and though it ran well-enough for a while after some more tweaks that I never got around to describing here, it was still never a fully satisfying experience just due to the inherent jankiness of the Engboot root. (And it gradually ended abruptly in a softbrick). I haven't kept up with developments on S7 root at all really, though I thought I saw something in regards to a new root method a while back - anybody know on that?
Anyway, here's what I found works much better, though still Engboot-based - the Stang5liter custom ROM found here - https://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
All of the frequently found issues with Engboot root - heat, lag, battery life, etc. - were pretty much immediately greatly improved when I installed it. "Improved," not "gone" - they do still exist to a degree which some may find unacceptable, but if you don't expect 100% perfection, you shouldn't have any problem with it. The issue I notice most on this ROM is lag, but this tends to happen mostly only when attempting to do a lot of tasks quickly, opposed to just here and there all the time randomly the way it often seemed before I switched to the Stang ROM. Oh, and for whatever reason, it kinda frequently runs crappy while charging, but that's really a minor annoyance. The biggest plus of all, however, is that you don't need to waste hours tinkering with arcane settings like before to create minor improvements in performance - all the tweaks are integrated into the ROM, so you pretty much just install it and forget about it. Overall besides the lag I've been basically problem-free with it, especially in regards to heat, which I always had varying issues with on "plain" Engboot root. It's worth noting too that I'm still using the v1 version of stang5litre - v2 is current and was released a while back, I just never upgraded out of sheer laziness and the "good enough for me" status of v1. I will probably try to upgrade finally this week sometime, so if I do I'll note any improvements/problems here.
The caveat that you may have noticed here is that Stang5litre is a Verizon ROM intended for the SM-935V. The good news is that it runs just fine on our SM-935R4 without any adjustments - I don't think I even had to tinker with the APN. Your phone may exhibit some Verizony characteristics - your phone will identify itself as a Verizon phone, for one - but you should be good. If you want to root, this is the best way to go that I've found, plus it's quick and easy.
(Oh and hey, has USCC pushed Nougat yet?)

No, no nougat. No root for nougat anyway, so no real rush to see it.
Sent from my SM-G935R4 using Tapatalk

Any idea of when nougat will be released for this phone? I'm using one and live in Malaysia. Haven't receive nougat. Really want to have it. Dont really care about rooting, etc

A US Cellular version? In Malaysia? You are in the wrong thread my friend.
Sent from my SM-G935R4 using Tapatalk

Just wanted to let you guys know this works on our variant of the S7 Edge.
https://forum.xda-developers.com/showthread.php?t=3552824
I flashed with Flash Fire and mounted system as read/write without any issues and it definitely makes a big difference in sound output.
Try at your own risk!!, but is working on my rooted US Cellular S7 Edge running PK1 firmware. Gonna try the dual speaker sound mod next and will update here if it works.
The dual speaker mod also worked for me, link below. I am using windows 7 professional 64-bit.
https://forum.xda-developers.com/showthread.php?t=3494412
Here is something else I found that works on the the edge panel to control your music. I only tested with Spotify, as that is the music player I always use.
https://forum.xda-developers.com/showthread.php?t=3365528
Sentm my SM-G935R4 using Tapatalk
Sent from my SM-G935R4 using Tapatalk

huszonnegy said:
I'm looking for a firmware which has european languages any idea?
Click to expand...
Click to collapse
Hi, did you find a solution?

Anyone taken the Nougat update yet? Just wondering how its running for you, if so.
Sent from my SM-G935R4 using Tapatalk

My wife set the update to install tonight,I have yet update ,liking my rooted mm, will update on how she likes it in a few days.
Sent from my Nexus 6 using Tapatalk

Yeah, I'm kinda hiding out for a more stable Nougat root, but I don't thunk we'll see one.
Sent from my SM-G935R4 using Tapatalk

The wife took the update and is really liking her battery usage. Said it is lasting way longer before needing charged(no definitive proof here. just what she said). She is trying to get use to the ui changes. So i decided to go ahead and update mine as the last week or so it has been lagging more than normal and eating battery. So i downloaded our firmware from updato.com and flashed with odin 3.12.3 and used the home.csc so not to lose any apps and data(had everything backed up with titanium in case of issues). All went well and was running fine so i decided might as well root and see how that goes. Rooted using this thread https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 and i used the alternative root.bat listed in the op(post #688) i also did the suggested cache wipe and leave the phone for 5-10min, i waited at least 10 watching a youtube video. Have been running all day with no noticeable lag and decided to download Antutu and do a test,pulled a 132374. I know that benchmarks dont mean dudu but to me it verified it is running as fast and smooth as it seems. So far i have no complaints and have not found anything not working properly.

Just an update, the update and root on nougat apparently broke the fingerprint sensor. Only had 1 app I use that on so no biggy for me.
Sent from my SM-G935R4 using Tapatalk

Back To Stock On VS995 After A Couple Of Years Post-Dirty Santa - Couldn't Be Happier

I originally used the Dirty Santa routine on my Verizon VS995, so it remained on VS99513A for a couple of years. Had all manner of issues over time - apps "failing to respond", YouTube not displaying video but rather black screens, green-screen crashes, etc. Finally had enough and used the LGUP process to return to stock and unroot, of course. I probably (assuming, anyway) could have gone right to the latest Oreo firmware with LGUP, but decided to go to the stock version of VS99513A and then just do the many system updates to get current.
It's now happily sitting on Oreo, and knock on wood it's like having a new phone! It's so much smoother, YouTube is working, lol, battery life is an order of magnitude better and it's working like a phone should work. No one knows the future, of course, but today, I'm happy.
Just passing this along, but I've gone from being ready to trash this thing to being able to enjoy it again without worrying about having to dump some $$$ into something else.
I had originally rooted to get around the Verizon mobile-hotspot check, but I have an unlimited plan that includes it anyway, now, so that's no longer an issue.

Possible placebo effect...
A clean stock unrooted firmware may run smoother than a few custom roms, but not smoother than a rooted version of the exact same rom.
I wouldn't give up on root, even if the best ever unrootable phone was given to me for free (Ad-blocking being the primary reason)

Prowler_gr said:
Possible placebo effect...
A clean stock unrooted firmware may run smoother than a few custom roms, but not smoother than a rooted version of the exact same rom.
I wouldn't give up on root, even if the best ever unrootable phone was given to me for free (Ad-blocking being the primary reason)
Click to expand...
Click to collapse
Blokada DNS changer. Also working without root. All problems gone. :good: for me the main reason for root is to prevent screen retention. The sucked soooo hart. If there would be an option without root I would also go with an unrooted stock fw.

Prowler_gr said:
Possible placebo effect...
A clean stock unrooted firmware may run smoother than a few custom roms, but not smoother than a rooted version of the exact same rom.
I wouldn't give up on root, even if the best ever unrootable phone was given to me for free (Ad-blocking being the primary reason)
Click to expand...
Click to collapse
It's not even a close comparison in my case. Admittedly I'm on Oreo now and not the original Nougat the phone came with (and was rooted with), but it's literally a night and day difference. It wasn't just performance - it was extreme instability, apps that wouldn't work or would constantly go into "not responding" mode, green screens, battery life that was awful to the point where it nearly always needed to be connected to a charger, etc. I'd tap on an app or a function in an app before, and I'd literally have to wait and wait for something to happen at times.
Now? Lightning fast and smooth operation, stability where there was none before, etc. And, as stated, for what I really needed root before (bypassing vendor check for mobile hotspot), it's no longer an issue due to the phone plan I'm on.
I'm not knocking rooting, so don't misunderstand. But for my experience with this phone, going back to stock where I could actually update the version of the OS, as well, has made all the difference in the world for my user experience. YMMV.

Interesting... I haven't tried stock Oreo yet but in every time I flash a new stock rom the phone runs great for 6 months then starts lagging.

oooh meee TOOO! me! meeeee!
Heyitsrick said:
I originally used the Dirty Santa routine on my Verizon VS995, so it remained on VS99513A for a couple of years. Had all manner of issues over time - apps "failing to respond", YouTube not displaying video but rather black screens, green-screen crashes, etc. Finally had enough and used the LGUP process to return to stock and unroot, of course. I probably (assuming, anyway) could have gone right to the latest Oreo firmware with LGUP, but decided to go to the stock version of VS99513A and then just do the many system updates to get current.
It's now happily sitting on Oreo, and knock on wood it's like having a new phone! It's so much smoother, YouTube is working, lol, battery life is an order of magnitude better and it's working like a phone should work. No one knows the future, of course, but today, I'm happy.
Just passing this along, but I've gone from being ready to trash this thing to being able to enjoy it again without worrying about having to dump some $$$ into something else.
I had originally rooted to get around the Verizon mobile-hotspot check, but I have an unlimited plan that includes it anyway, now, so that's no longer an issue.
Click to expand...
Click to collapse
Between the GIGANTIC pain in the ass that it was to root this phone (I have a VS995 rooted and on 13a ever since) and all the problems that rooting has caused I'd be ready to undo it all anyway. But due to some problem with internal storage* that started a couple weeks ago, I was fed-up and factory reset the phone. When it boots normally, a check in "about" shows the software status as "modified" but root checker says its not rooted, superSU can't find root (I installed it from play store).. Tried to update via the "system updates" in settings (could not get it to show developer options either).
* The storage issue: I have 50 gigs internal (or something similar) and I get a message that the storage is full and some apps may not work. Not possible, but I humored it and uninstalled everything, cleared cache, downloads cleared, etc ... still showing +/-1 gb free space avail. Factory reset, appears stock, but free space STILL less than 1 GB.
Regretted rooting this phone almost immediately since I still couldn't get rid of certain apps, I had to deal with the camera issues, etc... The only thing positive about it was that my work was unable to install their MDM crap (Mobile Iron shielding Gsuite etc). But anyway, it doesn't look like I'll be able to update the system - I tried it and now it boots to twrp, or boots regularly and then loops around to twrp again. I'm looking for the easiest way to get the phone working (with the persistent problem of internalstorage being full for no reason fixed) and at least reasonably updated. Don't care if it's rooted or not really.
Do you or does anyone have a link to a "play by play" for whatever might work? Its been too long since I rooted it for me to remember the nuances of the procedure so its safe to say that I don't really understand how Android works all that well, so instructions like, "flash xxx 3.2 then flash back to 2 then fastboot and load yer ROM but don't forget the dalvik blah blah" won't work... I'm looking for the idiot's version with hand-holding and everything.

Interesting analysis................ I mainly rooted my older phones due to the need for the mobile hotspot without paying VZ extra charges. However, now that I have the VS995, I was able to download and use the Foxfi app (I paid for the Pro upgrade license) so this left me thinking, do I really need to root my V20 at all? In the past, you couldn't run apps that ran many WIFI tools and other tech'y things, but it seems much of that has changed. I don't run custom ROMs so maybe I don't need to root. Would be glad to hear rebuttals on the subject

I received a new VS995 last week and I flash h910 to get FM radio. I could not be happier as I'm on OREO and the device is working perfectly without any issue whatsoever and with latest mk2000 kernel (2.2 beta) general interface performance is working very well - as it should. Hotspot needed a little workaround bit it wasn't too difficult. I wouldn't dream of going back to stock!
https://forum.xda-developers.com/showpost.php?p=79939652&postcount=269
I know it's not straight to bootloader unlock and root this phone but it's worth the trouble. I hope my new fone will last and last untill manufactures change mind about removable batter and horrible new aspect ratio! No thanks V30 !

You're right.
There's no good reason to root the v20. Even rooted you can't do things that other phones can do, like enabling monitor mode on the Wi-Fi. Nor have I been able to get an external Wi-Fi adapter to work on it.

0per said:
There's no good reason to root the v20. Even rooted you can't do things that other phones can do, like enabling monitor mode on the Wi-Fi. Nor have I been able to get an external Wi-Fi adapter to work on it.
Click to expand...
Click to collapse
YOU ARE WRONG.
AD BLOCK Yeah they have rootless ad block but they work like ****
screen burn fixes. hows the ghosting?
titanium backup still best option for absolutely all apps getting backed up.
Sorry i have run root too long i cant live without it anymore.

is this happening to just verizon version of LG V20? anyone?
is this happening to just verizon version of LG V20? anyone?