This brick, soft or hard? - Galaxy Tab S2 Q&A, Help & Troubleshooting

I'm not at all experienced with Android or mobile devices in general, and I have an old T813 WiFi (2016) that I needed to root.
I flashed twrp-3.5.0_9-0-gts210vewifi and that worked fine. Except, TWRP couldn't see the download directory where I dropped the magisk zip. I didn't seem to see any internal storage besides the root FS (tab has 60 gig and no sd card).
So on the advice of the internet, I used TWRP to wipe and reformat, resulting in not being able to boot. It gets stuck at the pulsing Samsung logo forever.
I did a factory reset with TWRP and no change.
I then tried to flash stock 6.x firmware using Odin but it failed with an Auth error, I believe due to the device not permitting "downrgades".
So then I used Odin to flash the closest thing to a stock 7.0 ROM that I could find, which was T813XXS2BSJ3_T813XAR2BSA2_XAR from www.sammobile.com. That flashed successfully, the tab rebooted to the stock recovery and loaded the new image, but on the next reboot we were back to same old pulsing Samsung. I left it for a couple of hours, then tried rebooting again, but no change.
I hope it's just that that firmware was for the cell version of the tab, an. d I need the WiFi version. If anyone knows where I can find the right 7.0 firmware for the SM-T813 (2016) it would be greatly appreciated.
I would also welcome any other advice for dealing with this thing.

I'm from the US, and I still have boxes for 3 of my 4 T813s. The part numbers all end in XAR. That being said I went through my filers, and the last ODIN file I used was a XAC file. Looking at Sammobile, just looks like XAC is Canada, XAR is celluar south.
I'm assuming if TWRP couldn't see the directory, you had an encryption issue.
I know I'm still running Akipe's beta TWRP, found in this post. I know it's an "older" version, but I've never upgraded as it had a bunch of fixes that the official one didn't have. Not sure if that ever got corrected or not at this point. That's a question I will ask actually.

OhioYJ,
I have the WiFi version, so it has no sim and no LTE radio, I assume. I'm pretty sure the XAR file is for cellular tabs. I did try it, and it did flash OK via Odin, but it wouldn't boot.
I couldn't find the stock 7.0 version for WiFi anywhere, so I ended up flashing Lineage instead. The tab works now, rooted, so all is well.
I also used the modified TWRP version linked on the Lineage site, which allows MTP in recovery mode so I could dump files where TWRP could find them.
I do wish I could find the stock ROM for the WiFi tab, just in case.

bascc said:
I have the WiFi version, so it has no sim and no LTE radio, I assume. I'm pretty sure the XAR file is for cellular tabs. I did try it, and it did flash OK via Odin, but it wouldn't boot.
Click to expand...
Click to collapse
All the T813s in my house are wifi too, no LTE. Those boxes end in XAR, it's like that even on my newer Tab S5e. So I don't think cellular south necessarily refers to LTE. That being said, the one I have saved on my PC is XAC (Canada), and there are still plenty of XAC firmware files that site.
Either way glad you got it working.

Related

