yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] ivorli:
Flashing my N915W8 using the CF-Auto-Root-tbltecan-tbltecan-smn915w8.tar.md5 verified with MD5 hash 23288dcbfaca4caaa1768ad0fe13d801, bricked the device. I had N915W8VLS1CPK1 firmware previously. I had to flash firmware again to get the device working again. I noticed there are 2 PDA versions for Android 6.0.1. Nope. Tried to flash from N915W8VLU1CPE2. Still doesn't work.

N915W8VLU1CPE2 Dated 26.05.2016

N915W8VLS1CPK1 Dated 27.11.2016

Here is the recovery for N915W8VLS1CPK1 .
[Android Software/Hacking General [Developers Only]] kushal.arora16:
Help plzz...

Plzzzz make CF-Auto-Root for Samsung Galaxy J Max ( SM-T285YD) Tablet LL 5.1.1.. I am attaching stock recovery image & boot img in zip file(Bcz of 8MB maximum upload limit allowed for img files).. Plzz help...:rolleyes:

thanksss....plzzz help me....
[Android Software/Hacking General [Developers Only]] Seken:
Request

Please Make Galaxy Note Edge SM-N915F. not working n915f MMB29M.N915FXXS1DPH2 cf-auto-root please make this recovery.img
[Android Software/Hacking General [Developers Only]] levyhuba:
Hi I have a Galaxy S5 Baseband version: G900FXXS1CQA3, Build number: MMB29M.G900FXXS0CQAB on Android 6.0.1.

How can I root it. Unfortunately no Build ID on https://autoroot.chainfire.eu/ :) Can anyone help pls?
[Android Software/Hacking General [Developers Only]] rode:
any idea if the samsung galaxy J1 mini will be ever supported? Can not find any root method for this phone.

Model SM-J105B
[Android Software/Hacking General [Developers Only]] ashyx:
I'm sure this device has root via twrp.
[Android Software/Hacking General [Developers Only]] rode:
Any link to this proces?
[Android Software/Hacking General [Developers Only]] ashyx:
There's various posts knocking about. Start with this one:

