yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] corkiejp:
18GB free I suspect your referring to your data partition.

Your cache partition seems to be causing the problems with the app not working.

Use FlashFire to wipe just "Dalvik Cache" and "Cache partition".

Then try the OTA update process again.

Error-ed out a Line 234

[OUT] 28753920 bytes free on /cache (56834504 needed)
[Paid Software Announcement and Discussion] aBigMeanie:
tried wiping them twice, but still fails to install ota each time.

new log <script src="//pastebin.com/embed_js/sQYR7ij0"></script>

pretty much the same. looks like wipe doesn't increase cache size

looks like i can attach files here now.
[Paid Software Announcement and Discussion] corkiejp:
Yes error-ed out at the same point. Maybe [MENTION=631273]Chainfire[/MENTION] or someone else can understand the problem here better
[Paid Software Announcement and Discussion] samccfl99:
You are asking him another question??? LOL.

He only answered you to begin with to tell you he could care less...YOU SHOULD BE HONORED!!!

SORRY, I JUST HAD TO...
[Paid Software Announcement and Discussion] tuxStyle:
So, i updated to 28 beta and tried to flash the Android N preview on my Nexus 6P.

I was running the first version of the preview and i noticed an update.

The problem is... it's getting stuck.

There seems to be something wrong with the flash size.

It says:

Partition Size: 2047 MiB

Flash Size: 2422 MiB

Any ideas?
[Paid Software Announcement and Discussion] demlv:
No, he was saying he COULDN'T care less.

SORRY, I JUST HAD TO...
[Paid Software Announcement and Discussion] sharp87:
After successfully flashing the OTA update in my Nexus 6p using flashfire v0.27 ..The Android system still prompts me to install latest same update again..Is there any way to get rid of this ?

[emoji106]

S3⃣nt ? G➿gle Ne❌uS 6⃣P
[Paid Software Announcement and Discussion] Ja_som:
I had same issue on my N5X, flashing system stuck almost on end for few minutes, then screen goes black, was still on, but black, without any text.

I had to reflash it via fastboot on PC.
[Paid Software Announcement and Discussion] Chainfire:
Root needs to modify boot. There's a good chance your locked device will check for modified boot and fail to boot.

Your cache size appears to be wrong. You need to format it. I've made a note to see if I can include an option for this in future versions of FlashFire. In the mean time, from adb shell, you can do the following:

get root:

su

list cache mount:

mount | grep /cache

that will output something like:

/dev/block/platform/15570000.ufs/by-name/CACHE

/cache ext4 rw,seclabel,....

unmount by doing:

umount /cache

format:

make_ext4fs

/dev/block/platform/15570000.ufs/by-name/CACHE

reboot:

reboot

Reproduced. Will see what this is about.

It should go away by itself after a bit. If not, try going to Settings -> About -> Software update.
[Paid Software Announcement and Discussion] Chainfire:
Aargh. Just confirmed this is a bug in Android itself. Seeking files beyond the 2GB barrier is broken on N Preview (works fine on older Android versions), this both causes the flash failure as well as the partition size to be reported as 2047 MiB (~= 2GB, maximum 32-bit signed integer value).

There goes my afternoon submitting a bug report to Google...

The bug is present in the 2nd version of N Preview as well, by the way, so you won't be able to use FlashFire to upgrade from npc56w to the 3rd version of N Preview either.

This specific error is sooo bloody 2008. I'm surprised they managed to introduce it into a previously working system.

EDIT: https://code.google.com/p/android/issues/detail?id=204389
[Paid Software Announcement and Discussion] tuxStyle:
Thanks for checking. I'll do it with fastboot and then CFA for SU

Thanks again
[Paid Software Announcement and Discussion] caseyatbt:
I joined the beta tester link on the first post and then the link to download gives me this:

We're sorry, the requested URL was not found on this server.
[Paid Software Announcement and Discussion] Christiancs1969:
Give it time. Check again in bit
[Paid Software Announcement and Discussion] roofrider:
[MENTION=631273]Chainfire[/MENTION]

Is this a bug or is it not possible to flash bootloaders via FF on the 5X?

I didn't get a clarity on the below issue either (from you or the community) so can I assume that FF isn't compatible with MultiROM?

