Database Info

For those wanting Root you can finally do it on the latest vzn official firm

on the latest stock official firm from verizon which could be found anywhere. With the unlocked phones being released in the U.S you can finally root the latest official firmware version G935VVRS2APF2.
Using Argyrus Rooting Guide also credited to dajmanjt for your edit of his guide
referencing to dajmanjt Guide on Rooting get links from his post
- Folder named "SuperSU-v2.76-S7QC" contains the SuperSU and thing needed to root the phone
- ADB Setup EXE called "adb-setup-1.4.3.exe", needed to install ADB and the Drivers
- Special patched Odin that skips the SHA 225 called Odin PrinceComsy.exe (Mainly for AT&T) including an .ini file named "Odin3.ini"
- file named "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone that will allow rooting
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services. If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
1. Install ADB by running adb-setup-1.4.3.exe (select YES to all options, especially system wide ADB)
2. Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
3. Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR, then flash it
4. Once restarted put the phone into USB debugging mode, if it is not already enabled (need Developer options for this)
4b. To get developer mode, go to "About" then tap "build number" about 6 or 7 times
4c. Go back to settings and you should now see developer options, turn on USB debugging
5. Now back on your PC, double click on the file called "root.bat" (it should be in the main folder with ALL the other files, aka no subfolders)
6. Wait for the CMD to finish and then your phone should restart
7. Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
Tested and working on my S7 Edge running perfectly on G935VVZW2APF2 firmware and rooted with the full functionality of the phone.
Enjoy

Is this thread necessary considering it already appears?
Sent from my iPhone using Tapatalk

So it's the same exact current method.

So you basically just copied the current method from the older post and applied it to the PF2 firmware. My mind is blown.

Won't be impressed til I can root on MacBook ????????

Thread and info already exists here http://forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624 @kenshin6105 Please do not copy/paste someone else's work as per rule 12.

(Tutorial) Root SM-903VL By Downgrading to 4.4 (Simplified, No Converting Needed)

hello i have put together a bunch of information about getting root on the S5 (SM-S903VL) though i cannot take all the credit.
I simply pulled info from different threads into one to make things less confusing and more simplified. so be sure to thank @parrotgeek1 on how to convert and @mortj19 for providing the link to the "testing" firmware. The downside to this is you will be downgraded to 4.4 kitkat from 6.0 marshmallow. Also your phone might read it as SM-G900V instead of SM-903VL in "About Phone" This will enable people to root the S5 that some want so badly and to have a pretty stable system (im still checking everything over myself) so lets begin...
NOTE: I am not responsible for any damage or data loss that may occur. proceed at your own risk.
I have swapped the system.img and cache.img that was originally in this thread to the G900V for better compatibility and most importantly to allow WIFI TETHER
WARNING: YOU WILL BE ABLE TO USE WIFI TETHER BUT IN STRAIGHT TALKS POLICIES, IT STATES THAT TETHERING IS PROHIBITED AND IF CAUGHT, STRAIGHT TALK CAN TERMINATE YOUR ACCOUNT WITHOUT NOTICE OR WARNING. YOU'VE BEEN WARNED. TETHER AT YOUR OWN RISK.
Known Issues (So Far)
-SHealth crashing consistently (disable it to fix or remove after rooting)
-After reboot, Wifi password is forgotten and needs to be re-entered - since swapping over to G900V, im not sure if this is an issue anymore. need someone to confirm if it does or doesnt since im on a custom rom now and cant.
-mobile data does NOT work until the system and cache are transferred to the device
Fingerprint sensor- has something to do with incorrect test keys. i do not have enough understanding on how to patch this to get it working again. so sorry. if anyone is able to get it working, please post and ill update the thread with the correct changes.
LINKS UPDATED!
Things needed are:
A PC with phones drivers installed
Odin 3.12.3 - https://mega.nz/#F!Ugh2CaRa!YcYsAQy-OG6hW3PPNA9TuQ
System Img. built from G900V - https://mega.nz/#!EkonBKAR!Xp_CCqMKgijpEFA_h0id6yn9NttPwTgArlLTU82rKWs
Cache Img. built from G900V - https://mega.nz/#!glAHmJgS!L4gHDv6y8M4_feSz1cDHqWtsMoeO7wvAj9HwWOzxAVk
sdk-tools - move this folder to the root of your C:/ drive - https://mega.nz/#F!gswwxSiY!Qx2dm6GlfL5vLwD2oQaV7A
4.4 Test firmware - https://forum.xda-developers.com/galaxy-s5/general/downgrade-to-4-4-2-factory-test-t3530449
Towelroot Apk - towelroot.com
kingroot Apk - kingroot.net
external SDCard (make things easier)
NOTE: download everything on a PC to make instructions easier to follow
Step 0: Move system.img and cache.img to the ROOT of your internal storage of your phone and kingroot,towelroot to your SDcard
Step 1: Put phone in download mode by shutting the phone off then turning it back on by holding the volume key up + Home button + power button
Step 2: NOTE:THIS STEP WILL WIPE EVERYTHING ON YOUR PHONE SO BE SURE TO BACKUP! Run Odin.exe and click AP in the program and select the 4.4 test firmware and click start. let it finish and the phone boot into system
step 3: Install kingroot and run it and let it root the device. If it fails just try again (You get a network error if you try to use towelroot at this point.
step 4: open up command prompt on your PC and type the following:
CD C:/sdk-tools
adb shell
su (grant permissons on prompt on your phone)
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
(give it a minute or two to say its transferred)
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
(give a minute or two to say its tranferred)
reboot recovery (if it says an error like not found like mine did. just pull the battery out after disconnecting phone from your PC and manually reboot into recovery and it will load some stuff in the backround. after that it will reboot again but BEFORE it does be sure to hold the buttons again to get into recovery)
step 5: go down to factory reset and perform the reset to prevent a bootloop
step 6: reboot into system
step 7: install towelroot and tap "make it rain"
step 8: login to google play store and install supersu
step 9: open supersu and install the binary.
step 10: install root checker from the play store to verify root
its bit of a long process but if you want root bad enough on the SM-903VL like i did. i would say its well worth it. so far i have installed safestrap for the G900V (verizon) and it works.(if you install safestrap, dont forget it requires to have busybox installed) ive tested two roms so far. MOAR rom doesnt boot. only get a black screen. acherom works just fine though. (dont try to install twrp recovery or you will get the "take to verizon store error" and have to odin back to stock 903VL and start all over. i assume its from it having a locked bootloader. this is pretty much word for word on how to do this correctly thats why its so long but its quite simple. I have just took a few steps out so you dont have to worry or bother about doing any converting.
any problems give a post and see if we can resolve it to make this a more stable system
NOTE: IF YOU GET A RANDOM KERNEL PANIC DURING THE PROGRESS OF THIS, JUST DO OVER AGAIN.. SOMETIMES IT WILL GO UNDER PANIC ON THE FIRST TRY AND WILL NEED ODIN BACK TO STOCK.

@bjf189
To fix first 2 issues
In build.prop
ro.securestorage.support=false
Oh and while you're at it
ro.tether.denied=false
You should make a build.prop with those changes already applied and upload it for easier instructions

bjf189 said:
hello i have put together a bunch of information about getting root on the S5 (SM-S903VL) though i cannot take all the credit.
I simply pulled info from different threads into one to make things less confusing and more simplified. so be sure to thank @parrotgeek1 on how to convert and @mortj19 for providing the link to the "testing" firmware....
Click to expand...
Click to collapse
Awesome stuff! Thanks for the credit for the testing firmware, that took awhile to find.

parrotgeek1 said:
@bjf189
To fix first 2 issues
In build.prop
ro.securestorage.support=false
Oh and while you're at it
ro.tether.denied=false
You should make a build.prop with those changes already applied and upload it for easier instructions
Click to expand...
Click to collapse
i will update the build.prop and reupload in a matter of days. its been a busy week for me so i have very little time. one other issue i have found is i cant get the fingerprint sensor/scanner to work. any idea how to fix that? im not sure what files the sensor requires to use it.
right now im seeing if i can find a bypass to use to keep root but be back on marshmallow

bjf189 said:
i will update the build.prop and reupload in a matter of days. its been a busy week for me so i have very little time. one other issue i have found is i cant get the fingerprint sensor/scanner to work. any idea how to fix that? im not sure what files the sensor requires to use it.
right now im seeing if i can find a bypass to use to keep root but be back on marshmallow
Click to expand...
Click to collapse
1) unfortunately I don't think that's possible, mismatched rom fails security check
2) 100% impossible due to dm verity

