yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] MikeDevenney:
I'm using a newly rooted Sprint S7 and want to run a debloat script to remove all the crap Sprint installs. When I try to open FlashFire it makes it up to the Enumerating Properties step (after detecting manufacturer and brand step) then it force closes (or is forced closed, I dunno). Is this a known issue? If not, is there something I can do to determine what is causing FlashFire to close? (probably relevant) I keep getting notifications from SecurityLogAgent that says Unauthorized actions have been detected... I'm guessing that maybe something Samsung installs is catching FlashFire during loading and shutting it down. If so, how do I prevent this?
[Paid Software Announcement and Discussion] -Tiz-:
I flashed Magisk 15 with FF on my Doogee S60 and now FF does not work anymore. Black screen. It previously worked with Magisk 14.3 and maybe with 14.5 and 14.6. I also installed and deinstalled Busy Box Pro. But FF does still not work.

How do I get back to old Magisk? Thanks
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
Whichever way you used to flash Magisk 14.3 in the first place, can you use it to flash the Magisk uninstaller I believe the dev(s) provide and then flash 14.3 again?
[Paid Software Announcement and Discussion] -Tiz-:
I flashed Magisk 14.3 with the help of Magisk Manager 5.5.1 (using the module installer). Now my phone does not start anymore (bootloop). I tried this with 14.6 before and it worked. Probably, 14.3 is not backwards compatible? I now need to try fastboot in order to repair the phone. It is encrypted and TWRP fails to decrypt data (although there is no password set). Apparently, the TWRP port for the Doogee S60 is buggy and does not support encryption.
[Paid Software Announcement and Discussion] slimcyril:
Use flashfire v0.53
[Paid Software Announcement and Discussion] elk1007:
I searched the thread for this issue but couldn't find an answer.

When I initially used FlashFire on my Samsung Galaxy Edge 7, I was able to backup and restore over ADB and to internal memory.

Now, when I attempt a backup operation, FlashFire will load and display the red bar logo with a black screen underneath.

I can't see any log and it appears that the backup is not being made. The blue light stays on.

Any ideas?
[Paid Software Announcement and Discussion] Ch3vr0n:
Restore your original boot image and loader. Then flash magisk 14.2 that's the one I can confirm myself works just fine with the latest flashfire version. Not the old 0.53 someone is telling you to use.

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] -Tiz-:
Thanks. The phone is back to life. However, I had to fastboot flash boot boot.img and fastboot flash system system.img. Now I have lost root. And TWRP is unable to mount data.

Is there any way I can root or directly flash Magisk via fastboot? Thanks!
[Paid Software Announcement and Discussion] KaMyKaSii:
Install Magisk Manager, patch your boot.img and flash on fastboot
[Paid Software Announcement and Discussion] brandon79:
I use flashfire on a s7 flat and have the same black screen but I found that backups take a while and if you let it do it's thing mine still makes a backup. It just doesn't show a log of what's going on. Maybe try and see if this works for you to. Mine even has a black screen when flashing anything.
[Paid Software Announcement and Discussion] -Tiz-:
Magisk Manager is installed. How can I patch the boot.img without having root (and TWRP not working on an encrypted Doogee S60)? Thank you.
[Paid Software Announcement and Discussion] KaMyKaSii:
Click "Install" and then "Patch Boot Image File". Good luck and let's stop here, this is already getting off topic
[Paid Software Announcement and Discussion] -Tiz-:
Agreed. I asked somewhere else for help (i.e. a patched boot image). The proposal you suggested does not work without root. Magisk manager needs root. But let's concentrate on FF.
[Paid Software Announcement and Discussion] BROKEN1981:
Will flash fire work with the LG V20 yet? Bought pro awhile back and never got it to flash stock ROMs.
[Paid Software Announcement and Discussion] elk1007:
This was exactly the case! I let the phone sit at the flashfire bar for an hour and it did make the backup after all with no log output.

