yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] AndroidifyIt:
I ended up softbricking my G930F by using FlashFire to update to the latest 6.0.X firmware.

I uploaded the firmware from Sammobile to my external SD card (the non-Adopted Storage part) and loaded it with "Flash firmware package" in FlashFire.

Unchecked Recovery (using TWRP) (the defaults were Boot, Recovery, System, Cache, Preload) and pressed ok, then flashed.

The phone shutdown, FlashFire did it's thing on the screen and shut off after a minute or so. Then it went into a bootloop a couple of times, and ended up in TWRP Recovery.

Tried booting into system from there, with no luck, always ending in TWRP.

What went wrong?

For the record I'm using FlashFire 0.53, and was on G930FXXU1BPHJ

Build-number: MMB29K.G930FXXU1BPI2
[Paid Software Announcement and Discussion] KaMyKaSii:
Go to TWRP, catch /sdcard/FlashFire/lastlog file and send here
[Paid Software Announcement and Discussion] AndroidifyIt:
Darn, already restored from my nanodroid backup. I may try again later, and I'll keep in mind to copy the log.
[Paid Software Announcement and Discussion] KaMyKaSii:
If the backup does not include the internal memory, the file is still there
[Paid Software Announcement and Discussion] AndroidifyIt:
Hmm i don't know if it did include that.

After the restore i installed FlashFire again, so maybe this is a new log? It could also be the old one.

https://pastebin.com/4FQyA8gK
[Paid Software Announcement and Discussion] geniusrafaelus:
Hi all.

Im on an s7 edge g935fd.

6.0.1 rooted, custom recovery.

Tried using flashfire to flash an ota, it seems like it failed because the update is still available. Now when i want to retry, flashfire no longer detects the OTA.

I also have xposed installed with xtouchwiz.

Anything different that I should be doing?

Sorry if I asked something that may have been asked. Tried searching around but havent really seen anything yet.

Thank you in advance.

Update: I have attached my lastlog file from flashfire. Hope it helps.
[Paid Software Announcement and Discussion] slshults:
Trying again, this time with a screenshot in case my description isn't clear enough.

I'm having the exact same problem on my Pixel running 7.1, rooted with Mark Skippen's Toolkit (skipsoft). Using TWRP (twrp-3.0.2-0-alpha2-fastboot-sailfish.img) and SuperSU Pro v2.78-SR5.

I downloaded the full sailfish-ota-nmf26o-3e7c4b66.zip . I can see it in Solid Explorer and in ES File Explorer, and it has the same perms as other files that FlashFire can see in its own file explorer (including other .zip files), but it can't see sailfish-ota-nmf26o-3e7c4b66.zip

I've used FlashFire's own "Clear cache" function, as well as clearing the cache via Android Settings --> Apps, but it still can't see the file.

I've tried putting it in the root of the sdcard (/storage/emulated/0) and in /download (/storage/emulated/0/download) but FlashFire's own file explorer can't display it after I do: + --> "Flash Zip or OTA" --> navigate to find file.

I also tried downloading it via Settings --> About phone --> System Updates

It was downloaded to /root/data/ota_updates as update.zip, where I can see it in other file explorers but not in FlashFire's file explorer. So very weird.

This image shows the same folder in Flashfire on left, Solid Explorer on the right

[IMG="Same folder. Flashfire on left, Solid Explorer on the right"]http://i.imgur.com/xePxkPP.png[/IMG]

Has anyone who has had this same issue been able to resolve it? Or, does anyone have any ideas of what I might try to get past this block?
[Paid Software Announcement and Discussion] Vaira:
This is of no use as long as the developer doesn't care about it. It has been reported already before (also by myself), the same happens with the s6 edge.

For both devices FF is useless a long time already. It's an issue with dm-verity..

Flashing stock firmware with default settings always lead to boot loop into recovery. People have to go the 'long' way using PC Odin....
[Paid Software Announcement and Discussion] Chainfire:
FlashFire is not functional on the Pixel yet, wait for the next update.
[Paid Software Announcement and Discussion] Chainfire:
The OTA checked for stock boot/recovery, but you're rooted and have TWRP. SuperSU makes a backup of the stock boot image when rooting, and can usually use that to also restore recovery. However, that backup was somehow lost and thus boot/recovery could not be restored, and OTA flash failed.

