Database Users

nand restore wont boot

long story short i had to restore from my nand backup. But the phone stays stuck at the black samsung screen. It makes the startup chime sound but doesnt load. What could the problem be? I really need this backup. For some reason not even mybackup pro backed up like it should have because when i restored it restored an old back up.
{
"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"
}

Why is this on this section? Please post in q and a.
Sent from my Evo Killer!!!

FIx
Here is what you do. Go back into clockwork and flash a different nandroid or the same one again. if non of your nandroid works. you will have to odin and then reroot and whatever.

What are you developing?

most likely this means you made a nandroid backup from an RFS rom and you are using EXT4 or vice versa. my suggestion is to do a nandroid restore, then flash the ext4/rfs dual kernel. see if that boots you. if not, nandroid, oneclick root/nand unlock and restore. if that doesnt work, you are officially boned. i suggest using titanium backup in the future. nand backups are nice, but i have had way too many problems with Clockwork recovery's restore. either not working or not restoring properly.

You most likely have the wrong kernel for your ROM. If the poster above me is correct, go find a dual-support kernel and flash that. Most versions of CWM Recovery right now don't back-up the kernel block for some reason.
If you can, go find the ROM you're trying to restore from, pull the kernel out of the zip, and make your own update.zip for the kernel. Should clear your problem right up.

nandroid does not restore the kernel on our phone (maybe others, too?). Flash a kernel after your restore.
The way I usually restore now is to flash the rom that the backup came from, then advanced restore->restore data to get my apps and settings back.

DiGi760 said:
The way I usually restore now is to flash the rom that the backup came from, then advanced restore->restore data to get my apps and settings back.
Click to expand...
Click to collapse
+1 to that.
Jared

not developing . just trying to over clock and find a rom i like.

i nand backupd on stock rooted. and im trying to restore on stock rooted.. stock rom and kernel

?
i tried an older nand backup and it restored. but thats not the one i need. im going to the the one i need again and see what happends. So how do you know if your properly nandbackuped? i guess you dont?

I think the problem is with CWM3...
Sent from my SPH-D700 using XDA App

?
what is cmw3?

It worked! I got my old backup restored!!!

[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

Android system failed to load.. Please Help!

My device is rooted. I m use substratum in my device.. I m using a theme in substratum for 2 week ago but today I try to install & apply a new one but once I did that my device itself restart & Showing me a message " Android system load failed.. Your Data maybe corrupted , Please do a reset factory " but I want to back my device without loosing my data... What can I do. Please anyone help me..
{
"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"
}

shafayetsabbir3 said:
my device is rooted. I m use substratum in my device.. I m using a theme in substratum for 2 week ago but today I try to install & apply a new one but once I did that my device itself restart & Showing me a message " Android system load failed.. Your Data maybe corrupted , Please do a reset factory " but I want to back my device without loosing my data... What can I do. Please anyone help me..
Click to expand...
Click to collapse
take a backup with twrp recovery and clear data

[email protected] said:
take a backup with twrp recovery and clear data
Click to expand...
Click to collapse
are u sure it will work?

shafayetsabbir3 said:
are u sure it will work?
Click to expand...
Click to collapse
yes boot in fastboot and boot twrp recovery and connect with pc you able to access your data you can take backup from pc and twrp as well

[email protected] said:
yes boot in fastboot and boot twrp recovery and connect with pc you able to access your data you can take backup from pc and twrp as well
Click to expand...
Click to collapse
Bro I want full backup like app, software everything as it was before

shafayetsabbir3 said:
Bro I want full backup like app, software everything as it was before
Click to expand...
Click to collapse
Then try to uninstall magisk with twrp then any application not able to modify your system and for boot successfully just download magisk uninstaller from XDA sorry for my bad english

This message showed up on my phone after my Xiaomi tried to connect to my sim cards. one of my sim was corrupted. after i took it out my phone worked normally

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.

Hard reset password not working

I was going to clear my cache this morning but my password at the unlock screen after restarting would not work. It's the same as your screen unlock, right? I had to reset my phone and reload everything. Any ideas why it wouldn't take my password? I know it was the correct one.
Sent from my ONEPLUS A6013 using Tapatalk

These phones don't have a cache partition, so clearing the cache in recovery wouldn't do anything.
In recovery if your lockscreen password does not decrypt your data, you have the wrong recovery installed or it's not up to date. Either way don't clear cache in recovery like you would on devices that have a separate cache partition.

OhioYJ said:
These phones don't have a cache partition, so clearing the cache in recovery wouldn't do anything.
In recovery if your lockscreen password does not decrypt your data, you have the wrong recovery installed or it's not up to date. Either way don't clear cache in recovery like you would on devices that have a separate cache partition.
Click to expand...
Click to collapse
Any time I install a local update, the instructions say to wipe cache. Why is that?
Sent from my ONEPLUS A6013 using Tapatalk

mabryan7 said:
Any time I install a local update, the instructions say to wipe cache. Why is that?
Click to expand...
Click to collapse
These instructions don't mention that, for any method.

OhioYJ said:
These instructions don't mention that, for any method.
Click to expand...
Click to collapse
What about this?
{
"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"
}
Sent from my ONEPLUS A6013 using Tapatalk

mabryan7 said:
What about this?
Click to expand...
Click to collapse
I'll have to eat crow on that one... you are correct. If Funk Wizard says to do it, it should be safe.
I've avoided because I've had odd results, and read not to do it. Doesn't take much to upset these phones.
So I guess then its a question of your exact setup to determine what went wrong. Since you are doing the local update, are you all stock, recovery and all?

OhioYJ said:
I'll have to eat crow on that one... you are correct. If Funk Wizard says to do it, it should be safe.
I've avoided because I've had odd results, and read not to do it. Doesn't take much to upset these phones.
So I guess then its a question of your exact setup to determine what went wrong. Since you are doing the local update, are you all stock, recovery and all?
Click to expand...
Click to collapse
No problem. Just wanted to make sure I wasn't missing something. I am all stock on the international variant. Recently installed Tasker and have been playing with that. Also installed Microsoft Intune for access to work emails. Those 2 things are only changes I can think of that could affect my phone unlocking.
Sent from my ONEPLUS A6013 using Tapatalk