Logs are present in the original post: http://xdaforums.com/showpost.php?p=65799621&postcount=2618 Let me know if you need anything else, will be glad to assist. Thanks!
[Paid Software Announcement and Discussion] RoadToNever:
It always leads me to:
[Paid Software Announcement and Discussion] johnlgalt:
I hit the restart and install and then it performed a system check and abruptly told me I was up to date.
[Paid Software Announcement and Discussion] RoadToNever:
It stalled after the reboot countdown. After manually restarting the prompt doesn't show up any more.:good:
[Paid Software Announcement and Discussion] robboby:
Hello,

personally successfully tested on:

i9195, c115, i9505, i9515, g900fd, G360F (of course it works on many other devices) ...

problem does not work on samsung sm- g361F (android 5.1.1) ... it opens does check by current binary: unknow and when the flash (or any operation) give black screen and after about twenty seconds, restart ....

[IMG="flashfire g361F"]http://i68.tinypic.com/2zq77mq.jpg[/IMG]

you can add compatibility?

thanks [MENTION=631273]Chainfire[/MENTION] !

I apologize for my bad english ....
[Paid Software Announcement and Discussion] shayind4:
You mean SM-P605? Knox 0x0?
[Paid Software Announcement and Discussion] SamuriHL:
SM-P600. Knox is tripped on mine.
[Paid Software Announcement and Discussion] Vaira:
???? :eek:

No, no other one. I just repeated the first part of my question from my original post!

I am using the paid app even though there is no advantage to do so yet, hence I should be allowed to ask a question about the tool being a customer.

To me one of the greatest features is everroot, which previously allowed to keep root without to trip KNOX.

It was unclear to me if the new approach introducing system-less root will break the signature and trip KNOX. :);)
[Paid Software Announcement and Discussion] Chainfire:
This is a bug. Put it inside a ZIP file and it'll flash.

MultiROM is not currently supported, and it is not all that high on my to-do list. It's there though.

The problem is that these KNOX related questions are hard to answer. Obviously all my own devices have KNOX tripped for a long time. So how can I guarantee something doesn't trip KNOX if I can't test it ?

That being said, I believe every non-exploit root method (such as TWRP and FlashFire) for Marshmallow and newer will always trip KNOX.

For the future, unless specifically stated otherwise, you should assume that every root method will trip KNOX.
[Paid Software Announcement and Discussion] roofrider:
Thanks! But i still don't have it all figured out. Here's what i did:

Created a .zip archive (store only) of the bootloader image, selected firmware package in FF and chose the .zip, but none of the partitions are selected by default (like it does in the case of vendor and recovery images). Primary and Secondary bootloaders are not available to select (screenshot attached). Confused. Please advice on the bootloader partition(s) that need to be selected (Primary alone?)

TrustZone, DBI/SDI, Image Data, PMIC, HYP, Keymaster, CMNLIB, and SEC can be selected but I don't know what those are.

Thanks, no worries. Since its not possible to flash vendor images on secondary ROMs via TWRP, I thought FF could help those of us using MR until such a functionality is added in MR TWRP.
[Paid Software Announcement and Discussion] arf8:
[MENTION=631273]Chainfire[/MENTION]

Posting in thread again.

Hi, I was hoping if could get your feedback on flaahfire and samsung s6 full disk encryption. I would like to use it with backups and restore but unsure if it can work with an encrypted phone.

Also I have been using flashfire since you released it, and on the s6 the backup does not backup the gallery and notifications memopad so upon a restore I always have to manually load these and countries figure the phone still.

Regarding the restore using flashfire, memo pad, Pics in "/storage/emulated/0/DCIM/" are never backed up and restored. I suspect that your app does not take into account phones like the S6 with built in flash memory so it does not look for those folder in this partition. The notifications are also stored by default in the same path "/storage/emulated/0/Notifications/" None of these are related or special in anyway to an account like google account or anything else they are the default for samsung and some of them are symbolic links to "/sdcard/" If you are willing to fix this I would be more than happy to send you any and all logs, I have root and can get around on my phone no problem. Flashfire is the only backup tool i use other than manually saving off these folders and configuring the notifications for contacts, voicemail, ringtones etc. It is quite a lengthy process but at least there is a way to restore.

Cheers
[Paid Software Announcement and Discussion] erichjelm:
Can't install the March OTA on Nexus 5x.

