Database Develop

[q] heeeelp!!! Please!

I have just bought galaxy s and i flashed to jm5 then used samset 1.9f then i think i have some fixlag on. BUT SUDDENLY WHEN I TRY TO REFLASH TO JM5 MY SGS GOT BROKEN??? i took some pic but how i add them here //sorry i am very new user
On screen all iget for options is these:
Android system recovery <2e>
Samsung Recovery Utils
- for BML-
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
----------------------------------------------
update media. please wait...
E:Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.

Have you tried to reflash your Galaxy with Odin?
Downloads:
Odin
JM5 Firmware PASS: samsung-firmwares.com
PIT 512
Howto:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (PDA=CODE, .PIT and PDA are required. CSC and Modem are HIGHLY recommended. They may be necessary depending on the PDA! Try flashing all three BEFORE reporting bugs, if you only used one initially!)
3.Remove the SD card and SIM card from the phone.
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.If the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
http://forum.xda-developers.com/showthread.php?t=723596

Your SGS is not broken you are just doing things without the right knowlegde.
Don't do things you don't understand !!!
Read before you do something !!!

Yes i have flashed mtimes with odin and successfully but this time its differrent i can't flash any rom and i keep having that error above

Welll it worked when i changed the .pit file which came with Odin to your .pit file and mine was 513 yours 512...but at the end when it booted there was one red line about some sytem ... it went fast so i could'nt read it but anyway thnx alot

You always have to use the correct PIT File for a Firmware.
Look at this:
http://samsung-firmwares.com/I9000.htm
Please read the FAQ Thread. ;-)

RTFM
10char

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

Device semi-bricked no way to rom zips to sdcard

Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated

mj_blue said:
Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
Click to expand...
Click to collapse
You're telling adb to push the file into a zip? Anyways, ADB sadly does not work in our CWM (nor USB mounting as you might have noticed), so the only way you can restore functionality and start again (no erasure of your SDcard contents so don't worry) is to use ODIN back to stock. From there, start again. It could be your download was corrupted (download again), because I could flash it fine, but eventually went back to KJ5 for functionality.
Edit: Check my guide below for ODIN FAQ and how-to if necessary.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...

kallt_kaffe said:
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
Click to expand...
Click to collapse
Edit: Sent you a PM.

was there a resolution to this issue? i have the same exact problem as the OP.
However, I cannot restore back to stock with ODIN. when writing my system.img.md5 my restore fails.
I know my devices can be fixed! i just have not found my answer yet.

you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.

How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...

ellokomen said:
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
Click to expand...
Click to collapse
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.

wyatt23 said:
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
Click to expand...
Click to collapse
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).

nirogu325 said:
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
Click to expand...
Click to collapse
I have done this. when i re-flash the odin stock image, i get stuck at the restoration of system.img.md5.
I uninstalled and reinstalled the samsung usb drivers and installed the latest. i've tried different usb ports. i am truly at a loss.
i installed an odin flashable version of CWM 5.0.2.6 (? i think thats the version), but adb was not available on that.
Does adb work on the stock recovery? Do you know where i can find this CM9 Kang thread? do you know if their version of CWM in flashable via Odin? that's the only way i can push anything onto the tablet as of right now.
btw... if i restart the tab unconnected to any USB cables, I get a message saying to reconnect to Kies and perform a recovery. IMHO kies is useless.
I am still stuck. I am open to literally anything not physically harmful to my tab.
Is nvflash an option for fixing this? I've never used it before, but if it can help I would be down.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
If i push files, they look as tho they are transferring, but i think they are not really making their way their on to the device.

After doing a little prying today at work, I found a .pit file. I read that this contains the partition information for drive.
I downloaded the stock 3.1 image, extracted it, and i found a P5.pit. Perhaps, I can use that PIT file, while keeping Re-Partition checked, and reflash the overcome CWM?
I know others have run into my exact problem and fixed it. there's gottttta be a way.
i will keep posting my progress and/or reading for others' suggestions.

