Related
Hey all,
First time posting, but have been rooting all my android phones using different guides on xda. This one, however, I am having issues with. I have a Moto G4, Amazon subsidized phone, running on Verizon. Whenever I install a custom rom LTE works until I reboot. Once I reboot, it shows 3G regardless of where I am and runs at those reduced speeds.
I have tried Ressurection, Lineage, CM and AOKP. I have two of these phones and on one I upgraded to N firmware and still had the issue. On the one I am using, I am flashing over the stock firmware and all works great until that first reboot regardless of what it is for.
Even if I revert back to a backup made in TWRP, it does not recognize LTE so it makes me think some type of setting is swapping over but I cannot figure out what it is.
Any ideas would be great. I can provide any other information needed, as this is my first time making a post so was unsure what to include. Also, I apologize if this is answered somewhere as my search-fu was failing me.
Thank you!
EDIT: If I restore back to stock firmware using fastboot and lock the bootloader, LTE returns.
I experience the same exact issue with my g4 running on sprint. i do not have the amazon variant. i purchased mine from best buy. i made a post about this a few weeks ago but it never was answered.
Hi guys,
I (we) desperately need help. Myself and a number of other Moto X Style are crying out loud for help on getting our roaming issue fixed. Long story short:
I have a Motorola X Style (all original, no mods), after the upgrade to Nougat International roaming stopped working (it was working on 6.0). Or better, international roaming does not work with a SIM from a Polish operator named PLAY. Funny enough the same SIM in another phone roams internationally fine and a SIM from another operator in the Moto X roams fine too. It seems to be a sick combination of Moto X Android 7.0 and PLAY. I (we) have tried everything, theres a thread on the official Motorola forum if you dare to read ( I cannot post the link because I'm new, but a search for "Moto X Roaming not working Polish Play" will give you a link). And when I say everything I really mean it... Starting from Clear the Cache to Factory Reset, and the obvious/trivial things too like "enable data while roaming" etc... According to the PLAY provider all is OK on their side and Motorola is ignoring the issue... Its 8 months that their "engineers" are allegedly looking into it, and that it will be "hopefully resolved in future updates" .... yeahhh believe it... Solution from Motorola: "send the phone in for a downgrade to 6.0". Many of us, me included, are locked into a # of years contract with PLAY so it is not that easy to dump the operator and go with someone else. That's why someone with a real deep knowledge on how this stuff work is needed. The last thing to add is that PLAY operator is one of the few that uses national roaming too to fill in the gaps on their national coverage, needless to say that national roaming works fine.
Any help will be really appreciated ... best regards Fulvio.
There's not much we can do about it. Editing the stock modem is nearly impossible.
Best you can do right now is flash Nougat Custom ROMs that are based on Marshmallow modem (Official LineageOS), In this way you'll get the Nougat features on Marshmallow base.
or.. try flashing other variants nougat modem RETUS, RETLA (this is not recommended and has a high risk)
antariksh said:
There's not much we can do about it. Editing the stock modem is nearly impossible.
Best you can do right now is flash Nougat Custom ROMs that are based on Marshmallow modem (Official LineageOS), In this way you'll get the Nougat features on Marshmallow base.
or.. try flashing other variants nougat modem RETUS, RETLA (this is not recommended and has a high risk)
Click to expand...
Click to collapse
RetLA & RetUS will not work in Europe, RetAsia has the same baseband.
I think @fulvy70 has locked bootloader so he can't flash anythng.
dzidexx said:
RetLA & RetUS will not work in Europe, RetAsia has the same baseband.
I think @fulvy70 has locked bootloader so he can't flash anythng.
Click to expand...
Click to collapse
Yes of course he has to unlock first and if the device is out of warranty, I don't see any harm in doing it.
Me to.
Someone here uses MM when he's on travels and Nougat at home.
Because...
Delta app doesn't work good on Nougat.
Hi,
Thank you for your answers... I understand that you are all pinpointing the issue in the Modem/Radio Firmware, not the Android OS itself ... this is already a step forward... I understand the risks connected with flashing a different Modem/Radio FW but anyhow is something to know ... I believe it is also something to consider if eventually any custom ROM will be compatible with the new modems/radios ... at that point even changing the ROM to custom will not solve the issue I believe...
Regards Fulvio.
Flashing custom rom doesn't change the modem/radio/baseband.
I don't know where is problem - only Play(Poland) doesn't support LTE roaming.
You can flash any custom for N modem and check it. @fulvy70
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!
Okay, so I used to love rooting my phones, but I mostly dealt with flagship phones in the US which made rooting and flashing a cakewalk. I understand some of the nitty gritty, so when I got my first phone in Japan, I was super excited about rooting it. But after reading this forum for hours, I have so many questions...my phone build is A2017G JPV1.1.0B03.
I read this but this mostly focused on using an update on this phone.
https://forum.xda-developers.com/axon-7/help/a2017g-japan-to-a2017g-european-a2017g-t3608411
1. If that thread is correct, that means I technically just have the European version of the phone with Japanese modems installed. Is that correct?
2. Also, does that mean (if I were not to root the phone) I would need to install a European Axon 7 Oreo update for it to actually work on the phone? Would the US version fail?
3. I can't seem to find the modem for my phone. I can upload some screenshots later but can someone clarify if I'm right that it's a "B03" or am I looking at the wrong information?
4. There is no Oreo release for Japan, so does that mean I can't flash an Oreo ROM because there won't be any modems for this?
That's all for now, but I'm sure I have a lot of follow-up questions to your answers. Your help is greatly appreciated.
Unlock bootloader, install twrp, instal "G" model bootstack, instal any custom rom, then flash "G" modem in twrp, reboot. No matter where you device are from, the model matters. If its "G", its a european version and its only what you need to know. If you want stock oreo and didnt recieve through OTA, download the update in ZTE website for your "G" version, put it in a sdcard then reboot your phone to recovey then select "install update from sd card" option.
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
RobboW said:
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
Click to expand...
Click to collapse
I'm so used to dealing with multiple modems for the same model of phone in the US (between the major carriers and stuff) that I was overthinking it.
Thanks a ton. That simplifies things so much...and also makes me wonder why updating never occurred for the Japanese release. It's not like there isn't language support for newer versions of Android, but maybe not for the MIUI? I need to be more careful choosing my next phone then, though probably it should be an AOSP phone like the Zenfone or Pixel.
Guess I have my work cut out for me this weekend. Time to run a giant backup and start rooting. Thanks again for all your help. I like this phone (though I often accidentally hover/touch the home button when typing, and I hope there's a sensitivity fix for that :laugh so I want it to last for a while before I get my next one.
It's still a good phone, I look at new phones and think, hmmm, nice, but what will I gain on a daily basis? Nothing more to be honest. The A7 has enough power for me still. The one thing I could really use would be a higher capacity battery. Was looking at Huawei phones but now, well.....
For updates, they had issues with OTA and reverted to only releasing for a whole ROM download for update from SD card.
I personally won't apply an OTA for mine even now at Oreo. Must be a whole ROM to flash with the updater. That's all I've done with it since purchase and it works great still. A lot of people seem to have all sorts of weird issues after applying OTA updates.
Sweet. As someone with some experience with this stuff, do you have any tips or tricks I should know moving forward? I'm going to try rooting it tonight.
-EDIT: Quick little question, my phone says the Android version is 7.1.1 but that would be Nougat, right? Or is it actually Marshmellow?
7.1.1 yeah, Nougat. That doesn't make sense from your first post.
Was it used when you got it or new? Have you checked the model from what's on the back of it, not what software says it is?
I keep mine stock, can't advise on rooting etc. I use it with personal and work SIMs and it has to pass requirements including encryption to run Microsoft InTune and our company portal and use it in work mode. Bootloader hasn't even been unlocked. The most I did was uninstall some built in user apps through ADB.
I also have a 2017G bought in Japan. I unlocked it and worked on it based on this forum, and I can say that it behaves as any other 2017G. I am not interested to use the stock ROM, but yes, I remember that it was on Nougat version when I received it.
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
darth_antz said:
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
Click to expand...
Click to collapse
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
The Zenphone 6 is looking a viable buy now.
My Axon 7 is still good so not really looking but I did just get a new Axon 7 Mini for use as a media player. It still has AMOLED screen, stereo speakers, headphone jack, DAC for the jack etc. No hi res bluetooth though. Cost me AU$149 new in box from retail store. Bargain! How much is a dedicated music player which is crap at movies or just cant do them?
Chucked my 128Gb SD in. Sounds good playing through the car hifi, lower 3.5 jack output matches HU aux in impedance better than Axon 7 which can overload the input at high volume. Very balanced and clean sound.
TheZen said:
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
Click to expand...
Click to collapse
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
darth_antz said:
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
Click to expand...
Click to collapse
I bought it at Rakuten Mobile. There was a super sale and it was like 80% off, lol.
I tried using the guide over the last couple of days and no matter what I've done, I can't seem to get to recovery after doing the flashing (step 9). I was able to flash a stock image back on, but then when I try again it's the same results. I'm at a loss as to why but...there's another guide using the Axon7Tool.
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
The downside is that I work two jobs tomorrow so I won't have time to try this new one out but I think I downloaded everything already. This is kinda frustrating though..
-EDIT: I used the unbricking guide to EDL flash the B10 Nougat and it is a different experience than what I had before...geez, seems the Japanese version was severely neglected. If I run into problems with the other guide I feel comfortable EDL flashing Oreo. Really appreciate the support guys, let me know what you think. Before I started this, my battery was lasting barely 8 hours with only LINE and Chrome being the main background apps...
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
GeoffUK said:
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
Click to expand...
Click to collapse
you can't. There are 3 modem variants by region (US, china, global) and many versions for each, but they are not interchangeable and flashing another has already wiped some IMEIs long ago (doesn't always happen though)
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.