yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] phorgan1:
not using magisk

I'm on a 6p and don't have magisk installed. Just like a lot of others on 6p. The common denominator for us is that we're on the beta program from google.
[Paid Software Announcement and Discussion] g0d0fmischief:
Chainfire has just said above your post that it isn't magisk, the beta thing seems to be the 6p users, but could be coincidence that modders here run the beta. Lots of us 5x people aren't on the beta.

Edit when did the beta release, he states he encountered the issue last month before vacation. Could be before the beta even?
[Paid Software Announcement and Discussion] mikeezy187:
I just have a quick question probly a noob question but if I I make a back up with flashfire and things go wrong without a custom recovery which recovers ef up if I have an ef up without a custom recovery how do I recover that flash fire back up I no I could use a cpu but that's alot of uneciceary hassle cahinfire is a legend could there not be some sort of custom recovery with flash fire the app has dam near everything just think some sort of boot recover would be a nice addition I no its in chainfires caperbilitys
[Paid Software Announcement and Discussion] g0d0fmischief:
Can't you now make a backup that you can restore via fastboot. Check the recent version release notes and the flashfire site. I'm pretty sure you can
[Paid Software Announcement and Discussion] mikeezy187:
Im using a galaxy s7 I had a sony z3 before and I could never get my head around adb
[Paid Software Announcement and Discussion] NPOA556:
I have a 6P and have never subscribed to the betas. I am running stock 7.1.1 with SuperSU 2.79-SR3 and the latest version of Flashfire from the Play store. When I tried to use FF to install the Feb security patch that was automatically downloaded to my phone, it failed during the unencrypting OTA step. Many times. I'm really glad to see that Chainefire is aware of the problem now.
[Paid Software Announcement and Discussion] Ch3vr0n:
If you're running SR3 then you ARE running a 'beta'. As posted months ago, the SR (service release) is the new name instead of the 'beta' scheme. So yeah, you HAVE subscribed to the beta's.

Sent from my Nexus 7 (2013) with Tapatalk
[Paid Software Announcement and Discussion] MultiKoopa:
I've had one problem or another every single time I've tried to do the plain old OTA update through FlashFire for the last several months. I think I only even got it working the first (and maybe second) time I ever tried it.

Using the OTA image from Google seems to work though. But of course that thing's gigantic to download each time lol
[Paid Software Announcement and Discussion] skiely666:
In settings what do I set my system as if say I'm rooted or I'm using adaway? Nexus 6P stock..

Treat system as original NEVER?
[Paid Software Announcement and Discussion] Ibuprophen:
Just an FYI...

Chainfire just posted an SR4 and provided some information about what it addresses.

https://xdaforums.com/showpost.php?p=71561057&postcount=9345

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[Paid Software Announcement and Discussion] jcmm11:
Assuming you're running AdAway in systemless mode, and you're running a systemless root, neither of these will actually change system (that's why they're called systemless).

If you don't make any changes to system, at all, then you SHOULD treat system as original.

In my case I'm running a custom ROM, I mess with /system all the time, and OTAs are non-existent for me so I treat system as original NEVER.
[Paid Software Announcement and Discussion] adarshadhungel1:
Can a full tar.md5 file of samsung be flashed with this

I mean a whole rom file
[Paid Software Announcement and Discussion] pvchip3:
First of all I want to thank you for Flashfire and your many other apps and contributions you make to android. All your hard work is very much appreciated.

I'm having a few issues with flashfire. I have a Samsung s4 active 1537 the att version and it won't make a backup of my current rom. When i hit flash it looks like it start to make it but then reboots and hangs on the Samsung screen forever. I'm also trying to upgrade to android 5.0.1 from a clean odin of 4.1.2. When i hit flash it looks like it starts to flash then reboots and hangs on the att screen for hours. I can reboot from there and it reboots normal as if nothing happened. Anyone have any ideas? Thanks in advance.
[Paid Software Announcement and Discussion] azim007:
bootloop after using flashfire

