Hi there,
Apologies if this is the wrong section or if it has already been posted.
I recently acquired an 8500 from Overseas (Middle East region) which doesn't seem to hold a stable 2G or 3G signal here in Australia (both before and after the update - see below).
I am normally an Android guy, and with Android you have the ability to flash different radios/modems/basebands btu I cant seem to find this anywhere. Is the radio automatically upgraded when flashing a new firmware?
I just (literally hours ago) upgraded to KL6 but it seems the radio hasnt changed.
WHen I type in *#5239870*# into the phone this is what I got both before KL6 and after.
Pre flash to KL6
S8500+JP+JH1
Modem:
SHP: VPP R5 2.1.1
CSC: S8500OJPJG1
Post flash to KL6
S8500+XX+KL6
Modem:
SHP: VPP R5 2.1.1
CSC: S8500OXAKL6
Note in both cases, there is nothing next to Modem
Is there a repository of radio files that is out there (for the life of me, no amount of google or xda searches have found anything)?
Any Australian users out there care to share what modem they have?
Hello sabaramo
About 3G signals in Australia
This was requested a while ago
you can see the solution right here : http://forum.xda-developers.com/showpost.php?p=20068355&postcount=26
And the result right here : http://forum.xda-developers.com/showpost.php?p=20071719&postcount=27
That was for bada 1.2
Nothing available for 2.0 yet
Best Regards
Thanks, I am getting 3G but its just seems unstable.
Can I flash that same amss.bin from the argentinian 1.2 with my KL6 bada 2.0 firmware?
Frankenware 1.2.0
you can try but honestly i doubt that it will work
Best Regards
Right, MyLove90. I just went through the same thing with Bada 2.0 flashed on a Bell Mobility Canada S8500M that I am trying to use in Thailand.
Step 1 - Try amss.bin from DXKE1 firmware with Bada 2.0. - No boot up - freezes on flashing SIM image.
Step 2 - Try to flash DXKE1 complete firmware. This is a downgrade from Bada 2.0 to Bada 1.2. Also set Preconfiguration to THL (Thailand) from default KOR.
Now the phone boots up, but it it cannot be used with the GSM network. Why is this? GSM is a world phone, right? People travel all over the world with their GSM phones and just buy local SIMs while travelling don't they? I had no trouble at all with this when I first brought my T-Mobile G1 phone from the US here. I just popped in the same AIS SIM and it worked fine with no fiddling with the phone at all.
By the way, my Thai carrier is AIS, and setting preconfig to THL makes this a fully AIS phone. AIS menu options and Mobile AP settings, etc that were not there before now appear all over the phone menus.
When trying to dial, I get the no network service error. If I try to select network manually, or access the SIM for a contact phone number or to set a PIN lock, the message changes to "Emergency Calls Only".
So I'm starting to think that I have a defective phone with bad radio, but I figure, well, I can dial 911 with no harm because here emergency is 191. So I dial 911 and the phone dials and starts ringing. Oops! So I hang up so I won't get in trouble, but at least the phone works!
So what's wrong? I went to AIS and after playing with the menus and trying one of their SIMs, they blame the phone not being from Thailand, but as far as I can see, after the Thai firmware flash, this phone is the same as what Samsung shipped to AIS themselves. There are no SIM locks or any reason the phone shouldn't work.
Any ideas? Am I missing something?
can you please mention full info about your very first firmware maybe i can get it for you from Check fus or Slyfer ??
S8500M model is not available at all on Slyfer ...I just heard about it today
You can see...i am from Egypt and here we don't have branding or network lock and such stuff
So all what i can do right now is getting your old firmware for your so your phone work again
Best Regards
Wow! I never even thought about that being a solution!
S8500MUGJF5/S8500MBMCJF5 (BMC)
Thanks!
I found this page : http://www.anysvc.mobi/categories.php?cat_id=2731&sessionid=4bqbt21kclnrg2m92fvo9qkhq6
I think you need to register to download
I am totally disappointed
Slyfer & Check fus don't have such product code !
Best Regards
mylove90 said:
I found this page : http://www.anysvc.mobi/categories.php?cat_id=2731&sessionid=4bqbt21kclnrg2m92fvo9qkhq6
I think you need to register to download
I am totally disappointed
Slyfer & Check fus don't have such product code !
Best Regards
Click to expand...
Click to collapse
You also have to pay upwards of €100 per download, not sure if the CSC is included for that price either. I know because I bought 2 firmwares several months ago.
sabaramo, it sounds to me like your phone is not a 8500T or a 8500M model. Thus unless you are with Telstra, using the Argentinan modem file wouldn't be recommended as you would be changing your broadband frequencies.
Who is your telco?
Let me have another try with SamMobile this time
Maybe our admin add support for Canadian Wave
Please don't pay for a firmware again
Best Regards
mylove90 said:
I found this page : (anysvc.mobi eGSM)
I think you need to register to download
I am totally disappointed Slyfer & Check fus don't have such product code !
Click to expand...
Click to collapse
You are so right mylove90! This experience is starting to bring back memories. I've been using my G1, so this phone has been put aside since I got it, but now I'm remembering how hard it was to find the original ROM. KrazyKong is right. It is 120 euros to download from that site. But with your help and suggestion, I started additional searching.
First I found this service tech offering to share it for a fee because he bought it too. I remember finding him last time I looked for the FW:
http://tinyurl.com/83w3q8k
He's actually on the second page of that thread, and I saw him around other forums last time I searched that firmware too. Other than the pay services, he's the only private party that comes up on that firmware search.
Still, I decided to search the FW name again to see if it crops up anywhere else for download. Actually, after a lot of practice with these searches, I'm starting to learn that Google isn't too useful, and that searching file servers like Megaupload directly are more useful, and those all panned out negative, as I expected since that firmware was non-existent last year too.
But searching that ROM number did find a fresh post from someone with the exact same phone as me and the exact same problem. It's really timely because he just posted the problem 5 days ago and found the answer 3 days ago.
http://tinyurl.com/7x25ags
In a nutshell, he recommends the Brazilian firmware because it has the same bands as our Bell Canada S8500M phones. I gave a try first just to flash the amss.bin file over my Thai firmware, but no luck. I am thinking it is because the Thai firmware I installed is Bada 1.2 and the Brazilian is 1.0.
So next I tried to flash the Open Brazil he recommended (but didn't work on his phone) because I didn't want to try the branded one first. That was unsuccessful because it's not a full firmware and I got error messages in downloading. I'm guessing again it's because I'm trying to load Bada 1.0 over 1.2.
Still, before going to the branded (Vivo Brazil) firmware, I took another look at samobile.com/firmware and found 2 similar Brazil ROMs misfiled under North America. But more hopefully, I found another "U" series ROM: S8500L UHJL1 (Bada 1.0)
I was hopeful for this because my Bell Canada phone is similar: S8500M UGJF5
Because of the common "U" prefix, or the close UH/UG combination, I had hopes that this might be a correct firmware belonging to my Canadian hardware, but for the other Canadian Wave provider/carrier, Rogers.
While I was flashing, I noticed the file name protocols for firmware files and saw that the Brazil file had "Open Brazil" embedded in the file name, so I checked the corresponding file name in this ROM and found CI Entel PCS, which is a provider in Claro, Chile. This corresponds well with the other firmware for S8500L, VCKH1, for Claro, Argentina.
So anyway, after finishing the flash, my phone is working again thanks to your tips and suggestions to point the way.
Thinking about the theory behind this, I have to ask why the regular telephony GSM bands didn't work regardless of firmware, or why flashing different amss.bin files didn't correct the problem.
The only thing I can conclude is that these S8500M phones have a different modem to accomodate Bell Mobility Canada and need firmware to support the oddball hardware. Fortunately this same hardware is available in other countries as well. This procedure also changed my phone to an S8500B.
my head is going to explode
WTH all these brands for
Why it isn't just a normal phone ?!
But still i have curioustiy to get that damn firmware for free
Thanks for explaning...maybe others can use this
Best Regards
I won't be paying for another firmware no. But the branded firmware I was after could not be located any other way than by paying and going through www.anysvc.mobi
mylove90 said:
my head is going to explode
WTH all these brands for
Why it isn't just a normal phone ?!
But still i have curioustiy to get that damn firmware for free
Thanks for explaning...maybe others can use this
Click to expand...
Click to collapse
Yeah, I understand the feeling mylove90. It had my head spinning too. This has been a big learning experience for me too. Like you, I just imagined all the phones were the same, and that having the right firmware would make it work anywhere in the world.
I can only guess, but I'm thinking a lot of non-standard telecommunications equipment is out there with the carriers, and Samsung just tries to accomodate their needs for hardware variations so they can make the sales.
A consequence of all this is that I have lost Badadroid. I used Rebellos' Bada 2.0 fota to install Badadroid the first time and everything worked fine. Now I need to set it up with Bada 1.0. Of course, this firmware isn't on the supported list in the tutorial, but I tried a couple of fixes posted in the thread.
First I installed the bootloaders that are supposed to enable you to run the regular TUT fota on any firmware version. I don't remember off hand what post I got them from, but they installed fine and did not disrupt my phone at all.
Next I tried to install the fota for Bada 2.0, but it doesn't work, giving a fota erase error. I suppose again this is a consequence of trying to mix Bada 2.0 files with Bada 1.0.
So, since I supposedly have the boot files that work with the TUT fota on any firmware, I went ahead and flashed the regular TUT fota. It will not start Android. It goes straight to Bada.
So then I got Rebellos new universal boot fota that is also supposed to run any firmware here:
http://forum.xda-developers.com/showthread.php?t=1020444&page=34
http://code.google.com/p/badadroid/downloads/detail?name=S8500_bl_univ_boot_v2.3.zip
It does not work either, booting straight to Bada.
Any ideas? I hate to lose Android on this phone.
Also, if you find that Canadian firmware for free, let me know. I would like a copy in case I ever need to restore the phone to original.
You are trying with bada 1.0 !!
Fota won't work for sure because it is not supported at all
Also bada 2.0 Fota may have a different address
Universal fota may have or may not have your bootloader address it use
Flash XXJEE bootloader because i am sure it is supported
I think it will work as normal bootloader
S8500XXJEE bootloader : http://code.google.com/p/badadroid/downloads/detail?name=S8500XXJEE_BL.zip&can=4&q=
Also you may need to patch apps_compressed.bin to make it support fota
About patching apps
You can use mijona's app : http://forum.xda-developers.com/showpost.php?p=15159642&postcount=309
You have to use it through windows cmd....place it with apps file you want to patch...go to that path from cmd and write command as following
App_ena.exe <inputfile> <outputfile>
Example : App_ena.exe apps_compressed.bin patched_apps_compressed.bin
or read my post and try to do it yourself : http://forum.xda-developers.com/showpost.php?p=15151700&postcount=300
I think mijoma did a good job already
Best Regards
mylove90 said:
You are trying with bada 1.0 !!
Fota won't work for sure because it is not supported at all
Also bada 2.0 Fota may have a different address
Universal fota may have or may not have your bootloader address it use
Click to expand...
Click to collapse
That's what I was thinking in my process of trial and error. I felt like the OS was protecting itself judging by the nature of the MultiLoarder error messages, so I wasn't worried about bricking the phone as I tried to see what the phone would and wouldn't tolerate.
Flash XXJEE bootloader because i am sure it is supported
I think it will work as normal bootloader
S8500XXJEE bootloader : (URL)
Click to expand...
Click to collapse
Okay. I put those in. The phone accepted them and continued to boot just fine, but there is still no Android boot, so on to the next step:
Also you may need to patch apps_compressed.bin to make it support fota
About patching apps
You can use mijona's app : (URL)
You have to use it through windows cmd....place it with apps file you want to patch...go to that path from cmd and write command as following
App_ena.exe <inputfile> <outputfile>
Example : App_ena.exe apps_compressed.bin patched_apps_compressed.bin
or read my post and try to do it yourself : (URL)
I think mijoma did a good job already
Click to expand...
Click to collapse
Okay, so true! It's been a long time since I have edited files in hexadecimal, so that's nice. I don't mind hex editing, but I haven't poked around with Wave Remaker to get a feel of how to operate in it, so I appreciate mijona's file.
Navigating in cmd is a nice time to do work in C:\ !!!
So that was fun, but flashing patched_apps.compressed.bin made the phone stop booting. So I went on to another route.
Somehow I still had a tab for this thread open from my amss.bin research. These guys are struggling with the same issue in Bada 1.2:
http://forum.xda-developers.com/showthread.php?t=1313675&page=3
Particularly this post gave me a lead on a solution:
http://forum.xda-developers.com/showpost.php?p=20068355&postcount=26
I didn't follow their approach of mixing firmware files though.
Since the CSC file is also a "U" series ROM from Latin America, and in fact closely related to the CI Entel PCS from Claro, Chile firmware that I had already used to successfully get my phone working, I decided to use the entire firmware to reflash my phone with the indicated firmware: S8500LVCKH1
This firmware has no bootfiles, so I used the ones you gave me above. This flash was successful as far as the phone booting okay and working with my carrier. I was surprised to see all my setup options and changes still preserved after the flash. I expected to lose everything on a Full Download flash. I only lost the numbers I store in Contacts for the service menus. This firmware changes my phone to an S8500L. I lose the cute Bada animation for a cheesy Claro animation, and get a stupid message everytime reminding me that data charges can be expensive. If you know how to change the animation back and get rid of the message, it would be nice!
Since this is a Bada 1.2 firmware, I was hoping for this solution to get BadaDroid running again. Unfortunately there is no Android first boot with the power+menu+vol up command. It goes directly and immediately to Bada first.
I tried this both with the Rebellos' Universal Boot 2.3 fota
http://code.google.com/p/badadroid/downloads/detail?name=S8500_bl_univ_boot_v2.3.zip
And I also tried it with the TUT fota, but neither one will boot Android.
Any more ideas?
Of course, all this progress is possible because of your help. Thanks.
This time i had to know what i am dealing with so i downloaded that firmware
and as i thought Apps_compressed.bin needs to be patched
flash the patched file from an old multiloader let's say 5.62 so you won't get errors
If after flashing the file your phone didn't restart please don't panic
Just turn it off then on and it will be fine
Don't use fota made for bada 2.0 please....use the one from the tutorial
About Power On/Off animation
We got a great thread made by adfree in which he explains everything : http://forum.xda-developers.com/showthread.php?t=944620
An advice : Use latest Wave Remaker because it is so cool in this part
You can even make your very own animation
Believe it or not
bada hacking is more cool than the whole Android thing to me and more fun but needs someone who really try to do it
Best Regards
Okay! Thank You MyLove90! You have really made a happy day for me today!
Patching this binary did fix my Android boot, and I spent the rest of the afternoon re-installing all my Android apps.
I miss Bada 2.0, but it wasn't completely functional, so I actually have a better phone now that I have gone back to Bada 1.2.
Even though the Android port isn't complete, it is more fun than my T-Mobile G1 because I haven't upgraded Android yet. Now that I have the Wave working right, I'll go ahead and update the G1 too.
I found this post from mijoma as to possibly why the patch didn't fix my Bada 1.0 install:
"It's also problematic with loading patched version using new bootloaders."
http://forum.xda-developers.com/showpost.php?p=15206739&postcount=1240
Of course, I used the same bootloaders you gave me for both the 1.0 and 1.2 installs, but maybe it was an issue of 1.0 compatibility.
I appreciate your appraisal of Bada. Before I got the Wave, I read rave reviews of Bada, so I didn't mind owning a Bada phone. I just need some Android apps when I'm out, so this phone is working great for me as is. It will be nice if the port is properly finished, but I'm glad I have what they have done.
Thanks also for the animation thread. I'll look into it and Wave Remaker more.
Bell wave firmware
Hi members. A couple days ago I found the S8500MUGJF5 firmware for free. Since I am new I can't post a link but I found it on hotfile website. Anyone that needs this firmware can go there for it.
---------- Post added at 12:59 PM ---------- Previous post was at 11:59 AM ----------
PJK2011 said:
Right, MyLove90. I just went through the same thing with Bada 2.0 flashed on a Bell Mobility Canada S8500M that I am trying to use in Thailand.
Step 1 - Try amss.bin from DXKE1 firmware with Bada 2.0. - No boot up - freezes on flashing SIM image.
Step 2 - Try to flash DXKE1 complete firmware. This is a downgrade from Bada 2.0 to Bada 1.2. Also set Preconfiguration to THL (Thailand) from default KOR.
Now the phone boots up, but it it cannot be used with the GSM network. Why is this? GSM is a world phone, right? People travel all over the world with their GSM phones and just buy local SIMs while travelling don't they? I had no trouble at all with this when I first brought my T-Mobile G1 phone from the US here. I just popped in the same AIS SIM and it worked fine with no fiddling with the phone at all.
By the way, my Thai carrier is AIS, and setting preconfig to THL makes this a fully AIS phone. AIS menu options and Mobile AP settings, etc that were not there before now appear all over the phone menus.
When trying to dial, I get the no network service error. If I try to select network manually, or access the SIM for a contact phone number or to set a PIN lock, the message changes to "Emergency Calls Only".
So I'm starting to think that I have a defective phone with bad radio, but I figure, well, I can dial 911 with no harm because here emergency is 191. So I dial 911 and the phone dials and starts ringing. Oops! So I hang up so I won't get in trouble, but at least the phone works!
So what's wrong? I went to AIS and after playing with the menus and trying one of their SIMs, they blame the phone not being from Thailand, but as far as I can see, after the Thai firmware flash, this phone is the same as what Samsung shipped to AIS themselves. There are no SIM locks or any reason the phone shouldn't work.
Any ideas? Am I missing something?
Click to expand...
Click to collapse
I have a problem similar to PKJ2011. I have an unlocked Bell Canadian wave with firmware S8500MUGJF5. I am using it in Barbados with that firmware on a 2G GSM900 network. I flashed it with S8500XXKL6 Euro firmware and now it is not getting signal on the 2G GSM900 band. When I do a network search it picks up the 2G GSM1900 band but it has a circle with a slash in it. Is there anything I can do to get it working with the Euro bada 2.0 firmware on the 2G GSM900 band since this phone is a quadband phone?
asmythy said:
Hi members. A couple days ago I found the S8500MUGJF5 firmware for free. Since I am new I can't post a link but I found it on hotfile website. Anyone that needs this firmware can go there for it.
Click to expand...
Click to collapse
Thanks for the tip. All three links go to usenet. They offer a free trial period, but you have to sign up for an account and give a payment method, so I'll pass for now. It's good to know the resource is there if needed.
I have a problem similar to PKJ2011. I have an unlocked Bell Canadian wave with firmware S8500MUGJF5. I am using it in Barbados with that firmware on a 2G GSM900 network. I flashed it with S8500XXKL6 Euro firmware and now it is not getting signal on the 2G GSM900 band. When I do a network search it picks up the 2G GSM1900 band but it has a circle with a slash in it. Is there anything I can do to get it working with the Euro bada 2.0 firmware on the 2G GSM900 band since this phone is a quadband phone?
Click to expand...
Click to collapse
You have to wait for Bada 2.0 to be released for one of the carriers that uses our same modem. This includes some carriers in Australia and South America like Brazil, Chile, and Argentina. So I had to downgrade to Bada 1.2 to keep my phone working. I used Claro in Argentina.
hey guys simply Iam still using Android 4.1.2 Would you advice upgrading to 4. 2.2 ?? the other question is why I didn't get the OTA update ?? by the way my tablet model number iS GT-n 5100
Thanks in advance
Was the question that hard???
donmedo said:
Was the question that hard???
Click to expand...
Click to collapse
No But the answer is!
I'll try to keep it short as we already have a thread on what all noticeable has changed etc.
1: Upgrade or Not as of now is more of a subjective thing. What I may find might better/worse might be completely opposite for you, as a lot of minor things have changed. Given that most will succumb to some form of an update and have to accept what is made available to them at the time, it seems like updating should be perhaps a good enough consideration, however, check your region and firmware on sammobile.
I would advise against updating unless applicable firmware version for your region ends with MI1/MI2 or above (MJ1,MJ2..,MK1, ..) (I/J/K denote build months, in this case being september/october/november resp). There are noted issues across different region with older 4.2.2 firmwares. Mainly S-pen and Magnetic cover issues (alarm) which again may or may not be of any consequence to you.
Q2:. Why didn't you get an OTA? :
2.1: Is your Device factory Stock?.
2.2: Might have to do with that samsung has not released updates for your device region yet and perhaps also look into settings if auto OTA Updates are enabled.
I have updated my Note 8 today manually because it has not been available neither via OTA nor via KIES - a quick check on SAMMOBILE shows no 4.2.2 version published for my region. Therefore I decided to push manually the latest 4.2.2 XX version (XX in the name of the ROM means that it is for Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom).
Note that it is the third 4.2.2 XX release which I hope is good enough. Samsung has released 4.2.2 versions for a few other regions too dealing with the reported problems. I am not aware of any strict schedule region by region - it means that you may wait quite long for your regional version. Therefore I replaced my XE version (Bulgaria, Estonia, Kazakhstan, Latvia, Lithuania, Russia, Ukraine) with the available XX one.
The update went smoothly even on my encrypted Note 8 and at first glance everything is running fine, every setup and data is preserved. The first thing I noticed was the "flatter" color palette as most of the contemporary changes in the colors. I do not see change in the performance, neither the sound quality for example...
There are some minor improvements in the 4.2.2 user interface which I was missing in 4.1.2 and they were the second driver for the upgrade. The main was the sheer curiosity .
So, it is really up to you whether you will go for your manual update
Sammobile
Sammobile being down, where did you get your file? Post link?
Moa1480 said:
Sammobile being down, where did you get your file? Post link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=48233827
Sent from my GT-N5100 using Tapatalk 4
Sammobile
Thank you for the link
Hello everyone
I've been battling with this issue for over a month now. I recently flashed CM12.1 / AICP 10.0 on my GTI9190 serrano3gxx and while they are beautiful ROMs, one problem arose. My mobile data doesn't seem to connect at all. WIFI, SMS and calls work without a hitch. I have tried all possible APN's for my carrier (Vodacom ZA) nothing worked. When I reverted back to my NAND backup of the stock ROM the mobile data was offline as well. Which makes no sense to me because it used to work fine in that configuration. This at least gave me the conclusion that the problem isn't ROM related, but then what?
Pretty much where I am now is I'm downloading an update for my firmware. I found a list on http://www.sammobile.com.
Original firmware: South Africa XFA I9190XXUBNA1 (Release date: 25-02-14 Version: 4.2.2)
Now downloading: South Africa XFE I9190XXUCOD2 (Release date: 01-07-15 Version 4.4.2)
Does this seem like the right path to take? I'm really struggling to find ANY sufficient information on the matter for my specific model s4 mini. Almost no information about firmware updates or anything on XDA. I'm not even sure of the risks from doing this firmware update. Will I still be able to run CM12.1 or AICP 10.0 etc? Will I be able to revert back to an older firmware version if this fails? (I'm leaning toward no)
All I want is for my mobile data to work again and this is the only sort of sensible option I've come across, however limited the information on it has been.
ANY help would be much appreciated. :good:
Update on this:
I first isolated the modem and tried flashing that (three times as recommended) Didn't work.
I then flashed the new firmware, which also didn't work. I'm now on new firmware and have tried different modems, nothing works.
Like what, is it actually possible to just "break" your modem? I'm starting to lose faith here.
[SOLVED. Seems like it was Vodacom denying me access somehow for whatever reason. Had to get a new SIM. Sigh. All that hassle.]
Hi guys and girls of XDA!
I have recently bought a used A5 2017 Dual SIM on eBay and I am in awe with its battery life even after the Oreo upgrade.
However, Samsung does not sell Dual SIM models here in Germany, my model comes from Iran (CSC: THR)
I have read the forum, but I haven't found answers to my questions.
I want to flash a DBT version onto my phone ans I have a couple of questions.
1) I have a DS model which were never available on a German market. Will Dual SIM work after I flash and will I get updates after I flash?
2) The german version of (mono-SIM) firmware, which is available on Sammobile still has A520FXXU7CRH9 baseband. I have already updated to the -I9 one. Does that mean that I cannot revert back o the H9 and will have to wait until german phones get I9?
3) My phone came with a sticker "Middle Eastern and African SIM only". Both slots work with German (and some other) SIMs as of now. Will this setting revert back and it will be locked to those SIMs, if I change CSC?
4) If I will apply the Combination CSC from Sammobile , will I get access to every region-locked option without tripping knox?
Thanks in advance!
Alex.
Anybody here? up!
I don't know the answers to your specific questions - but if the dual sim (Iran) phone you have works with your german sims why are you trying to reflash it?
Is there a problem or something that is not working?
I live in New Zealand and have an imported UAE (United Arab Emirates) 2017 A5 with dual SIM and it works just fine. I havent tried the second sim, but have heard of other people that have and it works as expected. The phone doesnt have any UAE junkware. You are right - the battery life on this phone is great. I did find the always on display uses more battery that I like though. Really wish they had an option that just turned the AOD on when you got a notification (new email/text/missed call etc) but Samsung don't seem to want to provide useful features like this. I came from a galaxy Note 2 and miss that little notification LED
If it helps, I see that the A520F and A520F/DS do not have different firmware - I have searched and there are plenty of posts on this forum where people have flashed Dual SIM hardware with the 'standard' A520F software and report that the dual SIM functionality works fine.
https://forum.xda-developers.com/samsung-a-series-2017/help/sm-a520f-to-sm-a520f-ds-t3704566
The DS model was never officially sold in new Zealand (the single SIM model was) but I have received the Oreo update and several security updates for my phone anyway since I bought it.
Hi, thanks for your reply!
Is there a problem or something that is not working?
Click to expand...
Click to collapse
VoLTE is not showing up in settings, for instance. I would need this option sometimes.
report that the dual SIM functionality works fine.
Click to expand...
Click to collapse
Thanks for the link.
the battery life on this phone is great.
Click to expand...
Click to collapse
I get 26-28 hours of norml usage.
However one thing that irritates me is why it loses up to 10% over the night? Everything is closed and AOD is off, too. Other than that I had to uninstall Chrome because it literally ate up trice as much battery as everything else added up, including screen.
Not sure about your overnight power loss - sounds a litle high...
I use my phone very little and usually only charge it every 4 or 5 days.
AOD uses more power than I like (I have seen 1% an hour mentioned and that is probably about right), so I switched that off.
Really annoyed that Samsung havent made an AOD setting that only enables the AOD on when there are notifications (Missed call, new messages). I would really find that useful.
Have searched all over but cant find any apps that will do this.
For those interested, here is what happened.
1) I have a DS model which were never available on a German market. Will Dual SIM work after I flash and will I get updates after I flash?
Basically, it is the same model and the same firmware. The "normal" firmware for a non-Dual-SIM market works perfectly with a DS model and gets updates via OTA.
2) The german version of (mono-SIM) firmware, which is available on Sammobile still has A520FXXU7CRH9 baseband. I have already updated to the -I9 one. Does that mean that I cannot revert back o the H9 and will have to wait until german phones get I9?
The main thing is that ninth digit ("7") because it represents the revision of the firmware. As long as it is the same, you can flash it. If not you will get a brick.
3) My phone came with a sticker "Middle Eastern and African SIM only". Both slots work with German (and some other) SIMs as of now. Will this setting revert back and it will be locked to those SIMs, if I change CSC?
It didn`t happen to me.
4) If I will apply the Combination CSC from Sammobile , will I get access to every region-locked option without tripping knox?
I did as follows.
I flashed the DBT firmware from SamMobile and got myself a british code because it is a standard one in this Multi-CSC.
Knox not tripped. But VoLTE and VoWiFi still not working
Then I found the Combination ROM (FACTORY BINARY) with the same revision as the firmware (See question 2 about the "7").
I flashed it, dialed some USSD code. Then menu appeared from which I could choose the product code.
I chose DBT, wiped the data and cache and voila, I had a DBT phone with working VoLTE and VoWiFi otb.
Knox not tripped 0x0 !
ioffer007 said:
For those interested, here is what happened.
1) I have a DS model which were never available on a German market. Will Dual SIM work after I flash and will I get updates after I flash?
Basically, it is the same model and the same firmware. The "normal" firmware for a non-Dual-SIM market works perfectly with a DS model and gets updates via OTA.
2) The german version of (mono-SIM) firmware, which is available on Sammobile still has A520FXXU7CRH9 baseband. I have already updated to the -I9 one. Does that mean that I cannot revert back o the H9 and will have to wait until german phones get I9?
The main thing is that ninth digit ("7") because it represents the revision of the firmware. As long as it is the same, you can flash it. If not you will get a brick.
3) My phone came with a sticker "Middle Eastern and African SIM only". Both slots work with German (and some other) SIMs as of now. Will this setting revert back and it will be locked to those SIMs, if I change CSC?
It didn`t happen to me.
4) If I will apply the Combination CSC from Sammobile , will I get access to every region-locked option without tripping knox?
I did as follows.
I flashed the DBT firmware from SamMobile and got myself a british code because it is a standard one in this Multi-CSC.
Knox not tripped. But VoLTE and VoWiFi still not working
Then I found the Combination ROM (FACTORY BINARY) with the same revision as the firmware (See question 2 about the "7").
I flashed it, dialed some USSD code. Then menu appeared from which I could choose the product code.
I chose DBT, wiped the data and cache and voila, I had a DBT phone with working VoLTE and VoWiFi otb.
Knox not tripped 0x0 !
Click to expand...
Click to collapse
Could you go into more detail, please? What USSD code did you dial?
Hello,
I am new to the unlocking stuff.
I just bought a used ATT Note10+ 5G in Malaysia, model SM-N976U
However the security patch was stuck in May 2020. It could not be updated over the internet or Smart Switch PC.
It says it is the latest s/w (the latest should be July 2020)
I checked Sammobile and discovered 2 firmware updates : USA(TMK) and USA (T-mobile)(TMB)
(tried to include sammobile link here but was disallowed due to new user status)
Which firmware is suitable for my phone?
Is there a way to unlock ATT and receive the normal monthly security update over the internet automatically?
(i saw Odin in youtube and have basic idea how to flash it)
Appreciate any advice. Thank you
SCitta said:
Hello,
I am new to the unlocking stuff.
I just bought a used ATT Note10+ 5G in Malaysia, model SM-N976U
However the security patch was stuck in May 2020. It could not be updated over the internet or Smart Switch PC.
It says it is the latest s/w (the latest should be July 2020)
I checked Sammobile and discovered 2 firmware updates : USA(TMK) and USA (T-mobile)(TMB)
(tried to include sammobile link here but was disallowed due to new user status)
Which firmware is suitable for my phone?
Is there a way to unlock ATT and receive the normal monthly security update over the internet automatically?
(i saw Odin in youtube and have basic idea how to flash it)
Appreciate any advice. Thank you
Click to expand...
Click to collapse
A thread already exists with the answers to your questions.
https://forum.xda-developers.com/galaxy-note-10+/how-to/att-note-10-5g-n976u-firmware-files-t4059721
No unbranded firmware version exists as of yet.. so you will have to flash a carrier specific firmware.
https://forum.xda-developers.com/showpost.php?p=81981925&postcount=3
Thank for for the link provided.
Based on the link information, i can download the 4 base files from sammobile (either TMK or TMB) and add USERDATA ATT N976USQS3BTF4 to flash it.
Is that correct?
I could find USERDATA ATT N976USQS3BTF4 in easy-firmware website with a purchase fee.
(editied: My phone Active CSC Code is XAA, CSC Country is USA)
SCitta said:
Hello,
I am new to the unlocking stuff.
I just bought a used ATT Note10+ 5G in Malaysia, model SM-N976U
However the security patch was stuck in May 2020. It could not be updated over the internet or Smart Switch PC.
It says it is the latest s/w (the latest should be July 2020)
I checked Sammobile and discovered 2 firmware updates : USA(TMK) and USA (T-mobile)(TMB)
(tried to include sammobile link here but was disallowed due to new user status)
Which firmware is suitable for my phone?
Is there a way to unlock ATT and receive the normal monthly security update over the internet automatically?
(i saw Odin in youtube and have basic idea how to flash it)
Appreciate any advice. Thank you
Click to expand...
Click to collapse
Hi SCitta,
Fellow Malaysian having the same problem as you. But my problem now is that I have Odin and the latest firmware (XAA) but Odin is showing failed to establish connection. How did you do it with yours?
Am using the AT&T version of the Note 10+.
KhairilH said:
Hi SCitta,
Fellow Malaysian having the same problem as you. But my problem now is that I have Odin and the latest firmware (XAA) but Odin is showing failed to establish connection. How did you do it with yours?
Am using the AT&T version of the Note 10+.
Click to expand...
Click to collapse
Never experienced the failed connection before.
Have you installed the SAMSUNG-drivers ? The Samsung Smart Switch PC installation might help to fix the drivers.
Hello everyone I am Malian and I live in Mali I recently bought a n976U locked by at & t since when I was putting a chip from an operator from here I was getting network unlock code So I looked for a way to unlock it for free if possible its like that I stumbled across your forum and read your posts and saw the code * # 272 * Imei # like we could try to change d 'operator with therefore when I put my chip it says "Invalid Sim card inserted" if I try to retype * # 272 * ... # it comes out nothing I'm lost please help me s 'please if possible of course Thank you
#123
Just want to share my experience in this. Bought an ATT N976U from the US and using in Malaysia. Phone came with XAA/XAA/ATT and never received OTA updates.
Downloaded Google phone app and changed CSC to TMB/TMB/ATT using *#*#27262826#*#*
Voila. Received the OTA updates one by one since May2020. Am now on N976USQU5EUC2.
Volte is also working on Celcom.
Did not have to flash firmware. Data not wiped. Everything seemed to be working normal apart from "Tips and Help" in settings crashes every time I click it. Also phone boots with T-Mobile logo now.