yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] SanketMohapatra:
Hey I am completely new to the Android porting and building , and I wanted to build for a device that has kernel sources but it doesn't have a device tree.

Anybody having any idea about how to start the development on my phone?
[Miscellaneous Android Development] tjohnso1:
Hello,

i have a Note 10.1 N8000, German version.

I tried this method: https://xdaforums.com/showthread.php?t=1957002

But it did not work. I followed the directions very precisely, but now the tablet/phone hangs on the Samsung start up....nothing else works. Is there anyone out there that can help me? I understand that Chainfire no longer is active in development, but perhaps he could help me here? Please...?

BTW, looking at your twitter feed it seems we may have been at the same Ski resort on Jan 5, judging by your posted picture...
[Miscellaneous Android Development] Chainfire:
I have not noticed any firmwares being missing?

Note that especially for Samsung firmwares, a lot of them use the same kernel/recovery. You need to look at PDA version, not CSC version.

I did some random checks on Google's site and SamFirmware, and the latest ones I see there are all present.

Regarding upload: yes I am aware this sometimes doesn't work for some people, but I have not been able to reproduce the problem on my end. If an upload doesn't show up in 15 minutes it didn't stick.
[Miscellaneous Android Development] tjohnso1:
I've two different firmwares:

N8000XXSDQA7_N8000OXADNE4_N8000XXUDNE1_HOME.tar.md5

and

N8000XXUDNL1_N8000EPLDNL2_N8000XXUDNH1_Home.tar.md5

Both i tried with a few versions of ODIN. The upload begins in ODIN, but then after maybe 2 seconds ends in failure. See attached screenshot.

I'm not sure what you mean by "You need to look at PDA version, not CSC version. What are these two versions and where do i get them from? Again, sorry for my ignorance on this...

I presume you have found the same versions that i mentioned above? N8000XX...etc. etc.?

When you mention 15 minutes, do you mean that the flashing takes this long and then "shows up" in the tablet?

Again, any help you could give me would be really appreciated. thanks.

pictures are attached in this previous post: https://xdaforums.com/galaxy-note-10-1/help/help-tried-to-flash-recovery-n8000-t3727031/page2
[Miscellaneous Android Development] androiduser19836:
Hey I have a ASUS Zenfone v live and I need a working root method can anyone help me
[Miscellaneous Android Development] norbkre:
Upload of a missing firmware

Tried today to upload NRD90M.G930FXXU1DQL4 (which is missing, but my last update at german Telekom). Upload worked to 100%, but I didn't get any "response" from site, nor do I see my upload under "Your uploads".

What's wrong with that?
[Miscellaneous Android Development] Alzter:
Won't boot into TWRP

So I tried installing this on my Samsung j120zn, and when I tried to launch into TWRP recovery, it just says in red on the top of the screen "RECOVERY IS NOT SEANDROID ENFORCING" and reboots. Any help?
[Miscellaneous Android Development] braincodeAB:
Problems with upload

I am experiencing the same issues several users are having with the desktop.firmware.mobi upload: seems to upload fine but then it quickly de-authenticates and re-authenticates (via HTTP redirects?) and nothing seems to stick in the upload sections.

I've tried with Safari, Chrome and Firefox Nightly with the same results, so I assume it's the input file issue perhaps? It is 22MB, is there any upload limit?

Here are two locations where I have uploaded my own samsung_KOT9H.i337UCUFNC1.zip, perhaps someone can reproduce the error with this input?:

mega.nz/#!TpwhzIYb!2Y5_w7_gQ7tBhn2wRMVPg2w5KoCzwAow8e_pAg6kK9k

send.firefox.com/download/edc08d9816/#5VcjGlyWrZP0kbtYMt3Svw
[Miscellaneous Android Development] nijohnson:
Yea. Same issue here. It seems clear that some folks are successfully uploading firmware, as new stuff appears. But I'll be darned if I can. I've tried with 4 browsers, on three different networks. Even tried from my tablet on 4g. No luck.