You'd need to flash the boot and recovery from your stock firmware for the OTA to stick.
[Paid Software Announcement and Discussion] Chainfire:
Get out of my thread.
[Paid Software Announcement and Discussion] Chainfire:
Even if the S7 7.0 ZIPs were supported (which they apparently aren't) I still think you'd soft-brick your S7. If I'm not mistaken you're talking about a bootloader locked model, so the only way to have root is using the engineering boot images. If you update and re-root with SuperSU, booting will fail due to the locked bootloader. If you put back rooted engineering boot image, I also doubt it would boot with latest beta ?

This is uncharted territory, you're going to have to test it all out to be sure, but I don't think you'll get anywhere.

Did you flash the bootloaders with ODIN as the instructions in the app tell you? (Tap the Samsung card)

There are number of issues with S6 and S7 at the moment, but if you have the wrong bootloaders (and these can only be ODIN-flashed) Android will *not* boot.

/data is usually already mounted, so if something is trying to mount it again, you'll see this error, but /data will still be available. Are you sure this error is actually a problem? Where did it occur?

For the purposes of FlashFire, that should be considered a Google phone, not a Huawei.

My own brick experiences have been those Kirin-based phones.
[Paid Software Announcement and Discussion] Alxoom33:
FlashFire v.0.53 worked great on my Nexus 6 December update to Android 7.0 NPD91U.
[Paid Software Announcement and Discussion] slshults:
Aha. That would explain it. Thanks for letting me know, and thanks for all you do.
[Paid Software Announcement and Discussion] AndroidifyIt:
Ah I missed the part about the bootloader, sorry about that.

Does it make sense to try flashing again? If there's generally issues with S6&7 and FF.
[Paid Software Announcement and Discussion] goofwear:
Thank you very much for the information. You are right we do have locked bootloaders. I am not going to try this.
[Paid Software Announcement and Discussion] geniusrafaelus:
Thanks a lot, sir. I figured I am better of letting go of OTAs in the meantime. I might end up bricking my phone:)

Thank you for all that you do for the android community:)
[Paid Software Announcement and Discussion] 089man:
Can I flash with this app a twrp image or tar? If yes, what is the right way? I used at this time twrp latest xxx. 4 and will back to previous version xxx. 3 because I have freezes from time to time with twrp and image flash don't works with latest build...
[Paid Software Announcement and Discussion] udtul:
I sucessfully flashed B190 over B120 on huawei device.Both are lollipop firmwares.

When I flashed boot.img from B190 firmware I bricked device.

It ends on rescue mod and says update again.

Then I flashed all image except boot.img , it sucessfully upgrade my device.

Now I am going to test it to upgrade device to B190 lollipop to B540 mm.
[Paid Software Announcement and Discussion] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] any idea what's preventing FF from detecting the OTA downloaded by the device? If I use the URL that's in a debug report and manually download the zip file FF DOES see the file. It just refuses to see the update.zip downloaded by my 6P. I'd be happy to upload the specific update.zip file to a host of your liking.

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] alfa_newuser:
flashing full firmware updates - need support

hi guys

my mobile in Note 4 N910C , running android 6.0.1 , rooted using CF-AR , after rooting the mobile stop receiving OTA UPDATES , i am planning to upgrade to latest official full firmware via Flashfire.

i will use flash firmware package command without wiping user/system data , only cash & delivak partition will be wiped

1- will this procedure maintain user apps & data as it's (this is my target)

2- modem partition is not checked by default , should i check it ?

appreciate your support
[Paid Software Announcement and Discussion] braxas:
Hello, ive got the following Problem. I made a normal Backup using flashfire. I Backuped data and internal SD . Ive got the data.tlz4 files and the intsd.tlz4 files. But when i start flashfire it only detects the data. files not the intsd files. What should i do ? Ive got all my pictures etc in that backup
[Paid Software Announcement and Discussion] Vaira:
[MENTION=631273]Chainfire[/MENTION].

I must apologise for posting the first sentence. It wasn't my intention to insult you when posting that.

I am grateful for all your work what you are doing for the Android community. I am looking forward to your next update, being more patently next time.

What I did was inappropriate and does not help at all.

I hope you accept my apology :).

Regards,

Vaira
[Paid Software Announcement and Discussion] mintytoo:
Hi, I was wondering if anybody has had a problem with flashing Nexus 6p modem firmware via the Flashfire app.

I recently updated to the most recent (Dec) factory image (System, cache, vendor) with flashfire and things were running smoothly except reception was not good in some area. I then flash the modem only (from the Dec image). The phone reboots and was usable for a minute, then went into endless re boots.

I can still get into bootloader, and recovery but so far it still bootloop no matter what I try.

