Database Develop

Help with nandroid restore

I rooted someone's phone earlier and first tried to flash AmonRA 1.5.2. It wouldn't load into recovery, so I flashed 1.2.3. That one worked, but wanted a newer one, so I went with God Speed. I made a backup and then flashed a 2.1 ROM. I was then showing him how to do a nandroid backup and restore and it wouldn't restore. I made another backup of the new ROM and tried to restore it. Still wouldn't restore. I then flashed AmonRA 1.6.2 and tried the same thing. Still would not restore. Everything works fine on my phone and they are both w/Google phones. I also copied his sdcard to my computer and reformatted his sdcard. Still would not work. Any ideas or suggestions.

'Wouldn't restore' is kind of vague. Did it appear to restore but not? Did the restore fail, and if so, what message came up?

try to rename the nandroid and make sure you phone is plugged into the wall or pc when restoring.

fixxxer2008 said:
try to rename the nandroid and make sure you phone is plugged into the wall or pc when restoring.
Click to expand...
Click to collapse
He'll only need to rename it if he already renamed it and put spaces in it. Plugging it into the wall won't make a difference unless the screen is shutting down due to power issues during the restore.
Two reasons why I asked for further clarification on what happens during a restore attempt.

smw6180 said:
He'll only need to rename it if he already renamed it and put spaces in it. Plugging it into the wall won't make a difference unless the screen is shutting down due to power issues during the restore.
Two reasons why I asked for further clarification on what happens during a restore attempt.
Click to expand...
Click to collapse
i dunno but that always worked for me. i had a message that said restore via adb.

fixxxer2008 said:
i dunno but that always worked for me. i had a message that said restore via adb.
Click to expand...
Click to collapse
restore via adb always happens when a nandroid has been renamed and has a space in it. I'm not saying that's the ONLY reason, but it's the only time I've ever seen or heard of it.

let me look at the copies on my computer.
The error I get is to do it via adb. But I didn't rename it or anything. All I did was
1. Flash the recovery
2. Reboot into recovery
3. Perform Nandroid Backup (just the basic nand backup)
4. Installed DC2.07 as that was what I had on my computer
5. Rebooted and let it load
6. Rebooted into recovery
7. tried to restore and I get the error about performing it via adb
Tried the same routine everytime I flashed a new recovery
Edit:Just checked the nandroid backups---There are no spaces

&RoidRage said:
let me look at the copies on my computer.
The error I get is to do it via adb. But I didn't rename it or anything. All I did was
1. Flash the recovery
2. Reboot into recovery
3. Perform Nandroid Backup (just the basic nand backup)
4. Installed DC2.07 as that was what I had on my computer
5. Rebooted and let it load
6. Rebooted into recovery
7. tried to restore and I get the error about performing it via adb
Tried the same routine everytime I flashed a new recovery
Edit:Just checked the nandroid backups---There are no spaces
Click to expand...
Click to collapse
Interesting. Then I'd try what fixxer said and plug it into the wall before trying the restore.

I will try that tomorrow

sandboxlove said:
hi there
i actually had the same problem today but then i learned (through a search...woah!!) that there is an newer ra, and after an update it worked like a beaut. perhaps your recovery is outdated...or maybe the nandroid is corrupted?
good luck!
Click to expand...
Click to collapse
I'm pretty sure 1.6.2 is the newest which is what is on there now. I've read of other peoples problems and solutions and tried what i rememebered, but it happened with every one I tried.

