yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Hypexed:
I suppose it is old by now. Even though I've had it less than two years. The specs are considered low budget now, even though it has a 64-bit quad core CPU at 1.2 Ghz, with 1GB RAM. I suppose 64-bit octa core at 2.4 Ghz with 2GB RAM is considered the respectable minimum these days. :P

Yes I had tried the CF root package you linked. In fact it was the only mod I have found for the G360G variant and I was grateful to find it. However my device now has a blank screen and doesn't respond to touch. I'm sure the LCD/screen is okay but the electronics are bad on the phone mainboard. Phoneboard? When I tried CF auto root the first time it rebooted and I could see some text on screen. But it was too corrupted to make out, just a flickering white mess, and when CFAR had done its work the screen didn't come back after it rebooted. That wasn't the fault of CFAR, my phone had a fault and went bad prior to the CFAR install.

So, ATM, given my situation, I'm tossing up between rebuilding a recovery image with ADB enabled and modifying the CF cache image. The cache script just looks like it removes root programs and includes some recovery image and a zip. Obviously it has some form of automation that is beyond my knowledge.

So the easiest may be to modify a recovery to enable ADB. I could call it PMR. Poor Mans Recovery. LOL. :P

The only thing is I see guides saying to echo the variables into the prop files, but if the variable already exists that would cause a duplicate. Unless I'm missing something here. To me the best would be some edit command that can modify existing text so a "=1" appears on the end or add the line otherwise. Or just editing the file directly somehow if it has nano or similar. :)
[Miscellaneous Android Development] matambanadzo:
I tried the CF-Auto-Root automatic image from https://desktop.firmware.mobi/device:376/firmware:4313

It matched perfectly to my version of Galaxy S5 G900I (XSA).

But sadly it failed halfway through and soft-bricked my phone :( Everything was set to auto when going through the process of downloading your version of CF.

Phone wasn't able to boot saying it had to be connected to Kies.

I then downloaded the 'deprecated' CF-Auto-Root version, installed via Odin and boom - phone is working again and rooted. :highfive:
[Miscellaneous Android Development] tomaasz:
Hi

Thank you for great tool!

I generated ".tar" file for Odin

"samsung_sm-g950f_dreamltexx_nrd90m.g950fxxu1aqi7_boot_recovery.tar"

Should I flash it by "AP" or "BL" in Odin ?
[Miscellaneous Android Development] Hypexed:
That should be "AP" that you flash it too.

You don't want to overwrite the "BL" as that is the Boot Loader. Some definitions:

BL (Bootloader)

AP (Application Processor)
[Miscellaneous Android Development] tomaasz:
Thanks,

I was not sure if "Boot Image" is the same "Bootloader" (BL)

But now I see that "Boot Image" is more kernel related then "Bootloader"
[Miscellaneous Android Development] ashyx:
Tbh it doesn't really matter, you can use AP for everything.

ODIN flashes based on the partition name, not the section you use.

BL will also flash boot images just fine.
[Miscellaneous Android Development] praveenvj:
Can someone help me please. I ran the root.bat file and selected the IMG file. Since then my device has gone into a boot loop. It shows on the Top right corner "KERNEL IS NOT SEANDROID ENFORCING" alternatively in Red and Blue and then reboots to the Logo screen and repeats the same.

Device is SM-T705

PC is Windows 10.
[Miscellaneous Android Development] ashyx:
Your device already has working root solutions in the Tab S forum.

I also have no idea what you just flashed and how. CFautoroot is a tar package flashed with odin.
[Miscellaneous Android Development] Hypexed:
You could try this. But this site wants a registration and I don't know of its validity. Got a firmware backup?

https://www.sammobile.com/firmwares/galaxy-tabs/SM-T705/
[Miscellaneous Android Development] praveenvj:
Thanks for your responses. There was an issue with the ROM i think, because I re-downloaded all the packages and was able to get the Tab working.

I downloaded the Stock ROM from Sammobile, re-installed it and then rooted using CF AutoRoot and then followed by TWRP to get everything working.
[Miscellaneous Android Development] JerryGoyal:
[MENTION=631273]Chainfire[/MENTION] My Samsung Galaxy Tab A SM-T355Y model is running on 7.1.1. but your firmware release is for 6.0.1. link: https://desktop.firmware.mobi/device:722/firmware:2143

Would it be possible for you to support 7.1.1? Let me know if you need further details.

If answer is no (which I hope not) then can i install your firmware 6.0.1 on top of nougat 7.1.1?

---------- Post added at 11:30 PM ---------- Previous post was at 11:21 PM ----------

Also, Would it help if I upload images from android 7.1.1 on https://desktop.firmware.mobi/authed? because i'm not sure if your system works on nougat or not.
[Miscellaneous Android Development] expose_it:
Hi, I have the p4noteltevzw and want to unlock the bootloader. On your site it says

"BOOTLOADER UNLOCK

If your bootloader is not unlocked, depending on the device, it may be automatically unlocked (wiping all data), flashing may fail, or the device may brick altogether."

So I tried to generate the auto root package and keep ERROR NOT APPLICABLE, even though the recovery and boot images are downloadable on the previous page. I have checked this thread: https://xdaforums.com/showthread.php?t=2263263 however the CASUAL download is no longer available and I get no response from AdamOutler when asking for the file.

1) If I can get ahold of the CF-Auto-Root package, will it unlock the bootloader for the SCH-I925?

