firmware.mobi

[eyeoflucifer]

Max upload size issue on the server. Should be fixed now. I uploaded the nvidia one, you can do the OP3 one

Still, it would be better to extract the boot and recovery images, then zip those up.

Cool. Thanks. I'll try that out and also upload a few others.

 

[roirraW "edor" ehT]

How big are the firmwares?

Can you put one of them on drive and link it to me so I can test if it has something to do with the firmware images itself?

It normally redirects to a queue page after the upload which shows you the status... what happeend? did it just redirect to the same page again?

Hi! Thanks as always for everything you do!

I've tried uploading definitely stock (pulled from the stock container myself) boot and recovery.img for the VS985 LG G3. I've tried in Chrome, Edge and Internet Exploder with the same result. I've tried both outside and inside a zip. I do initially get the queue screen but then within 20 seconds it turns to the following:

Current status: ERROR
Estimated wait: NOT APPLICABLE

Let me know if you'd like me to upload these IMGs to Drive.

Thanks!

Edit: I have a bunch of LG VS985 and LG VK810 images on Android File Host at https://www.androidfilehost.com/user/?w=settings-dev-files&flid=35380 for the VS985 and https://www.androidfilehost.com/user/?w=settings-dev-files&flid=28125 for the VK810. Unfortunately, my archives there include all the other partitions, plus they're in 7-Zip format, although I do keep the system partition in separate archives from the non-system partitions.

 

[eyeoflucifer]

@Chainfire any way for me to link external full images like the ones done in the Pixel XL page?

 

[Chainfire]

Hi! Thanks as always for everything you do!

I've tried uploading definitely stock (pulled from the stock container myself) boot and recovery.img for the VS985 LG G3. I've tried in Chrome, Edge and Internet Exploder with the same result. I've tried both outside and inside a zip. I do initially get the queue screen but then within 20 seconds it turns to the following:

Current status: ERROR
Estimated wait: NOT APPLICABLE

Let me know if you'd like me to upload these IMGs to Drive.

Thanks!

Edit: I have a bunch of LG VS985 and LG VK810 images on Android File Host at https://www.androidfilehost.com/user/?w=settings-dev-files&flid=35380 for the VS985 and https://www.androidfilehost.com/user/?w=settings-dev-files&flid=28125 for the VK810. Unfortunately, my archives there include all the other partitions, plus they're in 7-Zip format, although I do keep the system partition in separate archives from the non-system partitions.

It's probably something with the boot images it doesn't understand. I'll look into it.

@Chainfire any way for me to link external full images like the ones done in the Pixel XL page?

Not right now, no. But if you have a collection I can link to... ?

 

[eyeoflucifer]

It's probably something with the boot images it doesn't understand. I'll look into it.



Not right now, no. But if you have a collection I can link to... ?

Hi, no collection right now. Just linking to the official sources. Also when i tried to upload the recovery for OP3, i got the same error as @roirraW "edor" ehT

 

[Chainfire]

If there are proper official sources (like download pages on the OEM site), I would like to automate scraping them.

As for the upload errors, every upload capability to a site is an attack vector. As a precaution, the parser is extremely strict in the files it accepts. As such I must collect valid images that don't work, analyze why the parser rejects them, and fix the problems.

Obviously the system does store error details, but it would be bad form (security wise) to display this information to the uploader, it might help hone the attack.

So if you have images that are being rejected that have not been linked before, please link them (uploads to drive are fine).

 

[rokah]

Hello here a noob with first time root, I hope a simple yes or no answer I can get in my struggle to find a answer. Hope you don't get irritated. Can anyone tell me if the cf autoroot works with G930FXXS1DQHN - Galaxy S7 SM-G930F PHN Netherlands. I Allready seen how rooting works with Odin and what to do. But this latest update and info on this forum confuses me.
Samsung s7 G930F exynox G930FXXS1DQHN - Galaxy S7 SM-G930F PHN Netherlands.
Ty in advance.

 

[Chainfire]

Hi, no collection right now. Just linking to the official sources. Also when i tried to upload the recovery for OP3, i got the same error as @roirraW "edor" ehT

The earlier OP3 image you put on drive is an OTA image, not a firmware image, so that's not going to work either way.

You should upload both stock boot and recovery simultaneously, or if that doesn't work link me to them so I can take a look.

 

[eyeoflucifer]

The earlier OP3 image you put on drive is an OTA image, not a firmware image, so that's not going to work either way.

You should upload both stock boot and recovery simultaneously, or if that doesn't work link me to them so I can take a look.

Oh ok. I had tried to do both and then only the recovery image. i guess that's why it failed.

I tried again to upload the boot and the recovery images that i extracted. That too failed. Have also uploaded them in the drive.

Files names are recovery_op3.img and boot.img (did not change the names as per the instructions)

https://drive.google.com/drive/folders/0B0wyPrkY34xAcElCZU1CN3FzRnc?usp=sharing

 

[CaelThunderwing]

not sure if its something on your end or not or something still pissing in teh case of the SM-S327VL (using CROM Services 1.06 APK does seem to set the Bootloader to unlocked as we can now see FRP Disabled and get to fastboot/Bootloader,) but its stil failing Secure Check :/

 

[minhducsun2002]

Rooting without TWRP

Hello and many thanks as always.
I would like to have a simple question for my Chinese device.
It is possible for CF-Auto-Root to auto-generate root packages from uploaded images? I like being rooted, but...no custom recovery, and the "Magic…" stuffs doesn't work on my MT6580 Lollipop device.

