[Q] Weird Recovery Stuff - Samsung Mesmerize

I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.

Ignore it.
Sent from my SCH-I500 using XDA App

JayRHamlin said:
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Click to expand...
Click to collapse
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.

bdemartino said:
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
Click to expand...
Click to collapse
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App

JayRHamlin said:
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Lol yea, I tried that too when I buggered mine up, but since I couldn't flash anything in recovery I decided to find out how to fix it

Related

[Q] really bricked phone

i tried rooting my phone on 2.3.5 then found out i needed 2.3.3 max to root, so i tried flashing 2.3.3 to my phone, something went wrong and now after several attepths at restoring it it just boot cycles. i can get into download mode no problem, but it doesnt matter what i flash it tells me it cant mount efs or dbdata. is there a way to fix this or do i need to send my phone off to get it repaired?
melli.
could reflashing the efs sort this? if so where can i download it? cause i can't find the efs.rfs anywhere...
error messages in android system recovery as follows:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:can't mount /efs
-- Copying media files...
E:failed to mount /efs (invalid argument)
E:failed to mount /dbdata (invalid argument)
E:copy_dbdata_media:Cant mount /dbdata
your storage not prepared yet, please use ui men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
i have tried all the options in the recovery menu and none have helped...
melli.
ok i have now got my phone working again with a few hours tinkering thru heimdall. but now i have no imei number its just blank... any ideas? i have tried every rooting method ive managed to find on here so far none work so i can't edit the stuff in the efs partioion anyway. any other ideas???
melli.
well even despite the lack of replies suggesting how to fix this i have managed to fix it... got my phone working again it is stuck with the 004999010640000 imei but it works, so thanks for the help...
melli.
melliwuk said:
i tried rooting my phone on 2.3.5 then found out i needed 2.3.3 max to root, so i tried flashing 2.3.3 to my phone, something went wrong and now after several attepths at restoring it it just boot cycles. i can get into download mode no problem, but it doesnt matter what i flash it tells me it cant mount efs or dbdata. is there a way to fix this or do i need to send my phone off to get it repaired?
melli.
could reflashing the efs sort this? if so where can i download it? cause i can't find the efs.rfs anywhere...
error messages in android system recovery as follows:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:can't mount /efs
-- Copying media files...
E:failed to mount /efs (invalid argument)
E:failed to mount /dbdata (invalid argument)
E:copy_dbdata_media:Cant mount /dbdata
your storage not prepared yet, please use ui men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
i have tried all the options in the recovery menu and none have helped...
melli.
ok i have now got my phone working again with a few hours tinkering thru heimdall. but now i have no imei number its just blank... any ideas? i have tried every rooting method ive managed to find on here so far none work so i can't edit the stuff in the efs partioion anyway. any other ideas???
melli.
well even despite the lack of replies suggesting how to fix this i have managed to fix it... got my phone working again it is stuck with the 004999010640000 imei but it works, so thanks for the help...
melli.
Click to expand...
Click to collapse
I have the same errors on my Infuse.
How did you fix???? I'm pulling my hair out.
i have the same problem on SGT
did you find a solution?
I have the same problem on Galaxy ace
I did finally get it sorted if i remember correctly i had to use heimdall to flash not odin i think odin was the problem. Sorry it took so long to answer guys but ive barely been on here since then, too much work! lol
Sent from my GT-I9000 using XDA
melliwuk said:
I did finally get it sorted if i remember correctly i had to use heimdall to flash not odin i think odin was the problem. Sorry it took so long to answer guys but ive barely been on here since then, too much work! lol
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
i have same problem any one have that solution?
the acutel problem
ALL SAMSUNG ANDROID PHONE WHO GIVE ERRORS LIKE THIS
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:can't mount /efs
-- Copying media files...
E:failed to mount /efs (invalid argument)
E:failed to mount /dbdata (invalid argument)
E:copy_dbdata_media:Cant mount /dbdata
your storage not prepared yet, please use ui men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
THATS MEAN THE BUILD IN MEMORY CHIP HAS BEEN PHYSICALY DAMGED ONLY REBALLING OR CHANGING THAT CHIP CAN ONLU SOLVE YOU PROBLEM THERE IS NOTHING U CAN SOLVE THIS BUY SOFTWARE ITS NOT A SOFTWARE PROBLEM..................
What planet are you living on mate??? Its nothing to do with a damaged memory chip. Its cause a flash failed and the boot loader is looking for a partition that doesn't exist cause its not all there.
If you must post please make sure you have a clue what you're posting...
Sent from my GT-I9000 using XDA
[email protected] said:
i have same problem any one have that solution?
Click to expand...
Click to collapse
First of all what is the error its giving when you boot? Once you post that I can hopefully help.
Sent from my GT-I9000 using XDA