2) Is there a way to still get a copy of the Take Note Verizon CASUAL(R478b) package?

3) If I disassemble the stock rom and replace the boot and recovery files with the ones from firmware.mobi, will that give me a custom bootloader?

I'm not sure after checking your site if the boot and recovery files are the stock images or not. My whole goal is to just be able to flash a custom rom and it seems that Verizon has locked this tablet down pretty well.

Any help would be appreciated.
[Miscellaneous Android Development] SanketMohapatra:
Do you have any kind of proper instructions for development for the Snapdragon 210 because we are a community having the phone with the same same chip but we are unsuccessful in an attempt to Port a custom rom as well as a custom recovery for our phone.

Actually we discovered the thing that the bootloader is locked and the fastboot command are not working for our phone as it is a kind of Lock by the company.

We spoke to the developers of the redmi note 3 mobile phone and they told us that if there is no way to unlock the bootloader then please try to edit the emmc_appsboot.mbn but they could not tell us which are the values to be modified because they all are in hex and we don't have any idea about that.

So I am requesting all the members of this forum to please guide us in our development to unlock bootloader so that we can continue our development.

Cooperation is highly appreciated.
[Miscellaneous Android Development] K1nGKeLa:
Hey guys

I have Samsung Galaxy S6 SM-G920W8 and for the last couple days I've been trying to root it with CF Auto root...

I downloaded the image for my version (G920W8VLU5DQI2) and flashed it successfully but after reboot i didn't get any root however KNOX ticked.

Could you please help me to solve this problem

Thanks in advance

P.S. I turned off reactivation lock
[Miscellaneous Android Development] User540705538:
Failed to root

Flashed on sm-a320y with odin.

Odin reported pass but when I rebooted the phone was not rooted and it didnt have the supersu app.

I do have twrp installed, could that be a problem?

ps. I can't use twrp to root because it fails to mount data, if you have a fix for this as well that would be great.
[Miscellaneous Android Development] ashyx:
FORMAT(not wipe) your data partition then install SuperSU in the same session to root with twrp.

You will lose ALL your data on internal storage.
[Miscellaneous Android Development] User540705538:
Thanks, I've had this problem on several devices. Do I format the data partition in twrp?
[Miscellaneous Android Development] ashyx:
Yes FORMAT (not wipe) withe TWRP. If you want it permanent use my encryption disable patch in my sig.
[Miscellaneous Android Development] User540705538:
Thanks, you've been a huge help
[Miscellaneous Android Development] Kairosin:
generating a CFAR does not work on SM-j700T even though they have N 7.1.1 firmware on it. I try to generate and all that happens is that Seandroid is not enforcing.
[Miscellaneous Android Development] expose_it:
Is there any known method to unlock the bootloader of the p4noteltevzw (SCH-I925)?
[Miscellaneous Android Development] shaggyskunk:
Have a look at this Thread:

https://xdaforums.com/showthread.php?p=39021431

Just a quick Google Search produced the result ?

https://xdaforums.com/showthread.php?p=39021431

Sent from my SM-G955W ??
[Miscellaneous Android Development] expose_it:
That thread actually pertains to rooting using frodo exploit.

Im looking to unlock the bootloader.
[Miscellaneous Android Development] shaggyskunk:
If you Search any of Chainfire's Threads - You'll see that he doesn't support anything to do with locked bootloaders - And he never has... I was thinking that you wanted to unlock the bootloader to get Root ?

