Develop Bugs

[GUIDE][I337UCUAMF3][STOCK][NEUTERED] MF3 OTA Update - Keep Recovery and Root! [7-12]

Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
NOTICE: These instructions are pretty much obsolete. If you'd like to run a pure stock MF3 rom based on this exact method of neutering the MF3 OTA update, then read this thread. This thread shall remain for informational purposes only.
A quick THANKS to djbliss (motochopper root exploit), TeamWin (TWRP recovery), Chainfire (SuperSU), and all of the Guinea pigs that tested some of this stuff out for me in this thread.
What is this?
This is not technically a ROM, but by the time you are done, you will be running the stock, (albeit rooted) I337UCUAMF3 ROM provided by AT&T. Unlike the original MF3 OTA patch, if you perform the steps outlined in this thread, you will not lose your custom recovery, and your bootloader (including aboot) will remain untouched.
Here's what the neutered version does:
It will flash a new boot.img, which primarily includes the MF3 Kernel.
It will flash the RPM partition, which as far as I can tell is strictly for power management. I kept it in the package because it seems harmless.
It will update many files in your /system partition, bringing you up to the latest MF3 build (the whole point).
It will flash the new MF3 modem/Baseband, along with its counterpart, the NON-HLOS partition as well. The NON-HLOS partition will cause some problems with your sound (keep reading), but I've added a patch here that will solve this problem while creating another (WiFi breaks). I've kept this included in the original neutered patch, just in case someone is able to find a very easy fix for the sound and/or WiFi.
Can I go back?
From my experience, if you do not update the bootloaders, it is fully possible to return to the I337UCUAMDB or I337UCUAMDL stock versions. I used Odin, personally, but you could simply restore nandroid backups or flash a new rom. Your modem/Baseband will stay at I337UCUAMF3, along with your RPM partition - unless you use Odin or otherwise flash older versions manually. Personally, I found ZERO side-effects of performing these steps and then restoring my MDL-based nandroid backup.
Bugs?
At this time, you will have to choose between either having sound, or having WiFi. Can't have both. This is completely related to the NON-HLOS modem that's included and expected in the MF3 build. As mentioned above, the new NON-HLOS modem will kill your sound capabilities without having the new bootloaders, etc. I have no idea why, so I've provided a "fix" for this - a flashable .zip that will restore your NON-HLOS modem back to the MDL version. If you revert to this MDL NON-HLOS modem, you will lose WiFi capabilities. If someone finds a more proper fix for this, please let everyone know. Otherwise, you're welcome to keep switching back and forth as you please. See the section in this post about flashing just the modems.
Anything else?
In addition to all this, I've provided a modified, deodexed SecSettings.apk that will not scan for SysScope and will not mark your system as "Custom". This add-on package also removes SysScope entirely from the OS. This add-on optional, and you can choose not to flash this part if you wish. This package is based on my previous mod, located here (some minor changes in Status.smali to match the new MF3 build, but otherwise the same steps were performed to create this new SecSettings.apk). Basically, if you perform all of the steps outlined in this method, you will find yourself with an "official" status, and will have the original "Galaxy S4" boot logo (not the custom/padlock logo), regardless of the root or custom recovery.
Warnings and Caveats:
I have not extensively tested the I337UCUAMF3 operating system, and I WILL NOT be providing tech support for this operating system. Take it AS-IS, and ask your questions about the OS in the Q&A forum. This thread will be only for the process of getting you to I337UCUAMF3.
NOTICE: This is only intended for the I337 - a.k.a. the AT&T Galaxy S4. I have only tried this on my 16Gb, original device. You may try it on other devices, but there is of course a very high risk of bricking your non-i337 device. You've been warned.
WARNING: I am not responsible if you brick your device. Follow the instructions very, very closely, and you will be fine.
ANOTHER WARNING: There are mixed reports about certain things being broken with the MF3 update, such as the "free unlock with hidden menu" and tethering, etc. If these are important to you, you might want to make a full backup of your EFS just in case. Most custom recoveries (including the provided TWRP recovery) can help you do this. The EFS partition does not appear to be touched during the update, but just in case the new kernel or new modem does something to it on-the-fly, it would be a good idea to have a backup.
Okay, great. So what do we do?
Click the "Click to show content" button below to begin.
Download all these prerequisites. Get the downloads started now, and just read-ahead so you are familiar with the next steps.
openrecovery-twrp-2.6.0.0-jflteatt.img
Original is found on TWRP's website.
NOTE: You can download your own recovery.img if you'd like. Continue reading instructions for more details.
MDL-noSecure.zip
MF3-Neutered.zip
UPDATE-SuperSU-v1.41.zip
Original is found on Chainfire's website.
remove-SysScope.zip
modem-fix.zip
motochopper-mod.zip
Put each and every one of these downloads onto the root of your internal SDCard (/sdcard/).
Make a full Nandroid backup of your device - include system, data, and everything.
Make a backup of everything that is on your internal SDCard - it's possible to accidently wipe it.
Wipe data. Be careful not to wipe your SDCard!
Odin to stock, unrooted MDB package. Instructions here.
Allow the device to reboot fully into the clean, stock MDB. This will clear your "Custom" status, by the way.
When returning to MDB, some apps will likely force-close when they start. This is due to data problems with these apps. You could wipe data again to remove these, but there is risk of wiping your SDcard if you do it wrong. Otherwise, just clock OK and get through them all before continuing.
Run Motocopper - Use custom version that I've provided, OR you can download the original version here http://forum.xda-developers.com/showthread.php?t=2252248
NOTE: If you use the original version, be sure not to allow it to restart your device! At the end when it prompts you to "Press Enter to reboot..." - DO NOT REBOOT.
Install a custom recovery using your ADB shell. Do NOT mistype the partition number at the end, or you can easily hard-brick your device.
Code:
# dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
# reboot recovery
Note: You should be able to use your own recovery. You will need to install it using the method above, however. Programs like GooManager will not work at this stage.
Allow the device to reboot directly into recovery. Do not leave recovery until instructed to do so.
Flash MDL-noSecure.zip
NOTE: This is the original AT&T I337UCUAMDL update, but with the "ro.secure" check removed, and the recovery removed. Otherwise it is the same thing.
Flash MF3-Neutered.zip
Flash UPDATE-SuperSU-v1.41.zip
Flash remove-SysScope.zip
NOTE: This package will also clear your dalvik cache, just in case.
Flash modem-fix.zip
NOTE/BUG: If you skip this, you will lose all audio. If you flash this modem-fix, you will lose WiFi. Currently working on investigating this!
Wipe Data/Cache.
Reboot the device into system.
Enjoy I337UCUAMF3.
Click the "Thanks" button if this has helped you.
But I only want to flash the new modem (Baseband). Do I have to do all that crazy stuff?
Certainly not! You can flash just the modem itself, very easily. You need to be rooted, or have a custom recovery first.
The Manual Method - requires root (advanced users, but technically easier and quicker!):
Download the .zip I created of all the modems I've ever had here.
Make a nandroid backup for safekeeping. Note that a nandroid backup will not typically backup your current modem - this is just a precaution in case you mess things up and have to use Odin to restore your modems or something. Better safe than sorry!
Unzip contents to your sdcard.
Fire up your ADB shell.
Type the following very carefully. DO NOT GET THE PARTITION NUMBER WRONG or you could easily brick your device. Badly.
Code:
su
dd if=/sdcard/modem-MF3.bin of=/dev/block/mmcblk0p2
reboot
Start testing it out!
NOTE: The included NON-HLOS.bin is intended for mmcblk0p1. If you are on an MDL-based ROM and/or Kernel, don't flash this file yet, unless you're being experimental. Here's why:
If you have an MDL-based ROM/Kernel... said:
If you have an MDB NON-HLOS.bin and an MF3 modem.bin, Wi-Fi will break.
If you have an MF3 NON-HLOS.bin and an MF3 modem.bin, sound will break.
If you have an MDL NON-HLOS.bin and an MF3 modem.bin, .... Nothing seems broken. Sound and Wi-Fi are working.
Click to expand...
Click to collapse
The Automatic Method - requires custom recovery (recommended for flashaholics):
CPA Poke has offered a flashable version of the modem as an option here.
I just want the original, unaltered I337UCUAMDF patch. Where can I find it?
You can download it here. This was taken straight from \cache\fota\2400258.cfg. You can rename it as a .zip if you'd like to mess with it. Please note that this file may not be flashable on your device if you have customized your /system partition or have made other modifications to your device. This patch performs a series of integrity checks, and will not install if it fails any of them. If it fails, you should be safe, as the patch sequence aborts before making changes if it fails the checks.
BE FOREWARNED: Flashing this file directly will cause you to lose root, lose your custom recovery, and lose the ability to obtain root in the future (as far as we know). In other words, DO NOT install this unaltered, original update if you EVER want to have root again, flash custom ROMs, or have the ability to make/restore nandroid backups. You've been warned.
How can I make my own neutered version of the OTA patch?
Check out post #2 in this thread for all the details on how to customize your OTA patch file, including the warnings and potential ways you can hard brick your device.
What was changed in this patch?
If you were to flash the original patch without neutering it first, you'll be stuck with a stock MF3 build (or higher). As far as we can tell, this patch does blow some e-fuses in the device, incrementing a number such that it is impossible to return back to an older build (MDB or MDL). There is currently no known cure for this condition if this is the case, especially considering we have locked bootloaders on the I337 at this time.
For a complete list of all the files that this patch touches on your system, you can check out my previous post here.
Can I use this in my own ROM?
Certainly! In fact I encourage it. I'd like to see some cool ROMs be built using the MF3 base. It's got some nice improvements on the MDL base, so any stock-based ROMs should benefit. You have my full permission to use this complete process or any parts/pieces/packages/methods herein. I would like to see my name mentioned in your "thanks" list if you have one, but this is of course completely optional.
Where can I download a full system and kernel dump of the work you did? (ADDED 7-12-13)
You can download it right here. Apart from the SysScope mod mentioned above and injecting root, this is the full, stock image. This is NOT directly flashable, so don't even try. This will only be useful for ROM developers and advanced users. The modems and bootloaders have nothing to do with these packages, but these might be required for everything to work correctly (i.e. sound and WiFi).
This was created from my device after performing all the steps above, using these commands while the device was in recovery, from a root ADB shell:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/system-MF3.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/boot-MF3.img
Do you have this available as a ROM I can flash? (ADDED 8-6-13)
Indeed! If you want to install this as a ROM, check out my newer thread here.
Anything I can do to help here?
If this information and tutorial helped you out, just simply hit the "THANKS" button. It's great to know the work was appreciated. Another way that you can help is to provide feedback in this thread about how it worked for you, and if there's any improvements that can be made. Lastly, if you're interested in helping financially to help recover the costs of the JTAG box I now need to recover my S4, you're certainly welcome to assist by using the donate link on the left. Keep in mind that I'm not technically a Dev here - I'm just another forum member that's providing information to other members. It's what this whole community is about.

