Develop Bugs

Help me flash stock ROM on M919 which currently has i337 ROM

Hi guys, I'll admit I'm a noob, but I'm trying my best to understand the ins and outs of flashing ROMs. I recently purchased a used S4 SGH-M919. The problem is the phone has i337 AT&T firmware on it. (I'm pretty sure it's a stock ROM and not rooted). I need to find a way to use the Tmobile network on this phone, so I have been trying revert to stock by flashing the stock M919 ROM on the phone using odin. Odin repeatedly fails before the flash begins. Odin dislays "FAIL! (Auth)" and the phone displays message "SECURE CHECK FAILED : aboot". I have tried several different .tar.md5 firmware files from sammobile. I have tried several USB cables and every USB port on my PC. The phone isn't quite bricked, it still boots fine it's just the network unusable with my t-mobile sim and the at&t firmware.
Do I need to wipe the phone and do a kernel flash? I'm lost and any advice would be appreciated
Thanks in advance,
Ryan

pull out the battery and MAKE SURE the PHYSICAL sticker behind the battery says model SGH-M919 (not SGH-M919V) but exacly SGH-M919.
if that has been confirmed then download the ODIN image from sammobile
Download the latest M919UVUFOH3
install via odin using the PDA or AP slot depending what version of odin u have it will say PDA or AP.
btw: you are getting SECURE CHECK FAILED : aboot". error because you are either flashing wrong image or too old of a image and the boot wont allow it.

are you sure that it is not a stock I337 ? If it is, it would be much easier to just obtain the SIM unlock code to use it with T-Mobile, I337s are really difficult to root and the sim unlock code is free and takes less than 5 minutes on the at&t website

XeoNoX said:
pull out the battery and MAKE SURE the PHYSICAL sticker behind the battery says model SGH-M919 (not SGH-M919V) but exacly SGH-M919.
if that has been confirmed then download the ODIN image from sammobile
Download the latest M919UVUFOH3
install via odin using the PDA or AP slot depending what version of odin u have it will say PDA or AP.
btw: you are getting SECURE CHECK FAILED : aboot". error because you are either flashing wrong image or too old of a image and the boot wont allow it.
Click to expand...
Click to collapse
c_irie said:
are you sure that it is not a stock I337 ? If it is, it would be much easier to just obtain the SIM unlock code to use it with T-Mobile, I337s are really difficult to root and the sim unlock code is free and takes less than 5 minutes on the at&t website
Click to expand...
Click to collapse
Thanks for the replies fellas. I am sure it's a stock SGH-M919. The sticker beneath the battery says so. I've already tried using the most recent firmware from sammobile (ending with OH3) with odin and I receive the same error no matter what. I've even tried multiple versions of odin and have used PDA or AP accordingly.
c_irie, It's not a stock i337, I've read about the bootloader issues and Loki regarding that model. I would really prefer to do a clean M919 flash, but do you think I could use a sim unlock code from at&t with my current situation?

This may not be useful information, but here's exactly what is displayed at the top of the screen when I boot into download mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled

rkham said:
This may not be useful information, but here's exactly what is displayed at the top of the screen when I boot into download mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Click to expand...
Click to collapse
seems like someone sold you a "hybrid S4" the casing with sticker of the m919 but the "motherboard" of a I337...
was probably a "fixer upper" normally from those shady mom and pop cell shops/ebay/craigslist. consider that you got yourself a sgh-i337 even tho the outside doesnt say so...the board inside matches that of a i337 i will gaurentee u.

XeoNoX said:
seems like someone sold you a "hybrid S4" the casing with sticker of the m919 but the "motherboard" of a I337...
was probably a "fixer upper" normally from those shady mom and pop cell shops/ebay/craigslist. consider that you got yourself a sgh-i337 even tho the outside doesnt say so...the board inside matches that of a i337 i will gaurentee u.
Click to expand...
Click to collapse
Thank you for opening up a new realm of possibilities for me. I hadn't thought of that. Why would someone re-brand a i337? Do you think odin is failing because I have the wrong image for a i337?

Problem solved for now. I went ahead and assumed that it's actually an i337. I followed the suggestion above and requested an unlock code from at&t using the imei found in settings. I didn't think it would work, i figured the phone was stolen, but the code from at&t worked and I can use the t mobile network! thanks guys. I'm kind of bummed that it's an i337 since it will be difficult to root if i ever go down that path.