&RoidRage said:
I'm pretty sure 1.6.2 is the newest which is what is on there now. I've read of other peoples problems and solutions and tried what i rememebered, but it happened with every one I tried.
Click to expand...
Click to collapse
You're not on an ext4 filesystem are you? If so, you'll want godspeed (toast's version of the 1.6.2 recovery image). I believe it handles ext4 restores whereas the original 1.6.2 doesn't (if I remember correctly).

smw6180 said:
You're not on an ext4 filesystem are you? If so, you'll want godspeed (toast's version of the 1.6.2 recovery image). I believe it handles ext4 restores whereas the original 1.6.2 doesn't (if I remember correctly).
Click to expand...
Click to collapse
No, I did partition it to see if that would help, but only converted it to ext3. But I did not try nand+ext. I had him register with the site and will direct him to this thread.

Nandroid Restore
Yeah, i'm the one having this problem. I'm new to modding phones and not for sure what to do. &RoidRage is trying to help me out, if anyone else can that's figure it out that would be great.

Anytime I received the the "via adb" error, it was due to their not being enough memory on the sd card. I found you typically will need a little over 1 GB on the card remaining to do anything: Restore, or backup.
Hope that helps.

And make sure your battery is charged.

Nandroid recovery problem - MD5 mismatch/Error restoring boot image

I accidentally did a factory reset while in Safe mode. My first time ever getting into Safe mode and I have no idea how I got in there, only realized after the wipe. Thus, I lost all my pictures, videos etc... I made a Nandroid backup before the wipe so that got deleted as well. I have another Nandroid backup on my SD card that I have been trying to copy to the phone's internal memory but I keep getting errors.
First error on CWM was the annoying MD5 mismatch - I think I was able to fix that with the terminal emulator and the Notepad++ and MD5 calculator. Then the next error was, 'error restoring boot image.' I made this Nandroid backup with Semaphore 2.7.4 and still is my kernel now.
I believe this Nandroid recovery is corrupted. Is there any chance of recovering it? I've tried PhotoRec and Recuva already and they didn't work for me. PhotoRec gave me weird filenames and Recuva didn't find the stuff I was looking for. I still have this untouched backup on my SD and everything else on the SD works by the way.

Zytorious said:
I believe this Nandroid recovery is corrupted. Is there any chance of recovering it?
Click to expand...
Click to collapse
Have you tried to flash your semaphore kernel + recovery via Odin/Heimdall, so you have a clean recovery?
Cheers
EDIT: If this isn't working for you, you are always able to flash a stock samsung rom and then get back to your current rom + recovery.
If this does not work, i would guess your backup is corrupted. Had this by myself in the past... corrupted backups

[Q] Note 3 AT&T Safestrap Partition Troubles

Hi everybody! I recently installed safestrap 3.72 and installed a couple KitKat roms, everything worked great until I tried to install AzureRom it said E: Unable to mount ' /system'. After that it can no longer mount the system partition... I've tried multiple things and I can't find anything that will work including wiping, formatting, and fix permissions. I also cant flash any roms because of this. I figured out how to use ROM-Slot-1 and able to boot SlimNote but it is very, very buggy and I have zero memory whats so ever. I tried to uninstall Safestrap through the apk but it did nothing. Please help and give me any ideas!!! Thank you so much for all your help!!

antnyhills said:
Hi everybody! I recently installed safestrap 3.72 and installed a couple KitKat roms, everything worked great until I tried to install AzureRom it said E: Unable to mount ' /system'. After that it can no longer mount the system partition... I've tried multiple things and I can't find anything that will work including wiping, formatting, and fix permissions. I also cant flash any roms because of this. I figured out how to use ROM-Slot-1 and able to boot SlimNote but it is very, very buggy and I have zero memory whats so ever. I tried to uninstall Safestrap through the apk but it did nothing. Please help and give me any ideas!!! Thank you so much for all your help!!
Click to expand...
Click to collapse
Because azurerom is 4.3 and you are on 4.4. Boot to slimnote on your slot and try to load up a 4.4 rom on your sd or internal memory. Boot to ss then go to stock slot and advanced wipe and wipe everything EXCEPT sd card then flash the 4.4 rom you loaded.

Last time I checked I wasn't able to flash roms, even after wiping but I'll try it. Thank you

antnyhills said:
Last time I checked I wasn't able to flash roms, even after wiping but I'll try it. Thank you
Click to expand...
Click to collapse
Hope you get it figured out, if anything you can restore to mj5 and start out fresh.

posersk8r said:
Hope you get it figured out, if anything you can restore to mj5 and start out fresh.
Click to expand...
Click to collapse
How can I do that? Odin?

http://forum.xda-developers.com/showthread.php?t=2559715

Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?

mrmead2 said:
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
Click to expand...
Click to collapse
Are you on jb? Kk? What rom you trying to flash?

i Have no rom installed now...I was running Dynamic Kat 3.0
I have safestrap 3.72...
was trying to install URDroid

mrmead2 said:
i Have no rom installed now...I was running Dynamic Kat 3.0
I have safestrap 3.72...
was trying to install URDroid
Click to expand...
Click to collapse
That's weird, never had that mounting error before. If you can boot to ss 3.72 try doing a full wipe EXCEPT sd or ex sd. If you still have urdroid saved or kk backup try to flash or restore for kk backup. If it still doesn't work, read 4 posts up.

mrmead2 said:
Im Having the same issue I cant install ANY rom they all say
E:unable to mount '/system
E:unable to mount '/systemorig
Please help!?!?
Click to expand...
Click to collapse
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.

If nothing else works, go back to MJ5 (link on page 1).
If that fails, bring the phone to an AT&T Device Support Center. What will most likely happen is that they'll try to reflash it, fail and replace the phone. (If evilpotatoman's MJ5 restore fails, it's usually a bad motherboard.)

isharted said:
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
Click to expand...
Click to collapse
I have the same problem! I achieved root yesterday (finally) and tried to install the Firenote rom. It wouldn't take, so I restored my backup to try again. But when I tried again, it wouldn't mount E:. It wouldn't even allow me to restore backup. It failed to mount every time in stock slot. Eventually, it wouldn't even let me create a slot at all!
Out of desperation, I entered recovery and wiped data, and when I booted into safestrap again, I was able to create a slot, where I installed Alliance KK to have a functioning phone. Wifi works, although it's buggy (wifi doesn't work on Dynamic 3.2). So I'm stuck.
I tried downloading safestrap again and uninstalling/installing it, hoping that would work, but it didn't. The only thing I can think of that I did wrong was that I took the micro SD card out a few times while in safestrap without properly ejecting it, but I'm not sure if that had anything to do with it.

CPT Crunch said:
I have the same problem! I achieved root yesterday (finally) and tried to install the Firenote rom. It wouldn't take, so I restored my backup to try again. But when I tried again, it wouldn't mount E:. It wouldn't even allow me to restore backup. It failed to mount every time in stock slot. Eventually, it wouldn't even let me create a slot at all!
Out of desperation, I entered recovery and wiped data, and when I booted into safestrap again, I was able to create a slot, where I installed Alliance KK to have a functioning phone. Wifi works, although it's buggy (wifi doesn't work on Dynamic 3.2). So I'm stuck.
I tried downloading safestrap again and uninstalling/installing it, hoping that would work, but it didn't. The only thing I can think of that I did wrong was that I took the micro SD card out a few times while in safestrap without properly ejecting it, but I'm not sure if that had anything to do with it.
Click to expand...
Click to collapse
Yo fire rom is mj5, read up before you go flash happy. You can't go back to 4.3 once you are on 4.4 with the 4.4 bootloader...
Sent from my SM-N900A using XDA Free mobile app

