yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] KaMyKaSii:
Okay, now I do not know what's going on. I did 5 more tests today, and none went into FlashMode. From yesterday to today I can not think of anything I could have done to break the app again. Here is some information:

1. After test 5, I lost root access. But it was restored after the next reboot.

2. Before doing test 7, I cleaned dalvik-cache. Same result.

3. Before testing 8, I cleaned up FlashFire data. Same result.

Logs:

https://drive.google.com/folderview?id=0B1uvONk-jlRianJIbEhibXRXWE0

And at least on my device, the app crashes when trying to add a Wipe action (right after clicking the button)

java.lang.NullPointerException: Attempt to invoke virtual method 'int eu.chainfire.flash.partition.BootControl$Slot.getIndex()' on a null object reference
at eu.chainfire.flash.partition.PartitionManager.findFirst(PartitionManager.java:900)
at eu.chainfire.flash.ui.list.action.ActionWipeHandler.edit(ActionWipeHandler.java:140)
at eu.chainfire.flash.ui.list.action.ActionWipeHandler.add(ActionWipeHandler.java:95)
at eu.chainfire.flash.ui.list.action.ActionDisplayManager.addWipe(ActionDisplayManager.java:375)
at eu.chainfire.flash.ui.fragment.ActionDisplayFragment$5.onClick(ActionDisplayFragment.java:90)
at android.view.View.performClick(View.java:5265)
at android.view.View$PerformClick.run(View.java:21534)
at android.os.Handler.handleCallback(Handler.java:815)
at android.os.Handler.dispatchMessage(Handler.java:104)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5728)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:102)

I do not have a Pixel, but in case you really need flash TWRP, I think the recommended are following actions in FlashFire:

1. Install stock boot.img (and other partitions if you have modified them).

2. Apply OTA update.

3. Backup updated boot (and other partitions as system).

4. Install SuperSU.

5. Install TWRP.

When the next OTA is released, do the following:

6. Restore the updated boot (and perhaps other partitions).

7. Repeat from step 2 onwards.
[Paid Software Announcement and Discussion] Chainfire:
Non-stock boot image, exactly as warned about.
[Paid Software Announcement and Discussion] Chainfire:
That doesn't work either. Right now I'd stick to fastboot boot'ing TWRP only, and installing SuperSU from there, without flashing the TWRP ZIP at all.
[Paid Software Announcement and Discussion] Chainfire:
Very strange. Are you sure you are still on v0.54-PRE ? :) Have you tried without Xposed?

I'll fix this.
[Paid Software Announcement and Discussion] Majesty00:
Oooh! Thanks for your answer! Magisk 10.2 was the culprit, I guess. I've installed it yesterday and totally forgot about it... Sorry about asking what my trouble was.

I've downloaded the OTA (sailfish-ota-nmf26u-6ea22a0c.zip) and it worked with FlashFire.
[Paid Software Announcement and Discussion] phishfi:
Ok, I didn't realize the risk and scope of TWRP on a Pixel until you said this... Kinda sucks that it modified the Boot partition just to work.

So, to go back to not using TWRP permanently, should I just fastboot flash a stock boot partition, then install SuperSU and my kernel of choice (I can't help but use Franco's Kernel), then use FlashFire for any future updates?

Thanks for your help and hard work!
[Paid Software Announcement and Discussion] kpoverdorf:
Alright, I really hate to be this person... But I feel the more I read the more concerned and confused I get.

I have a Stock Rooted Nexus 6P running "Pixelize" (if that matters). I was looking to install the January OTA but since my phone is now seen as a Pixel XL I didn't receive the OTA. So I downloaded it from Google. When I go to flash the update, I choose "Flash ZIP or OTA" and the update does not appear. When I choose "Flash firmware package" it appears. Is there a difference between those options?

I don't want to wing it and regret it later.

I am also reading that after flashing using Flashfire I will need to reinstall TWRP Recovery and SuperSU. Just want to verify before I do anything.

I swear I read a good bit of the thread, but unfortunately I just got a tad confused due to all the different conversations and versions updates. :confused:
[Paid Software Announcement and Discussion] waleed794:
S7 edge user here, is it possible to update from marshmallow to nougat via flashfire, I don't have a pc to use Odin :(
[Paid Software Announcement and Discussion] Chainfire:
Are you sure you downloaded the 'Full OTA' and not the 'Factory Image' ?

On the 6P, if the "Reboot/Preserve Recovery" option is enabled as well as the "EverRoot/Inject SuperSU" option, TWRP will be preserved and the firmware will be rooted for you during flash, without further needed actions.