Thank you!
[Paid Software Announcement and Discussion] brandon79:
Your welcome. I'm not sure why this happens but sometimes it will show a log ,other times it doesn't, but always works. Glad it worked for you as well.
[Paid Software Announcement and Discussion] Alxoom33:
No, No, No. Magisk and Magisk Manager system-lessly root your device. They don't need root. They provide it!.
[Paid Software Announcement and Discussion] -Tiz-:
On my non-rooted phone Magisk Manager does nothing and does not offer to install Magisk. On my rooted phone I did. Therefore, I believe that you are wrong. But if someone can confirm what you are saying I won't complain. But would be a huge security hole, wouldn't it?
[Paid Software Announcement and Discussion] mobileman88:
Rooting is always a security hole. It offers more power and flexibility but you got to manage it.
[Paid Software Announcement and Discussion] ipdev:
OT

[MENTION=2719998]-Tiz-[/MENTION]

It started with Magisk 13.5.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3

I have used this option to root a few devices.

Please move to a Magisk thread for more questions.
[Paid Software Announcement and Discussion] Alxoom33:
https://photos.app.goo.gl/31WjmRj7i6wlTUss2
[Paid Software Announcement and Discussion] -Tiz-:
I agree that this belongs into another thread. I have raised the question here ( https://xdaforums.com/showpost.php?p=74988038&postcount=21581 ) because my phone cannot be rooted solely with Magisk Manager.

EDIT: My understanding was confirmed in the meantime. https://xdaforums.com/showpost.php?p=74988109&postcount=21582
[Paid Software Announcement and Discussion] bnwg:
OT

Your understanding is correct but it seems you didn't perform the last yet the most important step - flash the patched boot.img via fastboot
[Paid Software Announcement and Discussion] uHawk:
I can't do anything with FlashFire in a Samsung Galaxy J7 2016 (J710MN), using the flash or backup operation gets the same result: a sudden reboot. I tried using both permissive and enforcing SELinux.

log: https://pastebin.com/5pfdGQJ2
[Paid Software Announcement and Discussion] bibikalka:
[MENTION=631273]Chainfire[/MENTION]

Update : see this post https://xdaforums.com/showpost.php?p=75043836&postcount=6315

Device: Amazon Fire HD 10 (7th gen, 2017), arm64, ~Android 5.1.1 :

[ro.build.mktg.fireos]: [Fire OS 5.5.0.0]
[ro.build.version.incremental]: [40.5.9.1_user_591450020]
[ro.build.version.name]: [Fire OS 5.3.5.1 (591450020)]

v0.73 of Flashfire opens, but does not "Flash" anything (simply reboots) and produces no "lastlog". v0.24 with a date workaround via Xposed works (v0.24 version found empirically). Here is a v0.24 log flashing SuperSu v 2.79 zip:

...

Coincidentally, SuperSu 2.79 flash fails, and puts the device into a bootloop. I tried to flash busybox.zip with the same v0.24, and this one worked fine - so v0.24 FlashFire functionality seems OK in general, and the issue was specifically limited to SuperSu 2.79 zip.
[Paid Software Announcement and Discussion] master64nl:
I have the same problem after the new magisk 15.1 on my Samsung S8 SM-950F

By trying different things I had to go to stock and root again and lucky there was an backup made by twrp manager so I could get the data back on my phone and is working now with the latest firmeware PHN.

Sucks not using Flahsfire for firmewareupdates and making backups.
[Paid Software Announcement and Discussion] Ch3vr0n:
The last working magisk version is 14.2, anything higher doesn't work with flashfire until chainfire returns from his break and updates flashfire.

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] master64nl:
Aha, that makes sense. So when I flash the magisk 14.1 back it runs normal again?
[Paid Software Announcement and Discussion] Ch3vr0n:
14.2 works too. But you might need to flash the original boot image and loader back first. You can't flash an older magisk over a newer one. I tried a little over a week ago when I needed to get FF working with magisk to restore a backup

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] master64nl:
I was today busy with it. Couldn't find anything about it. Thanks to your answer I get it. Anyway, I get everything back to how it was but no working Flashfire for the time being.
[Paid Software Announcement and Discussion] bibikalka:
Update:

I was able to force SuperSu 2.82 to flash correctly in FlashFire v0.24. The details are in this post.

With Flashfire, v0.24 works, while v.26 fails. No versions past v0.24 work. So the moment when things stopped working is fully established.

Here is a log for v0.24 (success): https://pastebin.com/e8SziwiH

