yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] ktmom:
It's clear from the log that you're never getting into the actual backup. Is your SELinux in "Permissive" mode? If not, or you don't know, that's a good question for the device forum. I haven't had a Samsung device since the original epic [emoji3]
[Paid Software Announcement and Discussion] fiverings:
I flashed the Jasmine 6.1 rom on my Galaxy Verizon Note 3 long time ago using Flashfire. Now I'm selling this phone. Can I flash the same rom over the same one as before to get my account off the phone. If yes, then what would I have to wipe to do so. Or is there another method to accomplish this.

Thank you
[Paid Software Announcement and Discussion] ktmom:
Mounting r/w with a file explorer won't help FF.

The wake_lock had been a thing since 5.0.
[Paid Software Announcement and Discussion] Ibuprophen:
As much as FlashFire is a popular and extremely powerful tool/utility, it's not a perfect one and is sometimes just not for everyone and/or every device.

There are individuals who prefer others like Flashify (off the top of my head), amongst many others out there that others have preferred, for their own reasons, that can also do a good job in their own write.

Choices are out there... You've just got to look for it and try for yourself. I, and others, just can't state/endorse another option, because in similar circumstances, the member could potentially come back to ask for other app names or even point fingers at another member for whatever reason that didn't work out.

I wish you the best of luck!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] ktmom:
A clean flash of a ROM including the internal storage will effectively factory reset the phone. This isn't really a FF question though.
[Paid Software Announcement and Discussion] jcmm11:
Settings:accounts, select account, look for remove option (3 button menu on my current version). Flashing a ROM would just replace contents of system partition, which would do nothing for account info.
[Paid Software Announcement and Discussion] Dirty Flasher:
I saw that post but assumed it was "a thing" that didn't generally impede the rest of the install, whereas from the abrupt stop in the next line in my log, I thought that perhaps it was impeding it in this case.

For example, in my log, the "no such file or directory" line and the "stage 1 stop" line are lines 380 and 381 respectively, and the log ends there.

Whereas, a post or two before mine, another member links to their log at pastebin and the same lines are seen at line numbers 475 and 476 respectively, yet their log continues for another 1600 odd lines.

So it appears the no file/stop issue didn't stop their process and yet it did stop mine rather abruptly. I thought it may be significant that I found the file in question where it was meant to be.

Thanks anyway.
[Paid Software Announcement and Discussion] Bakuryu42:
According to my device info on my phone it currently Enforcing. SO no its not in Permissive mode and apparently to change that so that its like that in boot is a huge pain in the ass. Now what do I do? Also shouldn't SuperSu be enough?

[MENTION=631273]Chainfire[/MENTION] wouldn't mind your opinion of this as well.
[Paid Software Announcement and Discussion] Ibuprophen:
One of the requirements for FlashFire to properly work is that your SELinux State must be in a Permissive Mode whenever you are using it.

With that stated, try the following to see if it can place your SELinux State in a Permissive Mode.

[APP][TOOL][4.2+]SELinuxToggler

If it worked, then FlashFire should begin working properly for you.

Be sure to read the SELinuxToggler's OP carefully to ensure that you meet the Prerequisites first.

I wish you the best of luck!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Dirty Flasher:
I think you just need to wipe/format the data partition.
[Paid Software Announcement and Discussion] Bakuryu42:
Doesn't work I'm on Samsung Galaxy S5 4.4.2
[Paid Software Announcement and Discussion] Ibuprophen:
The app is for 4.2+... That means it's compatible with the 4.2 and higher.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Bakuryu42:
See my edit I forgot this is a general forum location. Full phone info is

Phone: Verizon Samsung Galaxy S5 SM-G900V

Android Version: Kit Kat 4.4.2 NCG

Kernel Version: 3.4.0

eMMC Chip: 11 Toshiba

Bootloader: Locked

Rooted: Yes

