Related
Just bought S6 G920T so i'm still new to all the bootloader security issues, i flashed TWRP yesterday and got stuck on bootloop after that. Bootloop was fixed after flashing Twisted v4 rom. I set up everything including fingerprint and when i restarted the phone it gave the error "Custom Binary blocked by FRP".
Currently i am trying to revive the phone, about to flash 6.0.1 PK5 firmware.
Now i have a few questions, please answer whichever you can:
- In case flashing 6.0.1 fails the next solution is to flash 7.0 firmware, is it possible to flash Twisted v4 (6.0.1) after that? Or i have to go with Nougat roms only?
- What should i know to avoid ever having another FRP lock again with a custom rom? Dont set up fingerprint? Or enable OEM unlock option is enough?
- Any way to permanently disable this Custom Binary lock security feature?
I want to use Twisted v4 with root and fingerprint if possible (dont need Samsung Pay). Sorry if this is a repost, i tried gathering whatever info i could on this issue but still confused on these questions. Thanks in advance! :highfive:
EDIT: Looks like this forum is dead, so i'll just answer my own questions from what i learned today with first hand experience for the next confused soul.
- Flashing 6.0.1 PK5 firmware fixed the FRP lock issue (if you were on newer firmware you will need to flash that one or higher)
- Enable Developer Options by clicking Build Number a few times, in Developer Options allow OEM unlock to avoid "Custom Binary FRP lock"
Now i am using Twisted v4 with root and fingerprint enabled, TWRP is installed and no issues till now.
If root/TWRP is what you're after, is the Tmobile version the friendliest S6 to get?
RunNgun42 said:
If root/TWRP is what you're after, is the Tmobile version the friendliest S6 to get?
Click to expand...
Click to collapse
Yes. The TMobile Galaxy S6 is the last Galaxy model with an unlocked bootloader.
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
killerxda said:
Just bought S6 G920T so i'm still new to all the bootloader security issues, i flashed TWRP yesterday and got stuck on bootloop after that. Bootloop was fixed after flashing Twisted v4 rom. I set up everything including fingerprint and when i restarted the phone it gave the error "Custom Binary blocked by FRP".
Currently i am trying to revive the phone, about to flash 6.0.1 PK5 firmware.
Now i have a few questions, please answer whichever you can:
- In case flashing 6.0.1 fails the next solution is to flash 7.0 firmware, is it possible to flash Twisted v4 (6.0.1) after that? Or i have to go with Nougat roms only?
- What should i know to avoid ever having another FRP lock again with a custom rom? Dont set up fingerprint? Or enable OEM unlock option is enough?
- Any way to permanently disable this Custom Binary lock security feature?
I want to use Twisted v4 with root and fingerprint if possible (dont need Samsung Pay). Sorry if this is a repost, i tried gathering whatever info i could on this issue but still confused on these questions. Thanks in advance! :highfive:
EDIT: Looks like this forum is dead, so i'll just answer my own questions from what i learned today with first hand experience for the next confused soul.
- Flashing 6.0.1 PK5 firmware fixed the FRP lock issue (if you were on newer firmware you will need to flash that one or higher)
- Enable Developer Options by clicking Build Number a few times, in Developer Options allow OEM unlock to avoid "Custom Binary FRP lock"
Now i am using Twisted v4 with root and fingerprint enabled, TWRP is installed and no issues till now.
Click to expand...
Click to collapse
Sorry I missed your post man. I am still rocking my S6 with Twisted Nougat so I could have helped ya out. I do not use the fingerprint option however.
cwhiatt said:
Sorry I missed your post man. I am still rocking my S6 with Twisted Nougat so I could have helped ya out. I do not use the fingerprint option however.
Click to expand...
Click to collapse
Its ok bro, experience is the best teacher
don’t mean to hijack, but
Saw this now after I posted and you’re saying it’s dead (which sucks, but oh well)
Which version were you on before flashing entirely?
Any chance you could lemme know what to google to grab the 6.01 fw? I’ll try that out I guess.
I’m having frp lock and can’t even flash anything it seems, but I’ll try anything.
killerxda said:
Just bought S6 G920T so i'm still new to all the bootloader security issues, i flashed TWRP yesterday and got stuck on bootloop after that. Bootloop was fixed after flashing Twisted v4 rom. I set up everything including fingerprint and when i restarted the phone it gave the error "Custom Binary blocked by FRP".
Currently i am trying to revive the phone, about to flash 6.0.1 PK5 firmware.
Now i have a few questions, please answer whichever you can:
- In case flashing 6.0.1 fails the next solution is to flash 7.0 firmware, is it possible to flash Twisted v4 (6.0.1) after that? Or i have to go with Nougat roms only?
- What should i know to avoid ever having another FRP lock again with a custom rom? Dont set up fingerprint? Or enable OEM unlock option is enough?
- Any way to permanently disable this Custom Binary lock security feature?
I want to use Twisted v4 with root and fingerprint if possible (dont need Samsung Pay). Sorry if this is a repost, i tried gathering whatever info i could on this issue but still confused on these questions. Thanks in advance! :highfive:
EDIT: Looks like this forum is dead, so i'll just answer my own questions from what i learned today with first hand experience for the next confused soul.
- Flashing 6.0.1 PK5 firmware fixed the FRP lock issue (if you were on newer firmware you will need to flash that one or higher)
- Enable Developer Options by clicking Build Number a few times, in Developer Options allow OEM unlock to avoid "Custom Binary FRP lock"
Now i am using Twisted v4 with root and fingerprint enabled, TWRP is installed and no issues till now.
Click to expand...
Click to collapse
p4cm4n88 said:
Saw this now after I posted and you’re saying it’s dead (which sucks, but oh well)
Which version were you on before flashing entirely?
Any chance you could lemme know what to google to grab the 6.01 fw? I’ll try that out I guess.
I’m having frp lock and can’t even flash anything it seems, but I’ll try anything.
Click to expand...
Click to collapse
You can download the PK5 Firmware here > https://www.sammobile.com/firmwares/galaxy-s6/SM-G920T/TMB/confirm/G920TUVU5EPK5/113173/
OR...you can try to use Samsung Kies or Samsung Smartswitch to restore your phone back to stock. You'll need the model and serial number which you can get by booting to Download mode and then pressing the home button. Once you get back up and running on stock firmware you can enable developer options then USB debugging and OEM unlock.
Once you have those taken care of you can root, install TWRP, Xposed, and flash Twisted Nougat.
hate to be annoying, but is there a better place to find this rather than a place that will take 12 hours to dl?
cwhiatt said:
You can download the PK5 Firmware here >
OR...you can try to use Samsung Kies or Samsung Smartswitch to restore your phone back to stock. You'll need the model and serial number which you can get by booting to Download mode and then pressing the home button. Once you get back up and running on stock firmware you can enable developer options then USB debugging and OEM unlock.
Once you have those taken care of you can root, install TWRP, Xposed, and flash Twisted Nougat.
Click to expand...
Click to collapse
p4cm4n88 said:
hate to be annoying, but is there a better place to find this rather than a place that will take 12 hours to dl?
Click to expand...
Click to collapse
Like I said u can try using Kies or Smartswitch. I have used Kies successfully on a handful of S6s without issue. Otherwise I could probably download it tomorrow at work and send you a link.
Sent from my [device_name] using XDA-Developers Legacy app
No worries. I’ll do it overnight. Thanks
Also Odin 3.10.6 started being able to flash where 3.12.? Failed.
I got the baseband you have in your sig I just installed. Still have FRP tho and was told to wait 72 hours.
Mean time my fiancé just bought an iPhone instead.
cwhiatt said:
Like I said u can try using Kies or Smartswitch. I have used Kies successfully on a handful of S6s without issue. Otherwise I could probably download it tomorrow at work and send you a link.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
p4cm4n88 said:
No worries. I’ll do it overnight. Thanks
Also Odin 3.10.6 started being able to flash where 3.12.? Failed.
I got the baseband you have in your sig I just installed. Still have FRP tho and was told to wait 72 hours.
Mean time my fiancé just bought an iPhone instead.
Click to expand...
Click to collapse
Been away from xda for a while so didnt see your post. Instead of sammobile you can usuallly find firmware on androidfilehost. If you were on 6.0.1 before then you should be able to flash this file:
https://androidfilehost.com/?fid=745425885120707260
if that doesnt work then 7.0 file should work (basically you need the same version that was flashed or updated version, older versions not allowed):
https://androidfilehost.com/?fid=961840155545571517
Good Morning,
I have a carrier unlocked Australian N950F Exynos Note 8 running 7.1.1 with OEM Unlock showing in developer settings (took a week or so). My phone has downloaded but not yet installed this OTA:
N950FXXU3CRC7/N950FOLN3CRC7/N950FXXU3CRC7 (1021.03MB)
I think it'll be Oreo but I haven't checked which exact version.
I have not installed TWRP or rooted this phone yet but I'd like to do so. I'd also like to move to Oreo before I proceed as my battery life could be better.
What is the best way to proceed? I've read through some long threads and ended up confused about exactly what's the best procedure.
Is some kind or decryption required at some point? Will I lose the data currently on my phone?
I haven't installed the OTA update yet.
Thank you.
CRC7 is Oreo, 8.0 which is currently the latest for Note8 (8.1 may be a long while out if we even get it officially).
The process for rooting Oreo is basically the same as Nougat, for Oreo just be sure you are using the updated TWRP that fixes the data mount issue.
If you root Nougat first, you won't be able to update OTA so you'll then need to install a custom rom to get Oreo.
You can update to Oreo via OTA first & your data will be intact but regardless if Oreo or Nougat, after installing TWRP you'll need to wipe data to remove encryption. So yes, you will loose data. You won't loose internal or external storage unless you choose to format them but it's a good idea to make a backup of them just in case.
As for data, you'll need to use smart switch, helium, etc if you want to back it up. I have no experience with backing up data without root so I'm not sure what methods work best.
It seemed to work. I restored all my contacts, apps etc in Oreo. When I went to restart the phone and enter TWRP to flash magisk I get a message about only official binaries are allowed. Now the phone won't even boot. I'm guessing I now need to re-flash official firmware with odin just to get my phone working? Another week for OEM unlock? I waited this long because I thought the problem was resolved
Unfortunately if you have the OEM lock issue, that will never go away. So yes, you have to flash official firmware to boot again. If you were on Oreo, you can try flashing Nougat to see if you might get lucky & get OEM unlock back.
Since you have the OEM lock issue, remember to always flash the RMM state fix even if you flash a custom rom that has the fix built in. Always flash RMM fix right after flashing a custom rom. If not flashing a custom rom, flash RMM fix before booting to system after you install TWRP.
Thanks for the reply.
Was I supposed to install Samsung AntiRoot Removal and RMM State Bypass as per this guide? Is this guide the correct method?
galaxynote8root.com/galaxy-note-8-root/how-to-root-galaxy-note-8-on-android-8-0-oreo/
I'm currently downloading Oreo 8.0 XSA (unbranded Australian rom) to reload my phone and wait another week.
I would like to use the XSA Samsung rom rather than a custom rom. Is OEM Unlock available in Oreo after a week?
Thank you
I use the method listed in any of the TWRP threads. I've never heard of Samsung Anti Root Removal. By the sound of it on the page it sounds like dm no verity. You need to flash that & RMM state fix. Flash the XSA firmware you want to use. Log into your Samsung account, don't reboot for 168hrs & OEM unlock should appear. Then follow a guide for installing TWRP.
Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you
dekalbcountyman said:
Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you
Click to expand...
Click to collapse
did you encrypt your device? when you reboot, do you see an animation of a pad lock?
bober10113 said:
did you encrypt your device? when you reboot, do you see an animation of a pad lock?
Click to expand...
Click to collapse
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
Are you using Snapdragon or Exynos?
mmjs14 said:
Are you using Snapdragon or Exynos?
Click to expand...
Click to collapse
Sir, I am using a
Galaxy Note 9
SM-N960F Internationals Unlocked
Alpine White
Exynos
Boot loader is TWRP and OEM Unlock is staying open permanently
I have all the hardware required, just need to overcome this software quirk so I can lock my phone when I’m not using it
dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
ive never seen this. what firmware are you on?
have you tried to download the very latest and completely wipe your phone? use samfirm tool 0.3.6 do dl the latest.
fill up all the slots with the md5 files u dled with samfirm and flash using odin( in csc slot use csc.md5 instead of home_csc.md5.)
go dl
magisk zip:
https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
and apk:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.2.0/MagiskManager-v7.2.0.apk
ketan oem fix +root
https://www.androidfilehost.com/?w=files&flid=281291
once back on latest stock firmware root again using twrp 3.2.x.x tar
flash it with odin but go to option and uncheck autoreboot
and flash twrp.tar in the AP slot.
once successful, manualy reboot phone to recovery( dont let it boot to homescreen! so hold vol up + Bixby +power
once in twrp swipe to get in recovery. go to wipe button and Format ( type yes) and go to reboot button and choose reboot to recovery
once back to recovery go again to wipe button and choose factory wipe.
once done flash dr ketan oem and root zip. ( within the aroma setup of that zip choose yes to both option for root and kernel)
once finished you can now flash the latest magisk.zip as dled earlier.
now reboot and setup your device. once done you can install magisk manger .apk that was dled earlier.
Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate
dekalbcountyman said:
Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate
Click to expand...
Click to collapse
actualy the root method that dr ketan created is just a way to bypass an issue that not all phones have(rmm state aka binaries error when booting.
but technically the method should be;
flash twrp, format, reboot again to recovery and flash official magisk .zip
you can also rely on rom developpers to flash their version instead of stock android via odin. this allows you to not always have to go through the twrp/root procedure each time and also rom devs include nice additional features.
anyways glad i could help.
Alirghty so i bought a used samsung note 8 duos. it says it on the back, in the software, in smart switch, heck even the AP and CSC files are infact for a SM-N950F
Here is where the problem is as far as I've figured out, I'll explain what the firmware files are on the device taken from dialing *#12580*369#:
BL:N950NKSU5DSK1
AP:N950FXXS7DSH1
CP:N950NKOU5DSH1
CSC:N950FOXM7DSG1
The phone runs fine honestly but its bugs me that there two different binaries mixed in my phone from what i can tell the BL and CP are from a Korean level 5 Binary (also can someone tell me why security levels matter now?) and the AP and CSC are from F model level 7 Binary
I cant flash anything stock cause its the only thing ive tried and it just wont let me. I am downloading a level 5 binary in *hopes* that it doesnt see an issue with the security levels between firmwares as i always get the fricken PIT error or secure download error orrrr the magic string invaild
All i need is a way to get my dualsims back up and running ive got two imeis on this phone which ive checked online and theyre working also id love it if i could just get all 4 files to be from the same firmware zip
FYI the only thing ive been able to flash is TWRP after which i got to installing no-verity and magisk, Ive been using twrp backups as a failsafe to revert back to the 'original' state my phone was in and thats the only thing working for me so far and i may or may not be a noob in flashing samsung devices
XtremeAwais said:
Alirghty so i bought a used samsung note 8 duos. it says it on the back, in the software, in smart switch, heck even the AP and CSC files are infact for a SM-N950F
Here is where the problem is as far as I've figured out, I'll explain what the firmware files are on the device taken from dialing *#12580*369#:
BL:N950NKSU5DSK1
AP:N950FXXS7DSH1
CP:N950NKOU5DSH1
CSC:N950FOXM7DSG1
The phone runs fine honestly but its bugs me that there two different binaries mixed in my phone from what i can tell the BL and CP are from a Korean level 5 Binary (also can someone tell me why security levels matter now?) and the AP and CSC are from F model level 7 Binary
I cant flash anything stock cause its the only thing ive tried and it just wont let me. I am downloading a level 5 binary in *hopes* that it doesnt see an issue with the security levels between firmwares as i always get the fricken PIT error or secure download error orrrr the magic string invaild
All i need is a way to get my dualsims back up and running ive got two imeis on this phone which ive checked online and theyre working also id love it if i could just get all 4 files to be from the same firmware zip
FYI the only thing ive been able to flash is TWRP after which i got to installing no-verity and magisk, Ive been using twrp backups as a failsafe to revert back to the 'original' state my phone was in and thats the only thing working for me so far and i may or may not be a noob in flashing samsung devices
Click to expand...
Click to collapse
The reason for that is because the phone has obviously been repaired using different hardware from different devices. It's never going to be able to flash normal firmware being that there's different hardware in it. If you want to upgrade that you'll need to use the different versions of firmware for each different hardware.. I'd just send it back if I bought it from somewhere like that.
Revert to Stock
I owns one Galaxy Note 8 SN950-F Indian version,
I have installed one custom ROM for my mobile last month and now i need to revert back to stock.
How can i do it ? Once i installed stock OS using Odin but Knox looks crashed and apps like secure folder not working !
Can i get it done through service center ? When i contacted them they said its impossible as you have rooted once.
nandu41 said:
I owns one Galaxy Note 8 SN950-F Indian version,
I have installed one custom ROM for my mobile last month and now i need to revert back to stock.
How can i do it ? Once i installed stock OS using Odin but Knox looks crashed and apps like secure folder not working !
Can i get it done through service center ? When i contacted them they said its impossible as you have rooted once.
Click to expand...
Click to collapse
Once Knox is tripped it takes a motherboard replacement to revert it.
If SF (Secure Folder) is that important to you, stay on a custom rom that has patched SF patched already.
Literally all TWRP/Rom threads warn you of this, always read the whole OP of any thread in the future.
Yeah. Thats what im doing now. Running on doctor ketans rom.
but im little worried now. Because haven't used any custom roms and worried about security issues.
Can we still go back to stock os ? With genuine updates?
nandu41 said:
Yeah. Thats what im doing now. Running on doctor ketans rom.
but im little worried now. Because haven't used any custom roms and worried about security issues.
Can we still go back to stock os ? With genuine updates?
Click to expand...
Click to collapse
Yes you can go back to stock and you will still receive OTA updates.
Great. How is this possible??
Where i can get the correct OS. ??
nandu41 said:
Great. How is this possible??
Where i can get the correct OS. ??
Click to expand...
Click to collapse
Just follow the steps in the thread below. At the bottom of post #2 you can download "samfirm" for you Pc, it will let you download the latest filmware at a decent speed. (once back on stock you should disable OEM lock so your bank app, Netflix etc will work)
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
stonedpsycho said:
Just follow the steps in the thread below. At the bottom of post #2 you can download "samfirm" for you Pc, it will let you download the latest filmware at a decent speed. (once back on stock you should disable OEM lock so your bank app, Netflix etc will work)
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
:good::good::good: Thank you
stonedpsycho said:
Just follow the steps in the thread below. At the bottom of post #2 you can download "samfirm" for you Pc, it will let you download the latest filmware at a decent speed. (once back on stock you should disable OEM lock so your bank app, Netflix etc will work)
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
Installed with it, Looks like genuine OS, But still secure folder crashes with some error !!!!
Dr Ketans ROM supports Secure folder , Do you have any other suggestions ?
nandu41 said:
Installed with it, Looks like genuine OS, But still secure folder crashes with some error !!!!
Dr Ketans ROM supports Secure folder , Do you have any other suggestions ?
Click to expand...
Click to collapse
Like I said to you above, once Knox is tripped SF won't work, if SF is that important to you stay on a custom rom that has patched SF. If you're worried about security updates use DeluxeRom which has last months security patch.
XtremeAwais said:
Alirghty so i bought a used samsung note 8 duos. it says it on the back, in the software, in smart switch, heck even the AP and CSC files are infact for a SM-N950F
Here is where the problem is as far as I've figured out, I'll explain what the firmware files are on the device taken from dialing *#12580*369#:
BL:N950NKSU5DSK1
AP:N950FXXS7DSH1
CP:N950NKOU5DSH1
CSC:N950FOXM7DSG1
The phone runs fine honestly but its bugs me that there two different binaries mixed in my phone from what i can tell the BL and CP are from a Korean level 5 Binary (also can someone tell me why security levels matter now?) and the AP and CSC are from F model level 7 Binary
I cant flash anything stock cause its the only thing ive tried and it just wont let me. I am downloading a level 5 binary in *hopes* that it doesnt see an issue with the security levels between firmwares as i always get the fricken PIT error or secure download error orrrr the magic string invaild
All i need is a way to get my dualsims back up and running ive got two imeis on this phone which ive checked online and theyre working also id love it if i could just get all 4 files to be from the same firmware zip
FYI the only thing ive been able to flash is TWRP after which i got to installing no-verity and magisk, Ive been using twrp backups as a failsafe to revert back to the 'original' state my phone was in and thats the only thing working for me so far and i may or may not be a noob in flashing samsung devices
Click to expand...
Click to collapse
I am having this same problem.....my phone got bricked so i was looking for my stock rom but the only stock rom that works with my Samsung note 8 is the korean version which supports one 1 sim but my device is dual sim
I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2
All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
I'd recommend around sammobile and samfw. These are the two sources I use the most
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((
My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).
Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?
You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata
DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse
WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell
schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.