Database Users

SM-G920R4 US Cellular 6.0.1 Root

If anyone wants to root their US cellular S6 Smg920r4 on 6.0.1, I know there's no section here for US Cellular, but this works perfect. It's the Sprint TWRP 6.0.1 Marshmallow root method. Just follow the instructions in the Sprint thread. Root in minutes thru Odin. Hope it helps someone else like me who was looking and looking for Sm-g920r4 specific root.
http://forum.xda-developers.com/spr...ide-how-to-root-marshmallow-sm-g920p-t3338694

I've got xposed running with a few modules that are stable and somewhat supported on marshmallow. Again it's super easy to root your stock firmware on your US Cellular SM-G920R4 Galaxy S6. If anyone has any questions, please let me know. Thanks

Twrp
My s6 won't boot into system it boots into twrp recovery. And I did make a backup of my phone with Smart Switch and now Smart Switch tells my device is not supported. Any solutions?

What firmware were you on? Were you already on 6.0.1 and did you get it fixed yet

How did you get Xposed to work? Did you have to use a custom rom? If so what one did you use?

thank
Thank to me

I'm still hesitant to pull the trigger on this. I see questions being asked about things that I don't fully feel comfortable stressing about. Was this a successful way to root or a fluke that may work for some?

how to install edge screen on s6, just like s6 edge

dee3 said:
If anyone wants to root their US cellular S6 Smg920r4 on 6.0.1, I know there's no section here for US Cellular, but this works perfect. It's the Sprint TWRP 6.0.1 Marshmallow root method. Just follow the instructions in the Sprint thread. Root in minutes thru Odin. Hope it helps someone else like me who was looking and looking for Sm-g920r4 specific root.
http://forum.xda-developers.com/spr...ide-how-to-root-marshmallow-sm-g920p-t3338694
Click to expand...
Click to collapse
Hi? Still got this phone?

MyQuickVw said:
How did you get Xposed to work? Did you have to use a custom rom? If so what one did you use?
Click to expand...
Click to collapse
i also haven't been able to get xposed framework installed. it just bootloops each time i've tried. i have got it rooted and twrp installed though. any know how to get xposed framework on us cellular / cspire?

I was able to root my device though a youtube video by "android doctor" but was not able to get his 7.0 ROM to load on my G920R4. Does anyone have a ROM they WERE able to work on this S6 variant? Thanks

cweatherford7 said:
I was able to root my device though a youtube video by "android doctor" but was not able to get his 7.0 ROM to load on my G920R4. Does anyone have a ROM they WERE able to work on this S6 variant? Thanks
Click to expand...
Click to collapse
This S6 doesn't get that much love. It needs more love though.