Safestrap: Yes
[Paid Software Announcement and Discussion] Ibuprophen:
I've seen it work for similar devices but, no guarantees.

The SELinuxToggler doesn't write anything permanent to your device. If it doesn't work then you can just uninstall it and reboot.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Bakuryu42:
Unfortunately it does not seem like it is working for me. What are my options at this point? The requirements for FlashFire according to the site is

So why isn't SuperSu enough?
[Paid Software Announcement and Discussion] Ibuprophen:
The following link provides the information as to SuperSU's what, how and why.

http://su.chainfire.eu/

The following is one of many links that provides the information as to SELinux's what, how and why.

https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
Just a second. He already has SuperSU. his selinux doesn't have to be in permissive. Even if it did (from my personal experience), flashfire will not even show the flash list and show a big red exclamation mark.
[Paid Software Announcement and Discussion] TheLastBoyScout:
Attempting to flash NHG47K on to my Pixel XL using FlashFire, but I keep getting the following error:

Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)

My google-fu isn't turning anything up in regards to this, so I'm hoping someone here is able to point me into the right direction.

**Edit: I did test with the latest Google OTA, and FlashFire loaded it with no issues, making me wonder if the Verizon OTA has an issue**
[Paid Software Announcement and Discussion] spainter:
In my experience: Everything Verizon has an issue when it comes to their updates and a locked down phone.
[Paid Software Announcement and Discussion] TheLastBoyScout:
Ordered my phone from Google, so it's not locked down (I.e. bootloader is unlocked), but I do use Verizon, so getting the patches for their network would be nice.

It is entirely possible they have mucked something up in the OTA Zip that is causing this error.
[Paid Software Announcement and Discussion] Bakuryu42:
Well considering I am not writing the app I don't see how this is useful to me? As the next person mentions I shoudn't need to worry about SELinux because I have SuperSu it even says so the chainfire website.

This is what I was trying to say. Also didn't know about the flash list thing.
[Paid Software Announcement and Discussion] spainter:
You should stay with the updates from Google there is a difference since the Verizon Pixel has a locked down bootloader. You will get the same updates. But you won't have to wait for Verizon mess with all their advertising junk.
[Paid Software Announcement and Discussion] TheLastBoyScout:
Yeah, it might be what I have to do. However it was my understanding that the Verizon update had network specific tweaks, but no advertising junk in the update.
[Paid Software Announcement and Discussion] Brett_Ryland:
Nexus 6 2017-04 OTA patch failed to flash

Hi, I'm trying to flash the latest OTA update (2017-04 patch) on my Nexus 6, which I rooted with the Nexus Root Toolkit, however I get a message

E3005: "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8688870:a619c8e6e6ab1f7e46e07a670c2de345af29457f:8688870:649e9f03a530a9c3a08f92dd9ac3038c4cd3c27c" has unexpected contents.

(line 351 of the attached log: pastebin.com/cGvjfaYr) and the phone reboots after apparently restoring from ramdisk. The phone works fine, but the update has not been installed and I can no longer find the update file. Could somebody please advise me on what I should do now to get the update installed?
[Paid Software Announcement and Discussion] Ibuprophen:
According to [MENTION=631273]Chainfire[/MENTION], on the following post:

"FlashFire needs to modify SELinux for flashing to work."

https://xdaforums.com/showpost.php?p=71747642&postcount=5395

Even though SuperSU is installed and should work, the bottom line is that FlashFire still needs to be able to modify SELinux to work. This means that FlashFire has to be able to change the SELinux mode and if it can't, and the user can't do it manually, FlashFire will not work.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Bakuryu42:
Here's the rub I have a backup from a year ago, I dunno what version of FlashFire it was, but it worked. Now unless something changed on my phone to suddenly make is enforcing instead of permission than it wasn't required then, so why is it not working now?

I'd like to hear what [MENTION=631273]Chainfire[/MENTION] has to say about this, as well as see if that is even the issue.
[Paid Software Announcement and Discussion] Ibuprophen:
I am familiar with what you're stating...