https://xdaforums.com/general/help/samsung-galaxy-j105-custom-recovery-t3377042
[Android Software/Hacking General [Developers Only]] rode:
Not very helpfull that topic. still nothing there that works. The last link posted (working for somebody with still a different version of phone) not donwloadable :( :(

Besides: J1 mini TWRP project had issues and was discontinued.
[Android Software/Hacking General [Developers Only]] Soft-Man:
Request

Please Make for Galaxy Folder 2 G1600
[Android Software/Hacking General [Developers Only]] bmbm:
Please [MENTION=631273]Chainfire[/MENTION] , make for Samsung Galaxy Tab 10.1 SM-P600 . With new update P600XXUDQA1 old cf-auto-root doesn't work anymore. Thanks!
[Android Software/Hacking General [Developers Only]] 52wiseson:
Hi [MENTION=631273]Chainfire[/MENTION],

I am requesting you to please add cf-auto-root for SM-N9208 for Marshmallow ROM

Build Number MMBK29K. N9208XXS3BQA6.

Thanking you in advance for your excellent work.
[Android Software/Hacking General [Developers Only]] asperrrrrrone:
recovery.img from Android 7.0; phone is SM-920F: https://www.sendspace.com/file/v171k1

Waiting for a CF-Auto-Root :)

Thank you very much [MENTION=631273]Chainfire[/MENTION] !
[Android Software/Hacking General [Developers Only]] alastairgreen_Nexus:
Hello [MENTION=631273]Chainfire[/MENTION], can i flash the SM-J510S root file to my SM-J510GN/DS device as they have the same processor, the MSM8916/Snapdragon 410
[Android Software/Hacking General [Developers Only]] jkeuclid:
[MENTION=631273]Chainfire[/MENTION], I've been out of the channels here for some time but as long time admirer, follower and supporter of your work I normally wouldn't post my question here but I have an International G930F arriving today and since CF-Auto-Root doesn't as yet support Nougat, I'm curious about your statement in the OP,

"The difference with many other rooting solutions is that those will often install a custom recovery for you (I am personally moving away from custom kernels and recoveries, for various reasons), while with CF-Auto-Root you will end up with a stock recovery again."

could you elaborate on this as I've been mostly in this camp since the beginning with my current S4 Active, opting for normal root, no recovery etc. I'd be curious why you feel as you do above, especially today currently, is it mostly the counters remaining at 0/official, etc.(Triangle Away)?. Having said this, I believe my G930F is coming with Marshmallow installed and may opt to use CF-Auto-Root to stay on this for the moment until I read more on Nougat and if it's beneficial to move to it.

There is another root solution for the G930F that works on Official stock Nougat found here, but it installs a recovery which is not what I want atm (since I use Flashfire Pro for my needs) but I don't usually like to root an OS until I have the flashable ODIN files which aren't as yet available for US users as I am. Any insight would be greatly appreciated, thank you.
[Android Software/Hacking General [Developers Only]] fundaprob:
[MENTION=631273]Chainfire[/MENTION]

Can you autoroot Docomo Note Edge (from a popular Japanese carrier)? Your site has no mention of it at all despite having 14 other Edge models. XDA has a few threads where other people would like to autoroot it also.

SC-01G, tlbtedcm, APQ8084, Android 6.0.1 (got an update in just 3 months ago)
[Android Software/Hacking General [Developers Only]] :
Is this thread even watched anymore by chainfire?

Still no response or result (root) for the SM-A720F, released over two months ago.
[Android Software/Hacking General [Developers Only]] ashyx:
TWRP + supersu = root
[Android Software/Hacking General [Developers Only]] :
[MENTION=4899305]ashyx[/MENTION]

There's no official TWRP support for the A7 2017, and I have spoken with the guy behind teamwin, he has no drive or passion anymore, certainly not for some models, like the A series from Samsung (not even the 2015 and 2016 A series have official TWRP images, so that's not a good prospect for the newest gen in the series). That's why chainfire and kingroot are my only hope, but all modern hackers are too slow, or they cherry pick certain models to patch them, and exclude others. That is annoying. The methods to patch/root devices are always the same, so finding new strategies for new models should be quick, as they supposedly already know the way.

Thanks for your idea (not like I have not thought about it), but TWRP will never happen for this model. Not even telling the guy I'd gladly support him if TWRP became a payware brought any hope, He was more interested in being rude and sarcastic than at keeping TWRP going for everyone.
[Android Software/Hacking General [Developers Only]] windrider42:
I find both of these

http://www.teamandroid.com/2017/02/05/update-galaxy-a7-a720f-2017-xxu1aqa1-android-6-0-1-marshmallow-official-firmware/2/

https://xdaforums.com/samsung-a-series-2017/how-to/root-cwm-recovery-galaxy-a7-2017-model-t3552157
[Android Software/Hacking General [Developers Only]] :
[MENTION=4376402]windrider42[/MENTION]

The CWM has a mention on another thread here at XDA, where a user calls it "suspicious", because either the coding or whatever is for a SM-A750F, which doesn't exist. (I don't remember what it is, exactly).

As for the other one, I will check it out, but I'd rather use trustworthy methods/brands.

Thanks.
[Android Software/Hacking General [Developers Only]] windrider42:
I understand.. Just thought I would post them.
[Android Software/Hacking General [Developers Only]] ashyx:
OK let's just get something straight.

What has official TWRP support got to do with anything?

How do you think most of these devices get support in the first place? They are compiled and built by people like me?

I have built TWRP for countless devices and none of them I have made official, I choose not to, due to the convulted process of actually getting them official status.

I have also ported CF-autoroot for many devices.

