/cache error - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I managed to root a stock Straighttalk (verizon fascinate) Showcase running GB 2.3.6. Then managed to flash a CM 10.1 (StraightTalk.showcase.cm-10.1-20130723-NIGHTLY-fascinatemtd.zip), and it seemed to run 'ok'. Then I read about HellyBean, but could only find the kernel. The other mirrors for it no longer exist, and the developer no longer has copies.
The file I flashed from CWM 4.0.1.0 recovery was: Devil4.2_galaxysmtd_20130624.zip. It said something about reparitioning. I figured what the heck and said flash anyway. It did but now will only boot into that. Trying to flash back to CM 10.1 I get a /cache error:
ClockworkMod Recovery 4.0.1.0
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 have tried numerous methods suggested in two year old (dead) threads: flashing pit with odin and original rom (atlas_v2.2.2.pit, Odin3 v3.07.exe, CI500_VZW_EH03_GB_CM.tar.md5) yet keep running into the /cache error, or it won't flash or whatever. It comes back to that error.
I bought another phone for the time being, but I would like to get this one working.
EDIT: didn't realize the i500 and i9000 were different phones. Going to the Fascinate forum...

Here's the fix
THIS IS ONLY FOR THE FASCINATE/SHOWCASE/SCH-I500 or SCH-S950C
MODERATOR PLEASE MOVE THIS THREAD to the Fascinate forum.
THIS WILL NOT WORK IN THE I9000. In fact, flashing i9000 kernels (like Der Teufel / The Devil kernel, CAUSED THIS PROBLEM).
Fire up ODIN (I used ODIN 3.07 on Windows 10 (12/2015 patch level))
**Uncheck Auto-Reboot!! in ODIN before flashing.**
Use the PIT from EZbase (others might work)
and flash cwm4_fixed_for_cm7-ODIN.tar
https://www.dropbox.com/sh/fk25duo59iyn33g/AADm6xkLJCOiprqe37e4TOMia?dl=0
I put them on dropbox. Although you can find them in other threads/places. I did not keep track of where I found the copies, but I found them on 12/2015, so you should be able to also.
Unplug the phone and remove the battery. It will turn off.
Remove the SDCARD and put in http://download.cyanogenmod.com/get/jenkins/35557/cm-10.1-20130723-NIGHTLY-fascinatemtd.zip (the latest nightly CM10.1 Android 4.2.2x)
Boot up the phone by holding the Vol Up & the Vol Down key, and press Power until you see SAMSUNG, then release the Power button. It will boot up into a 4.0.1.0 recovery. YOU MAY STILL SEE A CACHE ERROR... IGNORE IT.
Choose the option to load a ZIP from the SDCARD.
Flash cm-10.1-20130723-NIGHTLY-fascinatemtd.zip
It will reboot into the newer recovery, then continue with the update.
You should be done now.
No more /cache/ mount errors, no more stl11 errors.
I found a quote at http://forum.xda-developers.com/showthread.php?t=1190668
"All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems."
IT RUNS ON MTD/yaffs2... etc etc, it's clear that this repartitions/reformats the device. A lot of the struggle I had for days, a week, was trying to set the PIT over with Heimdall or ODIN, and restoring to stock. Unfortunately once one of these i9000 type kernels or ROMs 'touch' your Fascinate, you can't go back to the stock, at least not from being stuck with the /cache/ mount errors. You *might* be able to go back after flashing the nightly Cyanogenmod linked above.

Related

[Q] E:Can't mount /dev/block/st110 [Solved]

Hi, i am a newbie of Android. i flashed my Captivate to I9000ZSJPD, but found that the rotation has some problem. So, i tried to flashed other different rom many many times and try to fix up. I believe i make sometime wrong in between and bricked my phone... anyway, i tried to fix it by ADB in download mode
And now, it will going to recovery mode in opening...
and show:
_______________________________________________
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Cant's mount
your storage not prepared yet, please use UI me
nu for format and reboot actions
copy default media content failed
_______________________________________________
(I tried to flash I9000TGYJH1, I9000XXJP3, I9000XWJP6, I9000XXJPM, but still show it when starting)
i guess i need to format internal sd-card??? however, in this kernel,
The screen show "Enter: OK Key", but my Captivate seem no "OK Key", and all keys are not working except UP and DOWN....
if i reinstall "kernel-captivate-stock.tar.md5", it can be use "power key" to choice, but no format, or wipe data/factory rest option....
What should i do? Pls help me...
Try and Odin 1-click back to stock. Sounds like you might've had a lag-fix installed and you can't format the internal SDCard.
Odin should overwrite and format it starting you off fresh.
Either way.. your not totally screwed yet. Keep plugging away.
Thanks so much Avgjoegeek!, it's work again!
I am having the exact same problem on Rogers 896. I have tried the ODIN 1-click but it just seems to hang on either the Master Clear or the Rom flash. How long should it take? It seems fairly straightforward, am I missing something?

