Database Users

[Q] FlashFire for backup Purposes

Good Morning All,
I did a search for this but didn't come up with anything specific so apologies in advance if it does exist somewhere. After a long time owning an S7 under Verizon service I finally took the plunge and Rooted him. Works Beautifully so Hat off to the Warriors. I see that Flashfire can Perform backups and restores without having to utilize a custom recovery.
My Question is has anyone tested Backing up and restoring on a Verizon S7? If so can you provide Experiences, results, what paritions/items listed in flashfire backup was performed on, Workarounds if needed and of course Failures. If it is more advantageous to flash a custom recovery instead of using flashfire. Which one is preferable i/e TWRP/Clockwork Mod. Please excuse me as the last time I had rooted and romed an android fully was my Moto Droid. (LOCKED BOOT LOADER ON THAT ONE "Safe Strap used" )
Just to be clear again this is for my Rooted Verizon Galaxy S7 Debloted and Lag fix applied.
Gratsi me Android Familia.

FlashFire is the ONLY recovery that can be used other than stock, but not as a replacement to the stock recovery. The backup and restore feature is amazing on the S7, but you need to have it installed/operating first. I mean that if you do a backup and wipe the phone, you will need to re-root and install FlashFire before being able to restore.

CVertigo1 said:
FlashFire is the ONLY recovery that can be used other than stock, but not as a replacement to the stock recovery. The backup and restore feature is amazing on the S7, but you need to have it installed/operating first. I mean that if you do a backup and wipe the phone, you will need to re-root and install FlashFire before being able to restore.
Click to expand...
Click to collapse
That makes sense. Really so Clockwork and TWRP cannot be used? Prob because the bootloader is still locked right? Like I said is been a minute since I've been through the entire Process.
If flash fire is the only viable method other than stock, obviously that will be my Choice I may try the Stock too.
Additional Question about items to backup. The items/partitions marked below that are marked protected. will the restore perform without errors since they are marked as protected? Or are there specific Items only that should be backed up besides system and data?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I just use normal and have restored with no problems.

I was curious about this as well... Thanks for answering.

ok i see some of you are using the backup restore feature in flashfire but when i do a normal backup i deselect internal storage but the problem is that it keeps repeating over and over again listing the partitions see screenshot i know my explanation isnt very clear so is this normal or am i doing somethinv wrong. and this is on a rooted galaxy s7 verizon on nougat firmware
Edit: restarted phone and it works now

S7 Edge (Sprint) stuck in boot loop after attempting to root using Odin

Welp, I'm pretty sure I messed this up. Found a YouTube video (not even sure which one at this point, sorry) that was recently uploaded detailing how to root a Galaxy S7 Edge. Downloaded the firmware, opened up Odin, put it into Download mode, selected the Qualcomm firmware version for the AP field, and click start. It flashed correctly (according to Odin) and the phone began restarting and didn't stop. Just show's the "Galaxy S7 Edge" screen, goes black, and starts over.
I tried downloading the stock firmware for Sprint, load the appropriate files into Odin, and click start, I then get this output:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And on the phone, I see:
My build number is NRD90M.G935PVPS5BRA1, kernel version 3.18.31-12623509
I'm fairly certain this is entirely something that could have been avoided had I read more guides or instructions. Unfortunately, here I am! I really appreciate any help anyone can give me. I've been Googling and reading all morning, and I'm sure the answer is there, but I'll be damned if I can see it.

While I don't think there's much important info here, I figure it's at least showing some more in terms of version and name:

Your binary boot is v5. It won't work and you can't downgrade at the moment. What are you trying to do with root? There are many non root alternatives. To fix your bootloops, odin the stock firmware again.
Make sure you have the special version of odin too.
Also, download the stock firmware again. Try updato.com or plug the firmware version into android file host

lvpre said:
plug the firmware version into android file host
Click to expand...
Click to collapse
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.

reddeth said:
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.
Click to expand...
Click to collapse
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.

lvpre said:
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.
Click to expand...
Click to collapse
Mainly I was just wanting to get rid of the stock Sprint bloatware that you can't uninstall by default. If you've got any other suggestions for it, they're very much appreciated!

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.

Galaxy J5 (2017) stuck in recovrey mode.

Hi. During the update to Android 10 the phone turned off and after switching on it goes into recovery mode.
The phone is not mine and this description was provided to me by the owner of the phone. I was unable to see the phone directly because of the quarantine, so as a first solution I thought about a restore via odin. Has anyone had this problem? And is there a less drastic way than Odin to solve? Because the owner has some data that he would prefer not to lose.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.

You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?

I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.

myusernamesucks said:
I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.
Click to expand...
Click to collapse
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...

Emelin.2004 said:
How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.
Click to expand...
Click to collapse
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
garylawwd said:
You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?
Click to expand...
Click to collapse
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.

TheNightmare97 said:
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.
Click to expand...
Click to collapse
Put the j5ylte update onto sd card.
Get the update from updato or sammobile or somewhere.
Then reboot stock recovery and apply update from sd card. Or sideload it using adb on a computer. Not very complicated at all

Install the stock rom like i described here: https://forum.xda-developers.com/galaxy-j5/help/to-stock-rom-t4099857

jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
I cant even access download mode neither can I apply an update from SD card. It says dm-verity failed. System is completely stock. I didn't modify anything.

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin