I was recently doing a restore when I realized I restored the wrong backup file with aman recovery. When I booted back into recovery and tried restoring the proper backup file I get an error saying "E: Can't mount SDCARD: /nandroid/".
What should I do to fix this?
tryptic said:
I was recently doing a restore when I realized I restored the wrong backup file with aman recovery. When I booted back into recovery and tried restoring the proper backup file I get an error saying "E: Can't mount SDCARD: /nandroid/".
What should I do to fix this?
Click to expand...
Click to collapse
format your sd on your comp. if your phone still doesnt recognize try and partition it thru amon ra.. you might need to run an ruu
Related
hi, tried flashing cm7.0.3 from vegan 5.1.1, it downloaded fine, then i backed up my rom but when it went to install it couldnt find the download, and now, i cant restore my backup because /data wont mount or format or anything... what do i need to do to fix this?
update: attempted (http://forum.xda-developers.com/showthread.php?t=861950) with successfully flashing, but now it is a constant boot loop and i cant get to recovery now help please!
update 2: using nvflash, was able to flash cwr, repartitioned internal sd, all is well (sorta, lost my backup and everything on the internal, but the tablet works now)
I have looked up this problem on both xda and google but found no Galaxy SII specific solutions.
I receive the error "Can't mount /cache/recovery" message when I enter recovery mode. The same error occurs when try to mount every other mounts and still receive the equivalent error. eg mount emmc gives "error mounting /emmc/
I am unable to flash a new rom or even mount the sd card to place a rom on.
I have rebooted the phone multiple times but to no avail. I have also tried to full wipe, cache wipe and format the internal partitions individually through the recovery but it did not work.
Clockworkmod recovery v5.0.2.3
same error occurs on cwm 4.0.1.4
No current rom
Heard people say that by removing the sd card the error is resolved... (will only work if a corrupt sd card is to blame)
Might be able to use internal though
I tried it without the sd card, still same error. Also, the sd card i used before was working on another phone with all files intact, so no corrupted sd.
I would try starting a fresh... flashing with odin etc ... can you access download mode ?
http://forum.xda-developers.com/showthread.php?t=1113928
http://forum.xda-developers.com/showthread.php?t=1075278
Yeah that version of cwm has that problem. What you can do is copy a rom to your external sdcard, take out sdcard and put in card reader copy rom and put back in phone, and install from zip and then go external sdcard and install from there. Or what you can do is use odin to flash cwm v5.5 which works just fine.
Hope this helps.
Sent from my GT-I9100 using xda premium
fixed, thanks.
I just reflashed the chainfire kernel through heimdall command script as my odin wasntt detecting my phone
I had this twise thought I was the only one believe it or not on two sgs2s in 2 weeks I fixed by flashing stock rom
try flashing new rom hope this helps
recovery.img incompatible
chestertan2003 said:
try flashing new rom hope this helps
Click to expand...
Click to collapse
Could well help. The recovery.img turned out to be incompatible with my device, giving the same errors.
- CWM 6.0.0.8
- CM9 RC2
1. boot into CWM
2. go to backup and restore
3. selected backup to internal sdcard
4.
Backing up boot image...
Backing up recovery image...
Backing up system...
Freeing space...
Done freeing space.
Error while making a back image of /system!
E:Can't open /tmp/recovery.log
E:Can't open /tmp/recovery.log
5. I tried to reboot... still booting after 15min
6. I tried to install CM9RC2.zip again.
7. go to install zip from sdcard
8. choose zip from internal sdcard
9 .No files found.
Wht dose hell going on???
I just backup my system, Why do you delete anything???
Why?
Pls help me~
THx~ ><"
Its look like corrupted nand. All you can try now is to flash custom kernel or stock rom via odin. Very strange thing.
i9.0.1.3k galaxy imperator
Hello guys,
I have a very strange problem that noone else has because i cant find anything about it on the net.
I have a Galaxy s3 with cyanogenmod 10.2 and boeffla 2.1 stabe using twrp as recovery. I´ve set up my system and made a backup of everything. then i´ve wanted to check if the restore is working so i restored my backup. after a reboot my entyre phone was set to factory state. happened 2 times . cyanogenmod was still installed but i had to configure the entire system again. after downloading all apps i decided to install cwm instead of twrp using cwm 6.0.4.5 touch for i9300 flashing via odin 1.85. everything worked fine and i booted into recovery to make a backup. cwm then says: Error cant mount /system so i tried to mount the system via the storage option. still says cant mount /system. then i rebooted my phone and again everything was gone... im really angry because whats the point of using a backup and then everything is gonna be erased.
i hope someone can help me with this. i also would erase everything and start from zero so that everything works.
Edit:
manual factory reset shows this:
formatting data
Error mounting /data.
Error mounting /sdcard/ . android_secure!
Skipping Format
formatting cache is working
cant format sd card.
&
Cant download apps from google play because of server problems...
show log:
mount: mounting /dev/block/mmcb1k0p16 on/data failed: no such file or directory
W: failed to mount /dev/blockmmcb1k0p16 (file exist)
cant wipe dalvik cache
!!!phone gets resetted everytime after cwm says error cant mount /system!!!
regards
Can be closed
I´ve installed original Samsung firmware and then CWM + CM10.2 + Boeffla 2.1 again and now CWM can mount everything and the Backup also works. maybe Twrp ****ed something up. i dont know.
regards
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
u need to use pit file for repartition your internal memory.flash your phone with pit file
ifhi said:
u need to use pit file for repartition your internal memory.flash your phone with pit file
Click to expand...
Click to collapse
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
hello u should flash the tar file via recovery this should restores ur efs backup
tetakpatak said:
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
edwinn said:
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
Click to expand...
Click to collapse
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
tetakpatak said:
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
Click to expand...
Click to collapse
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
edwinn said:
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
Click to expand...
Click to collapse
I am sure it is possible to disable md5 check
tetakpatalked from P5110