after using flashfire i got an ota update ..am a leeco x509 user. after download update when i run flash my phone stuck in boot loop, screen on off continuously ... cant switch off or cant go to twrp mode ..what i do plz plz plz help me some1.. i know this is ryt place ..xoooo
[Paid Software Announcement and Discussion] JoshwaDroid:
Try googling "SP flasher" and the variant of your phone and you will find tutorials for this, youre softbricked, so not a big deal, but READ the exact TUTORIAL and be completely sure that the firmware you find is for your exact device, or you could HARDBRICK your device, best of Luck. Hope that Helps And you can learn a little bit more of your device, ; )
[Paid Software Announcement and Discussion] NoMoneyNoLife:
I tried to install magisk installer with flashfire but it doesnt work . I tried others zip files too but end up get the same result . I am running marshmallow 6.0.1 on samsung galaxy s6 edge . Any solution ?
[Paid Software Announcement and Discussion] dahawthorne:
You could try Magisk Manager )Play Store), which will prompt you to install the latest version and keep Magisk updated.

You may have more luck with TWRP flashing, unless you particularly want to use FlashFire. I have FlashFire Pro, and on at least one occasion I had to try a flash twice before it worked.
[Paid Software Announcement and Discussion] forsythejones0:
FlashFire not recognizing

I've updated my Nexus 6P to Android O preview and I had backed up my Nougat with FlashFire (in case I wanted to go back or something went wrong). Anyway, I install FlashFire on my device and I put the backup in /FlashFire/Backups, but FlashFire says that there are no backups. Newest SuperSU to date.
[Paid Software Announcement and Discussion] cwis:
Any s7 Edge (Nougat) debloat fixes for ATT?
[Paid Software Announcement and Discussion] Ch3vr0n:
What does that have to do with FlashFire? Ask in your device forum.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Paid Software Announcement and Discussion] cwis:
Flashfire is how I flash zips. Ergo, the reason why I'm asking in the FLASHFIRE forum. Doesnt take a rocket scientist to figure it out. :confused:
[Paid Software Announcement and Discussion] Ibuprophen:
- - - DELETED - - -

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[Paid Software Announcement and Discussion] Ch3vr0n:
It may be how you flash them yes, but flashfire does NOT do any 'debloat' fixes itself. Meaning it's not a flashfire issue and you need to ask for those type of fixes in your device forum.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------

That site offers an unauthorized download of SEVERELY OUTDATED apk's and chainfire has attempted to shut that site down for copyright violations. I think the 'latest' version it offers is 0.24 or something.

If you want to get an up to date manual/guide use the official site ONLY @ https://flashfire.chainfire.eu/

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Paid Software Announcement and Discussion] Ibuprophen:
I was unaware of that and will be removing the post.

I never downloaded anything myself and get any downloads from the legitimate places but, there's always someone who will...

I apologize and posted it PURELY in good faith!

EDIT: [MENTION=1754043]Ch3vr0n[/MENTION], you had quoted my deleted post. Can you please edit your post and just remove the quoted information from the, now, deleted post to prevent anyone from reading and going to the link?

Thanks a Bunch!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[Paid Software Announcement and Discussion] StupidIdea:
[MENTION=631273]Chainfire[/MENTION] I saw you were able to reproduce it but just in case you need any additional information I have pending 7.1.2 OTA (enrolled for beta) on Nexus 6P and Flashfire fc right at the beginning while trying to unencrypt. Let me know if you need logs or want me to test some beta.
[Paid Software Announcement and Discussion] Chainfire:
Reproduce is a big word - while I've seen the issue occur a few times, I cannot reproduce it at will, which makes debugging it very difficult. For example, I just did 4 monthly updates in a row on my 6P without any issue.

The contents of /cache/recovery may help me diagnose.
[Paid Software Announcement and Discussion] StupidIdea:
Here you go. I had this issue with previous update too so I flashed last one manually. This time I have pending update for a few weeks already so I can say the issue is consistent. I don't rush to update so take your time and let me know if you need anything else. I'm developing myself sometimes so I can debug/script/adb/anything if needed.

Edit: attached fc log too.
[Paid Software Announcement and Discussion] KaMyKaSii:
[MENTION=631273]Chainfire[/MENTION], as I did not receive your reply, I will repost.

I looked in all my logs after black screen and reboot and other people who posted logs here with the same problem and everyone has the following error:

c: echo flashfire > /sys/power/wake_lock: No such file or directory