FlashFire v0.53 was the last release that did work for many individuals because of a SELinux loophole style bug was present up until that release. That release is the version that I use on my other Samsung S4 device to flash install the Stang5litre.

This was addressed upon Chainfire's release FlashFire v0.55 that enforced the SELinux requirement.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] jcmm11:
https://developers.google.com/android/ota
[Paid Software Announcement and Discussion] Bakuryu42:
So a bug that enabled people to use the app... was fixed.. And apparently I can't get that version to work on my phone for some reason, did the timebomb on it run out?

Also that same post you linked to also said:

He only mentions setting SELinux to permissive for CM/LOS, but not stock.
[Paid Software Announcement and Discussion] Ibuprophen:
It wasn't really a bug... I had used the wrong word for it when i should have just linked Changelog. The following is a link to the v0.55 Changelog where you will find the changes that were made for enhancing the app.

https://plus.google.com/+Chainfire/posts/CCvS3gZ5Lzk

I guess you could say v0.53 was a kind of an inadvertent "blessing in disguise".

I know that and, not long ago (if you look back a bit at the posts), i had just asked for this clarification your asking and I had provided the link to the post where Chainfire had provided this clarification.

I understand that it can be a bit confusing but, it had taken me quite a while to get an idea of it myself.

I'm trying my best to help you, my friend, to understand it via text.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] ARandomNoob:
Can this be used on devices with as little as 400mb of ram? If i make a back up and flashfire fails during the backing up process will my device likely be left unharmed? i know it wouldn't be good if it failed during the flash. If a back up goes ok is it likely a flash will be successful? If i have 2 generic devices same hardware exactly and they are on the same android and kernel version could i back up the system partition from one and flash to the other? If just wanting to put the system partition of one phone to the other what are the exact steps? sorry that there is so many questions lol
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
I doubt it can be used on your device. I also doubt that a botched backup will do anything bad(personal experience). A restore, on the other hand, will most probably cause a bootloop. If you try this, make sure you have a custom recovery and a NANDroid backup.

Also, curious, why would you duplicate /system on two exactly same devices? what do you wanna do?

---------- Post added at 09:20 AM ---------- Previous post was at 09:08 AM ----------

I respectfully think that, Ibuprophen (is that a medicine?), that the one confused is you. The SuperSU binaries allow patching SELinux while the CMSU's do not (atleast not in enforcing). It is as simple as that. The guy in question has replaced his binaries, and can just run flashfire. REPEATING MY EARLIEAR STATEMENT: If there was a problem with the SU or SELinux, flashfire will tell you. There is some other angle to this.

---------- Post added at 09:32 AM ---------- Previous post was at 09:20 AM ----------

Sorry... Just a fancy name i made up for the list of tasks FF shows when you open the app.:D:D
[Paid Software Announcement and Discussion] ARandomNoob:
so since you believe a failed back up will not have a negative effect do you think if a can successfully backup is it likely that the flash would go as smoothly, i'll back up 3x and see if the check sums match.

there is no custom recovery or anything they are just some generic phones. there is a software issue causing the home button to not work on one and would like to create a backup on the working one and flash it to the phone with the issue.

Has anybody used this on A ram device like that?
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
See, everything is chance. A correct backup 3x certainly does not guarantee a right restore (even though it is pretty clever and increases the chances.)

p.s. you sure it is a firmware issue and not an hardware one?

p.p.s. lemme take a guess... is it a chinese phone?

Good luck and be sure to tell what happens.:highfive:
[Paid Software Announcement and Discussion] ARandomNoob:
thanks lol, yea i know it's never a guarantee, basically 100% sure it's not hardware. surprisingly its not Chinese.

ok will do for sure:) but going to wait a bit maybe somebody can con confirm they've used it on a device with such little ram.
[Paid Software Announcement and Discussion] agabey_42:
[MENTION=631273]Chainfire[/MENTION]