SM-N960U Stuck In Roaming After Moving From Sprint To Verizon

Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?
quackmaster said:
Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?
Click to expand...
Click to collapse
Since you've already done a factory reset I would think the next logical step is to flash the Verizon or the unlocked firmware. What about the SIM card, did they try a new one?
They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?
quackmaster said:
They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?
Click to expand...
Click to collapse
There is a thread somewhere in the guide section I recall seeing before from daillcyruz (I think was the OP). Search it and you will find instructions on how to install the VZ firmware.
I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.
quackmaster said:
I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.
Click to expand...
Click to collapse
Maybe try using Odin?
BladeRunner said:
Maybe try using Odin?
Click to expand...
Click to collapse
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.
quackmaster said:
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.
Click to expand...
Click to collapse
I ran across a thread where someone had posted a version of Odin that ran on Linux.
Here's one: https://forum.xda-developers.com/android/general/utility-odin-linux-jodin3-casual-t3777030
and another: https://forum.xda-developers.com/android/general/odin4-v1-0-linux-t3782930
None of these work. I am not able to get the PIT from device.
quackmaster said:
None of these work. I am not able to get the PIT from device.
Click to expand...
Click to collapse
you might be able to use odin in wine.. i never tried it tho.. heimdall i havent got to work either..
what firmware are you on? pie is pretty good at switchin csc based on sim inserted.. also crk3 i think it is you can access the csc.apk and change csc easily to any csc.. i havent found any other firmware it works on tho besides crk3..
if u can manage that, theres update.zips you can adb sideload but u need to b on specific firmware versions to update to certain firmwares..
i was messin around with firmwares and changed my csc to sprint.. i have vzw.. although it says roaming i am connected to verizon network so dont think its actually roaming but im not 100% sure
OK
Thanks everyone for help!
I was able to successfully flash using a Windows 10 VM running in Oracle VirtualBox VM. I used Odin v3.13_B. I did not re-partition.
I used this firmware:
https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U/VZW/download/N960USQS1ARJ9/242777/
There were no errors though after the phone rebooted it said there was an "unauthorized attempt" to install software.
It then tells me to connect to Wifi in order to verify my identity.
I cannot skip this process.
The Sprint firmware still seems to be present as I see Sprint applications. I am still roaming on Verizon though the port request was completed at least that's what they said at the store.
Interestingly the Sprint logo does not appear upon booting phone. Only the Samsung logo.
To remove Sprint firmware do I need to flash to the non-carrier firmware first before trying Verizon?
I sounds like someone else had the same problem with the SM-N960U.
The solution in that thread seems to be using the SM-N960U1 firmware.
Can anyone confirm this would be a safe fix to try?
SamMobile is a horrible website
I paid the 8 euro fee and the download for https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/VZW/download/N960U1UES1ARJ9/244757/ still takes like an hour.
It seems there's some Google phone protection targeted to deter thieves. That could be why it requires me to sign into the previous Google account after flashing.
I am removing my Google account from the phone, doing factory reset, then will try to flash Verizon firmware.
After flashing again it looks like some software called "Sprint OMDAM" still present on the phone. This loads after flashing. When I try to activate on network it comes up while the phone remains in roaming. Again Sprint unlocked the phone.
Should I re-partition?
OK
I wiped the cache partition and did factory reset.
I will yet again try another flash.
The Sprint logo is gone but Sprint apps still remain.
Should I try to re-partition the phone? I don't understand why Sprint applications are showing up when I flash Verizon firmware using Odin.
Make sure you have a Verizon SIM card in the phone.
1. Remove your accounts (Google and Samsung) under settings.
2. Factory reset under settings.
3. Download the U1 firmware using the SamFirm tool
4. Using modded ODIN 3.13.1B flash all four files (use CSC_OYN not the HOME_CSC file).
Optional, if you want WiFi calling and VoLTE:
Download the VZW N960U firmware using the SamFirm tool and flash it the same way using modded ODIN, but this time include the USERDATA file as well.
I think now on Verizon network after using U1 firmware!