parrotgeek1 said:
1) unfortunately I don't think that's possible, mismatched rom fails security check
2) 100% impossible due to dm verity
Click to expand...
Click to collapse
well your right that i cant bring it back to marshmallow. its even being a pain to extract correctly. so your saying that the fingerprint sensor cant be fixed?

I'm having trouble pulling apart the build prop. I have it extracted so I have it to edit and it has been corrected for tethering and that Wi-Fi error but I can't get it to inject back into the file or firmware of the downgrade. 7zip says error

================================================== =================
The Steps I used to go from SM-903VL MM 6.01 to ROOTED SM-S902L KK 4.4.2
================================================== =================
download the official stable version of ODIN 3.12.3 here:http://samsungodin.com/
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick ) from page 1
Download & downgrade to the factory test 4.4.2 SM-903vl Firmware from page 1 ( Using ODIN , use "AP" button for the .MD5 file )
root using KINGROOT PC version (windows) - INTERNET REQUIRED for KR to work! here:https://kingroot.net/thank-you-for-d...t-for-windows/
*** NOTE: May take a couple or few attempts to root phone. Exit & run KR again if no root.
(Also, try restoring 6.01 firmware, then try to downgrade again & root)
after ROOT successful, manually install stericson version of busybox: here:*https://www.apk4fun.com/apk/6139/
( copy apk to internal SD via PC mtp & install it from MY FILES )
download the s902L 4.4.2 TFN firmware here:https://samsung-firmware.org/model/SM-S902L/*( FREE, but have to register to DL )
(Windows use simg2imghttps://github.com/KinglyWayne/simg2img_win)
(Linux use a package manager to install simg2img)
Unzip the S902L KitKat Files to a folder, and then
use simg2img on cache.img.ext4 also ( *** temporarily rename it to system.ext4.img)
put the ext4 files in the same folder as simg2img.exe
open terminal or CMD prompt, then type:
simg2img system.img.ext4 system.img
simg2img cache.img.ext4 cache.img*
then copy the system.img & cache.img to your INTERNAL SD card
next run these commands from linux terminal ( or Windows CMD prompt ):
adb shell
su
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
**** Then exit the adb shell by typing exit (enter) 2 times to get back to command prompt, then
adb reboot recovery
let recovery do its thing, then when it reboots and is on the samsung boot screen
quickly do another
adb reboot recovery
then do a wipe data (Factory reset), then reboot
( I downloaded these APKS manually on PC, & copied to SD. WIFI will work on phone, but not DATA until you fix APN! )
install TR.APK ( Towelroot 3.0 ) and ROOT your phonehttps://towelroot.com/tr.apk
install stericson busybox-free ( found it here:https://www.apk4fun.com/apk/6139/*)
install PhoneInfo.apk and FIX the APN for LTE data to work ( menu, secret codes, lte stealth mode )
install XPOSED INSTALLER 2.6.1 ( KITKAT ) if you want xposed - google it
install SElinuxToggle.apk from XDA to be able to change SElinux to Permissive - google it
install SuperSu from playstore, upgrade binary & disable knox - Normal Mode ( as theres no custom recovery )
install ViperFX & ViperXHifi ( The BEST AUDIO MOD by far! Nothing can touch this! ) - google it
install a file manager with root capabilites: Rename the ContextProvider.apk in /system/priv-app/ folder to ContextProvider.apk.old
you should have ROOTED s902L normal KK 4.4.2 rom with XPOSED & Viper4Android Audio
Everything should work, EXCEPT for the WIFI TETHER & FINGERPRINT SCANNER
*** I DO NOT TAKE CREDIT FOR THIS... I PUT ALL THE PIECES TOGETHER FROM DIFFERENT SOURCES ***
But, did want to share the steps used in more detail to do this! Thanks XDA Members!!!!
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Fix APN with PhoneInfo.apk
http://apk.center/down_Phone-INFO-Samsung_apkcenter.html
Source of info was found here: http://www.reddit.com/r/galaxys5/comments/3uniq8/looking_for_lollipop_firmware_files_for_model/
Open Phone Info app Click on Secret Codes Click launch STEALTHMODE Click LTE APN SETTINGS Hit the + to add APN
Enter the follow information;
Name=Verizon Internet APN=TRACFONE.VZWENTP Proxy=(LEAVE BLANK) Port=(LEAVE BLANK) Username=(LEAVE BLANK) Password=(LEAVE BLANK) Server=(LEAVE BLANK) MMSC=(LEAVE BLANK) Multimedia message proxy=(LEAVE BLANK) Multimedia message port=(LEAVE BLANK) MCC=311 MNC=480 Authorization type=None Click menu in right hand corner and save Select new APN APN type=default,dun Bearer=Unspecified Mobile virtual network operator type=None
Click menu in right corner save. Select new APN reboot phone.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Questions:
(1) could we use the sm-g900v 4.4.2 fw instead of the sm-902l? https://samsung-firmware.org/model/SM-G900V/
build G900VVRU1ANE9 can be rooted with TR
(2) would lineage 14.x work via safestrap?
---------- Post added at 02:55 PM ---------- Previous post was at 02:46 PM ----------
bjf189 said:
I'm having trouble pulling apart the build prop. I have it extracted so I have it to edit and it has been corrected for tethering and that Wi-Fi error but I can't get it to inject back into the file or firmware of the downgrade. 7zip says error
Click to expand...
Click to collapse
i used es note editor as root. set the tether block to false. also did the sql thing to global database with the ",dun" thing.
i always get "hotspot not supported".
did you actislly get it to work???? how?
you could also from playstore download "root essentials". you can edit build.prop & csc data.
another tool in playstore, CSC FEATURES, not only allows editing of csc, but you can add missing features too. it has a huge categorized list built in!
please let me know if your mobile hotspot works and you can connect to it. i really need this!!!! thanks.
oh, if your trying to flash the csc via odin, and getting 7zip errors. assuming you are windows user (i am linux), try IZARC and use it to make your .tar file. http://izarc.org

fingerprint scanner.
*#0*#dialer code , sensors test , fingerprint version: null
build.prop shows:
samsung/kltetfnvzw/kltetfnvzw:4.4.2/KOT49H/S902LUDUAOD3:user/release-keys
maybe we need release-keys from 903vl factory test? can anyone help figure out the FP scanner issue?

DeepPurple72 said:
================================================== =================
The Steps I used to go from SM-903VL MM 6.01 to ROOTED SM-S902L KK 4.4.2
================================================== =================
download the official stable version of ODIN 3.12.3 here:http://samsungodin.com/
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick ) from page 1
Download & downgrade to the factory test 4.4.2 SM-903vl Firmware from page 1 ( Using ODIN , use "AP" button for the .MD5 file )
root using KINGROOT PC version (windows) - INTERNET REQUIRED for KR to work! here:https://kingroot.net/thank-you-for-d...t-for-windows/
*** NOTE: May take a couple or few attempts to root phone. Exit & run KR again if no root.
(Also, try restoring 6.01 firmware, then try to downgrade again & root)
after ROOT successful, manually install stericson version of busybox: here:*https://www.apk4fun.com/apk/6139/
( copy apk to internal SD via PC mtp & install it from MY FILES )
download the s902L 4.4.2 TFN firmware here:https://samsung-firmware.org/model/SM-S902L/*( FREE, but have to register to DL )
(Windows use simg2imghttps://github.com/KinglyWayne/simg2img_win)
(Linux use a package manager to install simg2img)
Unzip the S902L KitKat Files to a folder, and then
use simg2img on cache.img.ext4 also ( *** temporarily rename it to system.ext4.img)
put the ext4 files in the same folder as simg2img.exe
open terminal or CMD prompt, then type:
simg2img system.img.ext4 system.img
simg2img cache.img.ext4 cache.img*
then copy the system.img & cache.img to your INTERNAL SD card
next run these commands from linux terminal ( or Windows CMD prompt ):
adb shell
su
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
**** Then exit the adb shell by typing exit (enter) 2 times to get back to command prompt, then
adb reboot recovery
let recovery do its thing, then when it reboots and is on the samsung boot screen
quickly do another
adb reboot recovery
then do a wipe data (Factory reset), then reboot
( I downloaded these APKS manually on PC, & copied to SD. WIFI will work on phone, but not DATA until you fix APN! )
install TR.APK ( Towelroot 3.0 ) and ROOT your phonehttps://towelroot.com/tr.apk
install stericson busybox-free ( found it here:https://www.apk4fun.com/apk/6139/*)
install PhoneInfo.apk and FIX the APN for LTE data to work ( menu, secret codes, lte stealth mode )
install XPOSED INSTALLER 2.6.1 ( KITKAT ) if you want xposed - google it
install SElinuxToggle.apk from XDA to be able to change SElinux to Permissive - google it
install SuperSu from playstore, upgrade binary & disable knox - Normal Mode ( as theres no custom recovery )
install ViperFX & ViperXHifi ( The BEST AUDIO MOD by far! Nothing can touch this! ) - google it
install a file manager with root capabilites: Rename the ContextProvider.apk in /system/priv-app/ folder to ContextProvider.apk.old
you should have ROOTED s902L normal KK 4.4.2 rom with XPOSED & Viper4Android Audio
Everything should work, EXCEPT for the WIFI TETHER & FINGERPRINT SCANNER
*** I DO NOT TAKE CREDIT FOR THIS... I PUT ALL THE PIECES TOGETHER FROM DIFFERENT SOURCES ***
But, did want to share the steps used in more detail to do this! Thanks XDA Members!!!!
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Fix APN with PhoneInfo.apk
http://apk.center/down_Phone-INFO-Samsung_apkcenter.html
Source of info was found here: http://www.reddit.com/r/galaxys5/comments/3uniq8/looking_for_lollipop_firmware_files_for_model/
Open Phone Info app Click on Secret Codes Click launch STEALTHMODE Click LTE APN SETTINGS Hit the + to add APN
Enter the follow information;
Name=Verizon Internet APN=TRACFONE.VZWENTP Proxy=(LEAVE BLANK) Port=(LEAVE BLANK) Username=(LEAVE BLANK) Password=(LEAVE BLANK) Server=(LEAVE BLANK) MMSC=(LEAVE BLANK) Multimedia message proxy=(LEAVE BLANK) Multimedia message port=(LEAVE BLANK) MCC=311 MNC=480 Authorization type=None Click menu in right hand corner and save Select new APN APN type=default,dun Bearer=Unspecified Mobile virtual network operator type=None
Click menu in right corner save. Select new APN reboot phone.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Questions:
(1) could we use the sm-g900v 4.4.2 fw instead of the sm-902l? https://samsung-firmware.org/model/SM-G900V/
build G900VVRU1ANE9 can be rooted with TR
(2) would lineage 14.x work via safestrap?
---------- Post added at 02:55 PM ---------- Previous post was at 02:46 PM ----------
i used es note editor as root. set the tether block to false. also did the sql thing to global database with the ",dun" thing.
i always get "hotspot not supported".
did you actislly get it to work???? how?
you could also from playstore download "root essentials". you can edit build.prop & csc data.
another tool in playstore, CSC FEATURES, not only allows editing of csc, but you can add missing features too. it has a huge categorized list built in!
please let me know if your mobile hotspot works and you can connect to it. i really need this!!!! thanks.
oh, if your trying to flash the csc via odin, and getting 7zip errors. assuming you are windows user (i am linux), try IZARC and use it to make your .tar file. http://izarc.org
Click to expand...
Click to collapse
I kind of gave up on it being I've been real busy lately. If anyone can upload the new system img with the build prop corrections injected to it. I'll gladly upload it to the thread so it's all in one.
As for tethering and such. I just installed safestrap made for the G900V. Then installed acheron rom on slot one but that caused some errors. So I undid that and put it on stock slot after deleting the rom 1 slot. It got rid of the errors and enabled Wi-Fi tether. So that's an option to look into if you'd like. Still can't get finger print sensor to work though. I too think it might be something to do with the test keys but even on the test firmware I believe the finger print sensor didn't work. So I'm not sure if we can use the 6.0 marshmallow keys on 4.4 to fix the sensor or not. I have my doubts on it though

I am very busy also.
I think on the "downgrading to factory test 4.4.2" thread, someone posted the system.img & cache.img for 902l kk. Just use "root essentials" to edit the build.prop file and change the net.tether.block to false. Build.prop does not need to be injected. Its a quick edit using root, and can be edited directly.
As for the G900v kk 4.4.2, i will try and DL it, and make the system/cache img files.
will let you know when they are ready - but someone else will need to test them!
It took so long to get the 902L KK ver setup and all, and its working very good with root / xposed and all. But i am thinking the g900v kk should be more compatible to the 903vl than 902L, given that fcc id says 903vl is a g900v.

900
DeepPurple72 said:
I am very busy also.
I think on the "downgrading to factory test 4.4.2" thread, someone posted the system.img & cache.img for 902l kk. Just use "root essentials" to edit the build.prop file and change the net.tether.block to false. Build.prop does not need to be injected. Its a quick edit using root, and can be edited directly.
As for the G900v kk 4.4.2, i will try and DL it, and make the system/cache img files.
will let you know when they are ready - but someone else will need to test them!
It took so long to get the 902L KK ver setup and all, and its working very good with root / xposed and all. But i am thinking the g900v kk should be more compatible to the 903vl than 902L, given that fcc id says 903vl is a g900v.
Click to expand...
Click to collapse
i still cant get the fingerprint scanner to work even when i pull keys over from the factory test. i did however find a way to be able to get wifi tethering on stock after doing the system and cache switch. its simple. just use the G900V system.img and cache.img files in the G900V firmware and youll have wifi tether.
dont use the G900V firmware on the 903VL using odin. you will get a fail at aboot and with the aboot removed, it fails at the pit file. so thats out the window but you can still merge the system and cache over using your method to have tether though

Running G900V (Verizon) KitKat 4.4.4 STOCK ROM on SM-903VL !!!
Download G900V 4.4.4 Stock Rom HERE: https://www.androidfilehost.com/?fid=23991606952607146
Follow SAME directions as the SM-S902 4.4.2, only use the system/cache IMGs from this ROM instead!
( Yes, TowelRoot Works on this ROM! )
Debloat using a "System App Remover" app from playstore to delete the Verizon crap that you dont need/want.
Working for me on SMART-TALK (Verizon Carrier). Mobile Hotspot Works! (I'm using it now to post this)
I have already used the "PHONEINFO.APK" to do the LTE STEALTH MODE to add the APN for STRAIGHT TALK from previously using the 902L 4.4.2 rom.
I noticed that it does not seem to work on the G900V 4.4.4 - I'd suggest that while you have the SM-903VL FACTORY TEST flashed, trying the PHONEINFO LTE STEALTH MODE in that ROM if you have NO MOBILE DATA.
I also extracted the modem.bin file from the original SM-903VL MM 6.01 ROM's "AP" archive ( after extracting the MD5 files ), created a "tar" of just the modem.bin, and flashed the modem.bin.tar using ODIN AP mode to update the modem (baseband) back to MM 6.01 PH3 , for optimum performance as LTE seemed to be slower using the baseband that the FACTORY TEST flashed. I did not test PHONEINFO in the Factory Test rom - If it does not work and you have no mobile data, then you would have to install the 902L KK 4.4.2 first, root it with TR, then install PHONEINFO to be able to use the LTE STEALTH MODE in order to ADD the proper APN ( tracfone ) for STRAIGHT-TALK 4G/LTE mobile data to work. Then you can simply "dd" the system/cache img's from the G900V KK 4.4.4, reboot, let recovery do its thing and then when it reboots itself, go into recovery again and do the wipe data thing. The APN will not be affected. ENJOY!
FIngerPrint Scanner DOES NOT WORK ( maybe due to being ROOTed / ContextProvider errors - disabled that package )
*** I Believe the FIngerPrint Scanner will not work if the BOOT.IMG ( Kernel ) mismatches the SYSTEM image version, based on alot of googling. Since with a locked bootloader ( Toshiba Emmc ) we cannot flash the G900V boot image as ODIN fails ( due to bootloader locked ).
Also, I am using the modem from original SM-903VL MM 6.01
Performance is EXCELLENT! Running VERY FAST!
Xposed, ViperFX & ViperXifi, Lucky Patcher,etc ALL working. Phone/LTE/MOBILE HOTSPOT too!
Using Nova Launcher for Desktop ( love the 3D cube effects! )
I'm very HAPPY now that this SM-903VL has ROOT, and converted to G900V KitKAt 4.4.4
ITS SO EVIL HOW COMPANIES ARE LOCKING DOWN BOOTLOADERS / HINDERING ROOT!
If this where a PC, and they said you can ONLY install Windows 10 & You CANNOT be an ADMIN, but just a LIMITED USER, either their would be LAWSUITS or END-USERS say "FU" and NOT BUY the product.
Why should smart phones be any different from a PC in that respect?
Removed ALL Verizon apps EXCEPT VZ-NAVIGATOR ( which appears to work using STRAIGHT-TALK )
Also DISABLED/REMOVED the KNOX crap & SECURITY UPDATER too.
This can be done using SYSTEM APP REMOVER/UNINSTALLER, LUCKY PATCHER, etc.
Also using FDROID ( FOSS Software, kinda like the PlayStore app ), I use a nifty app called "autostarts"
to disable alot of apps from starting up at/after boot to save ram and battery.
Also, KNOX WARRANTY bit is still GOOD, doing all this stuff did NOT trip the KNOX WARRANTY!
THANK YOU SO MUCH XDA MEMBERS!!!! Your Posting of information has been extremely helpful!
---------- Post added at 02:37 PM ---------- Previous post was at 01:40 PM ----------
Getting XPOSED SECURITY ALERT CODE 2 errors with some Games/Apps ?
Oh, if you are ROOTED + XPOSED and play games, some games ( like NetMarble games ) detect XPOSED , pop up an error, and wont allow you to play them.
See my post here on how to defeat this ( without uninstalling xposed and without any reboot! )
https://forum.xda-developers.com/xposed/xposed-security-alert-code-2-netmarble-t3400258

Hello, I followed the instructions from the first post which booted, but i had an overlay on my main screen with yellow letters that would only go away if a menu or app was open. i eventually got a modem error of some sort on boot after the dd commands. so i found a zip with four files, AP BL, CP, CSC. This got me back to 6.0.1 and working but back to square one. and it must've updated the recovery part too because now the text colors are different and it has an extra option or two. when i tried to start over again, it failed in odin then i got a blue screen wanting me to connect the phone to quick connect app or something like that. eventually got that worked out and back running again, but any ideas on how i can go about trying this again? also this last post i've been reading, if i'm understanding correctly, i should be able to follow the same directions from the first post, but using the dd commands for the cache and system from the 4.4.4 download in the last post? also the CP file from the stock 903 6.0.1 zip folder i have is the modem file. if i want to use that modem file with 4.4.4 to possibly avoid the boot screen with the modem error do i load it in the AP or CP line in odin?
Sorry, i've rooted a tablet recently which was way less steps, and it's been a couple of years since i've rooted a phone so i'm rusty and still fairly noobish to this lol

GilFPV said:
Hello, I followed the instructions from the first post which booted, but i had an overlay on my main screen with yellow letters that would only go away if a menu or app was open. i eventually got a modem error of some sort on boot after the dd commands. so i found a zip with four files, AP BL, CP, CSC. This got me back to 6.0.1 and working but back to square one. and it must've updated the recovery part too because now the text colors are different and it has an extra option or two. when i tried to start over again, it failed in odin then i got a blue screen wanting me to connect the phone to quick connect app or something like that. eventually got that worked out and back running again, but any ideas on how i can go about trying this again? also this last post i've been reading, if i'm understanding correctly, i should be able to follow the same directions from the first post, but using the dd commands for the cache and system from the 4.4.4 download in the last post? also the CP file from the stock 903 6.0.1 zip folder i have is the modem file. if i want to use that modem file with 4.4.4 to possibly avoid the boot screen with the modem error do i load it in the AP or CP line in odin?
Sorry, i've rooted a tablet recently which was way less steps, and it's been a couple of years since i've rooted a phone so i'm rusty and still fairly noobish to this lol
Click to expand...
Click to collapse
Can you provide your Android version and model number and your baseband version under settings and about device? I will be updating this thread later today with the new fixes in place for those who want WiFi tether fixed. However I Still can't get fingerprint sensor to work correctly.

bjf189 said:
Can you provide your Android version and model number and your baseband version under settings and about device? I will be updating this thread later today with the new fixes in place for those who want WiFi tether fixed. However I Still can't get fingerprint sensor to work correctly.
Click to expand...
Click to collapse
Thank you!! Being able to have wifi tethering would be amazing! Currently using foxfi and pdanet to connect through usb and I get random connection drops.
Version 6.0.1
Model SM-S903VL (Straight talk)
Baseband S903VLUDU5AQA1

GilFPV said:
Hello, I followed the instructions from the first post which booted, but i had an overlay on my main screen with yellow letters that would only go away if a menu or app was open. i eventually got a modem error of some sort on boot after the dd commands. so i found a zip with four files, AP BL, CP, CSC. This got me back to 6.0.1 and working but back to square one. and it must've updated the recovery part too because now the text colors are different and it has an extra option or two. when i tried to start over again, it failed in odin then i got a blue screen wanting me to connect the phone to quick connect app or something like that. eventually got that worked out and back running again, but any ideas on how i can go about trying this again? also this last post i've been reading, if i'm understanding correctly, i should be able to follow the same directions from the first post, but using the dd commands for the cache and system from the 4.4.4 download in the last post? also the CP file from the stock 903 6.0.1 zip folder i have is the modem file. if i want to use that modem file with 4.4.4 to possibly avoid the boot screen with the modem error do i load it in the AP or CP line in odin?
Sorry, i've rooted a tablet recently which was way less steps, and it's been a couple of years since i've rooted a phone so i'm rusty and still fairly noobish to this lol
Click to expand...
Click to collapse
GilFPV said:
Thank you!! Being able to have wifi tethering would be amazing! Currently using foxfi and pdanet to connect through usb and I get random connection drops.
Version 6.0.1
Model SM-S903VL (Straight talk)
Baseband S903VLUDU5AQA1
Click to expand...
Click to collapse
The links have been updated and swapped to the G900V instead of the 902L for better compatibility and enable of WiFi tether. Just follow the guide and you'll have a rooted tetherable device.
As for your situation, your baseband I don't recognize. Where exactly did you pull that basrband from? When you go back to stock 6.0. You should have an ending of PH3 as your baseband. Then after using Odin it'll change to PH1.
Try starting over. Be sure the stock firmware you flash back to stock with has an ending of PH3. If you have trouble finding it. I'll upload the firmware here. After your back to stock. Just follow the guide word for word. Also the yellow wording on your home screen is the testing firmware that you flash that shows you downgraded from 6.0 to 4.4. After you see that yellow letters you are on 4.4. After that you go to the command prompt like in the guide and type in the commands on your pc to push the system and cache images to your phone and it will push out all that testing stuff. When using command prompt and type a command. Be sure to be patient and be sure that it says on your computer screen that it says "transferred in xx.xxx seconds" this means it got pushed to your phone successfully. If you pull the cord or cancel out before that reads on both the system and cache pushing. It won't be fully done and could end up stuck at start up or nothing changes which then you'd need to start all over. So he Patient. Hope this helps

bjf189 said:
The links have been updated and swapped to the G900V instead of the 902L for better compatibility and enable of WiFi tether. Just follow the guide and you'll have a rooted tetherable device.
As for your situation, your baseband I don't recognize. Where exactly did you pull that basrband from? When you go back to stock 6.0. You should have an ending of PH3 as your baseband. Then after using Odin it'll change to PH1.
Try starting over. Be sure the stock firmware you flash back to stock with has an ending of PH3. If you have trouble finding it. I'll upload the firmware here. After your back to stock. Just follow the guide word for word. Also the yellow wording on your home screen is the testing firmware that you flash that shows you downgraded from 6.0 to 4.4. After you see that yellow letters you are on 4.4. After that you go to the command prompt like in the guide and type in the commands on your pc to push the system and cache images to your phone and it will push out all that testing stuff. When using command prompt and type a command. Be sure to be patient and be sure that it says on your computer screen that it says "transferred in xx.xxx seconds" this means it got pushed to your phone successfully. If you pull the cord or cancel out before that reads on both the system and cache pushing. It won't be fully done and could end up stuck at start up or nothing changes which then you'd need to start all over. So he Patient. Hope this helps
Click to expand...
Click to collapse
QA1 was an update.

charliepop said:
QA1 was an update.
Click to expand...
Click to collapse
Well I've always had updates frozen and have been on a custom rom pretty much the whole time I had the s5. Does that updated version root with king root? I doubt it does and probably wasn't a good idea to update if you wanted root.
So new plan. Download the PH3 firmware and try using Odin to downgrade back the PH3 instead of what you have now. If it fails, I fear that Verizon/straight talk might have blocked downgrading. Be sure to let me know your result

I can't remember where i found the "back to stock" folder at, but it included these files which i loaded in odin but it did update once the phone was back up and running and i've yet to be able to get odin to flash anything since.
AP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
BL_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
CP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
CSC_TFN_S903VLTFN4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
also I didn't realize straight talk could shut my service off if they found out i am tethering. not sure if anything is different from the wifi hotspot than pdanet/foxfi which is what i've been using for the past couple of years. it's my only source of internet.

[Guide] How to modify Stock ROM

Hello!
Today I show you How to modify your stock ROM.
In this guide I won't use PC or other software because I want to make this guide easy for all.
Important notes:
For this guide I'll use Samsung Galaxy J3 2016, but similar principles works on other devices.
What you need:
TWRP Recovery for your device.
Root Explorer
Rooted Android Device
And APKs(See later what I think)
Step 1:Activating OEM unlock
Don't skip this step because it's the most important.
Go to Settings and tap About Phone.
Tap 7 times on Build Number and activate Developer Settings.
Enter in Developer Settings and search for OEM UNLOCK, ignore warning and activate them.
If you don't have OEM unclock don't worry you can skip this step.
Step 2: Flashing TWRP Recovery via Odin(Samsung Phones only)
If you don't own Samsung device(or device which can be rooted via KingoRoot) you can skip this step because this step is important for rooting phone.
YOUR WARRANTY IS NOW VOID
Download TWRP recovery for your device and flashable .zip file of SuperSu v2.XX(determine which version is best for your phone).
Run Odin, when Odin starts go to Options tab and de-check Factory Reset Time and Auto Reboot,
then return to main section. And click on AP button and locate your twrp recovery .tar file and than press open. Now turn of your phone and enter in Download Mode hold Power Button + Volume Down Button + Home Button and connect to PC and click on start. When green message PASS apear in Odin you successfully flash recovery.
To restart phone hold power and volume buttons for some seconds or simply remove and return battery
Step 3: Rooting phone
Enter in Recovery Mode(for Samsung device hold power+volume up+home). Swipe slider to allow modification on system partition. Tap on install and find zip file from SuperSU flashable zip and swipe slider to install zip. Wait to installation complete and reboot phone (your phone can reboot some times to complete.
Installing Root Explorer and exploring system/app and system/app-priv
Install Root Explorer and grant Root access.
Now we explore system partition, but before we start in TWRP Recovery make a backup of System partition.
Enter in system/app directory and search for bloatware and other unuseful apps, but be careful what you delete!
Now download apks from apk mirror(clean apks) and place in system/app and when you finished with placing apk files reset phone to Factory Settings.
Tips:
If you have older Android version( <5.0 Lollipop)
download and install XPosed Framework and MonsterUI from Google Play to have Lollipop Notification Bar.
If you have Samsung device with Android Lollipop 5.1.1 or newer go to system/priv-app(or app-priv) and find SecSetupWizard folder delete them and Factory Reset your phone and Voila Setup Wizard is now AOSP.
For Samsung TouchWiz Lollipop ROMs or newer you can download Material Status bar to get AOSP like experience.
If you running Samsung TW Lollipop ROM and want to have AOSP Phone and Contacts app go to system/app-priv(or priv-app) search for SecContacts_L folder and delete them, insert Google Dialer apk(downloaded from apk mirror looks for MINAPI(I USE MINAPI21) and Google Contacts apk and Factory Reset Phone. Now you free from Samsung Phone and Contacts app.
Customizing Stock ROM is so funny and you can make a new ROM(not new but different ).
If I help you Hit thanks button :victory:
And if you have suggestion write in post(s).

Any update on the video ?

Mr.Reticent said:
Any update on the video ?
Click to expand...
Click to collapse
You need to wait to I upload ROM now I'm testing Lineage OS by @djeman
Take a screenshot to I'm not lie

Uploading but it can take a long time...

ROM IS NOW AVAILABLE.
SEARCH ON XDA: J3 RELOADED(ONLY FOR FN MODELS)
-=-=-
mod edit - thread closed as per OP request

Japanese S7 Edge SCV33/SC-02H Magisk root and other tweaks!

This thread is for Japanese s7 edge scv33 that’s being booted up with SC-02H firmware after carrier unlocking.
This guide covers/ will help you
• Install Latest available Twrp recovery (Caution: will Trip Knox!)
• Magisk Root
• Remove Japanese carrier bloatwares.
• Make the default device language to English.
• Install latest available updates via default or, will add additional useful Samsung apps (will update the device stock apps like SMS, Touch wiz launcher, AOD, Contacts, etc to latest available.
• Various tweaks like sms delivery options turned on by default, always on display turned on by default etc-etc.
Overall, this guide is to help your Japanese S7 Edge scv33/SC-02H to look more like a standard international model.
So let’s begin.
Step 1:
All required files can be downloaded from here
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Caution. Backup all of your personal data. This process will need you to factory reset or will erase all of your data including your personal photographs, apps, videos etc.
You will also require to have a fresh piece of sd card (16 gb or more recommended) to store the twrp nandroid backup if anything goes wrong.
So, First, you will need to remove the modifications that were made to your device stock boot image. If you have flashed the modified kernel or have rooted using super-su, then, you will need to undo all the changes. You can flash the stock boot image file only but I would recommend you to flash the whole latest firmware that you can find easily over UPDATO Firmware website to start better all over again.
Here is the link to the latest SC-02H android 7.0 firmware:
http://updato.com/firmware-archive-select-model?record=AD3D69507E2D11E7963AFA163EE8F90B
Download and extract it. You will find 5 files. You can ignore the HOME……. file. Flash the 4 firmware file using latest Odin.
After flashing, let it boot up. Finish the setup wizard and turn off the device.
Step 2:
Flash the TWRP that you downloaded from here. Download Link is same as above.
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Twrp Bug: Device will reboot to twrp recovery if you choose to power down the phone from recovery option. You will have to choose “Reboot System” from twrp menu to solve this.
After installing, boot into twrp recovery. Go to Wipe and at the bottom right, you will have option to format data. Perform a Format data process. Then, make a TWRP backup to your sd card.
I repeat. Make a backup. This will help u a lot if anything goes wrong
Step 3:
Time to install magisk.
Extract root.zip file and there you’ll see magisk.zip
Flash this magisk installer file from twrp and reboot the device.
Install the latest magisk manager app apk.
Now your device is rooted with the latest magisk available.
Step 4:
Time to remove the bloatwares.
You will need ES file manager and System app remover from playstore.
Grant super-user access to both apps. Navigate to device/system/preloadFactoryResetOnly using es file manager and delete all the contents inside that folder.
Download the apps.zip file from here
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Extract it to your pc. Copy all the extracted apps including their folder to your device and paste it inside the same path i.e, device/system/preloadFactoryResetOnly folder.
Important: You will need to change the copied each app file permission to RW-R-R.
You do-not need to change the folder’s permission. But you will need to change the each apk’s permission one by one. Long press on the apk and then go to properties. Tick mark on (read-write, read, read).
But there will still remain some Japanese DoCoMo bloatwares. You will not be able to remove it by simply using system app remover.
So, use the system app remover app to track down the bloatware’s location by long pressing and delete it by using es file manager. Remember, only delete the bloatwares that are found in device/system/priv-app and device/system/app folders.
Caution:
You do-not need to super trim down your system in hopes for getting more internal space or whatsoever by deleting the bloatwares that you don’t know. Just delete the DoCoMo apps that you can see in the app drawers.
So be aware.
Factory reset after the above step.
Step 5:
Now comes the last part:
CSC Tweaks:
Download the 3 modified csc files from above link. Copy and replace them to path device/system/csc
Change the copied file permission to (rw-r-r).
To change the default device language and set the sms delivery option on by default, copy the Customer.xml file to your pc and edit it by using Notepad++.
Find the line as shown as in the picture below and modify as in it. Save it and replace it back to where it was from which will be device/system/csc and change its file permission again to rw-r-r.
Now turn off your device and boot into TWRP recovery. Perform a factory reset and reboot.
You will have latest apps with all the custom changes including your default language changed to English.
No need to install magisk manager apk as it is already there in the apps.zip folder.
Done!
Credit goes to all the rightful owners.
Special thanks to Mr. Buddha Tuladhar again for the phone.

Android 8.0 rom..and root/ twrp for scv33/sc-02h
Stock rom is in the link given
then flash
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
Boot to twrp and install:
1: no-verity-opt-encrypt-6.0.zip
2: Magisk-vXX.X.zip
Download link for all files
https://www.mediafire.com/folder/kn5cg1rolfjas/

Well done sir! thank you very much.
It would be wonderful if you can upload an odin flashable all in one file.
Appreciate your time and effort very much!

01. Flash 2017.03.07_SC02HOMU1BQC4 with Odin (upload by tienquynh93)
02. Flash 2017.04.07_1BQC4_Gobal_ManhIT.zip with Odin (upload & rebuild by ManhIT)
03. Flash 2017.03.17_TWRP_3.1.0 with Odin (AP) (Rebuild by ManhIT)
3.1 Reboot to TWRP Flash:
3.2 MaGisk to root (topjohnwu)
3.3 xPosed SDK 24 (Android 7.0) (rovo89)
This rom support multilanguage with defaulft vietnamese.
Lasest firmware: 2017.12.12_SC02HOMU1BQL3

Confused.
DariasLuc said:
01. Flash 2017.03.07_SC02HOMU1BQC4 with Odin (upload by tienquynh93)
02. Flash 2017.04.07_1BQC4_Gobal_ManhIT.zip with Odin (upload & rebuild by ManhIT)
03. Flash 2017.03.17_TWRP_3.1.0 with Odin (AP) (Rebuild by ManhIT)
3.1 Reboot to TWRP Flash:
3.2 MaGisk to root (topjohnwu)
3.3 xPosed SDK 24 (Android 7.0) (rovo89)
This rom support multilanguage with defaulft vietnamese.
Lasest firmware: 2017.12.12_SC02HOMU1BQL3
Click to expand...
Click to collapse
Is it necessary to flash 2017.03.07_SC02HOMU1BQC4 and 2017.04.07_1BQC4_Gobal_ManhIT.zip ? Or can i just simply flash the latest firmware 2017.12.12_SC02HOMU1BQL3 and root my phone?

Thank you, great job on compiling all this! It took quite a bit of study, but I understand now. Thanks again.

This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)

Hi
audioqueso said:
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Click to expand...
Click to collapse
Hi, what Twrp Work in Android 8.0 you can Shared whith me?

3.1.1, 3.2.1 and 3.2.3
They all worked. I had originally started working with 3.1.1 and 3.2.1. However, I tried the latest 3.2.3 because I couldn't get NFC to work. I did it just to give it a try.
But all three versions that I listed had no problem installing.
Are you having trouble installing TWRP?

Yes, recovery is not remplace
Will you have a link and instructions for Android 8?

How to install TWRP on Galaxy S7 Edge (SC-02H)
TWRP Installation:
1) Download and installed Odin 3.12.5 (or the latest)
2) Turn off phone. Pressed and hold Volume Down+Home+Power at the same time to get to Download Mode. Once you see the Download Mode page, let go of the buttons. Press Volume Up to accept. (To cancel, press Volume Down )
3) Open Odin and click on AP. Load the TWRP file from your computer.
4) On the second tab of Odin, uncheck "Auto-reboot" (you need to have auto reboot disabled in order to successfully install TWRP). Press 'Start'.
5) Once the Odin status changes to a green "Pass", the installation is complete.
At this point, your phone will still be in Download Mode screen. For this step only, you will need to do two steps back to back. First, press and hold Vol.Down+Home+Power in order to get the phone out of the Download Mode screen.
As soon as the screen changes, press Volume UP+Home+Power.
You will see TWRP load.
That's it. You have successfully loaded TWRP.
From here on out, you will need to press Vol. Up+Home+Power in order to boot into TWRP. If you reflash your phone back to stock firmware using Odin, you will lose TWRP and will need to repeat these steps in order to install TWRP again.

audioqueso said:
TWRP Installation:
1) Download and installed Odin 3.12.5 (or the latest)
2) Turn off phone. Pressed and hold Volume Down+Home+Power at the same time to get to Download Mode. Once you see the Download Mode page, let go of the buttons. Press Volume Up to accept. (To cancel, press Volume Down )
3) Open Odin and click on AP. Load the TWRP file from your computer.
4) On the second tab of Odin, uncheck "Auto-reboot" (you need to have auto reboot disabled in order to successfully install TWRP). Press 'Start'.
5) Once the Odin status changes to a green "Pass", the installation is complete.
At this point, your phone will still be in Download Mode screen. For this step only, you will need to do two steps back to back. First, press and hold Vol.Down+Home+Power in order to get the phone out of the Download Mode screen.
As soon as the screen changes, press Volume UP+Home+Power.
You will see TWRP load.
That's it. You have successfully loaded TWRP.
From here on out, you will need to press Vol. Up+Home+Power in order to boot into TWRP. If you reflash your phone back to stock firmware using Odin, you will lose TWRP and will need to repeat these steps in order to install TWRP again.
Click to expand...
Click to collapse
Could you provide a link to the latest version of twrp?

