My I9003 Is Dead...After Flash - Samsung Galaxy SL i9003

My I9003 Is Dead...After Flash
after i flash I9003JPKP5 all is done but phone run to 3e recovery
and show this error message.
E:can't mount/dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:can't mount SDCARD
your storage not prepared yet.please use UI menu for format and reboot actions.
copy default media cantent failed.
i try to reboot but that phone wont go in UI menu...
now keep restart

Just reflash using odin following insturctions closely. Its a soft brick, nothing to worry about.
Cheers
Sent from my i9003 powered by Cyanogenmod 7

ngagegames said:
My I9003 Is Dead...After Flash
after i flash I9003JPKP5 all is done but phone run to 3e recovery
and show this error message.
E:can't mount/dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:can't mount SDCARD
your storage not prepared yet.please use UI menu for format and reboot actions.
copy default media cantent failed.
i try to reboot but that phone wont go in UI menu...
now keep restart
Click to expand...
Click to collapse
Here's a step by step tutorial on how to recover a soft bricked I9003

Your storage not prepared yet
I am getting the same error message after flashing to xxkpe, is there a fix for this?

redcarullo said:
I am getting the same error message after flashing to xxkpe, is there a fix for this?
Click to expand...
Click to collapse
facing the same problem...pls help
i dont know my base number also..

http://plusandroid.posterous.com/recover-a-soft-bricked-galaxy-sl-gt-i9003
Have you all tried this tutorial?

stuck on sumsung logo
i can enter into download mode with simple vol down+ok+power...i also flashed it with xxkph (i dont know my base model number)..but still same stuck on sumsung boot ... and error like can't mount sdcard

You guys should try this....hope it helps.
http://forum.xda-developers.com/showpost.php?p=26505576&postcount=1295
Don't forget the thanks button

Related

[Q] HELP! I cant boot my device after updating to froyo 2.2 vibrant

So i followed i guide to install the froyo 2.2 update to my samsung galaxy s vibrant tmobile version.
my issue all seemed to go fine till it rebooted.
this is what i used
Odin 3 v1.0
S1_ODIN_20100512.pit
i9000XXJP2 Firmware
when it boots it goes into recovery utils
says enter: ok key select with vol up or down
i cant get past this screen i cant click ok
at the bottom it says update media. please wait
e:Can't mount /dev/block/mmcb1k0p1
(invalid argument)
e:copy_dbdate_media:Can't mount SDCARD
your storage not prepared yet, please use UI me nu for format and reboot actions
copy default meda content failed
What should i do now it wont boot?? Thnaks

[RECOVERY][UPDATE] Unofficial port of ClockworkMod Recovery for folio100 - BETA

This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
boot part is not backup when using Backup / Restore.
Update 1 : Cache is mounted at start
Installation instructions :
Download : update.zip
- Copy the update.zip to a sdcard
- Follow the same procedure as explain in this post for the FolioMod
- Don't need to wipe.
- After reboot, enter recovery again to see the change
Click to expand...
Click to collapse
Usage :
- ( VOL + ) and ( VOL - ) key to highlight the menu
- ( HOME ) key to select
Click to expand...
Click to collapse
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
wolfx said:
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
partitions do not mount automatically at startup
boot part is not backup when using Backup / Restore.
Installation instructions :
Usage :
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
Click to expand...
Click to collapse
this will be so great, good joob and keep em comming. Next stop Gingerbread
Installed it just aminute ago worked great. I played around a bit, i formated system, data, cache and dalvik cache. I also tryed format boot but that was a no go. In the first clockwork 3 releases there was also this problem with boot. i cant remember if it was the same error, but its fixed now so that it works correct. I also flashed FolioMod from clockwork iwth out any problems. Really nice work
Great Job!! Now we just need some AOSP/CM7 love
Can I use it with stock rom too? Tnx
Great work thanks alot for taking the time to do this
girello71 said:
Can I use it with stock rom too? Tnx
Click to expand...
Click to collapse
I don't try backup / restore (nandroid) with stock rom maybe it work, but when i try to flash stock rom it skip the different part and don't write anything.
However, what could be interesting if backup / restore work is to make a backup of a fresh install stock rom with the last update include.
boqonx said:
Great Job!! Now we just need some AOSP/CM7 love
Click to expand...
Click to collapse
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Of course dude, take your time and slowly churn that tasty gingerbread dough
wolfx said:
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Click to expand...
Click to collapse
Finaly, one more rom builder. We need some options to choose from. Wish you the best of luck. And if you dont mind, maybe from time to time post progress on your work. If you need some beta testing, im there
Back to square 0
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
If you delete the update.zip for clockwork recovery you will have normal recovery. When installing clocwork you pu the zzip to root of exterenal sd card boot to recovery do system update, device reboots, now you have to do the system update again, your now in clockwork recovery
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
Not sure you bricked it, you can use the fastboot method to flash the recovery again, then you can use the recovery to flash a full rom.
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
boqonx said:
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
Click to expand...
Click to collapse
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
wolfx said:
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
Click to expand...
Click to collapse
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
wolfx said:
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
Click to expand...
Click to collapse
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
nickwarn said:
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
Click to expand...
Click to collapse
Rom manager don't work with this recovery for now, official support must be added by Koush in rom manager before. I will commit the source to him when recovery is finalized.
Butchi said:
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
Click to expand...
Click to collapse
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
- start your folio in fastboot mode and plug in. Win will not find the right driver to use
- Force driver installation : click update driver -> have disk -> point to "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Choose bootloader driver
After this you normally can use fastboot place in : <your-android-sdk-folder>/tools
For the recovery.img you can use the one include in the update.zip or one from FolioMod.
Hope it can help you
I am still not there...
Again thanks for all the help and support
OK I installed the SDK (and the JRE as it was also a requirement). But i did not find the USB driver so far (which is strange because i had connected the folio with the PC earlier).
While doing all that i discovered that somehow the ClockworkMod Recovery was installed correct. I could get the expanded ClockworkMod menu. (Using the power button and simulteaneous the Vol+ button within the 3 sec. And whatever i selected update or recovery, i got to the ClockworkMod menu.) This looked promissing.
So i put an update.zip on the sdcard (dextermod 1.3b).
In the menu i selected 'apply sdcard:update.zip'. After this i got the screen (white text) Confirm install? THIS CAN NOT BE UNDONE and (yellow text) 7 lines with '-No', one line with '-Yes - install /sdcard/update.zip' and 3 more lines with '-No'.
After selecting the 'Yes' line i got the following messages:
--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted
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
Strange enough, even after the update was aborted, the system started again after i selected to reboot in the ClockworkMod menu. Wow. Who knows what happened may explain this. But nice for me the system works again (till the next time).
Looking very nice. Just flashed it and made a backup

