Database Users

[GUIDE] How to Root Note 5 I EFS Backup I Xposed I Deep sleep Fix I Updated

FOR TEMPORARILY USE THIS METHOD TO ROOT NOTE 5 running on NOUGAT
PS : Running version of SuperSU will not work, once It will be updated use below said method
-------------------------------------------------------------------------------------------------------------- For Marshmallow and lower use below method-------------------------
I have seen many users still have no proper information about rooting SM-N920* (Galaxy Note 5)
Here Steps to root your Note 5. Since there are major changes in policy to root device here I am updating this guide in favor of newbies to make it simple as possible.
Before you proceed to root, you should know some facts like we need to have custom kernel as of now to root device (This is no more compulsory as Systemless root like Supersu 2.60+ can root device on stock kernel. Read below.). Also we have bootloader protection to flash anything but that can be unlock (read below). Also to note that rooting your device warranty voids (permanently) apart from warranty if you want to unroot device after rooting it once, you may have deep sleep bug. Read Deep Sleep issue on stock non rooted ROM at end of this post.
Need to know before rooting Note 5.
Here I am making two parts for two different method to root your Note5. Before proceeding you have to device which way you want to root as mixing both method may mess up your system and ultimately you may need to reflash stock ROM.
Before starting step just to explain what is difference between both the methods of root.
Method 1: Systemless root.
Systemless root is recently provided by @Chainfire for our device.
Major advantage is you can simply flash same zip (superSu 2.60 and up) to any Note5 variant without any dependencies on kernel for your device.
As Systemless root is still beta and may be we will get stable version very soon but most of root stuff working fine as it should with beta version too. Edit : It seems Systemless root is almost stable now.
Systemless root can be achieved by two methods
1A. - Flashing SuperSU from custom recovery.This is two step procedure. First flash custom recovery and second Flash SuperSu zip Advantage of this method over 1B (below) is you will have custom recovery and helpful to make nandroid backup OR flashing other recoveries.
1B - Flashing with Odin - Flashing root package with Odin. Single step root. Easiest method.
Method 2 : Using prerooted kernel. With prerooted kernel you can root your device in single step even without having custom recovery. This is true in case of your kernel is having prerooted script and available in tar version. I will provide example below in guide which kernel have this.
There is no any issue using this method but you must have to find correct kernel for your device.
Click to expand...
Click to collapse
How to root Note 5
Method 1 (systemless root) Again there are two method for Systemless root and you can go with either of it.
Method 1A - Systemless root by flashing SuperSU zip
You will require custom recovery to use this method. Here are steps for how to install custom recovery as well how to root.
1.Unlock Flashing
Go to settings-about device-Software info - You will see "build number" - Tap repeatedly on build number to unlock development option
Now you will see Development option in setting (just above about device)
Open Development option - OEM Unlock - Enable it.
2.get custom Recovery.
Download TWRP by @bigbiff according your variant. Here select tar version of file NOT zip
OR
Philz CWM. Philz recovery is ported for Note 5 by @arter97 and you can download from his web page. - Here look to latest build and select your device model. for example your variant is N920I you have to open n920ci (this indicate n920c and n920i) and download Philz recovery with file name ending tar.md5 (not zip)
3A.Flash custom recovery.
Use Odin V3_10.7 to flash downloaded recovery
Switch off device
Reboot to download mode (Vol down+power+home)
Select downloaded above said custom recovery with AP tab of Odin and flash.
when TWRP prompts asking to "keep read only" or to "allow modifications", select the option to "Keep Read-Only." (Phil's CWM doesn't give the option to keep it read-only.) As well, _if_ TWRP/Philz offers to install root - DO NOT LET IT (as it's not compatible with systemless root.)
Reboot to recovery and now you should have custom recovery.
In case still you have stock recovery then follow this
Again reboot to download mode
Select recovery file with AP tab of Odin
Now uncheck Auto reboot option
Flash selected file
Once flashing complete, disconnect device and long press Vol down+Power
Once screen turns off, immediately press vol up+power+home to reboot to recovery manually.
3B : This step is only for those who want to use Android Pay otherwise you can jump to Step 4 directly.
A completely stock system with the systemless root installed will NOT, by default, work with Android Pay. To make it work with android pay, the following command should be run from a shell prompt on the device (while the device is in TWRP, but before installing superSU.) This is easier to do via 'adb shell', but could, I guess, be done from within TWRP itself (advanced->terminal command)
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
4.Root with Systemless root.
Once you have custom recovery on your device then simply download Systemless superSu zip and flash from recovery that's it.
Here is link for Systemless root Big Thanks to @Chainfire
You have to download latest version of it.
Click to expand...
Click to collapse
Once it is done, you will see SuperSU app on your drawer and your device is rooted now.
Method 1B - Systemless root by Odin (CF Auto Root)
Click to expand...
Click to collapse
This is easiest way to root Note 5
Download required files from CF Auto root download page. Simple search your device ID e.g. N920I. If you see your device model is listed then you can see download option beside of your device ID in table.
Download according your device ID and extract it. You will get Odin and one *.tar.md file.
Before starting unlock bootloader
1.Go to settings-about device-Software info - You will see "build number" - Tap repeatedly on build number to unlock development option
Now you will see Development option in setting (just above about device)
Open Development option - OEM Unlock - Enable it.
2.Reboot device to download mode (switch off device then Vol down+power+home)
3.Open Odin on PC
4.Select that *tar.md5 file for AP (PDA) tab of odin
5.Connect device to PC and wait till color change for com port (successfully connected device) and select 'Start' to flash
Once flash finish, disconnect device and reboot. You will have rooted device now.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Method 2: Flashing Prerooted Custom kernel.
Basically you can install any prerooted kernel with odin or with custom recovery but here i will show a example which can be done in single step
1.Download prerooted odin flashable (in .tar.md5 format)
Example : Get Skyhigh kernel by @UpInTheAir
here is Original thread by him
Look to post #2 of that thread and under Download section you will find many version of kernel. You have to download one which is for your variant as well available as odin flashable.
As of today available versions are
[Odin3 v3.10.6] SM-N920-C / CD / G / I [ v3.4 ] - which same for following devices like N920C N920G N920I N920CD
[Odin3 v3.10.6] SM-N9200 [ v3.4 ] - For N9200
[Odin3 v3.10.6] SM-N9208_SEA [ v3.4 ] - For N9208
2.Flash Downloaded file with Odin
Use Odin V3_10.7 to flash downloaded kernel
Switch off device
Reboot to download mode (Vol down+power+home)
Select downloaded kernel file with AP tab of Odin and flash.
Device will auto reboot and you can see kernel info in Setting-Device info. Also on successfull flashing you will see SuperSU app on your drawer.
If you don't find any version available for your variant, you can simply make request to OP on kernel thread OR Use Systemless root meanwhile.
PS : As said above you can use any custom kernel by any developer but keep in mind that if kernel is not Odin flashable then you need to flash custom recovery first and if not prerooted then flash Supersu recommended by kernel developer. I have make example is based on just easiest way to flash i found.
Click to expand...
Click to collapse
IMPORTANT
Here is end of how to root note 5. Read below some miscellaneous discussion.
- There may be issue with DRM protected videos (like Netflix). You can fix with this.
- Now DON'T FORGET TO MAKE EFS (IMEI) BACKUP
- Xposed on Note 5
Deep sleep issue. - THIS IS FIXED AFTER SuperSu 2.67
If your device doesn't go to deep sleep after root. commonly reported after rooting with stock kernel (systemless root)
How to know deep sleep issue : Main symptom of deep sleep bug is fast draining battery. You can confirm if your device has this issue or not by using batterbattery stat or any similar app.
After installing BBS keep device idle for sometime and see other profile and check your device record deep sleep? If you don't have deep sleep recorded then you need fix. Here is screenshot of deepsleep record.
Deep Sleep Issue on stock non rooted device:
This is classically happens when you root device/flash custom kernel/recovery/ROM and later revert to stock ROM. Now even you have non rooted device with pure stock ROM, your device won't enter to deep sleep. Basically this is not a bug but poor policy and samsung don't care to address this issue as if you use device as per samsung suggests (without tripping knox) there will be no issue. Again solution is root your device and apply deep sleep fix / any kernel/ROM which have bio;t in deep sleep fix.
How to Fix :
You can try this to fix Deep sleep issue.
Click to expand...
Click to collapse
Big Thanks and credit goes to @Chainfire
Thanks and credit to @garyd9 for all the helps to users and providing lots good information.
.

Reserved

Reserved 3

Rsereved 4

Last
I will add some more important information later

Last
I will add some more important information later

Mod Edit
Thread stuck
:good:
malybru
Forum Moderator

Perfect guide
Sent from my SM-N920C using XDA Free mobile app

Great info.
Maybe add a warning that it's not for 920A (ATT) or 920V (Verizon).

I've read that currently there is reboot issues with that kernels. Which one from the 3 versions is the most stable?
Sent from my SM-N920C using XDA Free mobile app

juliano76 said:
I've read that currently there is reboot issues with that kernels. Which one from the 3 versions is the most stable?
Sent from my SM-N920C using XDA Free mobile app
Click to expand...
Click to collapse
Let's keep this thread on the track only and don't make kernel discussing thread. All developers are working hard and it's insulting to say this one is better. For A - may be kernel X is better and for B - may be kernel Y is better, moreover it's subjective and you have to find yourself which one is best for you. Purpose of guide is how to root and I am pretty sure using any of mention kernel will do job. If you are not happy with your kernel you can change anytime OR may you can seek assistance from kernel thread.
Hope this make clear.

What about this root method? It seems so easy!
https://www.androidroot.us.com/how-to-root-samsung-note-5/
Sent from my SM-N920C using XDA Free mobile app

Dr. Ketan what is the version of Note 5 we will be getting from tomorrow in India ? Is it 920i or 920c ? whats the difference ?

N920G for India nothing great just the difference of the awesome naming trend of Samsung

Thanks you DR. KETAN!
This is really a huge help and put my mind at ease! Again, many THANKS.
Quick question... Once I root and install custom recovery can I install any note 5 rom? I have the n920i. Reason I ask is I would like to try a few n920T roms and was wondering if there would be any issues or negatives?

how to root indian SM-N920G .?
none of the kernels seem to support ..
---------- Post added at 03:05 PM ---------- Previous post was at 03:05 PM ----------
how to root indian SM-N920G .?
none of the kernels seem to support ..

stu5797 said:
Thanks you DR. KETAN!
This is really a huge help and put my mind at ease! Again, many THANKS.
Quick question... Once I root and install custom recovery can I install any note 5 rom? I have the n920i. Reason I ask is I would like to try a few n920T roms and was wondering if there would be any issues or negatives?
Click to expand...
Click to collapse
Not all but some variant can share same ROM like n920i and n920c
For tmobile, they need to flash call audio fix to use international rom so same way if you flash n920t rom may you get some bug. Yet I haven't read if anyone reported his/her experience regarding this, you can try yourself.
daviefl86 said:
how to root indian SM-N920G .?
none of the kernels seem to support ..
---------- Post added at 03:05 PM ---------- Previous post was at 03:05 PM ----------
how to root indian SM-N920G .?
none of the kernels seem to support ..
Click to expand...
Click to collapse
Either you can try n920c/i or can make request to kernel developer to add support to your device
Sent from my SM-N920I using xda premium

I currently have the SM-N9208 (Duos) version of the Note5. Would I be able to use this method to root it too?

Hi Dr. Ketan...
Just want to know what are the future possiblities of Rom Development for model no. SM-N920G which is being distributed in India rite now... are the roms/kernels going to be model specific or universal for models other than Sprint/verizon etc...!!
With so many models coming up , its going to be quite confusing for both developers and users i guess.... !!!!

There are possibilities there n920i/c model rom kernel may work on n910g. If not then you have to request developer for kernel. I may consider to add support for rom if there is no support for n910g and sufficient users available.
Sent from my SM-N920I using xda premium

Root for SM T237P 5.1.1 ???

As the title suggests, I am hoping someone can point toward the process of rooting this tab on stock 5.1.1 ota update. Every search turns up the process to root kitkat (which does pass Odin but did not root it.)but that didn't work on lollipop, and I can't seem to get TWRP to flash, for me at least. Is it KNOX stopping me maybe? I'm lost, Any help would be appreciated, I usually get by fine as long as I follow instructions.

sprint T237P WITH LOLLIPOP 5.1.1 (Need root)
.Sprint T237P 5.1.1 ota running philz recovery (Needs Root)
Hi , I had my device rooted and had philz touch 6.5 plus pure performance stock (which is another link in xda for the 4.4.2 root) on my tablet before I got the 5.1.1 upgrade on Sept 30 2015. I got the 5.1.1 upgrade the other day and I flashed philz touch recovery back onto my tablet it works perfectly and I installed pure performance on my tablet also with philz touch recovery runs good , now all I need is root for the 5.1.1 sprint T237P. Is anyone working on root for 5.1.1 for the t237p or can someone tell me anything all the hard work is appreciated. There is a link in XDA for philz touch recovery i don't know it offhand it is where i got mine... I wanted to add zip file of philz touch but don't see a way to add or attach file either...Anybody with information though on root for T237P 5.1.1 Please Post....Thanks
---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------
Quote:
Originally Posted by DavidBeckett.db
Hi , I had my device rooted and had philz touch 6.5 plus pure performance stock (which is another link in xda for the 4.4.2 root) on my tablet before I got the 5.1.1 upgrade on Sept 30 2015. I got the 5.1.1 upgrade the other day and I flashed philz touch recovery back onto my tablet it works perfectly and I installed pure performance on my tablet also with philz touch recovery runs good , now all I need is root for the 5.1.1 sprint T237P. Is anyone working on root for 5.1.1 for the t237p or can someone tell me anything all the hard work is appreciated. There is a link in XDA for philz touch recovery i don't know it offhand it is where i got mine... I wanted to add zip file of philz touch but don't see a way to add or attach file either...Anybody with information though on root for T237P 5.1.1 Please Post....Thanks
SM-T237p Philz 6.59 [QCOM/MSM] Thanks @hookem2oo7 for testing.
https://www.androidfilehost.com/?fid=95916177934549969

jayare313 said:
As the title suggests, I am hoping someone can point toward the process of rooting this tab on stock 5.1.1 ota update.
Click to expand...
Click to collapse
DavidBeckett.db said:
Anybody with information though on root for T237P 5.1.1 Please Post....Thanks
Click to expand...
Click to collapse
Alright here's my two cents worth. Going off what I saw from the 8.0 models, because you've got lollipop 5.1.1 and not 5.0.x, you cannot just root by flashing Philz and then in Philz flashing the superSU zip like usual. There is something new in the security measures of the 5.1.1 kernel that causes a boot loop if you try this. I say this because the 10.1 models, which got 5.0.2, could root like I just described but the 8.0 models, which got 5.1.1, could not.
Therefore, it seems that someone will have to make a modified rootable kernel, in a similar manner to what moonbutt74 did for the 8.0 models. Check out his thread here to see what I mean

T237P on 5.1.1
Hi, I wrote yesterday that i flashed philz touch recovery and pure performance to my tab 4 T237P which they worked good...Well today I flashed KitKat 4.4.2 back to the T237P and then updated back to Lollipop 5.1.1 OTA I am just going to be patient until I find out if someone comes up with a Root for the device a new kernel or Whatever it will much so be worth the wait...Moonbutt74 did it before for the T237P for root on kitkat so either he or someone else will come up with a good method for root on T237P using 5.1.1 Thanks to all...

Try Kingroot?
I am glad that you confirmed that Philz recovery at least installs and you can flash back to stock 4.4.2! Have you tried King root? I was thinking about trying King root first then replacing their custom recovery with ours if needed. Then we hope that recovery works correctly...

@jayare313 @DavidBeckett.db @thisisapoorusernamechoice
hi guys, can one of you upload and post the LP 5.1.1 release's boot.img to a site i can access, and also provide a listing of
/system/lib/modules
and as well provide the block device number for boot/kernel for this device? Meaning /dev/block/mmcblk0p??
While the kernel's for the sm-t33x "s work because i have an sm-t330nu to test, I DO NOT have an sm-t237p BUTTCHEEKS, because it's qcom/msm the leap shouldn't be too far. I already have a test defconfig and build using my working source for the sm-t53x/33x. I am interested in seeing if the sm-t237p/230nt etc. can also be supported from that source.
m

I have the 237p running 5.1.1 id be willing to upload your request Moonbutt if i knew how, would love to root this device and get its full potential back in play any instructions
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
moonbutt74 said:
@jayare313 @DavidBeckett.db @thisisapoorusernamechoice
hi guys, can one of you upload and post the LP 5.1.1 release's boot.img to a site i can access, and also provide a listing of
/system/lib/modules
and as well provide the block device number for boot/kernel for this device? Meaning /dev/block/mmcblk0p??
While the kernel's for the sm-t33x "s work because i have an sm-t330nu to test, I DO NOT have an sm-t237p BUTTCHEEKS, because it's qcom/msm the leap shouldn't be too far. I already have a test defconfig and build using my working source for the sm-t53x/33x. I am interested in seeing if the sm-t237p/230nt etc. can also be supported from that source.
m
Click to expand...
Click to collapse
Enlighten me so i may assist i have the 237 p on 5.1.1.

I pm'd him and he's moved on and I don't fault him for that. I also pm'd Kruser who rooted 442, just wish there was a simple guide. I don't have a ton of time to devote, but would gladly put up a bounty for it.
Bluheven14760 said:
I have the 237p running 5.1.1 id be willing to upload your request Moonbutt if i knew how, would love to root this device and get its full potential back in play any instructions
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
Enlighten me so i may assist i have the 237 p on 5.1.1.
Click to expand...
Click to collapse

I too would love the 5.1.1 to be rooted. I need UVC video on the tablet via otg.

Kingroot and Supersu_me works... almost! Also captured 5.1.1 update.zip
I successfully rooted my SM-T237p with King root and then supersu_me. The only problem is once you reboot the device it goes into a boot loop mode. Check out the entire process... https://www.youtube.com/watch?v=d8fAA4uTwuc
I ODIN to stock 4.4.2 to fix it. I also captured the update.zip from the /data/fota folder for the 5.1.1 OTA but it is encrypted... I can upload it if it would be helpful. Any way to unzip it?

K94U said:
update.zip from the /data/fota folder for the 5.1.1 OTA but it is encrypted... I can upload it if it would be helpful. Any way to unzip it?
Click to expand...
Click to collapse
Upload the zip

Here is the download link... http://www.filedropper.com/sm-t237pota511
Let me know how else I can help. Is there anything I can do if I root 511 again? And pull some files?

Works but nothing sticks...
I'm currently rooted on 5.1.1 with a working Philz recovery nandroid backup. everything works great except nothing sticks. Recovery is over written immediately on boot and su makes the os boot loop if the device is restarted. To restore, I flash Philz recovery in ODIN then boot recovery and restore or do a new backup. I'll try to get Moonbutt74 the files and info soon. What is the easiest way to fix this?

moonbutt74 said:
hi guys, can one of you upload and post the LP 5.1.1 release's boot.img to a site i can access, and also provide a listing of
/system/lib/modules
and as well provide the block device number for boot/kernel for this device? Meaning /dev/block/mmcblk0p??
While the kernel's for the sm-t33x "s work because i have an sm-t330nu to test, I DO NOT have an sm-t237p BUTTCHEEKS, because it's qcom/msm the leap shouldn't be too far. I already have a test defconfig and build using my working source for the sm-t53x/33x. I am interested in seeing if the sm-t237p/230nt etc. can also be supported from that source.
m
Click to expand...
Click to collapse
Here are the files... How do I determine the block/device boot/kernel info? There are many mmcblk0p...
http://www.filedropper.com/sm-t237poh7
Update, I rebooted to try some other stuff and it actually restarted and kept su. Then I reinstalled recovery and it stuck! I think I might have used the root option in recovery and then apply the updated su 2.52

All working perfect!!!
So, it seems that I had to whip this device into permissive mode by working it from both ends, hahaha... the Kingroot and supersu me method makes it boot loop but then you need to install PhilZ recovery and install from that side also. The first thing to do is install PhilZ recovery and immediately reboot into recovery and do a nandroid backup! Make sure you have enough memory internal or sd... Full backup is 4+ gigs!!! Then experiment away... This DOES TRIP KNOX!... Here is a little video for you all. Experiment at your own risk!!
https://youtu.be/kzOYB7l5XLo
PhilZ recovery: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
SuperSU 2.52: http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
Special update... It seems Chainfire has developed SuperSU 2.60 that has a special non-system mod root available!!! Anybody willing to install PhilZ on a stock OH7 and flash this new SU??? I think it might work... Just nandroid backup first! This is a special SU that MUST be installed on stock boot and kernel! Do NOT update your current SU with this version!
SuperSU 2.60: http://forum.xda-developers.com/attachment.php?attachmentid=3565977&d=1449330539

I restored my nandroid backup in recovery just to try this new Supersu on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... Su2.61 was just released. It works for mostly ALL Samsung and Nexus devices now... Read more:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
SuperSU 2.61 video: https://www.youtube.com/watch?v=03dBX7c2yiY

OK, just got my sm-t237p on 5.1.1, and philz recovery is loaded, @moonbutt74 are you still willing to help with root, i can upload partitions as needed... I'm here to help anyway i can...

fiddy619 said:
OK, just got my sm-t237p on 5.1.1, and philz recovery is loaded, @moonbutt74 are you still willing to help with root, i can upload partitions as needed... I'm here to help anyway i can...
Click to expand...
Click to collapse
f,
hi, this is what i need
reboot to recovery and connect via adb and run the following
adb shell
parted /dev/block/mmcblk0
print all
q
post that output.
and upload your current boot.img [lp 5.1]
in regular operation run in terminal
cat /proc/partitions
ls /system/lib/modules/
post that output
goto device setting about and post that screenshot, i need the build number for the rom/kerne/build id
There is currently no LL kernel source release for the sm-t237p and i will need to make a source request and that
is the information i require.
m

@moonbutt74 All requested has been uploaded, I had to compress the boot.img file using 7zip to allow to be uploaded due to 8MB limit, but just extract, and should be good... If you need anything else, just let me know...

A quick update, i can't get Philz recovery to stick, i have to re odin every time i want to get to recovery, I'm kinda new to odin, i've mainly been on htc, and lg devices, concepts all still the same just methods are a bit different to get to the same outcome. Is there a trick to get philz to stick, so i don't have to keep using odin?

[Guide] New and Easiest method for root ALL Galaxy S5 Mini (G800) on Lollipop 5.1.1

BETA: All this is still in testing!
Jump to:
- ODIN flashable devices
- Fastboot flashable devices
REQUESTS AND DISCUSSION
The central CF-Auto-Root thread can be found here on XDA-Developers.com. Use that thread for requests for new roots and generic discussion. Most device models have their own dedicated threads on XDA, please keep discussion about those specific models in that dedicated thread, and don't litter the central thread with them.
NO REDISTRIBUTION
Please link directly to this page, or use the link you find in the table below.
NO WARRANTY
Use at your own risk, I'm not responsible for bricking your device.
GET THE RIGHT FILE
Make sure you get the correct file. Using the incorrect file may brick your device.
FLASH COUNTER
If your target device has a custom firmware flash counter, CF-Auto-Root will trigger it. If you're lucky, Triangle Away has support for your device and can be used to reset the counter.
KNOX WARRANTY
If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status !
ENCRYPTION
Warning: If your device storage is encrypted, using CF-Auto-Root will wipe your data !
ANDROID VERSION
When newer firmwares are released for a certain device, sometimes that firmware includes new bootloaders that prevent kernels based on the old firmwares from booting. This usually coincides with a transition to a newer Android version. In that case, the CF-Auto-Root for download here may no longer work - flashing or booting might fail. It is too much work for me to keep track of all these firmwares, so if you encounter this issue, it is up to you to submit the recovery.img file from the latest firmware for your device to the CF-Auto-Root thread on XDA-Developers.com.
To be clear, just because you have a newer Android version than listed here, does NOT mean the CF-Auto-Root will not work - there's a good chance that it will!
How 2 falsh it?
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Files 4 rooting!
SM-G800H: https://download.chainfire.eu/524/CF-Root1/CF-Auto-Root-kmini3g-kmini3gxx-smg800h.zip?retrieve_file=1
SM-G800F: https://download.chainfire.eu/523/CF-Root1/CF-Auto-Root-kminilte-kminiltexx-smg800f.zip?retrieve_file=1
SM-G800R4: https://download.chainfire.eu/676/CF-Root1/CF-Auto-Root-kminilteusc-kminilteusc-smg800r4.zip?retrieve_file=1
SM-G800M: https://download.chainfire.eu/525/CF-Root1/CF-Auto-Root-kminilte-kminilteub-smg800m.zip?retrieve_file=1
SM-G800Y: https://download.chainfire.eu/526/CF-Root1/CF-Auto-Root-kminilte-kminiltedv-smg800y.zip?retrieve_file=1
If I helped Don't Forget click on thanks botton. :good: :good:
Source: autoroot.chainfire.eu

Reserved!

Reserved

No superSu Binary.
failed installation.
Brick on G-800M Lollipop.
---------- Post added at 12:32 PM ---------- Previous post was at 12:20 PM ----------
hekintools said:
No superSu Binary.
failed installation.
Brick on G-800M Lollipop.
Click to expand...
Click to collapse
thanks you.
I could already make root

hekintools said:
No superSu Binary.
failed installation.
Brick on G-800M Lollipop.
---------- Post added at 12:32 PM ---------- Previous post was at 12:20 PM ----------
thanks you.
I could already make root
Click to expand...
Click to collapse
It didn't Worked?
<<<<<<<<<Besure you uninstalled the security policy updates>>>>>>
Did you uninstall the security policy and security agent and the knox and knox II and reinstall the supersu to 2.65?
Did your phone soft bricked?

Works for G800H on Lillipop 5.1.1 100% tested
If U do the the ways correctlly.

Hi, all!
In my case, after flash all works fine, after open SuperSU and trying to update the binaries an error message appears. BUT when try to do something as root... works!

pouriasa said:
It didn't Worked?
<<<<<<<<<Besure you uninstalled the security policy updates>>>>>>
Did you uninstall the security policy and security agent and the knox and knox II and reinstall the supersu to 2.65?
Did your phone soft bricked?
Click to expand...
Click to collapse
100% work.
In G800m

pouriasa said:
It didn't Worked?
<<<<<<<<<Besure you uninstalled the security policy updates>>>>>>
Did you uninstall the security policy and security agent and the knox and knox II and reinstall the supersu to 2.65?
Click to expand...
Click to collapse
no, how i can do?

hi i have tested it on g800h and it works just fine.
Root is holding since 2 days and im doing a heavy testing with a lot of applications. I will keep u posted in case anything wrong will happen.
Thank as i was waiting for a new root method since a long time.
Best regards,

SeedViciouZ said:
no, how i can do?
Click to expand...
Click to collapse
Before you root you should factory reset your phone then go to the about phone and click on the system update to register your device.
OR
Go to the application manager and uninstall the security policy update if there is this option.
2-flash the file to your phone (CF-auto root) and (do not connect to the internet) download the uninstaller pro and uninstall knox and knox ll and security policy and security agent now the root is safe.
(If the supersu said: There is no supersu binary flash the cf auto again to uninstall those apps)

SeedViciouZ said:
Hi, all!
In my case, after flash all works fine, after open SuperSU and trying to update the binaries an error message appears. BUT when try to do something as root... works!
Click to expand...
Click to collapse
When it said update the binary click on cancel and go to the supersu setting and click on the reinstall now go and install the supersu 2.65 apk. That's done!

hekintools said:
100% work.
In G800m
Click to expand...
Click to collapse
Thanks for your feedback. :good:

zatrzask said:
hi i have tested it on g800h and it works just fine.
Root is holding since 2 days and im doing a heavy testing with a lot of applications. I will keep u posted in case anything wrong will happen.
Thank as i was waiting for a new root method since a long time.
Best regards,
Click to expand...
Click to collapse
Your Welcome man.
Thanks for your feedback.

I use unbranded Lollipop 5.1..1. on G800F. After flashing root I ended up at bootloop.
Could not get rid of it despite cache wipe/factory reset. Tried 3 times, same result.
Is there a way to get rif of bootloop to have root on G800F?

For g800h files is for 4.4.2 not for 5.1.1, do not flash this files with lollipop you brick phone

kowalwalcz said:
For g800h files is for 4.4.2 not for 5.1.1, do not flash this files with lollipop you brick phone
Click to expand...
Click to collapse
No it works on lp I tested it. And it's impossible to brick your phone.

AT-Mio said:
I use unbranded Lollipop 5.1..1. on G800F. After flashing root I ended up at bootloop.
Could not get rid of it despite cache wipe/factory reset. Tried 3 times, same result.
Is there a way to get rif of bootloop to have root on G800F?
Click to expand...
Click to collapse
U mean U use custome ROM?

pouriasa said:
U mean U use custome ROM?
Click to expand...
Click to collapse
No, I have used original Cyprus ROM and flashed hidden.img following these instructions:
First of all install Samsung usb drivers http://developer.samsung.com/technic...000000117#none (probably dont need if you have kies installed)
Make sure you have SM-G800F, download http://www.sammobile.com/firmwares/d...FVFG1BOL1_CYV/
Extract (unzip) the firmware file
Download Odin v3.10.7 - http://dl.sammobile.com/Odin3_v3.10.7.zip
Extract Odin ZIP file
Open Odin v3.10.7
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
If you have problems with hidden.img during flash, then:
Remove usb cable and battery,
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Add PIT file: https://www.androidfilehost.com/?fid=24369303960685133 (re-partition option will tick automatically, is ok)
Click the start button, sit back and wait few minutes
Done.

pouriasa said:
Before you root you should factory reset your phone then go to the about phone and click on the system update to register your device.
OR
Go to the application manager and uninstall the security policy update if there is this option.
2-flash the file to your phone (CF-auto root) and (do not connect to the internet) download the uninstaller pro and uninstall knox and knox ll and security policy and security agent now the root is safe.
(If the supersu said: There is no supersu binary flash the cf auto again to uninstall those apps)
Click to expand...
Click to collapse
Excuse my delay, after uninstall de security updates, all works fine. :good:

stock_N910VVZW2CPG2_VZW updated with FlashFire, Rooted

This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPG2_N910VVZW2CPG2_N910VVRU2CPG2_HOME.tar
( ! System and Cache only ! )
SAME as the thread Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910V
Except Now that SamMobile has posted 2CPG2 I was able to skip steps and go straight to Flashing the firmware package with FlashFire.
No need to do over the air updates.
-----------------------------------------------------------------------------------------------
Note: I was able to skip the recommended rooting of 5.1.1
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.

I have been flashing and playing with roms on many devices and there is something I don't understand. Why can't someone inject root into the factory tar file and make the upgrade a much simpler process? If our devices once rooted are considered the same as a developer edition, why can't we simply flash whatever image we want?

PaulPizzRom is just as good......
tbtaf said:
I have been flashing and playing with roms on many devices and there is something I don't understand. Why can't someone inject root into the factory tar file and make the upgrade a much simpler process? If our devices once rooted are considered the same as a developer edition, why can't we simply flash whatever image we want?
Click to expand...
Click to collapse
OR BETTER!!!!!!

Think you could fix your 'HERE' links in your OP?
hsbadr's CPD1 is already rooted or something? I just re-went through the unlock process and i thought if you flashed a stock firmware it re-locked the bootloader?

azreark1 said:
Think you could fix your 'HERE' links in your OP?
hsbadr's CPD1 is already rooted or something? I just re-went through the unlock process and i thought if you flashed a stock firmware it re-locked the bootloader?
Click to expand...
Click to collapse
Chick on the link in OP
Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910
That's all I got right now

I am in : [ROM] [5.1.1] Kyubi Note 5 Port Final [N910VVRU2BPA1] [2/23/16]
Can i flash stock rom 5.1.1 by flashfire?

Could someone please upload the ota zip file only

I'm on 5.1.1 PA1/PD1 with TWRP installed and would love to move to 6.0...would I have to start all over to accomplish this or could I begin in the middle of your guide where I am?
thanks!!
Nevermind..I'm on 6.0

Many thanks!

mistake
Posted too soon. Need to delete and repost later with more info

[Guide] Rooting G800F on Marshmallow 6.0.1 + getting Xposed framework

UPDATE 14.05.2017: Chainfire has released autoroot for Galaxy S5 Mini G800F based on firmware 6.0.1. It can be downloaded from the official CF Autoroot website (direct link to the G800F file). It is by far the easiest and fastest method for getting root access on your device without the need for TWRP.
Procedure for rooting with CF autoroot:
1. Charge your S5 Mini's battery to at least 80% and make sure you have Samsung USB drivers installed on your PC
2. Enable USB debugging on the S5 Mini
3. Download the CF autoroot file from the link above and unpack the zip archive
4. Open ODIN as administrator (right click -> Run as administrator)
5. Put the S5 Mini in download mode and connect it via USB cable to the PC
6. After ODIN recognizes the device, click "AP" and select the autoroot file
7. Click "Start" and wait for the process to finish - shouldn't take more than a few seconds
8. When the log in ODIN says "Disconnected", unplug the USB cable from the phone and wait for it to restart itself
9. Verify proper root with a tool like Root Checker
If you want to have TWRP recovery and Xposed framework, use the guide below.
This method applies only to the S5 Mini G800F variant running Android 6.0.1. Trying this on other variants may result in bricking your device. I used this procedure to get root access and Xposed working on my European S5 Mini G800F using a German (DBT) Marshmallow firmware. Use at your own risk, I'm not responsible for anything that happens to your device. Note that this procedure voids your warranty. This guide assumes that you already have TWRP recovery or know how to flash it.
Backup everything important like contacts and photos before you begin.
Requirements for this method to work:
unrooted Samsung Galaxy S5 Mini G800F running official stock Android 6.0.1 Marshmallow
Samsung USB driver
enable USB debugging
charge your phone's battery to 100% just in case
TWRP Recovery 3.0.2 installed Official TWRP Recovery 3.1.1 is available now - check out this thread for download links
IMPORTANT NOTE ABOUT RECOVERY: Official TWRP now available
Procedure for getting root access:
1. Download Chainfire's SuperSU v2.78 SR5 [link] and store the zip file in the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the SuperSU zip and flash it, reboot after it finishes.
3. You should now see the SuperSU icon, open it and update the binary. Verify proper root with a tool like Root Checker.
Congratulations, you have successfully rooted your G800F! If you only want root - stop here, you're done.
Procedure for getting Xposed Framework:
1. After rooting your S5 Mini, download Xposed v87.1 built by wanam [link], Xposed uninstaller [link], and Xposed Installer APK [link]. Put all 3 files on the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the file named "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" and flash it.
3. After the flashing is finished, wipe cache and dalvik then reboot.
4. Using a file manager, navigate to where you put the Xposed Installer APK and install it.
5. Open it and confirm that Xposed is installed properly.

weird enough all those files where already on my pc. i just wanted to know if it would work

it says no root

Zakipoophead27 said:
it says no root
Click to expand...
Click to collapse
Which firmware version are you trying to root and did you use the exact files I've linked?

kom-pakt said:
Which firmware version are you trying to root and did you use the exact files I've linked?
Click to expand...
Click to collapse
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work

I also have 6.0.1 Germany DBT but this didn't root my s5 mini

Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk

Zakipoophead27 said:
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
Click to expand...
Click to collapse
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Helius61 said:
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Click to expand...
Click to collapse
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.

Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.

kom-pakt said:
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Click to expand...
Click to collapse
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.

Tomislav3383 said:
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Click to expand...
Click to collapse
Same for me

Does this root trigger the knox counter?

Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works

i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you

Helius61 said:
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
Click to expand...
Click to collapse
Glad I can help, also check out the other solutions posted in the meantime.
Dark_Horse said:
Does this root trigger the knox counter?
Click to expand...
Click to collapse
Yes.
Snowgay said:
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
Click to expand...
Click to collapse
Zakipoophead27 said:
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Click to expand...
Click to collapse
It seems that the culprit for the failed rooting were the different versions of TWRP you were using. I will add links to 2 versions of TWRP and a note about this in the main post.

Can someone help me? I did it like in the tutorial but it does not work. Thanks all

Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
What version of twrp do you have?

Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
I keep updating the first post with additional information and links, read it again and follow the instructions carefully without skipping any of the steps.

thanks for answer. Now it work with Version 2.8.0

Scharnhorst1939 said:
thanks for answer. Now it work with Version 2.8.0
Click to expand...
Click to collapse
Good to hear, version 3.0.2 works too and is more up to date.