[Q] /dev/block/mmcblk0p1 error, busy
well, everything is working perfectly in jpk.......the only that isn't is clockworkmod recovery. that is where it gives the error "can't mount sdcard, /dev/block/mmcblk0p1 is busy" or something along those lines.
now, i reflashed with odin, click re-partition, and on first boot, went and took a look, those files/directories in the /dev partition are all there. but after a power cycle or two, they're gone again (except "vold" which is empty). i even tried formating the sdcard via jpk, and it goes through fine, but i still get this error in recovery.
i have no idea what i did. my phone did crash once and i had to pull the battery out to shut it off, but it hasn't done that since. and if it's relevant, i now have a "LOST.DIR" in the root of my sdcard.
suggestions anyone please?
what if you flash back to stock 2.1 ROMs ?
does it work?
yeah, i was thinking about that.......but it's soooooooo much work to setup, but i guess that's the only way to tell for sure.
i was just wondering if anyone else was having these issues. maybe this is why samsung didn't officially release it.
EDIT: well, that did it.......sadly i'm back on 2.1, but happily, my partitions are back! so it looks like it's related to the froyo update. i don't know if it was because i used the 512 pit and not 803 or what, and i don't care. i'm happy again
there's another thread i responded too where someone said they had trouble with their internal sdcard right after they installed froyo, so it might actually be froyo causing this.
Hi,
I have tried upgrading my bell I9000m to froyo twice now and both times I have gotten the following error leaving my phone partially bricked:
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E:copy_dbdata_media:Can't mount SDCARD:"
I have sent the device into samsung twice now and both times they have fixed the issue with a full phone software restore.
I have tried the repartition option and a full restore via ODIN with no luck. I know there are others out there with the same issue and have just returned/exchanged the phone.
I donot want to try any of the JPx releases again as I am scared and dont want to be without the Galaxy S for 2 weeks.
I am creating this thread to see if anyone has managed to find a fix to the above issue or if we want to explore options to create a fix.
Serious, It bricked twice. Does that tell you anything about running Froyo Beta? Also sounds like you happen to have one of the phones from a batch that had bad memory chips. I'd replace the whole thing If I was you. Installing the Froyo Beta just showed you the problem.
I ran into the same error but got lucky enough that I was able to re-flash jh2 with re-partition and fixed the sd problem. Then flashed jpk without re-partition and no more error.
Rumy,
I had the same thing happen the first time I tried to flash to JPK from JPH. My JPH was updated through Kies. I was running a custom ROM on it with the OCLF which I forgot to uninstall before upgrading to JPK. This may have caused the problem but I really don't know.
I was stumped. I could not format the SD card without getting the same message. The first time I tried was with the 803 pit. So I tried with the 512 pit and the same thing happened. Tried several times and it finally let me reformat the SD card. Tried to flash JPK again with 512 pit and I got the same error. I figured I bricked it.
I did some reading on the forums here and I found a post advising to re-flash back to Eclair and then try again which is what I did and it worked.
I used the XWJM8 pda the bell(BMCJH2) CSC and the XXJM4 Modem with the 512 pit to go back to Eclair. Once the phone booted up properly I just followed the JPK instructions again using the 512 pit and I had no issues.
I have a rooted JPK custom rom(Rombie's 2A Full) running now with the OCLF for a little over a week and I have no issues with the phone. I was certainly crapping my pants at the time though so I hope you find a way around this.
Good luck.
Phone is the GT-I9000
Hey guys thanks for the info.
I just got my phone back and have tried to upgrade to JPK, so far so good. Hopefully it stays like that. If not I will be knocking on your doors for help
I created this thread to try and figure out a solution for everyone on the Bell I9000M, and it looks like Banger242 might have one, but there is another thread with a similar goal.
http://forum.xda-developers.com/showthread.php?p=8424399#post8424399
rumy, someone who's been a member of these forums for as long as you have, should already be well aware that this thread belongs in the Q&A section as it has nothing to do with ROM development.
Also, searching a little more on this subject before posting would have revealed that the info you needed has already been well covered in previous existing threads.
Thread moved to Q&A, and closed.
how did you fix it?
wang1chung said:
yeah, i was thinking about that.......but it's soooooooo much work to setup, but i guess that's the only way to tell for sure.
i was just wondering if anyone else was having these issues. maybe this is why samsung didn't officially release it.
EDIT: well, that did it.......sadly i'm back on 2.1, but happily, my partitions are back! so it looks like it's related to the froyo update. i don't know if it was because i used the 512 pit and not 803 or what, and i don't care. i'm happy again
there's another thread i responded too where someone said they had trouble with their internal sdcard right after they installed froyo, so it might actually be froyo causing this.
Click to expand...
Click to collapse
Can't mount /dev/block/mmcblk0p1Arrow
tried this on the 2 phone i've have got here without invoices, and it's not working
still gives the error message "Can't mount /dev/block/mmcblk0p1"
Banger242 said:
Rumy,
I had the same thing happen the first time I tried to flash to JPK from JPH. My JPH was updated through Kies. I was running a custom ROM on it with the OCLF which I forgot to uninstall before upgrading to JPK. This may have caused the problem but I really don't know.
I was stumped. I could not format the SD card without getting the same message. The first time I tried was with the 803 pit. So I tried with the 512 pit and the same thing happened. Tried several times and it finally let me reformat the SD card. Tried to flash JPK again with 512 pit and I got the same error. I figured I bricked it.
I did some reading on the forums here and I found a post advising to re-flash back to Eclair and then try again which is what I did and it worked.
I used the XWJM8 pda the bell(BMCJH2) CSC and the XXJM4 Modem with the 512 pit to go back to Eclair. Once the phone booted up properly I just followed the JPK instructions again using the 512 pit and I had no issues.
I have a rooted JPK custom rom(Rombie's 2A Full) running now with the OCLF for a little over a week and I have no issues with the phone. I was certainly crapping my pants at the time though so I hope you find a way around this.
Good luck.
Phone is the GT-I9000
Click to expand...
Click to collapse
Related
Hi all, I'm starting a new thread because I can't find anyone else with this set of problems or an appropriate thread to post to.
My problem is that I've tried a number of "GT-i9000" 2.2 roms and I can't find one that fully works with my phone. At worst I get infinite force closes on boot. At best some functions are remapped. By remapped, I mean I can't hear any system or media audio until I plug in headphones, at which point the audio will play out of the external speaker . Or that if someone calls me and I cover the IR sensor (like with my ear) then the phone audio output stops (possibly routed to headphones?) so the only way I can hear the other person is to hold the phone in such a way that the IR sensor is not obstructed making it difficult to talk to people. It's quite a funny situation and I feel like I'm being pranked!
Sometimes something force closes in the background (phone vibrates) which causes it to hang for a bit before restarting the launcher. It seems quite random - sometimes this happens several times in a few minutes, other times only once in a few hours.
Keyboard touch vibrations also don't work. Other than these (super annoying) problems, 2.2 is very nice and fast to use. And yes, I do have an international Galaxy S with a hardware home button. I haven't found a way to use Kies to upgrade to a non-force-closing version so I've been relegated to using odin roms.
Any help would be really great!
Edit: I've been using 512 pit file if that makes a difference.
You are using a non froyo modem.
flash to the jpm modem and you will be good.
no progress
Thanks for the suggestion but unfortunately that did not help. I flashed the JPM modem from the i9000 Open Market Froyo package: MODEM_I9000XXJPM.tar.md5. No change from the symptoms I've described.
Any other suggestions?
Are you repartitioning? Using the right pit file? Does the rom have dbdata and cache.rfs in it? If not, try flashing to 2.1 with 512.pit, repartition ticked, then flash to 2.2 with repartition not ticked.
Flash froyo jpk with pit 512 and re-parition.
Start the phone and format the internal sdcard.
Restart the phone in recovery mode.
Wipe catch and do a factory reset.
Restart.
Flash Jpm/jp6 with no pit file and don't re-parition.
Start the phone and one again format the internal sdcard.
Restart again in recovery mode.
Wipe catch again and do a factory reset.
Start the phone again.
Check you crc code and an setting.
Now the phone should work.
If there still.problem.then flash back the original firmware and return it to the shop.
Its broken...
Sent from GT-I9000 Jpm OS kernel with z4mod
still no luck
Still no go.
I followed DamianGto's instructions to the letter using the following files found on XDA:
JPK
Code:
://forum.xda-developers.com/showthread.php?t=790686&highlight=jpk+firmware
JPM/JP6
Code:
://208.100.42.21/showthread.php?t=796987
More suggestions appreciated
I'll post more if I make progress.
Well almost.
Like i wrote at the end so if it don't work now is broken. That if you did what i wrote.
The reson to flash jpk first was to get the right filsystem with pit512.
And jpk is close to Jpm. So it would note change much when you flashed Jpm.
All wipe and format was to clean the system and make sure it was that In the end so noting could interfere.
So if you still has all this fault then its not the firmware/software.
Flash back an old firmware and upgrade it with kies.
You need to get it repaired.
I don't Like to write that and i hope someone else have any ideas what you else can do.
Sent from GT-I9000 Jpm OS kernel with z4mod
Yeah, I can't return this to a store in the near future.
Well thanks DamianGto for all your help. I'll keep hacking away and will post back if I succeed in running 2.2 without error.
cantinaNW said:
Yeah, I can't return this to a store in the near future.
Well thanks DamianGto for all your help. I'll keep hacking away and will post back if I succeed in running 2.2 without error.
Click to expand...
Click to collapse
Do so and good luck..
Sent from GT-I9000 Jpm OS kernel with z4mod
Resolution
So I figured it out eventually and am posting the resolution here for the few other people in the world who might be having this problem. This phone, though it has a 3-key body, is actually a [frankensteined] SGH-T959 T-mobile Vibrant. The fix is simple then, use a Vibrant rom! After flashing a Vibrant rom, there is one more step required since the phone has the international body and button configuration which the Vibrant ROM isn't expecting:
Make sure you have flashed with the right zImage so you can monkey with system files.
Download from the phone: System/Usr/keylayout/s3c-keypad.kl
Switch the numbers between the volume up and volume down keys because they're backwards.
Save, and reupload the file replacing the original. Reset the phone. Done!
Enjoy Froyo on your beautiful international-bodied Vibrant!
I curently have a bell i9000M I was running Doc's JPY for a few months but decided to his JS8 version the other day. As soon as I flashed it I noticed my phone was unable to install apps and in manage applications it gets stuck on computing.
So things I have tryed to get this working again........
Flashed EZbase using re-partition , still same issue on base.
Flashed Stock JH2 , still same issue.
Flashed Stock JL2 still same issue.
Flashed JH2 then JL2 through Kies same issue.
It seems I can not write to my internel SD although the rest of my phone seems to be working fine any Ideas?
Another thing I noticed is mass storage is not working on any rom only can connect using Kies method if I want to transfer files. Format internal SD is not working , it asks if you want to format you click yes it seems like something happens but then check the internal sd and all the files are still there.
I am not familiar with the I9000M but i know its very common to have SD card failures.
And it seems to me thats whats happened, im sorry for you
best thing you can do is, flash back to stock and send off for repair, hopefully you may get some luck with the next device.
One thing before you get all emotional have a look at this, its a long shot but......http://forum.xda-developers.com/showthread.php?t=905975
azzledazzle said:
I am not familiar with the I9000M but i know its very common to have SD card failures.
And it seems to me thats whats happened, im sorry for you
best thing you can do is, flash back to stock and send off for repair, hopefully you may get some luck with the next device.
One thing before you get all emotional have a look at this, its a long shot but......http://forum.xda-developers.com/showthread.php?t=905975
Click to expand...
Click to collapse
Yea I was not getting any mounting errors in CWM or 2e/3e recovery...Anyway after a frustrating 3 days I now and I think it's finally working , so far.
I manually deleted all files off the internal SD, then did a format from within 3e recovery while on JL2 (this was acting like it was formatting before but all the files I downloaded were still there after the format). Then flashed Hardcore's K13 and installed a custom rom all seems fine so far but it did work periodically over these past few days so I'm hoping it stays working now.
What was weird is I could download files using the web browser but the market would not work all the time but when it did it was downloading the items but would just get stuck installing them.
Anyway thanks for the quick response. Hopefully I have this sorted out now.
I think we need to sticky/pin this for us who just flash the stock/leaked GB 2.3.3 along with the optional root from this thread since we can't post there http://forum.xda-developers.com/showthread.php?t=1127249
Since this is the route that I went I would be able to help answer questions for others. I see cognition, mosaic.... but how about us who like to keep it stock?
Brickster
Just want to say that I have learned so much on here and I have a lot of fun trying out different ROMs. Thanks to all the DEVs, when I get a job I'll buy you guys some beers lol.
So... This has soft bricked my phone every single time. The first 4 attempts were from stock eclair. My last attempt I was successfully running Stock I9000 2.3.3 NEE so I thought I would try it from there. Odin gets to boot.bin and then says FAIL! I got into download mode using VOL DWN and PWR which is the key combination from Stock I9000 2.3.3 NEE. I have been running I897UCJF6-final-OCD-REV0 to flash back to stock after brickness.
So i'm sure i'm missing something pretty simple, but any help is appreciated.
Woah dude, that was very very very close to being a hard brick. Boot.bin is the primitive bootloader. so you had a kf1 pbl, and since you had the combos for I9k boots you obviously had an I9000 sbl, (secondary bootloader that's where the combos are contained.)
Make sure the usb chord is on a port attached to the motherboard (in the back of the pc), if it is already switch to another. Reboot the computer and try again.
But with such a close call like that, and the fact that you said it fails every time I would avoid it altogether I mean its a stock rom, is it worth bricking over??
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
ttr187 said:
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
Click to expand...
Click to collapse
Use admin mode for Odin and change the compatiblity to Xp service pack 2. This is the best way to run Odin for Windows 7 x 64. Since I use Cog 5 v2, I strongly recommend following the instructions 100%. Please remember when you need to loading stock UCKF1 and when you load UCKF1, you are loading bootloaders, so any disconnection can brick you hard. Thank goodness for the simplified instructions there.
GB stock? I thougth captivate stock were eclair or froyo.
KF1 is the leaked gingerbread firmware for the captivate...
popfan said:
Use admin mode for Odin and change the compatiblity to Xp service pack 2.
Click to expand...
Click to collapse
After changing the compatibility mode to XP pack 2 everything worked like a charm. Then I was able to successfully flash Cognition 5 v2. Sweet!
Thanks.
Hello. I use Darky's rom 10.2. And I have problem with Dialer. It sometimes crushes and exits. Problem will be solved with reboot. how can I fix it? thanks.
I would try to flash again and make sure you do a data/cache wipe. I've had random issues with other ROMs when I did not wipe, and all was fixed once I flashed properly.
I know I'm not wiping everything while flashing, but I flash it as told as in FAQ. But my memory will stay unwiped after I run newly installed ROM.
When you say "memory" what exactly do you mean?
If you mean the /sdcard storage partition, that is normal.
yes, /sdcard storage partition.
Before flashing, I get warning message about wiping all data in my internal storage... what does it mean then?
The /data and /cache partitions. And the dalvik cache.
The first 2 are in the cwm main menu. Wipe data/factory reset and wipe cache. Dalvik is in the advanced sub menu.
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Griff1220 said:
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Click to expand...
Click to collapse
It appears to be asking for some encryption password according to one of these guys that posted in the following thread. But there is a way to get past it by the method in this thread...http://forum.xda-developers.com/show...02&postcount=7
Remove ur external sd and copy over/back up anything u want to save from ur internal sd before u do this, just in case.
data/chache wipe i should do right after flashing right?
Hi,techies customer brought the fone in restart condition on galaxy s screen with wrong flash.i flashed almost all the firmwares available from samfirmware using odin,with pit and without .pit it gives me the error :
E:cant mount /dev/block/mmcblk01p (no such file or directory)
E:copy_dbdata_media:can't mount SDCARD.
fone starts up normally when flashed with JPJPM but the internal sd caard shows unavailable and cant run any apps and camera.after adb and got the output of
busybox df -h as below.Pls techies sort out this issue as i am not that much familiar with CMD's
I would like to help you, but this is very serious and technically complicated way to solve your problem.
So, first, go to the Google.com, and you have to read all FAQ and help located There
then, if you'll gain enough techie skills, you should buy a small plasma burner, and steel plate, 1.5-2mm thick, 15x20cm.
When you will have this equipment, you can use Google first, asking your question, it should direct you to This thread on XDA here.
And now most complicated thing:
while applying the patch given in this thread, use your plasma burner to cut the sentence: "I will ALWAYS use Google to help myself FIRST"
spamtrash said:
I would like to help you, but this is very serious and technically complicated way to solve your problem.
So, first, go to the Google.com, and you have to read all FAQ and help located There
then, if you'll gain enough techie skills, you should buy a small plasma burner, and steel plate, 1.5-2mm thick, 15x20cm.
When you will have this equipment, you can use Google first, asking your question, it should direct you to This thread on XDA here.
And now most complicated thing:
while applying the patch given in this thread, use your plasma burner to cut the sentence: "I will ALWAYS use Google to help myself FIRST"
Click to expand...
Click to collapse
thanks for response,I have applied the patch file very first attempt, googled every post,
resurrected in riff,flashed with nearly dozen firmwares with and without pit at last used EZodin to flash EZboot_gingerbread and froyo as instructed in guides.
I have searched the google already but with no results
Strange, as it would definitely clarify this specific issue...
Have you tried to:
factory reset;
ginger flash with repartition
apply this patch?
spamtrash said:
Strange, as it would definitely clarify this specific issue...
Have you tried to:
factory reset;
ginger flash with repartition
apply this patch?
Click to expand...
Click to collapse
Yes i have factory reset numerous times for every flash before and after,flashed with JHJV6 gingerbread,but i can't remember i have applied patch after this GB flash,ok any how i will give a try now and let u know.any how thanks for suggestions.
Hmm.. make sure that ROM contains bootloader too...
Yes offcourse it has the boot.bin file .And for correction it is JPJV6 and not JHJV6 as i mentioned in my previos post.some where in the forum i have found the guide for this and i'll try after i go to office and let u know.
******************
Found this guide:
Basically like everyone else my SGS (I9000M from Bell) died due to an internal SD error, but in my case I haven't updated the phone since I got it in September 2010 (it had the JG9 firmware). The good thing is I was able to flash it to the stock Froyo 2.2, and I'm currently using it as normal and can access the internal SD without problems.
Summary of steps that most likely fixed the problem:
1. Go into recovery mode and "wipe data/factory reset". If your phone boots (but still have problems accessing the SD card) then it's a good indication that you maybe able to fix it.
2. Flash JL2 (from samfirmware.com) using ODIN. Not sure if this is needed, but you may need to ask ODIN to Re-partition. You still get an error "Can't mount DBDATA", and the phone won't boot. That's ok.
3. Flash the SpeedMod Kernel using ODIN (I used SpeedMod K12J with HZ=256). Your phone should boot into JL2 and the SD card should be accessible again.
At this point your internal SD card is fixed and you should be able to flash whatever you want. Just note that Kies will sometimes not work properly with the SpeedMod installed. In my case I flashed 2.1 (JH2) again (this won't work if you have 2.2 without speedmod kernel), then used Kies to update to 2.2 (JL2).
***********************
so will be back after a try as mine is I9000 international
Guys, I'm new to the site but i have read nearly every xda forum post going for getting the Galaxy Tab P1000 with an ICS rom on it and im out now and cant find a thread relating to what i want to ask.
I have tried everything and even though it will install the tab simply refuses to boot, either get the black screen or stuck on the samsung logo, or boots then immediately reboots, ive tried everything from ODIN gingerbread roms to flashing cyna's and others custom ICS roms using their described methods, I can easily unbrick it now too! . ive tried different SD cards in different formats and buildign in the different zImage kernels to match my p1000.. what i cant seem to find is anyone that has successfully got a tab from Vodafone UK on ICS so any help on this would be beyond appreciative .
please!
Rich.
Quick question, for starters, you sure you have a P1000 and not some of the other ones (P1000N, P1000L...)?
If you do, try to explain the methods step by step you've been using for flashing ROMS.
When I started, I also bricked my Tab a few times before I got it right lol
(I actually bricked my tab flashing CM9 update just 10mins ago XD it's now booting again lol)
Hi Stilm, it says it is a P1000 on the back and on the box, no mention at all of an N or L as i noticed you need different kernels/zImage's for those too so can only presume its definitely just a p1000, i think in fact i did try one just to rule it out. it just seems weird that ive not seen a working UK Voda unit on anything but 2.2 but surely its only the rom thats different not the actual hardware.
first i tried cynagenmods instructions to get his CM9 on it including rooting it with oneclickroot to gain SU access, copy zip to SD Card and could boot to cynas menu to select the zip off the SD but, would say successful then brick it or would fail after a bit way through and say cant mount sd.
i tried a few other methods from other sites too but they all seem largely the same, i also tried renaming the cm9 file name to update.zip and using the update function on the original menu but this still bricked it lol.
About CM9, if it doesn't boot after flashing the ROM, flash a kernel (zImage).
the zImage is built in to the rom though, is it possible to flash just the zimage say through odin?.. because after it fails to boot the only way to get anything on it seems to be through odin or at best through the standard built in recovery?
You can use Heimdall, or tar it and use Odin. Or you can download a nightly.
would it recognise it if i tar it though i thought it had to be in a certain layout/format not just a tar container? i will give nightly a go too!
can anyone tell me why it always says CANT MOUNT /SDCARD/filename.zip installation aborted.?
johnsonra said:
can anyone tell me why it always says CANT MOUNT /SDCARD/filename.zip installation aborted.?
Click to expand...
Click to collapse
Hey, froyo and ics are totally different system. It is hard enough to flash a froyo to gingerbread without going through some problems. From my experience flashing gingerbread on froyo, I had to get a new pit file flashed together with the rom using Odin, with repartition checked. Even after that I would get error msgs like E:failed to mount /data or /system etc. I had to push new dbdata.rfs to get it working right.
any luck with getting ICS on though? so many have and its doing my head in now... given im an IT Pro too youd think itd be done by now lol. youre right though about GB thats why im thinking if its down to the actual vendor supplied units, ive not heard yet if other UK Vodafone users have had any success or indeed failure?