[Q] Problem with CWM / can't flash rom or restore backup - Galaxy S 4 Q&A, Help & Troubleshooting

Hello,
i got my root access running yesterday and backed up my apps with Titanium Backup.
Then it was time to flash cm 10.2. I backed up my stock rom and then wiped the data and cache partition.
Then I tried to flash cm, but it gave me an error. Now if I start cwm, the following errors appear:
Clockworkmod Recovery v6.0.3.2
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /chace recovery/log
E: Can't mount cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When I try to flash CM also errors occur.
I also can't restore my backup, the following error appears: MD5 mismatch!
Please help me, it is quite urgent
Thanks A LOT in advance.....
Best regards, Simon
E: I have the I9505, if I forgot something else, please tell me, my start in that day was so terrible and it's only 7o'clock
E2: when I try to flash CM 10.2, the following messages appear:
-- Installing: /external_sd/AROOT/cm-10.2-jfltexx.zip
E: can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package....
Opening Update package....
Installing Update....
Install from sdcard complete
Then when I try rebooting it doesn't go further then the CM Logo, which spins...

re: MD5
cH33zBurGer said:
Hello,
i got my root access running yesterday and backed up my apps with Titanium Backup.
Then it was time to flash cm 10.2. I backed up my stock rom and then wiped the data and cache partition.
Then I tried to flash cm, but it gave me an error. Now if I start cwm, the following errors appear:
Clockworkmod Recovery v6.0.3.2
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /chace recovery/log
E: Can't mount cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When I try to flash CM also errors occur.
I also can't restore my backup, the following error appears: MD5 mismatch!
Please help me, it is quite urgent
Thanks A LOT in advance.....
Best regards, Simon
E: I have the I9505, if I forgot something else, please tell me, my start in that day was so terrible and it's only 7o'clock
E2: when I try to flash CM 10.2, the following messages appear:
-- Installing: /external_sd/AROOT/cm-10.2-jfltexx.zip
E: can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package....
Opening Update package....
Installing Update....
Install from sdcard complete
Then when I try rebooting it doesn't go further then the CM Logo, which spins...
Click to expand...
Click to collapse
Go into CWM and or Rom Manger and find the option where it says "Ignore MD5"
or something to that effect and try restoring your nandroid backup with MD5 disabled.
The best thing you can do is download TWRP custom recovery for your specific phone's
model (i9505) and restore your nandroid backup using that, it's a lot better than cwm or
rom manager, and its also all "touch" and has large tabs to click on.
TWRP has the MD5 checking as an option which you cannot miss when you are creating
a nandroid backup or restoring one.
Good luck!
I am not 100% sure if cwm/rom manager has that MD5 option which
you can enable or disable. (I forgot, been so long since I used it).

I checked and I couldn't find an option to ignore MD5. Then I looked for it in google (for cwm). There I found, that a backup can be truly corrupted which could seriously harm the phone. Therefore I don't dare trying to restore my backup with another recovery...
Is there a way to fix the problem that cwm has? With beeing unable to mount or open the stuff I mentioned in my first post and therefore somehow hindering my system to start.
Thanks so far!

Wow, this is all really strange. I now formated chache (only works when cwm is rebootet in cwm). Then the errors do not occur again. Then I formated my data again, got stuck, shut my device on and tried again, then it worked. The same thing for installing cm. First try it gets stuck, second try it works....wtf..?
Well now it runs, but I am really not content with how it worked out...

Related

Stuck on htc incredible screen

