yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] ashyx:
I doubt the sizes of the recoveries are the same nor the md5, I don't even think that's possible. Are you sure you compared 2 different recovery images?

Anyway regardless both recovery images are stock, what I'm referring to is the actual recovery binary in the sbin folder(this is where the magic happens)

The init starts the recovery binary which in the case of CF-autoroot is fake and is just a script to run the the CFautoroot binary in the sbin folder(this is the actual recovery)

This then mounts the partitions and runs the supersu zip, which does the actual rooting. When that's done the cleanup script installs the stock recovery in the cache image and reboots the device.

There are other modified files in the sbin folder and some that have been added, so I don't t see how the file sizes and md5 of both recovery images could be the same.
[Miscellaneous Android Development] Hypexed:
I thought I had. I mounted the cache image and compared. And got the same results. Then found another folder I extracted with a recovery that differed. I then extracted the recovery image again to compare. And it looks like I must have overwritten the fake recovery with the stock then forgot about it. If I had known it was PEBKAC interference I wouldn't have asked! :P

It's funny as now I see this. It looks like I backed this up in one folder. Then made a copy of stock into another folder.

I don't see how I came up with duplicate images after extracting them again but somehow did. I knew I was getting old but this is a new low.

I wonder what would be the best way to modify it for use. Cache looks easy enough to modify but hardest to repack. OTOH recovery could be hooked into but whether mods to "/system" could be performed is another matter. Halting after the adbd server is started so ADB could be used would also be okay. While the fake recovery is still in operation.
[Miscellaneous Android Development] simon8261:
Samsung Galaxy A3 2017 SM320FL

I would be grateful for some guidance regarding the correct method to unlock the bootloader for this phone. Samsung Galaxy A3 2017 SM320FL

I have searched the threads and Googled it endlessy only to get conflicting guidance none of which is working. I want to simply use CF Autoroot retain stock recovery and gain root access allowing me to edit certain system files and debloat the phone.

I have downloaded the correct stock recovery image for this model and Chainfires boot and recovery MD5 tar file both in the later Nugat v7.0 and previous Marshmellow versions. Odin v3.12 is loaded and will connect to the phone and adb device commands work fastboot dosen't work but I am not sure if it should on a Samsung as I understand Odin download mode is the correct method.

OEM Unlock and USB debugging have been set.

I have seen and tried evey type of unlock guidance from using "Fastboot" or downloading "Modaco Superboot package" which appears to be for Motorola phones when you open and inspect the batch file. Nearly every site is giving incorrect information on how to access Download mode using ADB commands for Samsung and quoting the stock Android command which just reboots the phone.

I know this model can be unlocked and rooted but cannot find how to do the initial unlock proceedure and don't wish to experiment with wrong methods and brick the phone.

Any help would be much appreciated.

Simon
[Miscellaneous Android Development] ashyx:
OK several things:

1. Your device doesn't have a locked bootloader.

2. Cf_autoroot doesn't retain your stock recovery, it merely replaces it with ANOTHER stock RECOVERY.

3. Stock recovery is completely useless and pointless on a rooted device

4. Samsung devices do not use FASTBOOT.
[Miscellaneous Android Development] simon8261:
Thank you for your prompt reply to my questions.

Looks like I am trying to unlock and already unlocked door, one less thing to do to achieve root.

Before posting I had run the Chainfire MD5 Tar through Odin with no errors and a success tick in the relevant box however it only took 4 secs and booted back into the normal system.

Knox hasen't been triped and I can now see the hosts file which is one of those I wish to edit but still unable to do so at present.

ES Manager is telling me I havent got root, have sideloaded SU v1.82 and again it is saying I require root.

I appreciate Samsung dosen't use Fastboot but a lot of the guides to rooting are clearly wrong as I suspected and giving incorrect information, not surprised there are a lot of bricked phones out there.

Can you give me a brief run through on the further steps I need to take to achieve root on this phone, looks like I have gone so far and need to finish the job but not sure how.

