yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] daniello8:
S5 ... Backup still hangs at dome point during data backup. Only pulling battery helps then. Plenty of space in ext SD.

Gesendet von meinem SM-G900F mit Tapatalk

Edit:

No last_kmsg is written .. I checked the flashfire log (360K) from yesterday and this is the last line:

[UI] data/com.sec.android.app.sbrowser/app_sbrowser/Default/

I then started a fresh backup and the flashfire log (2200K) shows these as last lines:

[UI] dalvik-cache/arm/data@app@com.google.android.tts-1@base.apk@classes.dex
[UI] dalvik-cache/arm/data@app@com.sec.android.app.shealth-1@base.apk@classes.dex
[UI] IOException: write failed: EFBIG (File too large)
[EXC] IOException: write failed: EFBIG (File too large)

This time I also had the error message on my display.

BTW .. could you enable the reboot by long pressing the power button?

Edit 2: Backup works with V18 .. THANK YOU!
[Paid Software Announcement and Discussion] ionutmaruta:
Problems on G900F.

I made a FULL LZ4 backup first (on internal sd) with all partitions, installed applications, etc.

Flashfire v0.16 has been insterted in System.

Reboot, wipe data/factory settings + wipe cache partition.

Start the phone, I made the configuration for the first run the i run FlashFire to recover de full backup.

FlashFire verify the MD5 first, but at the SYSTEM it show IO error or something like that.

I can't remember the error message, because the phone has been restarted when I was to write here.

It stay for 3 minutes or I cand manually reboot. I leave it for 3 minutes....

I remember something like this: \dev\flashfire\ usage [imput] [output] .... bla bla bla.

Like I said I don't remember the correct error message :(