glad we where able to help you out. Sorry to hear that someone kinda scammed you and sold you the wrong phone. To be honest with you tmobile phones have a slightly higher resale value too...i hope you didnt pay the extra premium..esp since it was a fixer upper phone. well anyways glad you got it all figured out. btw: the att s4 on tmo is missing a band but you can possibly unlock it to have all the tmo bands.
http://forum.xda-developers.com/showthread.php?t=2291589

Yeah it's definitely not the device I was hoping to receive. I've discovered a few issues. I haven't been able to use internet at all without wi-fi, and the mic doesn't work in calls for some reason so I use speaker phone. Other than that, it seems to be working very well.

rkham said:
Yeah it's definitely not the device I was hoping to receive. I've discovered a few issues. I haven't been able to use internet at all without wi-fi, and the mic doesn't work in calls for some reason so I use speaker phone. Other than that, it seems to be working very well.
Click to expand...
Click to collapse
if you have used a factory ODIN image and flashed it and you have all those problems then im sorry to say it was probably a "fixer upper" phone that wasnt fixed properly. sorry to hear you are having all those problems...that sux. i always thoroughly test new phones IN PERSON before i buy them. i do the sim card test, screen color test, mic test, speaker test, model number test. and a voice and data and wifi test.

installing tmobile on att version
f irst of all you have to have root second you need to install a custom recovery such as TWRP. then you need to download the Wicked V.10 zip.then boot into recovery mode white data cache partition and dalvik cache partition.actually install the zip file you downloaded for the wicked v10 Rom. But make sure download the tmobile version because it willautomatically change your CSC settings

maybes this will help
Ok first things first. You have to be rooted and already have a custom recovery installed like TWRP or CWM. If u aren't rooted then try the king root apk. Once u have root access then you can go to download mode on your phone. Most of the Phones the power button & volume down at the same time will take you to download mode you have to search on Xda for the custom recovery version that is for your phone model it also has to be the Odin compatible ".tar" file. I use Odin 3.9 just because it seems to work better but after u have everything I've listed the install Odin 3.9 on your computer. Once that is done u have to remember where the custom recovery u should have already downloaded is located. Right click on the odin icon and click run as administrator make sure that you click on the BL button because that is where you will place the custom recovery.tar file. when you click on the BL button it will open up a window where you can search for the custom recovery that you downloaded earlier once you find it click on it and it will automatically go to the BL box then you click Start and just let Odin finish doing what it has to do when it says complete unplug your cable from the computer out phone reboot your phone hold volume up that should take you to your custom recovery once you have your custom recovery installed you can backup your whole system install zip files custom roms. things of that nature I hope this helps feel free to msg me if u have problems

Wifi and Bluetooth not working Verizon Galaxy Note 4

I have a used Verizon Galaxy Note 4.
I can't turn on the WIFI or the Bluetooth.
Nothing happens when you tap the buttons for either of these.
So far, I opened it up and detached and reattached the 2 cables for wifi and Bluetooth . This did not resolve the problem.
It also appeared to have a custom firmware on it so I used odin and installed the latest original firmware but it did not solve the problem.
I was wondering if it could be the charging port board or the Bluetooth and wifi cables but I have read that some people had to swap the main board instead.
A couple of other unusual things,
If I go to settings and tap "System Updates" it says Software update is temporarily unavailable "
Also, if I boot to recovery mode it says "Installing system update" and then says "No command" and finally goes to the menu.

What bootloader are you on? Also what is your baseband and currently installed android version? What firmware did you flash? Is your carrier Verizon?