I checked with file manager and the file exists. It appears just after getprop lines. Maybe you did not notice that?

Although the ">" (overwrite), The command is working as ">>" (append), Is that right?
[Paid Software Announcement and Discussion] Chainfire:
I found a possible issue going through the code again, I sent you a link to a test version through PM.

Let me know if that one works for you.
[Paid Software Announcement and Discussion] Chainfire:
This is normal behavior since 5.0 or so.
[Paid Software Announcement and Discussion] StupidIdea:
First it showed a pop up "OTA update failed". After that the app deleted the OTA so I had to re-download it.

I started the app the second time and the decryption passed and it rebooted to your custom bootloader. It restored bootloader and recovery. And then showed "Flashing update.zip" (or something similar) for a really short time (~1sec). After that it rebooted to broken robot page with "No command" message. It had 3 circles on the bottom (2 filled, 1 empty) if that means anything. It keeps rebooting to the same screen about every 10sec but I can boot to stock bootloader/recovery so it's all fine.

Let me know if you want me to get something with TWRP now. If not then I can fastboot flash 7.1.1 and try it again.
[Paid Software Announcement and Discussion] Chainfire:
Can you grab /sdcard/FlashFire/lastlog ?
[Paid Software Announcement and Discussion] KaMyKaSii:
I had already posted a continuous logcat where I tried to back up by adb (to keep adb active and to be able to capture the log). Could you take a look at it? As it is at the end of the log, the SurfaceFlinger service has died, I hope you can find the solution. Thank you

https://drive.google.com/file/d/0B1uvONk-jlRiU3AyLWVncEdab1E/view?usp=drivesdk
[Paid Software Announcement and Discussion] StupidIdea:
Attached. Renamed to .txt so I can attach uncompressed.

Edit: I'm still on TWRP. /system is empty.
[Paid Software Announcement and Discussion] g0d0fmischief:
I'm one of the one who absolutely can't get it to work without crashing during uncrypting if there's any info I can give you to help I will
[Paid Software Announcement and Discussion] StupidIdea:
[MENTION=631273]Chainfire[/MENTION]

1) Flashed again 7.1.1 and CFAutoRoot

2) At first FlashFire didn't see the OTA so I started system update, that restarted the phone and failed to update (obviously). Then FlashFire showed OTA too

3) FlashFire showed red error that updater.zip.uncoded (or something like that) is not ZIP file, patcher bootloader, injected root and phone booted again to 7.1.1.

4) OTA was gone so I redownloaded it.

5) Started update with FlashFire and the result was the same as the previous time (no ZIP error this time): short message about flashing update.zip and phone rebooted to No command.

I'm flashing 7.1.1 back so I should be at step 2.
[Paid Software Announcement and Discussion] Chainfire:
So things are getting a bit tricky.

- It seems I have solved the uncryption problem itself.

- However, the latest OTAs are doing a multi-stage update that isn't (yet) compatible with FlashFire. I'm trying to figure out how this works exactly, this might be tricky to actually fix. This is what causes the reboot and getting stuck in recovery (reflashing a working boot image should let you boot again).

- The red error of the update not being a ZIP file is normal if uncrypted updates fail. This is due to a left-over mapping file that is now pointing to incorrect data, which results in garbage rather than the update ZIP we want to flash.

- After failed attempts, wipe cache and re-download the OTA.
[Paid Software Announcement and Discussion] StupidIdea:
Thank you. It was fun while it lasted :). PM or mention me if you want me to test something (I will keep 7.1.1 for now) but I understand you can reproduce it with 7.1.2 ota.
[Paid Software Announcement and Discussion] Ch3vr0n:
We all have faith you'll fix things. The weird thing though [MENTION=631273]Chainfire[/MENTION] if you manually download the incremental (or full) OTA (from the Google servers directly via browser) it goes through the what you call 'multi stage' process absolutely fine. And that's exactly what I've been doing since I first reported me having that uncrypting error.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Paid Software Announcement and Discussion] Chainfire:
The full OTAs aren't multi-stage as far as I know. At least the latest 5X and 6P full OTA's aren't - I just downloaded them to check.
[Paid Software Announcement and Discussion] Ch3vr0n:
I only flashed a full one once Sunday far, cause the Feb OTA was stuck in a download loop

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Paid Software Announcement and Discussion] Chainfire:
[MENTION=6450691]KaMyKaSii[/MENTION] do you still have those devices without names in /dev/block/... ?

