Database Info

G Tablet coming tomorrow...would like to get some things set straight. Thanks.

Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.

Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...

"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.

Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.

Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.

I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.

Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update

hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas

rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..

dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.

hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning

I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!

hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.

rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing

I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.

Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...

Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.

ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will

I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.

Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom

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

Desperately in need of quick help with my OnePlus One.

I haven't used my OnePlus One in several months since I got my Nexus 6. I've been meaning to sell my OPO, but got lazy about it. Now I can't be, and I need money for rent. A friend/co-worker who's in serious (in my opinion) need of a new phone wants to buy it off me.
My OPO was on LiquidSmooth 4.4.4 but obviously it's out of date, so I tried to update it. I tried once before to update it with a 5.1 ROM, but it kept failing. I remember there was something about the firmware or baseband version that needed to be flashed to go from KK to LP, but it was several months ago, and I can't remember what exactly it was. And for the life of me, I can't find it.
I tried to find what it was, and in my searching I found that CyanogemMod Official 13 had a built-in baseband updater. So that's what I tried. TWRP version was/is 2.8.7.0. Maybe that was the problem?
Anyway, CM13 (the most recent snapshot) installed, seemingly fine, but it won't recognize my SIM card. I try reinstalling it, and it still won't recognize the SIM. Moreover, it doesn't even detect a cell signal (it should, as all cell phones in the US are required to have 911 emergency access, even if you're not actually paying for phone service). And then it starts rebooting. Not a bootloop, because it boots. Then a few minutes later, it reboots. Continuously.
So I try a different ROM. The latest Resurrection Remix (I have it on my Galaxy S4 and it works fine). Same thing.
The even weirder thing is that I figure I should just restore my latest nandroid, but it's not there. In fact, nothing's there. Nothing visible through TWRP's file manager or backups. Not even old pictures, which I didn't delete. I didn't delete any storage (because I wanted my backup, just in case, duh). But TWRP still shows that there's 26GB available. So obviously, there's something there. I just can't see it. My fault for not saving the nandroid elsewhere, but Humpty Dumpy has already fallen.
I have Wugfresh's toolkit (yeah, yeah, I know...), and tried restoring it to stock, and it won't do it.
I've used ADK in the past, but it has been way to long for me to remember specifics, and it has apparently been updated with the newer Android versions. Obviously, I've looked at the sticky thread about restoring your OPO to stock, but it hasn't been updated in a while. So I'm worried about using those instructions. I've looked up youtube videos, and they're all too old as well. I'm also worried that I'd be using the wrong version of ADK. I'm not scared of using ADK, as long as the instructions are correct and clear. I'd be using Windows 8, if that matters.
So what I'm asking (begging) for is instructions on how to make this phone work properly again. Quickly. I've tried doing the research myself, and haven't found my solution. I'd keep at it, but time is getting short, and I can't afford that. Literally. I can't afford the hours spent (it's 1am and my the office closes at 4pm), and I can't afford being late on my rent. A couple weeks ago I spent way too much up in Phoenix to go see Guns N' Roses (at least I got a kickass T-shirt). Entirely my fault. Also my fault for not realizing how desperate my financial situation was about to be, and for waiting to ask for help until now. And I'm not going to ask to borrow money. I just can't.
Finally, and I know it's taboo to ask "what's the best ROM?", because I've answered that question myself with "there isn't one - try them out for yourself and find which one's best for you". But as I said, I'm out of time., and I haven't been keeping up with what's going on with OPO's development. My friend is not like us. His phone's a LG cheapo POS from years ago that's on 4.1JB. He uses it for calls, texts, and podcasts. He doesn't need root, or even custom recovery for that matter. In fact, I'd prefer if it didn't have root (although custom recovery might be nice, just in case). So if I can get this damn thing working properly again, what'd be a good ROM for my firend? OPO's official Oxygen? Are they still updating it? Stability is the primary concern, but if there's something that gets regular (and stable) updates, that'd be good too. With an updater that's built-in, simple, and wouldn't need and XDA forumite to do it for him. Because it'd be nice that he could get updates with Google's security patches. But since he's still using a 4.1 phone, he's obviously not all that concerned about that issue. But still, that'd be nice.
Thank you (fingers crossed).

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?

Is this to go to phone for roms as of August 2020?

Looks great spec wise: microSD, no notch garbage, headphone jack.
I need something to replace my OP5 and need a headphone jack and microSD slot.
How is linageOS and flashing? Fairly simple or is it one of those really complicated phones?

I recently got this phone, and the phone itself is pretty great. The flip camera is amazing, and I impress everyone I go to take a selfie with.
Flashing LOS 17 is pretty normal I'd say. This was my first A/B device so it took a bit of getting use to, but a few tries, and I got it down.
As far as support, I think this phone has been pretty lucky to have as these people working on it, like luca for the LOS build, mauronofrio for his 9.0 TWRP builds, and bigbiff for this current TWRP builds, just to name a few. (Thanks to everyone out there helping as well!)
However, as always, the information on some of the details about this phone are scattered around the internet, and its taken me a few weeks to get a good grasp on what my options are with this phone, and some things im still not clear on. Sometimes, a particular detail is only mentioned once in one specific thread, and I guess there just arent enough users with this phone to spread the information around.
Specifically, this is some information I wish I knew about before I tried flashing this phone:
- On LOS 17 (the Android 10 versions), you will have a horrible camera experience. Not sure if its just me, but I havent found a camera app that works correctly, and has modern features like save to SD card / panorama / slow motion / etc. You would think the flipping camera would be the problem, but that actually works fine! One thing that seems completely botched is autoflash. I know nobody probobly uses autoflash, but it seems to use flash at random, in any camera app. The stock lineage camera app is extremely basic, and the quality isnt as great as stock, but if you can live with ONLY pictures and video, then I guess it works (autoflash still doesnt work). There are a couple of GCam ports. I havent tried them all, but they are patchy. The best one I tried only didn't have slow motion working (and autoflash). To my knowledge, there is no way to get the stock Asus camera app on LOS 17. There is, however, a flashable zip for the Asus camera for LOS 16 (Android 9), but that leads me to the next point.
- LOS 16 is a major pain to flash. I am actually going to try and flash LOS 16 right after this, so wish me luck. Ill update this if it goes well. Something is wrong with flashing these versions of LOS. I don't fully understand, so I dont want to say something wrong here and spread misinformation. The steps dont seem to be the same as flashing LOS 17. There are sometimes issues mounting partitions, and some people mention using the unofficial mauronofrio builds over the offical builds for some problem with encryption? Trying to boot into the Lineage Recovery for the 16.0 builds takes like 10 minutes, I almost thought my phone was just stuck, but leaving it there long enough, it finally opens recovery! Its just a pain. Lineage sometimes doesnt work if it wasnt installed using its own recovery, so i try to install LOS with LOSRecovery, and then switch to mauronofrio TWRP to install gapps, magisk and the asus camera app, but i havent gotten a working flash yet. I have to keep trying different combonations and it just takes forever for recovery to start and to flash things in the right order.
-There was an update released for this phone for Eastern countries for VoLTE/VoWifi, but it never made it to the west, and someone said they spoke to Asus, and said they dont plan to release that here (in America, canada, etc) Im not even sure if euro countries got it, but dont quote me on that. Point is, this phone _can_ use VoLTE/VoWifi, but you have to enable it yourself. This amazing man has a guide for the ROG Phone II, but i followed his steps, and it works perfectly on the Zenfone 6! https://forum.xda-developers.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073
Shoutout to HomerSP. Thank god this works. Why Asus wouldnt ship this phone without VoLTE amidst the 3G shutdown, i have no idea, but this features seems almost necessary to make and receive good quality calls anymore. So yea, if you get it, follow his guide. You need root for most of the steps. It seems complicated but its very easy if you just sit down and do it.
Uh yea, thats what I can think of right now.
Sorry for the wall of text.
I wish this phone was perfect, but flashing LOS and getting everything working correctly is taking me a while to figure out. I don't understand why I cant get LOS 16 to work, but If i get something working Ill post what I did incase anyone else is searching for an answer like me.
For anyone else looking to get this phone, Im starting to think just sticking with Stock firmware with Magisk is the way to go. Killer chipset, amazing cameras and app, 3.5mm, duel sim AND SD card (seriously wide tray, 3 slots!) The only thing this is missing is an AMOLED (if you prefer) and Band 66+71 (T-Mobiles best bands aside from 5G)
Alright, enough of my ranting. Message back with any questions, ill do my best to respond.

bobs50000 said:
I recently got this phone, and the phone itself is pretty great. The flip camera is amazing, and I impress everyone I go to take a selfie with.
Flashing LOS 17 is pretty normal I'd say. This was my first A/B device so it took a bit of getting use to, but a few tries, and I got it down.
As far as support, I think this phone has been pretty lucky to have as these people working on it, like luca for the LOS build, mauronofrio for his 9.0 TWRP builds, and bigbiff for this current TWRP builds, just to name a few. (Thanks to everyone out there helping as well!)
However, as always, the information on some of the details about this phone are scattered around the internet, and its taken me a few weeks to get a good grasp on what my options are with this phone, and some things im still not clear on. Sometimes, a particular detail is only mentioned once in one specific thread, and I guess there just arent enough users with this phone to spread the information around.
Specifically, this is some information I wish usenew about before I tried flashing this phone:
- On LOS 17 (the Android 10 versions), you will have a horrible camera experience. Not sure if its just me, but I havent found a camera app that works correctly, and has modern features like save to SD card / panorama / slow motion / etc. You would think the flipping camera would be the problem, but that actually works fine! One thing that seems completely botched is autoflash. I know nobody probobly uses autoflash, but it seems to use flash at random, in any camera app. The stock lineage camera app is extremely basic, and the quality isnt as great as stock, but if you can live with ONLY pictures and video, then I guess it works (autoflash still doesnt work). There are a couple of GCam ports. I havent tried them all, but they are patchy. The best one I tried only didn't have slow motion working (and autoflash). To my knowledge, there is no way to get the stock Asus camera app on LOS 17. There is, however, a flashable zip for the Asus camera for LOS 16 (Android 9), but that leads me to the next point.
- LOS 16 is a major pain to flash. I am actually going to try and flash LOS 16 right after this, so wish me luck. Ill update this if it goes well. Something is wrong with flashing these versions of LOS. I don't fully understand, so I dont want to say something wrong here and spread misinformation. The steps dont seem to be the same as flashing LOS 17. There are sometimes issues mounting partitions, and some people mention using the unofficial mauronofrio builds over the offical builds for some problem with encryption? Trying to boot into the Lineage Recovery for the 16.0 builds takes like 10 minutes, I almost thought my phone was just stuck, but leaving it there long enough, it finally opens recovery! Its just a pain. Lineage sometimes doesnt work if it wasnt installed using its own recovery, so i try to install LOS with LOSRecovery, and then switch to mauronofrio TWRP to install gapps, magisk and the asus camera app, but i havent gotten a working flash yet. I have to keep trying different combonations and it just takes forever for recovery to start and to flash things in the right order.
-There was an update released for this phone for Eastern countries for VoLTE/VoWifi, but it never made it to the west, and someone said they spoke to Asus, and said they dont plan to release that here (in America, canada, etc) Im not even sure if euro countries got it, but dont quote me on that. Point is, this phone _can_ use VoLTE/VoWifi, but you have to enable it yourself. This amazing man has a guide for the ROG Phone II, but i followed his steps, and it works perfectly on the Zenfone 6! https://forum.xda-developers.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073
Shoutout to HomerSP. Thank god this works. Why Asus wouldnt ship this phone with VoLTE amidst the 3G shutdown, i have no idea, but this features seems almost necessary to make and receive good quality calls anymore. So yea, if you get it, follow his guide. You need root for most of the steps. It seems complicated but its very easy if you just sit down and do it.
Uh yea, thats what I can think of right now.
Sorry for the wall of text.
I wish this phone was perfect, but flashing LOS and getting everything working correctly is taking me a while to figure out. I don't understand why I cant get LOS 16 to work, but If i get something working Ill post what I did incase anyone else is searching for an answer like me.
For anyone else looking to get this phone, Im starting to think just sticking with Stock firmware with Magisk is the way to go. Killer chipset, amazing cameras and app, 3.5mm, duel sim AND SD card (seriously wide tray, 3 slots!) The only thing this is missing is an AMOLED (if you prefer) and Band 66+71 (T-Mobiles best bands aside from 5G)
Alright, enough of my ranting. Message back with any questions, ill do my best to respond.
Click to expand...
Click to collapse
Hot damn this was an excellent read. I will say I'm deathly afraid of this new A/B partition nonsense. I swear google did it just to screw with us modders. I don't mind putting some work in but I hate when it feels like I'm flying blind in a volcano lol.
I debated the OP7 Pro, but not having and SD card slot or a 3.5mm jack is just unacceptable at this point honestly.
I do prefer IPS, but I would hate to miss out on 66+71 ...dang that stinks
So it looks like this phone is a strong maybe, might just be the best I guess as I can't find any other better options. Though maybe I should look at the ROG Phone II?
Let me know how LOS16 goes if you don't mind, especially if it fixes the camera.

Alright. I know it's been a while since my other post, but I wanted to leave my latest here for any body else reading.
I could not get LineageOS 16 to work at all. The best I was able to get was LineageOS 16 booting, getting to the first time setup saying "Just a sec...", and then a black screen. Holding the power button or using the volume buttons caused the side controls to show up, like the "Power off", "Reboot", or the volume slider to appear, but the rest of the screen was black. After about a minute or two. It would actually freeze up, and restart. But that was it. I mentioned it in my other post, but the recovery for LineageOS 16 takes 5 minutes to boot, I timed it. Its unusual, something must be wrong.
So my options were LineageOS 17 (Android 10) with a horrible camera, or Stock ZenUI (also Android 10).
So I'm choosing Stock, so that I can have a decent camera experience. I really wish I could have LineageOS on this phone, and is one of the major reasons I bought this phone, but the camera app on LOS 17 breaks it for me. I'm just going to have to put up with Stock shenanigans and limitations.
Because I have been flashing so many different times, the state of my device is quite messy. I've been following these steps I wrote down to get a good install every time:
Boot into the bootloader
Use flashall.cmd to revert Slot A back to Android 9 ZenUI v1906.167
Without entering the system, boot into recovery
I edited the end of flashall.cmd so that it wouldn't automatically reboot to system
Apply the ZenUI v1909.194 update, which will end up in slot B
While still in the recovery, use the "Wipe data/factory reset" option
Boot into the bootloader, then back into recovery, to end up in slot B
Reapply the ZenUI v1909.194 update, which will now end up in Slot A. Both slots now have ZenUI v1909.194
Wipe data/factory reset
Bootloader, recovery, your in slot A
Apply the Android 10 ZenUI update, which ends up on slot B
Wipe data/factory reset
Bootloader, recovery, your in slot B
Reapply the Android 10 ZenUI update, which ends up on slot A. Both slots now have Android 10 ZenUI
Wipe data/factory reset
Go into the bootloader once more to get into slot A
Boot into the latest TWRP for Android 10
Swipe to allow system modifications
Check to make sure there are no mounting errors in the log
Flash the TWRP installer
Flash the latest Magisk
And your all done! Reboot to system.
Swipe to install the TWRP app on your way out
flashall.cmd is from the Sevice Firmware zip I downloaded from somewhere. It was in an unbricking guide, but It helps me by downgrading to Android 9, and setting up the partitions correctly again, in case they got messed up (which they have been throughout my testing)
The ZenUI updates I downloaded directly off of Asus's support page for this phone. You just have to pay attention to the fact that these are incremental updates, and need to have a specific firmware already installed in order to be flashed correctly (They say which once in the description). They also only can be installed with the stock recovery. (or at least, twrp never got very far when trying to flash them). I'd say just stick with the stock recovery for installing updates.
Speaking of TWRP, it has issues with restoring backups. It normally ends up with an error like "TarFork() Error 255", but apparently that can mean a bunch of different problems, so its not very helpful. I found that if you want any chance of the backup being restored correctly, you need:
- To be on the same Android version the backup is for (Android 9 restoring Android 9 / Android 10 restoring Android 10 / etc)
- Make sure TWRP doesn't have any mounting errors. This seems obvious, but most times, I had issues where TWRP couldn't mount a partition for some reason.
- You MUST have the option "Use rm -rf instead of formatting" enabled. I never got a backup to work without it enabled
Even after all that, sometimes the backup STILL wont apply. Once a backup fails to apply, nothing will work until I flash the service firmware and incremental updates again in order to try again. It's very time consuming.
Now, I don't know as much as I probobly should about linux or android, but that last option makes me tells me that instead of actually formatting / recreating the correct partitions, it just deletes all files and puts back the ones from your backup. That works great and all, but if the partitions get messed up somehow, the only way I know to restore them is by flashing the stock ZenUI updates in order (Service Firmware -> ZenUI v1906.167 -> Android 10 ZenUI). To add to the confusion, I'm not actually sure if TWRP backups/restores include both slots, or just the slot you are on. For good measure, I make sure to update both slots evenly, so that they end up with the same firmware version, however, I have only flashed one slot per update, and gotten a backup to work also. For example, instead of flashing each update twice, to get it on both slots, I have only flashed each update once, so that Slot A gets the service firmware, then flashes slot B with Android 9, then flashes slot A again with Android 10, and then restore, and It works. Its all very confusing and seems inconsistent. Maybe I'm missing an important detail, but I can't figure it out.
One last thing about restoring backups. I have a hunch that going through the first-time setup of the phone (specifically, adding a figerprint/pin) does something to the system or data partition. Whenever I was restoring a backup, I had a better chance of it working if I went through first time setup, and skipped adding a fingerprint/pin. I would then get to the home screen, and restart into recovery to restore.
Sorry if this is confusing to read. I'm kinda just dumping all my information for me or someone else to read later if they are as frustrated as I am now.
I wish it would all just work, or at least give more descriptive errors. Trying to google any leads I find reveal almost nothing. I feel like If I'm not a retired developer, there's no way to understand any of this.
Also, if you know how something works better than I do, or if I'm explaining something wrong here, please let me know! Really, I need all the help I can get on these topics.
Uh yea, so that's all I got. I have my fingers crossed that all the pieces can come together for this phone, but I know its going to take a long time if its going to happen at all. The Zenfone 7/Pro just got announced(released?) and maybe everyone will just abandon the 6 now. That seems to be the trend now anyways.