Could it be because of Xposed?

I couldn't find another place to ask this.

It reads the update and says it'll flash it then reboots and the build number is still the same (old) one and then gives me a notification to update again.

Do I need to enable/disable any settings?
[Paid Software Announcement and Discussion] Ch3vr0n:
As has been said before, even as recent as one or 2 pages ago, yes it's because of xposed. Xposed modifies /system, the second you modify system on a block level ota device you'll fail the block level check. There's an easy fix. You need to reflash your system image. Run the following sequence (I think, I don't use xposed)

1. Copy your current version system image and all xposed module zips to device storage

2. Select 'flash firmware package' and select the system you copied to device

3. Select 'flash ota or zip' and navigate to the ota file, make sure 'mount system as rw is DISABLED', check if everroot is enabled

4. Select 'flash zip...' Select your xposed installer zip and repeat 4 for every module you have

5. Press flash

That sequence should in 1go, reflash your system image followed by immediately updating to the ota and rooting at the same time, followed by flashing xposed and your modules. If I got this right you'll be running the ota version and your xposed will be installed and ready to go.

You'll need to redo that sequence every time because of the modified system.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Paid Software Announcement and Discussion] Vaira:
Thank you for your reply. I really appreciate it.:)

That sounds reasonable. I understand that.

Anyway I thought it is already exactly known what trips KNOX and when. :) and still having a condition rooted with KNOX 0x0 makes me curious of course.

To me the most exciting question in this regard is, if KNOX will be tripped when the initramfs has changed only but the kernel is still original.

Well the only way to find it out is to try it myself on a KNOX 0x0 device I guess. Modifying the kernel itself always would, though....
[Paid Software Announcement and Discussion] Chainfire:
This has nothing to do with encrypted vs unencrypted.

Anything under /sdcard is not currently backed up - by design.

A setting to include this is coming, though.

The signature is on the full boot image, not just the kernel binary. Modifying the initramfs will modify the full boot image and is thus likely to trip KNOX.

The app only selects the primary Android partitions by default (system, vendor, oem, cache, excluding userdata). All the options presented to you are actually present in the bootloader image file - if you'd flash the image file with fastboot, they'd all get flashed. The primary and secondary bootloaders are currently not able to be selected because if those get messed up, even fastboot will no longer work. There will be an option at some point to select these as well, at your own risk. Personally I just select everything possible and flash.

If MultiROM itself doesn't support it, it sounds unlikely something like that would ever work.
[Paid Software Announcement and Discussion] aBigMeanie:
Your cache size appears to be wrong. You need to format it. I've made a note to see if I can include an option for this in future versions of FlashFire. In the mean time, from adb shell, you can do the following:

get root:

su

list cache mount:

mount | grep /cache

that will output something like:

/dev/block/platform/15570000.ufs/by-name/CACHE

/cache ext4 rw,seclabel,....

unmount by doing:

umount /cache

format:

make_ext4fs

/dev/block/platform/15570000.ufs/by-name/CACHE

reboot:

reboot

thank you. i think i'll wait and see if you add to flashfire so i don't make a mess of it.
[Paid Software Announcement and Discussion] roofrider:
Thanks for the explanation. I selected whatever was available and flashed the bootloader, but when I boot into the bootloader it still shows the older version number. I assume this is because the primary and secondary bootloaders aren't flashed by the app?

I think with time this will be resolved since only the new nexus devices have this vendor partition and neither 5X nor 6P are official supported by Tassadar yet.
[Paid Software Announcement and Discussion] Chainfire:
Yes, what you see when you reboot into bootloader is the "secondary bootloader", and this one isn't flashed by FlashFire at the moment.
[Paid Software Announcement and Discussion] djtheraven:
I just tried to back up my ROM, and it went through the motions it took like 30 min and then rebooted. When I looked for the backup there's nothing there. Note 3 rooted stock 5.0. Did I do something wrong?
[Paid Software Announcement and Discussion] Rakuu:
Check lastlog, you might have ran out of space.
[Paid Software Announcement and Discussion] roofrider:
Cheers! Do you see there being any kind of conflict or issue due to certain partitions of the bootloader (primary and secondary) being old and the rest being updated?