If you follow the in-app instructions very carefully, yes. But I think it is dangerous if you do not have a PC to fix your phone in case of problems.

EDIT: Forget that, you actually do need Odin to update the bootloaders, or your device will not boot.
[Paid Software Announcement and Discussion] kpoverdorf:
Thank you for your quick reply.

That's a great question... I was being a Mr. Rushy Pants and used the Factory page, not the OTA page. Thank you for setting me straight.

I will follow your instructions and see what I end up with. Thank you again!

UPDATE: Worked perfectly! Thank you!
[Paid Software Announcement and Discussion] waleed794:
AFAIK, upgrading to nougat from MM involves flashing new bootloader and modem, I know flashfire is capable of updating bootloader but I want to know if someone had any problems doing that.
[Paid Software Announcement and Discussion] KaMyKaSii:
Chainfire updated his post. Read it again
[Paid Software Announcement and Discussion] fone_fanatic:
OTI'm attempting to flash the Full OTA now and got OTA Result != 0

I left "restore stock boot and recovery" checked, was I supposed to uncheck it?

Waiting for the 5m reboot now.

Ok, so update OTA failed (still on NMF26O), but SuperSU updated from 2.79 to 2.79-SR2.

Going to try again but this time unchecking "restore boot and recovery images".

Edit: Same thing.

Installing [/data/media/0/sailfish-ota-nmf26v-1988a458.zip]

OTA RESULT != 0

EverRoot: Installing SuperSU. . .

SuperSU Installer

Boot image patcher

- Done !

Rebooting. . .

Waiting for 5m. . .

Is it because I have TWRP recovery? I'll flash back to stock recovery and try again.
[Paid Software Announcement and Discussion] rohitece06:
Same here
[Paid Software Announcement and Discussion] belloni:
Same result for me, but I had no TWRP installed just franco kernel...
[Paid Software Announcement and Discussion] fone_fanatic:
2nd update.

I reflashed all stock images via fastboot (I did NMF26O so I can test FlashFire), verified stock recovery was there, temp booted into TWRP Alpha2 and flashed SuperSU. Tried again with FlashFlire and NMF26U OTA and nothing, but again it did update SuperSU.

I'm on a 32GB Pixel, unlocked bootloader, stock rom, kernel, and recovery.
[Paid Software Announcement and Discussion] :
Combining sparsechunk files