[Q] Confusing software brick

Hey all:
While I consider myself quite technologically inclined, it appears that what I think and what reality is are quite different things. Thus, I look for advice from this wonderfully adept community (I've surfed around quite a bit, but I've never had to ask anything).
Here are my phone's specs:
Model: i9020A
Carrier: Koodo
The short story:
because, currently, there's only ICS for the GSM version of the phone, I thought I'd try flashing the GSM version of ICS onto my phone, then load the radio settings for my phone type so that it would work. It didn't. I was able to load ICS, and it worked great; the radio settings for the i9020A, however, didn't load up. As a result, I tried to reload the stock 2.3.6 onto the phone, and I seemed to have failed miserably.
I'm now at the following point:
Normal boot: only loads to the Google screen (with the padlock)
Fastboot Mode: here's the information.
Product Name - HERRING
HW Version - REV 16
Bootloader Version: I9020XXKL1
Baseband Version: I9020XXKI1
Carrier Info: ATT
Serial Number: 3935CEB394BE00EC
Lock State: Unlocked
When I select "Recovery," it briefly goes to the Google screen (with the unlocked padlock at the bottom), then loads into ClockworkMod Recovery v3.0.0.0
Here are the below options:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sd card
- backup and restore
- mounts and storage
- advanced
- GO BACK
Below these options is the following information:
ClockworkMod Recovery v3.0.0.0
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
Essentially, what I am asking is if there is anyway to load the original 2.3.6 for the i9020A on here. If I'm able, then I'll patiently wait for the ICS OTA.
Any help that anyone can provide would be immensely appreciated. If there's any other information I can provide, such as pictures, I'd be more than happy to provide that.
Thanks so much.
rcm8 said:
Hey all:
While I consider myself quite technologically inclined, it appears that what I think and what reality is are quite different things. Thus, I look for advice from this wonderfully adept community (I've surfed around quite a bit, but I've never had to ask anything).
Here are my phone's specs:
Model: i9020A
Carrier: Koodo
The short story:
because, currently, there's only ICS for the GSM version of the phone, I thought I'd try flashing the GSM version of ICS onto my phone, then load the radio settings for my phone type so that it would work. It didn't. I was able to load ICS, and it worked great; the radio settings for the i9020A, however, didn't load up. As a result, I tried to reload the stock 2.3.6 onto the phone, and I seemed to have failed miserably.
I'm now at the following point:
Normal boot: only loads to the Google screen (with the padlock)
Fastboot Mode: here's the information.
Product Name - HERRING
HW Version - REV 16
Bootloader Version: I9020XXKL1
Baseband Version: I9020XXKI1
Carrier Info: ATT
Serial Number: 3935CEB394BE00EC
Lock State: Unlocked
When I select "Recovery," it briefly goes to the Google screen (with the unlocked padlock at the bottom), then loads into ClockworkMod Recovery v3.0.0.0
Here are the below options:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sd card
- backup and restore
- mounts and storage
- advanced
- GO BACK
Below these options is the following information:
ClockworkMod Recovery v3.0.0.0
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
Essentially, what I am asking is if there is anyway to load the original 2.3.6 for the i9020A on here. If I'm able, then I'll patiently wait for the ICS OTA.
Any help that anyone can provide would be immensely appreciated. Thank you all kindly in advance.
Click to expand...
Click to collapse
Do you have a backup that you can restore? If not, grab the 2.3.6 update from here http://forum.xda-developers.com/showthread.php?t=1063664 and try a flesh install.
You should also flash a new radio, I didn't have any luck with the KI1 radio on my i9020a.
Not saying this will help at all but have you tried the latest version of clockwork mod your version seems to be very old. Try this one and see if it helps Clockwork 5.0.2.3
Thanks a ton for this. I'm a bit of a noob with this, so any other information, i.e., how to flash it properly, would be super helpful.
Again, thanks a bunch for the reply!
rcm8 said:
Thanks a ton for this. I'm a bit of a noob with this, so any other information, i.e., how to flash it properly, would be super helpful.
Again, thanks a bunch for the reply!
Click to expand...
Click to collapse
Download this LINK put it on your internal sd card boot up into recovery then do a full wipe in clockwork mod and flash the ROM it contains recovery, radio and bootloader. So you will be back to stock and can follow one of the guides on here to get back onto which every rom you choose.
Will do.
Thanks again!
FeaRThiS said:
Download this LINK put it on your internal sd card boot up into recovery then do a full wipe in clockwork mod and flash the ROM it contains recovery, radio and bootloader. So you will be back to stock and can follow one of the guides on here to get back onto which every rom you choose.
Click to expand...
Click to collapse
Okay, so I've downloaded the file, then put it onto the sd card.
I then boot into Fastboot Mode, then go to Recovery. I do the following here:
- wipe data/factory reset, then "Yes - delete all user data". It says the following:
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
E: format_volume: no MTD partition "cache"
Formatting /sd-ext. . .
Formatting /sdcard/.android_secure. . .
Data wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went into "advance" and "Wipe Dalvik Cache" (which works)
I also did "wipe cache partition," and it says the following:
-- Wiping cache
Formatting /cache
E: format_volume: no MTD partition "cache"
Cache wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went to "install zip from sd card," then "choose zip from sd card," then chose the file that you LINKED to (0b9c8148de0d.signed-sojua-ota-189904.0b9c814)
It says:
-- installing <the above file name>
E: can't find misc
Finding update package
Opening update package
Installing update. . .
then there's a bar, which never fills; it then goes to the following text:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E: Error in /sdcard/<the file name from above>
(Status 7)
Installation aborted.
I'm pretty stuck. Anything else you might have would be fantastic!
Thanks again.
tehgeekguy said:
Do you have a backup that you can restore? If not, grab the 2.3.6 update from here http://forum.xda-developers.com/showthread.php?t=1063664 and try a flesh install.
You should also flash a new radio, I didn't have any luck with the KI1 radio on my i9020a.
Click to expand...
Click to collapse
Yeah, I tried flashing the original 2.3.6 from that page, but there's no luck . . . :S
Thanks for the reply, though! Do you recommend anything else?
rcm8 said:
Yeah, I tried flashing the original 2.3.6 from that page, but there's no luck . . . :S
Thanks for the reply, though! Do you recommend anything else?
Click to expand...
Click to collapse
What do you mean "no luck"? What error did you get? Did you get the right version?
If you're on a i9020A you should be using this one - http://goo.gl/nN0Zp (Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.)
rcm8 said:
Okay, so I've downloaded the file, then put it onto the sd card.
I then boot into Fastboot Mode, then go to Recovery. I do the following here:
- wipe data/factory reset, then "Yes - delete all user data". It says the following:
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
E: format_volume: no MTD partition "cache"
Formatting /sd-ext. . .
Formatting /sdcard/.android_secure. . .
Data wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went into "advance" and "Wipe Dalvik Cache" (which works)
I also did "wipe cache partition," and it says the following:
-- Wiping cache
Formatting /cache
E: format_volume: no MTD partition "cache"
Cache wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went to "install zip from sd card," then "choose zip from sd card," then chose the file that you LINKED to (0b9c8148de0d.signed-sojua-ota-189904.0b9c814)
It says:
-- installing <the above file name>
E: can't find misc
Finding update package
Opening update package
Installing update. . .
then there's a bar, which never fills; it then goes to the following text:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E: Error in /sdcard/<the file name from above>
(Status 7)
Installation aborted.
I'm pretty stuck. Anything else you might have would be fantastic!
Thanks again.
Click to expand...
Click to collapse
Could be wrong but that looks like your partition tables got messed up at some point.
EDIT you could also try looking on here might be helpful LINK
EDIT X2 Other people have screwed up their partition tables and have fixed it using this guide LINK
tehgeekguy is right, if your model number is I9020A then it should work using the rom he linked, did you install Clockwork 5.0.2.3 before trying to install the stock 2.3.6 rom, if not then please try.
Yeah, that's the one I tried, but I received the same error message as before:
-- installing <the above file name>
E: can't find misc
Finding update package
Opening update package
Installing update. . .
then there's a bar, which never fills; it then goes to the following text:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E: Error in /sdcard/<the file name from above>
(Status 7)
Installation aborted.
I'm going to try it one more time to see if I can't get it working. I have a feeling my partitions may have been messed up . . .
Thanks for the reply.
d.chatten said:
tehgeekguy is right, if your model number is I9020A then it should work using the rom he linked, did you install Clockwork 5.0.2.3 before trying to install the stock 2.3.6 rom, if not then please try.
Click to expand...
Click to collapse
Yeah, I'll be sure to try this right away.
Thanks a ton.
FeaRThiS said:
Could be wrong but that looks like your partition tables got messed up at some point.
EDIT you could also try looking on here might be helpful LINK
EDIT X2 Other people have screwed up their partition tables and have fixed it using this guide LINK
Click to expand...
Click to collapse
I'll definitely take a look at this. Thank a bunch!
The partitions is probably right, have you tried with the stock recovery instead of clockwork, worth a try.
d.chatten said:
tehgeekguy is right, if your model number is I9020A then it should work using the rom he linked, did you install Clockwork 5.0.2.3 before trying to install the stock 2.3.6 rom, if not then please try.
Click to expand...
Click to collapse
So, I went to the page and downloaded the following file:
"Option for no confirmation at all. Just flash in recovery.
signed-noconfirm.zip"
I put this onto the sd card, then attempted to install. This is what I received:
"-- Installing: /sdcard/signed-noconfirm.zip
E: Can't find misc
Finding update package . . .
Opening update package . . .
Installing update . . .
Installing .no_confirm
use at your own risk!!
reboot recovery and enjoy!
Install from sdcard complete"
Thus, it seemed to work pretty well. I thus rebooted recovery, but ClockworkMod is still showing that it's version V3.0.0.0.
Should I be flashing one of the other options on that page? If so, which one? And would you, by chance, have a detailed explanation as to how to go about doing that?
Thanks so much. I'm starting to feel like I won't be getting anywhere . . . . The responses have been awesome, though, everyone. I really appreciate it.
You have been trying to install a switch to turn off confirmations, to get Clockwork 5.0.2.3 installed you will need to use the same method as when you installed Clockwork 3.0.0.0 but use this image > 5023-cyan.img.
d.chatten said:
You have been trying to install a switch to turn off confirmations, to get Clockwork 5.0.2.3 installed you will need to use the same method as when you installed Clockwork 3.0.0.0 but use this image > 5023-cyan.img.
Click to expand...
Click to collapse
Makes a lot of sense. I'll try that.
Thanks.
d.chatten said:
You have been trying to install a switch to turn off confirmations, to get Clockwork 5.0.2.3 installed you will need to use the same method as when you installed Clockwork 3.0.0.0 but use this image > 5023-cyan.img.
Click to expand...
Click to collapse
Okay, so I flashed Clockwork 5.0.2.3, then I flashed the correct i9020A package. It worked beautifully.
Thanks a ton, everyone, for all your help. This is great!
Clad it worked for you.

