yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] me_droid:
scootley, yes, thanks, I missed that, so we are pretty much both stock except for supersu (I'm on 2.82). In addition I'm running twrp recovery but not sure how that may impact this issue.

Where does FlashFire look for a downloaded OTA? Thought it might be worth a try to copy the zip to that location and let FlashFire find it and automatically generate a job to install it.
[Paid Software Announcement and Discussion] chisnz:
Trying to use FlashFire to upgrade Nexus 6p from June update to July OTA update. I'm running Magisk 13.170612.

FlashFire has worked fine in the past. Now whatever job I select I get a black screen for 20+ minutes.

My normal process now is to do a FlashFire backup immediately after flashing the OTA update then when I want to update to the next OTA I restore the backup to get completely back to stock then flash the new OTA. Now I can't even restore the backup as a simple job just to restore hangs with a black screen.

Any suggestions?
[Paid Software Announcement and Discussion] ktmom:
[MENTION=3002192]chisnz[/MENTION]

I was still on Magisk 12 and was able to test run a backup no problem. So I upgrade to Magisk 13.1 and got the same black screen problem you describe. The solution was to flash the (new) Magisk uninstaller and revert to 12.
[Paid Software Announcement and Discussion] chisnz:
Thanks, that's a big help. I'll give it a go.

[Edit] Worked a treat. So anyone having trouble on Magisk 13, take ktmom's advice and downgrade to 12 to get going again.
[Paid Software Announcement and Discussion] ktmom:
I tried again this morning wanting to get a log after updating to Magisk 13 and this time it worked as expected. So now I'm thinking there could be a conflict that using the uninstaller, then upgrading cleaned up.
[Paid Software Announcement and Discussion] tasnim_tamim:
Can anyone help me? I am running Galaxy Grand Prime. I tried to backup modem partition (which is protected) and now my phone is stuck in a black screen for more than 15 minutes. I heard that sometime backup takes more than 20 minutes.. But the partition is only 15mb.. So I am extremely worried should I pull the battery. Please can anyone help me.. Thanks :)
[Paid Software Announcement and Discussion] ktmom:
Although I hope you have by now, yes, pull the battery. Look at the FF log to get an idea what happened. What are you rooted with?
[Paid Software Announcement and Discussion] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] just tried updating to 7.1.2 (N2G48B, Jul 2017) on my nexus 6P. Everything went fine (did a full backup first) until after the patch. The patch itself was applied but SuperSU 2.82 (chainfire compiled) FAILED to extract ramdisk. Full log will be attached once i get the device booting and rooted again

1. After no-boot i connected device via usb to pc

2. Flashed TWRP 3.1.1-0

3. System restart in twrp

4. Device booted but NOT ROOTED into new system update N2G48B

5. fastboot reboot bootloader & flashed N2G48B boot & recovery

6. fastboot reboot to test system boot, boot succesfull

7. adb reboot bootloader

8. fastboot boot twrp 3.1.1-0

9. Flashed SuperSU 2.82 chainfire compile SUCCESFULLY (ramdisk extraction worked this time)

10. Rebooted system, now succesfully rooted

Syslog app logs & lastlog flashfire attached
[Paid Software Announcement and Discussion] fndpena:
Is this working on O already? Last time I checked it wasn't.

Any info about this? Is there a beta channel for this app?
[Paid Software Announcement and Discussion] rybshik:
what does "chainfire compiled" mean? and what would be "non-chainfire compiled"?
[Paid Software Announcement and Discussion] jcmm11:
From Chainfire's site as opposed to from the play store. Chainfire doesn't control the play store, the company he sold to does.
[Paid Software Announcement and Discussion] sabrefresco:
Same issue with 13.3. Here's the pastebin

The following line might be of use:

losetup: /dev/block/loop0: Device or resource busy
[Paid Software Announcement and Discussion] fearlessrogue32:
Problems Using App

I've used Flashfire in the past to flash the stang5litre rom on my verizon galaxy s4. When I tried it recently, using the newest version of Flashfire, there were some issues. After I push flash, the screen goes black and loads stuff as normal, but after it is done loading it sits at a black screen for awhile before rebooting. No changes are made. I recently went back to stock rom and rerooted. Here is a pastebin link to my last log, https:// pastebin.com/21nC2BNt. The last line talks about showing the ui, so maybe there was a problem there?
[Paid Software Announcement and Discussion] bggold:
Anyone with a pixel running magisk v12 or 13 successfully be able to backup or flash without getting the black screen and not getting past it?

