Profile

Cover photo
Verified name
352,087 followers|27,367,678 views
AboutPostsPhotosVideos

Stream

Chainfire

Shared publicly  - 
 
FlashFire v0.27 - Minor fixes

Hot on the heels of yesterday's major v0.26 release (see: https://plus.google.com/+Chainfire/posts/FjWwBm9vGyj ), here is the first bugfix release: v0.27.

It deals mainly with two things:

More warnings for OTA flashing
A fair number of you have complained that the OTA flashing didn't work for some Nexuses, while trying to flash the OTA on top of a modified system.

These OTAs only contain the differences between the 'old' and 'new' partition contents. If you change the 'old' contents (modify system) then it cannot produce the correct 'new' contents.

Some users did not understand this. Others were under the impression that their system was still unmodified.

FlashFire will now both attempt to detect if an OTA requires an unmodified system on the block level, and if the system is actually unmodified. If failure is expected, it will warn you about it.

The easiest solution in this case is to download the full firmware from Google's site, and flash that with FlashFire, instead of the OTA. This will still allow you to keep both root and your data.

More non-Nexus testing
There isn't much Marshmallow going around yet on devices I actually own, with the exception of the S6 and the Shield Tablet. Both are now better supported!

Download
You can follow the link in the box below this post to give Google's awkward beta system a try, and see if you can convince Google Play to give you the download. I have seen this work once, I swear. (Seriously, I do recommend doing this, though it may still be offering you v0.26 for a few hours).

For this twice, I've also made the APK available from my own server, though you shouldn't consider this a permalink: http://download.chainfire.eu/922/FlashFire/FlashFire-v0.27-20160203183412.apk

Discussion, bug reports, etc
As Google+ comments invariably turn into a beepfest of spam and foreign languages, I mostly ignore them. As usual, the thread on XDA is where it's going on: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

Changelogs
- Copy additional partitions from fstab
- Added NVidia OTA locations
- Mark NVidia devices as somewhat supported
- Partitions: Added various partitions
- Fixed internal storage on Samsung 6.0.1
- Fixed sdcard on NVidia Shield Tablet
- Files named twrp-* or openrecovery-* are now recognized as recoveries
- Added warning about OTAs often requiring an unmodified system
- Attempt to detect block-level OTAs and modified systems, and warn when the flash is likely to fail
- Added some more logging in case of failure/reboot
For your convenience, keep this checked. On shared devices, additional precautions are recommended. Learn more · Need help? Create an account. One Google Account for everything Google. About Google · Privacy · Terms · Help. Change language. Afrikaans , azərbaycan dili , Bahasa Melayu ...
269
19
Arham “IceandFire” Jamal's profile photoDr. Lee's profile photoCiprian Florea's profile photo国玺李(seal1215)'s profile photo
53 comments
 
Will this app work with an unexpanded Commodore Vic 20?
Add a comment...

Chainfire

Shared publicly  - 
 
CF-Auto-Root updated

Sorry for taking so long to update CFAR - the last major update was some time ago, and a lot has changed in Android land regarding root. Significant patching was needed for 6.0 in general, and Samsung made some security changes in 5.1 that also required more patching than usual.

As those patches seem to have somewhat stabilized over the last few weeks with only minor changes between the last few SuperSU releases, it was high time to update CFAR. So over the past week or two I've been collecting new firmwares, and the past few days the server has been whirring away crunching recoveries.