tylerholbrook said:
Yo fire rom is mj5, read up before you go flash happy. You can't go back to 4.3 once you are on 4.4 with the 4.4 bootloader...
Sent from my SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Doh! Sorry! That explains a lot.Would that have screwed up my stock slot in safestrap?

isharted said:
i have this issue on my stock slot in safestrap. i don't think it's even able to wipe /system. for some reason, it can't touch /system at all.
i'm googling around and came across this thread. i'll post again if i am able to find a resolution.
Click to expand...
Click to collapse
I had this same problem until yesterday, I followed the instructions found here . I was able to restore my phone back to KK goodness, root, install busybox and safestrap, then flash a rom to my (previously untouchable) root slot. It worked perfectly

[Q] AT&T Note 3 4.4.2 unable to mount system

I have a new n900a with stock 4.4.2. I rooted the phone with the TowelRoot and then installed SS 4.72. I backed up my phone with a nondroid backup via SS, titanium backup as well as Helium all on my external SD . The problem is that I tried to flash the Alliance ROM v6 and it didnt work. So I said, hey I've got a full backup lets just restore to the stock ROM and no foul. Well it happens that it FAILED and I noticed that SS cant mount the system partition.
From what I have read, the stock system file for AT&T is not available so I cant flash a stock rom back on my phone. I think that somehow the phone got corrupted. I tried wiping, format data, delvic cache, data, etc. via SS 3.72, nothing works. SS shows the system partition empty. I suspect this may have happened because the ROM I was flashing was based on using SS 3.71. The developer said I should not have a problem flashing the ROM with SS 3.72. I've been flashing roms for a couple of years but have never come across this and am totally stumped. Can anyone point me in the right direction or do I have an $800 brick?

ccaceres said:
I have a new n900a with stock 4.4.2. I rooted the phone with the TowelRoot and then installed SS 4.72. I backed up my phone with a nondroid backup via SS, titanium backup as well as Helium all on my external SD . The problem is that I tried to flash the Alliance ROM v6 and it didnt work. So I said, hey I've got a full backup lets just restore to the stock ROM and no foul. Well it happens that it FAILED and I noticed that SS cant mount the system partition.
From what I have read, the stock system file for AT&T is not available so I cant flash a stock rom back on my phone. I think that somehow the phone got corrupted. I tried wiping, format data, delvic cache, data, etc. via SS 3.72, nothing works. SS shows the system partition empty. I suspect this may have happened because the ROM I was flashing was based on using SS 3.71. The developer said I should not have a problem flashing the ROM with SS 3.72. I've been flashing roms for a couple of years but have never come across this and am totally stumped. Can anyone point me in the right direction or do I have an $800 brick?
Click to expand...
Click to collapse
Head on over to the soft brick thread for instructions on how to undo what you did. If that fails, well, you always have the hard debrick method.

