Database Info

[Q] Nexus S - lost my bootloader img - help needed

Like a complete prat, I have lost my boot and recovery img!!!
I was trying to get clockwork recovery as the recovery img and then accidentally did:
fastboot flash boot recovery.img
instead of
fastboot flash recovery recovery.img
I have found an unlocked bootloader from here (third one down) http://forum.xda-developers.com/showpost.php?p=9869067&postcount=38
I have saved this to the AndroidSDK\tools file as bootloader.img and tried the below whilst in fastboot mode:
fastboot flash boot bootloader.img
but the phone only reboots to the fastboot screen.
I now have no phone and I need it for work, can anyone help me, im desperate?
Thank you

Why not just flash cwm recovery then flash a ROM?
There's a sticky in this forum section with almost all full ROMs (stock Android, no need to flash cwm recovery for the signed ones, can use stock recovery) or head over to dev forums and look for a custom ROM you like (need cwm recovery).
Be sure to pick the right ROM for your device.

you don't need a bootloader! you need a boot.img! a kernel with ramdisk! ^^
Sent from my Nexus S using XDA Premium App

If the following command was executed successfully:
Code:
fastboot flash recovery recovery.img
Next step is to download a ROM of your choice and flash it via ClockWorkMod recovery and you're good.
FYI, the command
Code:
fastboot flash boot ...
does not flash your "bootloader". It is used to flash the kernel, which will already be included in the ROM you downloaded.

meso100 said:
...instead of
fastboot flash recovery recovery.img
I have saved this to the AndroidSDK\tools file as bootloader.img and tried the below whilst in fastboot mode:
...but the phone only reboots to the fastboot screen.
Click to expand...
Click to collapse
No problem. Flash your recovery using the correct command (above).
If you have access to fastboot, use your volume keys as up and down, and navigate to the "Recovery" option. When your phone boots into recovery, you can mount your USB and copy a ROM to your device.
Then go back, do a factory/data wipe, and flash the zip you copied. This should restore your phone.
Recovery images:
http://forum.xda-developers.com/showthread.php?t=988686
ROMS:
http://forum.xda-developers.com/showpost.php?p=13556812&postcount=2

Thank you all for your replies and help and apologies for the late delay.
I have been away for a few days and with your help and a bit of playing about I managed to sort out the problem. I was probably a bit hasty to ask for help but actually felt that I had bricked my phone!
This happened because I was following two different fastboot flash guides on the net...lesson being just keep to one!
Also, when I lost cwm I didnt know how to get it back...but again you can only learn from your mistakes and I did.
I managed to get cmw reinstalled and cm7 flashed.
Now I am running the latest MIUI and it is pretty good.
Thanks all for your help, see you the next time I panic!

meso100 said:
Thank you all for your replies and help and apologies for the late delay.
I have been away for a few days and with your help and a bit of playing about I managed to sort out the problem. I was probably a bit hasty to ask for help but actually felt that I had bricked my phone!
This happened because I was following two different fastboot flash guides on the net...lesson being just keep to one!
Also, when I lost cwm I didnt know how to get it back...but again you can only learn from your mistakes and I did.
I managed to get cmw reinstalled and cm7 flashed.
Now I am running the latest MIUI and it is pretty good.
Thanks all for your help, see you the next time I panic!
Click to expand...
Click to collapse
Thanks for using your brain and figuring it out. Congrats on getting it up and running.
Sent from my PC36100 using XDA Premium App

[Q] Xoom memory/flash LOCKED, Can not Factory Default ???

Posted this General, but hope to get a better response in here ...
Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks

Use adb to flash stock imgs. You need to fastboot flash instead of using cwm. Cwm sucks! I refuse to use it because it doesn't seem to flash crap right. Once your rooted you can use it to flash a rom and that's it. ADB is easy as long as you go one line at a time and be patient as you do it. Start with OEM unlock, then flash the boot, recovery, system, erase the cache, and the reboot.
Sent from my Xoom using xda premium

hammer4203 said:
Use adb to flash stock imgs. You need to fastboot flash instead of using cwm. Cwm sucks! I refuse to use it because it doesn't seem to flash crap right. Once your rooted you can use it to flash a rom and that's it. ADB is easy as long as you go one line at a time and be patient as you do it. Start with OEM unlock, then flash the boot, recovery, system, erase the cache, and the reboot.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
All flashboot flash command is confirmed to be working, but i think it's not written to the Xoom memory, because as soon as i boot it, it's just boot into the Old version (the one this is there before flash).
So can not event flash CWM or Rooted ... when i go to Recovery and try update with update.zip, it's alway fail with E: verify something ....
Any other ideal or else ... i guess this is the 1st "Working BRICKED Xoom"

Could be the wrong update file. Make sure of the file as well. Re download it too. Could be corrupted.
Sent from my ADR6400L using xda premium

Oh you need root again? If that's the case you have to adb push the file and update via adb to get there. You can't do it from cwm.
Sent from my ADR6400L using xda premium