I wrote earlier but it was not answered. I can add Turkish language. Why do not you want the program to have multiple languages? I add the Turkish translation file, it would be very nice if you add the program.

link : https://mega.nz/#!RhQAkK6Z!jNLla8tJue_gcpyE8W4iExd0QSZcbGI31QoVFKqO1Ko
[Paid Software Announcement and Discussion] Bakuryu42:
Yes and I read those posts and he didn't clarify completely if you read what he said it conflicts with my current situation. He said

He then said

I have SuperSU and its installed and working as it grants FlashFire root. So why does it not work? Also why did it work in the past? Also checking the change log for the link you posted only mentions fixing busybox not setting SELinux file context on files that already exist. Nothing about enforcing/permissive.

Everything you said makes sense to me, I feel like only [MENTION=631273]Chainfire[/MENTION] can clarify this situation at this point unless someone has any ideas as to what else would cause my issue.
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
Hey, Bakuryu, I was going through your posts and i just noticed you didn't mention your ROM. Does this mean you are on a stock ROM? Also, which backup were you trying? did you try a small ID backup (IMEI, MAC, etc)?
[Paid Software Announcement and Discussion] Bakuryu42:
It's stock. Also the small ID backup didn't work :\
[Paid Software Announcement and Discussion] KaMyKaSii:
Requirements

Android 4.2+ or newer

Please note that testing is done primarily on 6.0+ devices

Root access

Full root access is required, using either a recent version of SuperSU, CM's su with SELinux set to Permissive, or Magisk

1 GB RAM

A lot of RAM is used by FlashFire. Operations may fail completely on low memory devices

Unlocked bootloader

While an unlocked bootloader is not strictly necessary for many of FlashFire's functionalities, we strongly recommend all root users to run unlocked if possible. With locked bootloaders, there is a much higher chance of a device being unrecoverable if something goes wrong. This is not just true for FlashFire, but for many root apps. The specifics are device dependent.

Compatibility

While FlashFire is primarily developed and tested on Google Nexus and Samsung flagship devices, basic testing has been done on many other brands and devices, and users are using it succesfully on many more.
[Paid Software Announcement and Discussion] ARandomNoob:
ty but I've already read this and have used flashfire multiple times on a device with 800MB of RAM and i'd like to know if someone else had tried it with as little as 400

or anything low really (:
[Paid Software Announcement and Discussion] jcmm11:
Big difference between 400 and 800. Small difference between 800 and 1GB. If it really needs 750 the requirement would probably still say 1GB, especially when you think about common ram sizes. I'd say that 400 is just way too much off the mark.
[Paid Software Announcement and Discussion] Dirty Flasher:
Be a trail blazer. Look at it this way... If you brick your phone, I'll be OK.
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
Man, great ideals.
[Paid Software Announcement and Discussion] Dirty Flasher:
Yeah... I suppose I'd be a better person if I spammed a thread voicing my annoyance with a free app not working to my personal satisfaction, asked the same question repeatedly despite the answer being self evident, made clear by the OP, and the same sound advice being given repeatedly by other experienced users, argued with people who, for some reason, were still trying to help me, and made repeated demands that the busiest developer in android drop what he's doing and address my concerns because, you know, he owes me. They're some ideals to aspire to. :) lol
[Paid Software Announcement and Discussion] Brett_Ryland:
I see several builds of each of the versions there, which I assume correspond to the monthly security updates. Should I reinstall the NBD92D build of 7.0.0 that was on my phone when I rooted it, the updated 7.0.0 build NBD92G, or can I safely install the latest 7.1.1 build N6F26Y before re-rooting it? Thanks!
[Paid Software Announcement and Discussion] ARandomNoob:
I have yet to try it on the devices with 400MB but i did find a phone with 670 mb of ram today and was able to back up and restore without a problem for anybody who would like to know.:):good:

Edit i won't be able to attempt this on the device sadly, the back up button is out of the way (the screen is to small i guess) and the actions are not scrollable but was able to wipe 3rd party apps and dalvik with it so maybe it would've been possible but who kows /:
[Paid Software Announcement and Discussion] Dirty Flasher:
Lol I wasn't referring to you.
[Paid Software Announcement and Discussion] Barry Mad:
[MENTION=8184198]Dirty Flasher[/MENTION] well said/stated. Thank you for your referall back to this thread. Really enjoying revisiting chainfire code/work. Don't think people know who you really are with your new XDA handle. Good to See you here again.

Cheers & Respect. bmad
[Paid Software Announcement and Discussion] ashyx:
Lol, short and to point and totally true. :cowboy:
[Paid Software Announcement and Discussion] jcmm11:
You should be able to just install the latest build.
[Paid Software Announcement and Discussion] Khoadang:
I cannot use this app to update ota my phone( asus zenfone 2 laser z00ed) i downloaded the update file and open the app but nothing happen

* sorry for my bad english
[Paid Software Announcement and Discussion] Bakuryu42:
Ok so I decided to test doing a backup with Flashfire on my Nexus 10 and big surprise it worked. I checked the lastlog file and didn't notice anything specifically different. One thing I did notice and checked was that I although the Nexus 10 is already on Lolliop I could change the SELinux to permissive in the terminal console, while I cannot do this this on my S5. If this is the reason why this isn't working what are my options? Does this mean I can't flash anything either and if so why was I able to get this working previously and not now? I understand that it was changed to make it so it had to be permissive, my question is why was that change made if it worked without it?
[Paid Software Announcement and Discussion] Ibuprophen:
Please keep in mind your quoted statement when I ask this (though your statement kinda contradicts itself).

Since [MENTION=6420229]Bakuryu42[/MENTION] has SuperSU and its binaries installed successfully, can you please explain why the SELinux state isn't being changed on his S5?

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Chainfire:
I haven't really followed the conversation here, but it seems you guys are stuck in loop.

I'm not sure what the problem is exactly, but FlashFire not working could be due to many things, why do you think SELinux is even the problem?

If FlashFire thinks it will not be able to modify SELinux, it will warn the user about this.

SELinux state change is only performed when you press the Flash button. At this point, I'm not even sure how you're checking if the SELinux state has changed or not. And even if you were doing that, the check result would most likely be wrong. The method by which SELinux is bypassed does not show up in settings, nor with a getenforce command.
[Paid Software Announcement and Discussion] Ibuprophen:
I really appreciate your chiming in and clarifying the SELinux matter.

Your a great person and Admin!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Bakuryu42:
This all started really with the fact that I can't do a backup. The issue is once I start a backup it reboots, does its thing, reboots again except instead of booting into flashfire it does a normal boot and gets to the verizon logo where it stays until I hard reset the phone. Here is a recent lastlog of when I ran a backup. I have yet to try flashing anything, but felt it was to risky if I couldn't backup the phone first.
[Paid Software Announcement and Discussion] louiedee279:
Where the download i.usually use odin to root but if this is better great. I ll have to wait till i get the s8 teturning the s7 edge.
[Paid Software Announcement and Discussion] lop1:
Hello, is there a Way to get some help to make backups with Flashfire on the Samsung A3 2017 ?

Envoyé de mon iPad en utilisant Tapatalk
[Paid Software Announcement and Discussion] Ch3vr0n:
Press the backup button, select mode, done.
[Paid Software Announcement and Discussion] Ibuprophen:
I have a feeling that your rooted but, your bootloader is still locked up...

Am I correct?

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Paid Software Announcement and Discussion] dratsablive:
You can't have a locked bootloader and be rooted can you?
[Paid Software Announcement and Discussion] Badger50:
Nope.
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
Yup, you can... there are many other ways of rooting than flashing supersu... though i am still wondering how he deduced that just from that one line.