yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Noflexing:
I'm sure it had to have occurred to you that I don't know it was an auto generated build. I asked a question not knowing if my root will be a success. You didn't answer anything and was just plain rude. Shocking that you have around 9500 post and act this way. Should be more helpful.
[Android Software/Hacking General [Developers Only]] :
Come on guys lets play nice before this gets out of hand. Everyone of us was a noob once so we all got to learn at some stage

Regards

Sawdoctor
[Android Software/Hacking General [Developers Only]] Noflexing:
This is exactly my point that everyone was a noob at one point and has to learn. I don't get why a person with 9500 post that's been around this site for a long time had to answer that way without being helpful.
[Android Software/Hacking General [Developers Only]] force70:
Just so your aware, it already got out of hand.

Another mod has already deleted his original post for profanity and name callingdirected towards me and yet he still continues whining and crying in a development thread.

I did not swear at anyone nor broken any rules.

I am playing nice :D

Sent from my S8 plus, Note 7, S7 Edge or S6

---------- Post added at 04:39 PM ---------- Previous post was at 04:33 PM ----------

Yes and I expect people who dont know to search and read to educate themselves....like i did when i was new and still do.

I have never expected to be spoofed answers as seems common these days sadly.

To answer your question if it was not addressed no root will not work on those devices due to the locked boot loader. In the past there has been work around for some locked devices even the locked s7s and note 7 laat year got root via engineering firmware . But the manufacturers are making it harder and harder for us to even root let alone have twrp or roms available.

As for the S8...the exynos versions are not locked and development is in full swing!

I dont think the verizon note 5 ever got a work around...i could be wrong there but verizon and AT&T are notorious for being locked down...now Mobile and even the Canadian carriers are following that trend

Sent from my S8 plus, Note 7, S7 Edge or S6
[Android Software/Hacking General [Developers Only]] Noflexing:
Thank you for answering the question. I Just wish you had done that first before anything else. I was just confused since I thought if the file for the model number was there on chainfire it meant it could be rooted.
[Android Software/Hacking General [Developers Only]] force70:
Yeah thats been a topic lately...the builds are listed so since they are there in theory should be good to go.

In the OP theres a warning about locked bootloaders not working for this but one would also think if it wouldnt work it wouldnt be listed either so its somewhat odd. And if you dont know your BL is locked thats another issue and maybe some people dont know.

This is why i heavily encourage people to read and research as much as possible before flashing anything.

Sent from my S8 plus, Note 7, S7 Edge or S6
[Android Software/Hacking General [Developers Only]] zoryox:
When will SM-A710FD or just F version of cf auto root for the 7.0 nougat come out???
[Android Software/Hacking General [Developers Only]] RuAnShi:
Sorry to post this here, I've read policy to post question in dedicated device thread, but this thread is so old and seems to be dead.

I have experienced minor problem with CF-Auto-Root (CF-Auto-Root-gts28lte-gts28ltexx-smt715) for Samsung Galaxy Tab S2 LTE (SM-T715) on Android 7.0.

The SuperSu is installed and working fine but device after this process lost control of screen brightness (the slider has no reaction and screen always at high light) and USB connectivity (MPT interface does not appear anymore when plugged to PC). I have tested this twice, when original firmware flashed back all work as expected when rooted again, the same problem exist.

Can you please point me where to look to solve this issue manually since root access exist.
[Android Software/Hacking General [Developers Only]] osygen:
I was able to root my galaxy tab A sm-p555, but i had to unroot because i couldnt access the internet. Help fix this, please.:crying:
[Android Software/Hacking General [Developers Only]] Casper1982:
for SM-g920w8 android 7.0?
[Android Software/Hacking General [Developers Only]] BilboDaddins:
Canadian Note5 (SM-N920W8) Nougat root

Thanks for releasing CF-Auto root for Galaxy note 5 (SM-N920W8) Android 7.0. A great fan of your work.

Donated a dollar :)
[Android Software/Hacking General [Developers Only]] Actarus81:
Quick, recap, I own a galaxy S5 Lolipop 5.1.1 SM-G900W8 build #LMY47X.G900W8VLU1COI4, previously rooted.