I couldn't log back in here for some reason so I had to use a different account.
Yes it is Verizon
Baseband: N910VVRS2CQC1
Android Version: 6.0.1
Firmware: MMB29M.N910VVRU2CQC1
In bootloader it says:
Odin Mode: (High Speed)
Product Name: SM-N910V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Qualcomm Secure Boot: Enable (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START

JediYeti said:
I couldn't log back in here for some reason so I had to use a different account.
Yes it is Verizon
Baseband: N910VVRS2CQC1
Android Version: 6.0.1
Firmware: MMB29M.N910VVRU2CQC1
In bootloader it says:
Odin Mode: (High Speed)
Product Name: SM-N910V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Qualcomm Secure Boot: Enable (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
Click to expand...
Click to collapse
If you have data working, can you download this from the playstore https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and after you install and open it, scroll over to firmware and tell me what it says there. That will tell you what bootloader you are on. You should be on the CPD1 bootloader.

dhplap said:
If you have data working, can you download this from the playstore https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and after you install and open it, scroll over to firmware and tell me what it says there. That will tell you what bootloader you are on. You should be on the CPD1 bootloader.
Click to expand...
Click to collapse
I thought we got an update after pd1 that could he could potentially be on . I realize the bootloader didn't change but it may have gotten renamed to the appropriate firmware . That looks right (his device info) if it were stock updated

mojoswagger1980 said:
I thought we got an update after pd1 that could he could potentially be on . I realize the bootloader didn't change but it may have gotten renamed to the appropriate firmware . That looks right (his device info) if it were stock updated
Click to expand...
Click to collapse
The information he provided doesn't show what bootloader he is on though.

Yetisimo said:
I have a used Verizon Galaxy Note 4.
I can't turn on the WIFI or the Bluetooth.
Nothing happens when you tap the buttons for either of these.
So far, I opened it up and detached and reattached the 2 cables for wifi and Bluetooth . This did not resolve the problem.
It also appeared to have a custom firmware on it so I used odin and installed the latest original firmware but it did not solve the problem.
I was wondering if it could be the charging port board or the Bluetooth and wifi cables but I have read that some people had to swap the main board instead.
A couple of other unusual things,
If I go to settings and tap "System Updates" it says Software update is temporarily unavailable "
Also, if I boot to recovery mode it says "Installing system update" and then says "No command" and finally goes to the menu.
Click to expand...
Click to collapse
Hey man I m not sure how far you've gone but I'd have to suggest a complete factory reset then wipe from recovery then reinstall via Odin (latest firmware down to bpa1 should all be usable if you plan on rooting you need to go back anyway . Either way your info is correct something is wrong with your radio flash either pd1 or bpa1 just to be certain the bug isn't inherint to your current firmware

Thanks. It says Bootloader version N910VVRU2CQC1
Some other things while I'm looking.
PDA VERSION N910VVRU2CQC1 / N910VVRU2CQC1_QC4
CSC VERSION N910VVZW2CQC1
BASEBAND N910VVRS2CQ1
Kernel Version 3.10.40-8025465
[email protected] #1
32 BIT
ROOT EXISTENCE No

JediYeti said:
Thanks. It says Bootloader version N910VVRU2CQC1
Some other things while I'm looking.
PDA VERSION N910VVRU2CQC1 / N910VVRU2CQC1_QC4
CSC VERSION N910VVZW2CQC1
BASEBAND N910VVRS2CQ1
Kernel Version 3.10.40-8025465
[email protected] #1
32 BIT
ROOT EXISTENCE No
Click to expand...
Click to collapse
Well that looks right. I would take mojoswagger1980's advice.

I think that's what I already did unless I'm missing something. I did factory reset and wipe and installed the aforementioned firmware with odin.
I'm new to this.
Are you saying I missed something?
should i try again with a different firmware?

JediYeti said:
I think that's what I already did unless I'm missing something. I did factory reset and wipe and installed the aforementioned firmware with odin.
I'm new to this.
Are you saying I missed something?
should i try again with a different firmware?
Click to expand...
Click to collapse
Could you provide the link of the firmware that you flashed with Odin?

Ok.
Please note that this problem existed before I updated firmware.
I was hoping that updating firmware would fix it.
---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------
The link was
https://www.androidfilehost.com/?fid=745425885120726202

JediYeti said:
Ok.
Please note that this problem existed before I updated firmware.
I was hoping that updating firmware would fix it.
---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------
The link was
https://www.androidfilehost.com/?fid=745425885120726202
Click to expand...
Click to collapse
Can I get the link to the thread that file came from? I checked Paul Pizz's threads and didn't find that exact download file. It seems like that should have worked. Might have been a bad download. I would try again and if that doesn't work I would Odin back to bpa1. That's lollipop but that would give you a fresh start so you could unlock your bootloader if you decided to. That's just my opinion though.

Could you send me links to good files please?

JediYeti said:
Could you send me links to good files please?
Click to expand...
Click to collapse
Try this with Odin https://www.androidfilehost.com/?fid=529152257862721079

I tried it but it didn't fix it. Maybe a hardware problem.

JediYeti said:
I tried it but it didn't fix it. Maybe a hardware problem.
Click to expand...
Click to collapse
are you sure its a verizon note 4? its easy to flash other carriers ROM . please post a pic of your devices about phone screen(s) so we have an idea what firmware we r talking about . you do lose WiFi f you take safe upgrade maybe you got a phone only partially updated . need more info

N930V can't downgrade/flash any rom lower than ver.3, stuck in download mode X(

Hi guys,
I'm stuck with my note 7, n930v in download mode because I can't flash any firmware.Everytime when I am trying to flash this one N930VVRS1APH1 or N930VVRS2APHE I'm getting the same error in download: SW. Rev. CHECK FAIL: fuse 3 binary x, where x=1 for PH1 and x=2 for PHE.
What can I/we do when we are facing this problem? I am searching for a rev.3 firmware since 6 days, I will probably incinerate this phone finally if there is no solution to download that firmware.What exactly is this stupid sw.revision and why can't be bypassed....:| ?
However, is there anyone here who have any idea with that? Thank you !!
Cheers

I encountered the same problem. Any one can help us? Please!

Up??

You've updated your bootloader to revision 3. This is the same across all current samsung devices. You won't be able to downgrade to a revision 1 or 2 firmware now. Not unless you unlock the bootloader somehow.
I saw this thread in the forums: https://forum.xda-developers.com/ve...nbrick-verizon-note-7-matter-how-bad-t3467085
He used the Verizon Repair Assistant tool to make the device download the latest firmware from Verizon Servers. Maybe that will work if you can't find a Binary 3 Firmware. I mean I did a search on google for N930VVVRS3 firmware and got zero results.
I also found this Binary 3 Firmware File here in the forums:
AP_N930VVRS3APL2_CL8720001_QB11952598_REV00_user_l ow_ship_MULTI_CERT_meta.tar
I found this thread from GSM-Firmware showing an official VZW Binary 3 Firmware link: http://forum.gsm-firmware.com/showt...B11952598_REV00_u-ser_low_ship_MULTI_CERT-tar
Flashing that will downgrade your aboot version. Once that is fully installed and has booted up once, try flashing just the AP file from a binary 2 or binary 1 firmware, doing a factory reset from recovery immediately after flash before letting it fully boot. It worked on my AT&T Note 5 to get Rooted 5.1.1 running again after I had updated my bootloader too far. Although that might be a shot in the dark using Official VZW firmware.
You will want to get the 3APL1 Combination file or another Binary 3 Combo for N930V. And then try to flash a binary 1 or 2 AP file only. Don't flash a binary 1/2 BL or CP file. If you get the AP file to flash, then you can flash the CSC file.

battery dead fix last firmware
https://drive.google.com/file/d/1_PtuCij2SRPeGcCGiZ9vWSPF-n6IJZNw/view

Error when installing stock OS: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6

Recently I rooted my S9 and installed Lineage OS but I didnt like it and decided to swap back to the stock OS. I used Frija to get the .tar.md5 files for Odin but once I select all the files and hit start the log in Odin loads up to system.img then stops and I get the SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6 error on my phone. Any idea on how to fix this? I'd really appreciate some help as I'm going to be travelling soon and I need my phone for it and I'd prefer not to use Lineage OS. Thanks in advance.

Do you have an At&t branded phone? SM-G960U?
I am having a very similar problem. A customer came in and was having issues with device. I told them to back up, wipe, and update device. That didn't work so I tried a full flash with ODIN. Now I can't get the phone to boot at all and it says, "Secure Check Fail : Modem" and "Unauthorized software visit nearest AT&T blah, blah,..)
I think it is because AT&T has pushed out the latest update(OCT. 18th), but the Odin files are not out yet. According to:
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U
G960USQS7CSI5 is the latest FW. If you google it, there are only four results.

Yep, the problem was the phone was on the latest FW. Newer firmware was just uploaded a few days ago.
I flashed:
G960USQU7CSJ2_G960UOYN7CSJ2_CHA
and now I'm booting again.
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."

ma777 said:
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
Click to expand...
Click to collapse
^^^^ this ^^^^
the Odin error is telling you that youre trying to flash a revision of the bootloader than was last installed on the phone. to to sammobile.com/fimrwares and get the one with the correct bootloader for your specific phone and flash that.
also download the firmware with the frija tool or samfirm. trust me, its literallt 5x faster than a direct download from the site. The 5 min it takes to get samfirm up and running is worth it, believe me on that.

I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted

Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!

Youdoofus said:
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Click to expand...
Click to collapse
Getting no help was meant I hadn't Posted asking Questions, I read everything ya'll put up and I was able to do it on my own without continuing to ask, so Yeah I did get help here but not by asking only reading what is available

downgrade samsung sm-g570m
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??

pol1345 said:
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
Click to expand...
Click to collapse
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.

TheMadScientist said:
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
Click to expand...
Click to collapse
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?

pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
Like 99.9%. That's what that error is. The bootloader is blocking downgrade

pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
yes, if you get a firmware version matching the one last installed on your device, itll go right thru and boot just fine. Goodlock is finally working on all modules for A10 as well. Maybe we will see more development occur with this shutdown going on. Let us know if you run into any trouble, the error you were getting is totally resolvable!

at the end I give up on it..! my internet 2 slow 4 go downloading & trying rom after rom.! i am from venezuela.

Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
I have S20+ running Android 11 with U7 Binary. I tried downgrading to Androi 10 which has Binary U5. Now I have downloaded the Binary U5 file. But in some video, he is telling that you should download the Binary File with the same number as it is currently installed in your phone, which in my case is U7. So? Am I supposed to download U7 Combination Binary file and flash it in order to downgrade to Android 10
OR
Should I flash the U5 Combination File and flash the Android 10 AP, CSC, BL, HOME ???

Someone has Combination file to G960F with bootloader SF (Version 15)?

got bamboozled into buying a knox-tripped S9, and I'm at a loss on what I should do?

Help a brother out bros,
I'm new to android, been using a Nokia 808 for the past 7 years, and Nokias in general since 2006. anyway I'm from a ****ty 3rd-world country with no official Samsung dealer, so we're stuck buying whatever these 3rd-party merchants provide, so I got what appeared to be a sealed, brand new Samsung S9 (it was the smallest device I could find with acceptable specifications, if it was 1 cm shorter, and 0.5 cm narrower it would've been perfect).
Shortly I noticed that some text is dark grey/black against a black background, which makes it very difficult to see; upon googling, I found out that the issue was fixed with a software update, so I looked through 'setting' for the update function, and immediately noticed, I was having difficulty find it, I thought it was weird to have it hidden like that; and again upon googling I found out that it's supposed to be in [Settings > System Update > Download and Install] it's not there. I can only find it by typing "system update" in the 'search' box, and even then touching "Download and install" did nothing, no feedback whatsoever.
Anyways upon further googling and googling, I came to the conclusion that the device is rooted and knox is tripped, now the problem is the product number of the device which caused me confusion, in the software and on sticker at the back of the device it states the following
SM-G960F
IMEI1: ***MOD EDIT-IMEI REMOVED***
IMEI2: ***MOD EDIT-IMEI REMOVED***
SN: ***MOD EDIT-SERIAL REMOVED***
MADE IN VIETNAM BY SAMSUNG
but when I got into Odin mode it states that the model number is actually SM-G960N. so my questions are:
1. if I were to flash back to an official firmware using odin should I use the one for SM-G960N or the one for SM-G960F? keeping in mind that this was peddled to me as dual sim device, and it does support two sim cards.
2. If my device is indeed Korean, is it okay if installed firmware with PDA: G960FXXU7CSJ1 instead of firmware PDA: G960NKSU2CSJ1? are there any differences?
3. is it possible to fix Samsung-related issues like the black text against black backgrounds through some other methods like using a different rom/launcher/environment or whatever?
4. how do you recommend I proceed? what would you do if you were in my place?

According to your IMEI (that btw you should never share publicly), your phone is a SM-G960N. If knox is tripped, the only way to update the software is to flash through Odin. Since your phone is already rooted, i also advice you to check out some custom rom you can find in this forum. They're a nice improvement over the stock firmware.
if you want official firmware, you have to install one from this list
https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960N/

effry said:
According to your IMEI (that btw you should never share publicly), your phone is a SM-G960N. If knox is tripped, the only way to update the software is to flash through Odin. Since your phone is already rooted, i also advice you to check out some custom rom you can find in this forum. They're a nice improvement over the stock firmware.
if you want official firmware, you have to install one from this list
Click to expand...
Click to collapse
does installing a custom rom fixes/removes samsung-related issues like the dark text against black backgrounds?
what harm could be done if people knew my IMEI?

Coomer91 said:
does installing a custom rom fixes/removes samsung-related issues like the dark text against black backgrounds?
what harm could be done if people knew my IMEI?
Click to expand...
Click to collapse
If the custom rom is based on a samsung firmware that already fixes the issue then yes. For what i've found , your issue was fixed around of April 2019, so any ROM based on a firmware released after that date will include the fix.
Regarding the IMEI, you don't share it because is an unique identifier number. It's like giving out your ID card or passport number. Someone could impersonate you with your phone company and provide the IMEI as a proof.
You can read more here -
https://www.quora.com/What-can-we-do-with-someones-IMEI-number
https://ting.com/blog/understanding-imei-the-vin-of-the-mobile-phone-world/

effry said:
If the custom rom is based on a samsung firmware that already fixes the issue then yes. For what i've found , your issue was fixed around of April 2019, so any ROM based on a firmware released after that date will include the fix.
Regarding the IMEI, you don't share it because is an unique identifier number. It's like giving out your ID card or passport number. Someone could impersonate you with your phone company and provide the IMEI as a proof.
Click to expand...
Click to collapse
thanks for the answers effry, I do have one more though so bare with me.
the currently installed firmware is SM-G960Fblahblahblah (europe/worldwide), if I instead flash to official firmware from the SM-G960N (Korea) ones as you suggested, will that change the supported cellular bands? I live in Libya.

Coomer91 said:
thanks for the answers effry, I do have one more though so bare with me.
the currently installed firmware is SM-G960Fblahblahblah (europe/worldwide), if I instead flash to official firmware from the SM-G960N (Korea) ones as you suggested, will that change the supported cellular bands? I live in Libya.
Click to expand...
Click to collapse
Since you have now an "F" firmware, you could try first an SM-G960F ROM , then if you encounter issues i'd give a shot to the korean one.
For lybia the latest firmware is this:
https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960F/BTC/download/G960FXXU7CSJ1/296419/
My theory is that your phone is an SM-G960N, but someone flashed an "F" firmware on it.

effry said:
Since you have now an "F" firmware, you could try first an SM-G960F ROM , then if you encounter issues i'd give a shot to the korean one.
For lybia the latest firmware is this:
https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960F/BTC/download/G960FXXU7CSJ1/296419/
My theory is that your phone is an SM-G960N, but someone flashed an "F" firmware on it.
Click to expand...
Click to collapse
Just tried to flash the libyan (SM-G960F) firmware, it got stuck on system.img (odin said "secure check fail (bootloader)). anyways this what odin mode in my phone says
product code: SM-G960N
current binary: Custom (what does this mean?)
system status: Official (what does this mean in relation to "current binary: custom"?)
FAP lock: off
OEM lock: off
Secure Download: Enabled
Warranty Void: 1 (0x400)
what do we make if this? are there any other information you need?

Coomer91 said:
Just tried to flash the libyan (SM-G960F) firmware, it got stuck on system.img (odin said "secure check fail (bootloader)). anyways this what odin mode in my phone says
product code: SM-G960N
current binary: Custom (what does this mean?)
system status: Official (what does this mean in relation to "current binary: custom"?)
FAP lock: off
OEM lock: off
Secure Download: Enabled
Warranty Void: 1 (0x400)
what do we make if this? are there any other information you need?
Click to expand...
Click to collapse
You have to enable OEM unlock in developer options , then retry flashing

effry said:
You have to enable OEM unlock in developer options , then retry flashing
Click to expand...
Click to collapse
heh!! he made the same mistake i did and called it FAP lock!! LOCK DOWN ALL THE FAPPING!!!
also, i 100% agree with reflashing. Id even suggest trying it on a different computer. Install the system wide adb on the other computer, download Odin and get a fresh download of the firmware and reflash