Any help?
[Paid Software Announcement and Discussion] v12xke:
Being somewhat lazy I will admit I have flashed the radio.img from FF on my 6P, but only when there was a different base band. Going from DP2 to Public Release, it did not change, so I did not flash. What does the last.log file say in the FF folder? Did the flash complete successfully... if not what was the error? Not sure your issue is related to the modem partition... most boot loops I get are solved by re-flashing the kernel I use (EX). I would start by Fastboot flashing radio.img just because it was the last thing you did. If that didn't work, I would FB flash the boot.img. You can also do this from recovery if you have TWRP installed, just make sure you select flash IMG not ZIP. Once you're back in business, you'll then need to re-root by flashing SuperSU in recovery (and then custom kernel afterwards if applicable).
[Paid Software Announcement and Discussion] PhilipPeake:
I have a problem with flashfire on my Nexus 6p.

The first symptom is that a downloaded OTA update is not noticed by flashfire.

However it works fine on my Nexus 5.

I tried to run the OTA manually, but when I navigate to the download location, it appears to be empty (which would explain why it is not noticed by flashfire when it starts up).

Fire up a terminal emulator and su, then navigate to the same location and there is the update (update.zip).

So flashfire appears to have a problem with "seeing" zip files in the download location on the Nexus 6p.

Googling around shows others having what appear to be the same problem.

Suggestions for a fix??? Or is this something thatr requires a fix to the application itself?

Philip
[Paid Software Announcement and Discussion] Ch3vr0n:
Several reported that issue. It must be something with how the zip is packaged. Grab the OTA from droidsec and it will flash just fine. That's what I did for my 6p the past couple updates. Same issue for the 5X.
[Paid Software Announcement and Discussion] Chainfire:
The ZIP file is probably 'uncrypted'. Long story short, next update will support that.

As for why they don't show, the file dialog doesn't show files that appear to be corrupt. 'uncrypted' ZIP files cannot be opened, so they are treated as corrupt, and thus invisible.
[Paid Software Announcement and Discussion] Lord_Flaya:
FF does not detect OTA on Nexus 5x rooted stock. Anyone know how to find the OTA file and flash manually in FF?
[Paid Software Announcement and Discussion] Ja_som:
Yes, it was mentioned few times here, search...
[Paid Software Announcement and Discussion] onesolo:
[MENTION=631273]Chainfire[/MENTION]

