Database Users

[Q] CMW success, SU fail :(

Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.

jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used

leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.

jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.

leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager

actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.

No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card

scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice

jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!

[SOLVED] Coming Over From GS3 (d2att)

tomorrow i will be receiving my Galaxy S4 in the mail, and basically i just want to make sure i will be rooting this phone with the most recent and preferred method.
i found this guide from 2 different sticky threads "[HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2" and "Frequently Asked Questions"
http://forum.xda-developers.com/showthread.php?t=2297900
but i started to see thing different than what i'm used to on the GS3:
(1) "This will not work on Build Number I337UCUAMF3"
is this comparable to the bootloader on the GS3? kinda like how there's a different guide to root a GS3 on the MJB bootloader.
(1b) what version will come out of the box?
should i root it before even putting my SIM card in it so it doesn't have a chance to auto-update?
(2) CASUAL
it sounds like this is an all-in-one, do-it-all Windows application? so i won't need the use of Odin to flash any files?
(3) what's the preferred custom recovery?
i've been using CWM for so many years now, it's just my go-to custom recovery.
SOLVED, see my last post.

mrhomiec said:
tomorrow i will be receiving my Galaxy S4 in the mail, and basically i just want to make sure i will be rooting this phone with the most recent and preferred method.
i found this guide from 2 different sticky threads "[HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2" and "Frequently Asked Questions"
http://forum.xda-developers.com/showthread.php?t=2297900
but i started to see thing different than what i'm used to on the GS3:
(1) "This will not work on Build Number I337UCUAMF3"
is this comparable to the bootloader on the GS3? kinda like how there's a different guide to root a GS3 on the MJB bootloader.
(1b) what version will come out of the box?
should i root it before even putting my SIM card in it so it doesn't have a chance to auto-update?
(2) CASUAL
it sounds like this is an all-in-one, do-it-all Windows application? so i won't need the use of Odin to flash any files?
(3) what's the preferred custom recovery?
i've been using CWM for so many years now, it's just my go-to custom recovery.
Click to expand...
Click to collapse
Chances are you'll get an S4 with a newer firmware. This means you won't be able to use TWRP or CWM, and you can't run AOSP ROMs. You can still root and flash other Touchwiz ROMs.
1) Yes, that's exactly what it is in fact. Bootloaders MF3 and above do not support the only exploit we have to install AOSP ROMs.
1b) Like i said, probably a newer one. Check on the outside of the box and it will have a label somewhere about the software version. If it's not MDB or MDL then you can't use the exploit to get an AOSP ROM.
2) Yes, it is an AIO Windows app, but it won't work unless you get one on MDL or MDB again.
3) If you get the newer firmware, Safestrap is the only recovery, and Touchwiz ROMs are all that's compatible
If you want a better explanation of anything, PM me and I'll be glad to respond as soon as I finish the essay i should be typing at the moment.

so in short, MDB/MDL = awesome.
i really hope i get one of these then. i always flash CM on whatever phone i use.
if i do receive a phone that's MDB/MDL, i should NOT insert my SIM card, and NOT connect to wifi then? that way i can root first?

mrhomiec said:
so in short, MDB/MDL = awesome.
i really hope i get one of these then. i always flash CM on whatever phone i use.
if i do receive a phone that's MDB/MDL, i should NOT insert my SIM card, and NOT connect to wifi then? that way i can root first?
Click to expand...
Click to collapse
Exactly, do not let it connect. Just use CASUAL and then either use your root to disable the OTA updater or go straight to a ROM. Then just remember that if you ever have issues and need to flash stock firmware only flash the same and never a newer one.

aw man. just got the phone in, and it's already been updated.
came in on 4.4.2, I337UCUFNB1
found these threads:
http://forum.xda-developers.com/showthread.php?p=52167774
http://forum.xda-developers.com/showthread.php?t=2663545 (edit, upon more searching, this method seems the most mentioned/preferred)
and i'm wondering if i should even "root" this phone anymore. i feel like if/when a real root method comes out, i can root it then?
i guess the benefit of rooting now, would be to freeze/uninstall Samsung apps. also, would it be any easier to real root after sorta rooting?
edit, some more searching around, rooting right now (and with Safestrap Recovery installed) has a whole bunch of scenarios to be aware of. this is kinda overwhelming coming from the GS3 and Nexus phones/tablets.
edit, what are ROM slots? this sounds like dual-boots to me.
and also, since my phone came with NB1, what is the proper terminology for this situation? because i'm reading references like "NB1 users who took the OTA" and "NB1 users who started out there".
another edit! so i think i'm going to just root, and stop there, is that possible? or do i have to go one step further and install Safestrap Recovery?
i tried to follow the guide above (2nd link), and in Odin i got a FAIL message when i loaded the *.pit file to the PIT slot, and the *.md5 file to the AP slot.