Also, when you said you'd blocked the selection of primary bootloader to prevent fastboot from getting screwed up, did you mean that even when the correct bootloader images are selected there is a chance for something to go wrong (due to the app)? Or were you just referring to the human error of flashing a Nexus 5 bootloader on a 5X, resulting in bricks? The latter has happened a few times.
[Paid Software Announcement and Discussion] Chainfire:
If there will be issues or not is impossible to predict. I've never experienced any, but that doesn't mean there will not be.

As for the flashing of bootloaders being blocked, on some devices it isn't even possible for the app to flash them (and it is impossible for the app to know if this is the case or not). Flashing the wrong bootloader could indeed hard-brick as well. And then there's always the mid-flash power failure leaving the partition corrupted. Unlikely, but not impossible.
[Paid Software Announcement and Discussion] roofrider:
I have faith in your ability to code. Will be trying out the complete bootloader flash once those options become available. :p:fingers-crossed::good:
[Paid Software Announcement and Discussion] Chainfire:
v0.29 released

v0.29 released, release notes (and download) here: https://plus.google.com/+Chainfire/posts/GX4GSYkePYx
[Paid Software Announcement and Discussion] corkiejp:
Cache partition format now available in latest flashfire.

I wonder does it now also support backups to OTG?
[Paid Software Announcement and Discussion] Chainfire:
It depends on the device and method.

AOSP 6.0+ (Marshmallow) OTG mounts should work. Samsung-specific mounts should work. NVidia-specific mounts should also work. StickMount currently does not work.
[Paid Software Announcement and Discussion] minebynight8:
Whenever I attempt to flash xposed to my LG V10, the screen goes blank for about 5 seconds, the backlight turns off and then 5 seconds later it beings the boot process. The lastlog is provided below, hosted off my Google Drive.

https://drive.google.com/file/d/0B_JWBCHIKBtrMlBGNzhOUTFPSFk/view?usp=docslist_api

Any help would be greatly appreciated!
[Paid Software Announcement and Discussion] djtheraven:
I have a 128gb card with 110gb available and lastlog ends with reboot
[Paid Software Announcement and Discussion] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION]

with the changes in build 0.29 i decided to give my OTG drive (meenova adapter + sandisk 128GB with approx 103GB free) another try. In the attached zip file you'll find an image from the detected drives. If i select "USB drive 128GB (103GB free)", the device just reboots. If i select "USB drive 2123-1A07 (103GB free)" the backup process does start. However some time during the process, the backup failed due to an i/o error. Based on the backup directory, 2.7GB into the process. I have attached the needed logs for the 2nd attempt (backup to 2123...) in the zip file. I do have to say when the device rebooted, battery level was as 27%. Probably wasn't the cause. I had no additional tasks schedule. Just a simple backup.

** edit **

[MENTION=631273]Chainfire[/MENTION] the second attempt to 2123-... Went through successfully ended with something like /legacy. However I'm lacking a small functionality thing. The option to EXCLUDE certain folders. I also use TB which creates its backups on internal storage. When selecting internal storage with flashfire I'm basically making a backup of a backup. I also have some music on internal storage. Something that can easily be transferred back over if anything happened.
[Paid Software Announcement and Discussion] arf8:
[MENTION=631273]Chainfire[/MENTION]

I just read the change log for the new release, and it looks like you added sdcard backup. On Samsung the path is "/emulated/storage/0" is it safe to assume this is backed up also? I will test it this weekend hoping i don't have to go through the normal restore process post flashfire restore.

My question regarding encrypted backup & restore is whether or not Flashfire will have issues restoring a Full encrypted backup with phones like Samsung with Full disk encryption. A member mentioned to unencrypt the phone do the backup and encrypt again, same with restore process which is very cumbersome.

Just upgraded to Pro, yes i know there is no difference in function.

Thanks

---------- Post added at 05:56 PM ---------- Previous post was at 05:40 PM ----------

I could not wait, i tested and the internal storage "/emulated/storage/0/" was unfortunately not backed up.

"Additionally, the internal storage can now also be backed up, though it will skip FlashFire and TWRP backup files. "
[Paid Software Announcement and Discussion] Strizay:
Vs. .29 on my blu dash x plus xp d950u trying to flash Xposed still just reboots the phone and does nothing.
[Paid Software Announcement and Discussion] ozz200127:
Pull battery
[Paid Software Announcement and Discussion] VIP1961:
Error - ...Applying CSC [FAILURE]...