That does not mean to say that my builds are any less functional, they work perfectly, I make sure of it. Many of my builds have more features than so called 'official' builds

Official status means nothing more than a place on the TWRP server and updates when new versions are released.

Something which I do myself.

I also think you simplify too much what is actually involved in getting these builds working. There's a fair amount of effort that goes into it, especially considering I own non of the devices I've compiled TWRP or CF-AUTOROOT for.

I have compiled TWRP for many of the A series devices from the A3 to A7.

If the A720F needs it I will look into compiling TWRP for it too.

Head over to the A series forums, check it out. PM me if you are willing to try out a test build.
[Android Software/Hacking General [Developers Only]] :
[MENTION=4899305]ashyx[/MENTION]

Deal. I'll PM you tomorrow, and I'll check out the forum then too. It's almost 3am here, so see you then.

I'll have questions about the prototype being no-official though, like, bricking concerns and other stuff.
[Android Software/Hacking General [Developers Only]] misulik79:
Hi. I can't find CF-autoroot for Samsung Galaxy S7 SM-G930F*Nougat
[Android Software/Hacking General [Developers Only]] osygen:
My phone (Samsung galaxy tab A sm p555) wont boot after rooting. what am i doing wrong
[Android Software/Hacking General [Developers Only]] ashyx:
It's not compatible.
[Android Software/Hacking General [Developers Only]] fundaprob:
I found my recovery.img, hope someone's willing to compile CF-Autoroot for SC-01G.

Galaxy Note Edge (DoCoMo)

Model: SC-01G

Region: DCM

Version: SC01GOMU1CPL2

Android: Marshmallow 6.0.1

Build Date: 28.12.2016

Changelist: 10224933

recovery.img:

https://mega.nz/#!9L51XDCZ!UTD_KbTEd8Kvgp9ydbOAL3Fv54NgM--IKLJEcppNP0o

MD5: 8262b006edbead8ad9c1ae2d4e599086

Anyone? I can make a good donation ;)
[Android Software/Hacking General [Developers Only]] leo5111:
any hope for root on 5.1.1 on note 12.2 p907a?
[Android Software/Hacking General [Developers Only]] lbdanny:
tried chainfire root.. now phone stuck

First off, I am sorry if I missed the answer earlier in the thread... I really did try to search on this.. and did nto find an answer.

So I picked up a note 4 (N910T) , and downloaded the chainfire root files.