With this update, over 300 device models have been added or updated with new base firmwares, and 5.1 and 6.0 are now supported. (Note that all CFAR's have been updated to install SuperSU v2.65, regardless of if their base firmware has also been updated).

Note that the G920F CFAR does not yet support the BETA 6.0 firmware, I think. The G920F is my daily driver and I haven't had a chance to check out that BETA firmware yet. Stay tuned for that.
When newer firmwares are released for a certain device, sometimes that firmware includes new bootloaders that prevent kernels based on the old firmwares from booting. This usually coincides with a transition to a newer Android version. In that case, the CF-Auto-Root for download here may no ...
1046
65
Amine Rakmani's profile photoPam Wood's profile photoThally Ace's profile photoBieke De Lannoit's profile photo
231 comments
 
Where is the download link for SM-A800I 
Add a comment...

Chainfire

Shared publicly  - 
 
500 Firepaper breaks up with 500px

I've just uploaded v2.70 to the Play Store, which removes the 500px-supported upgrade to allow pinning for 7 days.

500 Firepaper to me has been one of those apps that was fun to build and I actually used daily myself. Every Android device I use runs it as its background.

It used to be optionally-donate, as in, all features were free and you could buy Pro to buy me a beer. About 1.5 years ago, the guys at 500px let me know they wanted half the 'revenue'. In exchange, they would allow paying users to keep images cached (and pinned) for 7 days instead of 24 hours. Fair enough, they're providing the bandwidth, after all.

About half a year ago, 500px started to watermark 'their' images. According to their own documents, you can get a watermark-free stream of images for a fee. Of course, I immediately started lobbying to have those watermarks removed for images shown in 500 Firepaper - if not for all users, then at least for paying users.

I'll be the first to admit that earlier this year, some of my payments to 500px were late and batched together - my bad. They made some comments about that, so I started making sure the payment were done within the terms of the contract. Terms that were negotiated at length when it was signed, and now apparently forgotten.

They have become first unreasonable (and they're Canadian...) then completely unresponsive. After months of this, it is clear to me that they have no intention to either work anything out, or remove the watermarks, even for users they have received revenue shares from.

To me this is completely unacceptable. I cannot justify taking user's money and giving it to 500px, while at the same time 500px presents those same users with watermarked images that go a long way to ruin the experience.

As such, I am no longer making payments to 500px, and have removed the paid functionalities from the app. It is now once again an optionally-donate app, with all features available for free.

Pinning for 7 days will still be available for users who purchased when that feature was offered, for anyone else it will be limited to 24 hour cache time limit.

Note that I fully expect this is the beginning of the end for 500 Firepaper. It wouldn't surprise me if they just disabled the app's API key out of spite. I'm sure they don't agree with me keeping the 7-days-pinning feature available for those who have paid in the past either.

Last but not least, it has happened several times in the lifetime of 500 Firepaper that the app's API key was disabled by a photographer's request. Photographs uploaded to 500px are spread through the API for public consumption (with cache time limits). It seems a large number of photographers aren't aware of this happening, and just see their photos appearing somewhere - to their logic without their permission. Of course, they have granted 500px permission to do this when they signed up, but not realising this, they file complaints. If that happens again, I fear the API key will never be reinstated.

That's it, enjoy it while it lasts.
500 Firepaper provides a live wallpaper and a daydream showing you the late...
446
23
Alessio M's profile photoveli tugay's profile photoKyaw Minnthu's profile photoRob Lukzak's profile photo
72 comments
 
Is this why my phone keeps telling me the app is not installed when I am in the change wallpaper setting??
Add a comment...

Chainfire

Shared publicly  - 
 
System-less root experiment

I posted some boot images (and basic how-to to make your own) for all the 6.0 Nexuses and a special installer ZIP (TWRP) for SuperSU on XDA.

Together, they allow root without modifying /system. It's an experiment, but it works out rather cleanly. See the linked thread for further details.
853
109
Stefan Quandt's profile photoJose Amaya's profile photoTuananh Tran's profile photoadolf hess's profile photo
76 comments
 
Can't wait to update my note 4 to Android M. Not rooted till this moment. :(
Add a comment...

Chainfire

Shared publicly  - 
 
CF.lumen v3.10 BETA

There's a new test version of CF.lumen available at the link in the box below.

It brings some base compatibility with 6.0, and a new driver (root users only) that doesn't require modifications to /system.

See the link for more info!
354
13
Daphna Adoni's profile photoji ji's profile photoElenilson El's profile photoGonzalez Gonza's profile photo
10 comments
 
We're having lots of trouble getting v3.16 of this app to work on the Oneplus2.  Any plans to test for this device?
Add a comment...

Chainfire

Shared publicly  - 
 
Recently updated to v1.30

I just uploaded the new version to Play, should start rolling out in a few others. You can also grab the APK from the XDA thread here: http://forum.xda-developers.com/android/apps-games/placeholder-t3050998

It now works on M. Or at least it does on my Nexus 5 :)

Additionally, I gave the clear all button a FAB look.
With Android 5.0 Lollipop's release, the recents view (multitask button) be...
422
20
Kiki Lala's profile photo‫محمد احمد‬‎'s profile photongoc huan's profile photoMichael Ibuyan's profile photo
25 comments
 
I need root note 4 sm-n910v version Android 5.0.1

Can you help me please 
Add a comment...
In their circles
1 person
Have them in circles
352,087 people
Nargis Kasper's profile photo
Esteban J. ferdez h's profile photo
Alan Angelim's profile photo
Tyrell Brunson's profile photo
ŞěçùŕîRťý I3ăQ's profile photo
Emmanuel Soult Smith's profile photo
Sabah Uddin's profile photo
Wadd Alan's profile photo
Marco Ioppolo's profile photo

Chainfire

Shared publicly  - 
 
FlashFire v0.26 - Marshmallow and OTAs

The new FlashFire update is finally here! This is the first version of FlashFire compatible with Android 6.0, and yes, it does OTAs!

Note that this update focuses mainly on Nexus devices and their capabilities, since most of my other devices aren't up to 6.0 yet.

Nexus OTAs and root
If you are using SuperSU in systemless mode (the default) on Android 6.0, and you haven't modified the kernel, /system or /vendor, just let Android download the update, but instead of clicking install, open FlashFire.

If all goes as planned, FlashFire will detect the OTA, and offer to generate the actions for you. Just hit "Flash" afterwards, take a minute to make an offering to your deity of choice, et voila! Booted and rooted.

I've personally tested this procedure going from the earliest 6.0 version, OTAing in several steps to the very latest update, while keeping root, on the Nexus 5, 5X, 6, 6P, and 9. The Player (because X86) and Pixel C (because ChromeOS leftovers) are currently not supported.

Full firmwares
There have also been significant improvements to flashing full firmware archives (and rooting in the process). Several more archive formats are now supported, as well as several more partitions.

However, please do not flash any of the new BETA Samsung 6.0 firmwares with this yet unless you are expecting to soft-brick and/or lose all your data. They are hard to flash and prone to (soft)bricking even with Odin and need more testing.

Backup/restore
Please note that backup and restore have not been tested as extensively yet on 6.0 as flashing OTAs and firmwares. There haven't been any specific issues with this during testing either, though.

Omni/CM
Many users had trouble flashing Omni, CM, and their derivatives on old FlashFire versions. A number of issues influencing this have been fixed, and I've flashed Omni and CM to several devices without issue. However, you should position a Wipe action before the ZIP flash, and make sure the "Mount /system read/write" option is enabled.

The UI does note both these things, but people rarely read. I don't even know why I'm writing this :)