Simon
[Miscellaneous Android Development] ashyx:
CFautoroot should boot you into the root process automatically after flashing with Odin.

If it doesn't you may have to Uncheck auto reboot and reboot to recovery manually.

Failing that then use twrp to root your device.
[Miscellaneous Android Development] Hypexed:
Hello again.

Something in my display controller is faulty but somehow when ever I flash CFAR it does its work, the phone reboots, and the screen comes on. Now, the screen is more faded than it should be but I can see the CFAR progress at work. It looked like a successful root and then waited before rebooting. The phone then reboots fine. But the display doesn't turn on after. What is CFAR doing that can activate the screen that the system cannot? Can CFAR be halted by a key press and grant ADB access?
[Miscellaneous Android Development] GuyWithNoLife:
I'm pretty new to all this rooting stuff, so don't mind this noob question.

I wanted to root my samsung galaxy A3 2016 (my android ver. is 7.0) so I decided to use CF-Auto-Root. I followed all the steps and it seemed like my phone was rooted succesfully, but that wasn't the case. I checked if SuperSU was installed and it wasn't; I downloaded Root Checker and it confirmed that my phone wasn't rooted.

My question is, did I do something wrong? Did I miss something?
[Miscellaneous Android Development] Hypexed:
I examined my system files after and didn't see anything really different. But it should be in there somewhere, usually in a section you don't have permission to look in. What's supposed to happen is when you attempt to do a root access operation is a request should come up asking permission. You could also try installing the SuperSU app that goes with the CFAR.

https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
[Miscellaneous Android Development] ali4796:
hi,

is there any root method for galaxy note 8 (exynos one), that doesn't stop Samsung pay, S health and secure folder from working? and does not trip KNOX?

thanks
[Miscellaneous Android Development] OnePlusGaming:
Is there a root for SM-J727T or is there away to unlock the bootloader.
[Miscellaneous Android Development] Weelliingtoon:
Cf auto root j530g

Should I retrieve the original ROM recovery.img from it?

And is not to abuse too much, how long does it take to do?
[Miscellaneous Android Development] wrunning:
Hello! I own a Samsung Galaxy S5, model SM-G900F. Looking at the stock build that was on, mmb29m.g900fxxs1cqdd, I came to to the conclusion that I should download and flash the firmware from here desktop.firmware.mobi/device:370/firmware:8900. However, after trying to do so from Odin, the download mode screen stopped with a "unsupported dev" error.

Further on, I tried with the firmware here download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip and that worked without an issue. I'm wondering why specifically that is.

Currently, used the latter image and everything is working fine.

Thanks!
[Miscellaneous Android Development] ashyx:
Which version of odin did you use?
[Miscellaneous Android Development] wrunning:
It was 3.12.3.0, the latest I could find.While it is not the version that comes bundled in the zips, it is the one that I tried with both images and worked with just the one mentioned.
[Miscellaneous Android Development] G Slim:
I'm just curious, what is the purpose of listing the Snapdragon variants (SM-G935V for example) on firmware.mobi if the boot-loaders are locked and cannot be rooted?
[Miscellaneous Android Development] ciberglo:
Gentlemen, I have a g903M (Brazil ZTO variant) and tried flashing cf-auto-root for installed firmware (UBU1BPK1), but after ODIN Pass! it reboots and just show the message "Recovery is not seandroid enforced".

After that, it reboots again to normal firmware, not rooted.

Tried many times, no luck.

I even tried un-checking the "auto reboot" option in ODIN, and doing a manual reboot to recovery mode (as it was supposed to force the cf-root to install).

But it just repeats the same behaviour. I kept holding vol_up+button+power and it kept rebooting trying to enter recovery but just showing the message "recovery is not seandroid enforced".

At the time I released the buttons, it rebooted to normal firmware, not rooted.

Tried different Odin versions (3.10.6, 3.12...), nothing did the trick.