Joslem said:
Could you provide a link to the latest version of twrp?
Click to expand...
Click to collapse
http://bfy.tw/KPwS

For Root SC02HOMU1CRH5
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
no-verity-opt-encrypt-6.0.zip
Magisk-vXX.X.zip
From: https://itok01.com/2018/09/23/root-sc-02h/

Global Rom for SCV33/SH-02H 8.0
https://drive.google.com/uc?id=1MiYK-VSYLRH_9T43sYbfgfvvKqqwRJjO&export=download
Go to Recovery and run "graphic test" > "Format Data" > ReBoot.
Install Magisk to root:
https://forum.xda-developers.com/showpost.php?p=77942910&postcount=14

DariasLuc said:
For Root SC02HOMU1CRH5
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
no-verity-opt-encrypt-6.0.zip
Magisk-vXX.X.zip
Click to expand...
Click to collapse
it works, thank you very much!!

S7 Edge Docomo sc-02h lost imei after factory reset
Sorry for being off topic, but please cam someone help me out in the regard that my S7 Edge Docomo sc-02h lost imei after just the factory reset. Any recommendation what i can do to get it back as my sim signals are now gone as well that means i cant make any calls or msg whatsoever.
Thanks in advance

usmann93 said:
Sorry for being off topic, but please cam someone help me out in the regard that my S7 Edge Docomo sc-02h lost imei after just the factory reset. Any recommendation what i can do to get it back as my sim signals are now gone as well that means i cant make any calls or msg whatsoever.
Thanks in advance
Click to expand...
Click to collapse
you just need working 3G sim card to fix your imei... after put 3g sim card to your phone and reboot imei will appear and you can use your normal sim again!