Future
I expect to release another update rather soon, as there are some more small things I would really like to adjust/fix ASAP. However, today is OTA day, so here we are.

Download
You can follow the link in the box below this post to give Google's awkward beta system a try, and see if you can convince Google Play to give you the download. I have seen this work once, I swear. (Seriously, I do recommend doing this, though it may still be offering you v0.24 for a few hours).

For this once, I've also made the APK available from my own server, though you shouldn't consider this a permalink: https://download.chainfire.eu/898/FlashFire/FlashFire-v0.26-20160202001009.apk

Bugs
There will be many. This is a fairly massive update to a fairly complex tool that runs on a fair number of different firmwares and devices, doing pretty much exclusively things that fall outside of the supported API. Things are going to break, and you get to keep all the pieces.

Discussion
As Google+ comments invariably turn into a beepfest of spam and foreign languages, I mostly ignore them. As usual, the thread on XDA is where it's going on: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

Changelogs
- (C) 2016
- Archives: TAR: Fix MD5 warning if no MD5 signature found
- Archives: Added option to ignore MD5 mismatch
- Archives: Added support for Huawei Bootloader packed image format
- Archives: Added support for MSM89xx Bootloader packed image format
- Archives: Added support for Motorola Bootloader packed image format
- Updated embedded SuperSU version to v2.67-3 - Root must be SuperSU or (CM SU + Permissive)
- EverRoot: Enable on boot image modification, if currently systemless
- Firmware: Display partitions in the correct order
- UpdateZIP/OTA: Support progress bars
- UpdateZIP/OTA: Fix several issues with flashing Omni/CM
- OTA: Work-around apply_patch freeze
- OTA: Detect downloaded OTA and suggest flashing
- Partitions: Added various partitions
- M: Fix clear cache not working fully
- M: Update partition detection
- M: Toybox compatibility
- M: Fixed native graphics library
- M: Fixed sdcard mounting
- M: Relocate systemless SuperSU during setup
- M: Do not remove boot image backups and su image on wipe
- M: UpdateZIP/OTA: offer to restore boot and recovery image before flash
- L: UpdateZIP/OTA: mount /system, /vendor and /oem as r/o if unmodified
- L: Backups: Use RAW mode for unmodified /system, /vendor and /oem partitions
- Backups: Use RAW mode for partitions where the filesystem cannot be detected
For your convenience, keep this checked. On shared devices, additional precautions are recommended. Learn more · Need help? Create an account. One Google Account for everything Google. About Google · Privacy · Terms · Help. Change language. Afrikaans , azərbaycan dili , Bahasa Melayu ...
437
57
Zach Morgan's profile photoPlum Lis's profile photoAndrea Ninci's profile photoAleksandra Huey's profile photo
48 comments