Here is a log for v0.26 (failure): https://pastebin.com/qX6KL5zs
[Paid Software Announcement and Discussion] KaMyKaSii:
Did you even test all versions after 0.24? I remember that several users were also having this problem the last functional version being 0.24 (including me) and Chainfire posted us a 0.29 test version and it worked. Do not forget to change your clock to before the time bomb

https://xdaforums.com/general/paid-software/flashfire-t3075433/post66018664
[Paid Software Announcement and Discussion] bibikalka:
Yes, another member ( [MENTION=3497316]retyre[/MENTION] ) tested all the versions down from 0.73 until 0.24 worked. I tried that 0.29 test version from the above post, and it fails too. I can add the log if necessary.

I think the hybrid arm64/armv7 system set up is confusing the hell out of misc software.
[Paid Software Announcement and Discussion] bibikalka:
build.prop ?

So, I was thinking, the latest Flashfire works fine on other Amazon Fire tablets, but not on HD10 2017. I already ran into troubles with SuperSu thinking that the device is arm64, whereas it actually operates much more like armv7.

Could I try to hack build.prop to just force it look like armv7 everywhere ? Would Flashfire pick this up from the freshly updated build.prop? It looks like Flashfire is reading from the variable that's declared obsolete (ro.product.cpu.abi), if I were to look carefully. At least, that's what SuperSu zip seemed to do. What's the best way to feed the correct ro.product.cpu.abi=armeabi-v7a into Flashfire? Do I update /system/build.prop right before I run it?

Basically, I'd take these lines

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a

ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=

And make them something more like this

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=

Here is what a pure 32 bit Fire device with the recent working flashfire looks like:

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
[Paid Software Announcement and Discussion] AndroidHtc101:
Hello guys

Been using flashfire for Nexus 6P security updates Oreo without any problems.

Does it work on January 8.1 too?

Thanks just wanted to check. :)
[Paid Software Announcement and Discussion] jcmm11:
Updating build.prop should work. Based on what you've posted Amazon should have changed the value of ro.product.cpu.abi (even if it's obsolete if present it should have the correct value) since all the other entries indicate a 32 bit device.
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
Worked with Pixel to go from December 8.1 to January. https://xdaforums.com/showpost.php?p=75061297&postcount=1074 Have to be using Magisk v14.2 (unless you're on 8.0 with SuperSU or SuperSU still works on 8.1 on the 6P - doesn't on the Pixel) exactly as far as I'm aware, at least on the Pixel - I don't know if things are the same on the 6P.

Good luck!
[Paid Software Announcement and Discussion] Markeee:
Can someone help me out I'm trying to use Flashfire to update stock Dec to Jan OTA update on a Magisk 15.2 rooted Pixel C

Flashfire is auto detecting the update not sure why its failing ?

Any advice or walk-thru please ??

Also running latest TWRP
[Paid Software Announcement and Discussion] Ch3vr0n:
Step one: read posts above. as posted multiple times above you need magisk 14.2 or below. Anything higher does not work

Step two: flash magisk 14.2

Step three: done

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] Markeee:
Step Four Thanks :)

Can someone point me to a copy of magisk 14.2 ?
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
Third link :) https://www.google.com/search?q=magisk+14.2+zip&oq=magisk+14.2+zip&aqs=chrome..69i57&sourceid=chrome&ie=UTF-8. Enjoy and Happy New Year!
[Paid Software Announcement and Discussion] Markeee:
Sorry I'm not seeing it under the third link :(
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
Just Google for

magisk 14.2 zip
[Paid Software Announcement and Discussion] Markeee:
I been searching magisk 14.2 not one link comes up with it just 15.2

to old
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
Dude. If you search for exactly what I put, the third link "Download Magisk v14.2 (Magisk Manager v5.3.5) - STechGuide", has exactly what you want.
[Paid Software Announcement and Discussion] Markeee:
Got it
[Paid Software Announcement and Discussion] bibikalka:
After updating build.prop to have consistent armeabi-v7a Flashfire 0.73 crashes just like before when it was claiming arm64-v8a. Strangely enough, there is a "/system/lib64" folder present, while device properties don't have arm64 listed in the right place!

The biggest inconvenience with v0.24 is that it did not support Lollipop unpacking commands, such as

block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

Therefore, OTAs using vendor update files are out of question.

[MENTION=631273]Chainfire[/MENTION] - It'd be awesome to get a modified v0.73 which would use the v0.24 method to transition into the Flashfire mode. ;) But who knows how laborious this is, and if there is time to do so ...
[Paid Software Announcement and Discussion] Ch3vr0n:
Why are you quoting me? I didn't post that link

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] Ibuprophen:
This looks like a job for "Super-Moderator" like [MENTION=631273]Chainfire[/MENTION] or even [MENTION=1205214]SacredDeviL666[/MENTION]!!! LOL :)

I knew that this verbiage looked familiar and found 3 duplicate threads from amberg467p and this post all with the same information...

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Paid Software Announcement and Discussion] seto9770:
Hi guys, I have some problem with FlashFire.

I start backups fastboot and normal backups and it freezes on scaning data and i cant do anything ( reset, power of ).

Life it own life XD :D
[Paid Software Announcement and Discussion] bibikalka:
I kept working with Flashfire, and there is one key diagnostics. In v0.24, I see this in "lastlog":

[init.svc.zygote]: [stopped]

In v0.26, I get this now:

[init.svc.zygote]: [running]

I've attempted to re-pack v0.26 apk with libflashfire.so from v0.24 - this did not work. For testing, I repacked v0.24 with libflashfire.so from v0.26, this one also stops working. So, whatever the method to kill all processes in v0.24 was - that's the only one that works here.

Anyway, porting v0.24 stopping method into the new version is the quickest fix, perhaps adding this as an option?

There was a similar situation a while ago, and below is a response from Chainfire.
[Paid Software Announcement and Discussion] shadin:
Hi There!

I get blank screen with header without progress bars. Backup and other processes has working.

What's wrong for me?

Thank You!

:confused:
[Paid Software Announcement and Discussion] ktmom:
What device, ROM and root version?

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Paid Software Announcement and Discussion] shadin:
Hi!

Samsung Galaxy S7 G930F stock BTU G930FXXU1DQJ3 ROM and rooted with CF-Auto-Root by Chainfire.

Properly worked with an earlier version of FlashFire.

THX!
[Paid Software Announcement and Discussion] baxxter106:
Hi, i'm new with flashfire App - and sorry If this question have been asked before:

I have a (magisk)rooted Nexus6P with twrp and try to install the latest OTA January/2018 from Google.

When the app goes down with the phone it turns black - and stays black...1min - 10min - i have to turn it on by myself but then nothing changed.

What goes wrong? Do i something missing? Whats the right way?

Thanks, baxx
[Paid Software Announcement and Discussion] ktmom:
Known issue. Start at post 6280

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Paid Software Announcement and Discussion] Kartlis:
8.1.0

Hi,

FF fail to encrypt Jan 2018 OTA on nexus 5x,

HNY!
[Paid Software Announcement and Discussion] Ch3vr0n:
FF doesn't encrypt anything. How about you provide the 'lastlog' from flashfire.

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] Kartlis:
Hi,

FF fail to Uncrypt Jan 2018 OTA on nexus 5x...

Uncrypting OTA failed!

I finally flash full OTA and it's work...

Thx for fast and constructive answer!
[Paid Software Announcement and Discussion] winnph:
So I have a Pixel XL and used FlashFire to install the 8.1 update in December (though I flashed the relevant partitions from the full factory images, not the OTA). I only just now noticed, however, that SuperSU is no longer installed, even though all the apps that had already been granted root appear to still have root (AdAway is working fine, FlashFire itself throws no errors when checking for root, etc.).

Can I safely use FlashFire to install the January update, too, or am I about to brick my phone? What should I do to get a functioning root solution on this phone instead?
[Paid Software Announcement and Discussion] ktmom:
First go back and pull the supersu apk from the zip file you used. It's in the common folder. Then install it and see if that fixes your problem.