hammer4203 said:
Oh you need root again? If that's the case you have to adb push the file and update via adb to get there. You can't do it from cwm.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
His Xoom has been relocked and needs to be unlocked again in order for him to be able to flash anything at all.
This thread is already active in General, don't waste more time here.

Yeah I see that. He needs to fastboot OEM unlock.
Sent from my Xoom using xda premium

Guys, thanks for you reply, but I know how to OEM unlock etc ... i have also make the "factory cable" for it, i have another Xoom that i'm testing all the steps and files and the others Xoom working like charm ... but this one is a [email protected]#%ch ...
If i can only flash CWM and i will be good, because i have make a backup from it to start, but now can not event flash anything to it ... memory seem to be "volatile" so event files that i copy into it will be wipe once the tablet reboot ... so it's beyond flashboot or adb ... i've event gone to RSD Lite but can not fine (or know how to dump my other Xoom) a right dump to flash it from there ...

NS4G- cm9 froze, pulled bat. stuck at boot, can access CWM Recovery, can't mnt SD

I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?

jivetrky said:
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
Click to expand...
Click to collapse
sounds like the sd(storage) is gone bad or going bad.

simms22 said:
sounds like the sd(storage) is gone bad or going bad.
Click to expand...
Click to collapse
Any way I could test that theory, through ADB or something?

jivetrky said:
Any way I could test that theory, through ADB or something?
Click to expand...
Click to collapse
maybe a logcat while trying to access the storage? but really, if it isnt accessible, thats all the info you should need.

Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA

rasengan82 said:
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
the internal storage going bad is actually a very common problem.

I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA

rasengan82 said:
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
How might I go about doing that?

jivetrky said:
How might I go about doing that?
Click to expand...
Click to collapse
fastboot oem lock
with fastboot while in the bootloader. provided that fastboot sees your device(fastboot devices).

Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA

rasengan82 said:
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
very true. but if youre doing it to send back to samsung for a warranty repair, does it matter?

I don't know the inner workings of Android or this device specifically, but isn't there just a single bit of flash on the phone which is divided/partitioned into SD, system, etc. Is it possible that the partitions have just been corrupted or something like that? I was playing around just seeing what the phone could do and Odin3 will recognize it, but I didn't want to play around and screw anything up even more than it is.
Is it possible to use Odin to try and attempt a fix? I see there is a re-partition option, I was wondering if that could be worth a try?

Well, I guess I've given up and I'll just hope for Samsung to replace/fix it.
Google-foo has not shown me anything as far as trying to repartition just in case it was corrupted or something; couldn't find any images out there with PITs. I'm able to write the bootloaders and recovery so I just used the one-click-stock provided boot and recovery images and flashed them with fastboot then locked it.
Doesn't boot and recovery go on the same flash that is theoretically bad which is stopping SD, system, & data from being mounted?

Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot

rasengan82 said:
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I can't unlock it now, as the bootloader pops up a screen that says to unlock it you have to wipe/factory reset. But it hangs on that probably because it can't see system/data.
I did try flashing it with fastboot though, before I locked it, and I could flash boot, recovery, and radio but it will just hang forever on flashing system. It never gives an error. I let it sit there for over an hour and it never did anything.
So I guess now that it's locked there really is nothing I can do.

Ok, I think Samsung warranty is the only thing left.

Forgot to update, sent to Samsung and they replaced the PBA, so the flash was apparently bad. Thanks for the advice, everyone!
Was only about a week turn around, just took me a while to actually get the RMA started.
They even send a UPS label to ship it to them then took a week turnaround, overall it was good service.

[Q] What are the signs of a Bricked phone?

My MT4GS is boot looping. I can get into the bootloader, but can't get into recovery and flashing a stock image doesn't do anything. I've unlocked the phone and achieved S-OFF using the j-bear wire trick. I've ran the phone for a few weeks after getting the s-off, so I don't think it's that. When I flash a stock image from the bootloader, the software/radio versions don't change and it still boot loops. I also have a faint red light in the notification and trackpad. I'm out of ideas. Anyone have any suggestions?

well first thing id attempt is to grab an image of a recovery and try and flash it through fastboot, image HERE
fastboot command
Code:
fastboot flash recovery recovery.img
if you need any further instruction on how to use fastboot you can get some info HERE
or if this dosent work or have more questions feel free to ask
its not a brick if you can get into hboot, you may have a tough time getting your phone working again but usually its doable.
good luck!

Thanks for the quick reply. I did a recovery flash through fastboot (CWM 5.0.2.7), but still couldn't get to recovery. I was able to update hboot to the jb_hboot. That allowed me to perform some more fastboot commands, such as: erase boot, recovery, system, userdata. I then tried to flashed a signed stock image, but still got stuck at boot loop and couldn't get into recovery. I might try TWRP recovery to see if it changes anything.

what all does it say on your bootloader screen now?

It says:
= Juopunut Bear =
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.1313
RADIO-11.16.3504.20_2
eMMC-boot
Nov 21 2011, 20:20:47

Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2

when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.