It all begin, when my phone been experiencing some battery draining issue. So I decide to do factory rest. But get this at that time my phone was fully rooted, w/Lolipop 5.1.1...

So I've read all the informations I could get online made sure to unroot the phone ( using CF-Auto Root ktlevl 82 048 989-sm G900W8.), with Odin, and reflash the phone with custom recory (G900W8VLU1COI4.tar.md5 file). I've made sure to get the exact one matching my phone carrier.

And after rooted the phone...All went well...Then 24-48 hours after the **** hit the fan.!!!!

They weere dialogue box keep poping up, from Touchwiz has closed, to Unified Daemond has closed just to name a few...

I decided to factory rest the phone again, reflash and rooted same problem occuring occuring.

So I decide not to root and the issue stop but now I'm unable to fully use my phone because it anin't root so certain function of my phone can't benefit such like using Airplane mode or Mobile data toggle using tasker. When my phone was fully rooted I was able to take full advantage of my Tasker profile. I've google the web and came acrros people who expericing the same issue as I did, but can't find a solution.

If there anyone who had that problem and manage to solve it, kindly share your story and solution with me....

Thank you in advance on getting back to me,
[Android Software/Hacking General [Developers Only]] BilboDaddins:
Use Smart Switch

Download Samsung Smart Switch and do the following:

1. Select the "more" tab

2. Go to the "emergency recovery and initialization" tab

3. Enter your device model, serial number

4. Follow the on-screen instructions

FYI,

1. If you have a side-by-side configuration error when installing smart switch, download "Microsoft Visual C++ 2008 redistributable x86" and install it from the Microsoft website.

2. Using Smart switch removes/restores everything to the latest version. You will lose root, custom recovery, backups, etc.

Good luck. Smart Switch is so simple to use.
[Android Software/Hacking General [Developers Only]] The..King:
Hi.

Quick Q relating to the short paragrapgh entitled "Android Version" over on the CF Auto-root homepage. As it describes, this is exactly what happened to me.

I previously had a rooted (via CF Auto-root) SM-G920F running 6.0.1 and everything was good. I tried the new update to Android 7.0 a few days ago - absolutely hated it (like a lot of people). I wanted to roll back to 6.0.1 again but due to what I assume were new Bootloaders, I couldn't rool back. Kept getting a "sw rev check fail device 5 binary 4" everytime I tried to flash the old 6.0.1 Stock.

Anyway, I eventually found a way around it without having to mess with Bootloaders or anything else and I got back to stock 6.0.1 (G920FXXU5DQA7). I then went back to Chainfire homepage and looked for the right CF Auto-root file to flash, but the only one available for SM-G920F is (NRD90M.G920FXXU5EQD7) which is based on Android 7.0. I obviously didn't flash this because I'm not running Nougat, I'm back on MM and the homepage of Chainfire says to "get the right file".

I still had the original CF Auto-root file I used the very first time around (G920FXXU4DHP5) which is based on Android 6.0.1, so I tried that. I seemed to work ok, but in recovery mode - it continually says "DM-Verity verification failed" and from Googling around, it seem to indicate there is a conflict between the stock 6.0.1 I recovered to and the auto-root I used based on Android 6.0.1.

So having given the details outlining the problem, my Q really is -- is there a CF Auto-root available for the SM-G920F, based on Android 6.0.1 stock (MMB29K.G920FXXU5DQA7)??
[Android Software/Hacking General [Developers Only]] ashyx:
Forget about cfautoroot. Just install twrp and then flash SuperSU v2.79 sr3. However do NOT update it as there are currently issues with the latest version.
[Android Software/Hacking General [Developers Only]] The..King:
Thanks for the reply ashyx.

Believe it or not, but I'm not familiar with TWRP at all - despite rooting many times.