The phone restart and boot loop to Samsung Galaxy S5 powered by android logo :(

Manually restart again and I do wipe data/factory settings + wipe cache partition, but the same boot loop on the same logo :(

Now I have to re-flash the whole ROM using Odin PC :(

LATER EDIT:

Now I'm on Android 4.4.2 + root + knox 0x0.

I want to flash zip ROM BOD3 by Alexndr DevBase prerooted using FlashFire 0.16.

Loaded the ZIP from internal storage, I tap to the Flash, but the FlashFire remain on black screen.

I can tap to the HOME button to see the UI icons, I can load the FlashFire again, but it still remain on the black screen.

I leave it for 5 minutes or more....

I restart the phone, the same issue. I can't flash Android 5.0 over 4.4.2 :(

LATER EDIT 2:

Solved from 4.4.2 to 5.0, restoring the whole backup of 5.0 BOD3 :)

But the normal procedures enumerated above are not working anymore :(
[Paid Software Announcement and Discussion] rcatank:
EFBIG Bug or Error

Not sure if this is a bug or just plain error, but the error handling should improve.

Signature contains what device I have. The issue occurred during FULL backup on v0.16. I got the error EFBIG on /data partition backup, saying it was too big. Not sure how this can be possible when I use a 64GB microsd card with 50 gigs of space left. And yes, I did chose External target when backing up. (Edit: Partitions show its 11GiB EXTx)

Let me know if you want me to do it again and run CATLOG or something, or I dont know if there are some debug files this app outputs in the background.

My goal is to go from current 4.4.2 to 5.0 using SMG900P method posted by muniz. Just backing up before I go flash.

Also, my 2cents on coding, if partition is unable to backup, just go to the next one. The app didnt seem to do that after 45mins of watching tv, I decided to hard reboot.
[Paid Software Announcement and Discussion] 2ndcarpenter:
[MENTION=631273]Chainfire[/MENTION] still working great on the SM-G900K(S5) and SHV-E300K(S4). I use it to flash the newest 5.0.1 BOD3. I also discovered the lagging issue I had with BOB1. By default FF doesn't flash the new modem firmware included in the update package from Sammobile.com or wherever it may be retrieved from. I was still on a NL2(4.4.2) baseband and a 5.0.1 rom. Once I flashed the update again, this time deselecting everything and the selecting modem firmware only (which is a protected partition) the newest baseband was installed and now running smooth as glass. Now on LRX21T.G900KKTU1BOD3 Knox 0x0. Again thank you.
[Paid Software Announcement and Discussion] needleyepoke:
Newest version stopped working on my nexus 5... Says cannot mount device.. So I went back a version and it works again... On a good note the app has been working on my moto x first gen
[Paid Software Announcement and Discussion] Chainfire:
At risk of repeating myself ...

I don't know. They haven't been tested together, at least.

Immediately after reboot after this happens, please pull /sdcard/FlashFire/lastlog and /proc/last_kmsg. And link to your original problem report post in your new post, please.

Immediately after reboot after this happens, please pull /sdcard/FlashFire/lastlog and /proc/last_kmsg. And link to your original problem report post in your new post, please.

After each of these errors...

Immediately after reboot after this happens, please pull /sdcard/FlashFire/lastlog and /proc/last_kmsg. And link to your original problem report post in your new post, please.

Immediately after reboot after this happens, please pull /sdcard/FlashFire/lastlog and /proc/last_kmsg. And link to your original problem report post in your new post, please.

As for continuing backup/restore/flash after errors, the result is just as likely to be completely borked as when halting.

Immediately after reboot after this happens, please pull /sdcard/FlashFire/lastlog and /proc/last_kmsg. And link to your original problem report post in your new post, please.
[Paid Software Announcement and Discussion] ionutmaruta:
How can I put the log file, if my system not booting anymore ?

I must flash the 4.4.2 again, then root, then I must flash with flashfire the old backup of 5.0 BOD3 :)

The log is deleted :(

Now I'm on 5.0 BOD3 from 4.4.2 ANG2.

The problem come from the BACKUP created yesterday using LZ4 compression. When I try to restore, the phone crash and not booting anymore !

Without log I can't say anything.... :(
[Paid Software Announcement and Discussion] Chainfire:
last_kmsg will not be there, but /sdcard/FlashFire/lastlog may still be there. If you don't have a locked bootloader, you could flash TWRP and retrieve it before flashing back 4.x. If you do have a locked bootloader there may indeed not be a way to retrieve it.
[Paid Software Announcement and Discussion] ocaldini:
"We're sorry, the requested URL was not found on this server."

:crying:

I want to download it...

---------- Post added at 06:05 AM ---------- Previous post was at 06:00 AM ----------

Did it!!

:):)
[Paid Software Announcement and Discussion] scampstom:
Samsung SM-G900FD

I came from stock G900FDXXU1BOD1 (5.0 VAE) OTA-Update and have used roms from sammobile, Odin 3.09, Towelroot and Flashfire:

1. Flash with Odin of G900FDXXU1ANF6 (4.4.2 VAE)

2. Root with Towelroot + wipe

3. Installed SuperSU pro

4. Flash with Flashfire pro of G900FDXXU1BOD1 (5.0 VAE) from internal memory in 2 steps, first step flash unprotected partitions, second step flash protected partitions

I had to remove battery after both the steps to get ahead (>30 minutes stuck in bootscreen), but after all everything is fine, Knox 0x0, OTA not working (reminds on non official status), but anyway ...

THANK YOU [MENTION=631273]Chainfire[/MENTION]
[Paid Software Announcement and Discussion] wutangkillabee:
I need a lol assistance/guidance... I recently upgraded to the s8+ from my Verizon s7 sm-g930v, had 1/2 of it paid off n was able to upgrade as long as send Verizon back my s7 in good condition... Well obviously in rooted with stang5litre rom, Knox is NOT tripped and all is good except having root. Bow in a perfect world I would just Odin back to stock BUT I do NOT have access to a computer nor do I kno anyones I could use. Tried the library computers 2 no avail... What i need help with is how exactly do I flash the firmware thru Flashfire? Any prepping steps? N what needs 2 be checked or kept unchecked via flashfire...

ANY help would be greatly appreciated, as you would be saving me over $300... thanx in advance
[Paid Software Announcement and Discussion] culiacanazo:
Oooppsss... That's a coin flipping in mid air you have there. There are no special instructions other than what ff provides. However, sammy is like a woman: you never know how she'll react
[Paid Software Announcement and Discussion] Brynn217:
quick question.. any issues using this on the s8... just got my g950F and it is successfully rooted... downloading the Ice rom now, but do i need to install TWRP or will this do the job like it did before?
[Paid Software Announcement and Discussion] ianmacd:
FlashFire isn't working for me on an S8+. It hangs on 'Acquiring root". SuperSU seems never to receive the request.
[Paid Software Announcement and Discussion] Brynn217:
I got it to work.. as far as loading.. but it was only seeing the my internal memory and would not see my sd card. . So i ended up using TWRP anyway.. wasnt that difficult... i love this g950f.... i have been suffering with a g930t for a year now...
[Paid Software Announcement and Discussion] zipredictive:
Hi everyone, Nexus 5x here. I've installed a custom ROM, with TWRP supersu root, force encryption disabled.

Want a fresh install of Android O beta.

Id factory reset the phone with TWRP without deleting the files ony smartphone.

Flashfire for flashing the factory image leaving recovery intact and reboot in recovery where I'll flash the latest super su.

The result : a clean install with TWRP root and sdcard intact. Right?
[Paid Software Announcement and Discussion] Kartlis Deda:
Flash Android O Developer Preview 2?

Anyone try Android O Developer Preview 2 with FF?
[Paid Software Announcement and Discussion] mobileman88:
No, did a full wipe of everything . Let me know if it works for you.
[Paid Software Announcement and Discussion] Kartlis Deda:
Android O Developer Preview 2

Unencrypt OTA is ok on Nexus 5x.

But I don't flash it since I have no idea if root is support by Android O Developer Preview 2.

Whatever awsome application!
[Paid Software Announcement and Discussion] firegoblin:
Worked for me. I even rooted using su sr4
[Paid Software Announcement and Discussion] Kartlis Deda:
Did the play store shows "uncertified"?
[Paid Software Announcement and Discussion] Ch3vr0n:
uncertified won't stop you from flashing the SU zip
[Paid Software Announcement and Discussion] Alxoom33:
I tried rooting with SR4, bootlooped on PixelC. What device are you using?
[Paid Software Announcement and Discussion] firegoblin:
Nexus 6p. It rebooted a few times did be on initial boot. But finally booted up
[Paid Software Announcement and Discussion] mobileman88:
Did you flash it without wipe?
[Paid Software Announcement and Discussion] firegoblin:
Nexus 6p. It rebooted a few times did be on initial boot. But finally booted up

---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------

I was on pure Nexus. I did a full wipe to stock deodexed. Flashed the OTA through flashfire. I didn't change any settings within the app
[Paid Software Announcement and Discussion] nyr2k2:
Log dump: https://pastebin.com/erXjSTGh

Last night I ran a full backup and it died halfway through system partition. Now I can't even get that far. It runs for a few seconds then I get a reboot.

I'm on a Verizon S7 Edge, rooted 6.0.1 stock.
[Paid Software Announcement and Discussion] mash4077fan:
I am on Sprint N5 with MM and root and I was wondering if anyone has tried to update to Nougat and keep root using flashfire
[Paid Software Announcement and Discussion] ktmom:
I'm using an N6. I was unwilling to FF the update to Nougat because the bootloader gets updated and I was more comfortable updating the bootloader via adb. The beauty of the Nexus devices is that is as simple as flashing the supersu (I'd use plain 2.79) zip to re-root.
[Paid Software Announcement and Discussion] TowerPartySpot:
Nexus 6p Bug