mrhomiec said:
aw man. just got the phone in, and it's already been updated.
came in on 4.4.2, I337UCUFNB1
found these threads:
http://forum.xda-developers.com/showthread.php?p=52167774
http://forum.xda-developers.com/showthread.php?t=2663545 (edit, upon more searching, this method seems the most mentioned/preferred)
and i'm wondering if i should even "root" this phone anymore. i feel like if/when a real root method comes out, i can root it then?
i guess the benefit of rooting now, would be to freeze/uninstall Samsung apps. also, would it be any easier to real root after sorta rooting?
edit, some more searching around, rooting right now (and with Safestrap Recovery installed) has a whole bunch of scenarios to be aware of. this is kinda overwhelming coming from the GS3 and Nexus phones/tablets.
edit, what are ROM slots? this sounds like dual-boots to me.
and also, since my phone came with NB1, what is the proper terminology for this situation? because i'm reading references like "NB1 users who took the OTA" and "NB1 users who started out there".
another edit! so i think i'm going to just root, and stop there, is that possible? or do i have to go one step further and install Safestrap Recovery?
i tried to follow the guide above (2nd link), and in Odin i got a FAIL message when i loaded the *.pit file to the PIT slot, and the *.md5 file to the AP slot.
Click to expand...
Click to collapse
To root, you'll need to downgrade to mk2 with Odin. See the second post in this
http://forum.xda-developers.com/showthread.php?p=50667360
Then root using saferoot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
To root, you'll need to downgrade to mk2 with Odin. See the second post in this
http://forum.xda-developers.com/showthread.php?p=50667360
Then root using saferoot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.

mrhomiec said:
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
Click to expand...
Click to collapse
Sorry man,I have you the wrong link. Use the all in one tar file from here http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my Nexus 5 using XDA Free mobile app

mrhomiec said:
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
Click to expand...
Click to collapse
The way most people follow on that thread is
1. Flash full NB1 post #2
2. Downgrade to MK2 post # 1
3. Root with safe root
4. Fix wife
5. Install safe strap
6 flash Tw rom of your preference.
7. Flash kernel if needed
8. Flash deadly venom magic tool.
9. Flash super su update.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

netomel said:
6 flash Tw rom of your preference.
7. Flash kernel if needed
8. Flash deadly venom magic tool.
9. Flash super su update.
Click to expand...
Click to collapse
flashing DVMT is optional. any modifications to the kernel will void his warranty (Knox 0x1). i'd advise looking into PurifieD or any 'stock' variant rom that does not require a custom kernel to be flashed, at least until your year of warranty goes by. Any post saying 'flashing period will void your warranty' is incorrect. On PurifieD with knox 0x0.

Rhymey said:
flashing DVMT is optional. any modifications to the kernel will void his warranty (Knox 0x1). i'd advise looking into PurifieD or any 'stock' variant rom that does not require a custom kernel to be flashed, at least until your year of warranty goes by. Any post saying 'flashing period will void your warranty' is incorrect. On PurifieD with knox 0x0.
Click to expand...
Click to collapse
We can't flash custom kernels on kit kat stock anyway.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
netomel said:
We can't flash custom kernels on kit kat stock anyway. I flashed deadly venom and knox still intouched.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