How can I make my own neutered version of the OTA patch?
With lots of careful snipping. But first, you need a copy of the original OTA patch. You can download this from my post above, or you can download one yourself straight from AT&T.
To download your own copy, the process is not terribly complicated - just risky. Here's the steps I performed to obtain the original update file from AT&T:
Make sure you have root before continuing. If you screw this up and allow the update to install, you're pretty much SOL.
If you are running the stock MDL rom, you can simply launch the updater in Settings -> More... -> About device -> Software update and let it download. Just don't reboot your phone until you've then frozen the AT&T update applications (all 3 of them) from performing the update. Keep in mind that your device will eventually reboot on its own, thanks to AT&T and their way of forcing updates.
Pull the update file from /cache/fota/2400258.cfg, and put it somewhere on your computer that you can work with it. It's just a .zip file in disguise, so you can simply rename it appropriately.
Delete the original .cfg from the device.
As mentioned, freeze or disable the updater applications.
You now have your own copy of the OTA update.
Great - you've got the file. Time to grab the scissors and perhaps something to steady the hands and numb the pain. A keyboard works too in this case. Here's what to do:
Save a backup copy of your update file. One copy for safekeeping (in case you want to start over) and another to work on. Do it now.
Open the update file using basically any .zip editor. I used 7zip because it performed quickly, whilst Win7's zip capabilities were VERY SLOW dealing with this file.
[*]From the root directory of the file, delete:
aboot.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
The entire "recovery" directory.
Within the file, browse to META-INF\com\google\android and pull a copy of the updater-script. This file does all the magic.
Edit the updater-script using a text editor, preferably something like Notepad++ (great program! I recommend it). Make the following changes:
Remove the following line:
Code:
assert(getprop("ro.secure")=="1");
Edit the following line from:
Code:
"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil",
to
Code:
"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil");
Remove the following line (it's right after the last one you edited):
Code:
"/system/recovery.img");
Remove the following lines:
Code:
delete("/system/recovery-from-boot.p",
"/system/etc/install-recovery.sh");
and remove:
Code:
ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/system");
and remove:
Code:
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
and remove:
Code:
ui_print("Update sbl2 ota");
assert(write_backup_fota("/dev/block/mmcblk0p4", "/dev/block/mmcblk0p22"));
assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p4"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package sbl2 Done.");
ui_print("Update sbl3 ota");
assert(write_backup_fota("/dev/block/mmcblk0p5", "/dev/block/mmcblk0p22"));
assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p5"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package sbl3 Done.");
ui_print("Update aboot ota");
assert(write_backup_fota("/dev/block/mmcblk0p6", "/dev/block/mmcblk0p22"));
assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p6"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package aboot Done.");
and remove:
Code:
ui_print("Update tz ota");
assert(write_backup_fota("/dev/block/mmcblk0p8", "/dev/block/mmcblk0p22"));
assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package tz Done.");
Save it, and put the modified updater-script back inside the update file where you found it, replacing the old one.
Upload it to your SDCard and flash. See all the warnings here in this post and in the original post about what to do with this thing.
NOTES and WARNINGS:
A careful reader will be able to easily tell what each part of the updater-script does, and you can choose whether or not to keep it, modify it, or delete it.
Keep in mind that the update will fail if it does not pass all of those integrity checks. You can technically remove all of the integrity checks, and the update will still process, patching files left-and-right. However, depending on how heavily you have modified your system, you will probably run into extreme problems (soft brick most likely).
CRITICAL WARNING ABOUT BOOTLOADERS: At this time, do NOT allow the update package to only partially update your bootloader! Failure to update the entire bootloader will result in a hard brick. For example, if you were to include the parts that update sbl2 and sbl3, but not include tz and aboot... your chain of trust will be violated, and the device will refuse to boot normally (a.k.a. QDL Mode or Emergency Boot). The only theoretically known way out of this is JTAG. You don't want to go there. So, simply put: regarding bootloaders, it's all or nothing. The bootloader updates included in this package are: sbl2.mbn sbl3.mbn aboot.mbn tz.mbn. It's like any good D&D campaign - if you separate these party members, the campaign is toast.
REMINDER: At this time, it appears that flashing the new bootloader will trip an e-fuse. This is a hardware device that is only capable of incrementing a number. If the number on the e-fuse is higher than the bootloader you are trying to flash (with Odin, for example), the device will refuse to take the update. In other words, if you flash the MF3 bootloader, there is no known way to return to the MDB or MDL bootloaders at this time.