When storing a fastboot backup, the image files are split into smaller chunks (Motorola's sparsechunk format):

userdata.img_sparsechunk.0
userdata.img_sparsechunk.1
userdata.img_sparsechunk.2

For combining these files into one image file, Windows users can use SparseConverter: https://xdaforums.com/showthread.php?t=2749797

Does a similar tool exist for Mac/Linux?
[Paid Software Announcement and Discussion] grep_i:
DD should do the trick
[Paid Software Announcement and Discussion] mario_de:
Need help with restoring recovery on Verizon LG G2 (VS980)

Hey everyone, so I goofed by trying to update TWRP from 2.8.4.0 by using the "Official TWRP" app which had me update to 2.8.7.0. Well, I don't know if it's because it pointed to a version that I later found out isn't even available (I could only fin 2.8.6.0) or the fact that my bootloader was locked but I do know the common denominator is that I'm a big dummy for even trying it. Anyways, I'm running AICP ROM 12.1 and I can't boot into recovery anymore as I keep getting the secure boot error. The good thing is that I am still able to boot the phone up and use it as normal.

I was told to attempt to fix this by using the FlashFire app but from looking at it, it looks to be a pretty powerful tool and I don't want to screw up my phone any more than it already is.

I do have a TWRP recovery backup with boot, efs1, efs2, radio, recovery and system backed up but I have no way of restoring the data.

I'm using Windows 10 and I'm able to see the phone via ADB but when I reboot into bootloader to attempt to restore using fastboot I keep getting a USB driver error and fastboot won't recognize my device. I've tried multiple USB drivers with no luck so I'm at a loss as to what to do next.

If anyone has any ideas on how to set up FlashFire to get my recovery mode back up and running I would really appreciate it. I am trying to avoid the nuclear option and reload stock to start from scratch.

Thank you.
[Paid Software Announcement and Discussion] maximusmullivan:
Perhaps you were selecting the wrong device in the TWRP app. It has the most recent versions
[Paid Software Announcement and Discussion] mario_de:
Nope, I'm sure I used the correct version. In fact, I had to specifically go to LG G2 and then find the Verizon variant (VS980). But the strange part is that TWRP manager on Android wants me to install TWRP 2.8.7.0 for my device but the website states the last update available was 2.8.6.0. Either way, the issue was that I tried flashing it without making sure my bootloader was unlocked. That's how I got into this predicament.
[Paid Software Announcement and Discussion] BROKEN1981:
Has anyone used this on the LG V20? Would love to know if I can take OTA's while rooted. This is my first LG. So used to Samsung.
[Paid Software Announcement and Discussion] Alxoom33:
Do you think that this new Flashfire version will work on the Pixel C? I am already updated to the January 7.1.1 version using [MENTION=5480152]followmsi[/MENTION]'s zip files. However, I am curious if there is a reason you that you think this new Flashfire version wil not work on the Pixel C. I am willing to test.
[Paid Software Announcement and Discussion] daitalos:
Very good work , Flashfire is one of the most useful tools by Chainfire... Thanks for your amazing work all these years!
[Paid Software Announcement and Discussion] KaMyKaSii:
Do you mean disable Xposed or uninstall it completely? Anyway, I'm going to test both. Just wait for the courage to go through the entire dalvik-cache rebuild.

Edit: I even got to install stock rom and make a data wipe. I installed only SuperSU v2.79 SR2 and I was sure that this time would work, but even then, same error. I do not know what else to do. Do you have any suggestion? If I add a adb backup action, it will be active and I can register a logcat until the device reboot?

Question: Trying to start an action in FlashFire soon after the system starts can cause problems or gives the same?

And I wanted to make a feature request. Below is attached screenshot of two OTAs on my device. A Block-based full OTA and then a File-based incremental OTA. None has recovery partition explicitly. The recovery update happens when "/system/bin/install-recovery.sh" script run during boot but this only happens after reboot and since I always install SuperSU, this script is not activated. Could you add the execution of this script after running OTA updates? At the moment with my kind of OTA, a recovery backup after OTA actually saves TWRP.

Can you download OTAs while rooted? If so, you can try FlashFire. But first test a common backup action before going to the more advanced and always have a way to recover the device in case of brick.
[Paid Software Announcement and Discussion] BROKEN1981:
Thanks for the advice. I'll try that.
[Paid Software Announcement and Discussion] jb220380:
Hello,

I face some issue trying to flash latest stock update (January security patch) on my Nexus 5X.

I tried to flash OTA or full factory image with FlashFire, but in both cases, same issue, the phone is just powered off...

To restart, I need to boot in bootloader and then select normal startup.

And nothing has been installed...

I use FlashFire 0.53, and my phone is rooted with SuperSU 2.79 SR1.

If someone has an idea why the process fails, feel free!

Thanks.

JB
[Paid Software Announcement and Discussion] KaMyKaSii:
Upgrade to SuperSU 2.79 SR2 and try with pre-0.54 version posted a few pages back.
[Paid Software Announcement and Discussion] jhs39:
I would just unlock the bootloader and reflash the latest recovery for your device through fastboot. You can't run a custom recovery with a locked bootloader. If you can't unlock the bootloader for some reason then you should reflash the stock recovery for your device through fastboot.
[Paid Software Announcement and Discussion] johnlgalt:
FWIW:. Used FlashFire to install 7.1.1 OTA on my Nexus 6 without a hitch.

From Nexus, with Nougat.
[Paid Software Announcement and Discussion] rybshik:
which FlashFire version?
[Paid Software Announcement and Discussion] Ch3vr0n:
I used the current stable release to update my 6p from 7.0.1 to 7.1.1. Worked just fine

Sent from my Nexus 7 (2013) with Tapatalk
[Paid Software Announcement and Discussion] johnlgalt:
0.53

From Nexus, with Nougat.
[Paid Software Announcement and Discussion] grep_i:
Flashed OTA update December 2016 for Nexus 5 with flashfire 0.54-pre without an issue.

After that tried it with sideload and with following instructions on device methods too, both seemed to work normally.

I was so brave to not make any backups.
[Paid Software Announcement and Discussion] rajesh00:
Phone dead

My phone had by-num partitions listings. So flashfire didn't detect any partitions. To counteract this, i created a symlink of the block mmcblk0p6, which i figured out to be the system partition, in the required by-name directory and renamed it "SYSTEM". Flashfire detected it and flashed the system partition flawlessly. Next i tried to flash boot.img and it is here where i messed up. I misunderstood the block mmcblk0(the whole device) to be the boot partition. Once done, flashfire wiped it out and now my phone is dead. It is detected as an unknown device in pc. Any way out there to revive it. Please help!!!
[Paid Software Announcement and Discussion] KaMyKaSii:
What is your device?
[Paid Software Announcement and Discussion] rajesh00:
my device details:

model: karbon titanium mach five

chipset: mt6582
[Paid Software Announcement and Discussion] KaMyKaSii:
You formatted mmcblk0 block device, but mmcblk0boot0 (preloader) partition is still intact. Install preloader driver, SP FlashTool and then the stock rom.

https://yadi.sk/d/gZ3gufglqxKX5

https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool

https://docs.google.com/uc?id=0B9Efx6YrHRRUVFkyeUt5X3dCanc
[Paid Software Announcement and Discussion] rajesh00:
one more mistake

i had previously tried to flash preloader with mtk usb vcom port driver thinking the preloader was wiped too, however without sucess. I hope the preloader is still intact.

If yes, can i use this:

http://www.needrom.com/download/karbonn-mach-five/

to flash my device.
[Paid Software Announcement and Discussion] KaMyKaSii:
Well then you already know what to do. If it is to do in Windows, do in 7. Windows 10 has many complications. But I think in Linux you have more chances to recover the device. And when connecting the device to the usb, in both Windows and Linux, keep the power button pressed. In my personal experience, this helps.

http://www.needrom.com/download/sp-flash-tool-v5-1612/

https://xdaforums.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
[Paid Software Announcement and Discussion] rajesh00:
i really don't know what to do.

If i need to first flash the preloader. I have tried that before too without sucess with either of these two errors popping out:

1) brom timeout error