Does this device have /proc/dumchar_info and if so, what are the contents?
[Paid Software Announcement and Discussion] Sczar:
[MENTION=631273]Chainfire[/MENTION]

Similar problem with my device. N900v

In LP works fine but when I flashed MM. Flashfire seems to be not working.

c: echo flashfire > /sys/power/wake_lock: No such file or directory

If I attend to flash recovery or simple as wiping anything. The screen will go off then the device will reboot normally. Nothing been done.

Thanks in advance
[Paid Software Announcement and Discussion] Chainfire:
I see and understand. After some further reading, it appears common for boot partition to not even have a numbered partition. This makes it hard for FlashFire to deal with - it is not designed to write index into the parent block device, which would be required in this case.
[Paid Software Announcement and Discussion] KaMyKaSii:
Well, in the case of my friend's cell phone, the only numbered partitions are those with ext4 file system. Then system, cache, data. Although the recovery partition is not numbered, it is present in dev/recovery so you can make changes to it without resorting to modifying the whole device block (/dev/block/mmcblk0). Although the boot partition (/dev/bootimg) is also present, it can not be backed up. This in Android booted (trying to copy the "file" or by FlashFire). TWRP works perfectly. Below is the TWRP fstab of my friend's device.

These "emmc@..." I think are symlinks pointing to the respective partition. Also below is some links in the Magisk topic where I tell how changes to the partition of these devices without the numbered boot partition can be made .

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post68909842

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post68910624

And about the logcat of my device, you had already explained to me about the SurfaceFlinger service activate the bootanimation on the screen to keep all the pixels alive and considering that he died before the mobile reboot, does not that mean he is the problem?
[Paid Software Announcement and Discussion] Chainfire:
Have you had a chance to test the last version I sent you in PM ?
[Paid Software Announcement and Discussion] Chainfire:
Yes, I understand fully how this works. Apparently, TWRP has code to cope with this, but FlashFire wasn't built for it. It does support reading this sort of partition, but not writing. The code changes required to support this are too large (and risky) to perform without a test-device in-hand, though.

Not necessarily. It might, but it is very difficult to tell.
[Paid Software Announcement and Discussion] Chainfire:
RE: Android O

I did some playing with Android O, but they changed some important things in SurfaceFlinger. I'm probably going to have to wait for the O sources before I can fix compatibility.
[Paid Software Announcement and Discussion] Pridexx:
Brightness & framebuffer emulation

Big thanks to you for this powerful app. Overall is worked very well, but i have couple issues related to AROMA.

My phone, Meizu M1 Note do not have custom recovery or unlocked boot so i use combination of Flashfire and AROMA installer to make modification in system via installer with gui.

In framebuffer emulation mode i have very dark screen - its like brightness is set to 20%. The touchscreen is worked, but with phantom presses. I can live with that, but maybe you could able to help me solve this issues.

Link to lastlog
[Paid Software Announcement and Discussion] Chainfire:
v0.57 released - https://plus.google.com/+Chainfire/posts/KoE1fuTqFb3
[Paid Software Announcement and Discussion] GRSteelers:
Alright, so I've just attempted an OTA using the latest (0.57) version on my Pixel.

I've never installed TWRP, so the backup of the boot partition was unchanged.

I had selected the inject SuperSU option for EverRoot, but after the update completed (I believe it failed but did not notice a failed message, possible I missed it), I had no root.

So, I attempted to reroot with your CF-auto boot-to-root image, but did not flash SuperSU, and I was in a bootloop. Resolved the loop by booting a TWRP image and flashing the latest SuperSU beta. The boot-to-root causes a boot loop, just flash the SuperSU instead.

FlashFire log: https://pastebin.com/aCEVUpjW

Bootloop (after boot-to-root, pre-SuperSU reflash) log: https://paste.ee/p/rrDRk (larger than 1MB, could probably cut down considering it's a loop but pasteee was easier)

TL;DR -- Attempted OTA, phone was unrooted instead.

Thanks