I tried it with both Odin3 v7 (which was used in the webpage description) and Odin3 v10 (whcih is what came with the down load.

In both cases, after multiple tries, according to ODIN, it seams to work... does all the stuff... then says "reset" in uper left... which changes to "PASS!" after a few minutes.

....but the phone just shows the samsung splash screen. and will not boot any farther... no mater what I do... pulled battery, tried rebooting holding vol. Up, home, and power... all same...

Screeen says

(tiny letters) in blue "Recovery booting"

in red Recovery is not SEANROID ENFORCING

in yellow Set Warrenty bit: recovery

..and then the Samsung galaxy Note 4

I am getting worried!!!!!

Thank you in advance
[Android Software/Hacking General [Developers Only]] ashyx:
It's just a simple case of flashing the stock firmware to fix.

It could be one of several issues why cf_autoroot hasn't worked. Firmware updates tend to break CFautoroot.

SuperSU is much more on game and keeping up with the changes.

I suggest you flash twrp and then the latest Supersu.

If you do the above you can probably save yourself the hassle of flashing the stock firmware.
[Android Software/Hacking General [Developers Only]] :
As the other tester said on the now closed thread, SuperSU is not flashing via the unofficial TWRP, so I immediately flashed the stock ROM after trying it. I figured logs would be useless, as the other tester had already sent them. I won't try Magisk, or anything other than SuperSU and Kingroot. So, A720F is still not officially rootable.
[Android Software/Hacking General [Developers Only]] ashyx:
I closed the other thread because it has been moved.

https://xdaforums.com/samsung-a-series-2017/development/xcc-t3591448

Also your statement doesn't make sense. It is your personal choice to only use SuperSU or a suspect Chinese rooting method.

Magisk and PHH superuser are both valid open source root methods.

So yes the device IS rootable.
[Android Software/Hacking General [Developers Only]] :
I do try to substitute Kingroot with SuperSU-ME, which is an app that has never worked for me in the past, but it's a valid shot. Kingroot doesn't work on newer devices either anyway, as of now.

So basically, all I'm willing to trust is SuperSU. It's that simple.
[Android Software/Hacking General [Developers Only]] ShinySide:
You trust "closed" source shady Kingroot over open source Magisk? Lol Developer of Magisk provides everything for you or anyone else to see and is hiding nothing unlike Kingroot or kingoroot which both have had shady practices from collecting data to collecting IMEIs in the past. And pretty sure it's Kingroot that needs a data connection to work....wonder why lol
[Android Software/Hacking General [Developers Only]] :
[MENTION=5580710]ShinySide[/MENTION]

No, what I actually said has just been quoted above. Super-SUME needs Kingroot so that Kingroot can be replaced by SuperSU, therefore the shady Chinese app is just a mean to an end for me. Unfortunately, this method never worked before for me (Gran Prime and J7, which are rootable with Kingroot), but you never know with Super-SUME Pro, as it seems it works for other people.. So if Kingroot roots the A7 soon, then this method to implement SuperSU will be an option I and others will try.

I never used the word "trust" when referring to Kingroot.

I don't trust brands I have never heard of before, and I don't want to be stuck with them once they have been flashed. That is my right and personal choice, and I'm entitled to them.
[Android Software/Hacking General [Developers Only]] ashyx:
Your logic is a little narrow minded and misplaced.

So you trust Supersu and therefore it's author Chainfire? You are aware then that Chainfire has been working with the developer of Magisk and allows Magisksu to work with Flashfire, something that King root isn't?

Also using your terms 'a means to end' then why not flash Magisksu then convert to Supersu with Flashfire?

Simply back up the stock boot image with twrp, look in the twrp backup folder for the image, rename it to boot.img.

Open Flashfire, select Flash Firmware Package, find the boot.img, enable EverRoot and flash.

Finally remove magisk.img and the Magisk folder to completely remove all traces of Magisk.
[Android Software/Hacking General [Developers Only]] JPCoetzee:
Nougat via CF-Auto-Root and Flashfire?

I've just bought a new unlocked S7 with Android 7.0. Can I root stock Android 7.0 with CF-Auto-Root like this:

1. Use CF-Auto-Root and therefore install Android 6.0.1

2. Install FlashFire

3. Install Android 7.0 via Flashfire

?

many thanks
[Android Software/Hacking General [Developers Only]] cytown:
SM-9200 newest firmware

[MENTION=631273]Chainfire[/MENTION],

The newest build number is MMB29K.G9200ZCU2DQC1, do I need to send the newest official recovery to you or I can try use your current MMB29K.G9200ZHU2DPC6 to get root?

If so, will it have change to brick my phone? Or will it wipe all my data?

BTW: will the official update system feature still working after flash auto-root?
[Android Software/Hacking General [Developers Only]] Mario3D13:
Hey [MENTION=631273]Chainfire[/MENTION], I'd like to have CF-Auto-Root for AT&T Galaxy Note Edge (SM-N915A), but I don't know how to extract the recovery.img file from the tar.md5 files provided for the device. Could you please clue me in on how to do so?

-Mario3D13

---------- Post added at 06:48 PM ---------- Previous post was at 06:11 PM ----------

Hey [MENTION=631273]Chainfire[/MENTION]

I've successfully extracted the recovery.img for the AT&T variant of the Galaxy Note Edge (SM-N915A). The build number is MMB29M.N915AUCS2DPK4 and the file can be found at this link: https://drive.google.com/open?id=0B1jBlXhYcgp2ejZheHhybW05Z1U

Looking forward to the CF-A-R file for this device!

- Mario3D13
[Android Software/Hacking General [Developers Only]] ShinySide:
Att = locked bootloader = no cfauto root
[Android Software/Hacking General [Developers Only]] Mario3D13:
Darn it, knew the idea was far-fetched. Thanks for letting me know though!

- Mario3D13
[Android Software/Hacking General [Developers Only]] tmiket:
I also have a note 4 tmobile. Will auto root work with EQC1 firmware?

Autoroot website has older build.

Mine is totallally stock.

My plan was to root get back deleted photos and unroot.
[Android Software/Hacking General [Developers Only]] tmiket:
I tried it and now

RECORVERY IS NOT SEANDROID ENFORCING,

How do I fix this? I want to fix this without wiping all data. I hope I'm not screwed.
[Android Software/Hacking General [Developers Only]] ashyx:
Flash twrp, install SuperSU. Done.
[Android Software/Hacking General [Developers Only]] tmiket:
I assume that will root it and fix the boot problem and leave undeleted data.

If data is wiped no point in rooting my moms phone. I'd undo what I did and use diskdigger without root to get thumbnails of pics which is better than nothing.
[Android Software/Hacking General [Developers Only]] ashyx:
No data will be wiped.
[Android Software/Hacking General [Developers Only]] tmiket:
Cool. Before AF old build I tried kingroot apk. Installed told me it couldn't root phone and to put in request. I uninstalled then but hope it wont screw up SU install somehow.
[Android Software/Hacking General [Developers Only]] tmiket:
Is TWRP model specific like AutoRoot?

Did AutoRoot flash my recovery to EPG2 or is it still newer EQC1?

I don't understand what AutoRoot screwed up with boot.
[Android Software/Hacking General [Developers Only]] ashyx:
TWRP is model specific. See your relevant device forum or twrp website.
[Android Software/Hacking General [Developers Only]] greardon:
CF-Auto-Root for Samsung T807P 6.0.1

Auto Root doesn't not work with the latest ROM Release.

Attached is the recovery.img from that version.
[Android Software/Hacking General [Developers Only]] ShinySide:
I suppose he's just supposed to guess what device and hope for the best? Lol
[Android Software/Hacking General [Developers Only]] cytown:
SM-9200 newest firmware

The newest build number is MMB29K.G9200ZCU2DQC1, the attached please find the recovery.img in zip format.
[Android Software/Hacking General [Developers Only]] MysterySeby:
Hi, Chainfire,

Today I've decided to upgrade from Android 5.0 to Android 6.0.1. On the old version I had root, but the version I've tried from your website MMB29M.G900FXXS1CQC2 for the new version of android it's not working. After the phone boots back it's still without root and when I restart it in download mode it says that it's a custom version instead of the Official one.

You have a screenshot with my phone details. I don't know if make any difference but in CPU-Z it says that the model is Qualcomm MSM8974PRO-AC.

Please, can you help me with a working version?

Thank you!
[Android Software/Hacking General [Developers Only]] angel_boulevard:
Hi chainfire

Note 5 verizon sm- n920v flash through odin alway fail
[Android Software/Hacking General [Developers Only]] ashyx:
Afaik you can't flash anything on a Verizon device. It's locked.
[Android Software/Hacking General [Developers Only]] angel_boulevard:
why it appear on cfauto root hompage?
[Android Software/Hacking General [Developers Only]] ashyx:
I'm as confused as you are. Traditionally Verizon devices always have a locked bootloader.

Do a little research on whether the device has a locked bootloader or not.

If it is locked I'm not sure why there is a CFautoroot for it? :confused:
[Android Software/Hacking General [Developers Only]] MrMike2182:
I'm curious as to why there's a version of CFautoroot for the N920VVRU3CQB9 Verizon also.. I tried it to and it got stuck 1/3 of the way through while flashing recovery and got stuck there..
[Android Software/Hacking General [Developers Only]] Icetech3:
Bah.. same.. almost had a heart attack when i thought someone finally was able to crack it:)
[Android Software/Hacking General [Developers Only]] droidzer1:
Ah - I should have found this thread before I PM'd Chainfire but I see the question is out there now so hopefully Chainfire has some more info about this. I'm wondering if having that ENG Root installed first might make a difference although that was for the 6.0.1 version and not Nougat.
[Android Software/Hacking General [Developers Only]] SNBogdanov:
Hi. Today I tried to root Samsung S7 Edge with new auto-root for 7.0