2) da didn't send responce data to flash tool
[Paid Software Announcement and Discussion] KaMyKaSii:
Probably you do not need flash preloader again. Just load stock rom into FlashTool SP, install preloader driver correctly and try connecting until the device is recognized. Try pressing hardware keys when connecting
[Paid Software Announcement and Discussion] rajesh00:
thanks for the info. I will try that soon and post the result.
[Paid Software Announcement and Discussion] Surge1223:
Hey [MENTION=631273]Chainfire[/MENTION] is there any way to get Gapps changes to persist without editing kernel verity? If not, would you mind making the commit we could cherry pick please? Seems payload.bin needs to have certain parameters for this to work. Would you mind helping explain the issues in regard to Pixel and a-b partitions in more detail too please? We don't have the latest TWRP source either to rule out if TWRP is a culprit (I know you're technically team Omni so if you could help that along that'd be great, thanks).

I guess we're still trying to figure out issues. It'd be awesome if you could be a tad more in depth about the these please. I know this isn't usually a post that you'd make on XDA (Stack Overflow would be more appropriate), but as information so far is scarce and problems are high I'd love more in depth explanation of the issues at hand regarding Pixel.

Thanks.
[Paid Software Announcement and Discussion] BeansTown106:
[MENTION=631273]Chainfire[/MENTION] to clarify what surge is saying a little bit, currently we have verity disabled in kernel here: https://github.com/PureNexusProject...mmit/a3c22aa8d824baa8874553ca845bacb7e1b1d35f

but after flashing a rom zip and then subsequently flashing a gapps zip(how its traditionally done) upon boot the gapps are removed, however if we boot the system, then flash gapps the gapps stick. this goes for any system based mod not just gapps. this seems to either be related to verity being on in twrp but not the kernel?(a thought) or something with the new payload.bin structure for the ab partitions.