Nice...as usual. Just to help make it clear, are you allowing other developers to use this to put into their ROMs (with credit given of course)?
Again, thanks for your work.

scott14719 said:
Nice...as usual. Just to help make it clear, are you allowing other developers to use this to put into their ROMs (with credit given of course)?
Again, thanks for your work.
Click to expand...
Click to collapse
Certainly! I've updated the OP with, "You may also use any of the packages created or modified here for inclusion in your ROMs." at the end of it to clarify. Thanks for bringing it up. :good:

thanks man!!.. you put alot of work into this!!! very nice job:good:

Aou said:
Certainly! I've updated the OP with, "You may also use any of the packages created or modified here for inclusion in your ROMs." at the end of it to clarify. Thanks for bringing it up. :good:
Click to expand...
Click to collapse
Just an fyi... Dropbox ha temporally disabled the down load. At least that's the error in getting.
Sent from my SAMSUNG-SGH-I337 using xda premium

spdwiz18 said:
Just an fyi... Dropbox ha temporally disabled the down load. At least that's the error in getting.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Figures. >_<
Looks like I'll need a better place to upload these... I'll upload them elsewhere and update the OP as soon as I can find a good place to put them.
Thanks for notifying me!!

Aou said:
Figures. >_<
Looks like I'll need a better place to upload these... I'll upload them elsewhere and update the OP as soon as I can find a good place to put them.
Thanks for notifying me!!
Click to expand...
Click to collapse
You dida great job, but think there may be an easier way to update if you are interested.
Food for thought.
This will only work with yours since you are updated.
dd if system and boot to the sdcard as system.img and boot.img.
Use kitchen to extract system and build update zip from that. This would create less flashes as it would have root and everything else built in.
Just a thought. If it sound likeva c goid idea. Great! If not its ok.
Again. Great job.
Sent from my SAMSUNG-SGH-I337 using xda premium