First of all it is very strange size of recovery.img

It is 6x times more then stock recovery.

During flashing Odin hangs on writing recovery.img and after 5 minutes gives fail.

Flashing stock recovery was successfull.
[Android Software/Hacking General [Developers Only]] cytown:
report back: MMB29K.G9200ZCU2DQC1 works very well!
[Android Software/Hacking General [Developers Only]] NeoandGeo:
Noticed that the SM-N920v has an entry and download available now. Is there something in the pipeline for this device hopefully?
[Android Software/Hacking General [Developers Only]] droidzer1:
I noticed that too a couple days ago and you might look here starting around page 14 or so to page 17 where we are talking about it:

https://xdaforums.com/verizon-galaxy-note5/general/finally-root-verizon-note-5-t3368127/page17

Two people tried it but it seemed to fail. Chainfire has never as far as I know supplied CF auto root for phones with a locked bootloader like the Note 5 Verizon. So it seems strange it's here. I tried it on Marshmallow but it is for Nougat. It failed on MM. I saw it go from 11 downloads to 152 downloads in the last two days so it seems it was just put up there very recently. It would be good to hear from Chainfire on this. I didn't lose anything trying - just rebooted after Odin said fail and everything was fine. This cf auto root expands out to around 300 Megabytes so I'm guessing this is some new type of tactic for root. Sounds like SNBogdanov found a similar thing with the S7 edge but apparently it also failed. Need some input on this.
[Android Software/Hacking General [Developers Only]] ashyx:
I know exactly how CF-AUTOROOT works. If there was a new exploit I'm sure it would have been announced somewhere.