[Q] Urgent - Boot loop and unable to restore to stock.

Alright guys, I've got a question. I have my brothers nexus s that has had CM9 A11 on it and we decided to move to the latest CM9. Long story short, I am no longer able to boot the phone up, but can only access CWM Recovery and Bootloader/Fastboot mode. Trying to boot results in a bootloop. I need help getting this thing back to stock however I can. I've tried to flash recovery.img via fastboot but cannot get my computer to recognize the phone in order to do what I need. He would like his phone back ASAP and I hate to tell him its bricked for a few days. Thanks!
Download full OTA ROM from the link in my signature. Boot into CWM, mount USB storage, and transfer the file to SD card. Flash it. Done.
Just make sure you download the correct ROM for your phone model.
Sent from my Nexus S using xda premium
Video on that page will show you how to install drivers on a windows-based machine to recognise the phone for fastboot, and provide files to do so.
Also, can't you go into CWM --> mounts and storage --> mount usb storage (while plugged into the computer) then copy over any files you need, then flash through recovery.
I forgot to mention that I am getting this when trying to format cache:
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/latest_log
E:Can't open /cache/recovery/latest_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
I tried to install the OTA update like you said but got the following:
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/(OTA file name here)
(status 7)
Installation aborted.
Maybe the internal SD card is bad? Any thoughts?
When you get the drivers installed, download the latest 5.0.2.0 CWM from here.
Alright, so I got fastboot to recognize the phone, but am having another problem. It gave me an error when I gave the command to flash the new CWM. I tried to install pdanet for the drivers, and the phone says at the bottom "FASTBOOT STATUS - FAILInvalid Command". I really think something has been corrupted, any ideas on how to fix it/restore it? Thanks for all the help guys.
Fastboot status is not a command.
Fastboot devices is the command you use to test if it sees the device . The serial number will show.
uh oh sounds like someone flashed brickROM V1
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