[Q] PLEASS !HELP! HELP! moto DROID 2 E:can't open /cache/recobery/com

please i need help with my MOTOROLA DROID 2 i had rooted my droid like 2 months ago, at that pint was everything oK. but then i looked on room manager for updates and i found the that says OTA and at that point i had installed gingerbread room on my device everything was good but when i was downloaded the file it stopped without a reason and i started to dowload again this time was complete and when i TRIED TO INSTALLED IT THE PHONE SHOW
This message:
Android sistem recovery<3e>
use volume up/down to highlight and camera to s
reboot sistem now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
E:can't open /cache/recovery/command
WHEN I APPLY SDCARD:UPDATE.ZIP
IT SHOWS
- -install from sdcard. . .
. . .finding update package. . .
openin update package. . .
verifying update package. . .
E:failed toverify whole-file signature
E:signature verification failed
installation aborted
please help me
Please flash any other recovery because you are in stock recoveey
Forever living in my Galaxy Ace using XDA App
how do i flash it
can you tell me how do i flash mi phone on the way that you say
i don't know how to do anything with my droid cause i cant turn it on and when i plug it un all what it does is shows the big letter of motorola the "M" AND I HAVE TO GLUG ITIN AND THEN TRY TO GO RECOVERY MODE AND IT JUST SHOW THE TRIANGLE AND THE"!" AND I CANT GO TO THE RECOVERY MODE THE WAY THAT IT SUPOSSE TO DO IT AND WHEN I PRESS THE LETTERS AROUND THE "Z" IT SHOWS android sistem recovery please help me
Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] Help : My Phone isn't detecting in Odin

