Related
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
ZeroXO said:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
Click to expand...
Click to collapse
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.
Is the unknown (bat) firmware the one I need to flash to stock?
Sent from my OnePlus6T using XDA Labs
TheLogicalGamer said:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
Click to expand...
Click to collapse
Using odin 13.1.3 is recommended.
As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)
If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.
Must Have An Unlocked Bootloader To Do This!
Must Be On One UI 2.5 Firmware Or Updating Too One UI 2.5 Firmware to Use
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet and install decrypted csc files. No flashing of zips is required. There are 2 tar files too choose from one will add all US carrier functions to your phone and the other is for Non US carriers ​
Downloads SM-G9600
USERDATA_G960U_AIO_TWRP_RECOVERY_8_12_21.tar.md5 -Use on android 10 when updating. This is for US U model phones that are bootloader unlocked
USERDATA_G9600_US_AIO_TWRP_3_5_0_0_RECOVERY.tar.md5 -Use on android 10 when updating. This adds US calling features and US CSC files. Use this if using A US carrier
USERDATA_G9600_NON_US_AIO_TWRP_3_5_0_0_RECOVERY.tar.md5 -Use on android 10 when updating. This adds almost all latin and Non US csc files to rom. Use this if not using A US Carrier
Downloads SM-G9650
USERDATA_G965U_AIO_TWRP_RECOVERY_8_12_21.tar.md5 -Use on android 10 when updating. This is for US U model phones that are bootloader unlocked
USERDATA_G9650_US_AIO_TWRP_3_5_0_0_RECOVERY.tar.md5 -Use on android 10 when updating. This adds US calling features and US CSC files. Use this if using A US carrier
USERDATA_G9650_NON_US_AIO_TWRP_3_5_0_0_RECOVERY.tar.md5 -Use on android 10 when updating. This adds almost all latin and Non US csc files to rom. Use this if not using A US Carrier
Odin3_v3.14.1_3B_PatcheD.zip
Files For SM-N9600 Found Here
TWRP Recovery Provide by @klabit87
Install Instructions
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode
3. Use patched 3.14 odin and load files in USERDATA_***_AIO_TWRP_3_5_0_0_RECOVERY.tar.md5 in the USERSDATA slot of odin and flash firmware. If updated firmware for example from android 9 to 10 load full odin firmware in appropriate slots with above file in the USER DATA slot and flash
4. Phone will reboot to TWRP and automatically install stuff needed.
5. Phone Will reboot 2 times back to TWRP to remove encryption if data is encrypted and continue automatic install. If data is not encrypted and no wipe is needed phone will reboot once to TWRP and continue automatic install.
Features
@klabit87 Q kernel with Added powersave governor, conservative governor and ondemand governor support
All carrier functions should work like wifi calling, volte, Hd call and etc
No patches or mod zips are needed phone will already be rooted
Rmm is removed and vaultkeeper service disabled
Bluetooth is patched for pairing to survive reboots
Netflix Fix Included
Samsung Health working
Unencrypted Odm csc feature files for easy editing
Added cricket carrier support for working wifi/hd calling
Native Call Recording added
Caller Id and Spam protection added
Places tab added too dialer
Samsung Backup Account added to Verizon CSC
Stock Network Speed added to status bar
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Kernel Source https://github.com/klabit87/android_kernel_samsung_sdm845
TWRP Source https://github.com/klabit87/twrp_and...g_star2qltechn
Thanks To People That Make My Life Easier
@elliwigy
@klabit87
@me2151
@stang5litre
@Raymonf for modified odin
@afaneh92
@rayan-refoua for boot animation
@TheMadScientist
@kdrag0n for safetynet fix
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7
mine
Nice! Awesome job as always!
Sent from my Pixel 2 XL using Tapatalk
Keep up the good work! ??
Sorry for the noob questions.
If I am reading this correctly, it should work on my G9650 that is currently already rooted and running @stang5litre rom, correct?
And this would upgrade to android 10?
Can I roll back to Stang's rom or is this a one way street?
Also, do you have any screenshots of what this Rom looks like?
Thanks in advance.
I'm getting a phone encrypted message upon restarting from twrp, any ideas??
tigras54 said:
I'm getting a phone encrypted message upon restarting from twrp, any ideas??
Click to expand...
Click to collapse
Ignore it. You can access internal storage and mount data correct?
Edit: You are talking about the red warning error in Twrp correct?
KBuskill said:
Sorry for the noob questions.
If I am reading this correctly, it should work on my G9650 that is currently already rooted and running @stang5litre rom, correct?
And this would upgrade to android 10?
Can I roll back to Stang's rom or is this a one way street?
Also, do you have any screenshots of what this Rom looks like?
Thanks in advance.
Click to expand...
Click to collapse
Yes its for g9650 and yes you will be android 10 and you can only roll back if that rom is v6 bootloader
Thank you very much for your work sir
Just one question, does this work for the g9600 model? why I tried to install and I got an error
Hexioo said:
Thank you very much for your work sir
Just one question, does this work for the g9600 model? why I tried to install and I got an error
Click to expand...
Click to collapse
No it does not. I may make rom for sm-g9600 eventually
jrkruse said:
Ignore it. You can access internal storage and mount data correct?
Edit: You are talking about the red warning error in Twrp correct?
Click to expand...
Click to collapse
I'm sorry I didn't specify, it wasn't however in twrp, when I tried booting into system it said system is encrypted and I need to enter a password to get into my phone. I fixed that issue! I had to instead of deleting data and cache, I had to format data and enter yes to confirm formatting entire phone. I restarted it hung then restarted again, I was finally in, I then came into another error as my setup kept crashing when trying to restore from google account. I flashed that zip that you posted for samsung mods, it got passed that. I finally got into the system and passed the setup, the fingerprints etc pin anything locking the phone will not work... is that normal? as of now? Plus I can't get my samsung account to work at all, it keeps saying to sign-in again to continue using my account, sync is broken. I can't get any photos back etc as of now,. as eveything is on my samsung cloud and I really don't like my phone in-secure as I always have nosy friends. I'm pretty good at trouble shooting but these right now are my issues. Magisk is working and functioning properly, idk if it's a problem with magisk because my other device (Huawei Honor 8) has the same issue with Magisk and the password on lock-screen. My s6 Edge Plus has no issues with Magisk 20+ though and has lock screen functions etc. fingerprints.
Hexioo said:
Thank you very much for your work sir
Just one question, does this work for the g9600 model? why I tried to install and I got an error
Click to expand...
Click to collapse
No it does not. I may make rom for sm-g9600 eventually
jrkruse said:
No it does not. I may make rom for sm-g9600 eventually
Click to expand...
Click to collapse
wow that would be great, there are currently not many options for the g9600 model
tigras54 said:
I'm sorry I didn't specify, it wasn't however in twrp, when I tried booting into system it said system is encrypted and I need to enter a password to get into my phone. I fixed that issue! I had to instead of deleting data and cache, I had to format data and enter yes to confirm formatting entire phone. I restarted it hung then restarted again, I was finally in, I then came into another error as my setup kept crashing when trying to restore from google account. I flashed that zip that you posted for samsung mods, it got passed that. I finally got into the system and passed the setup, the fingerprints etc pin anything locking the phone will not work... is that normal? as of now? Plus I can't get my samsung account to work at all, it keeps saying to sign-in again to continue using my account, sync is broken. I can't get any photos back etc as of now,. as eveything is on my samsung cloud and I really don't like my phone in-secure as I always have nosy friends. I'm pretty good at trouble shooting but these right now are my issues. Magisk is working and functioning properly, idk if it's a problem with magisk because my other device (Huawei Honor 8) has the same issue with Magisk and the password on lock-screen. My s6 Edge Plus has no issues with Magisk 20+ though and has lock screen functions etc. fingerprints.
Click to expand...
Click to collapse
Im sorry for some reason the OP reverted back to an early state on my direction. I updated them too state that you should add any accounts or set any security until you are through setup. You may not want to restore data and start fresh on this as this is not a sm-g9650 rom anymore its a sm-g965u rom. Just by chance who is your carrier? Fingerprint and all lockscreen security works fine for me so maybe wipe data and go through setup again without connecting to wifi or adding any accounts or security
My carrier is at&t
tigras54 said:
My carrier is at&t
Click to expand...
Click to collapse
I added those extra instructions to the OP. Sorry they were not there Im not sure why they didnt save when I updated them yesterday. Like I said I would wipe data and go through setup again without adding anything, Then once through add your stuff
glad I could help
---------- Post added at 04:27 AM ---------- Previous post was at 04:24 AM ----------
as I have restored apps etc and everything I will have to suffer until update hopefully soon a fix can be found as restoring everything again will take a long timeee
tigras54 said:
glad I could help
---------- Post added at 04:27 AM ---------- Previous post was at 04:24 AM ----------
as I have restored apps etc and everything I will have to suffer until update hopefully soon a fix can be found as restoring everything again will take a long timeee
Click to expand...
Click to collapse
well if you wipe and got hrough the process fingerprint and lockscreen stuff will work
Just did all you said and kinda upset now as it still did not fix... same error
Hi everyone !
I follow this forum for many years, being quiet but reading and learning from everyone. With my two previous Samsung phones, I installed custom ROMs, so rooted ROMs, on which I was able to use some apps allowing me to enable or disable CSC features.
My Note 9 is the first phone I don't wanna root because with OneUI, I can do most of the things I did with root on other phones (especially enabling dark mode, editing themes etc...). But I would like to enable some CSC features such as native SIP call support.
I have to say that my phone is the SM-N960F and I'm using CSC XEF as I'm in France.
I had an idea 2 months ago where I could extract the CSC archive from stock rom, edit the features file in XEF folder, repack the archive and push it to the phone for update, but :
1 - is it possible to repack in the right format?
2 - is it safe for the phone (no bootloop, no brick, no factory reset) ?
3 - will I keep OTA without it to wipe my changes or will I have to do this edit each time there is an update ?
Thanks for your reading and I hope some of you will be able to answer me
Hi everyone, still no idea ?
I have changed CSC from SEE to THL because I wanted to enable call recording function.
Did it with SamKey software, not free but not expensive too, couple of bucks.
Good thig is this will wipe nothing from the phone and OTA will work normal after.
I done that 2 months ago and everything is ok, had 2 OTA-s.
www.samkey.org
You have instructions here:
Enabling Native Call Recorder through CSC | XDA Developers Forums (xda-developers.com)
I already thought about it but there's no CSC with all the features I would like to have, choosing another one than OXM (the one I am running on) would force me to make a choice between having one specific new feature and lose another one
Livier8 said:
Hi everyone !
I follow this forum for many years, being quiet but reading and learning from everyone. With my two previous Samsung phones, I installed custom ROMs, so rooted ROMs, on which I was able to use some apps allowing me to enable or disable CSC features.
My Note 9 is the first phone I don't wanna root because with OneUI, I can do most of the things I did with root on other phones (especially enabling dark mode, editing themes etc...). But I would like to enable some CSC features such as native SIP call support.
I have to say that my phone is the SM-N960F and I'm using CSC XEF as I'm in France.
I had an idea 2 months ago where I could extract the CSC archive from stock rom, edit the features file in XEF folder, repack the archive and push it to the phone for update, but :
1 - is it possible to repack in the right format?
2 - is it safe for the phone (no bootloop, no brick, no factory reset) ?
3 - will I keep OTA without it to wipe my changes or will I have to do this edit each time there is an update ?
Thanks for your reading and I hope some of you will be able to answer me
Click to expand...
Click to collapse
Did you find a way?
alessandro_xda said:
Did you find a way?
Click to expand...
Click to collapse
Hi, still no solution by now, and now the Note 9 is not my phone anymore I switched to the S22 Ultra
hello, I have had the same idea for some years, I have tried the rooms from the samsumg s6 edge and from note 9, but I decided to leave the root and custom roms because I lose other functions linked to knox.
I understand that the lines of code that activate the csc features exist because the functions are hidden in the samsung stock rom, however, the closest I have come to activating these functions is by changing the csc of my phone with room OXM but I have only managed to activate call recording and HIYA. I have the suspicion that samsung natively activates these functions in South Korea or in China (CHC) (not TGY) and perhaps acquiring a phone from these regions may have the cscs features
Hello,
I need help and guidance on some things regarding N960F/DS.
My phone was rooted with magisk on android pie, so when i flashed the android 10 Q rom via odin and everything was fine except i didn't have any network and my IMEI status was NG. While the IMEI number was ok for both sims. I knw that you have to patch certificates in order to fix the network. I didn't have the tools so i got it fixed from a shop.
Now i want to know a few things.
1) can i somehow update the firmware without having to go through all the root process and having to patch certificate ??
I found this video where this guy patched the AP file with magisk manager and just flashed the files via odin ??
will this method work with note 9 ?? and do i need to do any other extra steps ?? i also read about fireflash in the S7 forum, will that method work ??
2) if i backup this rom and incase i get a IMEI NG problem will i be able to just restore the rom ?? or will i have to patch the certificates again ??
3) is there any other workaround of patching certificate ?? are there patched modems available for note 9 ??? can i backup certificates ?? is there a permanent solution to this ??
4) which is the best tool to patch certificate ?? chimera ?? Z3X?? or any other ?? and do they support the latest android 10 security patch ??
Thanks
I'm facing Same problem n960f and set of questions.
snanahmd said:
Hello,
I need help and guidance on some things regarding N960F/DS.
My phone was rooted with magisk on android pie, so when i flashed the android 10 Q rom via odin and everything was fine except i didn't have any network and my IMEI status was NG. While the IMEI number was ok for both sims. I knw that you have to patch certificates in order to fix the network. I didn't have the tools so i got it fixed from a shop.
Now i want to know a few things.
1) can i somehow update the firmware without having to go through all the root process and having to patch certificate ??
I found this video where this guy patched the AP file with magisk manager and just flashed the files via odin ??
will this method work with note 9 ?? and do i need to do any other extra steps ?? i also read about fireflash in the S7 forum, will that method work ??
2) if i backup this rom and incase i get a IMEI NG problem will i be able to just restore the rom ?? or will i have to patch the certificates again ??
3) is there any other workaround of patching certificate ?? are there patched modems available for note 9 ??? can i backup certificates ?? is there a permanent solution to this ??
4) which is the best tool to patch certificate ?? chimera ?? Z3X?? or any other ?? and do they support the latest android 10 security patch ??
Thanks
Click to expand...
Click to collapse
Have you got any answer to those questions yet? I have same phone and same questions.
s
oqaab said:
Have you got any answer to those questions yet? I have same phone and same questions.
Click to expand...
Click to collapse
Same here!?
Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched​
Downloads
SM-G991U/U1/W- Model
USERDATA_AIO_G991_FORCE_WIPE_NO_BL_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
G991USQU4AUFD_BIT1_SAFE.7z
This are odin files and will safely update all image files too bit 4 and keep bit 1 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_G991_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
S21+ SM-G996U/U1
S21 Ultra SM-G998U/U1
TWRP Recovery Provide by @Mentalmuso
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G99*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G99*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G99*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G99*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
Xylvion for testing s21
dark11b for testing s21
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7
Hi @jrkruse I dont see anything in Post #2. Might you share "Info For Bootloader Unlocks Can Be Found In Post 2"
991U1 USA Snapdragon
I finished unlock with afaneh and then I flashed USERDATA_AIO_G991_FORCE_WIPE_NO_BL.tar.md5 but ended up with bootloop.
https://imgur.com/WG7uFma
I then went back to post to read. Was I supposed to flash both stockfirmware and the tar file? I only did the tar file in USERDATA slot.
EDIT: Nvm. The black download links download the S20 (981) tar file and that's what I ended up flashing. Fixed by flashing the orange links for the S21 (991).
So I was sent here from the unlocked samsung bootloader's group in telegram because someone's been helping me there for the last day and a half trying to get my Samsung Galaxy watch 3 to pair with my wearables app on my unlocked and rooted s21 ultra and we've had no luck so I guess my question is how does this work? and what do I need to do?
jmac052002 said:
So I was sent here from the unlocked samsung bootloader's group in telegram because someone's been helping me there for the last day and a half trying to get my Samsung Galaxy watch 3 to pair with my wearables app on my unlocked and rooted s21 ultra and we've had no luck so I guess my question is how does this work? and what do I need to do?
Click to expand...
Click to collapse
Were you successful pairing you galaxy watch? I was able to pair mine after receiving help from Ali. 3 files need to be modified. If you still need help I have the files and would be willing to share with you so you can see what needs to be edited.
Jnewell05 said:
Were you successful pairing you galaxy watch? I was able to pair mine after receiving help from Ali. 3 files need to be modified. If you still need help I have the files and would be willing to share with you so you can see what needs to be edited.
Click to expand...
Click to collapse
Man Ali helped me alot but still we aren't being able to connect yeah I would love the files...I'm willing to give anything a try at this point! Thanks for reaching out!
jmac052002 said:
Man Ali helped me alot but still we aren't being able to connect yeah I would love the files...I'm willing to give anything a try at this point! Thanks for reaching out!
Click to expand...
Click to collapse
There is a updated version of the galaxy wearable fix in the telegram chat. I am rooted with magisk so i used root explorer to navigate to vender/etc/vintf/ here are two files that need modifying called manifest_lahaina.xml and manifest_shima.xml. Following the guide from the telegram you can execute 3 a few commands in terminal. Or just replaced the files included in the zip and reset the permissions. Permissions need to be rw-r--r--.
Jnewell05 said:
There is a updated version of the galaxy wearable fix in the telegram chat. I am rooted with magisk so i used root explorer to navigate to vender/etc/vintf/ here are two files that need modifying called manifest_lahaina.xml and manifest_shima.xml. Following the guide from the telegram you can execute 3 a few commands in terminal. Or just replaced the files included in the zip and reset the permissions. Permissions need to be rw-r--r--.
Click to expand...
Click to collapse
Also shared by Ali was fix for smart view and shealth, it's not part of this flashable in OP but think gear fix should be at least discussed. You'll have to modify system/build.prop
Ali stated "For screen sharing and S health following need to be in build prop : ro.config.tima=0
ro.config.iccc_version=iccc_disabled
wlan.wfd.hdcp=disable"
I also edited ro.config.nox=v30 changed it from 30 to 00 so that secret mode works in the samsung browser. See screenshot. And again set permissions to rw-r--r--
Hope this helps!!
I don't suppose any of this watch trickery is in any way applicable to samsung pass?
Does not help samsung pass. I don't know exactly details but samsung pass looks at knox trip and will not work once tripped. Have looked around for a fix but have not had any luck.
Updated files in OP fixed sum bugs. Added new safetynet patch and I think wearable fix now works
Worked like a charm the 1st try. It feels good to be rooted on a Samsung device again. My previous Sammy with root was the s5. Thank you very much!
Are you going to update this to the June patch? I'm hoping to get the Heat issue fix which June addressed.
How do I check to see which bootloader version I have?
The link is incorrect in the OP and links to the SM-996U1. Does anyone have the updated link?
Can you or anyone confirm this works on already magisk rooted G9910?
I just finished setting up the phone and temporarily lost root when i renamed the Magisk app, had to reflash the patched IMG with HOME_CSC and thank god i didnt lose settings
My whole reason for TWRP is the backup/restore functions, so i never have to suffer this kind of heart attack again
I'm on OneUI 4.1 .. is that what "DONT MIX BIT 1" means? should i avoid?