Thanks
[Paid Software Announcement and Discussion] Ch3vr0n:
No because as on the app website stated, the app REQUIRES SUPERSU or a kernel in permissive mode. Magisk will NOT work

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] KaMyKaSii:
FlashFire has initially supported Magisk since version 55, look at the changelog. But the problem may be with regard to Magisk or not. For example, even using SuperSU I can't make FlashFire work on 6.0, but on 7.1.2 it works perfectly
[Paid Software Announcement and Discussion] culiacanazo:
Funny! With me it's the opposite
[Paid Software Announcement and Discussion] ktmom:
Funny, I'm using FF with Magisk v12 through v13.3. ?
[Paid Software Announcement and Discussion] bggold:
do either of you have a pixel?
[Paid Software Announcement and Discussion] ktmom:
Not me. Have you looked at your log?
[Paid Software Announcement and Discussion] bggold:
Nothing in the log past creating fstab.
[Paid Software Announcement and Discussion] Zamanyxa:
Отправлено с моего SM-J120H через Tapatalk
[Paid Software Announcement and Discussion] Zamanyxa:
[/IMG]

Отправлено с моего SM-J120H через Tapatalk
[Paid Software Announcement and Discussion] Ch3vr0n:
And now in English per forum rules.

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] rybshik:
Downgrading full stock firmware to older firmware version

Is Flashfire capable of downgrading firmware to older full stock firmware package with older firmware version (i.e. earlier bootloader version and earlier system security patch version)?

Is possible in principle?

If i have already upgraded to stock anroid 7.1.1 firmware, can I flash full stock android 6.0.1 firmware? For example, such as "XT1601_HARPIA_LATAM_MPI24.241-15.3_cid50_subsidy-LATAM_regulatory-DEFAULT_CFC.xml.zip"

Can I achieve the same with RAW backup and restore?

Say, I RAW back up stock Android 6.0.1 firmware, then OTA upgrade to stock android 7.1.1.

If I now restore the RAW backup for Android 6.0.1 firmware, will it be identical to the original stock firmware and eligible for OTA?

Will it work on Moto G4 and Moto G4 Play? Will a free version of Flasfire do the job?

And one more question: Will Flasfire install on rooted custom ROM with OpenGApps such as LinageOS (based on Android 7.1.2)?

Thanks
[Paid Software Announcement and Discussion] culiacanazo:
I don't THINK it does. .. only the unprotected partitions when downward it is. .. that's what's done in my case, but whether it has the ability, i don't KNOW
[Paid Software Announcement and Discussion] ktmom:
Yes. The question is, how wise is it to do so.

FF has no idea what you're flashing over what. It will attempt to do what you tell it to do. Downgrading a bootloader in my experience is not a good idea. As far as I know, most bootloaders are backwards compatible. But, for example, while you can use the 7.1 bootloader on an N6 back to 5.1.1, you can not go back to 5.0. If you attempt to revert the bootloader on the N6, you'll probably softbrick the device.

What happens on other devices should be researched first.

This may be device dependant. On the N6 the answer is yes. Other devices, the answer is yes since that's how some have to go about getting their device rooted (revert to a exploitable version then step up versions again).

If by raw you mean take an image of a partition and restore that partition, the answer should be yes.

Most OTAs are looking to see if modified at a system level. Most OTA updates are just that, file differentials which are applied against expected files. If there is any modification, those files can not be patched with a differential so the OTA fails.

No reason it shouldn't. At this time, the pro version is a way to support the developer.

Again, no reason it shouldn't. Just try it. It won't break your device. Worse case is, it just doesn't work. If it doesn't work, get a log.
[Paid Software Announcement and Discussion] hell3456:
Hello , I have a sony Xperia Z3 Dual (d6633). Currently rooted (Lollipop 5.1.1++SuperSU-v2.82++lockeddualrecovery2.8.26). Trying to use flashfire to upgrade to Marshmallow 6.0.1 resulted in the lost of root and boot recovery option(TWRP). I am using a prerooted zip created with PRFCreator_v1.3 (firmaware D6633_23.5.A.1.291_R10D++++SuperSU-v2.82++lockeddualrecovery2.8.26).

During the process into flashfire configuration I have selected the following options (Inject SuperSU++Preserve recovery).