Sent from my SM-G955W ??
[Miscellaneous Android Development] expose_it:
Yeah I know, I was asking if anyone could help... the only thing I've found is the casual r478b.jar by adam outler but he won't reup the file and nobody seems to have it... so I was just hoping someone had any sort of idea how I can unlock this device. Ive already got root.
[Miscellaneous Android Development] shaggyskunk:
I'm guessing that you have Google Searched for "casual r478b.jar"?

Sent from my SM-G955W ??
[Miscellaneous Android Development] expose_it:
I've searched the hell out of it. The file is gone and adam won't reup it.
[Miscellaneous Android Development] acr123:
root for SM-S327VL

I have a Samsung Galaxy J3 Luna pro ( SM-S327VL ) using Veizon from Tracfone. I went through the process & generated the CFAR with my exact build that was listed. I left everything else on the default settings. I know on this phone the bootloader is locked. & reading the thread implies that this will not work to get root with a locked bootloader. Does this package take care of this, is there something I need to do first, or will this never work. If this will never work, what is the purpose of generated the CFAR package?

I have not tried to use the CFAR package yet, but have downloaded everything.

What should I do next?

Thanks,

Al
[Miscellaneous Android Development] ashyx:
Dont bother it wont flash.

What's the purpose of generating the package?

That's up to you to decide, it's up to the human brain to make the decision if it's going to work or not?

How do you expect the CFAR creation script to know if your device has a locked bootloader or not? :rolleyes:
[Miscellaneous Android Development] acr123:
Thanks for the info. I was initially very excited that the Galaxy Luna Pro 's with my exact build was listed since it has a locked bootloader & would be extremely difficult to root. However, as you pointed out , there could be other reasons to generate the CFAR package.

Thanks again,

Al
[Miscellaneous Android Development] sujan_2048:
Does this work for J7 pro 730F?
[Miscellaneous Android Development] dhart62:
Obtaining root

I have unlocked devices with locked boot loaders with kingoroot, then delete all files pertaining to kingoroot and replace with super super. The newerror phones are a bit trickier. Go into developer's option and tick enable oem unlocking and enable debug via USB.
[Miscellaneous Android Development] acr123:
I have tried kingoroot & many of the programs to try & get root. Unfortunately all w/o success. I have used google, but nobody seems to have had success that I could find. I have already ticked oem unlocking & enabled debug initially. maybe someone will figure out how to unlock the bootloader.

Thanks for all the suggestions.

Al
[Miscellaneous Android Development] dhart62:
How to geek has a walk through for unlocking the boot loader. I've never tried it but might take a look at it.

https: // www .howtogeek. com/239798 /how-to- unlock-your-android -phones- bootloader-the- official- way/
[Miscellaneous Android Development] XDA.NYC:
Sprint SPH-L900 on 4.1.2

New here and didn't want to resurrect a year old thread with no activity for the sprint galaxy note II.

-Should i update to the latest firmware for that phone 4.4.2? Currently on 4.1.2.

-way to back up the 4.1.2 firmware before starting the rooting process or after rooting??

I've seen how it's done and doesn't look difficult to root but wanted to ask about updating the firmware before i start.

I know i have to go to https:// autoroot.chainfire. eu for this phone since it's older and not found on https:// desktop.firmware. mobi

Thanks in advance.
[Miscellaneous Android Development] xstokerx:
https://desktop.firmware.mobi/device:1809

The files posted for pixel 2 and 2 XL don't work
[Miscellaneous Android Development] ASimke:
a510f

I want to root my phone A510F (A5 2016) but can't found build NRD90M.A510FXXU4CQF6?

Android 7.0

Can i use some othere or?
[Miscellaneous Android Development] donaldyg81:
I generate and download the root package for G610F/DS compilation mmb29k.g610fddu1aqc4, put device in download mode, extract file, read everything and when odin open it I load the image.tar.md5 file in the AP section of odin and flash it... after that the device reboot but nothing happen... no superSU.

I installed superSU manually but when I started superSU say me that no SU binary exist... what I´m doing worng ??? Please help me...

PD: Sorry my english
[Miscellaneous Android Development] ASimke:
Root but didn't root

I install cf-auto root whit odin,phone restarted 2 times all good ,start but phone isn't rooted.When i downloaded super su,can't start it but when i go to software update i can't use is on custom rom.Any help?

Sorry for english.