Chainfire

Shared publicly  - 
 
SuperSU v2.61 BETA released

In the ongoing effort of having root on 6.0 as streamlined and seamless as possible, SuperSU v2.61 BETA was just released.

The last few BETAs have been providing SuperSU installs without touching /system, as we are modifying the boot images anyway. Since a few days ago (v2.60) the ZIP installer automagically does this boot image patching for you (for Android 6.0+, and Samsung 5.1+), significantly reducing the hassle for devices this is compatible with.

While this works great on the 6.0.x stock Nexus firmwares and even custom ROMs such as CM13, we know it still has some issues on for example the G3 and some Samsung 5.1 devices.

Keep in mind this is still a BETA, and you should only be using it if you are tech-savvy enough to fix your device if you mess it up.

In the thread below, the information in posts #2 and #3 are both relevant, with the v2.61 BETA download attached to #3. The information is still a bit scattered and sparse, a clean-up is on the to-do list :)
969
66
Joe Dez's profile photoRoger Ratliff's profile photo许仁忠's profile photoJanne “JFA” Laakso's profile photo
107 comments
 
چی
Add a comment...

Chainfire

Shared publicly  - 
 
LiveBoot v1.20 released

I've just uploaded a new version of LiveBoot to the Play store, which should start updating in a matter of hours. Alternatively, you can grab it from the thread on XDA ( http://forum.xda-developers.com/android/apps-games/liveboot-t2976189 ), which is also the place where your questions should go.

The only change is support for Android 6.0, including system-less root (the boot script doesn't touch /system if you have the system-less root released earlier today installed).
LiveBoot is a boot animation that shows you logcat and dmesg outputs on-scr...
590
25
adolf hess's profile photoNarack 070's profile photoJoe Dez's profile photoISSA TOURE's profile photo
42 comments
Add a comment...

Chainfire

Shared publicly  - 
 
CF.lumen v3.15 released

I have just uploaded a new version of CF.lumen to the Play store, which should start updating in a matter of hours. Alternatively, you can grab the latest version directly from the XDA thread ( http://forum.xda-developers.com/showthread.php?t=2711912 ).

While not all issues for 6.0 are fixed yet, the most pressing one is: root driver support.

My thanks to all the beta testers!

(I am aware the box below may say "WARNING: DONT INSTALL...", this is because Play hasn't updated the description yet - and I don't think Google Plus will update the box when it has)
WARNING: DONT INSTALL ROOT DRIVER ON 5.1/6.0 - CAUSES BOOTLOOPSCF.lumen ada...
255
10
Mohammad Hossein Abedi's profile photoAndres Leal's profile photoIlyas Butt's profile photoДенис «foenix_kiev» Михайленко's profile photo
30 comments
 
Monochrome? I want my phone to be black and white
Add a comment...

Chainfire

Shared publicly  - 
 
StickMount updated to v3.33

I have just uploaded a new version of StickMount to the Play Store. It should be available for download within a few hours. Fixes a number of issues with M.
Automatically mount and dismount USB sticks on various devices like the Gal...
573
23
Bakhtaj Khan's profile photoWaledwaledsalah Waled01118767896's profile photoQASIM MOSANI's profile photoumamahesh p's profile photo
35 comments
 
On 3.33 (pro) with latest supersu (2.67) Nexus 6p, it always shows mass storage device mounted even with nothing external connected... 
Add a comment...

Chainfire

Shared publicly  - 
 
SuperSU v2.50 BETA, 6.0 boot images

A new BETA was released today, available in the usual spot (also linked from the thread below).

Additionally, I uploaded some modified stock boot images for the Nexus devices the Android 6.0 firmwares have been released for already - and instructions how to make your own.

Combined, they allow root on 6.0 devices with SELinux in Enforcing mode.

(of course the BETA also fixes some other minor things)
928
83
Shuqi Dou's profile photosungwook cho's profile photoJosh Decker's profile photoSamuel Osorio's profile photo
85 comments
 
Help me plz supersu code upgradin dont googleplay store
Add a comment...
People
In their circles
1 person
Have them in circles
352,087 people
Nargis Kasper's profile photo
Esteban J. ferdez h's profile photo
Alan Angelim's profile photo
Tyrell Brunson's profile photo
ŞěçùŕîRťý I3ăQ's profile photo
Emmanuel Soult Smith's profile photo
Sabah Uddin's profile photo
Wadd Alan's profile photo
Marco Ioppolo's profile photo