Hello,
I apologize if im violating any rules here, but the problem is making me so sick that i dont know what else to do ..
i recently got a i9000, locked to THREE.. had it unlocked, tried to update it via KIES but bricked on the Samsung S (static splash screen).. i tried a couple of firmwares, 2.2's and 2.2.1 (XXJPU) included.. all would just sit at the splash screen doing nothing.. even left it like that for an hour, but still nothing ..
im not sure what to do here. . whenever im stuck, i flash JM8 and while booting it gives me the following:
E: Cant't mount /dev/block/stl11
(invalid argument)
multicsc : cannot access to /system/csc/H3G/system/
copy_common_data E: Cant mount /dev/block/stl11
(Invalid Argument)
E: Can't mount /dev/block/stl11
(Invalid argument)
this only occurs once, once i select reboot system now it reboots fine and after that all other reboots go fine..
another thing that happens is that whenever i flash another firmware via ODIN, i cannot get the 3 -button recovery to work only the download.. while the 3 button recovery works on JM8
please help me.. this fone is driving me crazy
Have you tried re-partitioning in Odin before flashing?
Check re-partition, select correct pit-file, plug, flash, unplug, remove batt for 30 secs, uncheck re-partition, NO pit, select pda, modem, csc, plug, flash -> should work.
i actually tried a different trick to get rid of the errors ..
i used the modem and pda files from JM8 and the CSC file from JPU .. with repartition ticked i used the 512.pit to flash the phone via Odin.. all the errors went away .. well almost .. the phone started throwing a new error .. couldnt mount /dev/blocl/memblk10 or something ..
well .. thats something for the past now.. i got my cell changed .. things seem fine now .. thnx
For anyone checking this thread later for a solution...
I had the E: Cant't mount /dev/block/stl11 error myself and was able to recover via some combination of repartition and supplying a pit file. However, I was simply using a stock firmware for my phone (JH2 with 512 PIT). No fancy pda/modem/csc mixing needed for me
Related
I have just bought galaxy s and i flashed to jm5 then used samset 1.9f then i think i have some fixlag on. BUT SUDDENLY WHEN I TRY TO REFLASH TO JM5 MY SGS GOT BROKEN??? i took some pic but how i add them here //sorry i am very new user
On screen all iget for options is these:
Android system recovery <2e>
Samsung Recovery Utils
- for BML-
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
----------------------------------------------
update media. please wait...
E:Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Have you tried to reflash your Galaxy with Odin?
Downloads:
Odin
JM5 Firmware PASS: samsung-firmwares.com
PIT 512
Howto:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (PDA=CODE, .PIT and PDA are required. CSC and Modem are HIGHLY recommended. They may be necessary depending on the PDA! Try flashing all three BEFORE reporting bugs, if you only used one initially!)
3.Remove the SD card and SIM card from the phone.
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.If the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
http://forum.xda-developers.com/showthread.php?t=723596
Your SGS is not broken you are just doing things without the right knowlegde.
Don't do things you don't understand !!!
Read before you do something !!!
Yes i have flashed mtimes with odin and successfully but this time its differrent i can't flash any rom and i keep having that error above
Welll it worked when i changed the .pit file which came with Odin to your .pit file and mine was 513 yours 512...but at the end when it booted there was one red line about some sytem ... it went fast so i could'nt read it but anyway thnx alot
You always have to use the correct PIT File for a Firmware.
Look at this:
http://samsung-firmwares.com/I9000.htm
Please read the FAQ Thread. ;-)
RTFM
10char
Hi Guys,
Just tried to flash from JG4 to JM8,
I followed the instructions as per http://forum.xda-developers.com/showthread.php?t=809423
Before i started i removed voodoo lagfix with the disable-lagfix method, then i did a factory reset.
I was up to step 2, that worked fine in Odin, then when i went to restart i got this error : can't mount \dev\block\stl11
any ideas what went wrong?
Thanks
Emm, what instructions have you followed? The link you gave is for kies and 2.2, not 2.1 and odin.
My guess - something to do with pit files and repartitioning. JG I think needs 513, while JM need 512, so repartition and try flashing one more time.
This does not belong in the development section ! The link you give is for update to froyo using kies .. You have flashed JM8 that is not froyo ! So make your question more clear and post it in q&a .. Anyway the error you get has to do with repartioning .. Flash JM8 again with odin check repartition and use .512 pit
sorry http://forum.xda-developers.com/showthread.php?t=807886
that is the correct link.
I used pit 512...
Edit: re-partition was checked and i definatly used pit 512... do you think voodoo had something to do with it?
reflashed again and and this is full error i receive in recovery;
E:Can't mount /dev/block/stl11
(Invalid argument)
update media, please wait....
update media, finished
# MANUAL MODE #
-- Applying Muti-CSC...
Installing Muti-CSC
mps_dat value: OPS
copy_multi_carrier from: OPS
multicsc : can not acces to /system/csc/OPS/system/
copy_common_data E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount /dev/block/stl11
(Invalid argument)
Do not leave csc blank in first step (flash to jm8). No idea why someone wrote it.
Hi,
i had the same problem flashing from JM5 to JM8.
When i clicked on reboot the system started without problem.
Then I flshed to JPM --> no problems either.
jahash said:
I was up to step 2, that worked fine in Odin, then when i went to restart i got this error : can't mount \dev\block\stl11
any ideas what went wrong?
Thanks
Click to expand...
Click to collapse
What happened is you probably flashed using Re-Partition but your PDA and/or CSC was missing the cache.rfs file.
If you tick Re-Partition, you MUST flash the complete set of firmware files (those that include cache.rfs and dbdata.rfs) otherwise you'll get errors like that.
To fix it you have to flash again with Re-Partition and make sure this time your PDA or CSC file has the cache.rfs and dbdata.rfs file inside. You'll lose all your app data, so backup first.
Next time when u flash, don't Re-Partition unless you know you need to. For example, the official JPM/JP6 Froyo update files do not come with a dbdata.rfs, so if you (wrongly) click Re-Partition when u flash them, you're gonna get a similar error but with the /dbdata partition instead.
Had the same problem when I forgot to do disable OCLF on one of my reflash.
I repartitioned, then flashed to JM8 with odin without repartioning (all pit 512) and worked like a charmed.
The only time i get this error is when i flash a FW and it requires a diff pit file.
I am getting a similar error when attempting to "format internal sd-card" in recovery mode.
I get the following error:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Similarly, I didn't remove OCLF before I attempted to flash XXJPM using Odin, so maybe it has something to do with that?
Does a full flash overwrite any changes made by OCLF? If not, how can this be remedied?
I also flashed using Step 3 from the same link as was provided by jahash. I think it may have something to do with the lagfix not being removed.
Should have read further before posting I guess, but I think my question is answered in post #7 of the HOWTO link.
My next question is, can anyone point me to a dbdata.rfs file that would resolve this problem?
redcell said:
I am getting a similar error when attempting to "format internal sd-card" in recovery mode.
I get the following error:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Similarly, I didn't remove OCLF before I attempted to flash XXJPM using Odin, so maybe it has something to do with that?
Does a full flash overwrite any changes made by OCLF? If not, how can this be remedied?
Click to expand...
Click to collapse
This happened because when u flashed JPM you ticked re-partition (which you shouldn't have). Its not caused by OCLF.
To fix it you have to flash again with re-partition using another firmware package which has the dbdata.rfs file (JM8 for example, JPM is missing it). Then after that if u want JPM flash it but DONT tick re-partition.
Thanks hardcore, that's exactly the info I was looking for. I will re-flash wish JM8 and then with JPM with partition unchecked.
Thanks, I'll report back with results.
As you said, I made a mistake. Went through steps 1, 2 and 3 and everything is fine now! Cheers!
i do have the exact same problem but flashing JM8 doesn't solve it.
in odin 1.3 with re-partition enabled I used s1_odin_20100512.pit, CODE_I9000XWJM8.tar.md5 as PDA and MODEM_I9000XXJM4.tar.md5 as phone
on startup I still get "E:Can't mount /dev/block/stl11 (Invalid argument)"
any ideas please?
XIAfbk like one of the rep said earlier, you must also flash with csc as well. So pick your original csc when you flash JM8. I had the the same problem and it was fixed when i flash the second time with my original csc as well.
drbunny said:
XIAfbk like one of the rep said earlier, you must also flash with csc as well. So pick your original csc when you flash JM8. I had the the same problem and it was fixed when i flash the second time with my original csc as well.
Click to expand...
Click to collapse
Where do you get an original csc file? I'm having exactly the same problem..
My phone is orange uk.. did not back up efs folder before flashing to froyo via kies reg hack.. Didn't know i had to..
Changed phone to xeu csc on froyo but now am reflashing whole process jm8-jpm-jpo.. to try to fix some modem issues..
Thanks
hardcore's post helped me a lot the procedure he posted works well ..... thanks hardcore
I just got out of this issue after struggling for 1 whole day. I tried each and every solution/suggestion/recommendation available on the web but NOTHING seemed to work. If you are in the same boat, here is some good news for you.
You don't need to mess around with CWM or Voodoo or whatever, simply use ODIN to flash the latest stock JPU (2.2.1) from the link below. This one does a complete rewrite of every partition on your device, including /cache, which is the issue here.
http://hotfile.com/dl/88094739/f5545cc/I9000XXJPU.exe.html
Once it is done, all your partitions will be properly mounted and formatted as per defaults. Then you may choose any rom you may like.
Just make sure you use the PIT, PDA, MODEM, and CSC files come with this firmware. Don't forget to click repartition.
Good luck!!!
"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can'
I know you guys don't like new posts, but I've spent the past 2 days trying to figure this out and I am about to give up.
I'll just lay this out in bullets and this is just a last attempt before I throw this phone out:
Phone: GT-i9000 bought full price from Bell, unlocked running on Fido
Rom Installed: ROM Name: All In One Edition Version: 7.0 Developer: Spike_M Firmware: XXJPY
I shut the phone off because it stopped responding to any touches, turn it back on and its stuck on the SAMSUNG GALAXY S Logo.
Can enter DOWNLOAD mode using three button combo, but not RECOVERY mode.
This means that I tried to flash a new FW using ODIN. What I tried to flash:
Used:
Odin3 v1.3
PDA = I9000XXJPU-REV03-PDA-low-CL747761.tar
PIT = s1_odin_20100512.pit
PHONE = MODEM_I9000XXJPU.tar.md5
CSC = GT-I9000-CSC-MULTI-OXAJPU.tar.md5
When I click Start on Odin with either ☐ Re-Partition or ☑ Re-Partition, it reboots into RECOVERY mode, "Wipes Data", and gives me this error message:
HTML:
"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can't mount DBDATA: your storage and not prepared yet. Please use UI menu for format and reboot actions."
and just hangs.
I found this link: forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage
and tried the solution. I can access the adb shell when the phone is stuck in recovery mode, but I don't have root access so I can't push any files like parted onto the /sbin folder because it says "Permission denied"
If anyone can tell me if phone is a lost cause, I can stop trying already and get on with my life. If anyone can help, I would really appreciate it. Thanks a lot.
my "E: can't mount /dev/block/mmcblk0p1" problem has been solved by this.
It may not be the same problem but the following solved my "E: can't mount /dev/block/mmcblk0p1" problem, not "E: can't mount /dev/block/mmcblk0p2". I used JM2, 512 pit.
Credit to Margaliini
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks, I'll try that and report back to you...
Please help me I have this problem your suggestion did not work please help
and thanks
alaaflashaliraqi said:
Please help me I have this problem your suggestion did not work please help
and thanks
Click to expand...
Click to collapse
u can try this
Solved
If problem is still valid, I have found a kind of solution (or rather workaround) which can be found on YT.
www youtube com/watch?v=zdMhYYdMB08
Best regards
fteller said:
If problem is still valid, I have found a kind of solution (or rather workaround) which can be found on YT.
www youtube com/watch?v=zdMhYYdMB08
Best regards
Click to expand...
Click to collapse
Using some advice from your guide along with the fix found here, I was able to revive my once unresponsive internal sdcard http://forum.xda-developers.com/showthread.php?t=1665123
How did you mange to fix this Mount problem finally ?
E: Can't mount/dev/block/mmcblk0p2 (invalid argument
E:copy_data_default_apk:Can't maount DBDATA
Mu phone gets into download mode , and recognized by Odin (i have tried to put I9000xxJPU the download process was finished with no error, but when the phone made restart to start the update process i got the error message above). since the the phone is stuck in endless loop on the main samsung opening screen.
I tried to do this tip : (with the I9000xxJPU)
http://www.youtube.com/watch?v=zdMhYYdMB08
but got the same result ...i am not convinced that's the same error as mine ...
Please , any replay will be of great help.
Ran:fingers-crossed:
find dbdata
u can see here for i9000
http://forum.xda-developers.com/showthread.php?p=38025542
Sent from my GT-I9000 using xda premium
Apply again stock with pit file ...this error will finish.
Sent from my GT-I9000 using xda app-developers app
Dont work still
Hi ,
Thanks for your replay.
I tried to put the dbdata.tar file in the link that you said .
The phone seems to update dbdata when its satrted, but still get stucked with the same error...
Do you think a new stok will solve it ? i tride already 3 of thoes...(if you can give a link for somthing that you think that is recommanded i will be greatfull)..
Any outher guesses?
---------- Post added at 08:42 AM ---------- Previous post was at 08:38 AM ----------
Hi ,
Thanks for your replay.
I tried to put the dbdata.tar file in the link that you said .
The phone seems to update dbdata when its satrted, but still get stucked with the same error...
Do you think a new stok will solve it ? i tride already 3 of thoes...(if you can give a link for somthing that you think that is recommanded i will be greatfull)..
Any outher guesses?
Hello, I have been on Draky's rom 10.1 , today I noticed that my phone SGS was stuck at the first boot screen , i tried restarting it , and still would get stuck on the screen , then I tried to reflash it with darky's rom wouldn't help. I tried to reflash with original 2.3.3 still the same. The nature of the issue is it would freeze at the boot screen , and when I got to the recovery menu i get into Android System recovery (3e) even when flash with darky's rom through Odin. the following is displayed in recovery menu:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed
and I can't do anything with it, tried to flash 2.1, 2.2, 2.3 versions same thing ... at the best I was able to get into samsung animation and after that the phone would just go dead, until I physicaly remove battery. I tried to flash pit files separatly, then PDA, then PHone, and SCS from Odin still no results ... any suggestions gurus ???
You tried to flash pit files separately? So you used odin to flash three files
(PDA,CSC and PHONE) with a pit for repartition all at once because you don't repartition with pit files unless you have the other three files. I'd try Ezbase 3.0http://forum.xda-developers.com/showthread.php?t=991792 with the specific odin and pit file plus the three .tar files is included in the post.
tried all 4 files at the same time , pit, pda, phone, csc same results ...
That's quite weird then. I would try the ezbase I suggested above though, worth a shot
Hi Guys
Trying to go from Cyanogenmod 7 nightly back to stock
Been spending hours on this. Read through the AIO captivate thread and noted a few others with:
E: cant mount /dev/block/st110
(invalid argument)
E:Copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Stuck in this loop, wont go past this point with newish Rogers Captivate
Initially it was the ODIN version causing it for Rogers users but supposedly v1.0 should be OK and that's whats packed with the Rogers Version
But i can't get passed the mounting issue, things i've tried:
1. Just loading pre packaged PIT file with repartition ticked - Hangs
2. Loading pre packaged PIT and PDA with repartiton ticked - Can't mount
3. Loading pre packaged PIT and PDA part ticked / reboot / reset button / load just PDA part unticked - Can't mount
I've seen others load different PIT and JM files but they mostly seem to be for the AT&T version.
Anyone know which files i can try individually for rogers to get past this mounting issue?
cheers
there is a guide here on how to go back from cm7 on fascinate, maybe that would work for your solution.
Had a quick look in the Fascinate forum, didn't see anything going back from CM7 i was also under the impression to OS structure was different for the fascinate?
In the mean time i managed to load just the PIT file with repartition ticked, but still a no go.
I've tried wiping user data, cache's, factory reset all from the 3 button recovery and Nada
everything keeps coming back to:
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Luckily i can still get into recovery and download, but only with the buttons.
EDIT: Sorry put question in wrong section and currentyl following this thread to see if it fixes it http://forum.xda-developers.com/showthread.php?t=979133
You hear that ??? Thats my sign of relief
In all my reading around somehow i missed this thread http://forum.xda-developers.com/showthread.php?t=979133
Fixed it by flashing AT&T first and then the Rogers afterwards, worked like a charm.
Big thanks to the guys who provided the files, i couldn't thank you in the thread cos i don't have 10 post yet