Thanks in advance.

 

[Wasim625]

Hi,
First of all thankyou very very much for your work, effort and time you put in for us. I will definitely donate.

i have a question that i am try to root my device which is Samsung on5 g5520 running on marshamallow from your root file that i got from your website. but everytime i try to root it Odin tool ends unsucessfully and my device says Security check fail : cache. what can the issue be or may be i am doing something wrong?

 

[shaggyskunk]

Hi,
First of all thankyou very very much for your work, effort and time you put in for us. I will definitely donate.

i have a question that i am try to root my device which is Samsung on5 g5520 running on marshamallow from your root file that i got from your website. but everytime i try to root it Odin tool ends unsucessfully and my device says Security check fail : cache. what can the issue be or may be i am doing something wrong?

Sounds like either:
a) Locked Bootloader.
b) Reactivation Lock is Checked.

From Down the Rabbit Hole by:
My SM-G930W8 ??

 

[Chainfire]

Edit: I have a bunch of LG VS985 and LG VK810 images on Android File Host at https://www.androidfilehost.com/user/?w=settings-dev-files&flid=35380 for the VS985 and https://www.androidfilehost.com/user/?w=settings-dev-files&flid=28125 for the VK810. Unfortunately, my archives there include all the other partitions, plus they're in 7-Zip format, although I do keep the system partition in separate archives from the non-system partitions.

Either your links aren't right or AndroidFileHost requires a login. Please upload some samples to Google Drive and link them to me, or somewhere else where downloads are don't require sign-up.

 

[roirraW "edor" ehT]

Either your links aren't right or AndroidFileHost requires a login. Please upload some samples to Google Drive and link them to me, or somewhere else where downloads are don't require sign-up.

Apologies. I have occasionally forgotten that I'm not on Drive at the time and I copy the URL from the address bar instead of the proper shared URL. I'm in Drive all the time at work and at home because we use Google for everything at work and force of habit.

I verified these links are the right ones.

https://www.androidfilehost.com/?w=files&flid=35380

https://www.androidfilehost.com/?w=files&flid=28125

I'm mobile now but if you wish, say the word, and I'll separate out just the boot and recovery of all of them and put them on Drive.

 

[Exelios]

Hey @Chainfire, I just uploaded the files for Huawei hi3660, that's the Mate 9, but when searching for Huawei on home page hi3660 comes up as unknown device, any chance you could update the device name to make it easier for people to find it? Thanks

https://desktop.firmware.mobi/device:1755/firmware:13288


PS
This firmware is not compatible with CF-Auto-Root
You make me sad

 

[Chainfire]

Apologies. I have occasionally forgotten that I'm not on Drive at the time and I copy the URL from the address bar instead of the proper shared URL. I'm in Drive all the time at work and at home because we use Google for everything at work and force of habit.

I verified these links are the right ones.

https://www.androidfilehost.com/?w=files&flid=35380

https://www.androidfilehost.com/?w=files&flid=28125

I'm mobile now but if you wish, say the word, and I'll separate out just the boot and recovery of all of them and put them on Drive.

I tested with one of the vs985 images and that now uploads and parses correctly (there was a problem with legacy lz4 compression detection). You could now try again with all the other images.

Though I must note that 7z archives are still not supported, so you still have to extract those / upload them separately / zipped.

Hey @Chainfire, I just uploaded the files for Huawei hi3660, that's the Mate 9, but when searching for Huawei on home page hi3660 comes up as unknown device, any chance you could update the device name to make it easier for people to find it? Thanks

https://desktop.firmware.mobi/device:1755/firmware:13288

PS
This firmware is not compatible with CF-Auto-Root
You make me sad

The device information is combination of properties listed in the images, and a spreadsheet Google provides to translate them from OEM names to friendly names. There is no manual adjustment possible at this time

Huawei is not providing the proper information in their images, and/or Google does not have an entry in their translation sheet for it.

I'm not sure why this image is incompatible with CFAR yet.

Oh ok. I had tried to do both and then only the recovery image. i guess that's why it failed.

I tried again to upload the boot and the recovery images that i extracted. That too failed. Have also uploaded them in the drive.

Files names are recovery_op3.img and boot.img (did not change the names as per the instructions)

https://drive.google.com/drive/folders/0B0wyPrkY34xAcElCZU1CN3FzRnc?usp=sharing

I adjusted the parsing (on my dev box, not online yet!) to cope with these boot and recovery images. They are quite messy to be honest, but I was able to make it work.

I've also started work on a script that can parse OTA images, but this is a very time-consuming operation (think an hour per OTA). So I don't think I'll enable it for the 'upload ZIP' box. But I do think I'll add a OnePlus scraper in the next few days, so these images will all be added automatically from OP's site.

 

[Dark1Angel]

Can anyone enlighten me what should I choose when configuring CF-Auto-Root? There are many choices which I don't understand the meaning of: System, Systemless Image, Systemless SBIN and the other one: include suhite, don't include. If anyone can also explain what each means? Should I choose autodetect for both or are they important and the choice has implications?

 

[ashyx]

Can anyone enlighten me what should I choose when configuring CF-Auto-Root? There are many choices which I don't understand the meaning of: System, Systemless Image, Systemless SBIN and the other one: include suhite, don't include. If anyone can also explain what each means? Should I choose autodetect for both or are they important and the choice has implications?

Unless you need it and not aware of what the option does just leave all at default.

 

[nilkanth.marshiwane]

Can't generate package for xiaomi mi a1