demkantor said:
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
Click to expand...
Click to collapse
Riyal said:
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
Click to expand...
Click to collapse
I didn't get a fastboot error when I wrote to boot, it said completed and a time. When I choose recovery, I get a boot loop. I can't connect via adb. I don't think I have the right drivers setup for adb because when I type "adb remount" it says no device found.

Drivers taken from weekendsr2shorts mirror thread
it is strange that you can get fastboot working but not adb, but maybe more digging needs to be done to solve that. but it could just be from hboot screen there is no access to adb... come to think of it that sounds normal
try erasing recovery partition and flashing again, maybe there is some corruption there that stuck around even after the last flash
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
see if any of that works

Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?

Not too sure a great way of telling, maybe try reformatting recovery? On a side note what exactly were the stock image you were trying to flash? I believe there is an issue when flashing certain stock setups after the radio s-off, being the way bootloader varifies the radio, recovery, Rom, etc. Sometimes things can go awry when doing this. I don't have a ds yet (still waiting on stupid parts from China) so I haven't done a whole lot of research on this phone. Maybe someone will chime in who knows more specifically what to be looking for
Sent from my Desire Z using xda premium

I tried to flash both "PG59IMG_Doubleshot_TMOUS_1.55.531.3_Radio_11.59.3504.00_11.16.3504.20_2_release_227956_signed" and "PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed". You think I should try a custom ROM instead? Is there one available to flash through the bootloader or fastboot? I tried to flash the signed stock image zips with fastboot, but it complained about not finding expected signature. Sorry to hear about your DS. Hope you get your parts soon.

rumi409 said:
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Click to expand...
Click to collapse
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.

Well you can flash roms through fastboot,
fastboot update.zip
Just change the name of the Rom to what's needed
Maybe try to format as many partitions as you can through fastboot first?
Sent from my Desire Z using xda premium

WeekendsR2Short said:
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Click to expand...
Click to collapse
I flashed this recovery image via the bootloader and fastboot. Still no luck. Is erase and format the same thing? I've erased boot, recovery and system. I checked that they were erased by doing a Image CRC, which resulted in a 0 value. Then flashed the signed DS ROMs. It still resulted in the same, boot loop.

erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation

demkantor said:
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
Click to expand...
Click to collapse
I can't seem to get any of the format commands to work. It just displays the fastboot commands and options, as if I typed something it can't understand.

Have you tried a different SD card?

mattlowry said:
Have you tried a different SD card?
Click to expand...
Click to collapse
I'm not using a micro sd card. Have been flashing through the computer.

rumi409 said:
I'm not using a micro sd card. Have been flashing through the computer.
Click to expand...
Click to collapse
have you tried placing the pg file on your sd card and let the bootloder load it itself?

[Q] Could not mount /data ! Phone Stuck!

I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?

Ensifolk said:
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Click to expand...
Click to collapse
Clean fastboot install :/ Solved the issue for me

try and format cache. If still no luck, fastboot flash cache cache.img

rootSU said:
try and format cache. If still no luck, fastboot flash cache cache.img
Click to expand...
Click to collapse
Can I still fastboot even if I have no USB debugging enabled? The phone will interact with the commands normally? ( Since as I mentioned before I flashed the ROM only to check out and played with no settings at all, didnt know this is going to happen )

Ensifolk said:
Can I still fastboot even if I have no USB debugging enabled?
Click to expand...
Click to collapse
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.

rootSU said:
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
Click to expand...
Click to collapse
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe

Ensifolk said:
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Click to expand...
Click to collapse
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it

rootSU said:
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
Click to expand...
Click to collapse
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )

Ensifolk said:
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Click to expand...
Click to collapse
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.

rootSU said:
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
Click to expand...
Click to collapse
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
EDIT: I renamed the extracted file to .zip and extracted again, now I have the files displayed on that page...Trying to figure out now how to flash the cache.img

Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Extract it again.

Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Its a .tar file. Extract it again

...

I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/

Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010

Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
I think you'v nothing to loose by flashing the whole factory image. If /sdcard can't be mounted in this situation, I think that's because you did (or a toolkit) did something wrong and break it. I don't think that you'll be able to save anything.
(It's my point of view. Maybe somebody else has an idea ?)

rootSU said:
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Click to expand...
Click to collapse
I cannot mount /data even after flashing cache.img - Hence I think I am dead by this stage and I can no more recover whatever I have on the phone. Factory image flashing then ?

Yep, I would

And there we go, I did it, phone back to life. Thank you guys ! A LOT! Appreciated ! pretty much !
Allow me to recall the scenario : I was on Slimkat, decided to try Mahdi Rom ( CM Based ), Backup before flashing, flashed, wanted to revert back. And this can't mount /sdcard there. No idea what could be it...
What recovery you guys recommend me to use ? - Lesson I learned today? I should know how to use fastboot and ditch the Toolkit galore.

Well, seems that you did'nt do anything wrong. Maybe a problem with the rom or something else occur.
Next time, maybe, do a backup and, then, copy it to your computer
For the recovery, I use CWM 6.0.0.4