iRiceCookr said:
This S6 doesn't get that much love. It needs more love though.
Click to expand...
Click to collapse
For sure. US Cellular is small beans compared to the other major companies so its always been hard to find it. This is the first device I have ever struggled to find a way to do it though. All other took work, but this one is the only one so far that has been impossible.
I was able to get his ROM loaded onto my phone but there was a spot where I had to "select CSC" and US Cellular wasn't listed as one of them. I think T-Mobile and Rogers were the only USA companies that it had. Maybe I should have tried it by selecting T-Mobile or Rogers but I just didn't really know what to do. The one that I tried (which was a UK CSC - because it mentioned something about selecting it if yours wasn't listed..but I believe it was only talking about UK companies not listed) wound up getting the ROM to load but I had NO touch screen capabilities.
After 6 hours of getting that that point and having to reload the official Samsung ROM, I gave up and went to bed.
I wish I could find someone that has been through this already to lean on for some assistance but with this phone, it seems like no one has been first. Maybe that is my purpose in life.. But then again, I also don't want to completely brick my phone in the process. Maybe I'll try again tonight.

I have yet to find a simple guide on "How to load a custom ROM on your AT&T S7 Edge"

I have yet to find a simple guide on "How to load a custom ROM on your AT&T S7 Edge"
I've traveled all over the interwebs, including this website and many others but have not found a simple guide for noobs. I read about CWM, TWRP, Odin, rooting, zip files, tar files, nandroid, backup ROM, root with app, root via computer, blah, blah, blah, blah....
All I know is that before I do anything I want to backup the stock ROM but before that I'm thrown all kinds of different tools and processes that one could use. For the noob it should be as simple as:
Step 1: backup your stock ROM and to do this download/install this tool then follow these instructions.
Step 2: root your S7 Edge and to do this download/install this tool then follow these instructions.
Step 3: find a custom ROM you want to install and to do this go here, here or here for you model and download it to your PC.
Step 4: flash your custom ROM and to do this down/install this tool and follow these instructions.
Maybe I haven't done a good job of searching so shame on me but I don't feel like given the effort I've expended thus far has yielded a straight and easy answer when it probably should be. I seem to run across a lot of promising reads/threads about this only to find that there seems to be so much more knowledge and experience with the SM-935F and not so much with the SM-935A variant. On top of it, it would seem that I'm told that rooting will or will not break Samsung Pay and other apps/features or that the flag will or will not permanently trip that shows the device has been modified. Very confusing.
When I'm presented with a tar/zip download I'm not sure to where I'm supposed to be downloading. To my PC then used Odin s/w on the PC to install via USB cable to the handset?
Can someone please point me to the simple guide to get this going...or am I gonna have to write it myself? TIA.

BTW, I should note that I'm coming from a S3 on Virgin Mobile to a S7 Edge SM-G935A to be used on Cricket Wireless (AT&T). Since I'll be on Cricket and not directly a AT&T customer per se I'd like to get rid of all the bloatware that AT&T was so kind to load up on the handset. Right now it has Nougat 7.0 installed: samsung/hero2qlteuc/hero2qlteatt:7.0/NRD90M/G935AUCU4BQA6

I am not sure if you have a US version the S7 (Qualcomm G935A) or the S7 non US version. But if you have the US version, we are out of luck. Our bootloader is completely locked and all those steps you pointed out are not available.
Sent from my SAMSUNG-SM-G935A using Tapatalk

freeop said:
I am not sure if you have a US version the S7 (Qualcomm G935A) or the S7 non US version. But if you have the US version, we are out of luck. Our bootloader is completely locked and all those steps you pointed out are not available.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
So it seems that with all USA Qualcomm versions regardless of GSM carrier you have confirmed we pretty much cannot do much other than load some other versions of firmware such the U version ROM? From what I read HERE this is the Marshmallow 6.0 o/s. I currently have the stock Nougat 7.0 firmware from AT&T on my S7 Edge. Is there a debloated 7.0 version of the U ROM available?
UPDATE: Never mind...I came across THIS THREAD regarding an unbloated 7.0 U-version. I see you were active in that thread so now I need to read the entire thing before I have more questions and if so I'll ask them there. Thanks!

SyberTiger said:
So it seems that with all USA Qualcomm versions regardless of GSM carrier you have confirmed we pretty much cannot do much other than load some other versions of firmware such the U version ROM? From what I read HERE this is the Marshmallow 6.0 o/s. I currently have the stock Nougat 7.0 firmware from AT&T on my S7 Edge. Is there a debloated 7.0 version of the U ROM available?
UPDATE: Never mind...I came across THIS THREAD regarding an unbloated 7.0 U-version. I see you were active in that thread so now I need to read the entire thing before I have more questions and if so I'll ask them there. Thanks!
Click to expand...
Click to collapse
If you still want to root your phone, you can follow this link and will let you get rid of all the bloat and root your phone, install xposed and all the mods for xposed. I have used the ENG.IMG version of root for the G935A over 6 months ago and it works great, given the choices we have.
Here's the link: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
I know the thread is in the T-Mobile section but if you read the first line, it says it works for T-Mobile, ATT, Sprint, Verizon, etc. It is a very long thread but if you read mostly the later posts from @Craz Basics and you will be able to see that it works really nice.
Good luck

freeop said:
If you still want to root your phone, you can follow this link and will let you get rid of all the bloat and root your phone, install xposed and all the mods for xposed. I have used the ENG.IMG version of root for the G935A over 6 months ago and it works great, given the choices we have.
Here's the link: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
I know the thread is in the T-Mobile section but if you read the first line, it says it works for T-Mobile, ATT, Sprint, Verizon, etc. It is a very long thread but if you read mostly the later posts from @Craz Basics and you will be able to see that it works really nice.
Good luck
Click to expand...
Click to collapse
Hey thanks....but I have another question now that I'm given choices.
Which ROM is better, the U 7.0 ROM or the T-Mobile ROM you just linked? And, why is it better than the other?

SyberTiger said:
Hey thanks....but I have another question now that I'm given choices.
Which ROM is better, the U 7.0 ROM or the T-Mobile ROM you just linked? And, why is it better than the other?
Click to expand...
Click to collapse
Ok the U 7.0 ROM is still un-rooted and bootloader locked. If you go that way, you get the U ROM with-out all the Bloat. But nothing more.
And the link is not really for the T-Mobile phone only. The ENG.IMG is for all makes of the Qualcomm chip. You install that and you are still with ATT. Still have all the things ATT provides like WiFi-Calling and other ATT things. And you can get rid of the Bloatware from the ATT ROM using different apps, like Titanium Backup. With the ENG.IMG you can root your phone and use all the apps that are available for Rooted Phones. One of the best is Titanium Backup. You can only use that one Rooted phones. If you have the U 7.0 ROM, you will have to use the same ENG.IMG to Root the U 7.0 ROM to get that OS rooted. And as I mentioned before you can use Xposed with the rooted phone.
If you are just looking to get rid of Bloatware on the ATT, there is an app for that also. Check out BK Disabler in the playstore. You can get rid of all the bloatware without rooting your phone.
Anyway, hope this make some kind of sense...

freeop said:
Ok the U 7.0 ROM is still un-rooted and bootloader locked. If you go that way, you get the U ROM with-out all the Bloat. But nothing more.
And the link is not really for the T-Mobile phone only. The ENG.IMG is for all makes of the Qualcomm chip. You install that and you are still with ATT. Still have all the things ATT provides like WiFi-Calling and other ATT things. And you can get rid of the Bloatware from the ATT ROM using different apps, like Titanium Backup. With the ENG.IMG you can root your phone and use all the apps that are available for Rooted Phones. One of the best is Titanium Backup. You can only use that one Rooted phones. If you have the U 7.0 ROM, you will have to use the same ENG.IMG to Root the U 7.0 ROM to get that OS rooted. And as I mentioned before you can use Xposed with the rooted phone.
If you are just looking to get rid of Bloatware on the ATT, there is an app for that also. Check out BK Disabler in the playstore. You can get rid of all the bloatware without rooting your phone.
Anyway, hope this make some kind of sense...
Click to expand...
Click to collapse
Thanks, appreciate it.
I'm really not planning on spending a lot of time making changes or tweaking the handset. I'm on Cricket Wireless therefore I don't see any value in the AT&T bloatware which is why I wanted it removed. My interest is primarily having the latest/greatest android version I can have without all the stuff junking it up. I'd like it to be as fast as is reasonably possibly but at the same time have reasonably good battery life. I'm coming from a Galaxy S3 on Virgin Mobile so the change to the S7E is a huge upgrade. I haven't figured out yet if there are any apps (that require rooting) that are so slick I can't live without them.
I installed the U 7.0 and as I recall I got about 5 or 6 OTA updates which in encouraging. I think the AT&T ROM never received any of the 3 or 4 most current security updates. Anyhow, U 7.0 is up and running with no AT&T bloatware.

SyberTiger said:
Thanks, appreciate it.
I'm really not planning on spending a lot of time making changes or tweaking the handset. I'm on Cricket Wireless therefore I don't see any value in the AT&T bloatware which is why I wanted it removed. My interest is primarily having the latest/greatest android version I can have without all the stuff junking it up. I'd like it to be as fast as is reasonably possibly but at the same time have reasonably good battery life. I'm coming from a Galaxy S3 on Virgin Mobile so the change to the S7E is a huge upgrade. I haven't figured out yet if there are any apps (that require rooting) that are so slick I can't live without them.
I installed the U 7.0 and as I recall I got about 5 or 6 OTA updates which in encouraging. I think the AT&T ROM never received any of the 3 or 4 most current security updates. Anyhow, U 7.0 is up and running with no AT&T bloatware.
Click to expand...
Click to collapse
AT&T's software updater only works if you have an AT&T SIM card. This is why the first thing you should do if you buy an AT&T (or other carrier) device that you don't plan to use on that network is to convert it to the unlocked version. That, and AT&T (in particular) loads the crap out of their devices with bloatware to the point that switching to U feels like an early upgrade to the next generation device.

jshamlet said:
AT&T's software updater only works if you have an AT&T SIM card. This is why the first thing you should do if you buy an AT&T (or other carrier) device that you don't plan to use on that network is to convert it to the unlocked version. That, and AT&T (in particular) loads the crap out of their devices with bloatware to the point that switching to U feels like an early upgrade to the next generation device.
Click to expand...
Click to collapse
Yeah, I have a Cricket SIM which explains why this unlocked handset is stuck on 7.0 G935AUCU4BQA6 which is the February 1, 2017 update. Interestingly enough, the Network Signal Info app shows the SIM Operator as AT&T and Network Operator as Cricket/AT&T.
Going to the U got rid of all the bloatware and the handset immediately started receiving 5 or 6 OTA updates. I'll probably stick with the U version unless it becomes apparent there's a significantly better ROM available that increases performance, battery life or really adds some whizbangs that make the S7E experience a lot better.

forgive me for butting in -- I have a SM-G935A (stock) on Cricket as well.
Updates to the ROM and while keeping Samsung Pay are important to me.
In the past, I have d/led ATT updates and installed them using Odin, but that wipes my phone's apps/settings each time. Recently, I purchased an ATT sim & put the minimum $$$ on it with the intention of popping it in for OTA's. I've received BQK2, Nov 1 2017. It's a crappy work around, but the easiest I know of without having to rebuild my phone each Odin'ed update.
Would installing U or TMO firmware on the 935A remove the ability to use Samsung Pay? Would either of them be updated for frequently/easier than the 935A?

The U firmware supports Samsung pay and gets updates directly. The only downsides are no carrier features like wifi calling, etc., and if gets updates later than the carrier versions. I have run it on AT&T since I got the phone and it has worked fine.

jshamlet said:
The U firmware supports Samsung pay and gets updates directly. The only downsides are no carrier features like wifi calling, etc., and if gets updates later than the carrier versions. I have run it on AT&T since I got the phone and it has worked fine.
Click to expand...
Click to collapse
Thanks, jshamlet.
This is my first phone I haven't rooted & I feel a bit powerless without Xposed and Titanium Backup. I find myself using Samsung Pay so often, that I don't want to lose it & was concerned that installing the U (or TMO) firmware on the ATT version would trip Knox, too.

William Thornton said:
forgive me for butting in -- I have a SM-G935A (stock) on Cricket as well.
Updates to the ROM and while keeping Samsung Pay are important to me.
In the past, I have d/led ATT updates and installed them using Odin, but that wipes my phone's apps/settings each time. Recently, I purchased an ATT sim & put the minimum $$$ on it with the intention of popping it in for OTA's. I've received BQK2, Nov 1 2017. It's a crappy work around, but the easiest I know of without having to rebuild my phone each Odin'ed update.
Would installing U or TMO firmware on the 935A remove the ability to use Samsung Pay? Would either of them be updated for frequently/easier than the 935A?
Click to expand...
Click to collapse
Hmm, doesn't Samsung Smart Switch back up everything?

SyberTiger said:
Hmm, doesn't Samsung Smart Switch back up everything?
Click to expand...
Click to collapse
I've never gotten it working 100%.

William Thornton said:
I've never gotten it working 100%.
Click to expand...
Click to collapse
I'd be talking about the PC version not the phone-to-phone setup. Back up to PC then from PC to your phone. Worked great for me.

SyberTiger said:
Hmm, doesn't Samsung Smart Switch back up everything?
Click to expand...
Click to collapse
Um, no. No it doesn't. Helium (or if you are feeling oldster, ADB) does a vastly better job of backing up apps than Smart Switch. Smart Switch does a reasonably good job of putting your phone's settings back, but it doesn't appear to back up most app data.
I learned this the hard way.
---------- Post added at 01:51 AM ---------- Previous post was at 01:47 AM ----------
William Thornton said:
Thanks, jshamlet.
This is my first phone I haven't rooted & I feel a bit powerless without Xposed and Titanium Backup. I find myself using Samsung Pay so often, that I don't want to lose it & was concerned that installing the U (or TMO) firmware on the ATT version would trip Knox, too.
Click to expand...
Click to collapse
Samsung Pay, with the MST technology, is one of those weirdly underrated features that continually amaze people. It works nearly anywhere you can physically see the mag stripe reader, which instantly makes it vastly more useful than either Apple Pay or Android Pay. I have had more than a few people say "We don't take Apple Pay", and then drop their jaw when the transaction goes through.
The fact that Samsung doesn't make a bigger deal about it is strange, because it really is one of those technologies that sets them apart from the other two.

Stable Root for SM-G935P?

HI. I have a question regarding my s7 edge on sprint (SM-G935P) and to whether or not anyone has found a stable rooting method for it. Im somewhat experienced in this kind of topic as i have rooted my phone multiple times and have found success but all methods resulted in a very laggy phone. So im not new to this but could use a little more knowledge. From what i know, the root methods used to root the snapdragon models of the s7 and s7 edge are using ENG Boot and in result, that's why devices are not as stable as they are on stock firmware. Because of locked bootloaders and from my understanding, there is no way to root without a laggy phone. Unless you were to unlock your phone, there's no way of rooting without lag? Also, from what i gathered up is that you can convert a SM-G935P model phone to a SM-G935U. G935U is the unlocked firmware? If so, if i try to root will i keep the sprint service? I may sound silly right now but im posting this to better understand if any one of you have found a rooting method which eliminates all lag or as much lag as possible. If there's is nothing i will probably be better off sticking to my stock s7 edge like i have been for awhile now. I have found this though and im curious to know if this has anything to do with my post?
https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647

izzy6 said:
HI. I have a question regarding my s7 edge on sprint (SM-G935P) and to whether or not anyone has found a stable rooting method for it. Im somewhat experienced in this kind of topic as i have rooted my phone multiple times and have found success but all methods resulted in a very laggy phone. So im not new to this but could use a little more knowledge. From what i know, the root methods used to root the snapdragon models of the s7 and s7 edge are using ENG Boot and in result, that's why devices are not as stable as they are on stock firmware. Because of locked bootloaders and from my understanding, there is no way to root without a laggy phone. Unless you were to unlock your phone, there's no way of rooting without lag? Also, from what i gathered up is that you can convert a SM-G935P model phone to a SM-G935U. G935U is the unlocked firmware? If so, if i try to root will i keep the sprint service? I may sound silly right now but im posting this to better understand if any one of you have found a rooting method which eliminates all lag or as much lag as possible. If there's is nothing i will probably be better off sticking to my stock s7 edge like i have been for awhile now. I have found this though and im curious to know if this has anything to do with my post?
https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
Click to expand...
Click to collapse
It depends on what version you are using at this time. That U root only works if your sprint phone has a binary version of 4, sprint updated the binary in December. That makes all sprint S7E phones that received that December update unable to root as they were updated to binary 5. To find out what what binary version you have, go to setting and about phone. Look for the updated version (it should start with G935P), The 5th to the last number will have either a 4 or 5 on it. If it has a 4, you can root it, if it has a 5, you cannot root it. The U root will work on all American phones as it is programed for GSM and CDMA phones. You may lose all those "awesome" sprint apps when you use the U root flash.

I am very curious on this issue also. I just moved from Colorado to Wyoming and Sprint does not offer unlimited data roaming, so I want to unlock and maybe transfer services to another company, AT&T and Verizon are the two that seem to provide direct service here. But the rooting issue would be a possible huge advantage, maybe....

Sm-g35p, smg935pvpu6RB2
Hi there any to root this phone with magisk?

mikeb143777 said:
Ok, ive scoured the internet and got conflicting results. However, Im not a pro, and it appears you have the low down on the current root status. So here is my question for anybody that can help. I have the Sprint S7 edge (SM-G935P), and Im pretty sure Im on the number 5 bianary, so it appears that Im stuck. But please clarify, does this mean that there is no way to root my phone period? What if I dont go to the "U" firmware? Or better yet, isnt it possible to rollback to a different firmware, to marshmallow or something, and then go from there? I heard you can roll back if you have a "pit" file or something? Can anybody offer me any way to get rooted? Im sure I can follow the instructions if I can find any, Ive rooted plenty, but so far I havent found any options. Thanks.
Click to expand...
Click to collapse
Sorry I didn't get back sooner, I don't go to the sprint part of the forums as much anymore.
At the time, the U Firmware was the only way you could get root. The root method has changed but it still requires the same or lower binary version than the rooted rom. If you are binary 5 and the other ones are 4 you will not be able to root. From what I've seen so far, verizon and the U firmware is still binary 4. What makes this worse, is once you are on a higher binary version, you can no longer downgrade (I've tried during bricking). I have tried a pit file with a non sprint phone and could not get the phone to downgrade either.
Right now you can either wait and see if they upgrade to binary 5 and root then, or you can get an unlocked verizon s7 edge and get root. Both are not the greatest of options
It gets worse... Getting root on a newer phone is not like the older days. I am rooted and all I can use is an altered stock rom. Because the bootloader is locked you cannot use custom recovery and roms like lineage and crDroid. So even if you get root, depending on what you want to do, you will still be limited.