Got a bit of an issue here. Flashed the developer preview 2 for android o rooted but it seemed very buggy. So i tried to downgrade but it doesn't seem to work

Flashfire doesn't allow it..

Any tips? I tried with fastboot and it bricked my phone.. Don't want to factory reset tho
[Paid Software Announcement and Discussion] jcmm11:
Just restore the backup you took before flashing the developer preview. You did take a backup, right?

Otherwise how did you try to downgrade? Wipe data & system, install new system using factory image should work every time.
[Paid Software Announcement and Discussion] [Lemmy]:
SM-T719 running nougat: tried to flash suhide with flashfire, device is bricked

Hi,

i tried to use flashfire to flash suhide (everrot enabled). Screen turned black, device has been dead now. Can't even switch it on or to recovery or download mode.

Any tips/suggestions?

Cheers

[L]
[Paid Software Announcement and Discussion] KaMyKaSii:
What device and firmware?
[Paid Software Announcement and Discussion] [Lemmy]:
Samsung SM-T719, Latest official 7.0.1 from samsung, TWRP 3.1.1, SuperSU.
[Paid Software Announcement and Discussion] culiacanazo:
You're supposed to be able to keep root, that's the original sales pitch of FF! Just follow instructions and/or search-research.
[Paid Software Announcement and Discussion] Adi!@#:
Hello. I have a Redmi Note 3 Pro with SnapDragon 650 on it and it's running MIUI global beta ROM. Will flashfire work on it without any issues ?
[Paid Software Announcement and Discussion] skiely666:
Did you flash the bootloader? Did everoot fail on the flash & then you flashed sr4 afterwards??

Thanks
[Paid Software Announcement and Discussion] firegoblin:
I'm not sure, honestly. I know I just flashed susr4
[Paid Software Announcement and Discussion] skiely666:
Does anyone know if I have to flash the bootloader in the O 19 full firmware image? I'm on may 7.1.2 stock 6P & the bootloader is 03.68 but on O 19 the bootloader is 03.69 is it safe? Just got this rma'd refurbished 6P after the BLOD & I don't want to take too much chances ;)