As it stands its impossible for CF-autoroot to work on a bootloader locked device.

I'm going to pull it apart tonight and I'll report what's in that image that is making it 300mb.
[Android Software/Hacking General [Developers Only]] droidzer1:
Thanks - I'll be interested in your findings. I looked at it with a hex viewer and it seems there is a lot of empty space ( 00's ) in the middle of it. I'd guess about 70% of it is empty space.
[Android Software/Hacking General [Developers Only]] ashyx:
You were right, most of the image is simply just padding to increase the image size. The recovery image itself is 255mb, maybe this is required for it to correctly flash to the recovery partition.

How big is the recovery partition on this device anyway?

The strange thing is the untouched recovery image seems to have a signature, just like a stock Samsung recovery image would have. However I'm not sure who could have signed it and with what?

When the padding is removed the recovery image is actually only 28mb and the cache image is 40mb.

I unpacked both of the images and there is nothing else special about either, they both contain all the files I would expect for CF-autoroot to work.

The recovery properties indeed state it is for the SM-N920V, firmware version N920VVRU3CQB9, however as we know it just can't work with a locked bootloader.

Why this is on the Cf-autoroot website I have no idea?
[Android Software/Hacking General [Developers Only]] MrMike2182:
That actually is very close to the correct size of the recovery image but I really don't see why it wouldn't work on a locked bootloader because the S6 Edge I have is rooted and using a rom flashed via flashfire and working fine on the locked bootloader.
[Android Software/Hacking General [Developers Only]] ashyx:
Because the bootloader does not allow unsigned binaries to flash. The recovery image is not signed by Samsung, so it gets refused.