Hello community,
I have actually came across a difficult situation with my Galaxy S3 LTE i9305 (international variant).
In order to give you a high level view of what happened im going to write a few topics of what I have flashed to the phone since I bought it (new) back in March 2012:
1. I'm from Portugal and I bought the phone on an online retailer because I wanted the grey version. So far so good I ordered it on the UK.
2. The phone I received, although being unlocked and sealed/new, had software branding from MDA germany.
3. At the time we were on Android 4.1.2. I went to sammobile and installed the TPH version (Portugal) of 4.1.2 in order to have the full stock experience. Eventually I rooted the device.
4. Later on came the 4.3. At the time I was not aware of the bootloader complications and ended installing the UK or German version (clean) that was on Sammobile. Installation went fine and I immediately rooted the device without issues and disabled Knox in the Rom.
5. Yesterday I had this great idea of flashing 4.4 (still unaware of bootloader issues) and downloaded the spankin new 4.4.4. from the nordic countries from sammobile. This is where it gets interesting.
6. I have tried a zillion combinations and either I get stuck on the samsung logo or I get the error of binary 3 and device 2 (or the other way around). All the flashes via ODIN have been done using the AP/PDA option.
What can I do to unbrick it? I don't remember which ROM I flashed for 4.3 and I have tried to flash the german version of 4.4 (set 2014) and the nordic countries one. Also tried flashing 4.1.2 via CWM recovery directly from SD card but still no go and stuck at bootloop. Have also tried software repair using Kies (manually inserting serial number under the battery) and still no go for my dismay...
Is it recoverable? Is there a way to upgrade it to 4.4? If it helps so far I have been able to fash stuff via ODIN and still have download mode. I dont care about data as I did make a backup before setting off on this "adventure" :laugh:
Thanks in advance.
Eventually solved using Philz recovery. Turns out that during the flash process for some reason the /data partition could not be formatted.
Now recovered and running the clean 4.4.4. of XDA
Hey all. I decided to pick up a Note 8 Snapdragon variant LDU on eBay to see if I can get it to work on a stock rom. After researching through numerous posts on XDA and videos on YouTube, I took the plunge and decide to see for myself. I wanted to use a stock rom to get past the 70% battery cap on LDU's.
Some people claimed they were able to get it to run a stock rom and some failed. (Yes, this is a LDU. I bought it from a liquidator on eBay).
Here's exactly what I did (I've tried flashing many different roms, but to no avail).
1. Tried to enable OEM unlocking through developer options using date method = did not work.
2. Found me2151's thread on rooting Snapdragon variant of Note 8 = bootloop with QVPASS = 1 QVDONE = 1 prior to Samsung Note8 logo
3. Found a comment on me2151's thread saying they had the same bootloop... Solution was to check "phone bootloader update" (link here)
4. Tried above method in the comments and checked phone bootloader update = did not work, still on bootloop
5. Downloaded a stock rom for N950XU with Frija. ROM is N950USQS5CRL1, released 2018-12-27
6. Flashed the rom using ODIN v3.13.1_3B patched = did not work, "Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost."
7. I'm still able to go into download mode despite that error, but I have no idea what to flash now...
Any help is appreciated! Just want to get it to boot to Android, don't even care if it's the retail rom.
Hey ,I have the same issue, also bought the phone from a liquidator last week, Did you find any workaround?
azrael235 said:
Hey ,I have the same issue, also bought the phone from a liquidator last week, Did you find any workaround?
Click to expand...
Click to collapse
We might have bought it from the same place then.
Which bootloader version is your phone on? If you didn't flash a newer ROM and is still on bootloader rev 1, then you may be able to fix it.
hi, i was able to remove modem fail error by flashing a modified version of cp file
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?
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.
Hi!
It's a long story, but I need newest combination file. I couldn't find newer than u3, but I need u8, because I have s8 rom installed and bootloader won't let me install older version of course.
My current pda is a715fxxs8bvc2 ; csc - a715fprt8bva1.
And my long story is:
I've bought used a715f/ds 2 years ago. I've used it for these 2 years and now I've switched to s21+ 5g. I did a factory reset of a71 and gave it to my friend. The next day my friend tried to set up this phone and was copying her files, but got a message that phone is blocked by carrier (kg lock) "t-mobile", which is a fun thing, because phone was bought at other carrier "play". I called t-mobile, but they said that thay can't tell me nothing, because I'm not the orignial buyer. I tried contacting the person from which I bought the a71, but he didn't respond. So, I tried flashing rom and that's when I found out about the kg lock. I tried searching the internet and I tried few things. While searching the internet I found out a guide on xda forum in which someone suggests flashing pit file and then using "boot to bootloader" option, which opens fastboot and then to flash combination file from there. I have no idea how to flash combination file from fastboot and I coudn't find any guide for this, so I tried good old odin, but I get error in odin, because only combination files I could find are u1, u2 and u3 (android 10Q) and I need u8 (android 11R) or newer.
P.S. I've also contacted "play", but they haven't responded yet. (I've called to t-mobile, but I've used in-app chat function for play, because I'm their user)
P.P.S. Bootloader is unlocked. My plan is to flash newest rom after flashing combinantion file (which I hope will take down kg lock) and then do magisk and try to use some tools to fake/change imei, so my friend could use normal phone functions (call/sms).
If you have any other ideas, please let me know.
me to need that new version