Yesterday I received the notification from the incremental OTA of Nexus 6P, from 7.1.1 Developer Preview 2 to final 7.1.1. As I am rooted, twrp and custom kernel, I have manually downloaded the incremental OTA (there's no full OTA for this case).

I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??

I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android. Nothing has changed, still on DP2.

Any ideas?
[Paid Software Announcement and Discussion] onesolo:
I just found a workaround. I uninstalled Flashfire and installed again. Then I tried to flash again the incremental OTA and it worked fine this time.
[Paid Software Announcement and Discussion] Chainfire:
Anyone here have a Pixel C running the latest 7.1.1 ?

I'm having some display issues, dmesg leads me to believe my device may actually be defective, but I would like to confirm.
[Paid Software Announcement and Discussion] Alxoom33:
I have a Pixel C. In fact, I tried to flash the latest beta OTA update and had the same problem seeing it as mentioned above for the 6p. I would be happy to test for you. I'm on NMF26H.
[Paid Software Announcement and Discussion] drewski_1:
Also have Pixel C on latest 7.1.1

Not having any display issues.
[Paid Software Announcement and Discussion] Chainfire:
Can both of you unstill my LiveBoot app? It's attached in this thread: http://xdaforums.com/android/apps-games/liveboot-t2976189

Make sure you are in landscape mode, and start the app. Scroll down, and press the test run button. If all is well, at least the first time, you should (after a few seconds) see a bunch of lines in various colors scroll over the screen. Wait until they are gone, and do test run again. Repeat this a few times.

If you keep getting screens with scrolling text, that is good. In my case, I get garbled display, and massive screen flickering. So I need to know if this is just my unit (probably hardware issue), or something every Pixel C has (probably software issue).

(The underlying display code is the same as FlashFire, but it is much easier to test this way)
[Paid Software Announcement and Discussion] ~El Julio~:
I'm having this issue with LiveBoot. Did a few tests as suggested but nothing helps.. And while booting, it only shows one static serie of lines and the whole display is basically "stroboscoping" for a few seconds..

(Came to 7.1.1 via a clean installation of the ROM using [MENTION=5480152]followmsi[/MENTION] 's TWRP flashable zips on its latest 3.0.2-23 TWRP recovery)

(Should also mention I'm using his own kernel too)

Also, one strange thing is happening : each time LiveBoot is opened after having been quited, it goes through the install process..
[Paid Software Announcement and Discussion] Schrotty35:
Can i install odin roms on my Galaxy S7?
[Paid Software Announcement and Discussion] Chainfire:
Well, at least that implies it's not my unit. I was worried about a hardware issue as dmesg (kernel log) outputs GPU failures and errors in my case. The fix for this is probably not going to be in the upcoming FlashFire update, I'm sorry to say. I've spent all day on this already yesterday, and I'm not going to delay further just for the Pixel C.
[Paid Software Announcement and Discussion] ~El Julio~:
Well, knowing it is fixable is what matters most. Pixel C's have often been a pain .. ... ... anyway.

Sorry for OT, but sometimes I also get this message in LiveBoot ( screenshot attached ).

Using SuperSU(pro) 2.79.
[Paid Software Announcement and Discussion] pkelly517:
I've also seen this image on my dragon. I've never been able to get Liveboot to work on it. Any reboot results in a lockup.

I've posted in the liveboot thread along with a log.
[Paid Software Announcement and Discussion] Schrotty35:
I will flash FIRMWARE-G930F_ZPLH.BL.tar.md5 but witch from the both is the right one?
[Paid Software Announcement and Discussion] drewski_1:
I'll give it a whirl when I get home from work today :good:
[Paid Software Announcement and Discussion] Schrotty35:
Push
[Paid Software Announcement and Discussion] Alxoom33:
I installed Live boot from the Play Store v. 1.5. The test run works fine, in various modes. However, I don't see anything but my boot image when I reeboot. Is that normal?

Edit: Tried a few more times and got the scrolling text on reeboot when I checked the saved log. Also repeated the test run a few times. I got the strobe light effect once or twice, but I also got the full scrolling text about 3/4 of the tests. I also got flashing text on the lower 1/3 of my screen a number of times. The log looked fine and was saved in cache. Worked much more consistantly on my Nexus 6.
[Paid Software Announcement and Discussion] Freekolo:
Hi,

On my HTC one M7, I have a custom 6.0.1 crdroid rom.

On several occasions and I do not know why, recent notifications told me that supersu had binaries to update. In fact several apps no longer work as titanium or twrp manager. Rootchecker confirms that I lost my root.

Installed without problem flashfire v2.79 / 20161211.. by twrp. But it seems unable to root me again because it runs all the time. 2 reboots have not changed anything.

Some advices please to progress?

C: \ Fastboot> fastboot getvar all

(Bootloader) version: 0.5

(Bootloader) version-bootloader: 1.61.0000

(Bootloader) version-baseband: 4T.35.3218.16

(Bootloader) version-cpld: None

(Bootloader) version-microp: None

(Bootloader) version-main: 7.19.401.30

(Bootloader) version-misc: PVT SHIP S-OFF

(Bootloader) serialno: *****

(Bootloader) imei: *****

(Bootloader) meid: 00000000000000

(Bootloader) product: m7_ul

(Bootloader) platform: HBOOT-8064

(Bootloader) modelid: PN0710000

(Bootloader) cidnum: 11111111

(Bootloader) battery-status: good

(Bootloader) battery-voltage: 3972mV

(Bootloader) partition-layout: Generic

(Bootloader) security: off

(Bootloader) build-mode: SHIP

(Bootloader) boot-mode: FASTBOOT

(Bootloader) commitno-bootloader: dirty-0e2a13e5

(Bootloader) hbootpreupdate: 11

(Bootloader) gencheckpt: 0
[Paid Software Announcement and Discussion] jcmm11:
Try dirty flashing the ROM and reapplying root
[Paid Software Announcement and Discussion] drewski_1:
I also have mixed behaviour after trying this maybe 13-15 times

A little under 1/2 the time, I have scrolling text and it looks fine.

The other times I've had a few scenarios. #1 & #2 seemed to happen about the same frequency while #3 only happened once

1) text appears on the bottom 1/3 only and looks to be overwriting itself without clearing / scrolling the original text so looks to be "flickering",

2) text looks to be starting OK and fills the screen, but again, does not start scrolling, but here only the upper 1/3 of the screen is doing the overwriting with the bottom part of the screen showing the original, fixed text

3) one line of text appeared at the bottom of the screen and the tablet froze requiring a reset with Pwr+Vol-dwn (this only happened once).