What I mean is is it safe to flash the bootloader in FF?

Thanks
[Paid Software Announcement and Discussion] ktmom:
In Chainfire's own words
[Paid Software Announcement and Discussion] skiely666:
Yeah I've read that, was just hoping someone might have done & succeeded. I guess I'll go to my pc then..
[Paid Software Announcement and Discussion] Wman337:
Does not play nice with O

I can't for the life of me get FF to update the Android O beta. I'm not too upset about it, but if there is a reason or a fix I'd be interested.
[Paid Software Announcement and Discussion] firegoblin:
If I remember correctly I broke down the factory image and flashed everything. Then reflashed TWRP, then superSU
[Paid Software Announcement and Discussion] skiely666:
Yeah thanks man, I was trying to do it through FF but there's different bootloader's in the May update & O 19 & I don't know if you can mix & match..
[Paid Software Announcement and Discussion] firegoblin:
No worries. I was able to flash the 17th O beta through FF. But wasn't able to go from the 17th to 19th with FF.
[Paid Software Announcement and Discussion] skiely666:
Good to know, yeah I flashed DP1 O with FF wasn't thinking about bootloader's then until May update..
[Paid Software Announcement and Discussion] Alxoom33:
You should use and or [MENTION=3110798]WugFresh[/MENTION] NRT
[Paid Software Announcement and Discussion] smartypantsphone:
Thanks

Did you follow the steps in the link exactly? The link to the Knox Removal Script dead, did you use it?

Also have you updated to latest firmware I9505XXUHQC1, and root stays and knox still 0x0?
[Paid Software Announcement and Discussion] tempest22:
Can anyone help a noob out? I wanted to upgrade to Marshmellow from 4.4.2 (finally), couldn't do it through OTA since I was rooted, so I found FlashFire, downloaded a firmware for 6.0.1 for my model and country, flashed it with FlashFire, everything worked (went through the status screen etc), booted once into a full logo display, then something saying "optimizing files", so I thought it was almost done, then it goes dark again and up comes the Samsung logo screen flashing bright to dark slowly, nothing else, and I've been stuck on that for 1 hour. Is this normal? What happened, and how can I fix it? I appreciate any help because I have no idea what this is.
[Paid Software Announcement and Discussion] KaMyKaSii:
What is your device? What exactly did you install through FlashFire? If you have not wiped data, it is most likely that there has been some mismatch between the system updated and data outdated. In that case you should go to TWRP (you have a custom recovery, right?) and wipe data. But before you try this, answer my questions
[Paid Software Announcement and Discussion] tempest22:
Galaxy S5 SM-G900F

I installed a stock firmware for 6.0.1 with FlashFire that I downloaded from updato.com for my device and country. I was still on 4.4.2 and never updated. I don't think I wiped data, should I have? What is TWRP? I don't know what custom recovery is. My phone is now dead, ran out of battery stuck on the Samsung logo screen.
[Paid Software Announcement and Discussion] KaMyKaSii:
But which partitions did you select to install? And yes, for such a huge leap from Android versions, you should definitely wipe data. TWRP is the most famous custom recovery. You who have root should at least have heard of it. Please search for it on Google and how to install it on your Galaxy S5 SM-G900F
[Paid Software Announcement and Discussion] tempest22:
I didn't select any additional partitions besides the standard ones already selected when I started to flash the firmware, so boot, recovery, system, cache & preload. I'll get TWRP once I figure out what to do, because obviously something wrong happened, and I don't know what the first thing is I need to do to undo any damage or safely start my phone again. Is this a soft brick?
[Paid Software Announcement and Discussion] KaMyKaSii:
I believe that for a large jump of Android versions would require a new bootloader, but let's forget about this for a moment. Does the device hang on the logo (probably Samsung's static image) or bootanimation (a dynamic animation)? What S5 model exactly? If it's LTE-A, follow the steps in the link below:

https://twrp.me/devices/samsunggalaxys5ltea.html
[Paid Software Announcement and Discussion] tempest22:
It was for over an hour on just the "Samsung" letters logo, which was flashing slowly from bright to dark, over and over again. I don't know how much more exact my model gets beyond Galaxy S5 SM-G900F? Phone is completely dead now, being charged.
[Paid Software Announcement and Discussion] KaMyKaSii:
Ok, I think your device is the one below. Follow the tutorial to install TWRP through Odin. Do you remember which partitions you didn't mark or were grayed out in FlashFire? Even if it is not the main factor to hang on logo, you should definitely make a wipe data. I'm going now, I'm very sleepy. When I wake up, I'll help you with what I can. Good luck.