Here's the file (one of them as I tried the zip as well as individual files) that gave me trouble. As above, hopefully the results can be reproduced.

https://drive.google.com/file/d/1yixygSxpm0JqaKg819qhBvZuhFTdUlec/view?usp=sharing
[Miscellaneous Android Development] maciclazar:
Hi guys! Quick question.

When I want to root samsung devices I can only download CF-Auto-Root package file and flash it in AP slot in Odin to get root?

Also can I later flash twrp from twrp app once the device is rooted?

Asking because my friend wants me to root his galaxy a3 with nougat and encryption.
[Miscellaneous Android Development] Serp87:
Root for Galaxy A8/A8+ 2018 please!!!!!!!!!!

(Samsung Galaxy A8+ SM-A730F / A8 SM-A530F)
[Miscellaneous Android Development] ashyx:
Already done via TWRP. See relevant A8 and A8+ forums.
[Miscellaneous Android Development] osygen:
I have tried to root with cfar for galaxy tab A sm-p555 many times, but it fails and gives error "unsupport dev_type". Please what is the meaning and how can I work around it to have a successful root?
[Miscellaneous Android Development] ashyx:
Just flash supersu with twrp.
[Miscellaneous Android Development] phoenixflash:
Hello I am trying to root my Galaxy S4 i337m LRX22C.i337MVLUGOC4,

I am only finding packages for the LRX22C.i337MVLUGOH1 (same name same device same board though) through the Firmware.mobi site.

In the readme.txt it states that 'this package must be generated for the same device and a very similar firmware".