Any tips? May I have to try other phone variant, like F? (M variant is dual sim, don't know if others would disable second sim slot)

I've also enabled "USB debug" and "unlocked OEM" under developer settings.

Couldn't find "reactivation lock" option under account settings / security samsung settings.

I've also being told that other Brazilian variants (ZVV, ZTA, ZTR) are already on a more recent firmware, UBS1BQA1.

Should I try to upgrade firmware (even being other variant), and trying cf-root for the according new version (ubs1bqa1) ?

Thank you all in advance.
[Miscellaneous Android Development] IlConsiglieri:
Samsung J330FN J3 2017 Netherlands CF-Autroot question

EDIT: I have given up on CF-Autoroot. Ashyx has released a TWRP version that was suited for my phone. I have tested it, and its working like a charm. ==>Click here<==

I have tried and tried, and i am getting the feeling that either the bootloader of my phone is locked, or there is something else wrong.

The thing i could not try, because there is no quick way to open the back cover to flash, pull battery or power off otherwise, and go into recovery mode right after flashing with odin.

When im done flashing in download mode, i can only press all buttons at the same time to get out of download mode, and then try to use the recovery mode button combination, which does not work in any sequence or manner.

After searching and researching and trying for weeks now, i ended up on this package: cfar_samsung_sm-j330f_j3y17lteser_nrd90m.j330fxxu1aqi2_xet0 To no avail alas....

Device info:

Board=universal7570

Device=j3y17lte

Display=NRD90M.J330FXXU1AQI2

Hardware=samsungexynos7570

Manufacturer=Samsung

Model=SM-J330F

Product=j3y17lteser

Codename=REL

Version=7.0

Baseband: J330FXXU1AQF7

Samsung Experience version: 8.1

Kernel version: 3.18.14-11647328 dpi@SWDD5907 #1 Fri 8 Sept 18:52:51 KST 2017

Build number: NRD90M.J330FXXU1AQI2

Status SE for Android: Enforcing SEPF_SECMOBILE_7.0_0009

Fri Sep 08 19:15:53 2017

Knox version: 2.8

Security patch: 1 August 2017

I figure, if a cf-autoroot package is available, and the package site says it may unlock the bootloader if needed, and it doesnt, it must be something else.

At this point, i would be eternally greatfull if someone can help with this. :angel:
[Miscellaneous Android Development] MadC9ke:
unsupported dev_type

Hi.

I'm not sure if this is the correct place for such message so please let me know if it's not.

I'm having trouble rooting my Samsung SM-T355 tablet with android 7.1

The build number of my firmware matches perfectly the one mentioned in firmware.mobi till the last symbol ( T355XXU1CQJ6)

But when i try to root it it says "unsupported dev_type" and fails

I downloaded the firmware from SamMobile: sammobile.com/firmwares/galaxy-tab-a/SM-T355/SEK/download/T355XXU1CQJ6/197131/

And tried to root using cf-autoroot from here: desktop.firmware.mobi/device:720/firmware:14325

I tried to flash Boot+Recovery image from firmware.mobi but as i expected it changed nothing.

Also i tried cf-autoroot for similar build (NMF26X.T355XXU1CQJ2) - with same effect

When i rooted same device with android 6 it worked perfectly, even tho build numbers did not match
[Miscellaneous Android Development] ashyx:
Use the latest version of odin.

Failing that use twrp to flash supersu.
[Miscellaneous Android Development] ghkashki:
Hi, my friends, I have a 10.1-inch Samsung tablet, the gt-p7500, which was already on Android 4.4.

The problem is that I decided to change it to Android 6.1 Marshmallow. Unfortunately, I did not back up ... Unfortunately, the download package was not installed from the site and now the tablet is in recovery mode ... Now I figure out how to fix it. Please help me. Thanks for your help .....
[Miscellaneous Android Development] eduarcor75:
Hello there,

I was trying to root my Note 4, and I was not able to do it.

I am having the error unsupported dev_type, even though I am selecting the correct model (Note 4 SM-N910F) and build (MMB29M.N910FXXS1DQH7). Here.

I though the phone became a brick, but then I applied the Recovery Image and it come back to work again.

I used the version of odin that came with the CF-Auto-Root.

Can anyone help me to root the phone?

Thank you very much,

E.

PS.: I was able to root it with this. Even though, as this method is deprecated, maybe worth it to take a look, and see why is not working with the most recent method firmware.mobi which didn't work at all.
[Miscellaneous Android Development] pyronia:
Cant upload boot.img to the site, around 20% load then the page is refresh to login page
[Miscellaneous Android Development] hlygrail:
Works on SM-G920A (AT&T Galaxy S6) running Nougat 7.0?

So I sent my rooted (Android 5.0.2 bliss) S6 back to Samsung for a battery swap a year ago, and they didn't actually replace the battery but swapped the charging port (which was NOT the problem). It came back otherwise unaffected, so I just lived with it. Sent it back again last week for battery swap and this time it came back with a new battery and was updated to Android 7.0. KHAAAAANNNN!!!!

I cannot live without root on my primary mobile device -- can't restore my app backups (Candy Crush level 1500+ people!.. ok, that's just one of the things, but still), can't install an ad-blocker, so many things I can no longer do.