When trying to flash KJ4 , i get the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7310XEUKJ4_P7310XXKJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img.md5
<ID:0/006> NAND Write Start!!
<ID:0/006> bootloader.bin.md5
<ID:0/006> cache.img.md5
<ID:0/006> hidden.img.md5
<ID:0/006> recovery.img.md5
<ID:0/006> system.img.md5
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then when looking at my galaxy tab screen i see the following:
Code:
Partition size is small! [Bin:173568 > Part:147968] (4KB unit)
WriteExt4Partition: Error to OpenCompExt4![err:0xa]
DownloadPartition_odin: Error to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xa]
I have to believe my partition table is all botched.

wyatt23 said:
I have to believe my partition table is all botched.
Click to expand...
Click to collapse
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.

nirogu325 said:
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
Click to expand...
Click to collapse
and should i keep 'Re-Partition' Checked?
---------- Post added at 02:21 PM ---------- Previous post was at 02:12 PM ----------
wyatt23 said:
and should i keep 'Re-Partition' Checked?
Click to expand...
Click to collapse
ehh, so i tried it without re-partition. didn't work. still cannot mount /sdcard.
tried it with repartition checked with clockwork 5.0.2.6 and I'm stuck at the "choose download mode or recovery mode" screen. if i select recovery, the screen blinks.
TO FIX THIS: I can use odin 1.85 to flash KJ4. however, this will fail at system.img.md5. However, stock recovery will be bootable. stock recovery will give me errors saying most of my partitions cannot mount.
I then can use odin to flash clockwork 5.0.2.6 and enter recovery.
the partitions are still botched if i go that route.

OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.

Glad to hear you fixed your issue, thought I'd add a few side notes as I had the same problem as you pretty much but fixed it at 3am and went straight to bed and was gonna post this morning.
For my situation I was doing it all on a lenovo T500 so for any1 using one flash with the usb port closest to you, in win 7 there seems to be a difference in this port possibly being the only port with always on charge feature, the drivers handle this port differently.
Install or reinstall drivers with the tab unplugged and only plug it in once your already in download mode.
I used the same pit file posted on the previous page and used the stock 3.1 pda, no csc or modem or bootloader files, would still hang wen other files were included. Re-partition checked. Only use pit file once, later flashes shouldn't require it as you've just rectified you partition table.
Once you got 3.1 on there then continue the 3.2 flashes as you wish and hopefully no more problems.
All done trough odin and please people take your time with these steps, the rom should only take 2-3 mins and if it pauses for more than 1:30, its hung, just press and hold power button leaving everything plugged in and odin open and go straight back into download mode and try again.
I've done this several more times with 8 more roms and havent had an issue with any (all morning). I've broken it on purpose then gone through these steps so that the information is as functional as I can make it.
I know its querky but hopefully this saves someone the anguish we went through.
Sent from my GT-P7300 using Xparent Blue Tapatalk

wyatt23 said:
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Click to expand...
Click to collapse
Lol no I don't develop. But I am glad you found the way! That was the objective!
Sent from my SGH-T959.

Hello my honorable SGT colleagues, I managed to roll back from Overcome P7300 v2.3.0 to the Russian v3.1 stock ROM (PDA/CSC/PHONE) flashing it by Odin 1.85 together with p5_0614 PIT mapping table file kindly provided above by Nirogy325, however in my case in attempt to fix modem firmware. All operations including ROM re-partitioning went absolutely smoothly! However to my regret, this has not fix my problem – every ROM (either stock and custom) I used to try do not flash PHONE firmware properly, with basedband version always indicated as “unknown” in the system properties and GSM/CDMA modem not operable… this malfunction happened after Google map app inadvertently hanged up and I tried to shut down the tablet.. does anybody have a clue what happened with the damned tablet and what might be possible cure? Will be extremely grateful for any advice

