Can anyone Help Me Get Back to Rogers 2.1 - Captivate Q&A, Help & Troubleshooting

I have a Samsung Captivate that was running 2.2 flashed by Keis.
I could not see all of my internal sd space so I wanted to flash a custom rom.
I have used Titanium Backup to back up my phone.
I then Tried to use AIO Captivate Toolbox 2.5 to flash back to stock.
Now every time that I try to boot my phone it goes into system recovery <2e>
at the bottom it says
update media, please wait ...
e:Can't mount /dev/block/st101
(invalid argument)
e:copy_DBdata_media:Can't mount DBDATA:
copy defaul tmedia content failed.
Please Help

Just to add to the last post I can still get into download.

download the file in my sig. Flash it with odin 1.3
http://dl.dropbox.com/u/20958367/Odin3 v1.3.exe
I can walk you through it if you like.

I got 1.3 from the link that you gave me, but neither link in your signature works.
Could you post them again?

windburn said:
I got 1.3 from the link that you gave me, but neither link in your signature works.
Could you post them again?
Click to expand...
Click to collapse
theres the new URL for 2.1
http://dl.dropbox.com/u/20958367/I896UXJI2-homebinary.tar

Thank you so much.
I am downloading it now.
Just a few questions.
When I do odin what do I select pit, PDA or what?
Also do I have to change any of the options like re-partition?

Don't change any options at all. Open odin and leave it as is.
The file goes into the PDA section, no pit file is required.

odin did it's thing said pass 1:51.
Then it re-booted into android system recovery <2e>
What would you like me to do?

Exit recovery, and attempt to boot the phone.

I thought we had it but no luck.
it is still going into recovery
with this error
update media, please wait ...
e:Can't mount /dev/block/st101
(invalid argument)
e:copy_DBdata_media:Can't mount DBDATA:
copy defaul tmedia content failed.

try flashing the 2.2 one it has a different recovery 3e.

I am downloading now.
I will let you know what happens

Once it reboots it should go into recovery and install a bunch of files and then boot back up by itself.

It re-booted into recovery but got the same error.
It did not install any files or reboot again.

windburn said:
It re-booted into recovery but got the same error.
It did not install any files or reboot again.
Click to expand...
Click to collapse
Its by me at this point. That method has always worked for me.
Sorry I couldn't get you any further than you were.

I was reading this does it make sense to you
http://forum.xda-developers.com/showthread.php?t=788850

It looks Like I screwed up the partition table does anyone have a pit file for 2.2 Rogers?

windburn said:
It looks Like I screwed up the partition table does anyone have a pit file for 2.2 Rogers?
Click to expand...
Click to collapse
Reading that, its sounds exactly like what happened.
I don't know of any pit file for Rogers.

Thanks for your help nickm50
I will keep looking and see if I can find any way to fix this.
Maybe someone who has fixed the problem before will let us know how they did it.

Related

[Q] URGENT can't mount \dev\block\stl11 please help!

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'

"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?