Not being detected in Odin3 1.3, 1.83, 1.85, Drivers are installed properly, Tried in two systems and all USB ports, I had flashed UC V8, Was in MIUI and was updating when new updates were releasing through CW mode, Even had tried cm7 V2, now the USB mass storage isn't working, its just charging, and when i go to download mode and connect to system with Odin on, phone isn't detecting, USB Debugging is checked, Firewall and anti virus is off.
Working : CW mode, can flash through that.
Can not bear battery drain anymore in MIUI, so going back to Stock/Titanium.
My phone is Samsung Galaxy Sl I9003
Can you tell us what did u do before this happened?
First i was in stock KPN, then i flashed UC V8 and then through CW mode i flashed zip file of MIUI 9, then when update came, i had inatalled zip MIUI 10 through cw mode, then since there was heavy battery drain, i flashed cm 7.2, but since i used to like UI of MIUI and no change in battery drain, i flashed MIUI next version.. between this, i forgot till when i could do mass storage, but suddenly few days back it was just battery charging when i connect to sys, then i thought it will be fine if i go back to stock( also battery is better in that)/ thought to install titanium rom DDKP3, but now to do that, odin is not detecting device..
driver is installed properly, tried uninstalling and installing, tried in diff systems, diff cables, all the USB ports, but its just getting charged, USB Debugging is checked..
Help please..
recovery and downloading mode working.. i can also flash from zip files without any problem..
Re install...
RE
install drivers........kies
check ur ports....
download new odin.....
check ur usb cable....try ur friends..
nd finally if all is good...nd still nt working..
format ur windows..
Hope this helped
He tried on two systems, I guess its not Windows. When you connect your running device (not download mode) do you hear that typical device connected sound?
Sent from my GT-I9003 using XDA
YEAH...
Im in w7..
I also hear while in download mode.......also..dat tring
I guess it would be driver(kies)problem.....
Sure this would also work in download mode, but if she does, I wanted to ask whether she is able to communicate with the phone over adb or not...
If yes -> Some strange problem. Try to reinstall the drivers, but i think she has a low chance that this will work.
If no -> Probably the drivers are damaged?!? The system recognizes a usb device. Try a reinstall...
If she doesn't even hear a sound from her computer its something with the phone that probably only gets charged due to voltage on the usb port...
Sent from my GT-I9003 using XDA
Even i face this problem in MIUI. USB storage works occasionally for me. When it worked i had transferred CM7 rom.
USB works in CM7 but not in MIUI for me. So it isnt any driver problem on the pc.
my samsung galaxy s gt i9003 mt booting
my samsung galaxy s gt i9003 stop on booting screen hang on startup screen
When I tried to enter in "Recovery mode" it give followin massage:
Android system recovery <3e>
Enter : Ok Key, Select : Vol Up/ Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
---------------------------------------------------------
E:failed to mount /data (no such file or directory)
--Copying media files...
Sucessfully copied media files.
# MANUAL MODE #
-- Appling Multi-CSS...
Installing Multi-CSS
Can't access to '/system/csc/INU/system/'.
Successfully applied multi-CSS.
and sometime When I tried to enter in "recovery mode" it give followin massage:
Android system recovery <3e>
Enter : Ok Key, Select : Vol Up/ Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
---------------------------------------------------------
E:failed to mount /data (no such file or directory)
--Copying media files...
E:failed to mount /data (File exists)
E:copy_cache_media:Can't mount /sdcard
your storage not prepared yet, Please use UI menu for format and reboot action.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSS...
Installing Multi-CSS
Can't access to '/system/csc/INU/system/'.
Successfully applied multi-CSS.
its not detecting in odin also
someone help me plz
try to take away external sd card and sim i got the same problem on the original froyo rom and was unable to update the phone whitout pulling them out (both odin and kies was unable to recognize the phone but i was able to use it as mass storage)

Micromax funbook keeps booting into recovery - help

okay, so, i tried to install CWM on my micromax funbook P255 using Novatools or something.
and now, it keeps booting into recovery (v5.5.0.4 for SmartPad 907c)
and it gives this log below -
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've tried flashing a new recovery
when i do 'adb devices', it shows my device in recovery
when i do 'flashboot devices' it doesn't show my device at all
when i try to 'flashboot flash recovery recovery.img' it is stuck on waiting for device.
there's no external SD card yet, but I have a spare one which I tried
I put the recovery.img in a 'newzip.zip' and put the SD card into my tablet, and then tried to install the update from the .zip, but it said 'installation aborted'
i just got this tablet yesterday, i NEED to fix this by myself anyhow!
i've rooted my HTC One V before, so I do have basic rooting experience.
I just want to get my tablet to work, f*ck the root and recovery, just anyhow it can functional normally!
also, there's a reset pinhole at the back, but i don't think it's working, i put a pin in there and nothing happened at all..
help
hey i am having almost the same problem
i have micromax funbook P255
i wanted install custom ROM but i first flashed cwm recovery (cwmics.rar)
when it booted to the recovery, the volume up and down keys are not working only power button for selecting
"reboot" option is highlighted and when i press the power button it shows the boot screen and again comes to the recovery
it is also showing at the bottom
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
WHY IS THIS HAPPENING??????????
PPLLEEAASSEE HELP ME FROM GETTING OUT THIS HELL...FOR GOD'S SAKE...!!!
help pls
same problem here.
why the developers then post these kind of recoveries without checking.
feeling very bad.helpless
OK, reflash your stock firmware using live suite. You can get your Micromax P255 stock rom from this link- can't provide link because i am a new memberjust google android 4.0.4 stock rom for micromax funbbok p255.Then click the first link . Scroll down to the bottom and you will see the Mcromax P255 rom . Just download it.You get A zip File. Open it .It contains Live suite and the rom. how to use Live Suite ? Google it .
I had this problem.Fixed it yesterday using this method
This..is a common type of error with the micromax devices with cwm...which often results into imperfect flash.
Your device might be going in boot loop...
Solution;
Open the flashing software(i hope you would be using spreadtrum flashing software;Research Downloader) you are using open the stock image(To find yours google"Micromax all Stock Roms")
Connect your device randomly between vibration ...
You will observe that your computer will load the drivers then suddenly your phone will reboot
Identify the time driver loads ...
Run the system flash software though drivers aren't identified ...
Hold on the flash key(look up on google each set has different pattern) pattern of your phone and plug in cable(iam assuming that usb cable can be used to flash many other standard cable are used i had to cut the supply wire for mine to mske it flashable) at random times it will work.
PRESS THANKS If I was of any help.
Sent from my Micromax A65 using XDA Free mobile app
As of now there is no cwm recovery compatible vid our p255 ..but if u jus want to use ur tab den flash p255 stock firmware from tabletguru website....
Plzzz hit thnx if i helped

Categories

Resources