The new firmware install correctly but without root.Any idea why is not working ?.
[Paid Software Announcement and Discussion] KaMyKaSii:
Send the /sdcard/FlashFire/lastlog file so we can take a look
[Paid Software Announcement and Discussion] hell3456:
Well that is a another strange thing, into my flash card there is no such folder,. I have already solved the problem following another option (the system do not allow me to post the link)

The next chance to use FLASHFIRE will be to upgrade to Nougat. If I found any error will post it here

Regards and thanks for your promnt attention.
[Paid Software Announcement and Discussion] HBK_Rishav:
Can I flash kernel with FlashFire in my Sony xperia z4?
[Paid Software Announcement and Discussion] jcmm11:
Unless there's something really different about that device (and ttbomk there isn't) sure. I've flashed plenty of kernels with it (albeit on a Nexus)
[Paid Software Announcement and Discussion] ktmom:
Have you tried a simple back up? If that works, then flashing a kernel should.

I think the likelihood of a problem being created by trying to flash a kernel is low. You can minimize your risk by doing a back up first.
[Paid Software Announcement and Discussion] foosion:
When I try to backup my Nexus 6P (latest stock Nougat) using FlashFire 0.57 and backing up to adb (v 1.0.39), FF waits for me to type "adb backup go -f filename.zip". I type that on my PC and adb responds "Now unlock your device and confirm the backup operation ...", then goes back to the command prompt and nothing happens on the PC or the phone (other than adb creates a 0 byte file on my PC).

This used to work. adb is otherwise working normally, for example, I can backup with TWRP (adb backup --twrp).

I've successfully backed up and restored with FF in the past, so I'd like to get this working again. How do I fix?
[Paid Software Announcement and Discussion] gadiator:
DP4 on N5X Problem

I wanted to flash the newest DP OTA (OPP4.170623.014) on my Nexus 5X but when i pressed the flash button the screen turns of and stays of.

I'm on a rooted unlocked DP3.

https://pastebin.com/zuHGH8ai
[Paid Software Announcement and Discussion] Ibuprophen:
I believe that this may be a Language Barrier regarding your question [specifically the Structure of the translation from Unknown to English] :) ...

If I'm reading your question correctly, are you asking the following question?

I had attempted to flash the newest DP OTA (specifically the OPP4.170623.014) on my (Unlocked and Rooted) Nexus 5X. Then suddenly, after i had selected/pressed the "Flash" button, the devices display screen suddenly shut off and stayed off (like pulling the battery from the device). And when I powered the device back on, it was though nothing had happened. Please Help :)

I hope i had clarified your question correctly... :)

But, whether or not i had clarified your question, it's extremely difficult to answer without some additional information.

With that stated, questions of this nature is tough to answer because you really have to explain via text and provide some type of logcat or anything else you can provide so that others are able to understand and see (in a way) exactly what you're doing and experiencing.

I hope i had explained it okay... :p

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.

×MY DEVELOPMENTS×

[APP][TOOL][4.2+]The SELinux Toggler

[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}

×IN DEVELOPMENT×

[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch

Will Supersede "The SELinux Toggler"

×IDEAS FOR DEVELOPMENT×

[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}

[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
[Paid Software Announcement and Discussion] gadiator:
Yes, Ibuprophen.

You clarified it right.

So i can try it a little bit more precisely.

1. Starting the app. I get a dialog which tells me: "A OTA has been detected. Generate actions to flash it?"

2. I press the "Okay" button and the popup closes.

3. Next step is After i had selected/pressed the "Flash" button. I get a new dialog with the warning, that i'm trying to flash a block-level OTA, but my /sysem, /vendort or /oem partition has been modified.

4. I press the "Ignore" button and the popup closes. I get a new dialog: "It can take a minute or two for FlashFire to load. A black screen may happen twice, for up to a half minute."

5. I press the "Ok" button and the popup closes. A loading dialog appears for one or two seconds followed up by a loading screen for some seconds and then the devices display turns off and stays off.

I hope it is much clearer now.
[Paid Software Announcement and Discussion] mat317:
Having this exact problem flashfire says loading then screen turns off and I have to turn it back on with power and volume. Doesn't matter if I leave it for ages either
[Paid Software Announcement and Discussion] rybshik:
better yet Tylenol :)
[Paid Software Announcement and Discussion] gadiator:
No ideas about what's going wrong?
[Paid Software Announcement and Discussion] ktmom:
Look at your FF log and see where it's getting hung up.
[Paid Software Announcement and Discussion] gadiator:
The device hung up after unmounting /system. But i've no clue how i can fix it.

https://pastebin.com/zuHGH8ai
[Paid Software Announcement and Discussion] rybshik:
Extracting bootloader by RAW backup

Via RAW backup, I want to extract bootloader from one Moto and restore it to another, but identical hardware.

I would like to achieve the same result as if flashing stock firmware with Fastboot:

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img

So effectively, I want to extract raw versions of 'gpt.bin' and 'bootloader.img'.

Will such approach work?

I know it can brick the phone :)