[HELP] "E:Can't mount /dev/block/mmcblk0p1"

Title.
Everytime i try applying update.zip this error message appears.
Tried almost everything possible but can't find a solution for this problem.
How can i get into fastboot-mode?
bump
I also have this problem.
About a month ago Milestone was upgraded through cable to official Froyo.
Today, GOT_RTEU_2_2_1FULL.sbf was flashed with RSD Lite 4.9, using this guide
http://forum.xda-developers.com/showthread.php?t=698059
and
http://forum.xda-developers.com/showthread.php?t=983516
After going to recovery (x + power, vol up + camera) and trying to update previously copied Open Recovery 3.3, following problem occurs:
Code:
E:Can't open /cache/recovery/command
E:Can't mount /dev/block/mmcblk0p1 (or else)
Screenshot: http://dl.dropbox.com/u/20342824/2011-06-23 14.09.06.jpg
I've read that I can have my recovery reverted to non-vulnerable because of having flashed official OTA (and I can't undo this step)
Could this be the cause for such error message?
This is my wife's Moto, we really need to put a decent FW on it, stock Froyo is very disappointing

[Q] Stuck on Samsung logo, recovery says can't mount /dev/block/mmcblk0p1

Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)
Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
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 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...
Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS
Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!
has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.
Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?
Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.
Bump in hopes of solving this issue.
My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.
you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.
Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728

[Q] Can't boot phone after flashing CM9

Hello everyone,
I've tried to install CM9 on my Samsung Galaxy S I9000. However, I must have done something wrong in the process. I'm totally new to the whole custom ROM thing. I'll try to list the steps I performed to install CM9. I hope someone can point out where I went wrong.
Generally, I followed the instructions given in http://forum.xda-developers.com/showthread.php?t=1363593 .
1) Installed "ROM Manager" (https://market.android.com/details?id=com.koushikdutta.rommanager&hl=de).
2) Rooted my phone according to the instructions in http://androidadvices.com/root-samsung-galaxy-gt-i9000-android-234-xxjvr-firmware/3/ . This uses Odin 3 v1.7 and also installed CWM Recovery (v3.0.0.5) . I checked that my firmware exactly matches the one for which the description is for.
3) Performed a backup using CWM Recovery.
4) Performed wipe (data/factory reset AND cache).
5) Installed CM9 using CWM which I had downloaded from the links given in the thread given at the beginning and placed the four .zip files (CM9, Google apps, Google apps fix and Faceunlock) on my external SD card. I only realized afterwards that the instructions said to place them on the internal SD card.
6) Installed Google apps, Google apps fix and Faceunlock using CWM.
7) Selected reboot in CWM. However, the device didn't boot into Android. First I saw the CM logo screen, then the phone got stuck on the "Samsung Galaxy S I9000" screen.
8) Read instructions again, realized that I forgort the wipe after installing Google apps. Performed the two wipes again, however the problem remained.
9) Read instructions again, realized that I was supposed to install the .zip files from the internal SD card. I assumed that was the step I went wrong. So I decided to restore to my stock ROM which I had backup'ed before. I used the restore option in CWM, selected my previous backup (located on external SD card) and performed the restore.
10) However, the phone still does not get pass the "Samsung Galaxy S I9000" screen. When I boot into CWM, the following appears on my screen
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:Unable process volume! Skipping...
Checking /cache...
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:Unable to process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
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]
Click to expand...
Click to collapse
The same apperas if I try to do a "restore" from CWM again.
My questions:
1) Where did I go wrong?
2) What must I do to be able to attempt to install CM9 again?
Thanks in advance!
To get back to stock you have to flash a 3 file stock rom with repartition in odin.
i think the best is to get back stock, if you tried to restore a backup. then flash semapore kernel.
Then boot in recovery, wipe. Flash build 12 and gapps then reboot.
Sent from my GT-I9000 using Tapatalk
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
oxyris said:
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
Click to expand...
Click to collapse
First take a look in ramads thread: http://forum.xda-developers.com/showthread.php?t=1102881
1. Here you can read how to flash with odin and download the latest gingerbread stock rom
2 your backup will work, but you have to be on a stock rom first.
3. read how to flash with odin in the link.
4. Semapore kernel is a custom kernel, comes prerooted and stuff.
so after you are back stock you can flash this in odin, put it in pda and dont thick repartiton. No you are ready again. turn of phone, boot into recovery mode with 3 button combo, here you can restore your backup if you want. or wipe factory reset, wipe catche and dalvik catche flash build 12 and gapps from internal sd. reboot and enjoy ics http://forum.xda-developers.com/showthread.php?t=1112908 remember to download the correct kernel for your build.
5. hard to say, the best way to get correct cwm is to flash a kernel as semapore or cf root. maybe it was somthing with your cwm (recovery)
Edit: it take some time to boot the first time
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
oxyris said:
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
Click to expand...
Click to collapse
its not the newest. you should have thick repartition and 512 pit here. But if the phone boots up i think its ok. only kernel flash its important not to thick repartition.
its best to use this kernel http://download.chainfire.eu/124/CF-Root/SGS/CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip
I tried flashing CM9 again with the Semapore kernel I had installed first. It seemed to work, however, after booting into CM9, a screen appeared that said something like "Device encryption failed" and I could not get into the OS. Any idea what that could have been?
I'll give it another try anyway, this time with repartitioning and PIT when flashing the stock ROM and with the other kernel you suggested.
Slightly off topic, but what's with this obsession about 3 file roms that's been going around for a long time? I have yet to see any evidence to support the belief that 3 files rom is someone better than single file rom.
@OP: Try flashing CM7 first. See if that works. Then flash CM9.
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
edit2: According to the CM7 thread (http://forum.xda-developers.com/showthread.php?t=1061946), "you're not able to flash any kernel or run any filesystem you want". So which kernel can I use?
oxyris said:
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
Click to expand...
Click to collapse
Hi,
I'll get 3 weeks ago SGS in a bottloop after flashing CM9 build11 (teamhacksung's) from latest CM7.
I went mad four about few hours, afterthat I decided to reflash stock 2.3.6 (JVX_JV3_JVT.tar).
After flashing with Odin, I end-up with in DBDATA error after rebooting..
So I flashed dbdata.rfs.tar and I've got original 2.3.6 working.
So:
-I've rooted my device again (CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar)
-Installed ROM manager
-Rebooted into recovery
-Flashed ICS port latest builds + GApps + face unlock (and wiped ALL).
No my device is working with ICS,
hope this will help you guys on flashing ICS and don't waste time.
Cheers
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
Phone unnecessarily gets data connection on device encryption password enter screen.
Click to expand...
Click to collapse
But I'm not sure if they're referring to my particular problem.
oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
May be the only way is to wait devs to solve that issue.
I'm so sorry that my tips didn't work 4 u...
oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
One question, do you have your SD Card in your phone when you are going through the install process? If so, take that out before flashing anything. It has been the cause of problems for a lot of people coming to CM9.
Hi, thanks for your replies.
I seem to have solved the issue. When the "device encryption unsuccessful" screen appeared, I booted to recovery using the power button (a menu will appear letting you choose between shut down, restart or recovery) and came into CWM. There, I wiped everything (i.e. factory, cache and dalvik or whatever its called) and rebooted. I could then start the OS without any further problems (until now).
I also noticed that now my internal SD card is actually "clean" again, i.e. it only contains the folders and files that are there when you get your phone new. This wasn't the case when I performed a wipe BEFORE flashing CM9.
I'm using the CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar kernel you suggested, maybe that was the problem (I can't recall being able to boot into recovery the first time the "device encryption unsuccessful" screen appeared).
@ryanmat Yes, I did have my external SD card in the phone during the installation process, but thanks for your suggestions.
edit: I will report back if everything goes smooth for a few days.
ok, let me understand...
now you got CWM working and you've got CM9 after wipe all with rooted kernel I suggest you?
Exactly. Let me write down the individual steps I finally performed to get CM9 running.
1) Get Odin and PIT files -> http://www.multiupload.com/51MTA5K1H7
2) Boot phone to download mode
3) Start Odin on computer
4) Connect phone to computer (USB)
5) Flash stock ROM -> http://www.multiupload.com/PKVWPJJZMO (check repartition, put in the 512 PIT file and select the PDA, PHONE and CSC files from the stock ROM, then hit start)
6) Disconnect phone from computer
7) Restart Odin on computer
8) Boot phone to download mode
9) Connect phone to computer (USB)
10) Flash the CF kernel for root access -> http://www.filesonic.ch/file/2356034801 (don't check repartition, no PIT file, select the downloaded tar file as PDA, then hit start)
11) Boot the phone to the stock ROM. After the kernel was flashed, you should have CWM installed. Place the CM9 tar, as well as the gapps, gappsfix and faceunlock tars in your internal SD card. Start CWM and boot into recovery from there.
12) In CWM recovery, select install zip from SD card and select the CM9 ROM. After the installation, my phone automatically rebooted, booted CM9 and got into the "encryption unsuccessful" screen.
13) Hold the power button, select reboot and then select recovery to get back into CWM recovery.
14) Perform factory reset, cache wipe and dalvik cache wipe (found under advanced).
15) Select reboot in CWM recovery, you should now be able to boot into CM9.
16) Reboot into CWM again and install gapps, gappsfix and faceunlock if desired.
I don't know if all of these steps are required or if they must be performed in this exact order. However, it worked for me (CM9 build 12).
and now build 13 is out...!!!

Stuck without a OS

Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
E:failed to open/etc/recovery.fstab (No such file or directory)
E:unknown volume for path[/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/revovery/log]
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
deathstoned said:
Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
Click to expand...
Click to collapse
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 1:
I) Download Android 2.3.6 Gingerbread Value Pack (XXJVU)
II) Download ODIN http://www.mediafire.com/?nhhhkm5c2j43rhw Extract Odin3 v1.7.zip to get .exe file
also download the pit file, http://www.mediafire.com/?v2rub40k1bvccj4
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
I had this problem with Paranoid Android before... the zip was corrupt.
If you are able to extract the rom with winrar/winzip/totalcmd or other program, install it, if it is corrupt, download it again again and again...
Sent from my GT-I9000 using xda premium
Samtan4326 said:
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
Click to expand...
Click to collapse
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
-- wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/macblk0p2
Formatting /dbdata...
formatting /cache
Deleting meta data
Data wipe Failed
-- Applying Multi-CSC..
Installing Multi-CSC
APPLIED THE csc-Code "CPW"
Successfully applied multi-CSC
Click to expand...
Click to collapse
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
deathstoned said:
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
Click to expand...
Click to collapse
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Samtan4326 said:
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Click to expand...
Click to collapse
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
E:unknown volume for path [/system]
E:unable process volume! Skipping...
Checking /data...
E:unknown volume for path [/data]
E:unable process volume! Skipping...
checking /cache...
E:unknown volume for path [/cache]
E:unable process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E;Cant mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Cant mount /cache/recovery/log
and the same for last_log
Click to expand...
Click to collapse
deathstoned said:
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
Click to expand...
Click to collapse
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Samtan4326 said:
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Click to expand...
Click to collapse
I dont think you got what i said.I installed CFW and went into the recovery,there under Mounts and storage ,there was nothing apart from "mount USB storage"..not even Mount BOOT..nothing apart from that 1 option..when i tried to do a wipe "data/factory reset or cache" it showed me that message which i posted above.still i installed the jvu+root again (Twice actually),it was the same result,the error i posted 2 posts above.
I'm in no mans land now and cant do anything apart from my phone apart from go into download and recovery mode
Please someone help me,i've to go on a 33 hr train journey tmrw and without a phone,it'll be really troublesome
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
amerkiller1995 said:
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
Click to expand...
Click to collapse
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
deathstoned said:
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
Click to expand...
Click to collapse
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
amerkiller1995 said:
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
Click to expand...
Click to collapse
Ok dont know whether this is good or bad
I installed CM9 from the external sd as the internal sd was inaccesible in any way..the installation showed info like
"the internal sd card marker could not be found
Going ahead with installation"
the installation continues and restarts once and updates but it does not boot into the main page,it directly goes into the Encryption Unsuccessful page.When i try Reset Phone,it goes into the CWM recovery screen with some errors,
when i try to install CM10 from this recvery screen,it initially stops the installation saying the data partition layout is different and all my data will be wiped.run the .zip to go ahead with the progress.I run this it goes directly into the CWM 6.0._._ and it doesnt show any errors,i try to reboot it gets stuck on the galaxy s screen.
this situation is better than the previous condition as i know a OS can still run on my Phone..Just need to get this thing rectified now
Please if anyone could help me right now,i would be really grateful..not able to contact anyone without my phone
It might be a hardware problem... I had something similar
http://forum.xda-developers.com/showthread.php?t=1895224
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
amerkiller1995 said:
It might be a hardware problem...
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
Click to expand...
Click to collapse
I installed Cyanogen 9 and got through tht EU page by restarting abut 20 times or so,now i'm trying to install a working version of gapps in it.Tried 1 but the setup failed,so i flashed back to Cyanogen 9 and am not touching it till i reach home.a device capable of making and taking calls is better than nothing..
Is there a way to download contacts from gmail without gapps,the play store is not included in the original rom and i'm hesitant to go into CWM recovery mode as i will have to tackle the EU page again
Anyways thanks for your help,will have to fix this problem once and for all after i reach home
I don't know about contacts from gmail. When you're home look at my updated post above
Sent from my GT-I9000
basically
just reflash gingerbread

Categories

Resources