Thank you!
Thanks wyatt23 & nirogu325. I had this exact problem and downloaded 7-8 pit files that weren't working until I found this. I was about to get a baseball bat and go Office Space on the tablet. It's working fine now and will get a custom mod as soon as it charges.

[Q] SecSetupWizard stopped - 4.1.2

Good afternoon. I need help, URGENT!
I can say that I have some experience with S2, S3 and S4 currently with sufficient skills to perform upgrades, installations, restorations.
What happens, that recently got an S I9070 Advantage and how it was decided to perform the ROM 2.3.6 update to the ROM with CSC DBT latest 4.1.2.
Update fallhou to restart the first time (when you enter the recovery mode to format the cell) appeared the following error message:
E: failed to mount / efs (invalid argument)
E: failed to mount / efs (invalid argument)
# MANUAL MODE #
- Appling Multi-CSC ...
Applied the CSC-code: unknow
Successfully applied multi-CSC.
E: failed to mount / efs (invalid argument)
E: Can not mount / efs / log / boot_cause
E: Can not open / dft / log / boot_cause
Restarted manually and when you perform the initial settings of the Samsung, I get an alert with the following error:
The process com.google.process.gapps has stopped
Clicking Ok and proceed with the setup, but once you get to the last step I get the following error:
The SecSetupWizard stopped.
I click OK again, but this time returns the option to choose the language, making it impossible to access the cell.
Performed the downgrade to 2.3.6 it starts, it works normally, have the IMEI BACKUP, but I can not restore, need a form, a script to format the phone completely, even if you delete the IMEI.
Nor is it possible to install any CUSTOM ROM. Only this version that comes with the file. PIT, CSC and CODE.
Does anyone have a light, guidance?!
I look back.

Which firmwares were they exactly?
Sent from whatever the hell you want to think it is. I ain't yo mama.

I do not know the exact version 2.3.6 had, considering I got this phone yesterday. And knowledge to update other models, such as S2, S3, S4've downloaded the FW-Updates.com-Samsung GT-I9070-DBT-I9070XXLQE-1365486223 and gave this error when installing.
I found a complete FW Forum here to perform the downgrade, did, went back to GB, the phone works as usual, however, when you first start the errors appears to start in recovery mode:
E:failed to mount /efs (No such file or directory)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:check_selective_file:Can't moun /efs
-- Copyng media files...
E:failed to mount /efs (invalid argument)
Sucessfully copied media files.
# MANUAL MODE #
-- Updating application...
Copying Contents.
Successfully updated application.
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
The following report from ODIN - Downgrade 2.3.6.
Added <ID:0/005>!
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> CODE_GT-I9070_I9070DXLD1_CL1068093_REV00_user_SEC_KEY_LD1_8G.tar.md5 is valid.
<OSM> CSC_GT-I9070-MULTI-CSC-OLBLD1_SEC_KEY_8G.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> Set PIT file ..
<ID:0/005> DO NOT TURN OFF TARGET!
<ID:0/005> Get PIT for mapping ..
<ID:0/005> Firmware update start ..
<ID:0/005> GT-I9070_EUR_XX_8G.pit.md5
<ID:0/005> NAND Write Start!
<ID:0/005> EFS.img.md5
<ID:0/005> STE_boot.bin.md5
<ID:0/005> Cspsa.img.md5
<ID:0/005> Ipl.bin.md5
<ID:0/005> Kernel.bin.md5
<ID:0/005> Kernel2.bin.md5
<ID:0/005> Mem_init.bin.md5
<ID:0/005> Modem.bin.md5
<ID:0/005> Modemfs.img.md5
<ID:0/005> Normal.bin.md5
<ID:0/005> Normal2.bin.md5
<ID:0/005> Param.lfs.md5
<ID:0/005> Power_management.bin.md5
<ID:0/005> Ssgtest.img.md5
<ID:0/005> System.img.md5
<ID:0/005> Ums.rfs.md5
<ID:0/005> Userdata.img.md5
<ID:0/005> GT-I9070_EUR_XX_8G.pit.md5
<ID:0/005> Cache.img.md5
<ID:0/005> Hidden.img.md5
<ID:0/005> RQT_CLOSE!
<ID:0/005> RES OK!
<ID:0/005> Completed ..
<OSM> All threads completed. (Succeed 1 / failed 0)
Added <ID:0/003>!

