Related
I purchased my Moto G4 Plus from Motorola/Lenovo almost a year ago. FIrst I used StaightTalk/ATT and then switched to ATT prepaid. The 4G LTE worked great with both prepaid plans. Soon after I started to use the phone, the updates became very annoying (especially when interrupting GPS/Google maps and navigation while driving) so I followed this guide and rooted my phone:
https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
I did not install TWRP permanently and only ran the image. My bootloader is still unlocked. The only root ap I've used (via SuperSU) is SDMaid, to freeze the Motorola update process. (I purchased both excellent aps to support development, BTW, but they work so well, I've never needed their support!)
I'm moving and ATT towers are not available near my new home so I just switched to Verizon prepaid at Walmart today. 4G stopped working. I have a ticket with Verizon open but I've learned that I'm not the first with this problem--either on the Moto 4G or other phones!
I read as many threads here on the subject as I could stand to read. Those who had some success with changing settings (Settings >> Cellular Networks, APN, network type, etc.) are luckier than I! Nothing is working for me so far.
I'm not a "cell phone guy." What do you experts here in xda-dev recommend for my next steps. I don't have much faith in Verizon customer service!
Oh...I forgot to mention that I also flashed the image to wipe the annoying unlocked bootloader warning image on boot. That's all I can think of in the way of mods I've made to my phone.
Thank you for moving this topic. I thought I was posting in the QA section (my Internet is so slow, the entire screen fails to load and I was not where I thought I was).
My gut feeling is this is a hardware problem (a signal integrity problem in reading the SIM card). For any other Moto G4 users who stumble upon this thread, I found a discussion over on the Lenovo site:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/MotoG4thGen/thread-id/7585/highlight/false/page/1
Thank you all here at xda-developers who have read my post in consideration of my problem. I will restore and try install Nougat, which reportedly fixes the problem sometimes. I will post an update for Moto G4 users here too.
calinb7 said:
Thank you for moving this topic. I thought I was posting in the QA section (my Internet is so slow, the entire screen fails to load and I was not where I thought I was).
My gut feeling is this is a hardware problem (a signal integrity problem in reading the SIM card). For any other Moto G4 users who stumble upon this thread, I found a discussion over on the Lenovo site:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/MotoG4thGen/thread-id/7585/highlight/false/page/1
Thank you all here at xda-developers who have read my post in consideration of my problem. I will restore and try install Nougat, which reportedly fixes the problem sometimes. I will post an update for Moto G4 users here too.
Click to expand...
Click to collapse
What is your model? XT1644? What is your software currently (go to "Settings", "About phone", "Build number"
I un-rooted and took the OTA Nougat update, which fixed the problem (now getting LTE service). I suspect there is either a patch in Nougat for this Moto G4 problem or the problem, by good luck (software / hardware interaction and tolerance stackup, etc.), just doesn't occur with Nougat.
I have an XT1644 and now Nougat 7.0 NPJS25.93-14-4.
Thank you for your reply.
You have to update the radio;
As said above, you have to go back to stock and take whatever OTAs and then unlock your bootloader.
I went through this with Total Wireless (Verizon MNVO) and when the radio was updated to latest, everything is working great.
HueyT said:
What is your model? XT1644? What is your software currently (go to "Settings", "About phone", "Build number"
Click to expand...
Click to collapse
ajw85 said:
You have to update the radio;
As said above, you have to go back to stock and take whatever OTAs and then unlock your bootloader.
I went through this with Total Wireless (Verizon MNVO) and when the radio was updated to latest, everything is working great.
Click to expand...
Click to collapse
Some Moto G4 Plus Android 6 phones worked fine with Verizon LTE. I was just one of the unlucky ones. They all seem to receive Verizon LTE with Android 7, however. Sadly, I have found Android 7 to be far less stable than Android 6 (6 was quite good on my phone). Some of the Android 7 feature like split screen work very poorly too. (Split screen doesn't even work all the OEM-installed Android aps, which comprise a very minimal set of aps on a Moto G4.) I wish I could have avoided the update, but LTE is too important to stay on Android 6.
The OTA update worked well with my unlocked bootloader and there was no reason to re-lock it. Of course I had to return everything but /data to an OEM state (unrooted, etc.).
Moto g5 plus 64g (single SIM),unlocked bootloader, root...4g works fine on stock ROM rooted w/Xposed
. ..and that's great but Ive flashed custom ROMs
Resurrection
...and Halogen
... and Desolation
... and they are very nice ROM s but I only get 3g (no LTE) and the only info I find on this is a quick-fix w/jio SIM using a DUAL SIM. .... Am I the only unlucky human w/a single SIM 3g problem?
I was so excited about this phone, thought I did all of my research , bought TWO 64g g5 plus phones(not 32g no way because I wanted to BEST lol but its single sim, stupid me).
...should I just give up on custom ROMs ? ...or is there something can be done?
Ive being at this for 2 weeks now...Any/all info very appreciated.
I would've posted in other forum but wouldn't let me due to lack of status....or rep...or bling..or something.
Do you have correct APN set? On some custom ROMs I have installed I had to change APN, because it was set to first in the list by default.
I dont know much about APN ...not durecwhst it's suppose to be set at..im boost mobile.. I'll start researching that next ..thanks brother
No luck.
I found the APN settings on Boost mobile site, I set/saved that to no avail.
I went back to stock/rooted and 4g works fine. But no matter which custom ROM I use I still only have 3g.
Surely someone somewhere knows how to set/fix this.
Can a Mod move this to where someone may have hands-on with this 3g vs 4g issue? Dev or someone?
Month later...5 custom roms later...still either no 4g on custom rom or no camera on simple root w magisk. I still can't post in Dev forum.
No LTE
Bigmotoxer said:
Month later...5 custom roms later...still either no 4g on custom rom or no camera on simple root w magisk. I still can't post in Dev forum.
Click to expand...
Click to collapse
Have the same problem, how did u go back to stock? TWRP restore? or did you fastboot flash stock fireware? I'm not sure if it makes a difference but after reading a few of these it looks like stock firmware may need to be reflashed with fastboot then start flashing custom ROMs with twrp. If you get the answer let me know if i find out I'll let you know?
Thanks
Update: yes there are ROMs that will fix the LTE problem, I was reading someone with a connection problem someone suggested downloading stock debloated , another suggested AOKP, downloaded both , first I tried debloated got LTE , then flashed the other, for VoLTE. Also I'm not sure if this is correct or not but fastboot flashing modems may work I'm not exactly sure and would need to look it up further is something else I read but didn't try as its 2:00am and I'm being yelled at by a hidden speaker in my kitchen which is why it took so long for me to even try to look for a reason because I've been getting yelled at so long I think I got cancer, I hope Santa brings them a tall glass of shut the f up so I get one day without being yelled at , also Lineage 15 says LTE working. I haven't used it since I don't want to mess with 8.0 right now. MeryXMaz
I'm havin the same issue. Also with Boost Mobile. Most other devices I've rooted have had some sort of boost/sprint/virgin APN fix .zip. But I donno....
RozWellZ said:
Have the same problem, how did u go back to stock? TWRP restore? or did you fastboot flash stock fireware? I'm not sure if it makes a difference but after reading a few of these it looks like stock firmware may need to be reflashed with fastboot then start flashing custom ROMs with twrp. If you get the answer let me know if i find out I'll let you know?
Thanks
Update: yes there are ROMs that will fix the LTE problem, I was reading someone with a connection problem someone suggested downloading stock debloated , another suggested AOKP, downloaded both , first I tried debloated got LTE , then flashed the other, for VoLTE. Also I'm not sure if this is correct or not but fastboot flashing modems may work I'm not exactly sure and would need to look it up further is something else I read but didn't try as its 2:00am and I'm being yelled at by a hidden speaker in my kitchen which is why it took so long for me to even try to look for a reason because I've been getting yelled at so long I think I got cancer, I hope Santa brings them a tall glass of shut the f up so I get one day without being yelled at , also Lineage 15 says LTE working. I haven't used it since I don't want to mess with 8.0 right now. MeryXMaz
Click to expand...
Click to collapse
Thanks for responding. I still haven't found a fix for the LTE. I will try to aokp again maybe something has been fixed or added. I did fix my camera problem by flashing elementalX so that's good. But not having LTE is not cool. And I also did not want to message w 8.0 yet.
So I tried AOKP to no avail. Still no 4g/LTE. That's time I'll never get back lol.
had the same problem XenonHD seems to work well...
I'll try it thanks
Hoping it'll get better with the official 8.0 release.
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!
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.
So back when I got my phone in Feb 2020, I did what most people do when they have a new device, update it. After some googling, I found plenty of threads about how great the google version of Android 9 is for the v35. Removing the ATT bloatware was my main reason for flashing to it.
I've read on a few different websites that if you flashed to the stock google android 9 rom, that there is no way to flash back to the ATT roms, or upgrade to the current android 10 att rom. My phone is unlocked and is of course, the ATT version.
Model: LM-V350AWM (doesn't show that it's google I guess)
Hardware: Rev 1.0
I have not bought an ATT sim card or gotten there service to upgrade because of what I read. Is it possible to flash back to stock ATT ROMs or to OTA with an ATT sim if I flashed to the google version? Anyway to go back (stock 8.0 even)? I really don't want to switch to a new phone since I got this baby for 190$ and finding something equally good or better in this price range is not happening. I'd appreciate any information you guys have on this.
Thanks!
It isn't clear from your note what you want to do. If your objective is to get to A10, I highly recommend following cloud's guide to localize the Korean A10 rom. That would require unlocking the bootloader. Everything on that rom works at least for me and my use cases. Browse around here in the v35 forums and you'll find the threads you need.
If your aim is simply stock A10 with ATT, there is one option. Someone posted a partition dump. You could try writing partitions one-by-one usind qfil. I haven't seem any reports of anyone doing that....
Okay. So is it confirmed that if you flashed the stock Google Fi Android 9 onto your att phone that you can't flash back to atts? Different partition sizes end up bricking the phone? I can't find any att kdz anyway. Not even the older android 8. I know att $oesnt release theirs but plenty of folks normally upload their stock kdz for the community.
Really confused with how dead the LG V30/35 community has been since day 1. I remember when I was learning how to root my viewsonic g tablet and galaxy 3 (2011-12) the forums were bursting with people and stock kdz loaded everywhere. And 30 different roms were being worked on for one device. I think the galaxy S5 community is still more active than this one. Smh
Thank you for the reply. I'll look for the post you mentioned. I haven't worked or played around with modifying android in 10 years. Only thing I've done is a quick flash of googlefi kdz back in 2020 which was brainless. Just looking at the tutorials to root this phone seems daunting now lol.
Jebsauce said:
Okay. So is it confirmed that if you flashed the stock Google Fi Android 9 onto your att phone that you can't flash back to atts? Different partition sizes end up bricking the phone? I can't find any att kdz anyway. Not even the older android 8. I know att $oesnt release theirs but plenty of folks normally upload their stock kdz for the community.
Really confused with how dead the LG V30/35 community has been since day 1. I remember when I was learning how to root my viewsonic g tablet and galaxy 3 (2011-12) the forums were bursting with people and stock kdz loaded everywhere. And 30 different roms were being worked on for one device. I think the galaxy S5 community is still more active than this one. Smh
Thank you for the reply. I'll look for the post you mentioned. I haven't worked or played around with modifying android in 10 years. Only thing I've done is a quick flash of googlefi kdz back in 2020 which was brainless. Just looking at the tutorials to root this phone seems daunting now lol.
Click to expand...
Click to collapse
AT&T does not release kdz. Don't know why you think that needs to be confirmed. Partitions for AT&T A10 have been dumped. You can write them one by one by qfil.
As to why V30/V35 development is dead, a huge factor is that lg exited the mobile phone market. LG, despite making good hardware, was also not developer friendly. The V35 is 4 years old.
As for rooting a V35, just follow the instructions if that's what you want or move to newer models with 5G, more memory, and greater battery capacity.
I am still rocking my V35 Fi phone happily.
cmrntnnr said:
AT&T does not release kdz. Don't know why you think that needs to be confirmed. Partitions for AT&T A10 have been dumped. You can write them one by one by qfil.
As to why V30/V35 development is dead, a huge factor is that lg exited the mobile phone market. LG, despite making good hardware, was also not developer friendly. The V35 is 4 years old.
As for rooting a V35, just follow the instructions if that's what you want or move to newer models with 5G, more memory, and greater battery capacity.
I am still rocking my V35 Fi phone happily.
Click to expand...
Click to collapse
I thought people who were more tech savvy than me could pull a stock KDZ off their own ATT phone. That's what people did in the past anyway (I believe).
The phone is still great and I'm glad you are happy with it. I just wanted android 10 on my phone. Stock. English. I might try the Korean route since I'm less likely to brick my phone. Who knows, we'll find out. Thanks for the replys.
The localized A10 Korean rom has been fantastic for me. Everything works.
Make sure you backup ftm and efs partitions before starting. You will lose the S/N but it is easily restored. If you are in US, I suggest you flash the localized OP partition. Links are in the localization thread started by cloud.