Lost Baseband und IMEI after TWRP flash - Full TWRP backup not functional - ALEXNDR

Hey guys,
hope someone can help. I had a screen crack 2 weeks ago. I was on Alexndr CSD2 DBT with TWRP. So I have a full TWRP backup. Sent it to Samsung. These smart asses reflashed my phone without any need of doing so. On arrival it was on stock with funktional LTE Sim connection.
So I checked OEM Unlock, went to download mode and flashed TWRP. Went to TWRP and formatted everything and restored ALL partitions of my backup. On reboot my PIN was not accepted anymore - this is not concerning, I am willing to reinstall all by hand. But I lost IMEI/baseband - so deleting the key files I can enter the phone but I have no DATA connection via SIM anymore.
So I reflashed stock CSD2 .... no IMEI.... so I restored EFS only .... boot loop.
I installed CSD Alexndr fresh and restored EFS only .... no IMEI
Wtf is going on? Any ideas I can fix this without sending it back and starting all over and maybe getting stuck again?
Thnx
Peter

Trying flashing the modem, that alexndrs rom utilizes, solely, in TWRP .

CynicalHeight00 said:
Trying flashing the modem, that alexndrs rom utilizes, solely, in TWRP .
Click to expand...
Click to collapse
Thank you, tried it, did not change the situation unfortunately. He says I think it was included in the rom anyway.

Hmm, if you installed the rom again to install the modem- that's not what I meant.
Alexndrs rom makes a backup of your efs; Find the post and see what you have type in twrp terminal.
Then try the modem flash, solely.
I had the same issue, but it was fixed with modem flashing; however, everytime I reinstall a rom I need to do a separate modem flash.

CynicalHeight00 said:
Hmm, if you installed the rom again to install the modem- that's not what I meant.
Alexndrs rom makes a backup of your efs; Find the post and see what you have type in twrp terminal.
Then try the modem flash, solely.
I had the same issue, but it was fixed with modem flashing; however, everytime I reinstall a rom I need to do a separate modem flash.
Click to expand...
Click to collapse
Hey thanks for your answer.
I flashed the BL...zip solely and also tried to restore EFS and baseband partition only, besides trying full stock odin flash and full TWRP restore with all partitions.
I read:
"EFS restore command (TWRP -> Advanced -> Terminal):
gunzip -c /external_sd/.backup/efs/efs_recent.img.gz | dd bs=4096 of=/dev/block/sda3"
I did, it flashed it and still the same problem. This was the SD from my S8plus. I didn't know Alexndr is overwriting EFS backup every goddamn flash. So my old EFS backup says Aug 2018 - so it is of my S8plus. And the recent one got overwritten by the few flashing attempts. So the rom did overwrite EFS backup I suspect.
So I maybe left with the TWRP backup of EFS only. Why is it not working, to restore the EFS TWRP backup - it should have all data cause it was done when the phone was running well? Is there a way to restore EFS/IMEI/Baseband from that backup? I dont understand how baseband gets lost while having full TWRP backup?

phoenX80 said:
Hey guys,
hope someone can help. I had a screen crack 2 weeks ago. I was on Alexndr CSD2 DBT with TWRP. So I have a full TWRP backup. Sent it to Samsung. These smart asses reflashed my phone without any need of doing so. On arrival it was on stock with funktional LTE Sim connection.
So I checked OEM Unlock, went to download mode and flashed TWRP. Went to TWRP and formatted everything and restored ALL partitions of my backup. On reboot my PIN was not accepted anymore - this is not concerning, I am willing to reinstall all by hand. But I lost IMEI/baseband - so deleting the key files I can enter the phone but I have no DATA connection via SIM anymore.
So I reflashed stock CSD2 .... no IMEI.... so I restored EFS only .... boot loop.
I installed CSD Alexndr fresh and restored EFS only .... no IMEI
Wtf is going on? Any ideas I can fix this without sending it back and starting all over and maybe getting stuck again?
Thnx
Peter
Click to expand...
Click to collapse
phoenX80 said:
Thank you, tried it, did not change the situation unfortunately. He says I think it was included in the rom anyway.
Click to expand...
Click to collapse
phoenX80 said:
Hey thanks for your answer.
I flashed the BL...zip solely and also tried to restore EFS and baseband partition only, besides trying full stock odin flash and full TWRP restore with all partitions.
I read:
"EFS restore command (TWRP -> Advanced -> Terminal):
gunzip -c /external_sd/.backup/efs/efs_recent.img.gz | dd bs=4096 of=/dev/block/sda3"
I did, it flashed it and still the same problem. This was the SD from my S8plus. I didn't know Alexndr is overwriting EFS backup every goddamn flash. So my old EFS backup says Aug 2018 - so it is of my S8plus. And the recent one got overwritten by the few flashing attempts. So the rom did overwrite EFS backup I suspect.
So I maybe left with the TWRP backup of EFS only. Why is it not working, to restore the EFS TWRP backup - it should have all data cause it was done when the phone was running well? Is there a way to restore EFS/IMEI/Baseband from that backup? I dont understand how baseband gets lost while having full TWRP backup?
Click to expand...
Click to collapse
It's not bl file you flash. Also, that terminal code is for recent , which , i think is a backup of efs now flashed, not the one you had prior to the flash. Meaning, check for the efs- backup. That file is hidden on your external sd card.
In theory, that's what I suppose as well but it didn't work for me either- restoring via twrp.