https://twrp.me/devices/samsunggalaxys5qualcomm.html
[Paid Software Announcement and Discussion] tempest22:
Thank you man, I'll try that, but before I do I want to make sure if the following method is easier for me, so if someone else can chip in and tell me if this is safe to do I'd appreciate it so much:

Boot the phone into recovery mode by holding down Volume Up, Power and Home. In recovery mode, select Wipe data / factory reset and Wipe cache partition, then reboot.

This allegedly could fix my issue of an endless Samsung boot logo. Can anyone tell me if this is a fix?
[Paid Software Announcement and Discussion] dtriguero:
To wipe /data yes but to find why bootloop no especially if it isn't /data related. Also regardless you should still install TWRP its a custom recovery offering same things as stock recovery plus many more main thing being able to creat a full backup and restore incase something like this happens. It will also give you the ability to flash custom ROMs and mods.
[Paid Software Announcement and Discussion] tobbbie:
Sony partitions - what is TrustZone?

Hi all - recently I lost my LP Z3c due to bootloop in the failed update of super SU. Basically in effect I had to reload the device - now with MM. In the scope trying to recover my LP data (which failed) I also unlocked the BootLoader (and re-locked) - both with flashtool (not EMMA). I have not loaded any other kernel or recovery but the Sony Service Menu (Servie Tests -> Security) tells me that (DRM?)-keys are lost [Unkown Error] for the top 3 items (MARLIN, CKB and WIDEVINE). The 6 following items in the list report [Key OK].

I attribute the loss to the (unnecessary) BL unlock.

Since earlier I succeeded to not need an unlocked BL (flashing SU with FlashFire) - I now wonder if any earlier backup taken with FlashFire would have these keys saved in any of the partitions of a Full Backup. Information about the storage of these keys is a bit vague: Usually the saying is that they are stored in a "TA Partition" but elsewhere this is called "Trim Area" - suggesting some memory space outside a regular partition.

My hope is on the "TrustZone" partition - any comments on that?
[Paid Software Announcement and Discussion] ktmom:
I hope I don't come off as trying to push you away. I'm interested in your getting effective help since that situation was/is frustrating. But you will be much better off getting advice in the device forum. I think this thread is a starting place. At least all of the readers of that thread will know what you're facing.
[Paid Software Announcement and Discussion] kelex2014:
Ok so i have a galaxy s4, the prepaid variant and flash fire isnt working. The baseband is I545PPVRUAOH7. I try flashing, it shows the list of what its going through then just blacks out with the LED flashing and stays like that. Don't know what happens after but the most I've left it was for about half an hour.
[Paid Software Announcement and Discussion] G@mzy:
i have a galaxy s2 gt-i9100, i installed it and it is remaining on "detecting manufacturer and brand" . im using cm13 nightly builds.
[Paid Software Announcement and Discussion] ianmacd:
Can anyone tell me what format FlashFire uses for its back-ups of /data? I believe it's not a block-level back-up, but I'm not sure.
[Paid Software Announcement and Discussion] ktmom:
It's described in Chainfire's documentation
[Paid Software Announcement and Discussion] ianmacd:
I actually looked there prior to posting, but somehow failed to notice the section called Backup format. Please excuse the unnecessary question.

And thank you for your detailed answer. It's great news that FlashFire uses something that the standard tools can work with.

After a disastrous experience this weekend trying to restore a back-up of /data made with TWRP, I need something more reliable. I've actually made many FlashFire back-ups in the past, but never had to restore one. My disaster with TWRP highlighted the need to be able to examine and extract the contents of back-up files when the back-up tool itself fails to function as expected.

Thanks again.
[Paid Software Announcement and Discussion] jcmm11:
For future reference you can examine and extracted TWRP backups as well. They're actually tar.gz files. Just rename them accordingly.
[Paid Software Announcement and Discussion] ianmacd:
Well, that's part of the TWRP disaster I referred to. My back-up of /data failed to restore, and when I investigated the tar files, they turned out to be problematic, to say the least. I managed to save some data from them, but I still had to reinstall the phone from scratch.

The creation of said back-up completed without any errors whatsoever, which I find very alarming. Back-ups need to be flawless, but it wasn't until I came to do the restore that I discovered the serious problems with the files.
[Paid Software Announcement and Discussion] jcmm11:
Official version? Latest version? I know in the past some versions had problems but they tend to be fixed quickly when they're serious like this. What was wrong with the backups?