First off, I flashed everything as normal, followed instruction for flashing Blitzkrieg to the T and everything went fine.
When the phone first booted I had issues with installing market apps because I guess I was ridiculously low on space, but I'm not sure how. I resolved that using the Format USB Storage and lost all my data, which was expected and everything works fine now.
Now I'm getting errors in recovery, which are stated below:
E: Can't mount CACHE: recovery/command
E:Can't Mount /dev/block/stl11
(File exists)
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
E: Can't mount /dev/block/stl11
(File Exists)
Click to expand...
Click to collapse
Because of this error, I'm now unable to make and restore nandroid backups and such.
Any ideas on how to fix this?
Just odin back to stock
Sent from my SGH-T959 using XDA Premium App
So go back to stock and follow the same steps as before?
Sent from my Galaxy S via XDA App
Odin back, then follow instructions carefully when flashing gingerbread roms because they are a little more tricky to flash.
In the blitzkrieg rom install instructions, he offered two ways to flash it. Which method did you use?
I used the bootloader method while on project v and the 1.2ghz kernel for gingerbread. Although I could not get heimdall to work right so I used odin instead and everything worked fine.
Sent from my Galaxy S via XDA App
Related
Hi all
I was being foolish. was using the worng PIT file and trying to go straight to JI6. What fixed it was - using the right PIT and the JFD.tar for the PDA.
Mods - if this thread needs to be deleted, please do so.
Thanks.
Hi all
I think I am into some big trouble with my vibrant. I had Bionix-v installed and was very happy, then I messed around with Dragon kernel 2.8, then Dragon kernel 3.1.2, followed by DOW 14.
wanted to get back to bionix-v after a fresh install, so decided to ODIN back to stock. Then ran into trouble with ODIN - wont assign a com. Unistalled the samsung drivers and reinstalled, did not work. Tried a different laptop and it worked eventually.
ODINed back to JI6, (Re-partition was selected by default and I managed to overlook it ) but then got error:
E:Can't mount /dev/block/st110(File exists)
Error mounting /datadata/!
Skipping format...
E:Can't mount /dev/block/st110(File exists)
Can't mount /datadata/!
Tried to do restore from an image on my internal sd through clockword mod recovery: again got the same error.
E:Can't mount /dev/block/st110(File exists)
Error mounting /datadata/!
Skipping format...
E:Can't mount /dev/block/st110(File exists)
Can't mount /datadata/!
Looked on web - "eugene's froyo that does not brick"
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
I have not used sdk or adb before and am not confident either.
Sorry for making it such a long post but I wanted to make sure that I give all the details.
Can someone advise me further?
Freaking out in NYC.
Menn, I'v got the same problem.
Can anybody help please??
try repartition with another .pit-file. Solved the problem for me.
Odin back to jfd
The threads I looked at were out dated, or dealt with other mfgs. If it's out there, please post the link so I can follow it.
Used ODIN to flash ED01DB_DOx_SHARK.tar and clockwork file this morning from-- http://forum.xda-developers.com/showthread.php?t=1048380
In cwm [3.0.0.8], this is what I did and the errors I received:
Attempting nand backup
E:unknown volume for path [/sdcard]
Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
So then I tried this:
Command = mount /sdcard
E:unknown volume for path [/sdcard]
Error mounting /sdcard
Any thoughts or work around? Some threads say partition, some format. But I cannot seem to find anything that is Fascinate specific. Thanks!
No ideas at all? Only found 2 or 3 threads across the net and none deal with this version of cwm
InfiniteRefrain said:
No ideas at all? Only found 2 or 3 threads across the net and none deal with this version of cwm
Click to expand...
Click to collapse
Doing a nandroid backup with that recovery is a known issue. You can check toward the end the thread for possible solutions, I believe you have to go into mounts and storage from the first screen of that CWM and mount system and data before being able to do a recovery:
http://forum.xda-developers.com/showthread.php?t=1046905
Or you can flash the CWM from nemesis2all which I believe is capable of doing a nandroid backup:
http://www.multiupload.com/8VDE8GX69P
Thanks - will look it all over once I get home!
Sent from my SCH-I500 using XDA Premium App
Will pushing that through ODIN with fix the sd mounting, then? End result is to load a full custom rom. Looking at comrom 2, but those instructions say to load via cwm, but do you know if it is possible to load it through ODIN like I did for for the ED01DB_DOx_SHARK.tar
UPDATE: Those packages install VooDoo lagfix also -- Saw the folder on my sdcard, downloaded the VooDoo app in marketplace and:
Deselected the button - not lit
Rebooted in Recovery
-here it loaded the VooDoo recovery-
Was able to wipe all caches
Then did a backup through Voodoo
I can't post in the dev forum yet, so here it goes. Is it possible to load ComRom2 via VooDoo [ran a search in that thread with no specific results]? Will there be issues later due to both cwr 3.0.0.8 and VooDoo 2.5.1.x
EDIT 2: Took the plunge and ran them through the voodoo recovery and it all worked. Thanks for the tips above!
Hey there
I have a pretty serious problem with my I9100... I had installed the Paranoid Android 2.52 ROM and I was trying to switch to a different kernel. Which wasn't working for me, I'm guessing due to the Fastboot feature in that ROM.
The last kernel I tried was the Andromeda one. While trying that, I thought I might try to do a factory wipe using its recovery software, hoping that that might get Paranoid Android to boot.
Unfortunately, it would hang while doing the wipe, and I eventually (after about 20 minutes) power-cycled the device. I tried getting back to my working kernel, but Andromeda's recovery would either error out with mount errors, or it would hang altogether.
Eventually, I tried flashing a CF-Root kernel using Odin, and since then I was unable to get past the Samsung boot splash screen. I could no longer access the recovery software, but I could get into download mode and flash stuff via Odin (Kies won't recognize the device).
I've tried a variety of kernels and firmwares (including the stock one for my phone (GT-I9100_XEF_I9100XWKJ2_I9100XXKI4_I9100XEFKJ1, which I've previously flashed successfully to get it back to a non-rooted vanilla state)), but nothing I did would get the phone to boot.
Thinking the partition table might've been damaged somehow, I attempted the stock firmware from the first post here, including the PIT file and re-partitioning. This process would eventually hang when flashing datafs.
Thinking the bootloader might be damaged, I tried partitioning again, flashing the original bootloader from here, and again flashing the stock firmware that I've used successfully in the past.
I can now actually get past the boot splash! However, the phone boots directly into stock recovery, which looks like it's trying to do some post-update maintenance-type stuff, but fails horribly at it. Some of the output from it scrolls past the viewport, but this is the last lines that I can read:
Code:
[COLOR="Orange"]Formatting /cache...
Cache wipe complete[/COLOR]
-- Updating application...
[COLOR="DarkRed"]E:failed to mount /data (Unknown error: 0)
E:install_application_for_customer:Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
[/COLOR][COLOR="Orange"]-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEF/system/'.
Successfully applied multi-CSC.[/COLOR]
[COLOR="DarkRed"]E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Unknown error: 0)
E:Can't open /cache/recovery/log
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Unknown error: 0)[/COLOR]
It definitely looks like a borked filesystem/partitioning to me. I tried doing a factory wipe in this recovery, but it would hang at formatting /cache.
Any ideas of what I can do to get this thing up and running again?
Thanks in advance,
Daniel
I successfully flashed a CF kernel, and can now access CWM.
I get these error messages, however:
Code:
CWM-based Recovery v5.0.2.7
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
Wiping cache partition in CWM takes care of those errors. Trying a factory reset will give me "Formatting /data..." for a bit, and then the device automatically reboots.
I can format /cache and /system alright, but not /data... I'm fearing that NAND corruption bug I've heard of, except I don't see how I would've caught it...
All right, so I've now confirmed that the Andromeda kernel indeed has the hard-brick bug. Why on earth anyone in their right mind would release a kernel based on that broken leak is beyond my comprehension.
And, to add injury to insult, the devs know there's a problem, yet do not warn about it in the OP, but they mention it some thirty pages into the thread. Thanks, guys!
Anyway, I'm currently scanning my internal storage for damaged areas so that I can custom-PIT my way around it.
Useful posts for reference:
http://forum.xda-developers.com/showthread.php?t=1760107
http://forum.xda-developers.com/showthread.php?t=1667886
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Hopefully I'll see my phone booting tonight.
Using the patched PIT workaround, I now have my phone back up and running 2½ GB lost on the internal storage, though, but hey - beats being a paper weight!
Was charging my phone yesterday went to unplug and phone stuck at splash screen, pulled battery and left for a while on re-insert splash screen appears straight away. Pulled battery overnight and same thing happened.
Phone has been rooted and has latest (i think) CWM (v6.0.4.7) on it, was running CyanogenMod1! which updated yesterday to latest version (nightly 20140311 i think). I can get into recovery but can't install the rom i have on the phone just get the following messages:
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Does anyone have any idea how if i can get a working rom back onto the phone
Thanks in Advance
jedathoss said:
Was charging my phone yesterday went to unplug and phone stuck at splash screen, pulled battery and left for a while on re-insert splash screen appears straight away. Pulled battery overnight and same thing happened.
Phone has been rooted and has latest (i think) CWM (v6.0.4.7) on it, was running CyanogenMod1! which updated yesterday to latest version (nightly 20140311 i think). I can get into recovery but can't install the rom i have on the phone just get the following messages:
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Does anyone have any idea how if i can get a working rom back onto the phone
Thanks in Advance
Click to expand...
Click to collapse
I had a similar thing when I was changing between 4.3 and 4.4.2 in which my recovery struggled to mount storage after the system was flashed. In the end I had to flash an old version of Philz CWM, or alternatively flash TWRP and mess about with the settings as where it looked for files (something like that) I also found hat only zips on the internal card flashed for a while...
You may have to either:
1) Push the files to the internal card using ADB
2) Try various recoveries with various ROMS till you get on to sit nicely on your system
3) Or as a last option just reflash your phone with a stock rom through ODIN just to get it up and running, before reflashing a recovery and root using CF-AutoRoot and/or ODIN
pjcarrmole said:
I had a similar thing when I was changing between 4.3 and 4.4.2 in which my recovery struggled to mount storage after the system was flashed. In the end I had to flash an old version of Philz CWM, or alternatively flash TWRP and mess about with the settings as where it looked for files (something like that) I also found hat only zips on the internal card flashed for a while...
You may have to either:
1) Push the files to the internal card using ADB
2) Try various recoveries with various ROMS till you get on to sit nicely on your system
3) Or as a last option just reflash your phone with a stock rom through ODIN just to get it up and running, before reflashing a recovery and root using CF-AutoRoot and/or ODIN
Click to expand...
Click to collapse
Cheers pjc, gives me some idea of where to start. I'd just ogt everything the way i liked it as well, typical isn't it
PHONE GETS STUCK ON SAMSUNG's LOGO..
When I go into recovery mode it shows this:
E: Can't mount /cache/recovery/command
Warning: No file_contexts
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
Moreover when I try to to install zip from sdcard or external sd card..it's shows the following:
E: can't mount/sdcard/
To resolve this issue I tried flashing to stock firmware from sammobile using Odin v3.07.
But it shows failed every time..
NEED HELP ASAP!!!
Your partition structure is damaged, possibly due to nand memory failure.
Try flashing the rescue firmware (search in general forum) but make sure you follow the guide as it also includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Your partition structure is damaged, possibly due to nand memory failure.
Try flashing the rescue firmware (search in general forum) but make sure you follow the guide as it also includes a pit file.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply...I tired searching for the rescue firmware..but I wasn't able to find one with the .pit file...it would be really helpful if you can post the link here...
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Sent from my GT-I9300 using Tapatalk