Moto G4 Play XT1601
[Paid Software Announcement and Discussion] jcmm11:
Don't know about Moto (though I suspect it's similar), but on Nexus bootloader is spread out over 11 partitions so the approach you want is problematic to say the least. In other words there is no single "bootloader.img" to extract.

That being said if you get raw images of all the relevant partitions and successfully restore them it should work (theoretically).
[Paid Software Announcement and Discussion] rybshik:
Are there any tips on information for successful restore of a full RAW backup including bootloaders?
[Paid Software Announcement and Discussion] jcmm11:
I could give you the Nexus layout, but I have no clue on if yours is laid out the same.
[Paid Software Announcement and Discussion] rybshik:
Please do. Every bit helps :)
[Paid Software Announcement and Discussion] jcmm11:
Ok. These are all the partitions that are part of the bootloader on the Nexus 5x

/dev/block/platform/soc.0/f9824900.sdhci/by-name/sbl1bak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/tzbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/rpmbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/abootbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/pmicbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/hypbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/keymasterbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlibbak

/dev/block/platform/soc.0/f9824900.sdhci/by-name/sbl1

/dev/block/platform/soc.0/f9824900.sdhci/by-name/tz

/dev/block/platform/soc.0/f9824900.sdhci/by-name/rpm

/dev/block/platform/soc.0/f9824900.sdhci/by-name/aboot

/dev/block/platform/soc.0/f9824900.sdhci/by-name/pmic

/dev/block/platform/soc.0/f9824900.sdhci/by-name/hyp

/dev/block/platform/soc.0/f9824900.sdhci/by-name/keymaster

/dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib

/dev/block/platform/soc.0/f9824900.sdhci/by-name/sdi

/dev/block/platform/soc.0/f9824900.sdhci/by-name/imgdata

/dev/block/platform/soc.0/f9824900.sdhci/by-name/sec

The following partition is used as a flag partition when updating the bootloader. It's normally set to (32 bytes of) binary zeroes, but when updating the boot partition via boot flash or ota it's set to "updating-bootloader" (filled out with binary zeroes) at the start of the process and reset back to binary zeroes at the end. I would probably just ignore it if I were using flashfire.

/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc
[Paid Software Announcement and Discussion] rybshik:
Please share your experience of installing FlashFire over LineageOS 14.1.

Is your LineageOS rooted with standard "addonsu-14.1-arm-signed.zip"?

In my case, FlashFire refuses to install on LineageOS rooted with "standard" "addonsu-14.1-arm-signed.zip".

It says something like: "Root detected, but you should use SuperSU instead."
[Paid Software Announcement and Discussion] KaMyKaSii:
Did you really quote a post from 6 months ago? Wow. But anyway, have you tried to make selinux permissive before opening FlashFire? And why not migrate to SuperSU?
[Paid Software Announcement and Discussion] rybshik:
Is IMEI inluded in full RAW backup?

I just did. Thank you!

I am now making a full raw backup of all available partitions. All I mean I checked all 22 of them (Moto G4Play Harpia).

Is IMEI captured by such a backup ?

If so, which partition contains the IMEI data ? So I will exclude it.

I am going to restore the backup to another, but identical Moto G4Play Harpia.

I do not want to change IMEI :)

How likely will I brick the phone if enable "Flash bootloaders" in Setting? :)

I hope less than 20% :)
[Paid Software Announcement and Discussion] jcmm11:
If you tick the option to backup "ID Device IDs, EFS, IMEI" you'd see that the 2 partitions are "Modem Firmware Data #1" and "Modem Firmware Data #2".

