Database Info

FlashFire with HTC One A9?

Anyone used ChainFire's FlashFire with the One A9?
I've used it for backups successfully but have yet to restore anything with it (a little squeamish to do so :silly.
And I'll just add, if anyone has used it and could offer any tips or procedures that would be great.

FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
Click to expand...
Click to collapse
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?

theNdroid said:
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
Click to expand...
Click to collapse
Of course. Root is required to use FlashFire. I use Xposed as well, and I've had no problems updating via FlashFire.

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Click to expand...
Click to collapse
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?

eelpout said:
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
Click to expand...
Click to collapse
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***

CSnowRules said:
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
Click to expand...
Click to collapse
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.

eelpout said:
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
Click to expand...
Click to collapse
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.

CSnowRules said:
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
Click to expand...
Click to collapse
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.

eelpout said:
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
Click to expand...
Click to collapse
Ok, this post will go a bit off topic. That being said, I can offer two courses of action. I take no responsibility for anything in this post.
Safest--almost no risk (my personal preference)
1. Backup your data partition, including internal SD via TWRP to ext SD or USB OTG drive. Flash the latest RUU from HTC. Boot stock and apply OTAs until there are no more updates available. Fastboot flash the latest TWRP, and finally restore your data and flash the latest SuperSU via TWRP. Reboot your fully updated, rooted A9 with all your data still intact.
A little risky and untested to my knowledge--could result in a hard brick if something partially fails. FLASHING BOOTLOADERS IN FLASHFIRE IS STILL ALPHA FOR HTC DEVICES!!! This may work with s-on...but may require s-off.
Your system partition must have never been mounted r/w for this to work.
2. Download the OTA zips for your phone from the first update available to the latest and the latest SuperSU and TWRP. Use FlashFire to do everything in one shot. Select allow flashing bootloaders in FlashFire settings, select your OTAs for installation from oldest to newest (don't select restore boot and recovery), select TWRP and SuperSU for installation, disable everroot and preserve recovery. Cross your fingers and timidly press flash... If all is successful, you should have the same end result as option 1.
I STRONGLY recommend the first method, but if you're feeling lucky and decide to try the second method, please share how it goes, since this post is FlashFire related and this would be the ultimate test of FlashFire for our devices.

For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.

NuShrike said:
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
Click to expand...
Click to collapse
The solution for problem 1 can be handled in TWRP. The files can be deleted via TWRP's file manager or the built in terminal, which may be easier for some people.
Also, the solution for the corrupted data and internal SD is to create an image of the data partition (just like the system image backup option). This can be done via dd in TWRP or adb. It requires a large amount of storage and it takes longer, but I've had to do it, since I use VIP Access by Symantec for work. A normal file based backup in TWRP breaks that app. This also keeps the pin/fingerprint data intact.
If we could have that implemented in a user friendly manner, that would be great, but I'm sure CaptainThrowback and Chainfire both have bigger issues to deal with. I could probably figure out a solution, but the work wouldn't be worth it for my own benefit, since I'm fluent with the Linux command line.

Root, TWRP and Flashing

I recently got an S7 (Exynos) SM-G930F and decided to root it. So I went with the typical CF-Auto-Root method... I used the latest ODIN with the correct auto root file and everything went well. I have root.
But then I noticed that I didn't have any recovery, so I installed TWRP Manager from the Play Store and flashed recovery with that. Everything works fine except for not having access to backup /Data, this was expected.
But despite everything pretty much working, I've read on a few threads here that I was supposed to wipe my phone after flashing TWRP. Now I've also read the TWRP install thread which doesn't mention anything about wiping my device, but it does offer another method of rooting the S7... Flash TWRP first using ODIN, then flash SuperSU and dm-verity/force encryption disabler.
So I have a couple of questions.
In the TWRP guides it mentions this: "By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!". I've never had this issue, does CF-Auto-Root or SuperSU resolve this issue?
Do I need to install the dm-verity/force encryption disabler?
If I do have to wipe my device, am I going for a standard (factory reset) wipe? Advanced wipe (if so, which partitions?) or format data?
Unless there's another way to gain full access to all partitions in order to perform a complete nandroid backup (including data)?
Basically, once I've completely backed up the S7 I'd like to install the Xposed Framework. Will installing this lose any data?

d3adm8n said:
I recently got an S7 (Exynos) SM-G930F and decided to root it. So I went with the typical CF-Auto-Root method... I used the latest ODIN with the correct auto root file and everything went well. I have root.
But then I noticed that I didn't have any recovery, so I installed TWRP Manager from the Play Store and flashed recovery with that. Everything works fine except for not having access to backup /Data, this was expected.
But despite everything pretty much working, I've read on a few threads here that I was supposed to wipe my phone after flashing TWRP. Now I've also read the TWRP install thread which doesn't mention anything about wiping my device, but it does offer another method of rooting the S7... Flash TWRP first using ODIN, then flash SuperSU and dm-verity/force encryption disabler.
So I have a couple of questions.
In the TWRP guides it mentions this: "By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!". I've never had this issue, does CF-Auto-Root or SuperSU resolve this issue?
Do I need to install the dm-verity/force encryption disabler?
If I do have to wipe my device, am I going for a standard (factory reset) wipe? Advanced wipe (if so, which partitions?) or format data?
Unless there's another way to gain full access to all partitions in order to perform a complete nandroid backup (including data)?
Basically, once I've completely backed up the S7 I'd like to install the Xposed Framework. Will installing this lose any data?
Click to expand...
Click to collapse
Of course you are going to want to flash .zips through your Recovery, but as you have recognised there is the DM-Verification that will stop you doing so. In order to get rid of the encryption you will have to firstly have to Factory Reset but as you know this will also delete all apps and data that you have on your Internal Storage.
Then, you need to flash a .zip called 'no-verity-encryption-opt' and this will apply a patch onto your boot so you can flash unknown images and zips through.
If you can't find this no verity zip, leave me your email and I'll try and send it to you.
Good luck!
Also, installing the Xposed Framework will not cause you to lose any of your data.

AzzyC said:
Of course you are going to want to flash .zips through your Recovery, but as you have recognised there is the DM-Verification that will stop you doing so. In order to get rid of the encryption you will have to firstly have to Factory Reset but as you know this will also delete all apps and data that you have on your Internal Storage.
Then, you need to flash a .zip called 'no-verity-encryption-opt' and this will apply a patch onto your boot so you can flash unknown images and zips through.
If you can't find this no verity zip, leave me your email and I'll try and send it to you.
Good luck!
Also, installing the Xposed Framework will not cause you to lose any of your data.
Click to expand...
Click to collapse
Thanks for the info.
I may have already done this, I honestly can't remember. Is there any way to check if I've already installed no-verity-encryption-opt? Because I am already able to install zips in Recovery, so far I've installed a SuperSU update and AdAway. Although I do get a fair amount of 'Failed/Unable to mount /data' messages which may suggest that these zip installs didn't actually work.
I guess I still need to factory reset? And I guess that also means rooting again and installing no-verity-encryption-opt, then finally Xposed?

d3adm8n said:
Thanks for the info.
I may have already done this, I honestly can't remember. Is there any way to check if I've already installed no-verity-encryption-opt? Because I am already able to install zips in Recovery, so far I've installed a SuperSU update and AdAway. Although I do get a fair amount of 'Failed/Unable to mount /data' messages which may suggest that these zip installs didn't actually work.
I guess I still need to factory reset? And I guess that also means rooting again and installing no-verity-encryption-opt, then finally Xposed?
Click to expand...
Click to collapse
I had the same error message you are facing right now. Can you let me know what values you see when you view the Data, System and Cache partition, after clicking on 'Partition Options' - If you're on the latest TWRP you can take screenshots by hitting the Power and Vol Down.
^^^IGNORE^^^
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL

AzzyC said:
I had the same error message you are facing right now. Can you let me know what values you see when you view the Data, System and Cache partition, after clicking on 'Partition Options' - If you're on the latest TWRP you can take screenshots by hitting the Power and Vol Down.
^^^IGNORE^^^
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
Hey man, i'm having that problem.
I want to root my phone but i am not able to acess Internal Storage, on twrp its showing 0mb.
I did what you says in this post but i always have caught in ''Encrypetd phone'' or something like this.
What are the steps? 1- format data (then deletOS) and then? Can you help me please?

Flashing new firmware without loosing data

So I have an XZ Premium and I rooted it day 1 i got it (which is now a few months back).
I wanted to know if theres a way to flahs a new firmware without loosing all my data (apps, pictures, etc).

BigBrainAFK said:
So I have an XZ Premium and I rooted it day 1 i got it (which is now a few months back).
I wanted to know if theres a way to flahs a new firmware without loosing all my data (apps, pictures, etc).
Click to expand...
Click to collapse
You can use newflashtool, leave out all .ta files and userdata.sin

would you also happen to know how i can use the twrp to make a backup since when i tried it in the past it always produced garbage data when i restored them. this could be because of encryption or smth.

I'd like to know, that files I minimum need to change SI on XZP
I want to change from my operator's version to generic branding

@BigBrainAFK
use PrfCreator

kistigun said:
You can use newflashtool, leave out all .ta files and userdata.sin
Click to expand...
Click to collapse
So just search for "*.ta" in the folder of the firmware i loaded with xperifirm and delete ALL of them as in literally all of them.
And delete the "userdata_something_something.sin".
Correct?
//EDIT: Did it and all my data is gone thx to it being "corrupted" after decryption

BigBrainAFK said:
So just search for "*.ta" in the folder of the firmware i loaded with xperifirm and delete ALL of them as in literally all of them.
And delete the "userdata_something_something.sin".
Correct?
//EDIT: Did it and all my data is gone thx to it being "corrupted" after decryption
Click to expand...
Click to collapse
When I flash a new fw I remove all .ta files + userdata and I never get corruption.
Leave any .ta files in there and corruption happens.

i change name of userdata_X-FLASH-CUST-B6B5.sin and not worck

I really need your helps capacitive keys stucked

Hello.
Sorry my English is ....
I have a rooted galaxy s7 i use light room rom
The problem:
I tried to modify the file generic.kl to disable only the button recent app i just added a # before the line off switch app but after rebooting all the capacitives keys are blocked i deleted the # and reboot again but its stucked no capacitives keys responded
I even tried to download another file .kl and no responding
Plz helps me if there is any way to back or to repair this problem without formatting or installing or flashing any rom
:crying::crying::crying:

Houssem.sniper said:
Hello.
Sorry my English is ....
I have a rooted galaxy s7 i use light room rom
The problem:
I tried to modify the file generic.kl to disable only the button recent app i just added a # before the line off switch app but after rebooting all the capacitives keys are blocked i deleted the # and reboot again but its stucked no capacitives keys responded
I even tried to download another file .kl and no responding
Plz helps me if there is any way to back or to repair this problem without formatting or installing or flashing any rom
:crying::crying::crying:
Click to expand...
Click to collapse
You have to reflash your rom...
. But you can use twrp and just flash the data partition after you clean install
([emoji3590]09-09-18[emoji3590])

PoochyX said:
You have to reflash your rom...
. But you can use twrp and just flash the data partition after you clean install
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
By using this method i lose my data app and settings?

Houssem.sniper said:
By using this method i lose my data app and settings?
Click to expand...
Click to collapse
No your data and apps are in the data partition.... The system partition is what's going to fix your issue.... Before you clean install do another backup(Just data partition) and remove your magisk cause you won't have the modules after this is done cause magisk modules are store in system partition so after you clean wipe and restore your data partition then you reflash magisk and add back your modules and (xposed module if you use xposed) and you should be good to go if installs back good then your good there's a chance you can just get a blank screen after app optimization when you restore the Data partition if that happens you just going to have to rebuild your daily driver
([emoji3590]09-09-18[emoji3590])

PoochyX said:
No your data and apps are in the data partition.... The system partition is what's going to fix your issue.... Before you clean install do another backup(Just data partition) and remove your magisk cause you won't have the modules after this is done cause magisk modules are store in system partition so after you clean wipe and restore your data partition then you reflash magisk and add back your modules and (xposed module if you use xposed) and you should be good to go if installs back good then your good there's a chance you can just get a blank screen after app optimization when you restore the Data partition if that happens you just going to have to rebuild your daily driver
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Thank you very much you save my life.. this is the best forum ever

Houssem.sniper said:
Thank you very much you save my life.. this is the best forum ever
Click to expand...
Click to collapse
Anytime that's what we here for [emoji817]
([emoji3590]09-09-18[emoji3590])

Deteled some system apps, now stuck in a bootloop

It is just as the title states. I would like to somehow fix my phone instead of just recovering.
I can still access twrp, and the app(https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp) is used to create it with has created some backup files that i can still access. Is there still hope?
Mi 8 Pro with lineage os 18 unofficial

PalanixYT said:
It is just as the title states. I would like to somehow fix my phone instead of just recovering.
I can still access twrp, and the app(https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp) is used to create it with has created some backup files that i can still access. Is there still hope?
Mi 8 Pro with lineage os 18 unofficial
Click to expand...
Click to collapse
If you have some idea which apps you uninstalled then you can put them back in the right directory/folder, the app you used probably created a folder to backup them anyway for the next this app is not recommended to use it blindly; it doesn´t have a good criteria to determine what´s important and what´s not.
Or you can flash only the system image and after that wipe caches, reboot.

SubwayChamp said:
If you have some idea which apps you uninstalled then you can put them back in the right directory/folder, the app you used probably created a folder to backup them anyway for the next this app is not recommended to use it blindly; it doesn´t have a good criteria to determine what´s important and what´s not.
Or you can flash only the system image and after that wipe caches, reboot.
Click to expand...
Click to collapse
do you know of a way to find out exactly whats missing? like some log or something like that?

PalanixYT said:
do you know of a way to find out exactly whats missing? like some log or something like that?
Click to expand...
Click to collapse
Yes, there are some apps on PlayStore that can do that but you can´t boot right now to use it, probably you can take some logs through adb while in TWRP, check this https://github.com/IzzySoft/Adebar
The app you used creates a folder in the SDCard, probably it keeps the apps there, if you have TWRP you can navigate to it and you´ll find them.

the app has created an xyz.apk.backup can i just use adb install, or should i do something different?

hmm, i think just reflashing the system image would be easier. So should i just reflash the lineageos.zip?

PalanixYT said:
the app has created an xyz.apk.backup can i just use adb install, or should i do something different?
Click to expand...
Click to collapse
Yes, the first is identify the apps and then you can install them using adb through TWRP or copying the app to the folder where it was previosuly.
PalanixYT said:
hmm, i think just reflashing the system image would be easier. So should i just reflash the lineageos.zip?
Click to expand...
Click to collapse
You can flash it just wiping caches.

ok thank you very much, you are a life saver

i'm sorry i messaged you

it didn't work. Maybe also flash gapps?

PalanixYT said:
it didn't work. Maybe also flash gapps?
Click to expand...
Click to collapse
What´s inside the LOS zip? And what exactly didn´t work?

it's just the zip i used when installing the custom rom. i can send the file if you wnat.
META-INF/com/android/metadata
system.new.dat.br
system.patch.dat
vendor.new.dat.br
vendor.patch.dat
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
boot.img
install/bin/backuptool.functions
install/bin/backuptool.sh
system.transfer.list
vendor.transfer.list
META-INF/com/android/otacert
i was still inside a boot loop

PalanixYT said:
it's just the zip i used when installing the custom rom. i can send the file if you wnat.
META-INF/com/android/metadata
system.new.dat.br
system.patch.dat
vendor.new.dat.br
vendor.patch.dat
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
boot.img
install/bin/backuptool.functions
install/bin/backuptool.sh
system.transfer.list
vendor.transfer.list
META-INF/com/android/otacert
i was still inside a boot loop
Click to expand...
Click to collapse
It could work if you do it correctly:
- Wipe system, caches and data (not format)
- Flash the LOS zip.
- Flash the GApps (if you had previously Google apps on it)
- Reboot.

it worked, thank you very much. Is there a way to restore my phone to its previous state? i made a twrp backup just in case

PalanixYT said:
it worked, thank you very much. Is there a way to restore my phone to its previous state? i made a twrp backup just in case
Click to expand...
Click to collapse
Great, you can restore it just at the same time you did take the backup, if at the moment that this happened you didn´t take a backup of course you can´t anyway if you had some apps synchronizing with the cloud then this will be the only way. It works similarly as Windows (or Linux distros) also work if you have some idea from.