Upon reboot from #3, when LiveBoot started, I saw #1, with text only on the bottom part of the screen with the overwriting / flickering type of behaviour.
[Paid Software Announcement and Discussion] kopitalk:
I'm on N7 port MM 6.0.1 TW rom with SuperSU v2.79 systemless, Flashfire was granted root by SuperSU but then stuck at "Acquiring root access...". Any idea?
[Paid Software Announcement and Discussion] Freekolo:
Top support in XDA forum !

Thank you very much, your advice saved me.

After dirty flash, I removed all the crappy tools I had tried to use to get out of this situation.

A clean backup with Titanium and another with Twrp.

And hop, I jumped the step towards CyanogenMod 14.1 (no simcard recognized - but a solution seems valid to fix the error on GSM networks)

Also installed Slim7 Nougat (no simcard recognized too)

So I really need to apply the fix manually.

:)
[Paid Software Announcement and Discussion] bakhtawar shah:
How to download apps
[Paid Software Announcement and Discussion] Ja_som:
What apps?

If you mean FlashFire, you can find it on the Play Store
[Paid Software Announcement and Discussion] J_M_V_S:
I installed this on my HTC One m7 Dual Sim (M7CDUG) and it seems not to be detecting anything. I know my parition details and I was wondering if there's any way I feed FlashFire that info? Or how can I add to support to my device? Thank you.
[Paid Software Announcement and Discussion] KaMyKaSii:
http://xdaforums.com/general/paid-software/flashfire-t3075433/post69059419
[Paid Software Announcement and Discussion] J_M_V_S:
Thanks for the info. File attached.
[MENTION=631273]Chainfire[/MENTION]

Device info:

HTC One m7 802w (m7cdug).

Beware that I have a partitioned SD Card (fat32 + ext4 -mmcblk1p2-)
[Paid Software Announcement and Discussion] Cone1237:
Once you have rooted your phone and custom recovery and rom you will no longer be able to get or flash ota you will need to go back to stock
[Paid Software Announcement and Discussion] Ch3vr0n:
Wrong. When flashing SuperSU it takes a backup of boot and if you flash a custom recovery FF takes a backup of that too. Then when flashing an OTA though FF the backups get restored to enable OTA, and custom recovery flashed back after the OTA.

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] rybshik:
FlashFire-v0.52 fails to run on rooted Moto G4 Play

I have installed 'FlashFire-v0.52-20160718223301.apk' on Moto G4 Play rooted with (system-less?) SuperSU-v2.78. Bootloader is unlocked.

When I try to run it, it starts and then closes without any messages.

Android 6.0.1
[Paid Software Announcement and Discussion] ktmom:
Pull a catlog starting before you launch FF and see what it says.
[Paid Software Announcement and Discussion] rybshik:
Can you be more specific? Is [Tutorial] How To Logcat what I need?
[Paid Software Announcement and Discussion] ktmom:
Yes, exactly.
[Paid Software Announcement and Discussion] KaMyKaSii:
Unfortunately given the layout of your partitions, FlashFire can not identify them. I've already talked to Chainfire about some possible ways to identify them, and he said that this is not a high priority. Below you can see my post and his reply

http://xdaforums.com/general/paid-software/flashfire-t3075433/post66143356

http://xdaforums.com/general/paid-software/flashfire-t3075433/post66171336

Please use the latest version of anything before reporting bugs. The latest version of FlashFire is 0.53 and is available in the PlayStore

I think it meant that the problem happens when trying to start some action (after clicking on FLASH), then the required file would be /sdcard/FlashFire/lastlog. But this error has been reported several times (including by me) and I hope it will be fixed in the next update. This app is awesome
[Paid Software Announcement and Discussion] CynoMan:
Hi all. Has anyone successfully tested Flashfire on Asus phones?

I'm using Z00L on cm 14.1 Would be Flashing using the app later in the day ... Just wanted to know if any fellow Asus owners have gotten it right with Flashfire. Thanks ?
[Paid Software Announcement and Discussion] KaMyKaSii:
Test the backup function first. If it works correctly, you can try more dangerous actions like flash. But make sure you have some way to recover the phone in case something goes wrong, from a simple softbrick (bootloop on bootanimation) to a hardbrick (the device gives no sign of life)
[Paid Software Announcement and Discussion] Kartlis Deda:
New OTA ?

Hi,

Is there an easy way to render new Google OTA visible to FF?