Will this work on my SM-G920A running G920AUCS6EQJ1 baseband, Oct 1, 2017 security patch?? If not, any other kind suggestions before I punch a hole in my wall in frustration? It's such a great phone with root, and a really sluggish turd without.
[Miscellaneous Android Development] Hypexed:
What did you use to backup data? Something like Titanium? Even though I CF rooted it, I used Helium to backup app data from a broken phone. And it restored app data fine to my new stock unrooted phone.

All you need is a restore program that do it without root. Since it can work. Don't know if data needs converting but one way is to use ADB internally which an app can do. Then you see a message on screen. If the backup is in adb backup format it should be possible to do something with it.
[Miscellaneous Android Development] hlygrail:
Yes, I used Titanium Backup. So I have those packages, but since I can't access /data/data (or whatever) to replace/overwrite the settings files, I can't really restore the app backups. Most of the things I can just reconfigure -- painful, but do-able -- but there are a few that I can't, like Candy Crush (a trite example, but yeah).

Is there a way to use ADB to push these app packages back into my now-unrooted phone?
[Miscellaneous Android Development] bush911:
has anyone tried the cf-auto-root from link at OP on 1st Pixel with latest build 8.1. I tried, but when fastboot boot the boot.img , it said failed remote dtb not found.

Any suggestions?
[Miscellaneous Android Development] Hypexed:
I know where you are at. But in my case my trite example would be my Worms2 game saves. However, I ran Helium to back it up, which uses ADB to do a "poor mans" backup on stock-ware. Then on my new stock phone it was able to restore that app data so I could continue playing. All without root. Killed my apps. Restored. Loaded up a game, data back! :)

There must be. Helium does it. I even checked its backup files and apart from meta data file around each app backup the app data is stored in an ".ab" file which is an ADB backup file of sorts. It has the ID of "ANDROID BACKUP".

So you have the image of your rooted phone and data? As well as a Titanium backup? What comes to mind is running that image through an emulator and using Helium. Or, looking into the Titanium format and if it can be converted into ADB or Helium.

I suppose it would be out of the question to image the older firmware back and then use Helium or ADB? Then image the newer back with Helium? Bit silly since data is technically already backed up. So it comes down to data conversion I think.
[Miscellaneous Android Development] hlygrail:
I have a full Titanium backup of the rooted S6 running Android 5.0.2 before I sent it off, but not an ADB image backup. So I have access to the APK stuff easily -- I haven't tried, but I seriously doubt that extracting and reinstalling just the APK will get me back the data and configuration parts (like the fact that I was at level 1460-something in Candy Crush).