Edit: So I may have enabled auto-detect for the "Treat system as original" at an earlier date, so I thought that could have had something to do with the unrooting.

After reattempting, it again unrooted my phone and didn't install the OTA. Bootloop definitely caused by old boot-to-root image.

Second flashfire log: https://pastebin.com/mWEcY7cm
[Paid Software Announcement and Discussion] Chainfire:
boot-to-root is really old, it was made because there was no TWRP yet for the Pixel.

Re: your flash, the OTA complains your /system was modified somehow.

SuperSU flash fails with a permission denied error, which is really strange. I'll try to reproduce that.
[Paid Software Announcement and Discussion] GRSteelers:
The boot log with the permission failure is from the boot-to-root, pre-SuperSU flashing.

I'm most confused about the unroot instead of just failing the OTA, what's with that?
[Paid Software Announcement and Discussion] Chainfire:
They both contain the permission error, hence the patched boot image is never written.

The OTA first overwrites the boot image, and only then it fails on patching system. So your boot image is back to stock before SuperSU installs, and SuperSU in turn fails to install. Hence, root is lost.
[Paid Software Announcement and Discussion] corkiejp:
What version of SuperSU has EverRoot got now? The release info or google play doesn't say!

Never mind prior version updated to 2.79 SR3
[Paid Software Announcement and Discussion] Ibuprophen:
The latest Stable version of SuperSU is v2.79 (which is what is in the Play Store). If you have questions regarding the SuperSU v2.79 Stable, please post them on the following thread:

http://xdaforums.com/showthread.php?t=3452703

The SuperSU v2.79 SR3 is a Service Release (aka Beta Release). Not a Stable Release. If you have any questions regarding the SuperSU v2.79 SR3, then please post them on the following thread:

http://xdaforums.com/showthread.php?t=2868133

This thread is dedicated specifically to the FlashFire.

The thread links above are dedicated specifically to those SuperSU Releases.

Thank You for your Understanding.

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] GRSteelers:
Ah, I see.

I just installed the latest official full OTA, and then installed the incremental one and all is well.

Thanks for the quick and helpful replies by the way, I appreciate it and I'm sure everyone else does.
[Paid Software Announcement and Discussion] corkiejp:
[MENTION=648656]Ibuprofen[/MENTION] Well aware of the SuperSU threads. I was asking which version FlashFire was using with it's in built EverRoot!

But I also edited my post that I found the info in the last release change logs.
[Paid Software Announcement and Discussion] Chainfire:
EverRoot worked this time around ?
[Paid Software Announcement and Discussion] grävling:
Still not uncrypting NVIDIA OTA

Installed flashfire 0.57 (April 3 2017). Uncrypt of the 7.1 OTA failed (only message, 'uncrypt OTA failed'). Nvidia Shield K1 tablet, rooted, running 7.0

Let me know if you want me to send you anything, or if I can do anything to help.
[Paid Software Announcement and Discussion] GRSteelers:
Yep, no hiccups.

https://pastebin.com/KHS7UHne
[Paid Software Announcement and Discussion] FlyOnTheWall43:
So I may have screwed myself over, but I'm hoping someone here might be able to help me out.... I tried to use FlashFire to flash 7.1.2 (N2G47H) on top of 7.1.1 (N4F26T) on my Nexus 6P, but now I'm getting 'Wrong PIN' errors and I KNOW I'm tying it in correctly. I've tried rebooting a few times and wiping cache/dalvik cache and I can't seem to get my PIN to work. Do I have any options or do I need to factory reset? Let me know if there's any other info I need to provide to help debug.

Thanks in advance for any help.
[Paid Software Announcement and Discussion] TCattd:
Pixel XL, April OTA, FlashFire (latest 0.57) detected the OTA and did his thing, but hit the same error as before ( https://xdaforums.com/showpost.php?p=71325892&postcount=5243 ): ErrorCode: kDownloadStateInitializationError, [MENTION=631273]Chainfire[/MENTION]

After rebooting, the phone got stuck booting into TWRP. Have to download the OTA from https://developers.google.com/android/ota (from a computer) to flash it from within TWRP (beside TWRP zip and SuperSU zip) to recover the phone from the loop.

Latest log attached.