5th number from the right on mine is a 6.

Pyr0TeK said:
5th number from the right on mine is a 6.
Click to expand...
Click to collapse
Me too. I'm fed up with not having root. I not having a easy tether for wireless (BT is too limited) I has cost me on several occasions. I am actively looking for a new phone.
This entire phone is a step backward coming from the Note 4. I lost battery changing on the fly, reliable root / roms, and hotspot, and etc.

Sprint logo change
Hi
I have sm-g935p , s7 edge sprint
I want to remove sprint logo
How to do it

Mine shows up in stock recovery as g935PVPS5BQK1 . anyone know exactly which custom recovery and root method for this is? If I'm in right area then that's fine for me I'll continue as is but just wanted to make absolutely sure before I carry on.

Sprint
I removed the logo but I had to unlock the cell phone

Delayed Texts and Unknown Carrier with Custom ROMs (7.1.2 / 8.1) on Verizon S5-G900V

So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew

drewcu said:
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
Click to expand...
Click to collapse
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.

Fear_The_Fluff said:
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Click to expand...
Click to collapse
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.

drewcu said:
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
Click to expand...
Click to collapse
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.

Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew

drewcu said:
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
Click to expand...
Click to collapse
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630

Fear_The_Fluff said:
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Click to expand...
Click to collapse
Thanks for the quick reply!
You tried the deleting the modems fix or the link in your prior post for your Spring S5? And what is a "forget network" fix -- just resetting all network settings in Android?
Yeah I was really hoping the replacement SIM would fix it but sadly it was a dead end.
I have tried several messengers like the stock Lineage one, Google Messenger, and landed on Textra because it has the most configuration options.
Yeah I tried Odining modems from both the link you referenced and extracting them myself from the firmware. Not sure if this is essentially the same thing as overwriting the modems in the corrupted TWRP modem guide. I am tempted to try this over the weekend after making an EFS backup. Hard for me to believe that deleting modemst1 partitions and not restoring them afterwards as is what seems to be the fix... Does the system automatically rebuild them or something?

Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.