Just wondering what's up with sound. So weird modem would mess with that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

spdwiz18 said:
You dida great job, but think there may be an easier way to update if you are interested.
Food for thought.
This will only work with yours since you are updated.
dd if system and boot to the sdcard as system.img and boot.img.
Use kitchen to extract system and build update zip from that. This would create less flashes as it would have root and everything else built in.
Just a thought. If it sound likeva c goid idea. Great! If not its ok.
Again. Great job.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I haven't actually build a ROM yet, but this might be a good time to try!
jetlitheone said:
Just wondering what's up with sound. So weird modem would mess with that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
iknorite? Perhaps a more experienced Dev could shed some light on what's going on with this. If a solution is found, I would love to incorporate it into this project.
Also, an update: I added instructions in post #2 on how you can obtain and neuter your own OTA update file. I have no intentions of hiding any of my work.

Aou said:
I haven't actually build a ROM yet, but this might be a good time to try!
iknorite? Perhaps a more experienced Dev could shed some light on what's going on with this. If a solution is found, I would love to incorporate it into this project.
Also, an update: I added instructions in post #2 on how you can obtain and neuter your own OTA update file. I have no intentions of hiding any of my work.
Click to expand...
Click to collapse
You've tried different kernels and such
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Aou said:
I haven't actually build a ROM yet, but this might be a good time to try.
If you want or need help in this. Just ask.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse

I already sort of updated to the latest version I337UCUAMF3. Is there any hope left for me? Can I roll back to the previous versions and get my root back or should I just sit and wait and hope someone releases a root for the newer version?

Mrkqql143 said:
I already sort of updated to the latest version I337UCUAMF3. Is there any hope left for me? Can I roll back to the previous versions and get my root back or should I just sit and wait and hope someone releases a root for the newer version?
Click to expand...
Click to collapse
You can probably do the Samsung update utility through kies
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