SM-G900F - Need original firmware

Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Access to the original/official firmware for SM-G900F would be extremely helpful for me as well.
I'm running LOS 16 with pico GApps very happily on my S5, however I have mobile data connectivity issues. Data connects and disconnects at random; this is device-dependent (swapping the SIM into other devices gives fully functional data connectivity).
My baseband is G900FXXU1BOA3; I believe updating the modem might fix this?
kwajongen said:
Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Click to expand...
Click to collapse
Fox, you may download the official firmware at https://samsung-firmware.org/model/SM-G900F/
Select your region to get the right ***.md5.tar file to flah via Odin latest.
This will reset your handheld to out of box - original recovery reinstalled - you must reflash it also via Odin if you want to go back to custom Rom..
Good luck
.
Thank you.
What would be my region?
I purchased it in the US unlocked, but US is not a choice when it comes to region.
Would I be able to see the region the phone is from from the baseband #?
Alex
kwajongen said:
Thank you.
What would be my region?
I purchased it in the US unlocked, but US is not a choice when it comes to region.
Would I be able to see the region the phone is from from the baseband #?
Alex
Click to expand...
Click to collapse
If your reference to the baseband version# is correct -> G900FXXU1ANCE, then the region is BTU -> check this address to download the original firmware:
https://samsung-firmware.org/downlo...agon-__/1806/BTU/G900FXXU1ANCE/G900FOXA1ANCE/
After flash via Odin, reboot and optional reinstall TWRP via Odin to use other custom Roms.
Are you sure you did everything before resuming to scratch. Personaly I would have done the following:
- back up in TWRP (at least data) + back up in google drive if you use google or titanium, (anyway save your picts, ...) if rooted, it is possible to save the file containing SMS, ... search in XDA,
- format (not wipe) !!!! WARNING THIS WILL ERASE ALL !!!!!
- clean install the ROM (lineageOS or else) + optional Gapps (I use Pico),
- reboot and restore data (as shown in 2 above)
(The Roms I use on my two KLTE by personal preference order are Havoc, DotOS, Bootleggers, Resurection Remix, MSM-Extended. I also use LineageOS.
Captain Kangaroo said:
If your reference to the baseband version# is correct -> G900FXXU1ANCE, then the region is BTU -> check this address to download the original firmware:
https://samsung-firmware.org/downlo...agon-__/1806/BTU/G900FXXU1ANCE/G900FOXA1ANCE/
After flash via Odin, reboot and optional reinstall TWRP via Odin to use other custom Roms.
Are you sure you did everything before resuming to scratch. Personaly I would have done the following:
- back up in TWRP (at least data) + back up in google drive if you use google or titanium, (anyway save your picts, ...) if rooted, it is possible to save the file containing SMS, ... search in XDA,
- format (not wipe) !!!! WARNING THIS WILL ERASE ALL !!!!!
- clean install the ROM (lineageOS or else) + optional Gapps (I use Pico),
- reboot and restore data (as shown in 2 above)
(The Roms I use on my two KLTE by personal preference order are Havoc, DotOS, Bootleggers, Resurection Remix, MSM-Extended. I also use LineageOS.
Click to expand...
Click to collapse
That site is very buggy, if I search my model and enter all the other info I get to Lollipop 5.0, if I click your link, although I am registered, it does not allow me to the link you provided, I mean I can get to it but when I try to login, it takes me back to the home page, so there is no way to get to your same link while being logged in.
How do I get do the download page it is a mystery to me.
Also, how do you know from the base band that it is BTU region?
Thank you
Alex
PS: I managed to use your link in IE, this site is stone age! Unbelievable, never seen a website like this, there are bugs everywhere.
kwajongen said:
That site is very buggy, if I search my model and enter all the other info I get to Lollipop 5.0, if I click your link, although I am registered, it does not allow me to the link you provided, I mean I can get to it but when I try to login, it takes me back to the home page, so there is no way to get to your same link while being logged in.
How do I get do the download page it is a mystery to me.
Also, how do you know from the base band that it is BTU region?
Thank you
Alex
PS: I managed to use your link in IE, this site is stone age! Unbelievable, never seen a website like this, there are bugs everywhere.
Click to expand...
Click to collapse
Men, the subject of resuming to firmware has been discussed and is described in the net literature! e.g. in XDA Q&A.
This discussion is now not a thread anymore but a dialog and I’m sure it will be closed by XDA moderator for redundancy.
The warnings given when you flash a custom Rom are clear. It also implies “before all” to backup, but also keep all materials to resume to original firmware, …. Now I cannot help anymore because you have problem with downloading the firmware.
Last advice – google baseband# - there are probably other web options or torrents
!!!!Also use the thanks button!!!!
kwajongen said:
Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Click to expand...
Click to collapse
1. Its normal to have the "Set warranty: kernel" text. As my device does too. Just simply ignore it. It won't harm your device.
2. Basically you can search websites that had official Samsung stock firmware. Search your region of your device and (IMPORTANT!) your model, in your case, is G900F. (Wow same as mine but different region, Snapdragon rocks).
3. To your network problem, I think you need to wait. There is no other option.
Thanks!
Edit: https://forum.xda-developers.com/showthread.php?t=2715487
XDA forums has one. Tip: if your region isn't there, the replies have all the filmwares you can have.
Captain Kangaroo said:
Men, the subject of resuming to firmware has been discussed and is described in the net literature! e.g. in XDA Q&A.
This discussion is now not a thread anymore but a dialog and I’m sure it will be closed by XDA moderator for redundancy.
The warnings given when you flash a custom Rom are clear. It also implies “before all” to backup, but also keep all materials to resume to original firmware, …. Now I cannot help anymore because you have problem with downloading the firmware.
Last advice – google baseband# - there are probably other web options or torrents
!!!!Also use the thanks button!!!!
Click to expand...
Click to collapse
I have downloaded the firmware and this evening I will try to upload it and see what happens.
I still I have no answer to my question: how did you figure out that my firmware is BTU?
I mean, I gave you my baseband version #: G900FXXU1ANCE and when you eventually find it in any firmware sites you are given the choice to choose among many countries, expect USA and Canada.
Since I bought the phone in the US I still wouldn't know which country the firmware is from.
Would you mind to shed some light on this?
Thank you!
Alex
OfficialJohnGL4 said:
1. Its normal to have the "Set warranty: kernel" text. As my device does too. Just simply ignore it. It won't harm your device.
Click to expand...
Click to collapse
Thank you for your feedback John.
I am not sure that message is normal, if you google it they all say it is an issue with the firmware and that you need to go back to the stock one to fix it.
Is there anyone else with lineage having that same message?
Also, when I try to format my SD Card, it gets stuck to 40% and then it goes to the homepage.
I tried also a brand new card, same story.
It gives a message but it goes away after a few secs., I believe it is a Java message, but I can try again and take a picture of it.
Thank you,
Alex
kwajongen said:
I have downloaded the firmware and this evening I will try to upload it and see what happens.
I still I have no answer to my question: how did you figure out that my firmware is BTU?
I mean, I gave you my baseband version #: G900FXXU1ANCE and when you eventually find it in any firmware sites you are given the choice to choose among many countries, expect USA and Canada.
Since I bought the phone in the US I still wouldn't know which country the firmware is from.
Would you mind to shed some light on this?
Thank you!
Alex
Click to expand...
Click to collapse
I tell you my experience:
No matter the country you bought your device. As example, I leave in France, I bought mine in Hong-Kong, but choose an international device (G900F).
Before flashing anything, I checked all information in settings and recovery.
Pict below is original out of box G900FXXU1BOC7
Recovery information after latest update G900FXXS1CQD1
It happened recently 2 times my device was stuck because encription issues – I recover by reflashing original G900FXXU1BOC7 via Odin
I personally downloaded firmware as G900F – BTU, because I check the version at each updates and this sticked to BTU ONLY.
May be the site SamMobile will be more meaningful for you, because you see Countries/Operators and updates history.
https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900F/BTU/
For your device, you have to grab the search to find the closest original (which you have) to latest update (if you have it).
For the Kernel yellow tag at warmup, this is done when you flash TWRP. No issues since 2 years operation with that using LineageOS, Havoc, DotOS, AOSP, Bootleggers, RR, ViperOS. If you flash original firmware, it will disappear because twrp is erased and original stock recovery flashed.
kwajongen said:
Thank you for your feedback John.
I am not sure that message is normal, if you google it they all say it is an issue with the firmware and that you need to go back to the stock one to fix it.
Is there anyone else with lineage having that same message?
Also, when I try to format my SD Card, it gets stuck to 40% and then it goes to the homepage.
I tried also a brand new card, same story.
It gives a message but it goes away after a few secs., I believe it is a Java message, but I can try again and take a picture of it.
Thank you,
Alex
Click to expand...
Click to collapse
When it said that you go back to stock one to fix it. Then want if it is not stock? The message is still there. Its normal if you want to install a custom ROM other than the stock one. I reinstall the stock and install custom ROM again once. It still happened.
I don't know how to remove the text but still have a custom ROM tho.
As for the SD card message, I encountered times before. Maybe you need to format using the computer.
Captain Kangaroo said:
I tell you my experience:
No matter the country you bought your device. As example, I leave in France, I bought mine in Hong-Kong, but choose an international device (G900F).
Before flashing anything, I checked all information in settings and recovery.
Pict below is original out of box G900FXXU1BOC7
Recovery information after latest update G900FXXS1CQD1
It happened recently 2 times my device was stuck because encription issues – I recover by reflashing original G900FXXU1BOC7 via Odin
I personally downloaded firmware as G900F – BTU, because I check the version at each updates and this sticked to BTU ONLY.
May be the site SamMobile will be more meaningful for you, because you see Countries/Operators and updates history.
https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900F/BTU/
For your device, you have to grab the search to find the closest original (which you have) to latest update (if you have it).
For the Kernel yellow tag at warmup, this is done when you flash TWRP. No issues since 2 years operation with that using LineageOS, Havoc, DotOS, AOSP, Bootleggers, RR, ViperOS. If you flash original firmware, it will disappear because twrp is erased and original stock recovery flashed.
Click to expand...
Click to collapse
When I reflash the stock ROM TWRP is still there. However no "Set warranty: kernel" appeared. Maybe its just when you install a custom ROM or something, I don't know.
OK guys,
Lineage 16 is installed, everything went smoothly, however when I connect the USB, the phone just shows as 'SM-G900F' on my W10 PC and cannot be expanded, basically no Phone and SD Card folders.
I can see them in the phone no problem, but once I connect it, I am not prompted with the usual message on what I want to do, like file transfer etc. and on the left menu appears only the model of the phone.
I had no issues when I flashed the original firmware, so it must be related to Lineage.
I also installed the Android USB drivers, but no go.
Changing the USB Preferences, to PTP or File Transfer only allows me to see the phone, no SD.
I also tried a new SD, no success.
I am stuck again... Jeez it takes days to get this stuff to work, you do one step ahead and another back
Ideas?
Alex
Anyone?
Shall I ask the question in the Lineage section?
'Set warranty :kernel' means you are running a custom kernel. Any modified boot.IMG can cause this message. It doesn't mean you need to use stock room. This appears even in stock rom with magisk or SuperSU.

Having trouble converting unlocked Note 9 to AT&T firmware

Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
ww007 said:
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
bober10113 said:
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
Click to expand...
Click to collapse
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
ww007 said:
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
Click to expand...
Click to collapse
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
bober10113 said:
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
Click to expand...
Click to collapse
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
ww007 said:
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
Click to expand...
Click to collapse
just use samfirm tool or frija to dl firmware.

Please help! Flashing AT&T N960U firmware on N960U1 device with Android 10

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?

Really desperate for some help guys flashing note 8 stuck in boot mode:

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.

Categories

Resources