The ODIN steps were right....but why do you have so much efs errors? Is your phone network locked?
Sent from whatever the hell you want to think it is. I ain't yo mama.

Cell functioning normally to return to GB, JB but it does not start. Dandos the errors mentioned in the first post (The process com.google.process.gapps has stopped and The SecSetupWizard stopped.) Getting a constant loop. I need a solution to completely erase (the S2 / S3 / S4 - there is a script that does all this procedure, but this model did not find anything.
I have the backup of the IMEI (if it is corrupted) and the program EFS_Pro_1.9.12_Release even in the most current version EFS_Professional_2.0.40_Release gives error when trying to restore.

The EFS errors are because the S Advance has a special way of storing the EFS, much different from the SII.
But EFS errors are not my forte, hopefully someone will be able to help you out.
Sent from my GT-I9070P

Installing the JB by ODIN:
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> I9070VJLPD_I9070ZTMLPD_I9070VJLPD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished sucessfully ..
<OSM> Leave CS ..
Added <ID:0/005>!
<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> cache.img.md5
<ID:0/005> NAND Write Start!
<ID:0/005> hidden.img.md5
<ID:0/005> kernel2.bin.md5
<ID:0/005> kernel.bin.md5
<ID:0/005> modem.bin.md5
<ID:0/005> normal.bin.md5
<ID:0/005> param.lfs.md5
<ID:0/005> power_management.bin.md5
<ID:0/005> system.img.md5
<ID:0/005> RQT_CLOSE!
<ID:0/005> RES OK!

I don't see any problem.....weird....
Sent from my GT-I9070P

SOLVED!! (Y)
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA

tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
Click to expand...
Click to collapse
this really can be solved?

Efs.img help
This procedure actually works if done with the files available in the posting. In my case solved this problem, but now face a bigger problem. My backup IMEI is corrupted, and you can not restore it.
I need a file EFS.img to perform some tests. Someone with courage and willingness to send me that file?!

HELP
Didn't work for me :crying:
PLS HELP
I did every step till 10 but after i can't continue cause secsetup wizard had stopped!!!
Sorry if im n00b

Help
I get my imei with *#06# (the correct).And i can phone others,so guess there is no problem with the efs folder :S
2.3.6 runs gr8 but 4.1.2 still doesn't.Help me!!!!!!

God....Tussi great hooo....
It worked perfectly......saved my phone....:good:

tgabor7 said:
I get my imei with *#06# (the correct).And i can phone others,so guess there is no problem with the efs folder :S
2.3.6 runs gr8 but 4.1.2 still doesn't.Help me!!!!!!
Click to expand...
Click to collapse
Hi, tgabor , I had exactly same problem, I have tried everything, finally I have come to the conclusion that it can be solved by service centre or some tools like octopus box. Buying those tools are costly option. I have taken my phone to service centre after flashing jb(my phone was in warranty) and they repair it within one day for free . before going to service centre you should wipe your custom rom count using triangle away. You can see your count in download mode.
Sent from my GT-I9070 using XDA Free mobile app

tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
Click to expand...
Click to collapse
what if i dont have the efs backup? can i still get the phone working?

tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Click to expand...
Click to collapse
hi
my problem in step 6
my screen phone is off and phone will be restart and cwm can't be install : (

Aminhitman said:
hi
my problem in step 6
my screen phone is off and phone will be restart and cwm can't be install : (
Click to expand...
Click to collapse
I think there are 2 versions of CWM, one maybe not working on JB. Use right one.

[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