[Q] HELP- Nexus S bootloop, cache not mounting.

Hi, I was trying to install an ICS ROM on my Nexus S i9020a last night, and I must have messed something up. The ROM installed but it just hung on the google logo. So I went back into recovery (CWM 3.0.0.5) to restore my nandroid backup but I got:
E:format_volume: no MTD partition "boot"
Error while formatting BOOT : !
E:Failed to find "cache" partition to mount at " /cache"
E:Can't mount /cache/recovery/last_log
E:Can't mount /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partiton to mount at " /cache"
I don't know much about what these things, but I imagine the seemingly missing cache is the problem. I cannot mount or format the cache either. I get similar errors. Flashing roms seems to 'work', but I still get the bootloop. Flashing img's does not work. "Installation aborted".
I have no idea what I can do to reverse this. At this point, I want to restore to stock. I hope I haven't done permanent damage. Can anyone please help me with this?
First try to upgrade to the latesy cwm. It had very much bugs fixed
Sent from my Nexus S using xda premium
Computer doesn't seem to recognize the phone in fastboot mode, can you link me to the a newer CWM zip so I can flash it in recovery?

CWM errors

Ok, so first of all, the current firmware on the phone keeps crashing every 5 seconds, and some recovery log process keeps forceclosing, so I NEED to get a new rom. This current one is not functional.
I finally downloaded a ROM, and put it on the root of my SD card.
Now, when I booted to CWM (holding vol up and vol down, and holding power), I get some errors.
It looks something like this:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter: POWER Key. Select : Vol UP/ Vol Down
reboot system now
reinstall packages
delete all user data
delete cache data
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(Invalid Argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(Invalid Argument)
And so the CWM is messed up.
Now the menu looks something like this, (Totally different from what I've seen before)
Any idea how to get cwm functioning? By the way, I did not use ROM manager. Heard it messes stuff up.
Thanks.
Use the guide in the second link in my signature.
lumin30 said:
Use the guide in the second link in my signature.
Click to expand...
Click to collapse
Thank you sooooo much :laugh:
I finally fixed my phone!

Categories

Resources