When i try twrp my phone goes back to Official I don't know how.
[Miscellaneous Android Development] khalidchohans:
Galaxy J3 (2017) J327P Root Done

Here is tested root J327P (Remove all spaces from Link)

http : // www .mediafire .com / file / pr0f3a4cqol071w / J3+Emerge+Sm-J327p+v6.0.1.rar#!

Enjoy
[Miscellaneous Android Development] HACK3DANDR0ID:
Your device has a Qualcomm Chipset, The j327T/T1 has exxyos chipset as does the J727T/T1. But thanks anyway!
[Miscellaneous Android Development] GizmoSmith:
Tried CF-Auto-Root on a N910U (Note 4 Exynos Vodafone NZ) nothing happend

Tried CF-Autoroot on a Note4 N910U, but nothing seems to happen !!!

1) Went to this page (as it matched the firmware version the phone currently has as shown by Phone INFO app

https://desktop.firmware.mobi/device:592/firmware:5813

2) Clicked CF-AUTO-ROOT, It downloaded

cfar_samsung_sm-n910u_trhpltexx_mmb29k.n910uxxu2dpf1_t0

3) Unzipped it

4) Flashed the image.tar.md5. Instead of 15 minutes as the guide says, the process was over in 5-10 seconds!!

After that the phone rebooted & pretty much nothing happened. Started Titanium Backup & it is still not getting root permissions..

When I go to download mode, I see Current binary & System status as :" custom",

I think previously it was "official". That's the only difference I could see.

Am I missing something ???? Anything else I do to go to root mode, without losing years of data ???
[Miscellaneous Android Development] grapebuddy:
Samsung A5 SM-A520W. Android 7 Root doesn't work

I have been trying to root my Galaxy A5 which was newly updated to Android 7 (it was rooted before with android 6) but the CF-Auto-Root generated from firmware.mobi doesn't seem to do anything. Odin completes and says it worked but there is no root access. Can anyone offer assistance?
[Miscellaneous Android Development] Hypexed:
I'm seeing the same thing. So to speak. I pulled apart the CF-Auto-Root package for my rare Samsung G360G, and although I don't know fully how it works, I can see no way for it to install. There is a a stock recovery image and a cache image. In the cache there is a cfroot folder which contains a recovery image, so a bit digitally redundant, a cfar-cleanup.sh and a supersu.zip. How does it know to execute that? The script looks like it is a removal script. Does the Android system look in all folders for zip files and attempt to run what is inside? Does it look for random scripts and run them? This may look noobish but that is how it looks. This makes no sense!

Here is a list of files. Please explain! I can't find any explanation on the net for how these files root a phone. :-?

/home/damien/Development/CorePrime/build/cache:
total 8
drwxrwx---. 2 damien 2001 4096 Oct 14 23:44 cfroot
drwx------. 2 root root 4096 Jan 1 1970 lost+found

/home/damien/Development/CorePrime/build/cache/cfroot:
total 16464
-rw-r--r--. 1 root root 1371 May 5 2017 cfar-cleanup.sh
-rw-r--r-- 1 root root 10955024 Oct 11 23:34 recovery.img
-rw-r--r--. 1 root root 5897760 May 5 2017 supersu.zip
[Miscellaneous Android Development] ashyx:
The recovery image inside the cache image is not redundant, it's the stock recovery image which gets installed after the root process is finished.

The supersu zip is run by a script in the ram disk which in turn is run by a fake recovery, which is what odin installs.

There are 2 parts.

The recovery.img which installs and runs the fake recovery.

The cache.img which contains a regular supersu.zip, which does the actual rooting, the stock recovery and the clean up script.
[Miscellaneous Android Development] Cossack007:
CF-Autoroot Issue with Samsung Galaxy S5 Neo (SM-G903F)

Hello everyone,

I tried to root my phone with the CF-Autoroot option from firmware.mobi. Unfortunately without any success. If I use the CF-Autoroot file out of the list by chainfire it works just fine and my phone gets rooted. But as I mentioned before when I try to generate my own CF-Autoroot file with leaving anything (options / settings) on default it won't work. I tried a lot even with changing some options but still wouldn't work. Is there anything to mention how this issue can be fixed. I picked the right buildnumber matching to my phone : "MMB29K.G903FXXU1BQC1"! But after flashing with Odin having auto reboot and f reset time checked it still won't work. Odin shows the passed message just after a couple seconds. The phone doesn't install any su binary or show any path or success with root checker. Also I tried to Flash the twrp custom recovery which works just fine. As hard as I try I can't get root access with this CF-Autoroot create option. Besides from this I get the message: Recovery is not seandroid enforcing if I try to boot into recovery. But this is just normal when I try to modify my phone with root access or eather custom recovery. Am I right? I tried also without having f reset time or auto reboot checked in Odin. I tried different buildnumbers but overall no success to get root access on my phone. It's not even installing the su application. I would appreciate if someone could bring up some relevant or useful information to help me with my issue or telling me what I am doing wrong?