figured since you are working on flashfire and have a pretty good grasp on how things work so far maybe you could shed some insight. would really appreciate it as this is kinda killing aosp development :( because either roms have to include gapps in the rom zip :eek: which is apparently a big no no, or the user has to flash the rom, boot, reboot to recovery, wipe data, and flash gapps.
[Paid Software Announcement and Discussion] sronweb:
I have currently no laptop access and I'd like to flash BL and CP for a rom upgrade on Note 4 Int. N910F. I read that generally there is risk of brick of the device but I'd like to ask if anybody tried with it and go success. Otherwise I will test by myself sometime in the next weeks.
[Paid Software Announcement and Discussion] androodius:
Like all of Chainfire's scripts it's pure genius. I have two questions. Can I give you dollars to make the pseudo pro go away (it makes me feel like a scum bag) somewhere other than Play? I'm not seeing a purchase link in a free part of the interweb. I've all ready bought all of your apps and donated through XDA with another account. I had to give it up. But I really do feel worthless with that free loader thing. That's is a keen idea to get people to pay.

Also, I murdered a LG G3 trying to flash firmware. I kind of thought it was going to happen but it as still fun. Do you guys want the logs for that stuff like that? Before I killed it I did a full back up if the bootloaders and everything so I'm just wondering if that helps development.
[Paid Software Announcement and Discussion] Ch3vr0n:
Yes, uninstall mobile Odin pro and a purchase option will become available. And yes, with problems come logfiles required. Instructions are in the first post.

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] mario_de:
I wonder is that's why I can't get fastboot to recognize my device? Could it be because the bootloader is locked? Now I need to figure out how to unlock it. It's been almost two years and I've forgotten the process. Does it make a difference if I'm running Nougat?
[Paid Software Announcement and Discussion] Thijssie909:
Is backup and restore working as expected on the Pixel?
[Paid Software Announcement and Discussion] upNsmokeAllDay:
Flashfire doesn't see the rom zips on my s7. Any fix?
[Paid Software Announcement and Discussion] rybshik:
Are the zips on a SD card of size 64Gb or more? I had a problem when using a 64Gb card, then I changed to 32Gb and it helped
[Paid Software Announcement and Discussion] jwds1978:
I'm using a Lexar 200GB High-Performance (Class 10, UHS-I) microSDXC, which has been adopted, without issue.
[Paid Software Announcement and Discussion] rybshik:
Well, in my case the stock OS (Marshmallow) on Moto G4 Play officially supports 128GB (and more). The SD card is NOT formatted as "internal storage".

FlashFire is able to write to such larger card. So, I can see the files if I put the SD card to my PC, for example.

But afterwards, the files (written to the card by FlashFire) are not seen by the OS and by FlashFire.

Once I changed the card size to 32Gb, the problem gone.
[Paid Software Announcement and Discussion] skulldreamz:
[MENTION=631273]Chainfire[/MENTION] thanks so much for the latest beta of FlashFire (.54) I just flashed the full firmware package including all protected partitions (bootloader etc...) on my pixel xl 128gb. At the time of the flash I was on the O build with root and had TWRP rc1 installed. I flashed the new U build. Obviously it kept root but of course it installed the stock recovery which I thought would happen. From there I uninstalled SuperSU from the SuperSU app and then rebooted. Then fastboot flashed boot.img to both a/b slots. Then booted TWRP rc1 and installed the TWRP rc1 zip and then flashed 2.79 sr2 and booted to system. Then booted back to TWRP to install elemental 1.03 and everything is perfect. Thanks again my dude
[Paid Software Announcement and Discussion] bodomfan:
Will this work on Xperia z3
[Paid Software Announcement and Discussion] Ch3vr0n:
Make a nandroid, try it and find out. Or try the topic search

Sent from my Nexus 7 (2013) with Tapatalk
[Paid Software Announcement and Discussion] Ibuprophen:
I have a 64GB Sandisk Ultra and formatted it using exFAT.

Never had a problem and actually read and writes faster than using FAT.
[Paid Software Announcement and Discussion] TekWiz:
Stuck On Black Screen

My Nexus 5X has been stuck on a black screen for about 20 minutes. I am able to force reboot to get out of it, as just before I did so. What do I do? I even left it overnight once to install a firmware package but nothing happened.
[Paid Software Announcement and Discussion] paulsonmcreilly:
Much thanks to [MENTION=631273]Chainfire[/MENTION] for all the awesome tools made available (for free even!). This latest FlashFire v0.53 even works on my Acer B3-A20. Awesome!!
[Paid Software Announcement and Discussion] KaMyKaSii:
Send /sdcard/FlashFire/lastlog file. And if possible describe your setup (rom, kernel...) better
[Paid Software Announcement and Discussion] XVicarious:
On Nexus 6P Android 7.0 Flashfire 0.53. Downloaded an OTA, it is there, but Flashfire doesn't see it even if I manually go to the folder (/data/data/com.google.android.gms).
[Paid Software Announcement and Discussion] Ch3vr0n:
Old news and reported at least 4 or 5 times a few pages ago. Chainfire is aware of it. Hopefully the next update will add support, in the mean time just grab the normal incremental zip file from droidsec and it'll work just fine. It did for me.

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] bodomfan:
Can you downgrade to previous version of Android using this?
[Paid Software Announcement and Discussion] daitalos:
Thanks [MENTION=631273]Chainfire[/MENTION] for any awesome tool has made, & for all work...this tool are amazing .. Ty
[Paid Software Announcement and Discussion] jillofalltrades:
The beta sign-up link isn't working for me - getting an error saying there's nothing there.