i am totally lost right now. i finally got this guide to work:
http://forum.xda-developers.com/showthread.php?t=2663545
(i was being dumb, and i forgot to put the phone into Download Mode for Odin)
now, i'm having a problem with the last step...
1. Download all three files above
2. Open ODIN3v3.09
3. Load both Pit and AP together to corerct slot ( Pit >>PIT SLOT.....AP>>PDA SLOT ) and hit start.....
5. When is done....reboot to stock recovery and choose Full Wipe/Factory Reset.
6. Re-Root using Saferoot Method
7. Re-install Safestrap-v3.71
8. Try restoring your back up from safestrap recovery....CONFIRMED WORK...
9. Special Thanks to @Michael3214 @rebel1699 @Maribou @dolph8886 @Surge1223 @jeboo for his bypasslkm exploit and others that help to get WiFi Fixed....
Click to expand...
Click to collapse
Flash in Safe Strap then reboot open universal init.d toggle on then press nb1wififix then press the play icon on the top right grant su. After that you'll have wifi on boot.
https://mega.co.nz/#!dct3ALRT!e81l_V...LaYu_yKvCYeHhg
Click to expand...
Click to collapse
Code:
adb push bypasslkm /data/local/tmp
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm
i cannot get wifi to work on the phone, and also, LTE/data is nowhere to be seen as well, and i'm hoping if i get the wifi fixed, it'll fix the data part too. i tried to flash the bypasslkm.zip via Safestrap Recovery, and it said it was successfully flashed, but still no wifi.
OR, i'm not sure if i did this all backwards. i received the phone today, and instead of putting my SIM card in right away, i booted up the phone, didn't connect to wifi, and attempted this whole rooting process.
then, i can't apply the update.zip for some reason with these instructions...
1. U need Samsung USB driver install to your PC ......Install SAMSUNG KIES and plug your phone, it will install latest driver for your phone....
2. Make sure u unable USB debugging mode on ur phone.....go to menu>settings>more> it should be on top of about device
( Developer options ) but if u dont have it go to about device and click build number 5 time....so that will unable developer options and CHECK USB DEBUGGING.
3. Make sure u have latest ADB ( Android Debugging Bridge ) version 1.0.31.... ANDROID SDK
4. IF you like to update to NB1 coming from MK2 ....Reboot to recovery>>>Apply Update From ADB....( MAKE SURE U DOWNLOAD update.zip AND PLACE IT INSIDE YOUR SD CARD)
5. Go to your PC >>> ADB folder >>> Shift+Right Click >>> Open Command Window Here
Click to expand...
Click to collapse
Code:
adb devices
adb sideload update.zip
i get this error...
* cannot read 'update.zip' *

mrhomiec said:
i am totally lost right now. i finally got this guide to work:
http://forum.xda-developers.com/showthread.php?t=2663545
(i was being dumb, and i forgot to put the phone into Download Mode for Odin)
Click to expand...
Click to collapse
Hi there! If you have safestrap installed and you still have root on whatever you're currently on, please update to 3.72 (if you haven't already) found here (click), and flash the stock rooted NC1 100% rom via Safestrap over your stock slot found here. This [should] fix your issues 100%. If not, scroll down to where it has the NC1 modem and flash that too.

Rhymey said:
Hi there! If you have safestrap installed and you still have root on whatever you're currently on, please update to 3.72 (if you haven't already) found here (click), and flash the stock rooted NC1 100% rom via Safestrap over your stock slot found here. This [should] fix your issues 100%. If not, scroll down to where it has the NC1 modem and flash that too.
Click to expand...
Click to collapse
i am on Safestrap Recovery 3.72, and i'm downloading that 100% ROM right now.
so i don't need to worry about the "update.zip" or the "bypasslkm.zip" files anymore?
just flash this ROM via Safestrap Recovery and i'm good to go?
back to my original post then, so i'm used to using CWM as a custom recovery, do i follow the usual steps with Safestrap?
* wipe data/factory reset
* wipe cache
* wipe dalvik cache
* flash ROM
* reboot

mrhomiec said:
i am on Safestrap Recovery 3.72, and i'm downloading that 100% ROM right now.
so i don't need to worry about the "update.zip" or the "bypasslkm.zip" files anymore?
just flash this ROM via Safestrap Recovery and i'm good to go?
back to my original post then, so i'm used to using CWM as a custom recovery, do i follow the usual steps with Safestrap?
* wipe data/factory reset
* wipe cache
* wipe dalvik cache
* flash ROM
* reboot
Click to expand...
Click to collapse
Yup, you got it. Go into advanced wipe on Safestrap and tick all of those. I never bothered with either of those zips. The only thing you might need to do is reflash SuperSU, but I never had an issue using the stock rom, just custom ones. SuperSU DL here.

Rhymey said:
Yup, you got it. Go into advanced wipe on Safestrap and tick all of those. I never bothered with either of those zips. The only thing you might need to do is reflash SuperSU, but I never had an issue using the stock rom, just custom ones. SuperSU DL here.
Click to expand...
Click to collapse
i found a link somewhere (and i forgot where no with how many tabs i had open originally), for a version of "UPDATE-SuperSU-v1.93.zip", but i downloaded the v1.89 from your link anyways (just in case).
the 100% ROM is still downloading, and i noticed something, you said to flash the NC1 modem if i continued to have problems, but i didn't see a mention of that in the link you provided. there's a kernel link if that's what you meant.

