[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73

Status
Not open for further replies.
Search This thread

Biggspeed

Member
Jan 30, 2014
44
1
Lost USB functionality, unable to root via USB.

Samsung SM-N920W8, Canadian Note 5. Have successfully rooted many times via odin. Never flashed a custom rom just used stock. Installed Flashfire to wipe system and maintain root. Wiped successfully, lost root. Lost USB ADB functionality and USB fast charge. Unable to OTA because I have a device showing status as "custom". I would like to find a solution if possible to get USB ADB connectivity or root back. This is not a blame game. I knew the risks of using this app. I'm just looking to see if there is a solution. When I connect my note to any windows PC with Samsung drivers and ADB Debugging enabled. I just get a "device not recognized" error on the PC. Only happened after I wiped it. No longer able to use odin on PC as normal. Lost custom recovery so no flashing SuperSu either. Tried flashing stock rom via stock recovery and get an error there as well. Any help would be greatly appreciated.
Thanks.
 

Ch3vr0n

Senior Member
May 6, 2009
1,693
668
39
You're probably going to have more luck in your device specific forum. You're having somewhat hardware related issues, and that's a bit beyond the scope of this topic

Sent from my Nexus 6P with Tapatalk
 
  • Like
Reactions: cnjax and ktmom

silverik1

Member
Mar 12, 2016
21
0
blank screen after scanning archive

Hey All,
I have a question.
I have a rooted s8 and use flashfire and magisk
If I want to update I start flashfire and choose " flash firmware package" .
I downloaded the firmware from updato.
It starts scanning the archive and when its done nothing happens.
I have a screenshot from the screen I get.
Anybody know what this is?
 

Attachments

  • Screenshot_20180906-160751_FlashFire.jpg
    Screenshot_20180906-160751_FlashFire.jpg
    98.5 KB · Views: 514

HemanthJabalpuri

Senior Member
Hey All,
I have a question.
I have a rooted s8 and use flashfire and magisk
If I want to update I start flashfire and choose " flash firmware package" .
I downloaded the firmware from updato.
It starts scanning the archive and when its done nothing happens.
I have a screenshot from the screen I get.
Anybody know what this is?
Possibly it is a corrupted file...i think...
 

jult

Senior Member
Apr 22, 2011
446
122
Amsterdam, NL, EU
jult.net
Samsung SM-N920W8, Canadian Note 5. Have successfully rooted many times via odin. Never flashed a custom rom just used stock. Installed Flashfire to wipe system and maintain root. Wiped successfully, lost root. Lost USB ADB functionality and USB fast charge. Unable to OTA because I have a device showing status as "custom". I would like to find a solution if possible to get USB ADB connectivity or root back. This is not a blame game. I knew the risks of using this app. I'm just looking to see if there is a solution. When I connect my note to any windows PC with Samsung drivers and ADB Debugging enabled. I just get a "device not recognized" error on the PC. Only happened after I wiped it. No longer able to use odin on PC as normal. Lost custom recovery so no flashing SuperSu either. Tried flashing stock rom via stock recovery and get an error there as well. Any help would be greatly appreciated.
Thanks.
Sounds like your bootloader is damaged. What error does flashing thru stock recovery give you? Have you tried factory reset from stock recovery? First do that. Then see if that fixes USB access in Download mode with Odin. Flash latest stock firmware (from SamFirm) through Odin. Then flash TWRP, install magisk through TWRP and you're back as root.
 

Biggspeed

Member
Jan 30, 2014
44
1
Sounds like your bootloader is damaged. What error does flashing thru stock recovery give you? Have you tried factory reset from stock recovery? First do that. Then see if that fixes USB access in Download mode with Odin. Flash latest stock firmware (from SamFirm) through Odin. Then flash TWRP, install magisk through TWRP and you're back as root.

I have done a reset from stock recovery. No change. "DM-Verity Verification Failed" , is the error I get when try to flash Stock via stock recovery.
 

Biggspeed

Member
Jan 30, 2014
44
1
If the ota is doing integrity checking, it probably is not a full ota, check this out. And have you tried Heimdall instead of Odin? If it still does not work on Windows, try on Linux

https://glassechidna.com.au/heimdall/

I haven't tried Heimdall no, but I dont even get to that point. Odin works, its Windows not recognizing the device on every PC I've tried. I've thought about Linux but don't have a machine that runs it and figured it would recognize it the same way. And zero Linux experience too. As for a complete OTA I thought it was. Any good links for a complete OTA that you could point me towards? Thanks for the help.
 

jult

Senior Member
Apr 22, 2011
446
122
Amsterdam, NL, EU
jult.net
I haven't tried Heimdall no, but I dont even get to that point. Odin works, its Windows not recognizing the device on every PC I've tried.
Have you tried an older Odin version, like 3.12.3 ?
Either way, your /boot is damaged. You won't get proper USB connectivity on a Note with that.
As for a complete OTA I thought it was. Any good links for a complete OTA that you could point me towards? Thanks for the help.
https://updato.com/firmware-archive-select-model
Samsung SM-N920W8, Canadian Note 5.
Assuming your Region is BMC, fill that in with SamFirm to grab the full latest firmware.
 
Last edited:

Biggspeed

Member
Jan 30, 2014
44
1
Have you tried an older Odin version, like 3.12.3 ?
Either way, your /boot is damaged. You won't get proper USB connectivity on a Note with that.

https://updato.com/firmware-archive-select-model
Assuming your Region is BMC, fill that in with SamFirm to grab the full latest firmware.

Ok downloaded samfirm and downloaded the firmware. Was able to get the new firmware to my phone. Placed it in the root directory not in any folder. Booted to recovery. Selected apply update from SD card and got the same error "DM-Verity verification failed... Update from external storage is disabled."
 

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,381
Deep Space Station K7
Ok downloaded samfirm and downloaded the firmware. Was able to get the new firmware to my phone. Placed it in the root directory not in any folder. Booted to recovery. Selected apply update from SD card and got the same error "DM-Verity verification failed... Update from external storage is disabled."
I mean this as an effort for you to get the fastest help possible. But also to help this FlashFire thread not get so far off topic.

This is a question that will get the best assistance in a device specific forum. You may have a DM verity file that needs to be flashed but it's not a FlashFire issue at this point.


"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
 
  • Like
Reactions: cnjax

Biggspeed

Member
Jan 30, 2014
44
1
I mean this as an effort for you to get the fastest help possible. But also to help this FlashFire thread not get so far off topic.

This is a question that will get the best assistance in a device specific forum. You may have a DM verity file that needs to be flashed but it's not a FlashFire issue at this point.


"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Yup thats understood. Which is exactly what I did a long time ago. My problem was addressed in this forum thread and not the device specific thread.
 

SnowFuhrer

Senior Member
Apr 5, 2018
1,622
470
Spirit River
Is there any way to edit flashfire so doesn't shut when I open it? Its a pain to put the date back all the time. If you answered this already, I'm sorry. I didn't read the whole the thread. (I wonder why);)

Sent from my LG-K121 using XDA Labs
 

badvag

Senior Member
Jan 13, 2017
67
11
Rio de Janeiro
Hi,
I'm trying to install Xposed (v64 sdk26 arm64) on a Asus ZE554KL Android 8.0.0.
I performed the bootloader unlocking, and then with "tricks" I installed TWRP (3.1.1-0-Z01K) because it was overwritten by the stock recovery. Now it is working with TWRP and root (with Magisk-v17.1), I also used "no-verity-opt-encrypt-6.0".

But when I reboot on the device, I again have Internal Storage (0MB) and the error "Failed to mount '/ data' and Unable to mount storage."
This is the same problem I have before flashing the no-verify "no-verity-opt-encrypt-6.0" and "Magisk-v17.1" which I can fix with Wipe / Fortmat Data.
Another strange fact is that whenever you boot the custom Recovery TWRP on the first attempt the screen gets frozen, only when you boot again the TWRP works.

I would be able to flash the Xposed in Asus Zenfone 4 (Android 8.0.0) and install the framework? Or would I have problems at boot or some other problem?
I had this idea because I'm not getting Flash Xposed by TWRP as I described above.
 

cnjax

Senior Member
Aug 4, 2011
4,282
10,898
Jacksonville, FL
Hi,
I'm trying to install Xposed (v64 sdk26 arm64) on a Asus ZE554KL Android 8.0.0.
I performed the bootloader unlocking, and then with "tricks" I installed TWRP (3.1.1-0-Z01K) because it was overwritten by the stock recovery. Now it is working with TWRP and root (with Magisk-v17.1), I also used "no-verity-opt-encrypt-6.0".

But when I reboot on the device, I again have Internal Storage (0MB) and the error "Failed to mount '/ data' and Unable to mount storage."
This is the same problem I have before flashing the no-verify "no-verity-opt-encrypt-6.0" and "Magisk-v17.1" which I can fix with Wipe / Fortmat Data.
Another strange fact is that whenever you boot the custom Recovery TWRP on the first attempt the screen gets frozen, only when you boot again the TWRP works.

I would be able to flash the Xposed in Asus Zenfone 4 (Android 8.0.0) and install the framework? Or would I have problems at boot or some other problem?
I had this idea because I'm not getting Flash Xposed by TWRP as I described above.
This has nothing to do with flashfire

Sent from my LG-H910 using XDA Labs
 

badvag

Senior Member
Jan 13, 2017
67
11
Rio de Janeiro
Would not it be possible to flash Xposed on Zenfone 4 ZE554Kl with the FlashFire app?

---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------

This has nothing to do with flashfire

Sent from my LG-H910 using XDA Labs

Would not it be possible to flash Xposed on Zenfone 4 ZE554Kl with the FlashFire app?
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 939
    FlashFire is the most advanced on-device firmware flasher available for rooted Android devices. It can flash full firmware packages from various manufacturers, as well as apply over-the-air (OTA) and ZIP updates - all while maintaining root, and without using a custom recovery. It also offers full device backup and restore functionalities in several formats. Relevant files can be stored on internal storage, SD cards, USB connected storage, or can even be streamed directly to and from your computer using USB or Wi-Fi.

    FlashFire is the spiritual successor to the Mobile ODIN app, which was a similar solution (using completely different methods under the hood) exclusively for Samsung devices on older Android versions.

    FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and this thread before doing anything potentially destructive.

    If the FlashFire user interface crashes, please attach the logs of the crash to your post. The SysLog app can help.

    If you are experiencing an issue while FlashFire is flashing, please post FlashFire's log file to pastebin, and include the link in your post. The log file can be found at /sdcard/FlashFire/lastlog on your device.

    FlashFire's website/manual can be found at http://flashfire.chainfire.eu/.

    Note: currently all functionality is unlocked without purchasing Pro. This may change in the future!
    124
    Changelogs

    Please re-report any issues that persist after a new version comes out, even if you already reported them for the previous build. Either include the details again or link to your previous post.

    2017.09.21 - v0.73 - RELEASE NOTES
    - A/B OTA: Support for yet another streaming variant
    - Magisk support: Fix some black screen issues
    - Magisk support: Much improved OTA flashing compatibility (excluding A/B devices)
    - SuperSU: Updated embedded SuperSU version to v2.82-SR4
    - Backup: Exclude paths from backup with /sdcard/FlashFire/userdata_excludes and ./internal_storage_excludes
    - Restore: Fix issue where FBE keys sometimes weren't restored
    - Wipe: Add option to not wipe files from internal storage that aren't backed up
    - ZIP: Open ZIPs from file managers and (Chrome) downloads directly, or share to FlashFire (file must resolvable to reside on /data)
    - Adjusted timebomb for non-Pro users to 2018-04-01

    2017.09.13 - v0.72 - RELEASE NOTES
    - OTA: Fix new style OTA-download-complete marker detection
    - A/B OTA: Add suppport for 'streaming' style OTAs
    - A/B OTA: Enable pre-mount by default (required for incremental A/B OTAs now)
    - Wipe: Fix dalvik-cache wipe greedily removing some files it shouldn't

    2017.09.12 - v0.71 - RELEASE NOTES
    - A/B OTA: Fix update_engine_flashfire crash in logs
    - A/B OTA: Always make update_engine_sideload available
    - A/B OTA: Fix fstab availability for new style OTAs
    - A/B OTA: Don't automatically delete OTAs after successful install if located on internal storage or sdcard
    - A/B OTA: Detect target slot rather than blindly switching to the other one
    - FlashUI: More Android Oreo compatibility fixes

    2017.09.11 - v0.70 - RELEASE NOTES
    - FlashUI: Android Oreo support

    2017.08.15 - v0.60 - RELEASE NOTES
    - OTA: Implement O-style OTA handling (non-streaming)
    - UI: Fix not being able to deselect backup partitions
    - UI: Fix partitions listed multiple times in backups sometimes
    - FBE: Fix wiping encryption files during restore, triggering factory reset

    2017.08.13 - v0.58 - RELEASE NOTES
    - Fix (abort) parsing of loki boot images
    - Prioritize ZIP/GZIP/BZIP2 detection over other formats
    - Fix compatibility with SuperSU in SBIN mode
    - OTA: Fix /cache not being available sometimes
    - OTA: Fix handling issue with August A/B OTA
    - OTA: Show warning on 'OTA found' dialog if not using systemless SuperSU
    - Backup/Restore: skip lockscreen security files
    - Embedded SuperSU updated to v2.82 SR3
    - Adjust timebomb for non-Pro users to January 01, 2018

    2017.04.03 - v0.57 - RELEASE NOTES
    - Add support for multi-stage OTAs
    - Fix possible NPE during OTA uncrypt
    - Fix logic failure during OTA uncrypt
    - Fix unsupported root detection
    - Fix root detection sometimes failing
    - Prefer system-supplied reboot binary to our own
    - Adjust timebomb for non-Pro users to September 01, 2017
    NOTE: Sometimes OTA still reboots to recovery with an error, just reboot manually

    2017.01.27 - v0.55 - RELEASE NOTES
    - (C) 2017
    - Improved 32/64 bit handling (fixes some blackscreens)
    - Improved handling of devices that have a /vendor partition
    - Add initial support for devices with multiple slots
    - Add support for uncrypted OTA ZIPs
    - Add support for A/B OTA ZIPs
    - Add support for file-based encryption backup/restore (primary user only)
    - Add additional Pixel partitions
    - Add support for Magisk+SuperSU (preliminary)
    - Add support for Magisk+phh (topjohnwu version only) (preliminary)
    - Add circular icon (Android 7.1)
    - Restrict app usage to primary user
    - Make treating system/vendor/oem as original a setting (auto-detection is not completely reliable)
    - File selection activity now remembers last location
    - Fix drawer closing on back button press on tablets like Pixel C
    - Fix overlay display visibility on [email protected]
    - Detect and handle screen scaling on [email protected]
    - Fix archive scanner freeze when reading password protected ZIPs inside another archive
    - Fix seeking issue with custom recovery detector
    - Fix archive scanner inconsistency with multiple files targeting the same partition
    - Fix archive scanner scanning inside images
    - Fix archive creator display inconsistency
    - Fix unconditional block update ZIP detection
    - Fix busybox/untar not setting SELinux file context on files that already existed
    - Hide cache wiping options if no cache partition present
    - Restart and re-check for root if root not found initially
    - Refactor boot image analysis
    - Preserve recovery: option hidden from devices without a dedicated recovery partition
    - Replace update_engine service on A/B update devices
    - Add intent to flash a specific ZIP file
    - Workaround adb restore 'never-finish' issue by using adb push (temporary?)
    - Embedded SuperSU updated to v2.79 SR3
    - Adjust timebomb for non-Pro users to May 01, 2017

    2016.09.19 - v0.53 - RELEASE NOTES
    - Embedded SuperSU updated to v2.78 SR1
    - Adjust timebomb for non-Pro users to February 01, 2017

    2016.07.18 - v0.52 - RELEASE NOTES
    - Add option to delay reboot after flash
    - Fix mixing of 32/64-bit commands on NP4/64-bit
    - Fix re-mounting of lazily unmounted system partition
    - Fix partition detection on some Motorolas
    - Fix cache wipe breaking subsequent OTA on some devices
    - Detect 'full' OTA ZIP, and do not warn about modified /system in that case
    - Move 'preserve recovery' option from OTA/ZIP action to Reboot action
    - ZIPs: Add 'getprop' command emulation if /system not mounted
    - Fastboot: don't use 'fill' chunks
    - Credits listing updated
    - Embedded SuperSU updated to v2.76
    - Getprop harvesting

    2016.07.07 - v0.51
    - New TriangleAway binary that can read SGS6/7 status
    - PIT support
    - Wipe: Only remove .supersu if wiping systemless SuperSU
    - Wipe: Fix wiping systemless SuperSU from /data
    - OTA: Add additional Samsung paths

    2016.06.01 - v0.50 - RELEASE NOTES
    - Fix compatibility with N Preview 3 (in used libraries)
    - Added 'Restore from ADB' option to 'No backups found' dialog
    - NP3: Work around ART crash
    - NPx: Work around 'adb restore' bug by using 'adb push' instead
    - 4.2: Fix StatFs crash
    - ADB: Authorize all connections
    - ADB: Fix restoring not doing anything on some devices
    - Force 'clear cache' option to show UI
    - Include filesize in cache validation
    - (Temporarily?) Switched back to single-threaded lz4 implementation due to the multi-threaded version occasionally segfaulting
    - Add choice for visiting either FlashFire's website or the XDA thread when tapping the top card

    2016.05.11 - v0.33 - BETA - RELEASE NOTES
    - Add support for backing up to and restoring from ADB, through USB or Wi-Fi (special ZIP format)
    - Completely reworked progress code, more info is shown in more places now (current file, speed, progress)
    - Improved back key handling
    - Improved app startup performance
    - If sdcard is adopted, reflect that in location display name
    - Fix adopted SD card sometimes not showing up in mixed partition mode
    - Attempt to identify external sdcard (rather than calling it USB)
    - Adjust storage location display order
    - Add warning when using adopted storage
    - Rewrote file creation routines to cope better with adopted storages
    - Fix reboot card popup title
    - Refactor shell commands as root
    - Change install location to internal-only
    - Fix backup of internal storage not skipping backups in some cases
    - Adjust ZIP parser so it can cope with Samsung FOTA ZIPs
    - Added warning for Huawei users about brickability
    - Add OEM partition to TWRP emergency restore
    - Fix backup/restore per-file progress freezing
    - Archives: Add suppport for Huawei's UPDATE.APP format
    - OTA: Add detection for Samsung
    - OTA: Add detection for Huawei
    - OTA: Add detection for HTC
    - OTA: Add detection for Letv
    - OTA: Add multi-zip-file capability
    - Partitions: Add various Tegra-specific partitions
    - Partitions: Add various Mtk64-specific partitions
    - Partitions: Add various Huawei-specific partitions
    - Partitions: Add various Pixel-C-specific partitions
    - Partitions: Add generic Factory Reset Protection partition
    - Partitions: Add support for eMMC boot and general purpose partitions
    - Partitions: Attempt r/w unlock before writing
    - EverRoot: Updated embedded SuperSU to v2.72 BETA
    - EverRoot: Use LESSLOGGING mode, reduces SuperSU output

    2016.04.20 - v0.32 - BETA - RELEASE NOTES
    - Exclude multirom folder from internal storage backup as well
    - Ability to create fastboot flashable backups (read the release notes!)
    - Use proper ioctls for partition and block size detection
    - Added option to backup recovery before installing ZIP/OTA and restoring it afterwards (automatically enabled when a custom recovery is detected)
    - Added a watchdog to detect SurfaceFlinger crashes, fixes some black screen issues
    - Prevent repeating OTA flash suggestion on rotate
    - Added credits listing

    2016.04.05 - v0.31 - BETA - RELEASE NOTES
    - Exclude usbStorage folder from internal storage backup as well
    - Switched to multi-threaded lz4 implementation (much faster backup/restore)
    - Replace gzip with pigz in flash mode
    - Set umask to 0 in flash mode
    - Use tmpfs for /tmp
    - Fix several other issues preventing flash mode from starting (reboots)
    - Fix bug in TWRP restore listing (warning: old backups may not restore in TWRP !)
    - Fix files present in firmware packages not being shown if the partition cannot be found
    - Fix sdcard daemon running multiple times and eating CPU for no reason
    - AROMA: prevent reboot call
    - AROMA: only do framebuffer emulation if AROMA is actually detected, to prevent running into https://code.google.com/p/android/issues/detail?id=178583

    2016.03.31 - v0.30 - BETA - RELEASE NOTES
    - Exclude TitaniumBackup folder from internal storage backup as well
    - Add location (internal storage, sd card, USB drive, ...) to backup listing
    - Improve compatibility with StickMount-based USB mounts
    - Fix a number of issues that could cause reboot while switching to flash mode
    - Fix display brightness on some devices
    - Framebuffer emulation for AROMA Installer (pretends to be a debugger, hijacks graphics calls)
    - Fix bug where cache partition could lose data
    - Complete refactor of flash mode code
    - Improve Samsung CSC handling
    - Fix bug where internal storage mounting could fail if external (sdcard/usb) storage present
    - Update embedded SuperSU to v2.71

    2016.03.22 - v0.29 - BETA - RELEASE NOTES
    - Fix some compatibility issues with N Preview
    - Fix app_process causing a reboot during startup
    - Fix bug which could cause flashing /system to freeze
    - Improve partition detection size accuracy
    - Reduce app startup time
    - Reduce time taken to switch to flash mode
    - Add option to format /cache (wipe action)
    - Improve external sdcard compatibility
    - Improve adopted storage compatibility
    - Improve USB drive compatibility
    - Add additional OTA paths for NVidia
    - Improve partition platform detection
    - Add support for backing up internal storage (excludes FlashFire, TWRP and CWM backups)
    - Fix error when opening bootloader image not wrapped in an archive
    - Add setting to enable flashing primary and secondary bootloaders (automatically disabled)
    - EverRoot: "Enable ADB" no longer enabled by default

    2016.03.14 - v0.28 - BETA - RELEASE NOTES
    - N preview compatibility (requires SuperSU v2.70)
    - Properly copy selinux contexts
    - Updated embedded SuperSU version to v2.70

    2016.02.03 - v0.27 - BETA - RELEASE NOTES
    - 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

    2016.02.01 - v0.26 - BETA - RELEASE NOTES
    - (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 or 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

    2015.09.10 - v0.24 - BETA
    - Fixed about a dozen FC's caused by Google's new and "improved" compatibility library

    2015.09.09 - v0.23 - BETA
    - Motorola: sparsechunk format support
    - Motorola: MD5 listing/verification support
    - Motorola: firmware package support
    - Samsung: Fixed brightness slider disappearing from notification shade

    2015.06.17 - v0.21 - BETA
    - Fixed MD5 issue (showed up when creating a .tar.md5 package)
    - Possible fix for mid-operation reboot

    2015.06.02 - v0.20 - BETA
    - Fix FC on 64-bit
    - Disclaimer shown only once (and each update, data wipe)
    - Possible fix for backlight issue

    2015.06.02 - v0.19 - BETA
    - MD5 routines now 30x faster (improves backup, restore, verification)
    - Changed faulty warnings
    - Updated BETA expiration (sep 1)

    2015.05.02 - v0.18 - BETA
    - Fix archive creation (for protected partitions) that broke on v0.17
    - Split backup files into 1GB chunks

    2015.04.30 - v0.17 - BETA
    - Updated partition resolution (Motorola)
    - Sparsechunk support (Motorola) - DO NOT USE YET
    - Motorola ZIP package support (no MD5 checks)
    - Fixed LZ4 restore issue
    - Fix crash on navigating to '..'
    - Updated preview timeout

    2015.04.29 - v0.16 - BETA
    - Added various partitions
    - Experimental CM SU compatibility - not thoroughly tested
    - Out of space errors now logged during backup instead of just freezing
    - Added corrupt ZIP detection, in turn fixes several crashes caused by attempting to read corrupt ZIPs
    - Added LZ4 compression. Now configurable between None, GZIP, and LZ4.
    - Made threads used for GZIP configurable
    - Added kernel wakelock
    - Cache ZIP scans, speeds up file selection
    - Fixed several issues on 64-bit devices
    - SuperSU updated to v2.49 BETA

    2015.04.13 - v0.15 - BETA
    - Improved logging
    - Improved startup procedure
    - Fixed an issue where backup of some files were represented as an error
    - Fixed a number of compatibility issues with latest Exynos (SGS6)
    - Fixed USB drive support on stock Motorola
    - Lowered default compression level and threads to reduce backup time and CPU usage (not yet user configurable)

    2015.04.09 - v0.14 - BETA
    - Fixed some black screen issues

    2015.04.08 - v0.13 - BETA
    - Fixed issue with log not being saved to internal storage
    - Fixed issue with slow internal storage detection
    - Fixed issue with error detection delaying reboot
    - Fixed misaligned wordwrap
    - AROMA compatibility (only if framebuffer device available)
    - External storage and USB storage support

    2015-04-08 - v0.12 - BETA
    - Auto backup renaming improved
    - TWRP restore ZIP added to backups
    - Force grow ramdisk

    2015-04-07 - v0.11 - BETA
    - Initial release
    96
    --- reserved #2 ---
    78
    --- reserved #3 ---
    73
    --- reserved #4 ---