Percentage is somewhere between 0 and 100 ? (sorry, really can't give an accurate estimate. If everything flashes correctly you should be fine. If something happens and you crash while restoring then all bets are off)
[Paid Software Announcement and Discussion] rprussell:
SCH-I545 Verizon S4 won't do ANYTHING

Here's the Pastebin...

So, I can't seem to be able to do ANYTHING - this lastlog is from just trying to do a backup of the 10meg boot partition.

It just reboots, runs through the flashfire scrolling boot sequence, then the screen goes black and it sits, and sits, and sits, and... after as long as ten minutes of nada, I pull the battery and reboot the phone. I originally started out trying to do a flash, then a full backup, then the itty bitty minimal backup as described - same behavior each time.

I'm running OF1, ODIN'ed to stock, then rooted using Kingroot, then SuperSUMe'ed, so it's ostensibly running SuperSU Pro 2.82. Flashfire is 0.57beta.

I have "Enable su during boot" checked, and also "Mount namespace separation."

Stock OF1 (although rooted) is getting really draggy and I would love to replace with one of the few options still available at OF1.

Is the logfile useful at all? Can't figure out what's up.

Thanks,

R

---------- Post added at 11:03 AM ---------- Previous post was at 10:54 AM ----------

I will add: The blue status led in the upper left corner pulses slightly while I wait with no screen - this is whether it's plugged into power or no.
[Paid Software Announcement and Discussion] Chainfire:
PSA: some users have reported issues flashing this months OTA with FlashFire. It will probably be the end of the week before I can look at this (and hopefully solve it).
[Paid Software Announcement and Discussion] Alxoom33:
I had no problems with the Nexus 6 7.1.1 August factory image.
[Paid Software Announcement and Discussion] peterlee928:
hi all. just recently downloaded this sweet app. i know this a no-no, but ive flipped through many (not all) of the posts here. is there a post that outlines the process on how to flash factory image/twrp/supersu?

currently on a verizon pixel xl. rooted via twrp/supersu. no custom roms or kernels - pure stock.

sincerely much thanks in advance. ?
[Paid Software Announcement and Discussion] fearlessrogue32:
It seems that Flashfire v53 is the newest version that still works on the sch i545. Anything newer doesn't want to work with it and results the same as you described if used. The only way for me to get Flashfire v53 to work though was to manually set date to February of 2013. I've only used it for simple backups, haven't flashed any roms yet, but it works.
[Paid Software Announcement and Discussion] Ibuprophen:
Your correct as to the FlashFire v0.53 is, in fact, the last version that will work on the SCH-I545 with a locked bootloader.

Certain fixes/enhancements that Chainfire had implemented, beginning with FlashFire v0.55, had prevented it from working on the device.

This is why I had to manually resign (not modify) the app for my SCH-I545 solely to sever it from updating from the Play Store though, it's still seen but, severed.

I did purchase the app and, based on my account, it still registers as being purchased.

There's much more to it regarding FlashFire v0.53 being the last one to work for the SCH-I545 but, that's the gist of it.

Maybe [MENTION=4310299]bilgerryan[/MENTION] can confirm or add to any of the information i had provided but, i believe that this pretty much covers it.

Good Luck!

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[Paid Software Announcement and Discussion] peterlee928:
any love?
[Paid Software Announcement and Discussion] Ch3vr0n:
I reported problems flashing the ota the past 2 months. Each time the boot image or loader refused to either get patched properly or boot up the device. Fix for both ota's was to download the factory image, flash the boot image and root with 2.82. the one time I flashed SR1 the signing happened and device didn't boot either. Using 2.82 over the top fixed that. (Nexus 6p)

[MENTION=631273]Chainfire[/MENTION] that said can SR2 be flashed with FF 0.57. I read the release notes that FF might need an update AFTER flashing SR2, but nothing said if it could successfully flash SR2 itself.

Sent from my Nexus 6P with Tapatalk
[Paid Software Announcement and Discussion] jcmm11:
Should work. I also suspect that FF will still work if you're not using SBIN mode, although I'm less sure about this part of the statement.
[Paid Software Announcement and Discussion] lebaud07:
Hi all,

I've just tried to flash the new august-patched system (nexus 6, Android 7.1.1 N6F27I) with flashfire, and it doesn't seem to work anymore with magisk 13.3/magiskSU.

As far as I remember, I flashed the "may" version (N6F27E) without any problem, but I think it was with magisk v12...

Today, when trying to flash, I get the normal black screen but the phone never reboots for flashing, and get stuck here (hard reboot needed).

In my memories, the same problem happened a long time ago with magisk/phh's-superuser when forcing "permissive mode" : flashfire application worked and detected root, but flash stucked during the first black screen.

How can I help for more investigation ?

Thanks in advance !

Log after 20 minutes of «black screen» in attachement.