CynicalHeight00 said:
It's not bl file you flash. Also, that terminal code is for recent , which , i think is a backup of efs now flashed, not the one you had prior to the flash. Meaning, check for the efs- backup. That file is hidden on your external sd card.
In theory, that's what I suppose as well but it didn't work for me either- restoring via twrp.
Click to expand...
Click to collapse
Yeah, I know, I just had the file open and quoted wrong. It is
gunzip -c /external_sd/.backup/efs/efs_backup.img.gz | dd bs=4096 of=/dev/block/sda3
The command worked to restore the EFS but since it is the backup of my S8plus IMEI is still not recognized....
Initialization via SmartSwitch returned that the device is not supported...great.
So the only backup I have is TWRP. I need a way to rescue from TWRP. Since full resore ends in broken IMEI I may be screwed since a full restore should render the phone running but it is not for whatever reason. I am disappointed that the full TWRP backup doesnt seem functional to backup and restore EFS.

Is efs formatted the proper way?
I had also wiped clean everything in twrp.

CynicalHeight00 said:
Is efs formatted the proper way?
I had also wiped clean everything in twrp.
Click to expand...
Click to collapse
TWRP doesnt offer to wipe EFS separately?

phoenX80 said:
Yeah, I know, I just had the file open and quoted wrong. It is
gunzip -c /external_sd/.backup/efs/efs_backup.img.gz | dd bs=4096 of=/dev/block/sda3
The command worked to restore the EFS but since it is the backup of my S8plus IMEI is still not recognized....
Initialization via SmartSwitch returned that the device is not supported...great.
So the only backup I have is TWRP. I need a way to rescue from TWRP. Since full resore ends in broken IMEI I may be screwed since a full restore should render the phone running but it is not for whatever reason. I am disappointed that the full TWRP backup doesnt seem functional to backup and restore EFS.
Click to expand...
Click to collapse
phoenX80 said:
TWRP doesnt offer to wipe EFS separately?
Click to expand...
Click to collapse
I think it should be included under system?

I wiped all available partitions and restored again. Unfortunately still no change. No LTE no IMEI.

You have to check whether or not the format , ex. Ets4 or whatnot, is what is needed for efs to operate

Did you fix it?

No, I am stuck.
There is only a way to format System - which I did. Nothing changed.
I tried to odin flash CSD2 to have the phone update on its own to CSDE to maybe gain baseband on this update. But no luck.

phoenX80 said:
No, I am stuck.
There is only a way to format System - which I did. Nothing changed.
I tried to odin flash CSD2 to have the phone update on its own to CSDE to maybe gain baseband on this update. But no luck.
Click to expand...
Click to collapse
What's the recourse?

What do you mean?

phoenX80 said:
What do you mean?
Click to expand...
Click to collapse
What will you try to fix it?

I am out of ideas. I have to send it to Samsung I guess....

Since I know my IMEI shouldn'T it be possible to HEX edit another backup to reflash mine? I chekced that when I restore the S8s EFS the serial number actually changes but the IMEIs stay unknown. Shouldn't the IMEI of the S8 pop up?

phoenX80 said:
Since I know my IMEI shouldn'T it be possible to HEX edit another backup to reflash mine? I chekced that when I restore the S8s EFS the serial number actually changes but the IMEIs stay unknown. Shouldn't the IMEI of the S8 pop up?
Click to expand...
Click to collapse
could you figure it out to this day?