Kind regards,

Cossack
[Miscellaneous Android Development] GizmoSmith:
At least can anyone confirm if I had followed the correct sequence?

I am also not able to figure out if the boot loader is locked or not..In an Ubuntu machine.. 'adb devices' works but not 'fastboot devices'
[Miscellaneous Android Development] ashyx:
I'm confused by your post. You say you have successfully installed twrp yet you are trying to root with cf_autoroot.

Wouldn't it make more sense to just install SuperSU?
[Miscellaneous Android Development] Cossack007:
Sorry that i did confused you. I will try to explain it again.

Well i did installed twrp without any problem. I could just flash it over odin. I can normally boot into the recovery system. Except that i get the message: "Recovery is not Seandroid Enforcing" which i thought is not related to any error. Furthermore it's more about customizing and modifying the system. Am i right with this theory? A part from all of that. The main issue or problem is, that it doesn't work for me to root my Samsung Galaxy S5 Neo (SM-G903F) with the configured CF-Auto-Root file from firmware.mobi. I start odin, after extracting the zip archive i add the "image.tar" file to odin in the AP / PDA field, turn my phone into download mode, connect it via usb to the pc and hit the start button. Odin says passed afterwards. But i don't have any root access or grant on my phone. Also after checking with root checker no proof of root acces or grant could be found. If i install super su as you mentioned over the playstore it's just telling me after opening super su i can't start the application, cause i haven't got any root access. So what should i do?
[Miscellaneous Android Development] :
Awesome work! I used my device variants fingerprint to complete my init_sec.c so it's very useful!

By the way, could you add Honor and Huawei phones?
[Miscellaneous Android Development] ashyx:
SuperSU is a zip package which you install with TWRP. if you have a working TWRP for your device then search XDA for SuperSU beta and then install it with TWRP.

The SuperSU you downloaded is only the management app.
[Miscellaneous Android Development] Cossack007:
Allright got it. I will check it out right now and tell you if it worked properly. Only i want to know you sad i should pick the "Super Su Beta" from here: https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

But there is also a stable version "Super Su System-Mode" from here: https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 ! Which version i should flash with twrp? As the both versions (SuperSU v2.82 SR5) are equivalent to each other?

Also i want to know what is the different between flashing with "CF-Auto-Root" and flashing the "Super SU" with recovery?

Which method is more efficiently? Or do both the same thing?

If so i can't get it why they are two options / methods available?
[Miscellaneous Android Development] ashyx:
SuperSU sr5 is the latest version, there is a link to the stable version in that thread also. The other link to the system mode supersu is not what you want.

CF-autoroot is the same as SuperSU. CFautoroot is just a means to install SuperSU without needing a custom recovery.
[Miscellaneous Android Development] Cossack007:
Got it :)

Thanks a lot [MENTION=4899305]ashyx[/MENTION]. Just my only last question is: If you recommend the stable or the beta version?

I mean both should be allright but which one works better and more efficiently?

Whats the adavantage if i take the beta version?

Is the beta version more buggy?
[Miscellaneous Android Development] ashyx:
I always use the latest beta as it's the most up to date and usually the most compatible with the latest firmware releases and built by Chainfire himself.

However if you'd prefer the stable version, as long as it works as it should there's no real reason not to.
[Miscellaneous Android Development] Hypexed:
Thanks ashyx. That's what I understood it to be. And yet...

I still couldn't find this fake recovery. They all the look the same.

This is where things are unclear to me. I've found two recovery images, one recovery.img in the Odin archive root, and the other inside a cache.img.ext4 I extracted out. The file sizes of both are the same, as are the MD5 sums. Now it's possible the sizes will match but if the content differs as it should here with a customized recovery then it's highly unlikely they match. Unless some digital gymnastics have been performed so the MD5 sums match in order to pass a security check.

After more digging it seems this is the case. The sizes of the ramdisk inside differ. So some how they are different but made to look exactly alike. :-?