everyonesweird said:
This thread is for Japanese s7 edge scv33 that’s being booted up with SC-02H firmware after carrier unlocking.
I need help in order to compile all of these tweaks into an Odin flashable file so that users can simply flash it and make the changes.I would also like to add App-lock feature and international Samsung keyboard with secondary symbol in but can’t seem to make it work. So, if you are interested or have tried, please let me know.....
Click to expand...
Click to collapse
Very thank, im removed almost bloat of AU. But, what happen if i dont have CSC folder? and how to add Vietnamese laguage to SCV33 (AU) stock rom?

audioqueso said:
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Click to expand...
Click to collapse
I am also struggling about this. I think the problem only concerns TWRP or Root. However I think the problem is TWRP, because when I flash stock rom, nfc ok. Next, i flash TWRP (not root yet), nfc has been disabled now. So i think TWRP causes this problem. However, if i reflash stock recovery, everything remains unchanged, NFC is still turned off. so it is very contradictory.
Now I think of a test, after installing all (root), backing up all android. Then flash again with stock rom, check NFC. Finally, restore the backup. The goal is to completely remove the TWRP from the process but still root the device. I hope it will work. Will try if i have the time

[Guide]How to root Samsung Galaxy C9 pro (SM-C9000)

Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste
Code:
.\adb devices
to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type
Code:
.\adb push AP_C9000ZHU1CSC1_CL14667562_QB22709761_REV00_user_low_ship_MULTI_CERT_meta.tar.md5 /sdcard/
.(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type
Code:
.\adb pull /sdcard/download/magisk_patched.tar
This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.

Lojcs said:
Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type .(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.
Click to expand...
Click to collapse
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?

khankk42 said:
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?
Click to expand...
Click to collapse
Yes, I did root my SM-C9000 using this method, and it is working nicely. Obviously I lost access to Secure Folder and Samsung Pay. You should be able to install the Play Store version of Samsung Health. Maximum Power Saving froze the phone the first two times I enabled it, but it's working fine now. One unexpected caveat is that mobile hotspot started to turn itself off if mobile data is enabled even though my carrier has no restrictions on using hotspot. You can't share your data connection using Bluetooth or usb cable neither. You can still use the hotspot for creating a local network. Other than those, I didn't experience any problems after rooting. While I was rooting, I did the mistake of using MTP to transfer the image and as a result my phone bootlooped for half a day but if you follow the instructions, that won't be a problem.
Of course, I don't guarantee anything and don't take responsibility, but there is no reason anything should go wrong.

My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?

otocu said:
My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?
Click to expand...
Click to collapse
Sorry for responding late. Yes, that is the exact model that I have and rooted using the method in the post. If you feel confident, you can follow trough it and root your phone. You can grab the required firmware from Sammobile. Keep in mind that after rooting some features might stop working (like hotspot and knox-related features). Good luck!

I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!

cherrio128 said:
I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!
Click to expand...
Click to collapse
Sorry for the late response. Searching that on the internet, it seems you might be using an old version of Odin. Please make sure you're using 3.13.1 and try again