Related
Hi guys,
I know there are many similiar threads to this one and I'm sure I've read most of them. Either my issue is different, or, if the answer was in one of them, I was too stupid to realize it.
With my S4 Active GT-I9295 I had to go back to stock ROM for the Samsung S-Health and Gear related apps.
I came from spegelius' (absolutely awesome) Google Edition for SGS4A (int'l) v0.9.9.-od2 and flashed the Samsung Stock 4.4.2 with Odin (*). The procedure was: Flash -> Factory Reset -> Flash again to be absolutely sure all files are updated. Currently, I rooted the phone.
My problem persists:
After a reboot I (usually; not always) am able to make normal phone calls.
After some time (sometimes minutes, sometimes hours) I no longer have sound.
I do not hear ringing, the callee can't hear me, I can't hear the callee.
Same problem if I'm being called
Establishing a connection though works always.
Mobile Data is not affected.
WiFi works
Also observed after factory reset -> re-flash, only enter WiFi PW and Google Login Data -> try phone call
I know this problem often arises from a baseband/modem mismatch. So I investigated my CWM backup of the pre-installed 4.2.2 ROM.
That's what was pre-installed:
Bootloader: I9295XXUBMK3
CSC: I9295OXXBMK3
Modem: *I did not find the info in my backup*
This corresponds to the Romanian 4.2.2: http://www.sammobile.com/firmwares/download/22586/I9295XXUBMK3_I9295OXXBMK3_ROM.zip/
That's why I flashed the direct successor http://www.sammobile.com/firmwares/download/37083/I9295XXUCNI1_I9295OXXCNI1_ROM.zip/
PDA: I9295XXUCNI1
CSC: I9295OXXCNI1
MODEM: I9295XXUCNI1
I tried everything I could find online, nothing helped. I am really running out of ideas. Is it possible to go back to 4.2.2 to see if the problem persists?
I do have logcat logs of the radio module before and after the problem occured. But its thousands of lines. If it helps I can upload it!
Thank you guys for your help
(*): I did some intermediate flashing of several other firmware versions (especially different baseband / CSC versions of the same 4.4.2). But I assume this does not affect the result. I used Odin v3.07 & v3.09
Edit: PS: I still think that I might have the wrong CSC Version. I know the 4.2.2 PDA/CSC matches, but I am not from Romania. I'm actually from Germany. And what makes me wonder is that I cannot select the German Keyboard Style without downloading it first. I can't remember doing something similar after unboxing the phone and setting it up for the first time.
Are you aware of this thread?
http://forum.xda-developers.com/showthread.php?p=56955843
Bevare the Thanks Button
Thanks for the answer O-T!
Yes, I was aware of that thread. However, I never made it until here
http://forum.xda-developers.com/showthread.php?p=50787570
Although I did the things basically as described in that posts I have a new question:
Which country is relevant for the search on sammobile? I mean, do they ask me "Where do you live" or "For which country was your device produced?".
Edit: Okay actually they ask me for the 'product code', so it's probably the latter question.
I realized that my 4.2.2 PDA and CSC also match the French version. That would match the language of my original packaging. I already flashed the French 4.4.2 once but heard only noise when calling someone. So I gave up on that one quickly. But I'll give it another shot now.
Is it possible that I had a factory installation of the firmware for country A, and when I first registered with my local carrier I received a modem update OTA for country B?
That would really surprise me. But it could explain my issues, since there is no 4.4.2 for o2 Germany, i.e. I probably wouldn't receive another modem update OTA.
(I never looked into the carrier specific firmwares because I figured they are for sim-locked devices.)
If the above is true, I understand that the only option would be to somehow downgrade my device back to 4.2.2.
I know I'm asking a lot of questions that have been asked and answered elsewhere. But by now I tried so much and nothing worked that I'm really confused and need your guidance.
I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?
hyperion89 said:
I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?
Click to expand...
Click to collapse
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement
JASONRR said:
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
Click to expand...
Click to collapse
Yes, I always did a factory reset. Most of the times I even flashed the firmware a second time after the factory reset. (This was recommended somewhere else.)
JASONRR said:
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement
Click to expand...
Click to collapse
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.
hyperion89 said:
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.
Click to expand...
Click to collapse
You can flash only the modem & non-holos from the 4.2.2 firmware and check
JASONRR said:
You can flash only the modem & non-holos from the 4.2.2 firmware and check
Click to expand...
Click to collapse
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?
hyperion89 said:
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?
Click to expand...
Click to collapse
Identify the bootloader version and Knox state:
http://forum.xda-developers.com/showthread.php?p=57332718
Knox is not a counter - it's a like a fuse.
Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?
hyperion89 said:
Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?
Click to expand...
Click to collapse
There's 3 stock 4.2.2 TW ROM I9295XXUBMK3 to choose for flash by Odin. All have different Germany CSC (Carrier Specific Code) - Generic, O2, T-Mobile. PDA=MODEM=I9295XXUBMK3 for all of them. Not sure if O2 or T-Mobile versions are locked, but they usually have operators bloat apps.
Remember to power OFF before entering download mode, flash ROM in Odin, factory reset.
https://www.samdownloads.de/download/i9295xxubmk3-dbt-4-2-2-germany/
https://www.samdownloads.de/download/i9295xxubmk3-via-4-2-2-germany-o2/
https://www.samdownloads.de/download/i9295xxubmk3-dtm-4-2-2-germany-t-mobile/
Your choice.
O-T I'm so sorry. My post from yesterday was a lie; I can't read my own OP. :crying: :angel:
I9295XXUBMK3 was preinstalled
Now I'm on I9295XXUCNH2, which implies 4.4.2 and makes a downgrade to 4.2.2 impossible (afaik).
Please note that I already tried the generic German (4.4.2) firmware. I never had operater bloat apps and I bought a simlock-free version of the device. Thus I never tested the o2 / T-Mobile ones. (I did, however, once flash the o2 modem over the generic 4.4.2, which turned out to be a bad idea).
I would love to extract the modem info from my CWM backup. The bootloader / CSC strongly suggest I have a French phone, but the modem would ultimately clarify that.
What is your opinion on trying a different custom-ROM? I never built one so I have no idea from where designers obtain their NON-HLOS and modem files. I know many don't come with any of those and require an already working ROM before flashing so these drivers can be kept. On the other hand, Darkman's StockyROM has an additional modem pack.... which, in my case, didn't help.
I simply cannot believe that it's a hardware issue. Everything worked fine until the update to 4.4.2 and new radio drivers should be thoroughly tested before distribution.
Hello everyone!
I just bought an used P9 (EVA-L19) in pristine condition. It arrived with the nougat update but it is missing all Huawei apps. I don't think I really mind not having those (less bloat, hurray!), but I really want at least the camera app! What should I try? This thing is full stock (unrooted), and I'd rather keep it that way... Should I just flash the full stock firmware? HiSuite claims my phone is up to date, but I've got no idea how to check what build my current firmware is.
Thanks!
Oooh... the build seems to be NRD90M "test-keys", which appears to be an old beta build from my googling. Do I have to go back to MM and then upgrade to Nougat? Hopefully I can do all that without a custom recovery...
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Shymmy said:
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Click to expand...
Click to collapse
I'm from Brazil, but I know for a fact this phone isn't brazilian. It comes with a bunch of stuff written in spanish rather than portuguese, and a warranty certificate citing a bunch of spanish-spekaing latin american countries. I'm browsing through the forums and trying to find out what is my Cust yet. But thanks for the response.
Also, if I have to flash something, is it better to stick with Nougat or is Marshmallow more hassle-free?
(I've attached a screenshot of the status screen from Huawei P9 Tool, this is all the data I could gather so far)
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Shymmy said:
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Click to expand...
Click to collapse
All it says on "Version number" is "NRD90M test-keys". I've read that thread, but to downgrade you need a ROM, and without knowing my Cust ID I'm not sure which ROM I should get.
The screenshot shows my serial number (XVV7N16425001010), the model (EVA-L19 - Dual Sim 32GB Rom 3GB RAM) and a weird build string (eng.jenkin.20161230.130431)
absynte said:
Hello,
do you have dual sim , or single sim and NFC ?
Dual sim: EVA-L19 ou L29
Single sim and NFC EVA-L09 (Européan version)
Click to expand...
Click to collapse
Dual SIM EVA-L19 - No idea if I've got NFC or not. Can't find anything NFC-related on the menus, but it might be that I do not know where to look. Long time Windows Phone user here, just migrated back to Android :laugh:
absynte said:
NFC is an connectivity option.
If you don't have, you have dual sim
Click to expand...
Click to collapse
It does have dual SIM, and is the EVA-L19. So no NFC then. Does it help? I'm currently looking for debranding guides because I can't find what branding this phone originally had.
Oooh well... so far:
1- *#*#2846579#*#* doesn't work (nothing happens), can't enable Manufacturer mode for DC Unlocker
2- The HUAWEI EMUI site doesn't give me a bootloader unlock code, so can't unlock the bootloader with the official method
So, so far, I can't install TWRP, so I can't flash a C432 oeminfo.bin
Also, the Rollback instructions at https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091 fail, as the rollback intermediate firmware just fails at 5% claiming to be incompatible with my device.
Aside from blindly trying to flash random firmwares with the three button method, do you guys have ANY ideas at all? I need a rest, just wasted the whole day trying to get this damned thing fixed
Sad thing: even with a borked firmware install this is still orders of magnitude better than my old Lumia 930.
EDIT: GODDAMMIT, BLUETOOTH ALSO DOESN'T WORK!
absynte said:
Ok so you've got to google this or to find on xda some answers.
https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
For exemple....2 or 3 clicks....
bye
Click to expand...
Click to collapse
I'll give the instructions of the first post a try, though they did not work for the OP.
EDIT: AAAAAND the 800mb file is downloading at 28kbps... this won't be fun
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
alexanrsousa said:
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
Click to expand...
Click to collapse
how u downgrade to MM?
spring80 said:
how u downgrade to MM?
Click to expand...
Click to collapse
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
alexanrsousa said:
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
Click to expand...
Click to collapse
thanks for your answer my friend , i will try and update u
---------- Post added at 01:56 PM ---------- Previous post was at 01:25 PM ----------
working my friend , but be sure to backup first because u will lost everything
Hi. I am a complete noob when it comes to rooting Android.
**************************UPDATE************************************************
THIS ISSUE HAS BEEN SOLVED. PLEASE SCROLL TO POST #89 ON PAGE 9 TO SEE THE SOLUTION.
https://forum.xda-developers.com/showpost.php?p=77950935&postcount=89
***************************************************************************************************
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
orsonwells456 said:
Hi. I am a complete noob when it comes to rooting Android.
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
bober10113 said:
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
Click to expand...
Click to collapse
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
orsonwells456 said:
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
Click to expand...
Click to collapse
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
bober10113 said:
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
Click to expand...
Click to collapse
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
orsonwells456 said:
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
Click to expand...
Click to collapse
nothing like
SM-N960FOYAU1MYM or something?
bober10113 said:
nothing like
SM-N960FOYAMYM or something?
Click to expand...
Click to collapse
Ah ok. SM-N960FZBDMYM
bober10113 said:
nothing like
SM-N960FOYAU1MYM or something?
Click to expand...
Click to collapse
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
bober10113 said:
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
Click to expand...
Click to collapse
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
I went to a site with all "official" downloads and I don't see anything for ZBDMYM........
orsonwells456 said:
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
you can also download it using samfirm tool
enter 960F and MYM in settings it should also be a faster download then the web links
bober10113 said:
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
Click to expand...
Click to collapse
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
orsonwells456 said:
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
Click to expand...
Click to collapse
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
and in Odin fill in all slots and for csc use CSC but not HOME csc file.
good luck
bober10113 said:
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
Click to expand...
Click to collapse
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
orsonwells456 said:
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
Click to expand...
Click to collapse
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
check for a folder called .backup and or for a file like:
efs_backup.img.gz
efs_backup.img
or anything similar
bober10113 said:
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
Click to expand...
Click to collapse
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
orsonwells456 said:
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
Click to expand...
Click to collapse
probably a date code of some sort. Samsung mashes a bunch if letters to come up with country,date code. just Google it.
but try samfirm 3.6 tool to dl
https://1drv.ms/f/s!AhXVLDDj8g3AgdJZClzJmsN17YL2CQ
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
orsonwells456 said:
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
Click to expand...
Click to collapse
yeah looks good. its October 1st build
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
orsonwells456 said:
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
Click to expand...
Click to collapse
well ure screwed either way. the goal is to restore everything back to stock and see if you can get a line working
btw was there a seal on the box that you had to break in order to open the box when you first got it?
First i know i'm an idiot, i thought i knew what i was doing but i had no idea, i figured how hard could it be I've rooted a G1 and a Droid Eris.... but alas i was way over my head.
I have a Note 9 from KSA (Saudi Arabia) i'm a contractor there and it was way cheaper than buy in the states plus a dual sim variant. i tried flashing to the Detonator T-mobile rom, and now i'm left with a phone i can not use, I did not create a partition, i have backup all my personal data, but the original firmware is in the ether. I flashed what i thought was a dual sim international firmware, but all it did network lock my phone so god knows what international network, since neither my T-mobile or STC sim work in it. On top of that even though it has a "stock firmware" it's still rooted so knox has been triggered and even if my sim's worked all Knox linked programs wont work.
So what i need from you fine Ladies' and Gentlemen is a solution to get it as close to the stock version as possible, at this point dual sim functionality or the Wifi calling i was trying to flash on to it are second to having the phone function as a proper note 9 again. IF anyone has the stock firmware or knows of a place where i can get the original firmware, no i'm not asking for hacked version, yes i'm willing to pay for it as long as it works. Any help would be greatly appreciated.
Yeah, I know that Samsung devices purchased in the UAE are partitioned differently than those purchased in the rest of the world. I would recommend that you repartition the storage in your device and reinstall the stock OS back onto it again. That should resolve yoru issue. I don't know how to do this. Maybe somebody else can chime in a help you out.
iceepyon said:
Yeah, I know that Samsung devices purchased in the UAE are partitioned differently than those purchased in the rest of the world. I would recommend that you repartition the storage in your device and reinstall the stock OS back onto it again. That should resolve yoru issue. I don't know how to do this. Maybe somebody else can chime in a help you out.
Click to expand...
Click to collapse
do you by chance know where the Partition would be because i had not had any luck locating it. or the firmware for that specific region.
Samri13 said:
do you by chance know where the Partition would be because i had not had any luck locating it. or the firmware for that specific region.
Click to expand...
Click to collapse
Ok i got the correct firmware loaded, does anyone know how to Unlock network?
Samri13 said:
Ok i got the correct firmware loaded, does anyone know how to Unlock network?
Click to expand...
Click to collapse
Look up-thread, there's another person (besides you and I) whose had the problem and found solution.
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?