Related
I was tinkering with my new T-Mobile LG Leon LTE (MODEL NO : LG-H345) and broke the cellular service (installed Xposed for Lollipop and com.android.phone keeps stopping, tried Fix Permissions, doesn't work). Does anyone here have a Leon LTE or just have the stock ROM laying around? I've got TWRP installed, so that's not a problem.
I can make a back up but i have the lg Leon MS345 (metro PCs)
Maurylucha said:
I can make a back up but i have the lg Leon MS345 (metro PCs)
Click to expand...
Click to collapse
Would you? It's worth a shot.
I'm fairly sure I can bump (24 hours is the rule, right?)
EDIT: http://forum.xda-developers.com/showpost.php?p=60492946&postcount=3 fixed it, it seems! I guess it took a bit of non-tired Googling.
i've got a clean kdz for MetroPCS I think if anyone intersting.
help
I could sure use that kdz for my metropcs Leon can u post a file or link please phone stuck in ttwrp recovery no back no backup and accidentally erased some partition I think
Download LG flash tool and find use this firmware https://mega.nz/#!TV9ikYBZ!_e-x9u5GPTe-QVLETE5y4YF2VdMaZj2LOQEeP3cuv7M It's 5.1.1 Kdz for MetroPCS only!
Thanks a lot highly appreciated,, u were of great help,,,kudos
mixer_paths.xml
could anyone give me the "mixer_paths.xml" file changed the file on the other, and now I have no sound and no backup, please help and forgiveness is that this will not here but I can not create a post... sorry for my bad english . /etc/mixer_paths.xml
Warning: not Metro firmware
bkpaokfc said:
Download LG flash tool and find use this firmware https://mega.nz/#!TV9ikYBZ!_e-x9u5GPTe-QVLETE5y4YF2VdMaZj2LOQEeP3cuv7M It's 5.1.1 Kdz for MetroPCS only!
Click to expand...
Click to collapse
This links to H345 not MS345, IT'S NOT METRO FIRMWARE. The person who asked needed T-Mobile so they probably ran into no problem, but notice the file name on mega download. Thanks though, have you flashed HH firmware on MS devices? Does it work, what differences are there?
Paulzt said:
This links to H345 not MS345, IT'S NOT METRO FIRMWARE. The person who asked needed T-Mobile so they probably ran into no problem, but notice the file name on mega download. Thanks though, have you flashed HH firmware on MS devices? Does it work, what differences are there?
Click to expand...
Click to collapse
It is for Metro, I test it , wel there are some difference like you have Voice calls via Wi-fi, the notification bar have small changes too , but not a big deal and it's android 5.1.1 . For me Signal wasn't working cause i'm at Greece
no
no it's for T-Mobile, i flashed it and it's got tmobile boot and apps, but a locked boatloader that won't allow me to install twrp, so wheres the " i knew what i was talking about " button? oh thanks, ive now got a basic not really supported T-Mobile device. A little misinformation and lack of due diligence just took the fun out of owning this device.
---------- Post added at 09:21 PM ---------- Previous post was at 09:17 PM ----------
bkpaokfc said:
It is for Metro, I test it , wel there are some difference like you have Voice calls via Wi-fi, the notification bar have small changes too , but not a big deal and it's android 5.1.1 . For me Signal wasn't working cause i'm at Greece
Click to expand...
Click to collapse
it is a big deal, i just flashed it and ended up with aa T mobile device. Your in Greece, I'm sure there's more important things to focus on for you, and i did take my own risks, but thanks anyway.
As i search to unlock your bootloader it's a simply option in developer options.
I just purchased my LG-H345
Android 5.1.1;
Stock LMY47V;
Software version - H34510e
BaseBand - MPSS.DPM.2.0.c11.00021
Stock rom help
Maurylucha said:
I can make a back up but i have the lg Leon MS345 (metro PCs)
Click to expand...
Click to collapse
Is it still possible that you can make or help me get a stock rom for this devices please man because i've lost mine by deleting it on accident and i cant seem to find anyone else to do it or who's at least willing, i can't use kdz firmware because i do not have access to a windows pc or even mac
I made backups of my individual partitions on my metro pcs lg leon
LG Leon 4G (H342F)
I have found this site where they have many hard-to-find firmwares
Too bad it is in chinese/japanese so one will need translator to use it
Here is the link for the LG Leon 4G (H342F) Stock ROM (no carrier)
cwww[dot]gaodi[dot]net [slash] forum.php?fromuid=200800&mod=viewthread&tid=669709
Just have to register to access the rom links there.
Hope this help somebody.
Anyone have the stock ROM, kdz, for LGL33L? LG Sunset.
I've asked elsewhere but so far, nothing.
I was in the same problem because last month I got a new LG Leon (H340Y) with all that annoying icons and boot screen the carrier use to put. So, I was looking for a stock ROM without all of it. Googling here a there I've found this page
lg(dash)firmware(dash)rom(dot)com
Hope it works.
Aurey24 said:
Is it still possible that you can make or help me get a stock rom for this devices please man because i've lost mine by deleting it on accident and i cant seem to find anyone else to do it or who's at least willing, i can't use kdz firmware because i do not have access to a windows pc or even mac
Click to expand...
Click to collapse
Exact same problem lol so what happened? If you never found a solution I'll try to post one if i figure it out.
Problem first appeared when I enrolled beta program N 7.0 (unrooted)
Then i unenrolled beta program and went back to Marshmallow but then it appears unknown baseband version.
Then I root my device and
I tried to flash the 7.1.1 stock (nmf26f) but still no go.
Tried to do custom rom (du 7.1.1) but still no go.
Tried to downgrade to stock (6.0) still no go.
Tried to rebuild EFS partition with latest TWRP using
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Still no go
Try to Flash vendor image, radio image still i'm crying......:crying:
please help me.
There is no service center here for nexus device. I am from Bangladesh.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
robiulrana said:
please help me.
Click to expand...
Click to collapse
Read the end of this thread, maybe it will help. Basically used flash-all.bat to flash the latest February stock image from Google. For you that would be N4F26O.
v12xke said:
Read the end of this thread, maybe it will help. Basically used flash-all.bat to flash the latest February stock image from Google. For you that would be N4F26O.
Click to expand...
Click to collapse
Thanks. I'll try & inform the update.
Not working for me....
v12xke said:
Read the end of this thread, maybe it will help. Basically used flash-all.bat to flash the latest February stock image from Google. For you that would be N4F26O.
Click to expand...
Click to collapse
I tried with Factory Image N4F26O, NMF26F even MDA89D(6.0.0) still no change
No service, no signal :crying:
Maybe something on the carrier side needs to be reset?
Sent from my Nexus 6P using XDA-Developers Legacy app
Two images
CyberpodS2 said:
Maybe something on the carrier side needs to be reset?
Click to expand...
Click to collapse
Well there are two factory images for 6P for Feb. N4F26O & NUF26K. Maybe the other one fixes the connectivity?
Paidinfull said:
Well there are two factory images for 6P for Feb. N4F26O & NUF26K. Maybe the other one fixes the connectivity?
Click to expand...
Click to collapse
NUF26K is for Verizon and contains a different baseband with fixes specific to Verizon. N4F26O is for all others- including Bangladesh... besides OP has already flashed a different radio.
My Carrier won't help
CyberpodS2 said:
Maybe something on the carrier side needs to be reset?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've contact with my carrier also, they cannot help me in this regard.
I post this thread on Nexus Help Forum. Maryg Comex said there:
"I am from Buenos Aires, Argentina, and I have the same problem.
I called Huawei Argentina and was told that the last Android 7.1 upgrade blocked the cellular network un my country, because I purchased my Nexus in the USA.
They also advised to contact the store in the USA and ask them to get the international free code from the manufacturer in China in order to unblock the system foro South América.
Still waiting for this code... "
I don't know what to do
Paidinfull said:
Well there are two factory images for 6P for Feb. N4F26O & NUF26K. Maybe the other one fixes the connectivity?
Click to expand...
Click to collapse
Thanks.
Tried both, N4F26K is only for verizone though. Now I'm in N4F26O. New problem appeared now, Baseband version: unkonw.
robiulrana said:
I've contact with my carrier also, they cannot help me in this regard.
I post this thread on Nexus Help Forum. Maryg Comex said there:
"I am from Buenos Aires, Argentina, and I have the same problem.
I called Huawei Argentina and was told that the last Android 7.1 upgrade blocked the cellular network un my country, because I purchased my Nexus in the USA.
They also advised to contact the store in the USA and ask them to get the international free code from the manufacturer in China in order to unblock the system foro South América.
Still waiting for this code... "
I don't know what to do
Click to expand...
Click to collapse
Your thread is very confusing. Are you saying your phone is from NA (H1511) carrier locked (SIM locked to carrier). Please verify and confirm your phone is NOT carrier locked. Secondly, where exactly are you trying to use the phone and have you tried a local SIM from that location.
This was a reply on nexus help forum
v12xke said:
Your thread is very confusing. Are you saying your phone is from NA (H1511) carrier locked (SIM locked to carrier). Please verify and confirm your phone is NOT carrier locked. Secondly, where exactly are you trying to use the phone and have you tried a local SIM from that location.
Click to expand...
Click to collapse
Dear v12xke,
Your qouted thread was actually a reply from my same post on nexus help forum. If possible pls visit this post on nexus help forum: https://groups.google.com/a/[email protected].
I post some screenshot there.
I don't think my phone is carrier locked. I am from Bangladesh and i tried various sim from various carrier from Bangladesh. Those Sim worked fine when i purchase my Nexus 6P from local store. This issue happened when I enrolled to Android N (beta program).
Sorry for my English. Thanks
Have you fixed the problem?? i am from Bangladesh also.
Have you fixed the problem?? i am from Bangladesh also.
@v12xke
v12xke said:
Your thread is very confusing. Are you saying your phone is from NA (H1511) carrier locked (SIM locked to carrier). Please verify and confirm your phone is NOT carrier locked. Secondly, where exactly are you trying to use the phone and have you tried a local SIM from that location.
Click to expand...
Click to collapse
I am also facing the same issue. My phone was bought from google play store and delivered in Texas. It was unlocked and no carrier dependent. I used the t mobile while I was in Houston and when I came back to Bangladesh I have been using the local SIM without any problem until last week. I have tried almost everything (flashing the stock image, flashing a custom rom: purenexus, restoring efs backup and now trying to flash latest radio image). I don't think any of them going to solve the issue if the phone is locked for the country.
kach22 said:
I am also facing the same issue. My phone was bought from google play store and delivered in Texas. It was unlocked and no carrier dependent. I used the t mobile while I was in Houston and when I came back to Bangladesh I have been using the local SIM without any problem until last week. I have tried almost everything (flashing the stock image, flashing a custom rom: purenexus, restoring efs backup and now trying to flash latest radio image). I don't think any of them going to solve the issue if the phone is locked for the country.
Click to expand...
Click to collapse
What were you doing when this happened to your phone last week? There is no "country" lock. Your US phone was sold "carrier unlocked" and is supported in Bangladesh via GMS 900 and 1800, and UTMS B1/B8. All of which are supported by the H1511 (NA) variant. That is why it was working before. If you were lucky enough to have a TWRP backup of your own EFS partitions, restoring those should have worked BUT there was a time when the EFS backups from TWRP were not working because of an error in the script which was corrected in later versions. There is a thread and sticky dedicated to this issue. If not, format them completely and reboot the phone. Have you tried a SIM from another carrier there, preferably one that uses a different frequency as your carrier? Grameenphone appears to support the most frequencies of all the carriers in your area. What happens when you put your TMo SIM in?
v12xke said:
What were you doing when this happened to your phone last week? There is no "country" lock. Your US phone was sold "carrier unlocked" and is supported in Bangladesh via GMS 900 and 1800, and UTMS B1/B8. All of which are supported by the H1511 (NA) variant. That is why it was working before. If you were lucky enough to have a TWRP backup of your own EFS partitions, restoring those should have worked BUT there was a time when the EFS backups from TWRP were not working because of an error in the script which was corrected in later versions. There is a thread and sticky dedicated to this issue. If not, format them completely and reboot the phone. Have you tried a SIM from another carrier there, preferably one that uses a different frequency as your carrier? Grameenphone appears to support the most frequencies of all the carriers in your area. What happens when you put your TMo SIM in?
Click to expand...
Click to collapse
1. I was enrolled in android beta and installed Nougat 7.1.2 . I practically did nothing that could hamper the phone functioning. Yes it was working fine in Bangladesh, and in other country as well.
2. I was not lucky enough to have a TWRP backup of the EFS but I got a back up EFS and restore following instruction. It didn't help. I am using TWRP angler 3.1.0. angler. I also flashed the radio to latest one (3.82) and with no success. You can have a look at the phone information and the drop down menu (Screenshots).
3. I have flashed the stock Nougat 7.0 and reboot the phone several times. It didn't work. Can you explain a bit about "formatting and rebooting". Need to know whether I did the right thing.
4. I have tried another SIM from another carrier but still it didn't work. These sims are working fine in my Nexus 5 which I also bought from Houston.
5. Haven't tried the Grameenphone sim but I don't think it is a SIM issue. and I don't have the TMo sim with me now. It is now being used by my mother who is currently in Houston.
6. Can you share the link of the sticky thread that you have mentioned?
7. I must thank you for your time, your suggestion and your cordial support. I really appreciate that.
kach22 said:
1. I was enrolled in android beta and installed Nougat 7.1.2 . I practically did nothing that could hamper the phone functioning. Yes it was working fine in Bangladesh, and in other country as well.
2. I was not lucky enough to have a TWRP backup of the EFS but I got a back up EFS and restore following instruction. It didn't help. I am using TWRP angler 3.1.0. angler. I also flashed the radio to latest one (3.82) and with no success. You can have a look at the phone information and the drop down menu (Screenshots).
3. I have flashed the stock Nougat 7.0 and reboot the phone several times. It didn't work. Can you explain a bit about "formatting and rebooting". Need to know whether I did the right thing.
4. I have tried another SIM from another carrier but still it didn't work. These sims are working fine in my Nexus 5 which I also bought from Houston.
5. Haven't tried the Grameenphone sim but I don't think it is a SIM issue. and I don't have the TMo sim with me now. It is now being used by my mother who is currently in Houston.
6. Can you share the link of the sticky thread that you have mentioned?
7. I must thank you for your time, your suggestion and your cordial support. I really appreciate that.
Click to expand...
Click to collapse
>>3. What I meant was to manually format the EFS partitions using fastboot and note any errors:
fastboot format modemst1
fastboot format modemst2
>>6. The thread on TWRP/EFS botched backup/restore does not really apply to your case. It forensically details how the dev mistakenly coded the EFS backup script, why it broke many phones, and how it was fixed. Your problem is more likely one or both of the EFS partitions is corrupted. Your best bet is probably finding someone else with a fully working N6P, make a backup of their EFS partitions and then restore that backup to your phone. A pretty tall order.
I did that couple of hours ago already. Downloaded the working EFS partition from a reliable source and flashed through fastboot. Didn't solve the problem. I will check again with the command you have mentioned to see which partition is corrupted. What do you suggest me to do if there is an error in any of the partition?
kach22 said:
1. I was enrolled in android beta and installed Nougat 7.1.2 . I practically did nothing that could hamper the phone functioning. Yes it was working fine in Bangladesh, and in other country as well.
2. I was not lucky enough to have a TWRP backup of the EFS but I got a back up EFS and restore following instruction. It didn't help. I am using TWRP angler 3.1.0. angler. I also flashed the radio to latest one (3.82) and with no success. You can have a look at the phone information and the drop down menu (Screenshots).
3. I have flashed the stock Nougat 7.0 and reboot the phone several times. It didn't work. Can you explain a bit about "formatting and rebooting". Need to know whether I did the right thing.
4. I have tried another SIM from another carrier but still it didn't work. These sims are working fine in my Nexus 5 which I also bought from Houston.
5. Haven't tried the Grameenphone sim but I don't think it is a SIM issue. and I don't have the TMo sim with me now. It is now being used by my mother who is currently in Houston.
6. Can you share the link of the sticky thread that you have mentioned?
7. I must thank you for your time, your suggestion and your cordial support. I really appreciate that.
Click to expand...
Click to collapse
bro, same problem.Here, does tinkering with EFS will work?? Has anyone really solved this issue? I am finding a pattern here, in Marsmallow, there was no problem. But as soon as we switched to Android Nougat, this "no service" issue arised. But, who knew updating a OS will brick a phone!!!! I wish i could go back in time and continued with Marshmallow. I have spent 47k on this phone. Now, i wish nobody buys phone of google or huwaei . DON'T BUY NEXUS 6P
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
kach22 said:
I did that couple of hours ago already. Downloaded the working EFS partition from a reliable source and flashed through fastboot. Didn't solve the problem. I will check again with the command you have mentioned to see which partition is corrupted. What do you suggest me to do if there is an error in any of the partition?
Click to expand...
Click to collapse
from where did you download "working Efs partition"? can u provide me the link. I am helpless here
Google will not admit this but there were major security flaws in factory images before jan,2017.
They patched it in Jan. But effected users like us(who got effected on 2016) got proper fu***.
Hence, the only solution is:
find a nexus 6p user who has everything working....make a backup of their EFS using TWRF (ROOT their phone)...and apply that efs to your phone. Both the phone must have same build version. Both phones must be unlocked to use TWRP to make backup amd restore EFS. N.B. EFS are responsible for detecting celluar modem in your device. Maybe it got corrupted.
if anyone is gracious enough to upload their stable NEXUS 6p Efs backup with build number mentioned, it would be really helpful to us, the affected users.
@parvezrobi
parvezrobi said:
Google will not admit this but there were major security flaws in factory images before jan,2017.
They patched it in Jan. But effected users like us(who got effected on 2016) got proper fu***.
Hence, the only solution is:
find a nexus 6p user who has everything working....make a backup of their EFS using TWRF (ROOT their phone)...and apply that efs to your phone. Both the phone must have same build version. Both phones must be unlocked to use TWRP to make backup amd restore EFS. N.B. EFS are responsible for detecting celluar modem in your device. Maybe it got corrupted.
if anyone is gracious enough to upload their stable NEXUS 6p Efs backup with build number mentioned, it would be really helpful to us, the affected users.
Click to expand...
Click to collapse
Firstly this only solution didn't work for me. I restored the efs partition collected from a reliable source (link provided in the conversation between me and Mr. Dhananjay) matching the build number but it rebooted with the restored EFS but the problem is still there. I have also flashed latest radio image (3.81) and it didn't work as well. If you have time you can read the conversation I am having with Mr. Dhananjay who is well aware of the issue and supplied me the fresh EFS. You can try the same solution which he offered, who knows it might work for you. If it fixes your device let me know. Best of Luck.
https://www.droidorigin.com/how-to-flash-custom-rom/#comment-3275809153
Hi All,
I have recently updated my Sprint device, which had the mobile data working flawlessly before updating. Now I want to fix it and I want to flash my device to a T-Mobile firmware but I kinda lost between forums. Where should I start? Can someone outline the steps for me?
Thanks!
rzrplp said:
Hi All,
I have recently updated my Sprint device, which had the mobile data working flawlessly before updating. Now I want to fix it and I want to flash my device to a T-Mobile firmware but I kinda lost between forums. Where should I start? Can someone outline the steps for me?
Thanks!
Click to expand...
Click to collapse
Start by flashing the latest T firmware to it , if that doesn't correct your data and its showing invalid sim then your device may have been re-locked which I'm seeing a lot of lately
Good day to all.
I recently bought a V20, a Taiwan version H990DS, so with a TWN ROM. The latest TWN ROM is from last year. Is it possible to flash to the newer Singapore ROM? (SEA)
Like this one : H990ds10e_00_OPEN_SG_DS_OP_0314.kdz (10 april 2017)
I now have :
BASEBAND : MPSS.TH.2.0.1.c3-00027-M8996FAAAANAZM-1.77269.3.79643.3
KERNEL : 3.18.31
BUILD NUMBER : NRD90M
SOFTWARE VERSION : V10c-TWN-XX
MODEL NUMBER : LG-H990ds
I have experience with flasing rom's, but only at Samsung devices. LG is new for me. But I have read the threads around here how to flash a new ROM.
I hope somebody can give me a answer to my question. Thanks in advance!
Greetings from The Netherlands
Hello
someone actually managed to do it, so it seems doable, and fairly easy I'd say.
I was tempted to do it myself, and still am, but then I was just hoping LG would come around with a new update to avoid me all this nuisance...
---------- Post added at 11:10 AM ---------- Previous post was at 11:10 AM ----------
https://forum.xda-developers.com/v20/help/lg-v20-h990ds-upgrade-t3586986/page2
buongu said:
Hello
someone actually managed to do it, so it seems doable, and fairly easy I'd say.
I was tempted to do it myself, and still am, but then I was just hoping LG would come around with a new update to avoid me all this nuisance...
---------- Post added at 11:10 AM ---------- Previous post was at 11:10 AM ----------
https://forum.xda-developers.com/v20/help/lg-v20-h990ds-upgrade-t3586986/page2
Click to expand...
Click to collapse
Hi @buongu
It is just one person who switched his ROM, (@Mattfly93)
On Samsung devices, like the S7, it was a piece of cake switching ROM with ODIN. The risk was very minimal.
I wonder how high the risk is switching ROM with the LG V20 H990DS using LGUP.
there were others too, a guy here (https://forum.xda-developers.com/v20/help/australian-f-h990ds-t3551066) tried out different ROMs to find better suiting apn settings; other guys too, actually a lot of people with the H990DS seems to be into this subject
buongu said:
there were others too, a guy here (https://forum.xda-developers.com/v20/help/australian-f-h990ds-t3551066) tried out different ROMs to find better suiting apn settings; other guys too, actually a lot of people with the H990DS seems to be into this subject
Click to expand...
Click to collapse
I see, thanks for the link. I read that topic but must have overseen it
Are you going to change ROM version? And what is the reason to change it?
What are the differences between the Taiwan(TWN) and the newer Singapore(SEA) ROM?
Pierre118 said:
I see, thanks for the link. I read that topic but must have overseen it
Are you going to change ROM version? And what is the reason to change it?
What are the differences between the Taiwan(TWN) and the newer Singapore(SEA) ROM?
Click to expand...
Click to collapse
Yes I'm definitely considering a change. Mainly because they keep receiving updates, I don't know the details, but it seems like there have been a few improvements in the audio compartment as well (which is what I care most about), practically every version had them expect for the h990ds twn. SEA seems to be the one getting updates on a regular basis, so that's the one I'm looking at
there shouldn't be any real difference, same apps, same sw release, just a few fixes ahead so hopefully less glitches.
buongu said:
Yes I'm definitely considering a change. Mainly because they keep receiving updates, I don't know the details, but it seems like there have been a few improvements in the audio compartment as well (which is what I care most about), practically every version had them expect for the h990ds twn. SEA seems to be the one getting updates on a regular basis, so that's the one I'm looking at
there shouldn't be any real difference, same apps, same sw release, just a few fixes ahead so hopefully less glitches.
Click to expand...
Click to collapse
What is keeping you not doing it?
Pierre118 said:
What is keeping you not doing it?
Click to expand...
Click to collapse
I don't enjoy this kind of tweaking anymore
I used to, when updates were scarce and custom ROMs were pretty much the only way to prolong a smartphone's life... but nowadays companies promise a 2 year support for all their devices, so why do we still need to put up with boring and elaborate actions like this?
and there's a chance we won't see any future OTA either, judging from the info I have found it will still be recognized by your software as from TWN, but the update won't match any of the ones for TWN or the ones for SEA, so from that moment on manual updating is all you have... and THAT pisses me off
buongu said:
I don't enjoy this kind of tweaking anymore
I used to, when updates were scarce and custom ROMs were pretty much the only way to prolong a smartphone's life... but nowadays companies promise a 2 year support for all their devices, so why do we still need to put up with boring and elaborate actions like this?
and there's a chance we won't see any future OTA either, judging from the info I have found it will still be recognized by your software as from TWN, but the update won't match any of the ones for TWN or the ones for SEA, so from that moment on manual updating is all you have... and THAT pisses me off
Click to expand...
Click to collapse
I can understand your feelings about this and to be honest, I share them. I am not afraid of switching ROM from TWN to SEA, i think that will go without any problem. But after that it is manual updating, that is something I did not realised. I have to think about this, but the chance I will manually update is big. The updated software and, most important, the security updates can not be ignored. We will keep in touch. Thanks for your opinion.
I would like to know if I can safely use the 'Refurbish' option in the LGUP tool for changing my TWN(Taiwan) Rom to SEA(Singapore) Rom?
Or do I have to use the 'Upgrade' option?
I am currently on the India ROM, which was last updated in January. Also seriously thinking of switching to the SEA ROM. My only concern is if VoLTE will work on it -- currently, I use a Jio 4G SIM. Does anyone know if SEA will support it?
I also have a S7 Edge, and when I changed ROMs on it (from India to UK ROM), VoLTE stopped working. I had to flash back the INS ROM to get it to work again. Does the same happen with LG ROMs? That is, are regional variants of LG ROMs unique?
krumbs said:
I am currently on the India ROM, which was last updated in January. Also seriously thinking of switching to the SEA ROM. My only concern is if VoLTE will work on it -- currently, I use a Jio 4G SIM. Does anyone know if SEA will support it?
I also have a S7 Edge, and when I changed ROMs on it (from India to UK ROM), VoLTE stopped working. I had to flash back the INS ROM to get it to work again. Does the same happen with LG ROMs? That is, are regional variants of LG ROMs unique?
Click to expand...
Click to collapse
I can only answer your first question: yes, the SEA firmware fully supports VoLTE
im also thinking about doing this. im on v10e ESA, securiry patch is December. where can i get the DLL for H990ds for LGUP?
dyepnoodle said:
im also thinking about doing this. im on v10e ESA, securiry patch is December. where can i get the DLL for H990ds for LGUP?
Click to expand...
Click to collapse
All you need is in the 1st post of this thread. Good luck and let us know.
https://forum.xda-developers.com/v20/how-to/v20-kdz-restore-failing-9-completing-fix-t3546817
I took the plunge and it did not go off well! A few observations.
1] I was trying to switch from INS to SEA. Refurbish option did not work -- throws up errors when installation reaches 4 per cent.
2] Upgrade option went off without errors but I ended up with cust id mismatch error after reboot. I think Upgrade leaves a few files behind that are related to firmware region. However, you can dismiss these warnings and use the phone. I also ended up with device failed to decrypt error, but that was sorted with a factory reset.
3] VoLTE (from Jio in India) does not work on the SEA firmware.
4] The SEA firmware felt smoother and more responsive than INS one from January. I also see a few SG specific apps.
5] Have now restored back to the INS firmware by downloading the appropriate KDZ file.
6] Now hoping LG wakes up soon and ports the SEA update to other regions!
Thankfully, the LGUP tool is pretty reliable, and if you are used to ODIN, you will be at home here. I would suggest you go ahead and check it out. Maybe it will work for your region...
I just did the same from TWN to SEA, and surprisingly VoLTE is there!
I see it in the shortcuts, I have no use for it because neither of my carriers support it, but it's there
krumbs said:
3] VoLTE (from Jio in India) does not work on the SEA firmware.
Click to expand...
Click to collapse
just in case you needed the info, this is a screenshot from the latest SEA firmware
update is comming is comming guys, check here http://devtester.ro/projects/lg-firmwares/#imei
buongu said:
just in case you needed the info, this is a screenshot from the latest SEA firmware
Click to expand...
Click to collapse
That's interesting. I did not have this option on SEA. I guess it is carrier specific. From my experience with Samsung S7 Edge, relevant carrier strings had to be present in the CSC file/ folder for VoLTE to work.
If root was available for our device, then perhaps this issue can be fixed.
---------- Post added at 12:09 PM ---------- Previous post was at 11:58 AM ----------
dyepnoodle said:
update is comming is comming guys, check here http://devtester.ro/projects/lg-firmwares/#imei
Click to expand...
Click to collapse
For India, the latest update listed on that site is from April 1. But I don't see it in the downloads section. Does it take over a month for the firmware to be actually available?!
Does any of these dual sim firmware enable band 66?
Hi!
I am sorry if this has been asked here before. I'm fairly new to this kind of stuff.
So I'm a foreigner living in Japan. Due to the allure of local warranty, I decided to get the Axon 7 (A2017G JPV).
It has been months since the last Nougat update came to other A2017Gs but hasn't arrived on the A2017G JPV. So I thought, may be ZTE Japan was just taking a longer time, etc. So recently, I decided to contact customer support. And their answer was unclear at best. They were apparently still deciding if they would release a Nougat update for Axon 7.
So here's my question. Considering that my Axon 7 is also A2017G, is there a way for me to install the latest A2017G European ROM or any other A2017G Stock ROMs for that matter, without unlocking my bootloader and rooting? And get OTA updates from A2017G European? If so, can someone please kindly point me in the right direction, I'm getting a bit lost.
If that isn't possible, is there a way, to install the stock A2017G ROMs (aside from JPV) and then relock the bootloader afterwards?
Please help me. Thank you.
jjquinto said:
Hi!
I am sorry if this has been asked here before. I'm fairly new to this kind of stuff.
So I'm a foreigner living in Japan. Due to the allure of local warranty, I decided to get the Axon 7 (A2017G JPV).
It has been months since the last Nougat update came to other A2017Gs but hasn't arrived on the A2017G JPV. So I thought, may be ZTE Japan was just taking a longer time, etc. So recently, I decided to contact customer support. And their answer was unclear at best. They were apparently still deciding if they would release a Nougat update for Axon 7.
So here's my question. Considering that my Axon 7 is also A2017G, is there a way for me to install the latest A2017G European ROM or any other A2017G Stock ROMs for that matter, without unlocking my bootloader and rooting? And get OTA updates from A2017G European? If so, can someone please kindly point me in the right direction, I'm getting a bit lost.
If that isn't possible, is there a way, to install the stock A2017G ROMs (aside from JPV) and then relock the bootloader afterwards?
Please help me. Thank you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Absolutely no need to root.
Enjoy.
Hamburgle4 said:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Absolutely no need to root.
Enjoy.
Click to expand...
Click to collapse
Hi
Thank you for replying so quickly.
Please bear with me as I am still a bit confused.
The link you gave mo contains Factory Images for the A2017G, right? Therefore, I should just put the factory images (zip file), into the root directory of my SD Card, and update via settings (no need to unlock bootloader or root, right?)?
My A2017G (JPV) is now on A2017G JPV1.0.0B03.
Which factory image should I use?
Thank you very much.
*Deleted for apparent "madness"
Are you mad?!!! This won't work as the signature's don't match.
At best you end up with a failed update, at worst a brick...
ultramag69 said:
Are you mad?!!! This won't work as the signature's don't match.
At best you end up with a failed update, at worst a brick...
Click to expand...
Click to collapse
Now I'm scared. Haha
Do you have any advice on how I should proceed with this? Thank you very much.
Hamburgle4 said:
*Deleted for safety reasons.
Click to expand...
Click to collapse
Considering @ultramag69 said, do you think I should still proceed with this?
I don't think you have to the same radio firmware with all the G version out there.... If you dare to try it probably you will end up bricking your phone.... So don try. Unless you are sure can warranty claim it if it is briked
Unfortunately this region locking thing came in, sometimes it's different hardware for different regions but mostly it's to stop the grey import trade...
Due to this it is a requirement to unlock your bootloader if you want to flash other region/carrier roms, which again is a trial in itself...
If you do wish to try it, make sure you have a flashable version of your FULL stock rom, not an OTA - the difference is an OTA is a patch, usually of a few hundred Mb or so to update parts of your ROM, the full ROM is a stand-alone installation that will completely replace the current ROM.
Generally this will get you out of hot water but be aware this is also not 100% guarantee...
It will probably also delete all your data, back up first....
ultramag69 said:
Unfortunately this region locking thing came in, sometimes it's different hardware for different regions but mostly it's to stop the grey import trade...
Due to this it is a requirement to unlock your bootloader if you want to flash other region/carrier roms, which again is a trial in itself...
Click to expand...
Click to collapse
What I'm confused about is he's not asking to flash A2017A/U firmware (where region locking comes into play) on his device, only another country's A2017G fw so why would he need to unlock bootloader? It's still fw for the global model if I understand correctly.
Hamburgle4 said:
What I'm confused about is he's not asking to flash A2017A/U firmware (where region locking comes into play) on his device, only another country's A2017G fw so why would he need to unlock bootloader? It's still fw for the global model if I understand correctly.
Click to expand...
Click to collapse
I'm on your side - the modem file might be different, but since the hardware is the same, it should work. Maybe the modem file has improved signal stuff for Japan, but it's extremely improbable considering ZTE's craptastic devs...
Also, what could be the worst thing that could happen? Here are the possibilities:
- Works: enjoy
- Installation failed: Should fail before even changing files anyways
- Soft brick: get to recovery, download full update zip, install, wait for Nougat
- Hard brick: "I woke up this morning and it was off, doesn't boot anymore, I want a replacement"
And if the modem is too crappy you can always go back to Japan's firmware
I believe that the Japanese version is different from the other G versions, at least on the modem level. Japan uses some bands that are not used by any other country in the world, so unless ZTE Japan decided to release the G model knowing that it would have some connectivity issues on all Japanese carriers, the Japanese G model must have at least a different modem.
Bold = band is present in the global G model
KDDI: CDMA BC0 / BC6, LTE 1/11/18/41
NTT Docomo: UMTS 1/9/19, LTE 1/9/19/21/28
Softbank: UMTS 1/8/11, LTE 1/8/9/41
I kinda get what you're getting at after looking further into the models. Basing off the spec sheets, Amazon JP has the exact same A2017G TD-LTE with matching bands sold by ZTE. Whereas on the ZTE JP page, it instead matches the bands of something named Axon 7 TD-LTE JP (couldn't find model number, but sounds like OP's A2017G). This has over half the exact bands available on A2017G, additional UMTS bands 6 & 19 and one CA band.
I think someone in another thread previously mentioned about potential signal issues with the Axon 7 being sold in Spain after flashing DE fw. Looking at their spec sheet, it appears to have a few bands missing, may have additional bands, but it's hard to tell since only the frequencies are stated. Could just be anecdotal as you'd think with the greater range of frequencies, it shouldn't face those issues. Anyways this is a separate matter, and potentially an apples to oranges comparison.
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
jjquinto said:
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
Click to expand...
Click to collapse
Great to hear. Also vindicates my apparent "madness" lol.
Hamburgle4 said:
Great to hear. Also vindicates my apparent "madness" lol.
Click to expand...
Click to collapse
Yeah it was nonsense, they are both a2017Gs anyways
We're all a bit mad though, flashing stuff on a 400 dolar thingy...
ive got the A2017 Chinese, bought from aliexpress. Ive rooted and installed the twrp flashable B15 from @djkuz, but the nougat firmware is awful for my DoCoMo phone reception (in far regional Nagasaki). So i need a method to either flash the modem for A2017G (not sure which B# release), or wait for the next chinese firmware release and hope for the best. Any suggestions or experiences to improve my reception? Is it the modem?
Thanks for all the contributions to this thread, as it has got me in the right direction.
jjquinto said:
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
Click to expand...
Click to collapse
Hey I know this is an old thread but I thought I would poke in and add my feedback. I also live in Japan and have the A2017G. I bought it because it was the only phone on the market at the time that [supposedly] supported Google Daydream. Later I realized that only the US version actually worked with Daydream. Later on support was added to European ROMS (when upgraded to 7.1.1). But for some reason the Japanese ROM, despite being 7.1.1 would say 'Incompatible Phone', even when installed manually. I contacted ZTE's customer service, which was terrible; all they said was "we don't know when it will be supported". This was about a year ago, so this week I just got sick of waiting, found the German firmware (A2017G-N-B10), installed it and everything works fine. The radios have no issues, and I was able to download Daydream right from the marketplace.
Thanks for everyone who contributed to this thread!