Database Users

[N7100 Leaked 4.3] How to Root and other Information.

Get PRE ROOTED from Here
Flashed Leaked 4.3
Rooted successfully
It does have Knox suite But bootloader is not included so thats used for appl security, shouldn't make issue regarding warranty, though it's primary report, use at your own risk
Who are not in hurry to Root wait, let me study and understand better
THIS ROM IS WIPE ROM YOU WILL LOSE EVERYTHING ON DEVICE AS WELL INT SD CARD
Changes noted so far
Who can't hold to root follow this - TESTED by ME
How to Root :
Flash Philz recovery
Flash SuperSu1.65 (older won't work)
How to Rest Flash CounterTESTED by ME
-Download Stock Recovery
and copy to SD card Int/Ext
- Download MultiTool Advanced version (see My signature)
-Reboot to CWM, select MultiTool zip, Look for Recovery Menu - Select flash recovery from SD card (int/ext depend on location of stock recovery you put as in step1
-Flash
-Use Triangle away 3.05 to reset counter.
How to get USB debugging (Dev option)
Multiple time tap on setting - more - about device - Build number to unlock devlopment option
Titanium backup tested working
Directory Bind Working - You may need to describe path again backup may not work
First Mod created MultiWindow for all app - + CSC Features + Xposed Battery Module here
Don't Install Widget Locker
Someone reported Mobile Odin works - I personally didn't checked
Xposed framework working (I am using only two module both worked)
Lockscreen Widget (multiple) available
CSC features you can use with my MultiTool Advanced version, but don't select messege folder view, it will crash messeging app. Backup is highly recommended
-Someone reported No issue to downgrade
Bew leaked ROM doesn't have bootloader so Knox security may be just as suite but not related with warranty (These all are assumption now and follow at you own risk)
Also you should able to downgrade (DIDN'T TRIED YET)
No issue in downgrade
No issue in downgrade. This is how i have tested before public relelase
-Leaked 4.3 installed and rooted -> unrooted from SU -> rooted with prerooted ->No issue -> downgraded to MG1 (I had to wipe after downgrade, but no other issue) -> again flashed prerooted
So i have tested for both downgrading as well prerooted have no issue in root.
Found one weired thing with Knox
If remove knox related app, getting issue to use secured sites
I was unable to use banking sites (wifi/Mobile network disconnects), then i have restored knox app and then it is fine now,
If Anyone have notice some persistent notification with some application, it is due to 4.3
google have made persistent icon mandatory for application running in foreground. some developer makes their application running in foreground to make it non killable. they have to recode application.
Updating soon

Stock modem and kernel Recovery from 4.3 leaked
Stock Modem And Kernel
How to Flash
Download Stcok Kernel and copt boot.img to SD card. Use My MultiTool (Advanced)to flash kernel from SD card option
Download Modem.rar and Extract it to modem.bin Then copy modem.bin to SD card. Use My MultiTool (Advanced)to flash modem from SD card option
Download Stock Recovery and copy to SD card. Use My MultiTool (Advanced)to flash recovery from SD card option

Reserved

Reserved too

Last

KNOX ??
does it contains knox suite??
if yes then pls write about knox counter pls.
KNOX discussion in s4 must look they got it before us

Good news !!
so it is an authentic leak !

Damn Dr. K That was quick!
Well done.

There is Knox security
let me study some more
Who are not in hurry hold your horse to root

dr.ketan said:
There is Knox security
let me study some more
Who are not in hurry hold your horse to root
Click to expand...
Click to collapse
**** its in way flashing i f**** up.
s4 thread about knox

I love this Forum, Go Doc Go.

Will it be rooted if I use mobile Odin and inject supersu?
Sent from my GT-N7100 using Tapatalk 4

Give me some time to answer

How to root ?

Can we flash CWM (for example: philz) via odin and then flash any mods from note3 (snote3, launcher, etc ...)?

hold your horses, thats what the Doc said...this is LIVE coverage of a new release
mods come last in the list of priorities

dr.ketan said:
Give me some time to answer
Click to expand...
Click to collapse
give please instruction for root.I think this procese not hard.

rraaka said:
hold your horses, thats what the Doc said...this is LIVE coverage of a new release
mods come last in the list of priorities
Click to expand...
Click to collapse
i mean mods and also SU zip via CWM, it should be simpler with CWM, no?

I know some guys have rooted successfully.
Idiots worship phones like hell♡♥

How to root already updated half an hr ago on OP

HELP! SuperSU has been forced to stop WITH [i9505-cwm-recovery] & [SuperSU-v1.65.zip]

HELP! SuperSU has been forced to stop WITH [i9505-cwm-recovery] & [SuperSU-v1.65.zip]
Phone = I9505
Firmware = I9505ZHUDMI1
Recovery = i9505-cwm-recovery-6.0.3.2-4.tar (flashed by Odin)
su = UPDATE-SuperSU-v1.65.zip (flashed by cwm-recovery)
Now the phone keeping prompt message "SuperSU has been forced to stop ..."
In this situation, I have tried to flash the "CF-Auto-Root" by Odin, but I got error message from Odin "flash failed" and then the phone cannot boot, it said "firmware upgrade error .." I have to re-flash the cwm-recovery again by Odin to make the phone bootable.
Then I tried Chinfire's suggestion (h t t p s : / / p l u s . g o o g l e .c o m / +Chainfire/posts/5ggu7naWtaW) to turn off the KNOX - the prevention information was created by the KNOX.
Run the command "pm disable com.sec.knox.seandroid" in terminal emulator on the phone. As the su has been killed time to time, the terminal emulator cannot really complete the "su" command, then cause the "pm disable com.sec.knox.seandroid" cannot completed. So cannot turn off the KNOX.
I really need the phone been fully rooted without the "Prevention information".
Could anybody help me on this issue?

tedaz said:
Phone = I9505
Firmware = I9505ZHUDMI1
Recovery = i9505-cwm-recovery-6.0.3.2-4.tar (flashed by Odin)
su = UPDATE-SuperSU-v1.65.zip (flashed by cwm-recovery)
Now the phone keeping prompt message "SuperSU has been forced to stop ..."
In this situation, I have tried to flash the "CF-Auto-Root" by Odin, but I got error message from Odin "flash failed" and then the phone cannot boot, it said "firmware upgrade error .." I have to re-flash the cwm-recovery again by Odin to make the phone bootable.
Then I tried Chinfire's suggestion (h t t p s : / / p l u s . g o o g l e .c o m / +Chainfire/posts/5ggu7naWtaW) to turn off the KNOX - the prevention information was created by the KNOX.
Run the command "pm disable com.sec.knox.seandroid" in terminal emulator on the phone. As the su has been killed time to time, the terminal emulator cannot really complete the "su" command, then cause the "pm disable com.sec.knox.seandroid" cannot completed. So cannot turn off the KNOX.
I really need the phone been fully rooted without the "Prevention information".
Could anybody help me on this issue?
Click to expand...
Click to collapse
Same problem here. have you found any work around?

unmanarc said:
Same problem here. have you found any work around?
Click to expand...
Click to collapse
Yes, I flashed the ZHAME3 (includes PIT, PDA, PHONE and CSC) by odin.
Then the knox warranty related text dispeared from the recovery screen.
And then I flashed the ZHBMF4 (includes PIT, PDA, PHONE and CSC) by odin, rooted with CF-Auto-Root. Now the phone works perfectly!
Before big mans conquered the KNOX, I would like stay at the BMF4 version.

tedaz said:
Yes, I flashed the ZHAME3 (includes PIT, PDA, PHONE and CSC) by odin.
Then the knox warranty related text dispeared from the recovery screen.
And then I flashed the ZHBMF4 (includes PIT, PDA, PHONE and CSC) by odin, rooted with CF-Auto-Root. Now the phone works perfectly!
Before big mans conquered the KNOX, I would like stay at the BMF4 version.
Click to expand...
Click to collapse
download es file manager from play store
go to tools and click on root explorer
now you must mount system and / as rw
then go to system/app delete apps that begins with the name knox files
then go to /data/data/ and delete com.seandroid.knox or like so files (or click on search and type knox and delete the results)

Boot errors
Bordo_Bereli51 said:
download es file manager from play store
go to tools and click on root explorer
now you must mount system and / as rw
then go to system/app delete apps that begins with the name knox files
then go to /data/data/ and delete com.seandroid.knox or like so files (or click on search and type knox and delete the results)
Click to expand...
Click to collapse
If you could explain in more detail how to get rid of this knox error i would greatly appreciate it.
KERNAL IS NOT SEANDROID ENFORCING.. and SET WARRANTY BIT : KERNAL

ICEMAN4280 said:
If you could explain in more detail how to get rid of this knox error i would greatly appreciate it.
KERNAL IS NOT SEANDROID ENFORCING.. and SET WARRANTY BIT : KERNAL
Click to expand...
Click to collapse
Disabling KNOX Using Terminal Emulator
This method requires root access on your device.
Download and install the Terminal Emulator app on your phone or tablet.
Launch the app on your device and grant it root permission when prompted.
When you see the command box, type the following command:
su pm disable com.sec.knox.seandroid
Doing this will disable Samsung Knox on your device
Alternative Method To Disable KNOX
Download and install an app that is capable of freezing system apps on Android devices. Titanium Backup is a good option. Open TB when it is installed and freeze the following apps:
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
2. Alternative Method to Disable KNOX (CWM/TWRP required)
download the zip (see attachment)
and flash it
If you have the latest bootloader, you can't delete set Warranty bit: Kernel because the bootloader find out, if kernel is signed or not. You cannot downgrade the bootloader.

(ROOT) (CUSTOM RECOVERY) FOR MOTO G 1st GEN

Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well

On which android version , were you on before rooting . 5.01 or 5.1 .

This method works for both 5.1 and 5.01

Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849

Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk

Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!

Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:

Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?

sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!

sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)

Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:

sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you

thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!

notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:

Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device

Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!

issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.

pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.

issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link

facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??

[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:

[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.