jetlitheone said:
You can probably do the Samsung update utility through kies
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I am saying I already updated. Is there a way for me to go back using the utility?

Mrkqql143 said:
I am saying I already updated. Is there a way for me to go back using the utility?
Click to expand...
Click to collapse
Yes it'll update you backwards since the new update isn't up on their site haha do an emergency firmware update or whatever
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Mrkqql143 said:
I am saying I already updated. Is there a way for me to go back using the utility?
Click to expand...
Click to collapse
Last I read odin was a no go if you take the update so you're stuck until someone figures out how to get around it.
EDIT: Let me know if the above works if you try.

If I am rooted with supersu 1.41 (custom status removed) and cwm recovery - can I just flash the neutered ota.zip and get the modem update that came with the ota zip?
Thanks for the clarification.

Noobla_Khan said:
Last I read odin was a no go if you take the update so you're stuck until someone figures out how to get around it.
EDIT: Let me know if the above works if you try.
Click to expand...
Click to collapse
Nope. Odin is a NO go!

Mrkqql143 said:
Nope. Odin is a NO go!
Click to expand...
Click to collapse
Yup knew odin was a no go, I was wondering if you could emergency back with Kies due to them not having the update on the web yet as stated above.

How to root after you take the OG5 OTA update

Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)

Will this process work on the Galaxy s5 with og5 5.11
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?

Dmary said:
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Click to expand...
Click to collapse
PM sent.
Sent from my SM-N910P using Tapatalk

So, its been about a year since I rooted a phone, but I feel like I'm missing something at the beginning of the instructions. In the video
https://www.youtube.com/watch?t=32&v=k2oOvf5tOCY
it goes over the auto root process, but that hasn't been updated. Is that something I need to run first anyway? Wouldn't it not work due to the mismatch of android version?
Oh, never mind. It froze at the TWRP screen, but a restart fixed that.

I would like to know if it's possible on the S5 as well...G900V...Everywhere i've read says it's not.
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse

When I try to flash twrp, odin says failed. Any suggestions?

Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...

Newbie_from_NJ said:
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Click to expand...
Click to collapse
TWRP is fine for most. Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
If you decide to flash a custom ROM and get a binary failure, reboot recovery and try again.
Sent from my SM-N910P using Tapatalk

samep said:
Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
Click to expand...
Click to collapse
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk

Newbie_from_NJ said:
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
From power off, Vol+, Home + Power.
Sent from my SM-N910P using Tapatalk

I am also curious about whether this would work on a G900V.

Anyone try this on their 920v????

samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Could you please reply about G900V? I would greatly appreciate it.

AcidBurn22 said:
Could you please reply about G900V? I would greatly appreciate it.
Click to expand...
Click to collapse
I sent the PM to not clutter this thread with off-topic discussion.
Sorry, I don't have this phone, nor have I rooted one.
If you need help or don't know where to start, I'd suggest reading thread below before asking in thread:
http://forum.xda-developers.com/showpost.php?p=61688768&postcount=1
Reading through the OP's threads, the same thing started at OE1 update that started here, you can no longer downgrade in Odin once taking this one and later updates; it progressively worsens. Regarding your carrier, it appears that root prior to OG5 update is a prerequisite as well as steps to keep root in the update process (those do not apply here). But I don't claim to know any more about it than you so read, search and ask in the appropriate thread. Best wishes for success; perhaps it's not as grim as I describe it. I only researched a few minutes, following closed threads to links to next thread, starting here:
http://forum.xda-developers.com/showpost.php?p=61682294&postcount=242
If you have a choice, don't take the OE1 update until you're rooted and clear on how to keep root through updates. But again, I'm not claiming to know any more than yourself, possibly less with the effort I gave.
Anyone else finding this through search, please keep this thread on topic. Refer to your specific thread regarding phone model and carrier. Thanks.
Sent from my SM-N910P using Tapatalk

DaggettBeaver said:
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Click to expand...
Click to collapse
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:

Reivaj1803 said:
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Click to expand...
Click to collapse
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk

samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I wasn't aware of the latest update, thanks for the heads up.
I have never tried Chainfire auto root. I found Chainfire post http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
I'll try this route.
Thank you sir, greatly appreciate it. ???

samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?

Reivaj1803 said:
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Click to expand...
Click to collapse
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk

samep said:
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually did remove and disabled most the apps that I was able to. The rest there were not options, other than root.
My preference was to root, maintain OTA capabilities and remove the bloatware.
What option/s would best suit that preference?

Want to root Friends Note 4, a few questions.

Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?

The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk

How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.

rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk

samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.

rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk

Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.

[ROM] [Touchwiz-PC1,PD1] [100% Stock, Root, No KNOX, No Itson] [4/5/2016]