Nope, no way to go back now that the bast___ds at Samsung pushed a new 7.0 image on it. No one has apparently been able to unlock the bootloader on the S6 since Android 5.x (which is specifically why I bought that phone and had it rooted within 15 minutes of taking possession a little more than 3 years ago). So that's a no-go.

HOWEVER, I think that now that I understand that Helium and Carbon and all those types of backup apps are just front-ends for ADB, I might be able to use 'adb push' to shove my backed-up version of Candy Crush (and other apps) over. ADB has full access to /data/data, it sounds like, so that may be the only doorway through. What I'm not sure of is whether the Titanium package has enough information or is in the right format for 'adb push' to do its job... or even what specific file(s) hold the magic keys to unlocking my Candy Crush levels again so I know what to push over.

I'll give that a spin when I care enough to throw away another 2 hours on this and report back...
[Miscellaneous Android Development] snowgod06:
quick question..

stock Samsung S6 on N. SM-G925V

security patch date of 12.1.17

Base: G925VVRU4DQL1

Build: NRD90M

Looking at the chart on firmware.mobi, I'm assuming by picking the first option HERE should generate the zip file I need? I'm a little apprehensive as my old S4 was much easier to root.. Reading the steps on the main page, has me worried that a brick will happen because of the bootloader being locked, but i cant figure out if/how to unlock it before I proceed. I mean IF i did use CF-Auto, could you install TWRP in the same process and or after CF-Auto reboots the phone?

any insight would be appreciated. Just was given the S6 to replace my dead S4 and I'm missing my MODULES. lol
[Miscellaneous Android Development] bpleat:
Could you please be so kind as to point me to that spreadsheet?
[Miscellaneous Android Development] ashyx:
You've answered your own question. Your bootloader is locked so it's pointless attempting to root your device using this method or any other that needs a custom recovery.
[Android Apps and Games] carikjot1993:
Learn Japanese with fun games, grammar, expressions, alphabet, food and places.

Learn to speak Japanese with fun games, phrasebook, beginner and intermediate level courses. Listen to all the essential words and phrases you need to build a solid foundation of Japanese.

This app was created by a language teacher who found that students learn language more effectively through fun and repetition. Different learning styles are catered to with the many games and quizzes:

- Visual (picture quiz)

- Auditory (listening quiz)

- Read-Write (multichoice quiz, word guess)

Learn common words and phrases that are sorted into many useful categories.

Phrasebook sets include: greetings, hobbies, conversation, food, animals, language difficulties, travel phrases, adjectives, verbs, countries, clothing, colors, emergencies, shopping, directions, numbers, school, work, and telling the time.

Learn the 4 Japanese writing systems - Hiragana, Katakana, Kanji and Roomaji - and pronunciation in the Alphabet Section.

Listen to authentic, high quality audio of a beautiful Japanese native speaker with clear pronunciation.

This app will help you learn Japanese for travel in Japan, work, school, fun, or to talk to your friends or partner.

All Japanese words and phrases are in Kanji, Hiragana, Katakana and Roomaji.

Study a new language set every day and practice it in the Games Section.

Learn language tips and grammar in the Grammar Section.

Quickly find a word in the Search Section.

Change user language and romanisation (roomaji) in the App Settings.

Read about Japanese food and famous places.

Words and phrases have been translated by native speakers into English, French, German, Spanish, Chinese (simplified and traditional characters), Arabic, Czech, Dutch, Indonesian, Italian, Japanese Korean, Portuguese, Polish, Russian, Swedish, Thai, Turkish and Vietnamese.

All language is carefully translated by native speakers and NOT by computers/online translators.

Created by a team of Japanese native speakers, language teacher and iOS developer.

If you have any feedback, please let us know what you think.

There will be regular updates and improvements in the future.

https://play.google.com/store/apps/details?id=com.silvermoonapps.learnjapaneselanguageguide&hl=en

https://itunes.apple.com/nz/app/learn-japanese-language-luvlingua/id1048854903?mt=8
[Android Apps and Games] Arcadian123:
great app! But I want to learn for N3 now. Do you have any features supported?