drewcu said:
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
Click to expand...
Click to collapse
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!

Fear_The_Fluff said:
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Click to expand...
Click to collapse
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!

drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
My Verizon S5 (this is the working phone) is a CID 15 (I don't have the phone with me right now to get the CID ID), I can look around for the setup I used. It was some months ago when I ran the bootloader unlock and root. BUT! the phone I had an issue with the LTE was a sprint S5 that was unlocked for years before they started locking the bootloaders. This bug affects all carriers, but mostly sprint and verizon.

drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529

Fear_The_Fluff said:
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!

drewcu said:
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
Click to expand...
Click to collapse
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows

Fear_The_Fluff said:
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Click to expand...
Click to collapse
Pretty sure this whole unlocking the bootloader on CID 15 requires that you change your CID to match the Developer CID. I know that my current CID is referenced in the thread https://forum.xda-developers.com/ve...locking-galaxys-s5-bootloader-t3337909/page39 back when this was all just coming out (and when I first unlocked it using the old method 4 - https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909). I used to have a different CID that's saved somewhere else.
Any chance you can look your CID to see if it matches 1501004d414732474300bd6d97165100?
Thanks!

Should I change my AT&T Rom?

I just bought an unlocked AT&T phone. I don't care about security updates. I do like performance improvements and certain changes when moving to a new operating system though. However I am not willing to make those changes if I sacrifice stability.
Should I switch my AT&T rom to U.S unlocked? Is the gains worth it? Do I gain anything other then "Android 9 pie" in the settings? How is performance?
Will I get OTA updates after that or will I still need to use LGUP?
Thank you
Edit: I think I answered my own question. The ability to use HDMI out is not available until after the December 2018 update. My phone is stuck in November.

Also, unless you're an AT&T customer there's no reason to want or keep AT&T firmware.
Curious-Octopus said:
I just bought an unlocked AT&T phone. I don't care about security updates. I do like performance improvements and certain changes when moving to a new operating system though. However I am not willing to make those changes if I sacrifice stability.
Should I switch my AT&T rom to U.S unlocked? Is the gains worth it? Do I gain anything other then "Android 9 pie" in the settings? How is performance?
Will I get OTA updates after that or will I still need to use LGUP?
Thank you
Edit: I think I answered my own question. The ability to use HDMI out is not available until after the December 2018 update. My phone is stuck in November.
Click to expand...
Click to collapse

ChazzMatt said:
Also, unless you're an AT&T customer there's no reason to want or keep AT&T firmware.
Click to expand...
Click to collapse
Would only flashing and no root/bootloader unlock allow me to keep the serial and imei in the phone? Or should I make alot of backups of files?

Curious-Octopus said:
Would only flashing and no root/bootloader unlock allow me to keep the serial and imei in the phone? Or should I make alot of backups of files?
Click to expand...
Click to collapse
Let's take one topic at a time.
Using Dev Patched LGUP to flash to NAO firmware for your carrier unlocked phone only gets rid of the AT&T bloat and allows you to update firmware while keeping AT&T firmware does not.
Nothing about that conversion touches serial or IMEI.
_____
Unlocking the Bootloader and rooting is a more advanced process which is harder. But that also normally shouldn't affect serial or IMEI. If you do lose serial or IMEI there's a method posted to write them back, I believe.

ChazzMatt said:
Let's take one topic at a time.
Using Dev Patched LGUP to flash to NAO firmware for your carrier unlocked phone only gets rid of the AT&T bloat and allows you to update firmware while keeping AT&T firmware does not.
Nothing about that conversion touches serial or IMEI.
_____
Unlocking the Bootloader and rooting is a more advanced process which is harder. But that also normally shouldn't affect serial or IMEI. If you do lose serial or IMEI there's a method posted to write them back, I believe.
Click to expand...
Click to collapse
Thank you!
I am new to all of this, but I have experience in computer so I am confident about my ability to do it.

With the talk of Android 10 available via OTA update on AT&T only, it might make sense for ppl who want Android 10 to stick with AT&T firmware because if you cross-flash there is no going back. Android 10 for other carriers is not out yet so if you cross-flash, you're stuck with Pie.
Sorry, nevermind, seems its coming out for all soon.

Android# said:
With the talk of Android 10 available via OTA update on AT&T only, it might make sense for ppl who want Android 10 to stick with AT&T firmware because if you cross-flash there is no going back. Android 10 for other carriers is not out yet so if you cross-flash, you're stuck with Pie.
Sorry, nevermind, seems its coming out for all soon.
Click to expand...
Click to collapse
For V35 on AT&T firmware, you won't get the OTA AT&T update unless you're an AT&T customer. Or AT&T MVNO Red Pocket customer.
Whereas you can flash to NAO Android 10 firmware when that is released via KDZ.
People, don't get hysterical like you did with the Pie update. All variants will get Android 10. All but AT&T will have full image KDZ which you can download and install.
NAO KDZ will be the best choice for those who are not Google Fi customer or AT&T customer.
Don't go trying to flash Korean carrier firmware like some did for Pie. Just be patient.

Stupid question... i bought one chep last year of course AT&T and i paid the unlock code, of course it came with Oreo and as later i found it couldn't get Pie. So i flashed it to the unlocked version, but as someone in other thread it seems that the firmware "official" has just been on Oreo, mine seems has security update of June and it has been updated this month with another security update...
Mine seems to work normally, however i could say it has three main flaws, first and most annoying for me is that do not disturb doesn't work properly even with rules established, only way to get it working is setting the alarm, which is a bit annoying considering that as for this virus situation i am not working since 2 months ago, and of course i don't want to get disturbed after 10:00 pm and also very early in the morning...
And second one is the signal which is worst than my previous V30+ converted to US998, funny because with other of my old phones as Z2 Force, Iphone 7 and of course US998 i could get easily 30MB+ at average using same SIM card and in the same area for more than two years, but since i have this V35 i can barely get 2MB at average and max 38MB, and max with the other ones mentioned i could get 45MB and in one time i got 60MB
And i don't know if mine has a weird battery but it can barely get around 15-16 hours of normal use.
Should i flash again to AT&T, flash the latest Pie with security update or just wait for the KDZ of Android 10?
And is that true that it now can be rooted?

This thread is widening in scope to the pros and cons of the various vendor roms and android levels. There are a couple of points to add toward that end. To my knowledge, all v35's on any existing rom can be rooted including the AT&T model. The difficulty with AT&T phones is that kdz's aren't released. You need to make your own backup before flashing to another rom if you want to return to AT&T firmware from say GFI/NA.
The next is about Oreo, at least the "h" NA/GFI build. Hotspot and tethering is broken. It may work once or twice after first setup, but it will stop working. That is a deal breaker for some. Everything (that matters to me) seems to work on Pie.
It will be interesting to hear reports on Android 10 on v35. Before taking the leap, it is important to know that ARB remains 0. An ARB change could lock you to Android 10. I don't recall reading about ARB changes on flagship LG phones in the past several years. Regardless, ARB or back-flashing is not yet reported and I do not know if qfil can overcome an ARB change. My suggestion is to be patient and watch for A10 v35 updates from the skilled, brave and sometimes foolhardy here on xda or tg.
tonochito said:
Stupid question... i bought one chep last year of course AT&T and i paid the unlock code, of course it came with Oreo and as later i found it couldn't get Pie. So i flashed it to the unlocked version, but as someone in other thread it seems that the firmware "official" has just been on Oreo, mine seems has security update of June and it has been updated this month with another security update...
Mine seems to work normally, however i could say it has three main flaws, first and most annoying for me is that do not disturb doesn't work properly even with rules established, only way to get it working is setting the alarm, which is a bit annoying considering that as for this virus situation i am not working since 2 months ago, and of course i don't want to get disturbed after 10:00 pm and also very early in the morning...
And second one is the signal which is worst than my previous V30+ converted to US998, funny because with other of my old phones as Z2 Force, Iphone 7 and of course US998 i could get easily 30MB+ at average using same SIM card and in the same area for more than two years, but since i have this V35 i can barely get 2MB at average and max 38MB, and max with the other ones mentioned i could get 45MB and in one time i got 60MB
And i don't know if mine has a weird battery but it can barely get around 15-16 hours of normal use.
Should i flash again to AT&T, flash the latest Pie with security update or just wait for the KDZ of Android 10?
And is that true that it now can be rooted?
Click to expand...
Click to collapse

cmrntnnr said:
This thread is widening in scope to the pros and cons of the various vendor roms and android levels. There are a couple of points to add toward that end. To my knowledge, all v35's on any existing rom can be rooted including the AT&T model. The difficulty with AT&T phones is that kdz's aren't released. You need to make your own backup before flashing to another rom if you want to return to AT&T firmware from say GFI/NA.
The next is about Oreo, at least the "h" NA/GFI build. Hotspot and tethering is broken. It may work once or twice after first setup, but it will stop working. That is a deal breaker for some. Everything (that matters to me) seems to work on Pie.
It will be interesting to hear reports on Android 10 on v35. Before taking the leap, it is important to know that ARB remains 0. An ARB change could lock you to Android 10. I don't recall reading about ARB changes on flagship LG phones in the past several years. Regardless, ARB or back-flashing is not yet reported and I do not know if qfil can overcome an ARB change. My suggestion is to be patient and watch for A10 v35 updates from the skilled, brave and sometimes foolhardy here on xda or tg.
Click to expand...
Click to collapse
Well my teher works, the phone itself has been good for the amount i paid $100, however those bugs or may be wrong flash? affects me a bit... i guess i should be patient and wait for the kdz.

Can anybody confirm this?
https://piunikaweb.com/2020/06/09/lg-v35-thinq-android-10-lg-ux-9-0-update-rolling-out/
Says that LG G7 Android 10 can be flashed to the V35...

tonochito said:
Can anybody confirm this?
https://piunikaweb.com/2020/06/09/lg-v35-thinq-android-10-lg-ux-9-0-update-rolling-out/
Says that LG G7 Android 10 can be flashed to the V35...
Click to expand...
Click to collapse
NO, that article doesn't say that. It doesn't mention LG G7 whatsoever at all. Seriously. You are just making stuff up?
Confirm what? That you can cross flash to Korean carrier V35 firmware to other V35 against our advice? Why would you want to do that? Just be patient!
Here's my reply from earlier in the thread. Please read it this time.
ChazzMatt said:
For V35 on AT&T firmware, you won't get the OTA AT&T update unless you're an AT&T customer. Or AT&T MVNO Red Pocket customer.
Whereas you can flash to NAO Android 10 firmware when that is released via KDZ.
People, don't get hysterical like you did with the Pie update. All variants will get Android 10. All but AT&T will have full image KDZ which you can download and install.
NAO KDZ will be the best choice for those who are not Google Fi customer or AT&T customer.
Don't go trying to flash Korean carrier firmware like some did for Pie. Just be patient.
Click to expand...
Click to collapse

ChazzMatt said:
NO, that article doesn't say that. It doesn't mention LG G7 whatsoever at all. Seriously. You are just making stuff up?
Confirm what? That you can cross flash to Korean carrier V35 firmware to other V35 against our advice? Why would you want to do that? Just be patient!
Here's my reply from earlier in the thread. Please read it this time.
Click to expand...
Click to collapse
i know but is kinda weird that even that article links to Reddit and some people on the video saying they flashed "successfully" their v35...

tonochito said:
i know but is kinda weird that even that article links to Reddit and some people on the video saying they flashed "successfully" their v35...
Click to expand...
Click to collapse
Yet again, we went all through this a year ago with Pie.
You can flash it "successfully" but you wipe all data, some of the menus are in Korean... Then a month or so later every other variant gets a KDZ (EXCEPT for AT&T). So then people have flash again to what they REALLY want -- which is a North American Open (NAO) carrier unlocked variant firmware. AND they lose data again and risk messing up their phone by cross flashing entirely different region yet again.
There's no need to do it. JUST WAIT. FLASH to NAO firmware when Android 10 is released for that variant.
If you're already on NAO firmware now, then when Android 10 is released for that variant, it would be simple "Upgrade" in Dev Patched LGUP (keep your data). If you're not yet, then it would be Partition DL or Refurbish mode to cross flash to NAO at that time. You would lose your data only once.
The people who are impatient are NOT going to stay on Korean carrier firmware long term. They will cross flash yet again to NAO when it comes out, because it's more desirable. They will be unhappy with the Korean carrier firmware. Many will mess up their phones. Don't be one those people!
Look it's your phone. Do what you want. But weeks ago I predicted this would happen and have cautioned people to not make the same mistakes again that were made last year during Pie rollout.

I just installed the korean ROM and it works... kinda good there are some minor bugs that may bother you if you pay too much attention or that are a bit annoying i am going to put here:
As soon you reboot your phone it is going to give you some warning about well some codes and stuff, i guess because the hardware is not the same?
Menu is in korean at set up but you can change it to your language
There are 3 apps that are in korean and you can't uninstall it, specially Q voice that is on korean language not working
LG Smart World does not work, but anyway i never used it, also Quick Help but it never worked on Pie too so its irrelevant
There is one app called DMB which does not work, don't know what it does but it just freeze when i try to open it
Some weird bug with the battery? It doesn't show up the estimated remaining battery, it just keep on calculating data
For some reason i haven't been able to find or change the data configuration, you know change LTE, 3G or 2G. Seems like it is on auto mode which is kinda annoying for me.
The only drawback i could say for me its dual apps... is not that easy as on Pie
And for some reason it fixed in my case the annoying but it had about do not disturb, which only worked when an alarm was set, but if there wasn't alarm it never worked
Seems the "AI" camera has been improved or fixed because when i selected AI cam it just never do anything relevant compared with my old V30+, now it recognize stuff such person and so on
Although i love stock music player i just hate the annoying purple tone with it, now it changes depending on the setup of the midnight menu. I think that on a rooted v30+ it could be changed but i am not interested on root it and doubt being on Android 10 could be rooted. But it has integraded FM app radio which i regulary use but being the american version of course it has been removed, so it has to be installed manually
What i like its that now it has integrated viedo screen recorder so good bye third party apps, which in my case i really don't like you know if you don't pay you have adds and stuff related.
But the drag menu is with a bug? i don't know how to explain it but it just goes with the hour and date long... instead of just taking a portion of the screen
I just did it and didn't wait because my v35 is broken so i need to change or leave it as secondary phone, around 20 days ago the fingerprint begun to be erratic and was hit or miss trying to unlock it, i have tried cleaning it but it worked as i mentioned on hit or miss. Right now seems i can't configure it. No idea why it just became erratic. And there was a little crack on top of the screen and it seems it got wet under the screen with a white spot, so i guess it is going to be progressively worst with time. Even i tried the old trick of putting on a zip bag but after i left it for the night, when i opened it in the morning it was just wet...
My only question could be if this can be flashed to the North America firmware...

tonochito said:
My only question could be if this can be flashed to the North America firmware...
Click to expand...
Click to collapse
People who flashed to Korean Pie last year were able to flash to North American Open (NAO) Pie when that was released a month or two later.
For most people, cross flashing from AT&T to NAO first and then waiting for Pie would (using Dev Patched LGUP Upgrade mode) have been the better decision. Instead of cross flashing twice -- to Korean, then again to NAO -- to different variant firmware. NAO was what they really wanted in the first place.
OR if already on NAO, just be patient. Android 10 is coming.

ChazzMatt said:
People who flashed to Korean Pie last year were able to flash to North American Open (NAO) Pie when that was released a month or two later.
For most people, cross flashing from AT&T to NAO first and then waiting for Pie would (using Dev Patched LGUP Upgrade mode) have been the better decision. Instead of cross flashing twice -- to Korean, then again to NAO -- to different variant firmware. NAO was what they really wanted in the first place.
OR if already on NAO, just be patient. Android 10 is coming.
Click to expand...
Click to collapse
Well it seems that when NAO kdz will be available i will have the G8, as for me the fingerprint stuff drives me nuts right now that is not working lol, it has been a fantastic phone just well i guess it's time to move on. At least is good that can be flashed to NAO easily and with no problems like other brands out there.

Hello everyone,
I cross-flashed Android 10 on my v35 following this guide everything went as expected.
* I restored my backup from original Android 9 without any problems.
* Overall the phone feels faster, the camera experience is better(not sure that it has any benefits in the quality), unfortunately we cannot change lens during video
* The gCam 6.2 that I was using and was previously kinda stable now cannot save the picture, installed a 5.2 version that was stable in G6 -> v30 and v35 and I will be using this one until the problems with 6.x or 7.x are resolved.
* There are some korean apps that can be hidden but it they do not create any problems.
* Gestures are exactly what I needed and far better than FNG (apart from the customization options that are completely missing)
* Battery is also considerably better, but must be tested in time.

Hello to everyone!
Recently i bought an unlocked AT&T LG V35 which i am using it in Europe without any issue.
I want to cross-flash it in NA ULM kdz cause i don't want the AT&T firmware,but after a lot of reading here and there about the way i have to flash,i am a little bit confused,so i have some questions in order to go on.
My phone came with Pie version AWM20c and security patch level July 1,2019.
1)Which version of NA kdz should i download from LG firmwares site?
I see 4 versions..AIO,GFI,AMZ and USA..Maybe the latter is the most suitable?
2)Should i first crossflash it to Oreo NAO firmware and after update to Pie,(like used to do with LG V30 US998 that we must first install Nougat),or going straight away to NAO Pie?
3)The method of crossflashing is the same like LG V30 from other carriers to US998,as it is in Frankenstein thread?
4)Which of 2 methods between Refurbish and Partition DL is better for my case?
I want a completely clean kdz install,because a weird fact happens to my storage capacity in System,which has 16GB of storage used,and i suppose that all this used capacity,is because of AT&T bloated firmware,in addition to my 2 LG V30's,one is AT&T unlocked and the other is open EU 930,that both have about 10 GB used storage from system.
Thank you all in advance for your answers.

Succesfully crossflashed ULM firmware NAO USA 20f,android 9,security patch level February 1,2020.
Previous software version was android 9,AWM20c,security patch level July 1,2019.
I followed the same procedure of Frankenstein LG V30,V30+.
I used the Partition DL mode to flash and everything went fine..just in the end of the process and after the phone rebooted for first time,i got a notification referring the below:
"Decryption unsuccessful
The password you entered is correct,but unfortunately your data is corrupt.
To resume using your phone,you need to perform a factory reset.When you set up your phone after the reset,you"ll have an opportunity to restore any data that was backed up to your Google Account.
Reset phone"
I don't know if this notification is something bad,but all looked normal after the reset.
No issues till now,no AT&T bloatware,LG logo when powering on,instead of AT&T logo.
As others mentioned,the software version form,remains AWM,instead of ULM.
The previous version from AT&T was AWM20c,now it is AWM20f despite the fact that i have ULM firmware.
I hope my infos can help others in future.
Of course a big thank you goes to everyone here that contributes with their knowledge,making all these useful guides.