Help I f***ed up :(

So I rooted my Galaxy s(bell) and put speedmod kernel on it, I then tried to install a theme which partially worked but now I get "the process android.process.media has stopped unexpectedly" every few seconds and any time I try to do something I was unable to do anything at all really. So I then installed dark core kernel and that did not change anything, I restored to factory default and that did not stop the error(Even though all data was wiped). So I then formatted system under dark core recovery(Bad idea?) and now I can't get past the Samsung Galaxy 19000M boot screen(Assuming because there is no system files now that I wiped them?). I can access dark core recovery and download mode....What can I do?
flash jvk(gingerbread) or jl7(froyo) system files useing odin 1.3+
Sent from my GT-I9000 using XDA App
Where can I get jl7 firmware?
Www.samfirmware.com or search the forum. I think he meant jl2
Sent from my Iphone killing I9000
The trouble was flashing a theme onto a stock ROM. Unless a ROM has been deodexed it can't be themed, so for themeing you need a custom ROM or one prepared using doc's kitchen. Just swapping a new kernel does not allow you to install a theme. Flash a stock theme in download mode from odin and then start again, you will be fine.
There are lots of guides about how to do that here.
Sent from my GT-I9000 using XDA Premium App
Have you tried factory reset/wipe data in recovery mode? this may not work but worth a try
I keep I9000XXJPU on my PC because it has saved my ass in the past when i bricked my phone, it has all the files required to use in odin to flash. just get into download mode, open odin, attach files into specified areas, connect phone then start
make sure to look here, follow step and your all good
http://forum.xda-developers.com/showthread.php?t=846913
I flashed my phone with I9000UGJL2 and it goes to recovery and says "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.
If I reboot it does not get passed the Galaxy S logo. What is wrong?
Edit: For some reason, after I unsuccessfully flashed 2.1 stock(wouldn't boot past samsung screen) I tried re flashing 2.2 JL2 and it worked phone is now fine.
After you got the message stl10 you need to flash dbdata and that file only it work.
endrien said:
I flashed my phone with I9000UGJL2 and it goes to recovery and says "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.
If I reboot it does not get passed the Galaxy S logo. What is wrong?
Edit: For some reason, after I unsuccessfully flashed 2.1 stock(wouldn't boot past samsung screen) I tried re flashing 2.2 JL2 and it worked phone is now fine.
Click to expand...
Click to collapse
Sent from my GT-I9000M using XDA App
You can't flash a theme over a stock rom

E:failed to mount /sdcard (File exists) Problem

Hello every one,
I tried to flash my Bell Samsung Galaxy GT I 9000M with gingerbread but things got messy and now I am stuck in bootloops...
I have already tried to flash back to the stock Eclair room but it's still not working.
I can still access download mode and recovery.
Here is the error message I get when I go into recovery:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
I think I need the seperate PIT, PDA and PHONE files to flash via Odin ticking repartion, and then upgrade to last version avaible via kies to fix this. But I don't where to get this files for Bell Canada I9000M.
I don't know how to fix this. Can someone help me ?
Here was my phone stock configuration before all that happens:
Baseband version
I9000UGJL2
Firmware
2.2
Kernel
2.6.32.9
[email protected] #3
Build number
FROYO.UGJL2
galaxy s vibrant bell
gt-i9000m
Note: I hope I posted at the right place, if not the mods can feel free to move it
google searched and found this in an old thread:
http://forum.xda-developers.com/archive/index.php/t-768441.html
http://www.multiupload.com/N62CDNXXXK I haven't downloaded the file so I'm not sure if it is 3 parts.
The other thing I'm thinking of (and I hope is not true), is the time when all Bell I9000M phones were dying after the official upgrade to froyo 2.2
http://forum.xda-developers.com/showthread.php?t=886158
Best of luck to you, sorry I can't be of more help as I'm not that experienced with this.
Thanks man.
I found a way to fix it. I installed back the stock I9000UGJL2 froyo via ODIN using 512 PIT file and repartition, then I got this new error message
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
After that I followed this tuto http://forum.xda-developers.com/showthread.php?t=984140 to solve it.
Now I'm back on trail and I have to find a safer way to instal Gingerbread JVH.
I will try the method that you described me here http://forum.xda-developers.com/showthread.php?t=1075144&page=2 but I would be happy to have some more details and the exact files I have to use...
I'm afraid to get in troubles again.
Thanks again for your help JJustin.
I found a way to solve my problem (i described it in the other thread I started http://forum.xda-developers.com/showthread.php?p=14620127#post14620127).
Now eventhough I am not so confident, I will try to install gingerbread again using other methods.
I am open to any ideas. I will let you guys know if I get it right.
Thank you all.
If u want gingerbread follow darkys guide exactly and u will run gingerbread
Sent from my GT-I9000m using XDA Premium App
nguetto said:
I found a way to solve my problem (i described it in the other thread I started http://forum.xda-developers.com/showthread.php?p=14620127#post14620127).
Now eventhough I am not so confident, I will try to install gingerbread again using other methods.
I am open to any ideas. I will let you guys know if I get it right.
Thank you all.
Click to expand...
Click to collapse
wat was it?
OH S***T!!!!! Thank you very much worked like a charm!!!
Plss help me i9000
I heve this error in my galaxy s i9000 .

[Q] Rogers AIO mount/st110

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

Categories

Resources