Is there any specific TWRP I should be using? (I ask because I've never used TWRP before. Used CWM but that was years ago [Galaxy S2] and have only rooted with cf auto-root & a few other custom roms since then.)

Once I know which twrp to use, do I flash it to my stock ROM the same way I would cf auto-root? i.e. phone in recovery mode and then by selecting the 'AP' button via Odin? (I've had a look at some tutorials before replying here, but most I can find are conflicting/misleading and are from years ago.)

Once I have TWRP installed, I assume I just download SuperSU v2.79 sr3 on my PC, copy the file over to my phone (any specific location?), ensure usb debug is enabled, boot into recovery mode and then............?

Feel like a proper newbie now...

Thanks in advance.
[Android Software/Hacking General [Developers Only]] The..King:
Hi again,

Further to my earlier post (#2027 ) is there also a reason to run with SuperSU v2.79 sr3? I just seen that there was a lot of issues with v2.80, but I see v2.81 has been released as a stable build?

I'd really appreciate if you could get back to me on both of my recent posts - kinda hanging on here before I make any changes again to my phone again. (Not for the first time in my life it's a case of "should have left everything alone" when it worked fine. #grassisn'talwaysgreener

Again, thanks in advance.
[Android Software/Hacking General [Developers Only]] ashyx:
Neither are stable, stick with v2.79.

---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------

I suggest you consult the development area of your device forum. Everything you will need will be posted there.
[Android Software/Hacking General [Developers Only]] The..King:
Ok - thanks.

Ehhh - thanks??? I only asked you because you were the one to suggest forgetting about CF auto-root and doing something else (alien to me) instead. Thought the suggestion would have at least been supported in some fashion like perhaps clarifying how to apply TWRP via Odin (over a stock [non-rooted] rom) and then how to flash SuperSU from there. In all fairness, I've been sifting through endless pages for the last two days on this and other sites looking for various answers to get me to the point of recovery I am at now. No offence, but if a suggestion can't be supported in any fashion by the person who suggested it - then I need to sift through even more topics/threads like I need a hole in my head. Thanks for the bit of help, hopefully someone else will weigh in to get this over the line.
[Android Software/Hacking General [Developers Only]] ashyx:
Really? :rolleyes:

https://xdaforums.com/galaxy-s6/help/help-installing-twrp-sm-g920f-7-0-t3610005
[Android Software/Hacking General [Developers Only]] Flukester69:
Will your Auto-Root work on my device? I have an ASUS Z300M (specs here). It's got a MTK 8163 chip. ASUS recently released the tool that unlocks the bootloader of this device. My bootloader is now unlocked. This is actually a really good tablet with a MALI 450. I'd like to root it. I'd like to try and eventually make a clean and bloat-free version of the ROM, it's the biggest handicap. Appreciate any help/guidance.

P00C_2:/ $ cat /proc/emmc
/system/bin/sh: cat: /proc/emmc: No such file or directory
1|P00C_2:/ $ cat /proc/partitions
major minor #blocks name

254 0 1000276 zram0
179 0 15388672 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16348 mmcblk0p9
179 10 16348 mmcblk0p10
179 11 16348 mmcblk0p11
179 12 512 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 5120 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 2048 mmcblk0p19
179 20 32768 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 102400 mmcblk0p23
179 24 204800 mmcblk0p24
179 25 3665920 mmcblk0p25
179 26 11186523 mmcblk0p26
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 30981120 mmcblk1
179 129 30977024 mmcblk1p1
253 0 11186523 dm-0
P00C_2:/ $
[Android Software/Hacking General [Developers Only]] KinG Of PiraTeS:
Hello !

Chainfire ( Life savior ) ^_^

I've updated my Galaxy S4 "I9505" to latest firmware build date : Sat, 25 Feb 2017 03:19:43 +0000

the problem that it can not be rooted With CF-Root or any other rooting tools

I have tried Flashfire to keep the SU from the old to the new Build the same issue >_<

I decided to download another Firmware ( I9505XXSHQB1 ) the same problem cannot be rooted

I will upload to you the "Recovery.img" from the firmware file as you mentioned in your website :

-----

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!

-----

I've uploaded the "Recovery.img" into a Zip file to bypass XDA Limit size

This is the last log file from Flashfire : https://pastebin.com/4rK7Rr4W

Thankx in advance
[Android Software/Hacking General [Developers Only]] lukumon.tj:
Hello Chainfire,

Can I use the CF auto root for Tecno W2? A mediatek phone. I am having a Triada malware on it and i need root to disable adups fota
[Android Software/Hacking General [Developers Only]] The..King:
Brilliant - thanks very much for that, appreciate it! A simple link makes finding a needle in a haystack a lot quicker.

Once I flash TWRP so, does it matter where on my phone I copy the downloaded SuperSU v2.79 file to in order to flash it in recovery? (Bearing in mind that I've an SM-G920F and therefore no external SD).

Even contemplated just sticking with a stock rom and running 'Debloater' by GJ, but having tried on a new stock rom and reading a tonnes of forum pages here after encountering ("Error: java.lang.SecurityException: Neither user 2000 nor current process has android.permission.MANAGE_USERS. ") - it seems Google have disabled 'Debloater' from running adb commands and GJ hasn't been able to find a workaround to date. So once I know where to stick the SuperSU v2.79 file - I'll give it a go.

Again - thanks.
[Android Software/Hacking General [Developers Only]] ashyx:
As long as your device isn't using encryption you should be fine copying to internal storage.

If not you can try adb sideload.
[Android Software/Hacking General [Developers Only]] The..King:
I took a backup of my SM-G920F and was about to flash TWRP & SuperSU as you suggested, but I just read this on the TWRP website:

Can I just get some clarity on this? i.e. The whole reason why I have always used CF Auto-root in the past (apart from being uncomplicated to use) is that it leaves the stock rom in place and just gives SuperSU access without messing around with anything else.

As Chainfire says:

In fact, the only reason I am currently 'here' now, is because I had DM Verity issues after downgrading from stock 7.0 back to stock 6.0.1 and Chainfire doesn't seem to have a version of CF Auto-root for the SM-G920F based on the latest/last 6.0.1 build (G920FXXS5DQC4_G920FXEU5DQB8_XEU).

Subsequently, when I try the current CF Auto-root (over on https://autoroot.chainfire.eu/) based on 7.0 (NRD90M.G920FXXU5EQD7) - it works but I get DM Verity issues. It's the same if I try an older CF Auto-root I still had on my PC which is at least based on the same Andriod version 6.0.1 - but an earlier build (MMB29K.G920FXXU4DHP5) - it works but I get DM Verity issues because it's not the latest build of 6.0.1 and I can't downgrade the stock 6.0.1 to an earlier version because I get "sw rev check fail device 5 binary 4" when I try to flash it over a newer bootloader which I assume happened during the 7.0 update. (By the way, 'OEM unlock' is not listed in developer options on my phone and according to many websites I've read - it apparently means that my bootloader is not locked? Damned if I know. I'm just mentioning this because if I could downgrade to an earlier stock rom of 6.0.1 without encountering the "sw rev check fail device 5 binary 4" error, then I could still use the earlier CF Auto-root I still have (MMB29K.G920FXXU4DHP5) without getting any DM Verity issues. (aka. Back to where I was before this whole upgrading mess.)

To be clear, my objective is to keep the normal stock rom on 6.0.1, but to have root access.

Finally, the TWRP website also states:

Does that mean finding an official stock rom (usually from Sammobile) and then flashing it to the phone, which may result in loss of data?

Sorry for more questions, but outside of what is known to me over the years from rooting S2, S3, S5, S6 many times - I don't know much about the complexities of roms, kernals, recoveries, binaries, etc. Just a stock rom, root access and no major messing around with anything - and I'm all good.

Thanks in advance as always.
[Android Software/Hacking General [Developers Only]] ashyx:
OK just to clear a few things up.

CFautoroot and supersu are the same product.

The only difference is that CFautoroot reflashes the stock recovery after its done rooting.

Both use custom recoveries to install and both use SuperSU.

CFautoroot is ALWAYS behind SuperSU in development. That's why it's recommended to install the latest Supersu to avoid issues especially when using the latest firmware.

Neither CFautoroot nor supersu modify the stock rom.

SuperSU will automatically disable dmverity so that is not an issue.
[Android Software/Hacking General [Developers Only]] doclorenzo:
Used the new cf-autoroot for nougat 7.0 on a Samsung S7 Edge.

I could not get past the PIN code at boot because it kept saying wrong PIN. Had the same issue with TWRP.

Does this mean that cf autoroot, just like twrp, does not work with encrypted data, and I have to disable pin at boot and format data, before using cf autoroot?

I really hoped that cf autoroot would bypass this...
[Android Software/Hacking General [Developers Only]] BilboDaddins:
CF Auto root on older android versions

Would CF Auto root for Android Nougat work for Marshmellow?
[Android Software/Hacking General [Developers Only]] KennyLG123:
No it wont work because of the changes in system between MM and Nougat...
[Android Software/Hacking General [Developers Only]] BilboDaddins:
Tried and worked.

I flashed Android 7.0 CFAuto Root on my Note5 running Android 6.0.1 and it worked fine. Weird thing is on the stock recovery it says Android 7.0 but I am running 6.0.1.
[Android Software/Hacking General [Developers Only]] KennyLG123:
Ive seen it not work for others but if you didnt get bootloop thats good..i also have a n5 but 920c but there is a cf for 920 on 6.01..
[Android Software/Hacking General [Developers Only]] ashyx:
It's not weird, you've flashed the stock recovery from Android 7.0.

Thats what CF-AUTOROOT does.
[Android Software/Hacking General [Developers Only]] KennyLG123:
Well it must be close on art/delvic to flash cf nougat on a MM OS device and work. I never did it that way to find out..lol but its good to know it does work i used to tell some its not how much you know you always learn something new....
[Android Software/Hacking General [Developers Only]] ashyx:
Not sure what you mean about Art and dalvik as they are irrelevant to rooting.

Samsung are quite lazy when it comes to updating the firmware on their devices.

If CFautoroot is using a Nougat kernel then its probably just a patched MM kernel which is why it works on a MM bootloader.

I. E. same kernel version.
[Android Software/Hacking General [Developers Only]] KennyLG123:
Im just meaning placement of binary in system. I heard Rovo mention art/devlic didnt show a significant change between the two. Now we know something like KK and LP this wouldnt work major changes. I always flash device sufficient to eliminate problems. Im glad there wasnt much of a change or it wouldnt work..im just hoping to get a few more years in before google and the oems patch the devices like some....lol
[Android Software/Hacking General [Developers Only]] ashyx:
Unless you forced it then the binaries will be on data. Supersu decides where to install the binaries based on the SDK version the device is built on.

Also the same binaries are used for all supported arm android versions aside from 32bit or 64bit versions of the binaries.
[Android Software/Hacking General [Developers Only]] alastairgreen_Nexus:
CF Auto Root For SM-A510Y running Nougat

Here is the recovery img for the SM-A510Y, as it receives a Nougat update in New Zealand(NZC Unbranded)

PDA: A510YDOU4CQD7

CSC: A510YNZC4CQD7
[Android Software/Hacking General [Developers Only]] Riden44:
It is possible to root the galaxy note 5 n920v with the cf auto root? I'v got fail in odin.
[Android Software/Hacking General [Developers Only]] force70:
Lol no.

I guess you didnt read the part about CF not working with locked bootloaders?

Read first flash later, it will save you wasted time and effort

Sent from my S8+ exynos , S7 Edge exynos or S6
[Android Software/Hacking General [Developers Only]] roxyd:
Just a quick question, the one on the website for the sm-g935f is baseband DQD3, I'm baseband DQD7. Does this mean it won't work or should I give it a try? Kind of new to all this ?
[Android Software/Hacking General [Developers Only]] canynballa:
[MENTION=631273]Chainfire[/MENTION] I had a question about on your cf auto root site it says there's a cf auto root file for the sprint S8 ended in QD9. I thought all US Samsung S8's had a locked bootloader.
[Android Software/Hacking General [Developers Only]] MECH_TECH:
I am not having any progress searching for an answer to my post or a few others that posted the same question. Is there a CF Auto Root for the Canadian SM-G920W8 yet for Android 7. I checked the web site and I found the root for 6.0.1 "CF-Auto-Root-zerofltebmc-zerofltebmc-smg920w8.zip" but not sure if the recovery image is the same in it as in the new stock 7 recovery.

Or

Can I install the Standard Ver 7 SM-G920W8 ROM for Rogers using ODIN then install the latest TWRP for it using ODIN then root by just installing SuperSU using TWRP?
[Android Software/Hacking General [Developers Only]] force70:
They are locked down yes

Sent from my S8+ exynos , S7 Edge exynos or S6