Once you've done that, you'll probably feel better about flashing the new update [emoji6]

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
SuperSU (even 2.82 SR5) doesn't work with Android 8.1. That's why it's not installed. You have to use Magisk v14.2 (not a higher version) in order to be both rooted and to use FlashFire. I use FlashFire the same way to flash the entire image.
[Paid Software Announcement and Discussion] winnph:
Ah, so it's interesting that AdAway and FlashFire both still claim to have root, then. I wonder what's going on.
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
Interesting. I will clarify that a bunch of people, including myself, have had the experience that SuperSU v2.82 SR5 won't successfully install once you've got 8.1, but there's always a possibility of some weird exception.
[Paid Software Announcement and Discussion] vMAC:
So to be clear I can not use FF, even to just do a backup, if I am on Magisk 15.2? I would have to go back to 14.2 or wait until there is a future update of FlashFire to even use FF for backups?

Sorry to quote you but most of the posts I found while searching were answered by you in this regard.
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
If you are also on Android 8.1 on the Pixel, then yes, as far as I know and has been my and others' experience, correct. I haven't used FlashFire's backup and restore, however - I only know that trying to flash firmware and zips definitely doesn't work with Magisk 14.5 or 15.0, and I assume (and from other people's reports) 15.1 and 15.2. I have no idea if using other versions of Magisk under other versions of Android or on non-Pixel devices still allows FlashFire to work. I didn't use Magisk at all until I upgraded to 8.1, since SuperSU doesn't work with 8.1, at least on the Pixel.

No sweat!
[Paid Software Announcement and Discussion] winnph:
FYI, I went ahead and tried to flash the updated (Jan) marlin factory images using FlashFire since it claimed it still had root, but the usual black screen stayed that way indefinitely, never loading FlashFire's flashing dialog. So clearly there's something not working right even though the app believes it has root.

So, I manually flashed using fastboot, which went smoothly. SuperSU still will not install, but AdAway still has root and successfully merged/applied the hosts file. Since AdAway is the only app I use regularly that requires root, I guess I won't worry about sorting out the SuperSU situation or switching to Magisk.

Edit: Interestingly, when I try to install SuperSU using the apk, it treats it as an *update* in the install dialog, so I decided to check the list of installed apps in settings, and whaddya know, SuperSU, SuperSU Pro, and suhide are all still listed there. None of their icons appear in the normal apps list (swiping up from home screen), but I guess they are still somehow semi-functional.
[Paid Software Announcement and Discussion] biustech:
hey guys, i tried to search on this thread but didn't find a final answer.

i have a samsung S8 fw AQK7. i 'm rooted (SuperSU) and have twrp installed. does anyone tried to upgrade via flashfire? i used to have a s7 edge and i used FF a couple of times and it worked perfectly. does it still work on S8?

cheers
[Paid Software Announcement and Discussion] Pttigui:
Hi everyone, I've an issue with flashfire for which I didn't find any info browing on the oracle and various forums.

Basically, flashfire does not work :( The app opens but whenever I ask to backup or install a new ROM I just have a blackscreen, the phone restarts and ... it did nothing.

Did any one of you already faced that and if yes, did you found a patch ?

Thanks in advance for your help :)

Guillaume
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
If anyone is to help, more information is needed. Exactly what model phone? What version of SuperSU or Magisk are you on? The logfile might be helpful.
[Paid Software Announcement and Discussion] Pttigui:
Hi Roirra, thanks for the answer. The device is a A520F with TWRP as recovery and rooted with Magisk 15.3. How can I provide you the log ?

Thanks for the help, Guillaume
[Paid Software Announcement and Discussion] roirraW "edor" ehT:
You're welcome. Check [MENTION=631273]Chainfire[/MENTION] 's FlashFire website for instructions on getting its log. I'm just guessing but the culprit is probably Magisk v15.3. I only have experience with Magisk on my Google Pixel, but at least on Android 8.1, Magisk v14.2 is currently the highest version that works with FlashFire - I don't know about other versions of Android or on other phones. You might be able to downgrade your Magisk to get it working, but don't quote me on that.

Just to be clear, I won't be looking at your log, but someone who's actually knowledgeable about these things might look. :)
[Paid Software Announcement and Discussion] Pttigui:
Hello,

I tried with Super SU but it doesn't change anything, Flashfire still doesn't work.

I feel that I'll have to backup and do all the procedure inc. wipe to be able to update :(