Related
My recently bought (Feb 2017) Axon 7 has a firmware that is unusual.
The phone name: ZTE A2017_7383
Model number: ZTE A2017G
Android Version: 6.01
Android Security patch level: December 1, 2016
Baseband version
M8996FAAAANAZM-1.68528.1.71127.1
Kernel version: 3.18.20
Build number: ZTE A2017GV2.0.0B08
Note that the build number is a V2.0.0B08
This phone is incompatible with the A2017GV1.0.0B05 and A2017GV1.0.0B10, so beware. I semi-bricked my phone (no network connectivity anymore) and I can't find a replacement A2017GV2.0 software.
I contacted ZTE, but no reply yet.
The reason I upgraded was due to inability to connect to 4G or LTE networks, even though my provider is on LTE band 3 and band 7.
Can anyone help me with this problem?
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
laicc said:
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
Click to expand...
Click to collapse
The A2017 is the chinese version...you can check this link to get the latest nougat update.....100% working
https://forum.xda-developers.com/axon-7/how-to/a2017-nougat-twrp-flashable-djkuz-t3571714
laicc said:
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
Click to expand...
Click to collapse
as far as I know A2017 variant doesn't have capacitive keys under the screen, so you would notice it right away. My sticker does spell "Model: A2017G" though. Have you made sure that the IMEI numbers written on the sticker match with your phone actual IMEI numbers too? (to be sure it's not a sticker issue)
laicc said:
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
Click to expand...
Click to collapse
USA (U) & International (G) = Hardware keys.
Chinese = No Hardware keys , and uses On-screen Navigation keys.
About the V2, that's something else.... Need further findings thought.
DrakenFX said:
USA (U) & International (G) = Hardware keys.
Chinese = No Hardware keys , and uses On-screen Navigation keys.
About the V2, that's something else.... Need further findings thought.
Click to expand...
Click to collapse
About the Chinese version, the 64GB model doesn't have hardware keys, that's right, but the 128GB version does. I have one.
Thanks everyone, just to close this issue, for the benefit of everyone, my discussions with the Ebay seller revealed that the handset is actually an A2017 Chinese set, and reflashed with their custom ROM to emulate an A2017G. Thats why it didn't work very well, and practically cannot be OTA'ed or updated.
This same message has been cross posted to [A2017G] B10 Update Released 1 2 3
Thread by rikin93
So sorry if I repeat myself here, but I just wanted everyone to know that the issue is closed.
I have the same issue, So how did you manage to solve it? did you flash the Chinese version? (A2017) if so how?
or did you ask the seller for the custom ROM to flash it back to that?
thank you
dude215p said:
I have the same issue, So how did you manage to solve it? did you flash the Chinese version? (A2017) if so how?
or did you ask the seller for the custom ROM to flash it back to that?
thank you
Click to expand...
Click to collapse
I had looked at the various options available here on this XDA site, like flashing back to the stock Chinese A2017 rom, or converting it to an A2017U, but in the end, I didn't think it was worth the trouble, and could even make the problem worse.
They did mention that their supplier has the custom rom, and he could probably get it for me. But that means I will be stuck with that rom forever with no possibility of an OTA.
I eventually convinced the Ebay seller to accept the return for a full refund.
Hope this helps.
laicc said:
I had looked at the various options available here on this XDA site, like flashing back to the stock Chinese A2017 rom, or converting it to an A2017U, but in the end, I didn't think it was worth the trouble, and could even make the problem worse.
They did mention that their supplier has the custom rom, and he could probably get it for me. But that means I will be stuck with that rom forever with no possibility of an OTA.
I eventually convinced the Ebay seller to accept the return for a full refund.
Hope this helps.
Click to expand...
Click to collapse
Hey, thank you for sharing,
I decided to do the opposite, and dived into getting my phone in working condition by flashing the chinese rom on it, although I never done anything like this before. I think I'll make a noob's guide to it, because while there are a lot of good tutorials out there, there are a lot of details kind of glossed over on how to do certain small steps, and you'll have to search for other guides on how that particular step is done.
For now let's just say that I'm happily running Nougat 7.1 with the Google Now launcher, and Google stock apps.
dude215p said:
Hey, thank you for sharing,
I decided to do the opposite, and dived into getting my phone in working condition by flashing the chinese rom on it, although I never done anything like this before. I think I'll make a noob's guide to it, because while there are a lot of good tutorials out there, there are a lot of details kind of glossed over on how to do certain small steps, and you'll have to search for other guides on how that particular step is done.
For now let's just say that I'm happily running Nougat 7.1 with the Google Now launcher, and Google stock apps.
Click to expand...
Click to collapse
That's great. I would really like to know how you did it. Reading the forum, even with the fairly detailed instructions that have been posted, can be intimidating for noob's like us. Is your 4G working good now? Thanks in advance.
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!
Hi, I'm new one.
Really I want to know thet I can flash the rom XT1687( US version ) to my XT1680( La )?
What will be happened? and How( show me the link, please )
ritasa said:
Hi, I'm new one.
Really I want to know thet I can flash the rom XT1687( US version ) to my XT1680( La )?
What will be happened? and How( show me the link, please )
Click to expand...
Click to collapse
Why are you trying to do this?
If you are trying to change the radio bands (like enable new or different LTE bands) just changing the ROM or modems doesn't work, it is embedded deeper in the system.
ritasa said:
Hi, I'm new one.
Really I want to know thet I can flash the rom XT1687( US version ) to my XT1680( La )?
What will be happened? and How( show me the link, please )
Click to expand...
Click to collapse
They are different HARDWARE versions. Different RADIO hardware to be more precise. This action is very likely to result in the radio not working anymore, and you might be left wit a small tablet, that can't make phone calls or connect to cellular data...
Thanks for your information.
There's no specific firmware for each variant. All firmware are universal, so any would adapt to your hardware (NFC, Compass, TV).
So, flashing any firmware will work on any potter
And yeah, model, and radios are on other partitions, so, they won't change on fastboot, or through TWRP
abeloman said:
There's no specific firmware for each variant. All firmware are universal, so any would adapt to your hardware (NFC, Compass, TV).
So, flashing any firmware will work on any potter
And yeah, model, and radios are on other partitions, so, they won't change on fastboot, or through TWRP
Click to expand...
Click to collapse
Is this confirmed?
If so, what are the partitions where model and radios are stored (and other model specific stuff)? Are there any other partitions that you should never flash with a copy of another model?
Hi,
I recently bought a S8+ (Exynos) from a Korean friend..
It works fine but constantly ask for roaming cause I'm not in Korea.
so I tried to install Official firmware SM-G955F with Odin but it didn't work.
I have to install the official firmware SM-G955N again to be able to use it and also I could root it.:fingers-crossed:
It is possible to change the firmware from SM-G955N to SM-G955F?
ben.ahumada said:
Hi,
I recently bought a S8+ (Exynos) from a Korean friend..
It works fine but constantly ask for roaming cause I'm not in Korea.
so I tried to install Official firmware SM-G955F with Odin but it didn't work.
I have to install the official firmware SM-G955N again to be able to use it and also I could root it.:fingers-crossed:
It is possible to change the firmware from SM-G955N to SM-G955F?
Click to expand...
Click to collapse
No, yours is snapdragon, g955f is exynos. You can't flash firmware from that model since they have different chipsets
adj998 said:
No, yours is snapdragon, g955f is exynos. You can't flash firmware from that model since they have different chipsets
Click to expand...
Click to collapse
Ahum you assuming that ?
https://www.sammobile.com/devices/galaxy-s8-plus/specs/SM-G955N/
adj998 said:
No, yours is snapdragon, g955f is exynos. You can't flash firmware from that model since they have different chipsets
Click to expand...
Click to collapse
I ran a Chipset test and it says that is Exynos... also the description posted down says that its Exynos
snippem said:
Ahum you assuming that ?
https://www.sammobile.com/devices/galaxy-s8-plus/specs/SM-G955N/
Click to expand...
Click to collapse
My bad sorry I confused it with the G9500 model that's snapdragon
---------- Post added at 12:49 PM ---------- Previous post was at 12:48 PM ----------
ben.ahumada said:
I ran a Chipset test and it says that is Exynos... also the description posted down says that its Exynos
Click to expand...
Click to collapse
Yeah I'm sorry my bad I confused it with the G9500 model that's snapdragon I just assumed the N was the same line. My apologies
SM-955x specs
This is just an FYI for anyone else that might read this thread looking for info.
It is correct that many of the SM-9500 (S8) and SM-955 (S8+) variants (US, Canada, Japan, China, Hong Kong) use the Snapdragon 835 chipsets but all of the variants of both S8 and S8+ that the whole rest of the world got all use the Exynos 8895 chipset. That's a ton of phablets. There's a lot of misinformation out there but if you look at the spec sheets that Samsung has themselves supply as well as the official Wikipedia page, you'll see exactly what I'm talking about. Another for instance, I've seen lots of sites that say the S8+ has 4GB of RAM which is only true of the 64GB version. The 128GB version has 6GB of RAM.
If you look around on XDA and a handful of other sites, people have flashed different CSC's with varying degrees of success. I have no idea where the issue stand currently, but I am working on figuring out what I'm going to do with my SM-955N variant right now. I don't need it working completely ATM as I still have my daily driver but I will be rooting (no warranty anyway since it was imported) and flashing. I am playing around with it and so far everything works great. I just haven't gone as far as getting it on the network as my SIM is one of those that can be resized to different sizes. It's currently a MicroSIM and once I snap the edge off to make it a NanoSIM I can't go back...without some super glue LOL! I'm not sure I want to risk that just yet as I don't want any of that glue getting inside my phone.