[MENTION=631273]Chainfire[/MENTION]

Galaxy S6 (SM-920FD), firmware stock 6.0.1, FlashFire - v0.29

When I try to flash part of firmware (cache and recovery) occurs error - ...Applying CSC [FAILURE]...
[Paid Software Announcement and Discussion] roofrider:
Did the full bootloader flash and everything was fine! :good: The pre-flash warnings did make me a bit nervous though, lol.
[Paid Software Announcement and Discussion] VIP1961:
How did you flash full bootloader ?
[Paid Software Announcement and Discussion] Ch3vr0n:
Go into settings and enable flashing bootloader, flashfire does the rest.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Paid Software Announcement and Discussion] VIP1961:
Thanks
[Paid Software Announcement and Discussion] UAEhawk:
Does it work on Note 4 please thanks
[Paid Software Announcement and Discussion] FletchF:
I've read the release notes and warning about bootloader flashing and I have a few questions:

- Why do my Nexus 5 and 7 devices have multiple bootloaders and what are they all used for?

- If I want to keep the bootloader updated when flashing the monthly Nexus factory images with FlashFire, which bootloader partition(s) should I check?

- If using FlashFire to flash the bootloader is "dangerous", what is the safe way to keep my bootloader updated? Should I flash the bootloader img file with fastboot and then use FlashFire for everything else?

Feel free to refer me to resources where I can read to learn more about this... Thanks.
[Paid Software Announcement and Discussion] Chainfire:
Sorry, I still have no idea why this happens or how to fix it for you.

So your USB disk is appearing thrice... That's certainly not good. Are you using both AOSP USB and StickMount at the same time or something?

What's the output of these commands (I know, tricky with USB connected):

mount
ls -l /mnt/media_rw/
ls -l /sdcard/usbStorage
ls -l /storage

I'll add TitaniumBackup to the (hardcoded) excluded paths.

How did you confirm the internal storage wasn't backed up? Did you select it?

I've tested this on about a dozen devices (including an S6) yesterday and today and there was not a single failure backing up or restoring the internal storage. Is there an intsd.tlz4 file in FlashFire's backup folder? How big is it? Please post the /sdcard/FlashFire/lastlog file of the backup (copy/paste to pastebin.com).

If the internal storage isn't backed up still, there's something different with your setup.

Regarding encryption (again), FlashFire doesn't care about that, as the firmware itself deals with that - this is a layer below FlashFire.

Nothing I can do to help you with this at this time, unfortunately.

I know there's some issue with the new CSC's. I'll look into it.

Does your firmware work though, or does it error during use, because of this CSC failure?
[Paid Software Announcement and Discussion] VIP1961:
Firmware works without errors and this occurs only during flashing.
[Paid Software Announcement and Discussion] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] I've attached an image how things appear without the USB drive attached. I assume you want me to run those commands through adb shell? Do I need to call su first? I'm not very experienced when it comes to running such command hence the question. However, if you look at the previous image, the USB drive of 128gb is only mentioned TWICE. If you'll look closely you'll see 'USB drive for Android' free space is equal to internal storage space.

Below image is without otg drive attached, the otg drive level is there but the size matches internal storage.

I do hope you'll add folder exclusion in a future version, perhaps that can be an option for pro.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Paid Software Announcement and Discussion] saccentekennedy:
Hello. With 276 pages in this thread I apologise if this has been asked before, but I'm looking for guidance.

I have a Nexus 6p with Viper installed, and therefore a modified System. So, instead of trying to flash the OTA, I downloaded the whole new updated image and used FlashFire to flash this (system, vendor, cache, boot) leaving Recovery unchecked as I have TWRP and wanted to keep it. I then reinstalled my Franco kernel. This worked fine withouta problem.

Then I learned that the updated image actually included an updated radio. So I went back into FlashFire and tried to flash the modem. This didn't go well and I was stuck on the boot animation until I could get to work and my work PC and use fastboot to flash the new image manually the way I used to.

My question is what should I have checked when installing the updated image from Google? This is so when the next update comes next month I don't have the same problem. Using fastboot I flash bootloader, radio, boot, vendor, system and cache. If I just want to use FlashFire in future to flash an updated image from Google for my 6p, how do I go about doing this safely?