I have tried uploading my stock firmware but have been having troubles (as it seems other's have as well).

I was just wondering if this package would be a close enough match to work?

Sorry "noob" here and I just unbricked my device from a past owner so I am slightly cautious now haha.

Let me know if any other information would be needed,

Thank you for your help.
[Miscellaneous Android Development] magicstone1412:
I am trying to root my latest firmware of E210L (E210LKLUKPJ2) but it was failed. Could you please take a look to that version? Thank you so much

https://desktop.firmware.mobi/device:109/firmware:3642
[Miscellaneous Android Development] ashyx:
Why not just flash supersu with twrp?
[Miscellaneous Android Development] drvish:
hi. i want to root my galaxy tab A SM-T385. I downloaded the cf autoroot package from firmware.mobi. but when i tried to root my tab i get odin fail message. and flashing is stopped midway. i have to flash boot and recovery image to get my tab working. please tell me how to root it. i have checked all the options in odin they are all correct. i had same issue with my c9 pro. please tell me how to root as i dont want to root with twrp. i bricked my device twice with twrp so dont want to rely on twrp
[Miscellaneous Android Development] gsmzarzouna:
site is not working correctly

Same issue for me...
[Miscellaneous Android Development] likeablasXD:
Trying to upload Galaxy J7 Sky Pro (SM-S727VL) boot & recovery images into the platform to get CF-AUTO-ROOT working to no avail. Site refreshes and upload never sticks.

This model has no TWRP or other custom recovery root method currently available, trying to root this thing. Is this site closed to uploads now or is the upload broken?

Would appreciate any help, thanks!
[Miscellaneous Android Development] ashyx:
You can't root your device. It has a locked bootloader, so it's pointless.
[Miscellaneous Android Development] likeablasXD:
Device can be and is OEM unlocked, quick google search says that

(Probably more know than me on this, but I'm praying you're wrong right now, would love to root)

(Can't post photo of settings option having the OEM unlock option ticked, or source for quote on here, DM for proof)
[Miscellaneous Android Development] ashyx:
It's irrelevant whether there is the OEM UNLOCK option in settings, this will just disable FRP.

It doesn't unlock the bootloader on Samsung devices.

Tracfone lock the bootloader on their devices. This is why you won't find a root method for this device.
[Miscellaneous Android Development] cmslick3:
AT&T N950U CF Auto Root

I'm looking for help with an AT&T N950U, I downloaded the correct CF Auto Root file for the build number I have NMF26X.N950USQS2UBQL5.

When I try flashing through ODIN I get and error stating SHA256 is invalid.

Any advice?
[Miscellaneous Android Development] nijohnson:
Any update on the upload issues?
[Miscellaneous Android Development] ashyx:
ATT devices have locked bootloaders.
[Miscellaneous Android Development] cmslick3:
If I understand correctly there is nothing I can do to get this to work with the AT&T version of the phone. I preferred to use the CF Auto root method because it is simple and easy, but I guess AT&T doesn't like you messing with their phones.

I did try the SamFAIL method described in other threads and did get that to work, kinda...

Do you have any thoughts on rooting the AT&T Galaxy S6 Edge+ SM-G928A??
[Miscellaneous Android Development] ashyx:
Did you get any kind of root using SamFail?
[Miscellaneous Android Development] cmslick3:
With my AT&T Note 8, SM-N950U, I was able to get full root with SamFAIL process but I had to do some very funny things to get everything working again. By everything I mean VoLTE and WiFi calling...

I have two phones to root and I messed up the first one so I tried to recall from memory the steps but I'm not 100% sure. I will work on the other phone today and actually document the steps and can report back if you like. I don't want to accidentally thread jack this discussion.
[Miscellaneous Android Development] ashyx:
If you got root then why don't you just use Flashfire to update supersu, or is this for the other device?
[Miscellaneous Android Development] cmslick3:
On the Note 8 I think I have what I needed. I can install APKs and control the settings I need to change.

For the S6 Edge+ I think I'm just giving up on that phone.
[Miscellaneous Android Development] nijohnson:
Is there a size limitation on the files uploaded? Or is there a timeout issue that is shutting down/redirecting things?
[Miscellaneous Android Development] iBowToAndroid:
This procedure doesn't appear to work. I've tried it on G925T and G928T (making sure to select the current version/Build Number) and after flashing the image md5, both phones reboot with no SuperSU app and no adb shell root access either. I never had issues using the regular (old) CF page - used it for years for many different Samsung devices
[Miscellaneous Android Development] e3n.sato:
Cannot upload to *.mobi

Hello everyone! Why I can't upload all files to *.mobi site? I'm logged in Google account, then insert boot.img, recovery.img, cache.img.ext4 (I have two similar - in CSC and HOME *.tar.md5, which one is needed?) and zipped all of these files. Then the page reloaded and nothing, uploaded list empty... What I'm doing wrong. I have J2 2018 (SM-J250F) and stock 4-file (maybe 5-file) firmware. Pls, help me :)
[Miscellaneous Android Development] shai_m:
Need help with CF-Auto-Root on Samsung Note 4 SM-910F

Need help with CF-Auto-Root: either fails to flash or doesn't root.

Samsung Note 4

SM-910F

firmware MMB29M.N910FXXU1DPG3

h t t p s : / / desktop.firmware.mobi/device:582/firmware:5594 (noob so not allowed real links)

Downloaded, flashed with ODIN (v3.12.3). Fails. :(

Tried playing around with the various options of CF-Auto-Root on

h t t p s : / / desktop.firmware.mobi/device:582/firmware:5594/cfar?

but I don't really understand what I'm doing.

Sometime variations above do not fail, but when I use a root checker, or try Titanium Backup or the TWRP app, they all say the device is not rooted. :eek:

Help !

Thanks
[Miscellaneous Android Development] .::Alien::.:
Will you mate please update CF autoroot for SM-G955F having android oreo!
[Miscellaneous Android Development] shai_m:
Issue resolved by random CF-Auto-Root version

Hi me,

Issue resolved by DL-ing and installing this version: h t t p s : / / androiddatahost.com/v54h8m

Why does this work and the official version doesn't? No idea.

Perhaps the good people of firmware.mobi should look into it.

me
[Miscellaneous Android Development] galaxis3:
Rooting latest N920I Stock ROM

I have latest XSA Stock ROM:

N920IDVS4CRB1_N920IXSA3CQL3_N920IDVU4CRB1_HOME.tar (I am not sure, it could be that the note 5 is from Optus OPS, while XSA is general ROM, can that cause any issue???).

From https://desktop.firmware.mobi/ I downloaded supposedly appropriate CFAutoRoot:

cfar_samsung_sm-n920i_nobleltedv_nrd90m.n920idvs4crb1_t0

Installing this through ODIN but no supersu is installed and apps requesting root can not be granted it. Issue with Samsung login loop appears. No more stock Recovery is available.

Would you please be so kind to have a look and help me with Rooting my Stock ROM?
[Miscellaneous Android Development] shevtak:
Hi, is there any way to return to OTA updates after having tripped KNOX and blown the eFuse?

And if not, what is the suggested and easiest method to install updates and where to get them from?

I rooted a Samsung Galaxy A3 (2017) / sm-a320fl using CF-Auto-Root from firmware.mobi which worked pefectly.

Having voided the warranty is not a problem and I was aware of that, but now it seems that with a tripped KNOX and blown eFuse there may be no way to return to OTA updates even after reflashing a stock firmware. That would be terrible news since the phone is used by a friend who would prefer an automatic and trivial way to update. Btw: The sm-a320fl is not in the list of Triangle Away-supported devices, in case that's relevant.

I hope someone can help me find a solution.

Thanks for providing a great and easy-to-use tool with CF-Auto-Root

Edit: I was told in another thread that OTA updates will be reenabled if I flash the latest firmware. I will try that. Sorry for the unnecessary double post. However, if you have anything to add to that, I would be glad to hear your advice.
[Miscellaneous Android Development] xenowood:
T813 CF-Autoroot Fail

Hi

I have tried in the past several times to use CF Autoroot für my SM-T813. It did always fail, so also with the latest version. (samsung / Galaxy Tab S2 9.7 / sm-t813 / gts210vewifixx / gts210vewifi / msm8976).

I was using the T813XXS2BRC2 build (its my installed build) - I am curious If I am the only one that has problems with rooting the T813. I never had problems on my Galaxy Tab Pro or my S6 with CF Autoroot.

I would really like to root the Tab S2 finally again.

Thanks
[Miscellaneous Android Development] Shedaim:
Samsung Active Tab 2 - SM-T395 - Root does not work

Hi,

Tried flashing CF-Auto-Root + Boot & Recovery images via Odin on a Samsung Tablet that enforces Knox.

Device Model: SM-T395

Build Number: NMF26X.T395DXU2ARB2

Android Version: 7.1.1

Android security patch level: 1 February 2018

Odin v3.12

OEM unlock is on in developer options

BootLoader is unlocked.

Flashed Boot + recovery as BL, Flashed CF auto root image as AP.

Odin showed Success and device restarted itself.

While trying to enter to recovery mode, the Samsung logo appears + a red "Recovery is not SEAndroid enforcing" at the top of the screen. Then the phone restarts again and loads into regular Android (Not into recovery).

Tried restarting manually after flashing without the "auto reset" option marked; same same.

Tried at least 5 different combinations of CF-Auto-Root details; same same.

Also tried with another device running Build version: NMF26X.T395JXU1AQJ2 (Although the images I used were for NMF26X.T395JXU1AQJ3 - Mind the last digit) with same results.

Would appreciate some help on the matter.

Thanks
[Miscellaneous Android Development] :
I tried rooting my Galaxy S5 with this, and it doesn't work. The booatloader/something flashes correctly in Odin, but anything I try to install either from recovery or through ADB ends up with "e: failed to verify whole-file signature" error.

What do I do?
[Miscellaneous Android Development] ashyx:
You can't use recovery nor ADB to install CFautoroot. Odin only.
[Miscellaneous Android Development] :
You don't understand. I installed the CFautoroot thing, but it didn't help, and I still can't install any package.
[Miscellaneous Android Development] ashyx:
You mentioned attempting to flash with stock recovery.

What exactly are you attempting to flash?
[Miscellaneous Android Development] :
LineageOS for example.

The phone is somehow locked, and I can't get around it.
[Miscellaneous Android Development] ashyx:
You can't flash Lineage or any other custom rom with stock recovery.

You need a custom recovery such as TWRP.
[Miscellaneous Android Development] :
I can't flash TWRP. I get the same error.

Talking about the download mode.
[Miscellaneous Android Development] ashyx:
What error? You haven't mentioned any error in download mode? :confused:
[Miscellaneous Android Development] :
Sorry, I must be mixing several posts I made across different forums

When I try to flash TWRP through Odin, the download screen says

SECURE CHECK FAIL : recovery

Custom Binary(recovery) Blocked by R/L
[Miscellaneous Android Development] ashyx:
Reactivation Lock?

Disable in security settings first.
[Miscellaneous Android Development] :
I can't do that. The phone is freshly stock-ROM installed. I am being bugged by some stupid Samsung account that refuses to log in (processing failed error), so I don't have access to settings (like, the installation can't finish because I am stuck on this step). That's why I'm trying to install custom ROM so this crapware is not present. Thus far, no luck.
[Miscellaneous Android Development] ashyx:
You cannot bypass it without entering the correct Samsung account details and disabling RL.

Unfortunately I cannot help you any further due to security reasons.
[Miscellaneous Android Development] :
What security reasons?

I DO have the correct credentials, but the ****ing thing refuses to log in. That's what I'm trying to tell you.
[Miscellaneous Android Development] whitebeardedtrimmer:
whatever you do........DO not LOOK UP CROM SERVICE, SAMSUNG APK. hope this helps.
[Miscellaneous Android Development] HACK3DANDR0ID:
The J3 was many many many devices ago.... See some of my current devices below....
[Miscellaneous Android Development] GoeNToeR:
please add boot.img and recovery.img from xiaomi devices,thxs
[Miscellaneous Android Development] m.fk:
I too cannot upload to firmware.mobi

After extracting recovery and boot image from KDZ file, I've tried to upload them. But after some time the site just reloads. No messages, no uploaded files shown.
[Miscellaneous Android Development] StuttgartKiwi:
CF-Auto-Root on Pixel XL

Hi, I have a couple of questions regarding using CF-Auto-Root on my phone. I've got a Pixel XL (Marlin) running completely stock firmware, not rooted, with the latest April security update. I'd like to root it, but without using TWRP, just to keep things as original as possible. I believe CFAR is the best way to achieve this.

The bootloader of my phone *is* already unlocked (I unlocked it last year when using the PixelFix method to root the phone, although I unrooted it again a bit later).

What I'm not sure about is whether CFAR will wipe my phone after I run it. The README.txt file, which is included in the CFAR zip, says:

"If your bootloader is currently locked, or if you are currently not rooted, or you are rooted but your device's storage is encrypted, YOUR DATA MAY BE WIPED."

Is that just a general or generic warning, that the data on some phones

may

be wiped? Or does it mean, with certainty, that the data on my Pixel will

definitely

be wiped?

Next question: if I root the phone with CFAR, then I want to flash the next security patch from Google next month, will I need to run CFAR again afterwards, to keep it rooted? In other words, will flashing the monthly updates from Google result in the phone getting unrooted again?

Is there a recommended way to flash the monthly updates when a phone has been rooted with CFAR, and TWRP is not there?
[Miscellaneous Android Development] kg415:
Error downloading CF-Auto-Root for Samsung GT-P5113

Error downloading CF-Auto-Root for Samsung GT-P5113:

Download queued

The file you requested is being generated.

Current status:	ERROR

Estimated wait:	NOT APPLICABLE
[Miscellaneous Android Development] AcidAngel21:
cannot upload to firmware.mobi

I just tried uploading stock boot/recovery image for Moto G5 but it does not get added under "Your uploads". The page just refreshes and nothing happens.

I'm on Windows 10 and tried with Chrome, Firefox, IE and Edge. Even tried from my mobile with Chrome. No luck.

I tried the zip and the individual files.

Maybe someone can try to reproduce the problem or successfully upload the files?

https://drive.google.com/open?id=1WjFTiZiJrZChETAIlrXe983MNqvE3Bok
[Miscellaneous Android Development] carsten888:
I'm getting an error trying to download cf_root file for Samsung GT-I9105P Galaxy S2 plus.

https://desktop.firmware.mobi/device:1198/firmware:8458/cfar?
[Miscellaneous Android Development] whitebeardedtrimmer:
Crom Services APK Samsung
[Miscellaneous Android Development] m.fk:
Good news!

I opened my Devtools and watched the traffic. Noticed some strange behaviour: After the upload (POST) is completed I get a not authorized error. Only AFTER the page is loaded, A JS is triggered and I'm authorized with my Google account by sending a token ID. So what if...

Using Firebug I added an hidden input field to the upload form. Name="token_id". Copy the value from your network tab. Some Browsers may insert linebreaks into this value to display it. Remove the linebreaks. Length is about 1200 chars.

With this, upload your files again. You should get HTTP 303 answer instead. The table at the bottom may still be empty, just check again in few minutes.
[Miscellaneous Android Development] jylong_away:
I recently managed to get ahold of a Samsung Galaxy Folder 2 (SM-G1650) from Hong Kong running 7.1.1. Have been trying my darnedest to root the thing, but to no avail.

What I've done so far:

1) Deactivated FPR

2) Deactivated CROM service using the APK v.1.0.7

3) Generated a CF-Auto-ROOT file using the website. They seem to have a copy of the latest firmware file

I've checked Developer Options, and this model doesn't have a 'OEM Unlock' option. I gather that the CROM service is the equivalent for China models?

The image from CF-Auto-ROOT contains a recovery.img, and a cache.img.ext4 file. Whenever I try and flash the image using Odin, I get a 'SECURE CHECK FAIL : cache' error in red text. It then proceeds to softbrick the phone. Thankfully it's easy enough to fix with a full Odin flash of the firmware to stock.

Am I doing anything obviously wrong? I assumed that since the stock firmware is on the website, it should be rootable using CF Auto, but is this not the case? If it isn't does anyone have specific ideas about rooting 7.1.1 using other methods?
[Miscellaneous Android Development] ashyx:
I'm surprised it's cache giving the error and not the recovery.img.

It appears the bootloader is locked.

Have you got a screen shot of your device screen while in download mode?
[Miscellaneous Android Development] jylong_away:
Hey, thanks so much for helping with this. I've attached a photo of the download screen after the failed CF-Auto-Root image flash.

When I first tried this, FRP lock and CROM service were both 'on', and the flash failed, but the reason was displayed on the screen (eg. CROM preventing installation of custom ROM). I removed my Google account to deactivate FRP lock, and used CROM Service 1.0.7 to turn of CROM lock. I was lead to believe that the CROM aspect was the equivalent of unlocking bootloader in China models. I've tried installing the CROM service again to check status, and it says that CROM is already unlocked.

Knox fuse was tripped by TWRP flash, which had the touch screen issues(so unusable). Given that I was able to flash TWRP, wouldn't that mean the bootloader is unlocked?

'SECURE CHECK FAIL: cache' only appears after attempting the CF-Auto-Root. It happened before Knox was tripped as well.

Is CROM different from the bootloader then? If so, what would be the way to check bootloader status in this phone, since the 'OEM Unlock' doesn't appear in my developer options?

Thanks again!