mrhomiec said:
i found a link somewhere (and i forgot where no with how many tabs i had open originally), for a version of "UPDATE-SuperSU-v1.93.zip", but i downloaded the v1.89 from your link anyways (just in case).
the 100% ROM is still downloading, and i noticed something, you said to flash the NC1 modem if i continued to have problems, but i didn't see a mention of that in the link you provided. there's a kernel link if that's what you meant.
Click to expand...
Click to collapse
Oh, guh. You're gonna need that kernel too. It's samsung signed so no voiding there. Modem here, just in case.
wipe everything except ext sd > flash rom > download mode, flash kernel in AP slot > boot, see if wifi works. If not, go flash the modem.

Rhymey said:
Oh, guh. You're gonna need that kernel too. It's samsung signed so no voiding there. Modem here, just in case.
wipe everything except ext sd > flash rom > download mode, flash kernel in AP slot > boot, see if wifi works. If not, go flash the modem.
Click to expand...
Click to collapse
looks like i'm good to go! thank you! :highfive:
i am on 4.4.2, baseband NC1, build NC1, LTE works, wifi works.
only took me 6 hours. :victory:

mrhomiec said:
looks like i'm good to go! thank you! :highfive:
i am on 4.4.2, baseband NC1, build NC1, LTE works, wifi works.
only took me 6 hours. :victory:
Click to expand...
Click to collapse
good to hear! if you have any issues with root just reflash SuperSU in safestrap. you can also jump around on TouchWiz roms now if you want to, but don't let any of them touch your kernel. And if you do, you'll need to flash an AT&T wifi module found here to get wifi working, and a build.prop to get LTE working found here. Have fun!