installed leaked ota then rooted, tried a hydra but saw cam didnt work so i went into nandroid and did restore. now im stuck on htc incredible screen. pulled battery and still have access to clockwork what can i do?
wipe data/cache and do another nandroid restore
tried that, still wont load....tried to unroot and take ota out with method but i wouldnt push the files onto my phone...tried clear storage, then tried to go back into recovery and it gives me a bunch of error messages i think im screwed here
if this gets too complicated to me what are my options as far as gettin it fixed will htc fix it im sure i would have to pay but i would if i got my phone back
wrong section but put the file in this thread on your sd http://forum.xda-developers.com/showthread.php?t=727263
Run from clockwork
just tried that goes back to the main clockwork recovery screen underneath that it says
ClockworkMod recovery v2.5.0.1
E:Cant mount/dev/block/mmcblk0p2 (file exists)
E: cant mount cache:recovery/command
E:cant mount/dev/block/mmcblk0p2 (file exists)
E:cant mount cache: recovery/log
E:cant mount/dev/block/mmcblk0p2 (file exists)

[SOLVED] Galaxy S I9000B not booting, no recovery mode

I rooted and installed CM7 on my SGS i9000B about 1 month ago. Everything was going fine and I was in love with my phone.
This afternoon, suddenly and with no apparent reason, it started giving me infinite "Force Close" messages to all apps I tried to open, making the phone pretty useless. Whe this happened I tried repairing permission from within Rom Maanger but the problem persisted. So I booted in recovery mode (Clockwork Mod Recovery) and tried fixing permissions there, but force closing problem was still there.
I had an Nand backup from the day I installed CM7. So I went to recovery mode again and tried restoring the backup, but it gave me an error (I believe it was somwthing related to disk space, but I'm not sure about that). So I did another backup (just in case) and tried to reboot the phone to try restoring backup again.
The problem is, now I can't get to recovery mode again. When I rebooted I was not able to go back to recovery mode anymore. I am still able to get to Download mode though. So I was thinking about flashing some rom/bootloader or something back in from Odin, but as I have no experience doing this, I believe it's safer to ask for help here before doing anything to the phone.
I believe it's not bricked yet, since I can still get to download mode.
Can anyone give me some detailed info about what I should do?
Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.
evernet21 said:
Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.
Click to expand...
Click to collapse
Sorry but I have very little experience with this and I want to be sure about what I'm supposed to do. What do you mean by flash kernel again? Is it flashing CyanogenMod 7 again via Odin?
I flashed the kernel again using Odin. Used the same file that I used before (when I fisrt rooted the phone a month ago - speedmod k13C). Now I can get into Recovery Mode.
But now I have a different problem. I tried to do a nandroid restore (backup and restore - restore ALL) but I have some errors related to mounting errors:
Code:
Checking MD5 sums...
Restoring system...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Error mounting /system/!
Skipping format...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Can't mount /system/!
I have no idea what that means.
Any help?
While searching for help on this error I found some people saying that flashing stock rom back intro phone could solve the problem. So this was what I did. Flashed stock samsung rom back i using Odin but when phone rebooted the following error appeared:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
[some recovery options]
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
So I have a very similar error - "can't mount /dev/block/SOMEFILE". It looks to me like a problem with the internal sd card. What do you guys think?
Solved
I could solve the problem using the method described in this thread.
http://forum.xda-developers.com/showthread.php?p=14732179#post14732179

[Q] Error Mounting Cache

Hey guys.
Got a GT-I9505 and was trying to look at some custom ROMs to install, even thinking of giving the beta AOKP a go, but I ran into an issue.
I was first able to gain root access without much issue from the pre-installed firmware, worked through Odin like a treat, but after I went to install the CyanogenMod Nightly through CWM Recovery, the ROM wouldn't install. I noticed the Factory Reset through CWM and that there was an Error mounting the cache partition. I checked the mounts and only the system partition was mounted, I couldn't mount anything else.
So,after essentially bricking the phone, I used Odin and flashed the Stock Firmware back on and followed on as instructed. but the same thing happened again.
Any suggestions would be great. I have been looking at other devices to see if there had been any problems with mounting cache through CWM and to check if they had solutions, but I was coming up pretty thin with explanations. I was thinking if I format through Odin while flashing the firmware back on, that might help?
Thanks in advance, hopefully.
Tried a few more times.
third time clearing cache, the entire screen started to go more and more green.
fourth time made it reboot
fifth time just cant factory reset at all. its ridiculous.
I honestly cant say im doing something different.
Is there a way to break and actually force the cache to be wiped?
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Argh. I don't understand why I cant access/wipe my cache. is this a recovery problem?
Okay, there may be a problem with the CWM recovery. I have been looking through a few of the threads and comments in particular with Philz touch CWM recovery, and It now works. but there stillseems to be a few problems popping up with installing aosp/aokp roms. backup and restore is working fine. cache/data wipe also working. but it's quite a pain for the whole process to get it to work.
ill post the threads in a bit.
here is the AOKP rom i was referring too
http://forum.xda-developers.com/showthread.php?t=2276722
and the recovery thread that helped solves some issues
http://forum.xda-developers.com/showthread.php?t=2281367&page=18

I'm afraid I bricked my phone!

Hi,
I've a galaxy S4 I9505, I can't start anymore any ROM on my phone, when I try to boot the phone, it get stuck on the samsung page.
also when I open the cwm recovery i get the message:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log,
I already tried to wipe data, dalvik cache. and to format the cache. but it doesn't change anything
I also tried with custom ROM via Odin, or some other different ROMs, but I can't boot my phone yet,
Can I try something else?
Try flashing a full stock ROM with .pit
Sent from my GT-I9505 using xda app-developers app
fraibcicoi said:
Hi,
I've a galaxy S4 I9505, I can't start anymore any ROM on my phone, when I try to boot the phone, it get stuck on the samsung page.
also when I open the cwm recovery i get the message:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log,
I already tried to wipe data, dalvik cache. and to format the cache. but it doesn't change anything
I also tried with custom ROM via Odin, or some other different ROMs, but I can't boot my phone yet,
Can I try something else?
Click to expand...
Click to collapse
Flash the latest stock using odin without pit first and try woth wipe cache / dalvik
If that does not work then flash it with the correct pit
.
I already tried, I don't get any error in the installation, but it get stuck in the boot
Then try to go into recovery mode and to wipe everything cache,factory reset,dalvik's cache

Error when flashing hero2ltexx - Could not find 'META-INF/com/google/android/upda...'

I had some issues when trying to flash xposed and ended up formatting my data with TWRP.
After formatting data, I tried flashing root and xposed again. Xposed flashed fine, but root gave me an error. I thought it was because I hadn't gone through the system setup, so I went ahead and went through the setup and tried again but I'm getting the same error in TWRP.
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file '/external_sd/CF-Auto-Root-hero2lte'hero2ltexx-smg935f.zip'
What should I do?
Also, every time I boot in recovery now it asks me to swipe right as if it was the first time.
Thanks!
Bump. I haven't found a single solution to this on Google.
same problem here
l33t p1mp said:
I had some issues when trying to flash xposed and ended up formatting my data with TWRP.
After formatting data, I tried flashing root and xposed again. Xposed flashed fine, but root gave me an error. I thought it was because I hadn't gone through the system setup, so I went ahead and went through the setup and tried again but I'm getting the same error in TWRP.
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file '/external_sd/CF-Auto-Root-hero2lte'hero2ltexx-smg935f.zip'
What should I do?
Also, every time I boot in recovery now it asks me to swipe right as if it was the first time.
Thanks!
Click to expand...
Click to collapse
You do not flash CF-Autoroot in TWRP. You extract the zip in Windows and Odin the tar file in order to obtain root.
My problem begins when installing "dm-verity and force encryption disabler". This are the errors it shows:
Could not mount /data and unable to find crypto footer
Failed to mound 'data' (Invalid argument)
Unable to recreate /data/media folder
....
Unable to mount storage
Failed to mount 'data' (Invalid argument)
Unable to mount storage
..
Unable to mount /data/media/TWRP/.twrps
Click to expand...
Click to collapse
sonnax said:
My problem begins when installing "dm-verity and force encryption disabler". This are the errors it shows:
Click to expand...
Click to collapse
Reflash stock rom and start over.

Categories

Resources