Once again I bring to you completely stock builds of Android Marshmallow 6.0.1 (N910PVPU4DPC1 and N910PVPS4DPD1) for the Sprint Samsung Galaxy Note 4.. The ROMs are built from the official Samsung tar balls. The ROMs will self root upon flash and have init.d/busybox support. Knox and Sprint Itson has been removed. These ROMs are completely stock with all of the original factory installed apps. You will have to de-bloat yourself if you so choose.
Other than the removal of Knox and Sprint Itson, the ROM is 100% stock in every other way. It is stock and will stay that way. Please don't ask for mods, changes, etc in this thread. This ROM is intended for those people who want the stock ROM in it's original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base ONLY if you contact me prior to using it. If I find users using my work without proper credits I will report you and make you look like a fool. Do the right thing and give credits to people for their time and work. It's a courtesy and respect thing, nothing more. With that said, I highly recommend other rom chef's/dev's to use this base rom because it is bug-free and built from the official Samsung tar ball. Last but not least, if you appreciate my work please press that Thanks button, rate this thread and consider a kind donation! Enjoy!
Mods, etc will be in post #2 below.
Important Notes: Before flashing ANY Marshmallow 6.0.1 TW-based ROM, including this one, you MUST first do one of the following:
1. Take the Marshmallow PC1 ota update on your phone. (Start by being on the stock unrooted OK1 rom then take the PC1 ota update)
2. Odin flash the stock PC1/PD1 ROM tar using odin on your PC.
Once you have correctly updated your Note 4 to Marshmallow 6.0.1, software version N910PVPU4DPC1 or N910PVPS4DPD1 DO NOT... I repeat, DO NOT attempt to root your phone with CF-auto root or other methods. It will soft brick your phone. Instead, you ONLY need to flash the latest TWRP recovery using odin on your pc. Nothing else. These ROMs will pre-root your phone using the new systemless root by Chainfire as well as flash the stock PC1/PD1 kernel.
If you are still on any KK or Lollipop 5.0 TW-based ROM such as NIE, OB7, OE1 , OF5, OG5, OJ6 or OK1 (including any KK AOSP/CM-based roms) then you MUST first update to Marshmallow 6.0.1 PC1 by one of the two methods I mentioned above BEFORE flashing this ROM. Failure to properly update your device partitions to 6.0.1 PC1 firmware absolutely WILL cause problems. You have been warned. Please don't ask for help if you did not follow my simple instructions and warnings.
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal and external storage to another location just to be safe.
2. Download the ROM using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the MD5!!! Once the download has finished, compare the androidfilehost MD5 using a MD5 tool on your pc. (Google "md5 checksum windows") for a good MD5 tool for your pc.
4. Put the downloaded ROM onto your internal storage or external micro sd card.
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT micro-sd card and internal storage. Internal storage is optional but recommended when first updating to a major software revision such as 4.3 to 4.4 or 5.0.1 to 5.1.1, or 5.1.1 to 6.0.1. The reason is to remove left-over data from previous version of Android and start with a clean slate. I highly recommend doing this for a trouble-free experience.
7. Choose the "Install" option and select the ROM "Stock_DeOdexed_N910PVPU4DPC1_1.0_03302016.zip" or "Stock_DeOdexed_N910PVPS4DPD1_1.0_04302016.zip" from either your internal or external micro-sd card. It will flash the ROM and give a confirmation once completed.
8. Reboot system. The phone will reboot two times while the systemless root builds the new .img and properly sets up root on your phone. It is automated so let it do it's thing. Once the Samsung boot animation completes the phone will boot in approximately 12 minutes.
9. Let the phone optimize for at least 12 minutes (for the deodexed rom) and the screen will show the setup wizard once it finishes. Proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically download the Sprint "bloat" installer and begin installing the addition Sprint apps exactly the way it does on a new phone when you first turn it on. That's it! You're done!
Credits:​@Chainfire for root and SuperSU. Without him we would not have root. Thank you!​@TeamWin for TWRP recovery. http://teamw.in/project/twrp2 and here​
flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device. However, all of my roms, mods, etc are pre tested by myself and other testers prior to public release.
Stock_DeOdexed_N910PVPU4DPC1_1.0​Stock_DeOdexed_N910PVPS4DPD1_1.0​
XDA:DevDB Information
Stock-Rooted-TW-Marshmallow, ROM for the Sprint Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910PVPU4DPC1 - N910PVPS4DPD1
Based On: ALL_SPT_N910PVPU4DPC1_N910PSPT4DPC1_CL7381751_QB8794358_REV00_user_low_ship_MULTI_CERT.tar / N910PVPS4DPD1_N910PSPT4DPD1_N910PVPS4DPD1_HOME.tar
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2016-04-05
Current Beta Version: N/A
Created 2016-04-06
Last Updated 2016-05-07