i think i'ma stay on this 100% ROM. i don't want to screw anything up. everything about rooting this phone is wayyyy out of my comfort zone. all the years of rooting i've done up until now was pretty much the same steps on different devices.
with that, i figure my last post should summarize this adventure.
basically, if you're in the same situation as me, getting a brand new Galaxy S4, automatically updated to 4.4.2 (NB1), here is what i went through. please see the original threads for all the download links.
NB1►DOWNGRADE★UPDATE◄MK2 ★ NB1 FULL ODIN ★ Apr.24.2014 said:
http://forum.xda-developers.com/showthread.php?t=2663545
1. Download all three files above
2. Open ODIN3v3.09
2b. put phone into Download Mode (from a shut down state, hold the Volume Down + Home Button + Power Button to start up)
3. Load both Pit and AP together to corerct slot ( Pit >>PIT SLOT.....AP>>PDA SLOT ) and hit start.....
4. (i don't know where step 4 is)
5. When is done....reboot to stock recovery and choose Full Wipe/Factory Reset.
5b. phone may freeze at the ATT screen, i left it alone for a good few minutes. then i took the chance to power down via holding Power Button, then putting the phone into stock recovery (hold the Volume Up + Home Button + Power Button).
6. Re-Root using Saferoot Method (not really re-rooting since this is a new phone, see below)
7. Re-install Safestrap-v3.71 (and not really re-installing either, also see below)
8. Try restoring your back up from safestrap recovery....CONFIRMED WORK...
8b. i skipped step 8.
9. Special Thanks to @Michael3214 @rebel1699 @Maribou @dolph8886 @Surge1223 @jeboo for his bypasslkm exploit and others that help to get WiFi Fixed....
9b. i skipped step 9 too.
10. download custom ROM, a kernel, and follow directions here:
http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
10b. and if needed, download modem here:
http://forum.xda-developers.com/showpost.php?p=52167761&postcount=2
11. and DONE, you should be on 4.4.2 again, but this time on NC1.
Click to expand...
Click to collapse
ROOT Saferoot: Root for VRUEMJ7 said:
http://forum.xda-developers.com/showthread.php?t=2565758
Step 1 - setting up the USB drivers
Before you try using this rooting program, you'll need to have the USB drivers installed for your phone.
The easiest way to do this is to install Samsung Kies (Kies 3, fyi). If Kies sees your phone, you're OK for the drivers.
If you don't have the drivers working, the root installer will hang at "waiting for device..."
Step 2 - Enable USB Debugging
The second thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled.
In Developer Options, make sure "USB Debugging" is checkmarked.
Step 3 - Enable USB ADB Access
Make sure that your computer is allowed to use USB debugging on your phone. To do this, unplug your phone (from the phone end, not the computer end) and unlock it. Then, plug in the USB cable back into the phone.
If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK.
If you don't see that popup, it's OK, you should be OK to proceed.
That's it for the phone.
Step 4 - Unzip the saferoot.zip
Then you need to unpack the attached ZIP file somewhere onto your PC.
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 5 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed.
If SuperSU asks you to update the su binary, choose the "Normal" method.
If SuperSU asks you about disabling Knox, allow it.
This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about.
While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone.
You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
Click to expand...
Click to collapse
RECOVERY LOCKED Safestrap Recovery v3.71/v3.72 2014-04-02 KK Beta said:
http://forum.xda-developers.com/showthread.php?t=2448925
1. Requirement: Root
2. Requirement: Allow APK install from Unknown Sources
3. Download the Safestrap APK
4. Find the APK using a Filemanager tool and open it on your device, then click "Install".
5. (If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this
message.)
6. Once installed, open up the Safestrap application as you would any other app.
7. Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
8. Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
9. From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap
10. Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
(this part was pretty straight forward)
Click to expand...
Click to collapse

Safestrap installing but not?

I actually searched this in depth and much to my surprise, I didn't find much. Odd.
I've got an ATT GS4 with the NC1 loaded. I'm rooted and ready to go after downloading a few files following instructions:
Code:
Files you will need on ExtSdCard before starting:
-- Safestrap-JFLTE-3.72-kk-B01.apk from here
-- ROM Install Zip (check ROM notes... may need to replace updater-script)
-- ATT_NC1_Modules.zip from here
-- UPDATE-SuperSU-v2.00.zip from here
ALL 4.4.2 ROM installs starting with rooted NC1:
0. Root and install safestrap v3.72
1. Copy remaining files above to extSdCard
2. Reboot into Safestrap Recovery
3. Wipe... Advanced Wipe... everything except extSdCard
4. Install... 4.4.2 ROM
5. Install... ATT_NC1_Modules.zip (to fix wifi)
6. Install... UPDATE-SuperSU-v2.00.zip (to keep root)
7. Reboot
8. Check APN settings and configure if necessary
I never got to the end because when I installed Safestrap, I chose "install recovery" and it went all the way to 100% and said the install was a success but for "state" it says "not installed".
Not sure what's going on. I do note that on the SafeStrap thread, it only mentions NB1 but I assumed that was the same as NC1 functionally.
I have SuperSU installed and Safestrap is listed in the apps section.
Like I said, I'm surprised I didn't find more info on this upon my searching.
Ive tried:
uninstall safestrap and superSU
reinstall
reboot multiple times in-between
Something odd that happened after I uninstalled superSU - I resbooted and what came up was a warning screen with yellow writing that warned me about installing alternative OS's. It asked if I wanted to install an alternative OS and I chose "NO" and it booted normally. Not sure where that screen came from or what it was. I never saw it again.

You need to set selinux to permissive mode and then you should be able to install safestrap recovery. Use selinuxmodechanger app for that

what's up with this software? anyone got 3.72b working on NB1?
burgertime78 said:
I actually searched this in depth and much to my surprise, I didn't find much. Odd.
I've got an ATT GS4 with the NC1 loaded. I'm rooted and ready to go after downloading a few files following instructions:
Code:
Files you will need on ExtSdCard before starting:
-- Safestrap-JFLTE-3.72-kk-B01.apk from here
-- ROM Install Zip (check ROM notes... may need to replace updater-script)
-- ATT_NC1_Modules.zip from here
-- UPDATE-SuperSU-v2.00.zip from here
ALL 4.4.2 ROM installs starting with rooted NC1:
0. Root and install safestrap v3.72
1. Copy remaining files above to extSdCard
2. Reboot into Safestrap Recovery
3. Wipe... Advanced Wipe... everything except extSdCard
4. Install... 4.4.2 ROM
5. Install... ATT_NC1_Modules.zip (to fix wifi)
6. Install... UPDATE-SuperSU-v2.00.zip (to keep root)
7. Reboot
8. Check APN settings and configure if necessary
I never got to the end because when I installed Safestrap, I chose "install recovery" and it went all the way to 100% and said the install was a success but for "state" it says "not installed".
Not sure what's going on. I do note that on the SafeStrap thread, it only mentions NB1 but I assumed that was the same as NC1 functionally.
I have SuperSU installed and Safestrap is listed in the apps section.
Like I said, I'm surprised I didn't find more info on this upon my searching.
Ive tried:
uninstall safestrap and superSU
reinstall
reboot multiple times in-between
Something odd that happened after I uninstalled superSU - I resbooted and what came up was a warning screen with yellow writing that warned me about installing alternative OS's. It asked if I wanted to install an alternative OS and I chose "NO" and it booted normally. Not sure where that screen came from or what it was. I never saw it again.
Click to expand...
Click to collapse
I've tried everything to load a rom onto this thing even what op replied and still nothing. My version of safestrap is 3.72 beta with NB1 4.4.2
I'm about to suck it up and stay on stock att witch i hate cause I can't use none of my tmobile features oh well. If anyone's got this working please, please let up know step by step how it was done.

Wanabedev83 said:
I've tried everything to load a rom onto this thing even what op replied and still nothing. My version of safestrap is 3.72 beta with NB1 4.4.2
I'm about to suck it up and stay on stock att witch i hate cause I can't use none of my tmobile features oh well. If anyone's got this working please, please let up know step by step how it was done.
Click to expand...
Click to collapse
That worked like a charm - the SELinux change app.
Thanks JmJoyas!

burgertime78 said:
That worked like a charm - the SELinux change app.
Thanks JmJoyas!
Click to expand...
Click to collapse
how are you loading the the roms? Is it threw one of the numbered slots or in the stock one? I don't wanna mess too much with the stock one but if it's the only one that work's then I guess i might give it a try.

Wanabedev83 said:
how are you loading the the roms? Is it threw one of the numbered slots or in the stock one? I don't wanna mess too much with the stock one but if it's the only one that work's then I guess i might give it a try.
Click to expand...
Click to collapse
At the time of this, I had not installed any roms. This thread was because I could not get safestrap installed.

burgertime78 said:
At the time of this, I had not installed any roms. This thread was because I could not get safestrap installed.
Click to expand...
Click to collapse
oh okay, cool. Do you know of a thread that you might link me to where they might be discussing that? If so link me if you can please.

Wanabedev83 said:
oh okay, cool. Do you know of a thread that you might link me to where they might be discussing that? If so link me if you can please.
Click to expand...
Click to collapse
Not sure of a thread for that. However, last night I installed over top of my stock slot. Apparently, KitKat does not allow flashing to "rom slot 1-4" so, I just did a full backup in safe strap, then wiped the stock slot and installed over top of it. worked fine.

Would like to flash a custom rom, seem to have a problem doing it. need help

Ok, after my last attempt to follow the instructions and spending over a full day with a bricked phone, I don't trust myself to do it again.
But I refuse to let the bloatware have its way...
So if someone can work me through the process to installing an easy, basic ROM I would highly appreciate it.
My phone is a Samsung Galaxy s4. i337. AT&T service, and it's on stock right now. 4.4.2. That's all I can tell you, I think it's Mk2 but I'd like to be able to find a way to MAKE SURE, before I screw anything up.
I have Odin, and I'm about to root my phone. If anyone will help me I'd greatly appreciate it!

i don't think you need odin anymore since towel root. i'm fairly certain it is just root, install safestrap, flash rom, flash root and carrier modules enjoy. goldeneye is a really nice rom for these phones with all the bloat removed and a few nice tweaks and addons.

exactly what i did last time, i flashed the new goldeneye with safestrap and it was brick city for 24 hours...
everything went fine and then it went into a bootloop when it tried to restart

First thing I'd do is read through this more than once http://forum.xda-developers.com/showthread.php?p=53758227
Then I'd update to nc1 firmware, root with towelroot, then install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
First thing I'd do is read through this more than once http://forum.xda-developers.com/showthread.php?p=53758227
Then I'd update to nc1 firmware, root with towelroot, then install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
alright thanks
is there no way to just upgrade from where I am now? really would take an inferior rom over having to upgrade firmware before I...upgrade firmware.....
also how do I tell for sure what I'm on now?

Damani311 said:
alright thanks
is there no way to just upgrade from where I am now? really would take an inferior rom over having to upgrade firmware before I...upgrade firmware.....
also how do I tell for sure what I'm on now?
Click to expand...
Click to collapse
Go into settings, about phone. Look at your build number, what are the last three characters?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Go into settings, about phone. Look at your build number, what are the last three characters?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nb1
sweet
recommendations?

Damani311 said:
nb1
sweet
recommendations?
Click to expand...
Click to collapse
I'd ota to nc1. Then you can use towel root to root
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I'd ota to nc1. Then you can use towel root to root
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Damani311-
You're on NB1 stock ROM, but I bet your baseband is actually NC1, based on the description here and in our PMs about your current status.
Like JD said, you can go into the phone's settings, and see if it takes the OTA update to NC1. That's the easiest way to get there. Alternatively, you can download the NC1 update zip file (from here) and flash it in the stock recovery. You get into stock recovery by starting with power off, and doing a power/home/upvolume start up. In there, there are options to install update from SD card. See the All things ATT & related links for the details. It's handy to have that NC1 updater zip. It's just an update that needs to be applied on top of NB1... it's not a replacement for starting with NB1.
Then, root with towel root. Install SuperSU from play store and let it disable knox. (may need to reboot phone after installing SuperSU if it hangs). Install SELinux Mode Changer from play store and set to permissive. Install SafeSTrap (from here). Note, there seems to be a zip file with lots of these goodies pre-included as a variant of the NC1 zip, at the same location quoted above. I haven't used that version, but it's probably fine.
Boot to safestrap. Very important: THOROUGHLY WIPE THE SYSTEM BEFORE FLASHING THE ROM. This means go into advanced wipe and wipe everything but the external SD card. Some folks say do it three times... seems to me there's a problem if doing it once doesn't work...
Then while still in safestrap recovery flash the GoldenEye ROM to the stock slot (our version of Safestrap only supports the stock slot). When it flashes, it brings up the Aroma installer. Choose the ATT / Safestrap options. When it finishes DO NOT DO NOT!! reboot. Exit the installer without letting it reboot and go back to safestrap. Some people recommend wiping the cache/dalvik caches again after flashing the rom (but of course you wouldn't wipe system at this point!).
While still in SafeStrap recovery:
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip (from here) . You could also manually enter the APN info (from the All Things ATT 1st post) but it is unclear to me whether GoldenEye properly identifies the phone build.prop entries with everything needed to be able to download all the I337 apps. I used the zip file and everything worked out great.
That's the overview. Detailed instructions are in the various threads. It sounds awfully complex but once you've done it a few times it all makes sense and is easy. But forgetting to do the wipes, or omitting SuperSu or any of the little details can cause a failure.
Takes ~5-10 mins for first boot, as I recall. I was nervous when it took so long. I left it, started cooking dinner, came back in a bit, it was done.
Good luck. Let us know how it turns out.

Frankenscript said:
Damani311-
You're on NB1 stock ROM, but I bet your baseband is actually NC1, based on the description here and in our PMs about your current status.
Like JD said, you can go into the phone's settings, and see if it takes the OTA update to NC1. That's the easiest way to get there. Alternatively, you can download the NC1 update zip file (from here) and flash it in the stock recovery. You get into stock recovery by starting with power off, and doing a power/home/upvolume start up. In there, there are options to install update from SD card. See the All things ATT & related links for the details. It's handy to have that NC1 updater zip. It's just an update that needs to be applied on top of NB1... it's not a replacement for starting with NB1.
Then, root with towel root. Install SuperSU from play store and let it disable knox. (may need to reboot phone after installing SuperSU if it hangs). Install SELinux Mode Changer from play store and set to permissive. Install SafeSTrap (from here). Note, there seems to be a zip file with lots of these goodies pre-included as a variant of the NC1 zip, at the same location quoted above. I haven't used that version, but it's probably fine.
Boot to safestrap. Very important: THOROUGHLY WIPE THE SYSTEM BEFORE FLASHING THE ROM. This means go into advanced wipe and wipe everything but the external SD card. Some folks say do it three times... seems to me there's a problem if doing it once doesn't work...
Then while still in safestrap recovery flash the GoldenEye ROM. When it flashes, it brings up the Aroma installer. Choose the ATT / Safestrap options. When it finishes DO NOT DO NOT!! reboot. Exit the installer without letting it reboot and go back to safestrap. Some people recommend wiping the cache/dalvik caches again after flashing the rom (but of course you wouldn't wipe system at this point!).
While still in SafeStrap recovery:
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip (from here) . You could also manually enter the APN info (from the All Things ATT 1st post) but it is unclear to me whether GoldenEye properly identifies the phone build.prop entries with everything needed to be able to download all the I337 apps. I used the zip file and everything worked out great.
That's the overview. Detailed instructions are in the various threads. It sounds awfully complex but once you've done it a few times it all makes sense and is easy. But forgetting to do the wipes, or omitting SuperSu or any of the little details can cause a failure.
Takes ~5-10 mins for first boot, as I recall. I was nervous when it took so long. I left it, started cooking dinner, came back in a bit, it was done.
Good luck. Let us know how it turns out.
Click to expand...
Click to collapse
wow awesome dude thanks a ton!
got to the part after installing safestrap, where it's time for goldeneye
which version of the rom should i use? the newest one got me in big trouble last time?
and so I'm going to need 4 zip files on my phone before i flash ROM?
Flash Goldeneye
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip
?
If so i'll proceed.....thanks again

I'm using Golden Eye v36. However, I've seen folks saying v38 (current) is good too... not sure where the problem cropped up with your last attempt so I can't speculate what the problem was.
And you're right, there should be 4 zip files on your SD card. The ROM, SuperSU, NC1 module, and the ATT APN/BuildProp file, which may not be necessary but worked fine for me.

alright looks like I'm up and running! wifi doesnt work, I think that's the only issue I can detect so far.........

WiFi fail usually fixed by flashing module matching your baseband. If nc1 module doesn't fix it, try nb1.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Frankenscript said:
WiFi fail usually fixed by flashing module matching your baseband. If nc1 module doesn't fix it, try nb1.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
i was hoping that was it, but it didn't get it....shoot
thanks for helping me out here
i flashed the jfleatt nb1 modules, btw

I'm out of ideas, sorry! Maybe start a thread about module not restoring WiFi after flash. My one relevant data point is that once, instead of Odin NB1 then flash NC1 update, I odined the rootable NB1. After that I did safestrap and flashed a ROM plus modules. I was never able to get WiFi no matter what I flashed. Odined back to regular NB1 then did NC1 update. Flashed ROM and modules again... Success. I assume kernel (locked on nc1 for me) has to interact with ROM and module. Improper match causes fail. Are you certain of what baseband you have?
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Did you do the Selinux thingy--:good:

rugmankc said:
Did you do the Selinux thingy--:good:
Click to expand...
Click to collapse
Damani311,
Were you able to sort out the WiFi? Poking around the internet it does seem like permission issues are often at root of it, and the Selinux Mode Changer mentioned above (set to permissive) might be the solution.
Good luck! :good:

I think he is sorted based on posts on other threads. Maybe he will let us know--:good:

In just a couple of words, here's a basic overview of the ROM-flashing process:
- Root using Towelroot
- Install SuperSU
- Install Safestrap
- Download ROM
- Download modules
- Flash both
- Reboot
- Enjoy
Just make sure that whatever firmware you're on matches the ROM and modules (ex. NB1 users flash NB1 ROMs or MK2 ROMs and NB1 modules)
Best of luck! :good::good::good:

Appreciate your reply, but think OP is sorted and never came back--

Magisk

Dear advisors,
Iam using stock samsung note 4 SM-910G. Snapdragon 805. Android 6.0.1. Marshmallow. I need advise on to how to install magisk on my device. Can it be done? Appreciate on a step by step instruction on how do i install it.

I don' think this is the right place for this, but it't not my job to decide.
Anyways, which ROM are you using? Are you on stock TouchWiz?

No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?

Firdhaus81 said:
No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?
Click to expand...
Click to collapse
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.

Black Shade said:
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.
Click to expand...
Click to collapse
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.

Firdhaus81 said:
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.
Click to expand...
Click to collapse
As I thought, Magisk won't work with the stock ROM. The main issue here is the kernel, which doesn't allow such modification. ChainFire has found a workaround to bring SuperSU on TouchWiz, but the fact it's not open source doesn't allow Magisk developers to use the same method. The head developer, few months ago, said that he was working on it and he was making some progress, but apparently it's not ready yet. I think it's not worth trying again, it won't work at the moment. I suggest keeping an eye on the thread, in case there are some updates. At the moment, I recommend either using SuperSU (which I recommend anyways), or flashing a different ROM, since deodexed TouchWiz ROMs with H-Vitamin or RAM Kernel do actually support Magisk, I tried myself.

Thread moved to proper section

The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. :laugh:

Firdhaus81 said:
The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. [emoji23]
Click to expand...
Click to collapse
Black Shade is right about the kernel. Using the wrong kernel will cause the install to fail. I'm on an n910t3, using ramrom v3 kernel, and I'm using magisk 13.3 for Android pay and viper audio. There's an official magisk 13.3 thread on xda somewhere. You should try there as a start.
Sent from my SM-N935S using Tapatalk

Attached my kernel info if u can help to check?

Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G

thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G[/QUOTE]

MagiskFan said:
Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.

pippideniro said:
thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
[/QUOTE]
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.

@lhooipg Were you asking to help him, or do you wanna know yourself?

bmwdroid said:
@lhooipg Were you asking to help him, or do you wanna know yourself?
Click to expand...
Click to collapse
I wanna know myself, I am facing the same issue as him. Thank you.