Database Develop

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

Please Help: Phone is.. Stuck

So I've never rooted my phone, but one day my phone just stopped responding.. it entered into an endless loop of that white screen.
I believe its due to water damage from steam/heat or something because when I took it in, they said the water damage sticker was activated... anyways, I'm able to get into reboot mode by hitting the power button + volume.
However, there are some errors that pop up:
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: Can't mount SDCARD:update.zip
Installation aborted.
I tried plugging it into the PC to see if it is recognized but it is not...
Any leads on what I should do? My phone is completely stock with default software.
Thanks in advance!

If you can get it into 'reboot mode', you should be able to get it to download mode too.
First of all, if you look underneath where your battery is (so on the phone itself), you should see a bunch of numbers. One of them will be something like 1006,1007,1008,1009,1010,etc.
This is important, if the numbers are from 1006-1009 then follow these steps, but remember... nobody here is responsible for what you do to your own phone:
0. Make sure your USB isn't connected.
1. Download this: http://www.mediafire.com/?fr8bkogcu923wdu
2. Install the correct version for your computer (32-bit or 64-bit).
3. Download this: http://www.megaupload.com/?d=SBSMALFJ
4. Turn off your phone and pull the battery out.
5. Open the I897UCJF6-final-OCD-REV0.exe
6. Press the Volume + and - both at the same time and keep holding them
7. Put your battery in, and plug the USB in (never press the power button).
8. You should see a screen that says "Downloading now..." Or something like that.
9. Your Odin should show that your phone is connected (you can let go of the volume keys at this point), and just press on the 'Start' button.
10. Wait until it all finishes, NEVER pull the USB cable out.
If you're on a number that's 1010 or bigger, then tell me.

It says 1007. Trying now. Will keep you updated in the next 10 minutes

At the end of it all... It says device driver software was not successfully installed...
The Odin3 One-Click Downloader seemed to be successful though.
<ID:0/003> Firmware update start..
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
I tried going into reboot mode after, and it says:
#Manual Mode#
-- Appling Muti-CSC...
Installing Muti-CSC
And it stalls there..
However, it's acting the same as before. Any other solutions?

Not really I'm afraid... I think it'll be best for you to try one more time, and if it still doesn't work try using this version of ODIN next: http://www.megaupload.com/?d=QL6NX702

venomio said:
Not really I'm afraid... I think it'll be best for you to try one more time, and if it still doesn't work try using this version of ODIN next: http://www.megaupload.com/?d=QL6NX702
Click to expand...
Click to collapse
I think your first post is the most recent version of Odin
How long ago did it get moisture in it?
one of the things to try(if it was fairly recent) take the SIM/Micro SD, if you have one/and battery out. Put the phone IN a small bag of rice for 24 hours. If there is any moisture left in the device the rice will absorb it. When you take it out, use a can of compressed air to blow out any residue

kangi26 said:
Try this version of Odin. I think it's the "latest"
http://www.mediafire.com/?0w2y31maz8mdom4
How long ago did it get moisture in it?
Click to expand...
Click to collapse
The same version as in my first reply... But it's the thought that counts

venomio said:
The same version as in my first reply... But it's the thought that counts
Click to expand...
Click to collapse
I just saw that and edited my post

it got moisture in a few days ago... 4? 5?
method still doesnt work with alternate odin version...
looks like im screwed...
it says movinand read fail
movinand checksum confirmation fail
-- movi_checking done!
edit: actually. I feel like there's hope. Now it shows the galaxy s screen after the att screen.... but still no luck.
Anyone know what the next step should be?

did you flash with your sd card in? no promises but i forget what or when but once, flashing with sd card in caused me to stall, now i just always do it, give it a shot.

How do I flash with my sd-card in? I'm sort of unfamiliar with the terminology...

xpiamchris said:
How do I flash with my sd-card in? I'm sort of unfamiliar with the terminology...
Click to expand...
Click to collapse
If you have a micro SD card, make sure you take it out before you start the Odin process
Sent from a autonomous device

Just to give an update, I've tried flashing with sd card both in and out.. and its the same..
Updated list:
When rebooting phone:
ATT World Phone Screen comes up
Galaxy S Screen Comes up
Screen goes black after.
Booting phone under reboot mode:
ATT World Phone Screen comes up
--Movi_check Start..!!
movinand read fail
Movinand Checksum Confirmation Fail
--movi_checking done!!...
update media, please wait
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
So after this pops up, I try to format internal sd-card, and this pops up:
update media, please wait
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
When I try to reinstall packages:
Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
(Still hoping there is a solution!)

Okay... this is the final step you can try.
This is the manual (or "full") Odin, it's taken from a post by icezar1 in the Development Forum:
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Do not use this if you know you flashed a -LOW- ODIN package (when opening the PDA***.tar or CODE***.tar you will find inside boot.bin or sbl.bin)
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
Download the package from here
Download the phone drivers from DG's thread if you dont have them already. [Note: You should already have this xpiamchris, it will be the same one I asked you to download and install]
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot your phone in Download Mode
Run Odin3 v1.3.exe
Plug in your phone via USB
Click on the button PDA
Choose JF6_secure.tar.md5
Click start
Wait and do not unplug cable until it is finished

I noticed on the reboot, the phone said "data wipe failed"
But phone is acting the same as before..

[GUIDE] how to get IMEI to stick across reboots