Mods​
Hotspot mod for N910PVPU4DPC1 ONLY
Hotspot mod for N910PVPS4DPD1 ONLY
Hotspot mod for N910PVPU4DPE1 ONLY
(my hotspot mods are made to work on both stock odexed and deodexed roms for their corresponding software version. The installer script will automatically handle everything, just flash and reboot and you're done)
Note: These hotspot mods are primarily intended for stock roms. If you run a custom rom that has a modified services.jar then flashing these "stock" hotspost mods will break those other mods in services.jar, such as reboot mod for MM roms. Check with the rom dev for details on specific mods used in their roms before flashing these. In any case, these hotspot mods will work fine even if other mods in a custom rom get replaced by the stock java classes. No harm either way, you would simply be without the custom mods.
Private Mode Fix for N910PVPU4DPE1 may also be used on previous MM software beginning with software version PC1. DO NOT use on Lollipop or earlier software.

last one... just in case.

tx_dbs_tx said:
last one... just in case.
Click to expand...
Click to collapse
Thank you tx_dbs. You are so awesome

Sorry it took so long to get this rom posted. i've had it done for several days, i just didn't post it. Anyways, it's good to go!

tx_dbs_tx said:
Sorry it took so long to get this rom posted. i've had it done for several days, i just didn't post it. Anyways, it's good to go!
Click to expand...
Click to collapse
Been patiently waiting on this, thank you sir!!

Awesome work! Using the Texas mirror for obvious reasons.
Sent from my SM-N920P using Tapatalk

I am downloading this now, I mainly use AOSP but have been waiting to try your flavor of the official MM release, thanks!

GROOVYJOSHCLARK said:
I am downloading this now, I mainly use AOSP but have been waiting to try your flavor of the official MM release, thanks!
Click to expand...
Click to collapse
Lol its stock. Not really his flavor
Sent from my 0x1 Note 4...... I love tep

Finally a twrp flash3ble pc1 stock rom! Thanks
Sent from my SM-N910P using XDA-Developers mobile app

kaos420 said:
Lol its stock. Not really his flavor
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
his flavor enough, meaning it is deoxed, no itson, no knox, goodies like that.
---------- Post added at 02:55 PM ---------- Previous post was at 02:52 PM ----------
Shoot, mine didnt self root, I followed the directions to the T (using TWRP 3). Anyone else have issues?
-EDIT, correction, it still didnt self root using TWRP, however using SuperSu-v2.46.zip in recovery DID work and installed the correct binaries needed to root. So it seems to work and boot NP with this version of binary installed.

Wow, there is a God.

I must be missing something......where can i get the the Stock PC1 ROM Tar?
Thanks in advance.

GROOVYJOSHCLARK said:
his flavor enough, meaning it is deoxed, no itson, no knox, goodies like that.
---------- Post added at 02:55 PM ---------- Previous post was at 02:52 PM ----------
Shoot, mine didnt self root, I followed the directions to the T (using TWRP 3). Anyone else have issues?
-EDIT, correction, it still didnt self root using TWRP, however using SuperSu-v2.46.zip in recovery DID work and installed the correct binaries needed to root. So it seems to work and boot NP with this version of binary installed.
Click to expand...
Click to collapse
You must have done something wrong. When you flash the rom it will automatically add root binaries and supersu.
salukis93 said:
I must be missing something......where can i get the the Stock PC1 ROM Tar?
Thanks in advance.
Click to expand...
Click to collapse
Look in the Note 4 general forum. User "Sunderwear" posted the PC1 tar in a general thread.

thank you good sir!!! been waiting for this.

Many Thanks. Installing now. Love all your Roms.
Cant wait to see what comes out of this MM update.

tx_dbs_tx said:
You must have done something wrong. When you flash the rom it will automatically add root binaries and supersu.
Click to expand...
Click to collapse
Maybe he misunderstood, and accepted TWRP's offer to root the rom?
Sent from my SM-N910P using XDA Free mobile app

tx_dbs_tx said:
You must have done something wrong. When you flash the rom it will automatically add root binaries and supersu.
Look in the Note 4 general forum. User "Sunderwear" posted the PC1 tar in a general thread.
Click to expand...
Click to collapse
Didn't for me, I followed it to the letter T but it's all good, using the older root worked fine installing the binaries from the recovery.
---------- Post added at 11:48 PM ---------- Previous post was at 11:47 PM ----------
styles420 said:
Maybe he misunderstood, and accepted TWRP's offer to root the rom?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
LOL nope, I've been doing this since ICS. I know how to follow directions

couple questions
1. has anyone confirmed xposed working with deodex?
2. can anyone confirm or deny PC1 compatibility with PB5 engineering bootloader? I don't have easy access to a computer and won't for several days
3. if coming from PB5 will this wipe my internal sdcard again?

This rom has language similar to Vietnam darling note 5 not? I am Vietnamese!
Add language vietnam to rom. Thank pro )

QF1 Recommended thread/instructions for unlock bootloader/root/lollipop

