I used the forum search and didn't find a match to my problem, so I figured I would ask to see if anyone knows what the heck is going on.
When I try to copy a file to the internal storage of my Captivate, I get an error from Windows "Invalid Parameter", and it won't copy over.
When I try to flash a ROM, I get the following:
Code:
Copying Files...
E:Can't mount /dev/block/st19
(file exists)
E:Can't mount SYSTEM:
E:Failure at line 12:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
at&t Samsung Captivate
Rooted, ClockWork Recovery
Last Flashed ROM file successfully: 12/30/2010
File: di11isJPU2.zip
Disregard. Flashed back to stock using ODIN. Got tired of trying to figure out the cause of the problem.
Its because you have a lagfix. Windows wont read ext filesystems i dont think.
smokestack76 said:
Its because you have a lagfix. Windows wont read ext filesystems i dont think.
Click to expand...
Click to collapse
Yep. That turned out to be the problem. Now that I'm back to Ginger Clone 2.2 R5, all is well. (IMO, the perfect rom)
Just make sure you disable them before you flash another rom. Or go back to stock like you did
Related
Hi everyone! I'm new here, please don't shout at me!
Basically, I've been rooting and installing recoveries images all night. But I've run into a problem. I was going to flash to the Super-Hybrid HD-Desire ROM by MicroMod777 (link to thread: http://forum.xda-developers.com/showthread.php?t=784260) but it won't install, and now won't boot past the Nexus colour logo with the unlock bootloader padlock symbol at the botom. Here is what I did to get to this stage:
Followed these guides: http://wiki.cyanogenmod.com/index.ph...l_Update_Guide
http://androidandme.com/2010/01/hack...t-a-nexus-one/
I then downloaded said ROM and put it in my SD card like it said, and booted into ClockWork from ROM Manager. I tried to flash it, but it didn't work, coming up with this error:
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Copying files...
Copying files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
E:Can't mount SDEXT:
E:Failure at line 24:
copy_dir PACKAGE:ext SDEXT:
Installation aborted.
I then did a factory wipe, and that didn't work, so I wiped the cache partitions. Nothing worked, always the same error. I also did a backup before I tried to flash for the first time, I've tried to restore that, but it doesn't work either; it also says that it can't mount SD-EXT, but I don't know if this is the error.
I can still get into the bootloader (trackball + power buton) and get to recovery through there, and I saw someone say in a thread here that if you can get into the bootloader it is basically impossible to be bricked. The phone will also not mount when I connect it to the PC, however the PC knows it's there, as I can see the phone, and on fastboot's menu it says 'fastboot usb'.
I hope some of you guys can help me! I really do love my phone, I need it ASAP! Ideally, I'd get onto the ROM I mentioned above, but restoring it to factory settings would also be perfect. Whatever is easier!
Thanks
redbullcat
This is also in the General section, but I realised I posted it in the wrong section. Sorry.
EDIT: Just completed this tutorial and it worked! I am now back to where I started! I'll post in this thread if I have any more problems!
LINK doesnt work in your EDIT
Edit: i did this :
fastboot, unlock, flash clockwork recovery, nandroid
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.
I'm currently on froyo rom andromeda 3. Today while charging my phone. I turned my phone off while it was still charging. My screen froze and now my phone doesn't work. Anyone, please please help me? Took my battery out and put it back but it took me into recovery mode. I tried reflashing andromeda 3 but it didn't work. Does anybody have a fix for it?
Sent from my T-Mobile myTouch 3G Slide using XDA App
with such a vague description of what you did, its kind of hard to help.
is there some reason you opened an entirely new thread rather than using the Q&A we already have???
http://forum.xda-developers.com/showthread.php?t=962276
My friend told me that I might of broken my phone bcause he said that there is a thread thats said u can't have the phone charging while turning the phone off while u are on the andromeda 3 rom. Is there a fix for this without having to go odin?
Sent from my T-Mobile myTouch 3G Slide using XDA App
jaydenboy said:
My friend told me that I might of broken my phone bcause he said that there is a thread thats said u can't have the phone charging while turning the phone off while u are on the andromeda 3 rom. Is there a fix for this without having to go odin?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
i have never heard of such a bug.
i can tell you right now, that a reflash should fix it. if it doesnt, then you must have hardware damage, not rom-related.....
If u can...flash andromeda 3. Nothing else just the plain andromeda 3. Now after u successfully flashed it. Let it sit for 10-15min. Turn phone off. Turn back on then connect charger to phone. Then while still charging u turn the phone off, while the phone is still charging. N there u will encounter my problem that I am talking about. Wat do I do? I hope this will help u understand wat i am talking about.
Sent from my T-Mobile myTouch 3G Slide using XDA App
jaydenboy said:
If u can...flash andromeda 3. Nothing else just the plain andromeda 3. Now after u successfully flashed it. Let it sit for 10-15min. Turn phone off. Turn back on then connect charger to phone. Then while still charging u turn the phone off, while the phone is still charging. N there u will encounter my problem that I am talking about. Wat do I do? I hope this will help u understand wat i am talking about.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
dude. im a founding member of team komin. i helped BUILD andromeda. i have shut my phone off hundreds of times while plugged in with ZERO issues.
what happens when you REFLASH the rom?
when i try to re-flash it say it could not flash and i was aborted. i well rite it down re-post exactly like it said on my phone thank you for helping
ok. just to appease you. i have on my dev phone a fresh flash of andromeda 3, it has sat here for a few minutes, it is charging, and i am shutting it down
jaydenboy said:
when i try to re-flash it say it could not flash and i was aborted. i well rite it down re-post exactly like it said on my phone thank you for helping
Click to expand...
Click to collapse
you need to boot into recovery, go to mounts and storage, mount usb storage, and copy a new download of andromeda3 to the sdcard from a computer. sounds like you have a bad install/download
by the way, my experiment has concluded that i do NOT have the issue you are describing......
i can power off and power on my device a million times while its charging....
I've been running Andromeda3 since early May with zero problems. Just for grins I turned my phone off lastnight while charging just to see if I could duplicate what jaydenboy has encountered. After 20 minutes of charging I booted back up with no problems, still smooth as the first day I flashed it.
Here wat i get when i reflash
1ST page
CLockworkMod Recovery v2.5.1.3 - voodoo
- reboot system now
- apply sdcard:update.zip
- wipe data/factory reset
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- voodoo lagfix
- ***** GO Back *****
---------------------------------------------------------------
CLockworkMod Recovery v2.5.1.3 - voodoo lagfix
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/command
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/log
E: can't open CACHE:recovery/log
E: can't mount /dev/block/stl11
( No such file or directory )
2ND page
Apply update from .zip file on SD card
- apply sdcard:update.zip
- choose zip from sdcard
- toggle signature verification
- toggle script asserts
- ***** Go Back *****
-----------------------------------------------------------------------
CLockworkMod Recovery v2.5.1.3 - voodoo lagfix
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/command
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/log
E: can't open CACHE:recovery/log
E: can't mount /dev/block/stl11
( No such file or directory )
-- Installing:SDCARD:Andromeda3-Final.zip
Finding update package...
E: can't mount /dev/black/mmcblkOp1 ( or /dev/block/mmcblko )
( device or resource busy )
E: can't mountSDCARD:andromeda3-Final.zip
Installation Aborted.
sorry for the repost but i really need help evertime i try to reflash i keep gettin this any help will do
1ST page
CLockworkMod Recovery v2.5.1.3 - voodoo
- reboot system now
- apply sdcard:update.zip
- wipe data/factory reset
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- voodoo lagfix
- ***** GO Back *****
---------------------------------------------------------------
CLockworkMod Recovery v2.5.1.3 - voodoo lagfix
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/command
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/log
E: can't open CACHE:recovery/log
E: can't mount /dev/block/stl11
( No such file or directory )
2ND page
Apply update from .zip file on SD card
- apply sdcard:update.zip
- choose zip from sdcard
- toggle signature verification
- toggle script asserts
- ***** Go Back *****
-----------------------------------------------------------------------
CLockworkMod Recovery v2.5.1.3 - voodoo lagfix
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/command
E: can't mount /dev/block/stl11
( No such file or directory )
E: can't mount CACHE:recovery/log
E: can't open CACHE:recovery/log
E: can't mount /dev/block/stl11
( No such file or directory )
-- Installing:SDCARD:Andromeda3-Final.zip
Finding update package...
E: can't mount /dev/black/mmcblkOp1 ( or /dev/block/mmcblko )
( device or resource busy )
E: can't mountSDCARD:andromeda3-Final.zip
Installation Aborted.
something has happened to the phone that is not at fault of the ROM. that phone needs to be flashed back to stock, and reset. something was done that did not involve the rom.
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
Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)
Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...
Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS
Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!
has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.
Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?
Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.
Bump in hopes of solving this issue.
My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.
you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.
Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728