This is a rundown of restoring your IMEI and /efs partition. A lot of people lose their IMEI and have no problem restoring it a variety of ways. But if your restored IMEI disappears on next reboot, your problem is something else. I had this, and I believe it was a corrupted /efs partition.
solution, short answer: flash a good efs.rfs file. I did it in Heimdall; I assume it'll also work in Odin. The one I found online (see attachment) restored my efs to the dummy IMEI of 004999010640000. Where I live and on my provider, this gives me network access. From there I could restore my backup nv_data.bin file to /efs. And then my proper IMEI sticks across reboots.
also: kitch posts another way to fix this, here and here.
NOTE: Messing with IMEI has potential legal problems. The attached file restores IMEI to a fairly common dummy number, so I assume it's not a problem. (mods, please delete if this is a problem). The dummy IMEI could work in your area, but that still could pose legal problems. Check in your area, and see the next paragraph.
WARNING/DISCLAIMER: I found this file on Rapidshare. I don't know who made it, put it there, where it might have been linked from, or what exactly is in it. All I had was a filename and I googled it. And all I know about it is that if you have the problems described above and below, then this may work for you. It did for me. If anyone can "see" inside the file to check that it doesn't contain anything malicious, please comment. All I can say is that ClamXav found nothing wrong with BML3_RESTORE.tar.md5 or the efs.rfs contained within it. And that I'm not responsible for what you do to your own phone.
More ways to check if this is your problem:
- You have no signal. In System Settings > About phone, Baseband says Unknown, even if you know you have a modem in there. Also, them going to Status, your IMEI and IMEI SV also say "Unknown". Other people posting about lost IMEI say they have either all zeroes there, or the dummy IMEI 004999010640000.
The rest of this is what I did in GB. I assume if you have this problem, you tried other solutions that got you here too.
- Flashing stock Samsung ROM with repartition doesn't restore IMEI (at least in Heimdall; I can't check Odin). Flashing EZbase Recovery in Heimdall doesn't do it either. They flash, but afterward boots to recovery mode and shows errors about not being able to apply Multi-CSC.
- in Terminal Emulator or adb, running 'mount /efs' returns: 'mount: can't read 'etc/fstab/': no such file or directory'.
- From here, you can still flash a rooted kernel and flash GB ROMs in CWM recovery mode. After each flash, recovery mode shows errors about not being able to mount /efs and/or /dbdata, and not being able to apply CSC.
- From here, if you try flashing to CM7 or CM9, installation aborts. Onscreen error message shows problems with /tmp/updater.sh.
- If you tried to flash a recent kernel with Heimdall, you can get in its recovery mode. I did this trying to get to a known working JB nandroid. I flashed the JB rom again, and it completes. Rebooting sent me back to recovery mode. Repeat rebooting until fed up. Restoring nandroid completes. Rebooting sent me back to recovery mode. Repeat rebooting until fed up.
solution, long answer:
For me, this was from GB.
- Flash the attached file. For Heimdall, untar it (in command line, run 'tar -xvf /path/to/BML3_RESTORE.tar' without quotes, and replacing /path/to/ with the proper filesystem path. If you don't know what this is, try dragging and dropping the file into your terminal window on your computer.)
Then run: 'heimdall flash --efs /path/to/efs.rfs' (without quotes, again replacing path, or drag-and-drop the file into your terminal window)
On first attempt (second was other human error), I did not flash a whole package with PIT file, or repartition. I did later, and that worked fine, too.
- It automatically reboots (unless you told Heimdall not to). You may go to recovery mode and see a bunch of errors about mounting, but applying Multi-CSC is a success. Reboot, and the phone starts normally. You may momentarily see the circle-and-slash no-signal icon in the upper left corner, but soon after it should show signal bars. Your homescreen may show your network somewhere.
- Check IMEI. It should be the dummy number. You can do this with the phone's number keypad (typing *#06#). I prefer to go to System Settings > About phone > Status. This way you can see the dummy IMEI, and IMEI SV should now also show a number. Go back up one level and also check Baseband; that should now show your modem.
- Restore actual IMEI. This requires that you previously backed up your /efs folder. Restoring this is documented better and more thoroughly elsewhere. I went into my /efs backup folder and copied nv_data.bin to /efs. This is easy with Root Explorer. Press the filename, select copy, navigate back up and to /efs. At the top of the screen, click Mount R/W. Delete everything in there (menu, multi-select, select all, delete). Paste the file. Long press the file, change permissions. Make it 644 (Owner is Read+Write, others are Read), save. Long press again, scroll toward bottom of menu and Change Ownership. Make it Radio (1001) and Radio (1001), save. Click to Mount R/O and exit.
- Check it. Go back and check your IMEI and it should be your real one. IMEI SV should probably change, too. (For me, it was 01 in GB, but now it's 03 in ICS). Reboot, and it should remain. Baseband is also filled in.
From here you can flash up to ICS, or whatever, and your IMEI should remain.
note on attachment: The original filename I searched for and found on Rapidshare was BML3_RESTORE.tar.md5. I've changed the extension to be *.tar, so it can upload to XDA. I think Odin users need to add the .md5 extension.
md5 checksum for BML3_RESTORE.tar: f5ab4c90ed60105c8b50e4e9b112e50b
Credit: XDA user magarto is the one whose post led me to this file and fix, from his post here.
errata: This was originally a [Q]-tagged Question thread. I overwrote the OP with this guide and changed the thread title. Hence, the next several posts may seem out of context.

Still unsolved huh? Khmers do have limited access, due to what happened in their country, anyway you can get a better idea here http://forum.gsmhosting.com/vbb/f258/ how efs problems are solved by various box. Just search this forum about efs or post, many Filipinos there .
Having said that, the version of Galaxy S I am using is Korean (has DMB TV, so hardware differences), and to solve this in our version , we simply flash the beginning ROM (with MOVI Files) Its like the Installation Files of Windows, which does a complete setup . This is the last resort for the Korean Galaxy S, solves any and every problems, always wondered why the Galaxy S, does not have this compilation or its only with samsung service centers. anyway
If you have an efs backup, you should try using Root explorer to overwrite (copy paste) the the current efs folder, fix chmod 644 and EXIT using the menu of root explorer and reboot phone to see if it sticks.

thanks for the forum link. yeah, the phone shop nerd was stuck, too. and they did have a box, several that sounded like the octopus box you said.
i've been doing some looking, too, and wondering if it's corrupted file system. i saw several posts about corrupted internal SD, and I don't know if that could be related. my internal SD mounts fine when I boot up, and all my files are there and working. nonetheless, this post seemed interesting, about reformatting in adb with parted:
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
but i still have yet to find out if it's related. flashing anything in recovery, i see this:
E:failed to mount /efs /dbdata your storage not prepared yet please use UI menu for format and reboot actions
ehhh... i'd put off learning more about adb on the backburner. looks like i'm diving in.

Two different issues, internal SD get corrupted when one fails to UNDO lag fix, since samsung uses rfs and lag fixing changes it to ext 4, internal SD will fail to be recognized and needs to be formated to rfs by any Rom using rfs ( mostly stock Roms (to solve that flashing a speedmod kernel, does the trick) But your problem is efs folder
and i came across one person, who had both because he had made a onenand mode lagfix and failed to undo before flashing and was pretty impossible to get over

xsenman said:
and i came across one person, who had both because he had made a onenand mode lagfix and failed to undo before flashing and was pretty impossible to get over
Click to expand...
Click to collapse
ugh ... that does not sound promising.
and i'm not even fully aware yet what lagfix is or does. it had never been an option on any kernel i used since i started flashing roms, only early this year from stock to CM7 and soon after to CM9 and other ICSes. Well, until yesterday, when i tried flashing a supercurio kernel on a GB rom, and that failed. But I did see lagfix options under recovery>advanced. at any rate, i hope i'm not in the same boat.
is there any way in adb to find out if i am?

groksteady said:
ugh ... that does not sound promising.
and i'm not even fully aware yet what lagfix is or does. it had never been an option on any kernel i used since i started flashing roms, only early this year from stock to CM7 and soon after to CM9 and other ICSes. Well, until yesterday, when i tried flashing a supercurio kernel on a GB rom, and that failed. But I did see lagfix options under recovery>advanced. at any rate, i hope i'm not in the same boat.
is there any way in adb to find out if i am?
Click to expand...
Click to collapse
what I am saying is that, you do not have this problem, cause If you had, your internal SD will become unavailable and cannot be used and cannot be formated either ...so just solve the efs problem , thats what you need to concentrate on.

xsenman said:
what I am saying is that, you do not have this problem, cause If you had, your internal SD will become unavailable and cannot be used and cannot be formated either ...so just solve the efs problem , thats what you need to concentrate on.
Click to expand...
Click to collapse
thanks, man. i just did try this, simply taking a Camera photo and opening it in Gallery. also, ran mount in terminal to see, and yeah, saw rfs not ext.
when i try to mount /efs, i get an error:
moutn: can't read '/etc/fstab/': no such file or directory. there's a vold.fstab in there, with paths for mounting the internal and external sdcards. ehhhh... still learning what all this is about.

groksteady said:
thanks, man. i just did try this, simply taking a Camera photo and opening it in Gallery. also, ran mount in terminal to see, and yeah, saw rfs not ext.
when i try to mount /efs, i get an error:
moutn: can't read '/etc/fstab/': no such file or directory. there's a vold.fstab in there, with paths for mounting the internal and external sdcards. ehhhh... still learning what all this is about.
Click to expand...
Click to collapse
efs folder has read only permission, so you cannot do anything you like...don't mess with vold.fstab...you will have problems with your SD cards .
The only thing I can suggest is to go back to th earliest eclair or froyo to recover.
you may need to unarchive the downloaded file and then unarchive the resulting TAR files too
Hence in heimdall you should have
PIT file (s1_odin_20100512.pit), CHECK repartition
IBL+PBL = boot.bin
SBL = Sbl.bin
MODEM = modem.bin
PARAM = param.lfs
CACHE = cache.rfs
DBDATAFS = dbdata.rfs
FACTORYFS = factoryfs.rfs
KERNEL = zImage
But First, try to delete the EFS Folder (using root explorer) shut down, Go into recovery and wipe everything than battery pull to shut down and go onto download mode after that Flash
just a suggestion

xsenman said:
Hence in heimdall you should have
PIT file (s1_odin_20100512.pit), CHECK repartition
Click to expand...
Click to collapse
thanks ... this is where I get hung up. Anytime I check repartition, I get libusb End of Pit errors. It runs fine without repartition. This is Heimdall 1.3.1 and 1.3.2 on a Mac 10.5.8.
I'm going to make an Ubuntu Live CD and see if I can get it that way. I used to have an old Lubuntu laptop, and I remember Heimdall working to flash a kernel when the Mac didn't. It'd be great if the repartitioning is what's holding me back.

aargh. didn't work. Heimdall on Linux does let me repartition, but on the reboot I still get errors that /efs can't be mounted, multi-CSC can't be applied, etc. I tried ezbase recovery and the full stock setup for the original provider from sammobile. I tried deleting /efs, full wiping and pulling the battery like you suggested. I tried separately flashing a dbdata.rfs in heimdall, which was suggested for someone else with mount problems. but, it seems like all the other mount problems people have are with sdcard, and not /efs.
If I restore /efs, is it supposed to write data to /dev/block/stl3? because that file is always 0kb. But I could try the dd command to restore that way... maybe later tonight. it's been a long afternoon working through this.
I also don't know what is the deal with not being able to find /etc/fstab. I saw in some other places that Android doesn't use it, so I don't know what's calling it, and why. Or if that's tied to why I can't flash anything beyond a GB rom; I get errors about /tmp/updater.sh.
EDIT: OK, so at some point with ezbase recovery and manually restoring nv_data.bin to /efs, after a little while I saw that my /sys/block/stl3 (and so /dev/block/stl3) were looking normal. I successfully restored the file, plus the IMEI folder, which has bluetooth info. I did this with flight mode on, toggled it off and connected to my network. About Phone was showing my real IMEI, plus BT and wifi MAC addresses. And I had /sys/block/stl3 looking normal. So I ran the dd if=/sys/block/stl3 of=/sdcard/efs.rfs, and used that efs.rfs file to flash full roms in heimdall, repartitioned. I used ezbase recovery and the stock firmware from sammobile.com for the original mobile provider. Neither worked. On first boot both times, I got errors about not being able to mount /efs or apply multi-CSC. My IMEI on reboot is always "unknown", not even all zeroes, until I fix it. And CWM won't flash any CM7 or CM9 zips, giving status 7 errors that it couldn't mount. I also tried flashing the efs.rfs file alone in heimdall command line, and that didn't work. Ezbase is 2.3.3 and my stock is 2.3.5, and serial number info indicates it was made in 2011 or really late 2010 (i'm loathe to pull the battery off these days), so I wouldn't think Froyo could help out. I've reached out to a few people here who had the same problem, but never posted about a fix, or finally giving up. I'm almost at my wit's end. There must be a solution, some way to reformat or push back /efs data to /stl3.
BTW, can anyone post the filenames of what is in /sys/data/stl3 for their i9000? I'd like to know if I'm missing something in there, at least when it does fill up. Right now, I'm thinking it's gotta be a bad partition.

weird..just can't help wondering why it seems so difficult, I assume you are always practicing standard requirements before and after flashing like
1. Using CWM, make sure to wipe data/factory reset,
2. Then wipe cache, and then go into advanced, and wipe the dalvik cache too.
3. From there, flash the ROM
4. Afterwards, repeat the wipe step as in step #1
5. Continuing on, go into advanced and fix permissions.
6. Finally, reboot the device.
In my version its even more stricter, take a look this is required for an uncomplicated Flash

Hm, I've always done 1-3, as that's what's prescribed in most installation instructions, and still Dalvik even if it's not specified. I've only ever wiped post-flash a couple times, and only because it was mentioned in some threads, plus a whole re-flash of the rom. And I'd never heard of fixing permissions after flashing until HellyBean, but I always did with that.
This problem came up coming off of HellyBean with the test idle2 kernel, to AOKP JB, which apparently boots after a status 7 error and abort, but I only knew that later and didn't try that. I then flashed Semaphore to get to the working CWM 6 backups, and ended up in a loop of recovery modes. In hindsight I should have flashed a whole rom -- I went from a datadata rom to one without that I never booted, then to a kernel without datadata just to get the recovery and nandroid.
Rats, I didn't even think about that.until just now typing this out.
sent from a telephonic device

IMEI BACK.
There was a link in a post here that got me there -- basically, someone uploaded an efs.rfs file. Mods, flag me if this is illegal/against rules, but I'd guess it's not because the file gives you the 0049 IMEI.
But for me that didn't matter -- my partition or the linking was screwed up somehow, and I needed a proper one to flash in Heimdall. I couldn't simply correct my nv_data.bin backup and then export bml3.
The Spanish forum link goes to a dead upload, but I was able to find the file BML3_RESTORE.tar.md5 on Rapidshare. If you need this, it was a rollercoaster. At this point I didn't expect anything to work, and I'm still suspicious of finding a file on the web and flashing it without at least some community I can "talk" to about it.
What happened with the file: I flashed it in heimdall, onto a pretty overloaded and laggy JW5. Rebooted, and immediately saw the circle-and-slash no signal logo, so thought it didn't work -- then it pops up to four bars. I swipe to unlock the screen and it completely freezes. So I went back to ezbase recovery kit and flashed the whole thing (with the CF-root kernel, not stock) plus the efs.rfs file. I didn't repartition because I'm on a Mac, and that doesn't work for some reason, and the linux live CD is painfully slow. It flashes, and after completion, I still get a bunch of errors about mounting, but i get a success message about applying multi-CSC. I reboot, and About Phone shows the fake IMEI, but the homescreen is showing my provider. Also, the file explorer showed my internal and external sdcards.
I reinstalled Root Explorer with Titanium Backup, deleted all in /efs and dropped in my backed up nv_data.bin, changed perms and ownership to radio and radio. Exited folder and reopened, and it was all repopulated. Then I dropped in my backup of the /efs/IMEI folder, only because that has a file with BT info and that didn't regenerate. Rebooted, and all was still there! Finally getting out of this weeklong rabbit hole, and able to come back up to ICS with my real IMEI.
Word of caution, though, if going back up from there to one of the latest ICSes. There's people saying to take the latest CM9 nightly -- if you do that, you're flashing up to CWM 6. If you want to go from there to any of several other ICS roms, you might run into a problem because they might be CWM 5.*. After I had CM9 booted, I went into recovery to flash AOKP M6, lost recovery and ended up having to go *back again* to heimdall. Then onto Team Hacksung's CM9 build 16, then finally to AOKP. Done. And I think at this point I'll lay off the Jellybeans for a little while.

groksteady said:
IMEI BACK.
Click to expand...
Click to collapse
This is great, Now in order to get others who may get into this situation, out of this mess, can you post a step by step guide ( simplified as much as possible)
such that I can link your post to my EFS problems and solutions post, already downloaded Bml3 and will upload to another , so a step by step guide to resolve this will be helpful to others.

xsenman said:
This is great, Now in order to get others who may get into this situation, out of this mess, can you post a step by step guide ( simplified as much as possible)
such that I can link your post to my EFS problems and solutions post, already downloaded Bml3 and will upload to another , so a step by step guide to resolve this will be helpful to others.
Click to expand...
Click to collapse
Sure thing... I'll amend the OP later today. So glad to be out of this mess. I seriously thought I'd be manually restoring my imei on every reboot until I get a new phone.
sent from a telephonic device

xsenman, I changed the OP to a guide, hopefully the symptoms and instructions are clear enough. and thanks for talking me through this; I was losing my mind, and so close to throwing my phone in the river.
for anyone else: xsenman was helping me in another thread too. There, I mention how the official Samsung Service Center here said I had a memory board problem, can't recover IMEI without replacing that, for US$150. I went to one of the many phone seller shops with decent hackers/tinkerers, and they couldn't do it either, and they had Octopus Boxes, or at least a box for Samsung.
anyway. HTH others.
and a tinfoil-hat request: anyone who is able to look at the file attached in the OP, can you see if there's anything troubling or 'weird' in it. I just found the damn thing and tried it. It wasn't the most security-conscious step, but I was in a pinch.

so i had this same problem flashing hellybean 20120820 and used one of the guides here to return to stock then copied my good efs off to my computer flashed all the way back then restored the efs folder but it wouldnt stick. I tried several times fixing permissions and a few other suggestions on this forum but nothing worked. Finally i read somewhere that the cache would restore the efs folder if it wasnt cleared, so i restored my efs thru root explorer to the good one from gingerbread rebooted to recovery, wiped cache, and rebooted. Voila it finally stuck, i dont know exactly why it worked or where i heard clear the cache but it did. Maybe it will work for oyu

Psykologikal said:
Finally i read somewhere that the cache would restore the efs folder if it wasnt cleared, so i restored my efs thru root explorer to the good one from gingerbread rebooted to recovery, wiped cache, and rebooted. Voila it finally stuck, i dont know exactly why it worked or where i heard clear the cache but it did. Maybe it will work for oyu
Click to expand...
Click to collapse
Huh, that's cool. I hadn't read that anywhere before. I'm not in that jam anymore, but its good to know.
I do wonder if I all the other 'normal' methods never worked for me because I was using Heimdall. It shouldn't make a difference, but I did run into basic common problems, like repartitioning not working on Macs.
Thanks for the tip. I hope I won't need to try it.
sent from a telephonic device

I have SC-01C docom tab. during unlocking its imei became null and baseband became unknow. I try this tutorial and result in imei 0000946xxxxx.
But when I restart tab. Imei again null.
Note: there is no option of 644 in Permission.
Please help me to solve this.

nsnobel2 said:
I have SC-01C docom tab. during unlocking its imei became null and baseband became unknow. I try this tutorial and result in imei 0000946xxxxx.
But when I restart tab. Imei again null.
Note: there is no option of 644 in Permission.
Please help me to solve this.
Click to expand...
Click to collapse
Sorry to get to this reply so late. And, that I'm not sure I can help you -- I don't know anything about this tablet. This guide helped me with a Samsung Galaxy S i9000. From a quick search online, the PIT file you'd use is different. I don't know for sure, but I would guess it's possible that your EFS partition is different from the i9000, and this method would not work for you.
For permissions, you should be able to change them by long-pressing a file in Root Explorer, Root Browser or similar apps; it's not an option you choose, you manually toggle r/w, r and r for owner, group and others, respectively. Or you can use the chmod command in Terminal to set to 644, same thing.

Is it possible to get back contacts data in N7000 stuck at boot logo?

This may be the last chance to get back the needed important data (please don't ask the awkward question: why not back up the data first) .....
Tried the official SAMSUNG repair office, they said no way!!! Tried search the net and not much available either!
Any expert here can help?
Problem:
Galaxy Note 1 GT-N7000, possibly still in unrooted Ginger Bread, suddenly stuck at boot logo. Press+hold Power/Vol Up/Home brings the machine into recovery mode showing:
1. the green Android robot and yellow arrow out from a file box logo,
2. messages displayed:
<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
<in Red>
<in yellow>
Media files copy failed.
# MANUAL MODE #
-- Updating application …
<in yellow>
..<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
Copy application failed.
<in Red>
..<in yellow>
-- Applying Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/TGY/system/’.
Successfully applied Multi-CSC
<in yellow>
Then, the usual Android system recovery message <in blue> for reboot, apply update, wipe data/factory reset, wipe cache, test redbend fota displayed at the top part of the screen.
3. Tried wiping cache partition and reboot, no luck with the same situation after reboot.
4. The SAMSUNG repair office said it’s not the battery problem. All data will be gone for rebooting the machine.
The data are more important than the machine, ie, saving the data is more important than saving the machine.
Any suggestions and directions for a workable solution will be highly appreciated.

there is a possible way ... do at your on risk..
1. boot into dwonload mode and connect the phone to PC.. open odin and check if connecting fine
2. download philz kernel for for ICS/JB (tar version) and flash it using the PDA tab in odin. (This will not boot the GB rom but should give you access to CWM)
3.Once flash is completed, remove the cabe and battery.. put the battery back in and boot into recovery mode, (vol up+home+power) .. You should see CWM recovery
4. Contacts can be backuped up by doing a nandroid backup of your rom. for the data in InternalSD, go to mounts and storage and choose mount USB storage.
conect phone to pc and wait for the drivers to appear.
5. copy what ever data you need.

It is possible.
Flash CF Root Gingerbread kernel using PC Odin.
Drop into recovery and connect your phone to PC.
From ADB you'll be able to copy (backup) ANY file you need.
DO NOT perform factory reset / wipe data or you'll lose the data.
---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------
Ohh yes nandroid backup too will work.

Easier way. Do a nandroid backup on recovery. Flash the same rom you were using. Advanced restore of data partition of the nandroid.

Thank you very much guys for all of your quick and valuable replies.:good::good:
Please excuse my ignorance as I’m only a dummy, actually the worst, an old dummy!!
In order not to make the suitation worse, I’d like to know/clarify the following details before proceeding to the suggested ways:
@nokiamodeln91:
1. Connected to PC with the N7000 in SAMSUNG logo display, opened Odin3 v1.85, ID:COM column shows <in yellow>0:[COM4] and Message column shows<ID:0/004>Added!!
Is download mode=press&hold [power+vol up+home] keys?
2. In the thread: http://forum.xda-developers.com/showthread.php?t=1901191
Trying to download philz-cwm6-n7000, found the following 5 tar files:
PhilZ-cwm6-XXLT5-OXX-5.03.0.tar.md5
PhilZ-cwm6-ZSLO2-OZS-5.03.0.tar.md5
PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5
PhilZ-cwm6-DXLSE-OLB-5.03.0.tar.md5
PhilZ-cwm6-JPLSB-UAE-5.03.0.tar.md5
Which one is suitable for an UNROOTED GingerBread N7000 with csc/TGY/system?
Will try to follow the other steps after clarifying the suitable tar file.
@Boy124:
1. What is CF Root Gingerbread kernel? Where can I download a copy for an UNROOTED N7000?
2. Please elaborate on or direct me to detailed ADB procedures, preferably a step-by-step guide if not asking too much. I’ve downloaded adt-bundle-windows-x86-20130219. How to copy (backup) the contacts data?
3. Thanks for reminding not to wipe data and perform factory reset.
@projeto56 and Boy124:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Hope you guys have enough patience to bear with me and answer the questions.
Thanks again.

@liway
CF Root is not necessary.
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Flash Gingerbread firmware with PC Odin again.
Root it. If you have Titanium Backup Pro, you can directly restore data from a nand backup. Or restore data only after rooting your ROM.
Lemme know if you need further assistance.

liway said:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Click to expand...
Click to collapse
Do this:
Boy124 said:
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Click to expand...
Click to collapse
But afterwards, i recommend you to flash a JB stock ROM directly from your new recovery. And after you've set it up, you either restore your data from your nandroid, or you use titanium backup pro to restore only what you need (recommended).
Anyway, if you've set up your google account previously, probably your contacts are already saved in the cloud.

You need to connect the phone in download mode (vol down + home + power). Then volume up to continue. The screen should show downloading.
Now connect the phone to pc and use odin to flash any tar version of the kernel. (like ddlsc). Select on pda tab.
None of these kernels are suitable as it will not boot on GB. This is just for you to get into an advanced recovery to backup your data before you wipe and get your phone working.

Following the suggested procedures, set the machine in downloading mode to download PhilZ-cwm6-DDLSC-ODD-5.03.0.tar, the bar below KERNEL square in Odin becomes completely green with the Message displayed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
It stayed at this stage for hours and seems stopped there.
Tried to boot it in recovery mode [vol up+home+power], this time only the boot logo with an exclamation mark (!) in yellow triangle. Odin message:
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Put back in downloading mode again, and the machine now is exactly at the same stage with the above message displayed and apparently halted at "NAND Write Start!!". The machine's screen remains in the downloading mode.
What should I do next?

Make sure kies process is not running in task manager. Use the main usb ports. Use samsung usb cable only. Reboot the phone in download mode and try again. The tar file should be in pda.

kies process is not running in task manager.
using one of the main usb ports.
Cannot locate the original samsung usb cable, using ordinary USB 2.0 cable. Will try to find the original samsung usb cable and try again later.
The tar file is in pda.
Thanks.

maybe a pciture of where file should be added in odin will help him/her. flashing kernel takes only seconds. as i can see drivers were properly installed from the descriptions above.

In Odin, I've ticked the box for PDA, then put the file with the whole path name for the folder in the column after PDA.

Tried again with
1. sure that all kies process is not running in task manager.
2. using one of the main usb ports at the back plate of a desktop PC.
3. Using an original samsung usb cable from Note 2 (should be the same as for this Note 1?),
4. The tar file is in pda, and path/location stated in the box after ticked PDA in Odin.
....
Still halted at the stage of NAND Write Start!!:crying:

did you reboot into download mode? you should not continue from a failed flash. reboot
restart the pc and run odin as admin.
disable any AV and Firewall softwares.
if still a no go then try on a different pc

Disconnected the machine. Taken away and put back the battery. Rebooted in download mode [vol dn+home+power].
Restarted the pc and run under a user with administrator right.
Disabled all norton internet security protections. Turned off modem/router connection.
Connect to Odin, still no go. Same situation, halted at NAND Write Start.
Will try to arrange another pc next day or so.
In the meantime, any other alternatives worth trying?

Even a bricked phone in download mode should be able to flash a kernel.
What you could try is unintall kies and usb drivers. And then download samsung usb drivers from developer. Samsung.com and install it again. Then try.

- deleted Kie and SAMSUNG USB driver. Restart the PC.
- reinstall samsung usb driver.
- restart in download mode and connect PC.
still no go!
to recap: using Odin3-v1.85 and PhilZ-cwm6-DDLSC-ODD-5.03.0.tar

diff PC seems to be the last option
though you could try this. download http://d-h.st/FVh. its the PIT file. Select the PIT file in PIT Tab.. and kernel in PDA tab..
make sure repartition is checked.. then flash again and see..

flash wit PIT and kernel.
In Odin, Set Partition shows up in the 1st square and message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
seems halted there!
How long will I have to wait?

[Q] Boot loop on Captivate after reimaging stock

My girlfiend's Captivate had CM10 with ClockWork recovery. While traveling abroad it stopped booting (that's from her words - I am not sure what exactly happened ) so she brought it to a local "service center" where they attempted to fix it. not sure what they did but it looks like they tried to flash the stock - the phone boots a little past ATT animation into the stock animation and then reboots.
I went into recovery mode and it looks like stock recovery, not clockwork. So, the phone is in an unknown state and I don't know what to do to fix it. I assume there an image I can flash using ODIN to put it into some known state so I could take it form there and flash what I need. I am a beginner-intermediate ROM flasher so please give as many details as possible on a fix.
Thank you!

andreyl79 said:
My girlfiend's Captivate had CM10 with ClockWork recovery. While traveling abroad it stopped booting (that's from her words - I am not sure what exactly happened ) so she brought it to a local "service center" where they attempted to fix it. not sure what they did but it looks like they tried to flash the stock - the phone boots a little past ATT animation into the stock animation and then reboots.
I went into recovery mode and it looks like stock recovery, not clockwork. So, the phone is in an unknown state and I don't know what to do to fix it. I assume there an image I can flash using ODIN to put it into some known state so I could take it form there and flash what I need. I am a beginner-intermediate ROM flasher so please give as many details as possible on a fix.
Thank you!
Click to expand...
Click to collapse
The internal SD probably died, which is why it stopped booting. The service center was probably some local store that tried to fix it blindly by flashing it back to stock, which leads you to the state it is right now.
Steps:
1. Get a spare MicroSD if you don't already have one on hand. Format it blank. Copy a copy of Glitch Kernel from here (http://narod.yandex.ru/disk/5065044...1e2649/CM7Captivate-Glitch-V13_1-REL.zip.html). Sorry about the Russian site, but the original mirror died, at least for me.
2. Flash Semaphore Kernel (http://semaphore.gr/kernels/Semaphore_2.5.0c.tar)
3. Pull the battery, reboot into recovery. Flash Glitch Kernel. Reboot recovery
4. Use Glitch Kernel to partition the SD card. The EXT partition will be your replacement /data partition, so set the size accordingly.
5. Flash CM7 twice, without rebooting.
6. Make sure CM7 boots
7. Flash your ROM. Before rebooting, flash the patch from here (http://forum.xda-developers.com/showthread.php?t=2177876). Stick to 4.2.2 and below

thebulletfromhell said:
The internal SD probably died, which is why it stopped booting. The service center was probably some local store that tried to fix it blindly by flashing it back to stock, which leads you to the state it is right now.
Steps:
1. Get a spare MicroSD if you don't already have one on hand. Format it blank. Copy a copy of Glitch Kernel from here (http://narod.yandex.ru/disk/5065044...1e2649/CM7Captivate-Glitch-V13_1-REL.zip.html). Sorry about the Russian site, but the original mirror died, at least for me.
2. Flash Semaphore Kernel (http://semaphore.gr/kernels/Semaphore_2.5.0c.tar)
3. Pull the battery, reboot into recovery. Flash Glitch Kernel. Reboot recovery
4. Use Glitch Kernel to partition the SD card. The EXT partition will be your replacement /data partition, so set the size accordingly.
5. Flash CM7 twice, without rebooting.
6. Make sure CM7 boots
7. Flash your ROM. Before rebooting, flash the patch from here (http://forum.xda-developers.com/showthread.php?t=2177876). Stick to 4.2.2 and below
Click to expand...
Click to collapse
Thanks for the comprehensive answer.
I am stuck on #2. Trying to flash Semafore Kernel using Odin v1.85 and it's failing:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is in Downlaod mode and USB driver is installed (ODIN sees the phone as 0:COM3)

Can you try another USB port/cable? If that doesn't work, try heimdall?

I removed and reinserted the battery, put it into download mode and now instead of Downloading it shows "Firmware update failed". ODIN can still see it but it gets stuck on SetupConnection. I've tried three different USB cables and all three USB ports my box has - same thing, stuck on SetupConnection. I am going to try Heimdall now

Ok, Heimdall failed to detect the phone. I tried to run Odin 3.09 instead of 1.89 and it seemed to work! This is the log:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
It did shut down the phone after completion. Does it look good?
Any way to test if the internal SD is indeed dead or not? I would much rather try to use it than an external SD

Ok I think I am making progress - after flashing Semaphore kernel I was able to boot into CWM recovery. I also chose to format /data pertition and it did it without error, which tells me that probably internal SD card is not dead.
The next problem - recovery doesn't see the external SD card. That I overcame by pushing C7 Glitch onto the internal SD card (it's alive!) using adb push.
Then I installed Glitch from internal SD. And then **** happened. I booted into Glitch recovery to install CM10.2 and it started err'ing that it can't find /sdcard. I could still see the sd card using adb shell. Using ODIN I reflashed Semaphore, thinking that Glitch is havign a glitch, but now Semaphore recovery can't see /sdcard either!
What do i do? teh internal SD card was accessible a few minutes ago - i copied CM7 there, i installed CM& Glitch from it. And now I can't access it any more. Any ideas?

From what I read I might need to reformat/repartition my internal SD card - how do I do that?

andreyl79 said:
From what I read I might need to reformat/repartition my internal SD card - how do I do that?
Click to expand...
Click to collapse
...You can't. It's a hardware problem, and the only permanent solution is to get a new board. There is no interface to access the raw internal SD (that we know of). Your best hope is just to follow the steps I've listed, and hope one day the card comes back to life (mine never did, although some people did on this forum).

thebulletfromhell said:
...You can't. It's a hardware problem, and the only permanent solution is to get a new board. There is no interface to access the raw internal SD (that we know of). Your best hope is just to follow the steps I've listed, and hope one day the card comes back to life (mine never did, although some people did on this forum).
Click to expand...
Click to collapse
I am not sure how to follow your steps in this situation - how do I flash CM7 Glitch if I can't copy it onto the internal SD? My external SD is not recognized by Semafore, and I think it's a known issue as I saw other people talking about it as well (Semaphore not seeing external SD).
Any ideas?

Try Corn Kernel: http://forum.xda-developers.com/showthread.php?t=1294477

thebulletfromhell said:
Try Corn Kernel: http://forum.xda-developers.com/showthread.php?t=1294477
Click to expand...
Click to collapse
Just flashed Corn, getting a boot loop (as expected I guess) but I can't get into Recovery mode. Vol UP+Dn+Power just boots it up and gets it into the loop.

http://forum.xda-developers.com/showthread.php?t=893880 Speedmod? Just partition straight from here, and flash CM7.
If that doesn't work, flash GearKernel/Semaphore for ICS/JB/KitKat, then flash Glitch from there.After that, format everything multiple times before you try and flash CM7 (or it'll perma bootloop, since the partition layout is wrong, and fixing it is a pain. I have no idea how I got mine working back then)

thebulletfromhell said:
http://forum.xda-developers.com/showthread.php?t=893880 Speedmod? Just partition straight from here, and flash CM7.
Click to expand...
Click to collapse
Maybe I'm not understanding smth... I flashed Speedmod, went into Recovery. What do you mean by "partition straight from there" - partition what? It still gives errors if I try to access /mount/sdcard or /cache or /boot or /system.

andreyl79 said:
Maybe I'm not understanding smth... I flashed Speedmod, went into Recovery. What do you mean by "partition straight from there" - partition what? It still gives errors if I try to access /mount/sdcard or /cache or /boot or /system.
Click to expand...
Click to collapse
Format everything, partition the SDcard from there (its in one of the menus, can't remember which). That'll partition your external SD, to replace the internal one.

thebulletfromhell said:
Format everything, partition the SDcard from there (its in one of the menus, can't remember which). That'll partition your external SD, to replace the internal one.
Click to expand...
Click to collapse
Ok, after a few days of the phone resting on my table it somehow decided it can see the external SD card as /mnt/sdcard and I was able to copy cm-7.2.0-captivatemtd.zip onto it and flash it.
Now, when I reboot it shows cyanogenmod logo and goes straight into recovery. Second attempt to flash the same 7.2 shows an error:
Installing update..
Checking state of BML/MTD...
assert failed: run_program("/tmp/updater.sh") == 0
E: error in /sdcard/cm-7.2.0-captivatemtd.zip (Status 7)
Installation aborted.
UPDATE: I flashed 7.2 twice in a row, second time it rebooted in recovery. Then I flashed CM10.2 twice in a row, first time it showed the error and second time it just rebooted into the recovery, but it shows the new version 6.0 of CWM recovery so something got updated. BUT - it still reboots in recovery - it feels like it doesnt want to flash the actual OS, just CWM
UPDATE 2: While in teh CWM recovery, I found "Partition sd card" option and i partitioned it. No errors. But now if I try to flash CM 10.1.3 I get this error:
E: error in /sdcard/cm-10.1.3-captivatemtd.zip (Status 0)
Installation aborted
Update 3: I tried to install SlimRom 3.1 - it rebooted to CWM, then I reflashed it twice again, each time no errors but it went really fast - prolly 15-20 sec each install. And then again it reboots into recovery. No errors anywhere. I am stuck at this point - after flashing any ROM it reboots into recovery.
Any ideas what's going on?

Ok, I decided to step back and just follow your initial advice.
1. I flashed Glitch
2. In Glitch I partitioned SD card
3. I flashed CM 7.1 twice
4. I rebooted and the phone still reboots into recovery
This is boot.txt log:
Code:
Thu Sep 4 04:32:38 GMT 2014
Bad block 19 at 0x4c0000.
Partition info: Total 11534336, Erase 262144, write 4096
Bad block 43 in reservoir area, skipping.
Found mapping block mark at 0xa00000 (block 40).
Found start of mapping table.
Found raw block mapping 91 -> 2042
Partition relative block mapping 19 -> 38
Absolute mapped start addresses 0x16c0000 -> 0x1fe80000
Partition relative mapped start addresses 0x4c0000 -> 0x980000
Found raw block mapping 766 -> 2041
Found raw block mapping 1387 -> 2040
Found raw block mapping 1647 -> 2039
Found raw block mapping 1800 -> 2038
Bad block has properly mapped reservoir block 19 -> 38
Successfully dumped partition to /stage1/boot.bin
umount: can't umount /sdcard: Invalid argument
cpio: dev not created: newer or same age file exists
cpio: proc not created: newer or same age file exists
2584+0 records in
2584+0 records out
1323008 bytes (1.3MB) copied, 0.201845 seconds, 6.3MB/s
cpio: sys not created: newer or same age file exists
cpio: system not created: newer or same age file exists
4401 blocks
Thu Sep 4 04:32:41 GMT 2014
What can I do?

Flash back to stock and try again. Make sure the flash actually takes a while (so the conversion is successful)

thebulletfromhell said:
Flash back to stock and try again. Make sure the flash actually takes a while (so the conversion is successful)
Click to expand...
Click to collapse
I can only find a stock image as Odin one click, but for some reason when I launch it, it doesn't see my phone. When I launch regular ODIN it can see the phone. Do you know of any non-one click stock image locations? All I could find was expired links

Odin one click is very hit-or-miss. It worked on my desktop, but not on my iMac or laptop.
http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3