Related
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Bump?
Have you tried using Samsung Smart Switch?
DevicesNow said:
Have you tried using Samsung Smart Switch?
Click to expand...
Click to collapse
I didn't try Samsung Smart Switch, but I had reflashed it using Odin, and tried a factory reset and it didn't fix it, i got it fixed through Z3X box.
This happened to me also.
ashal said:
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Click to expand...
Click to collapse
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Hunterzzz said:
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Click to expand...
Click to collapse
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
ashal said:
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
Click to expand...
Click to collapse
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Hunterzzz said:
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Click to expand...
Click to collapse
Not sure about that but we can't update because probably our CERT files have been patched in EFS is messed, I got it done back in July 2017, and at that time, the guy who repaired it said that they didn't have Z3X's software update for Nougat, so they had to downgrade my phone to Marshmallow, and the patch they used won't work on Nougat. Don't know about yours though, maybe he used an updated patch or a different tool, you can ask that guy whether if its safe for you to update to Nougat or not, if he allows it, then try flashing Nougat through Odin, if it doesn't work you'll have to get it patched by him again. Don't update if he doesn't allow, otherwise he won't patch it again without extra charges, and if he allows that and something goes wrong you can blame him for that
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
leprkon said:
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
Click to expand...
Click to collapse
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
Thanks for the prompt reply! I am downloading the file right now from sammobile. Let's hope it has everything needed! Thanks again!
Please let me know what worked, didn't. I may be doing the same very soon.
Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
leprkon said:
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
Click to expand...
Click to collapse
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
BlueFox721 said:
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
Click to expand...
Click to collapse
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
I failed to mention that you needed the modified Odin. I think it is normal for it to stop at 32% and then start erasing. It did the same when I went from unlocked variant to vzw. Keep us updated on your progress.
leprkon said:
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
Click to expand...
Click to collapse
The boot to bootloader is In the main recovery menu, but yeah...you need to use the modified odin
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
Support SINGLE-SKU
Supported API: 3
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
-- Installing package...
Finding update package...
opening update package...
Verifying update package...
Update package verification took 1.1 s (result 2).
Installing update...
Successfully installed package.
-- Resizing data...
E:failed to mount /data (Invalid Argument) can't mount '/data', rc = '-1'(Invalid Argument)
E:failed the resizing-data-- omc_binary_download...
-- Deleting selective files
Successfully deleted files selectively
-- Deleting RSU selective file
Successfully deleted RSU selective file
-- amazon_symlink_vze...
-- Deleting VZW's apn file
Successfully deleted VZW's apn file
Successfully verify for dmverity hash tree.
Click to expand...
Click to collapse
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
leprkon said:
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
Click to expand...
Click to collapse
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
BlueFox721 said:
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
Click to expand...
Click to collapse
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
leprkon said:
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
Click to expand...
Click to collapse
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
BlueFox721 said:
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
Click to expand...
Click to collapse
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
leprkon said:
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
Click to expand...
Click to collapse
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
BlueFox721 said:
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
Click to expand...
Click to collapse
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
leprkon said:
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
Click to expand...
Click to collapse
Good to know....I try to use updato when available...how is that one?
BlueFox721 said:
Good to know....I try to use updato when available...how is that one?
Click to expand...
Click to collapse
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
leprkon said:
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
Click to expand...
Click to collapse
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...sorry I didn't think of it sooner...hope it helps.
Looks like we need factory binary and Canadian firmware...
BlueFox721 said:
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...
Click to expand...
Click to collapse
I've done version 3.12.7 and PC 3.12+
I'll try the carrier switching instructions again, but I couldn't get it to work properly. I'll let you know how it goes.
Edit -
It looks like those instructions require a factory binary firmware flash. Is there a way of doing it without that?
I've got an unrooted xz1c that came with some sort of non-US stock firmware - which I know, because the fingerprint reader works. It's been nagging me to update it to Pie since I bought it, and I'm thinking I'd like to do it via the "official" (OTA) route, since it claims to be able to do it in-place, without having to reinstall apps, restore data, etc. What I want to avoid, though, is ending up with a US update, losing my fingerprint reader, and having to jump through hoops to get it back.
The build number in About Phone says 47.1.A.12.270. Is there some way of determining the current region, and confirming what region the update plans to install (without starting the update) - and/or forcing the region to match what I currently have? My google accounts, phone #, etc. are all US-based, if that makes any difference in terms of the update deciding what region is appropriate.
I was looking at a guide for installing specific region firmware via xperifirm/newflasher, but it indicated that the result would be a wiped phone, and I don't have time to deal with re-configuring everything from scratch right now.
Firmware customization does not change by applying OTA update. It will install the update of the same region that is already installed.
meeotch1 said:
I don't have time to deal with re-configuring everything from scratch right now.
Click to expand...
Click to collapse
In the past the OTA updates have famously locked thier owners out of thier phones by not regonising the unlock code that has been set, so make sure you disable it before you start.
Also, updating from 8 to 9 leaves some apps glitchy and there have been several reports of phone problems that can only be resolved by a full factory reset.
If you want the best experiance from your phone, wiping it would be the best option when upgrading.
Use Xperia transfer to back up apps/call history/contacts/text history. Then restore once you've wiped your phone.
@meeotch1 If you are happy with Oreo and without the latest security patches and updates, just let the phone OTA update it to the final Oreo version 47.1.A.16.20 and leave it there.
You can force close the Software update app from app settings to make it stop nagging about the update. And with adb you can even disable it permanently (and enable later if you wish to go for Pie).
Thanks for the advice. Good to know that the nag is disableable. So I take it that OTA upgrades *within* major versions (so Oreo 47.1.A.12.270 to 47.1.A.16.20) do not suffer the glitches mentioned by the first reply above?
Also, when I eventually go Pie, what's the least painful / most reliable restore method after wiping the phone? Is the built-in Xperia backup/restore available in Settings good enough? I'd prefer not to upload all my data to Google, unless there's some guarantee that it's encrypted. Don't need the NSA digging through my messages to radical terrorists and international drug lords.
To find out the customization, go to the service menu and select "Software Info".
You'll see an entry named "Customization Version" with a number like "1310-4371_R6C".
You can then look in XperiFirm at the column named "CDA".
On the example I gave, "1310-4371" corresponds in XperiFirm to "Customized US".
You can also look further down in the software info at "Current Modem Config" where the format will be something like:
/system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn"
That tells me that my SIM card matched a mobile operator that is recognized as having a valid modem configuration file for my customization's region and, as such, loaded the correct modem file for that operator.
It also shows that I'm using T-Mobile US as my operator (tmobile_us) and I have some kind of VoLTE available (ims).
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Greeny308 said:
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Click to expand...
Click to collapse
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
brokenbrain939 said:
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
Click to expand...
Click to collapse
how do I do this?
I can get into the boot menu and have tried all options as in:
Wipe cache partition
Wipe data/factory reset
reboot system now
still stuck in boot loop (1st power on screen)
brokenbrain939 said:
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
Click to expand...
Click to collapse
Greeny308 said:
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Click to expand...
Click to collapse
What did you flash in your second attempt?
stonedpsycho said:
What did you flash in your second attempt?
Click to expand...
Click to collapse
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Greeny308 said:
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Click to expand...
Click to collapse
It should boot after flashing that, it could be a hardware problem preventing a successful boot :-( Probably worth trying different filmware though, you could try BTU (UK) or XEU (UK & Ireland)
Bro i will advice you to just get over this stock rom and install some custom rom.
You can install a custom recovery like twrp through odin and then using that recovery install some custom rom made for your device.
All these you might find in your device's xda forum.
Brp i just checked and found that galaxy note 8 has plethora of custom roms available just install the one which you like.
You can see the installation process on youtube.
Samsung Tab S8+ won't update via wifi, I get a server error message when I try, last worked in June and since then it hasn't worked. Tried clearing cache, restarting and everything else I can think of. Contact Samsung, I'm just saying phew... not much help there. Anyone have a solution to the problem?
My Samsung Tab S7+ 5G is working fine on wifi, no problems at all.
Hi. To be 100% clear, you don't have the bootloader unlocked, and you're not rooted, correct? (Although I wouldn't necessarily expect the problem you're facing with both of those things)
Bootloader locked, no root, just like straight out of the box.
What CSC (Country Specific Code) is your Tab S8+? Quoting another user on here - I don't remember who:
Go to settings > about > software information > service provider SW ver
The region code (CSC) will be written there.
Click to expand...
Click to collapse
And what specific model number?
I don't really have any specific suggestion other than a factory reset, which I know is extreme, and wouldn't guarantee to fix the issue. You could always use the SamFirm or Frija Windows programs to manually download the firmware, and use Odin to flash it. As long as it's the completely stock Samsung firmware of any type for this device, it will work without unlocking the bootloader.