I've been going through the learning curve on rooting/custom ROM/etc. This will be my first time to go through this process. I have the QF1 firmware and the latest version for Sprint Samsung Galaxy Note 4:
Software Version: N910PVPS4DQF1
Hardware Version: N910P.05
Model: SM-N910P
Android 6.0.1
security patch level: June 1, 2017
I tried calling Sprint to unlock my bootloader, but they thought I was asking to unlock the device. Finally, I got to their tech support and they said they didn't do that, and the guy recommended watching a video on YouTube.
It seems that sometimes the instructions you follow need to be oriented towards the version you have. Would anyone be able to point me to the best instructions to follow?
there seems to be a lot of contradicting information, so I thought some general direction to point me off in the right direction would save me a lot of grief in the long run
My thought was to:
1. unlock boot loader
2. using Odin flash a ROM with Lollipop for the Sprint Note 4, maybe the Omega one?
3. depending on the ROM in #2, then I could automatically get root?

Bootloader on Sprint Note 4 is unlocked already.
Custom ROMs usually include root or alternate methods.
Depending on the ROM you choose and as long as it's OG5 and above, it's recommended to use Odin to flash the stock tar that corresponds to the update that the ROM is based on. Otherwise, you may lose compatibility, network connectivity or camera focus.
Edit: you can find stock tar downloads in a thread for Sprint Note 4 in the general forum. Latest recommended Odin can be found in post 1 or 2 of that thread.
I'm not sure what ROM you're referring to but clean install is best practice for ported ROMs or switching between Android versions or switching to and from CM to stock based ROMs. Data may not be compatible so backing up internal memory keepsakes and wiping internal memory may be necessary, where recommended.
That's the general idea but best to follow OP of the ROM you choose.
Sent from my SM-N920P using Tapatalk

How would I go about making my own Custom Rom? I'm thinking of adjusting the Resurrection Remix So it would work on my phone but the specific ROM is on Verizon verison of the Note 4 and I want to port that for my Version for Sprint I know I can change some CSC stuff to get the modems and carriers ready for no signal loss or mobile data or sms issues as I have seen a method for flashing a zip file, but I;m just really curious, as I hope I can rebuild LineAgoe or CM for this Note 4 as I have a lot of time and alot of learning to do.

rayel said:
I've been going through the learning curve on rooting/custom ROM/etc. This will be my first time to go through this process.
Click to expand...
Click to collapse
To add to samep's comment. Here's a few pointers, in no particular order.
1. You only use Odin on PC to flash stock firmware. Or Twrp recovery.
2. Once you have Twrp recovery, then everything else is done through it.
3. Your very important first thing to do, once you flash Twrp. In Twrp, make a full backup of your phone, especially your EFS partition. Keep in safe place.
And if you want to be even more safe, backup your efs every time you upgrade your firmware.
4. READ, READ, READ! Google is your friend. If learning something risky and new, read from a few different sources, make sure it adds up!
GOOD LUCK!
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
IAmTechFreq said:
How would I go about making my own Custom Rom? I'm thinking of adjusting the Resurrection Remix So it would work on my phone but the specific ROM is on Verizon verison of the Note 4 and I want to port that for my Version for Sprint I know I can change some CSC stuff to get the modems and carriers ready for no signal loss or mobile data or sms issues as I have seen a method for flashing a zip file, but I;m just really curious, as I hope I can rebuild LineAgoe or CM for this Note 4 as I have a lot of time and alot of learning to do.
Click to expand...
Click to collapse
This cannot be taught in a response.
If your serious about learning then....
Lots and lots of reading, then try smaller stuff first. And work your way up.

aaron74 said:
To add to samep's comment. Here's a few pointers, in no particular order.
1. You only use Odin on PC to flash stock firmware. Or Twrp recovery.
2. Once you have Twrp recovery, then everything else is done through it.
3. Your very important first thing to do, once you flash Twrp. In Twrp, make a full backup of your phone, especially your EFS partition. Keep in safe place.
And if you want to be even more safe, backup your efs every time you upgrade your firmware.
4. READ, READ, READ! Google is your friend. If learning something risky and new, read from a few different sources, make sure it adds up!
GOOD LUCK!
Click to expand...
Click to collapse
Thank you aaron74! Question, would it be better to install Twrp using Odin, backup (w/EFS partition), then downgrade to stock Lollipop using TWRP? Or would the original order Odin > stock Lollipop > TWRP > backup > root be just as good?

rayel said:
Thank you aaron74! Question, would it be better to install Twrp using Odin, backup (w/EFS partition), then downgrade to stock Lollipop using TWRP? Or would the original order Odin > stock Lollipop > TWRP > backup > root be just as good?
Click to expand...
Click to collapse
I don't think you can downgrade from within Twrp.
But it's definitely safer to install twrp and get your EFS backup first. Just in case. It's extra step but you have your EFS, in case something goes wrong with downgrade. I'm not very knowledge on the downgrade process, never done it.