Database Develop

[Q] Bricked, and Odin doesn't fix it

I updated my phone to Cognition 2.1.2, and think i bricked it. I was on Cognition 2.1.1, i disabled the lag fix as per the instructions, and then installed cognition 2.1.2 with Rom manager. when my phone rebooted it seemed to work fine. Then i realized that there was no calculator app installed anymore. I went into the settings screen, but when i clicked on any of the options it would highlight, but not do anything. I rebooted, but i got stuck on an ATT boot loop.
I then pulled the battery, got into the download mode with the button combo, and did an odin oneclick back to stock. however, when it rebooted it went into the stock recovery console and gave an error message "cant mount \dev\block\ stl11"
After that i tried updating with odin 3 to JH2. Everything went ok, but when it reboots it still goes to recovery, but this time it gives me a differnet error
Code:
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
run_program: child exited with status 1
E: Can't mount /dev/block/mmcblk0p1
(No such File or Directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
I can boot into download and recovery with the button combos
I can use adb when in recovery , I'm not sure what to do though (I can't mount with shell, nor can i get to su
I can't get to ClockWork Mod Recovery as it was'nt the last update.zip, and when i try to reinstall packages it says
Code:
E:can't mount SDCARD:update.zip
Installation aborted.
I'm pretty sure this has to do with the lag fix. I think that odin can't wipe the ext4 partition even though i disabled the lag fix.
Please help, am i completely bricked? If so should i return to att even though its been rooted? I guess i could say it was from the OTA.

I would suggest making sure that you disable the lagfix by
Code:
adb shell
touch /sdcard/voodoo/disable-lagfix
Reboot, and it will probably say "converting back to rsf blah blah blah" It takes like friggin 10 minutes to disable
Then I would try to replace the update.zip with the clockwork recovery update.zip. I uploaded it here: http://dl.dropbox.com/u/115587/update.zip To do this I would use
Code:
adb push [local path to update.zip] /sdcard/update.zip
In my case since I'm using a mac (I put it in my downloads folder) I did
Code:
adb push ~/Downloads/update.zip /sdcard/update.zip
Then try to go into recovery mode and reinstall packages, hopefully clockwork will come up and you can restore a good version of your phone
Hope it helps

Laundry? Do you have insurance on it?
Sent from my 42 node TI 89 cluster

i dont know a whole lot about adb or even know if this is possible, but is there a way to reformat the internal sd card in adb like there is in the stock settings menu? if you reformat that should get rid of all traces of anything including lagfixes correct?

I am unable to use the touch command because it can't mount the Internal SD. it gives me
Code:
touch not found
even when i touch files that i now were there.
I wonder if i could flash the voodoo kernal back on to it if it would take care of it. is there a .tar of it that can be flashed with odin 3?
Is there a way to see what partitions are on the internal sd, and like di11igaf said, is there a way to reformat with adb?
Also i don't think warranty covers putting it through the laundry and w/ insurance it costs like $125 to replace

Wow this one is a bit of a headscratcher.
Have you tried manually flashing in a voodoo compliant kernel just to see if it will boot? It's not mounting the internalSD, which is bizarre, but I do know that stock kernels can't read EXT4 data- now I don't know why your internalSD might get switched over, and I have very little expectation that this will work, but at this point what's the harm?

I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)

I have flashed a voodoo kernel but it just tries to create the ext4 partition, fails and reboots. The problem is that there is now no /dev/block/mmcblk0p1 or /dev/block/mmcblk0p2. There is still a /dev/block/mmcblk0 but since we both tried to flash stock with Odin we no longer have root to attempt recreating the partitions. We also can't flash anything from recovery since there is no /sdcard.
We need a rooted ROM that is flashable with Odin. The e3 recovery also has an option to reformat the internal sdcard but I've only found it with i9000 ROMS where the captivate power button doesn't work to select it.

Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is able to mount your SD again, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.

Zilch25 said:
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is seeing that, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Click to expand...
Click to collapse
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.

Devin5277 said:
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Click to expand...
Click to collapse
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?

Another thing that might be worth trying... though doubtful. Do an Odin 1 click, yank the battery as soon as it completes before it gets a chance to boot again. Restart Odin and get your phone back into download mode, and flash in the Voodoo kernel, see what errors it spits out on first boot (if any)

Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
Zilch25 said:
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Click to expand...
Click to collapse
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.

Devin5277 said:
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Click to expand...
Click to collapse
Sorry I didn't mean to come off harsh My theory here is that SOMEHOW voodoo is writing EXT4 data to the internalSD outside of the NAND area and in some cases it's corrupting it in such a way that the internalSD cannot be read by the stock kernel (since it has no EXT4 support) so in theory if you can get the internalSD mounted again it can be reformatted to allow a stock kernel to return to use... if this is the case, or at least close enough to what's happening it would fully explain why the froyo kernel with repartition couldn't touch the internalSD (It couldnt mount or read it due to the limitations for file systems in a stock kernel)

Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.

kakalaky said:
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
Click to expand...
Click to collapse
Is this after using a Voodoo kernel? And are you attempting to perform the ffdisk and parted commands while using a voodoo kernel, or stock? I'm just trying to gather as much information as possible on this problem, so forgive all the questions

I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?

Trump211 said:
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Click to expand...
Click to collapse
Nah, make sure you have the phone plugged in when you turn it on and go into recovery. For some reason plugging it in when it's already in recovery doesn't work. At least it doesn't for me...

Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.

Trump211 said:
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Click to expand...
Click to collapse
Not sure =/ I had it running last night without too much issue, but I did have to juggle it around a bit before it would find the device. You might want to try doing an adb kill-server before you try to connect in case the system still thinks its running

[Q] Samsung I9000 Boot Loop, after Odin reflash etc.

I have a samsung galaxy s, gt-i9000. It was on the t-mobile network. It stopped working one day and is now stuck on a boot loop. (It does go into download mode)
Can anyone help me? ps. I do not know the original firmware names etc.

Hooolagon said:
I have a samsung galaxy s, gt-i9000. It was on the t-mobile network. It stopped working one day and is now stuck on a boot loop. (It does go into download mode)
Can anyone help me? ps. I do not know the original firmware names etc.
Click to expand...
Click to collapse
If your phone goes in to download mode you can flash, using Odin, a full stock firmware.
Have you ever update it since you've bought it?

umberto1978 said:
If your phone goes in to download mode you can flash, using Odin, a full stock firmware.
Have you ever update it since you've bought it?
Click to expand...
Click to collapse
I have a problem saying Cant Mount sdcard

I have the exact same problem as ysr84.. When i click "reboot system now" it just goes back into the boot loop.
Also.. My phone does go into download mode.. I have tried to flash using Odin3 but get the image as ysr84.. My phone then repeats the boot loop sequence..
PS. I do not know which firmware the phone started with, I have been flashing with JVR.
Since I bought the phone I have not tried to update it, I think there was no available update.. =/ not 100% sure..
Although when flashing with JVR I get the "Can't mount etc"

Android system recovery <3e>
Enter: OK Key, Select : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
_____________________________________
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
Successfully copied meida files.
--Wiping data...
Formatting /data
E:format_volume: rfs format failed on dev/block
/mmcblkop2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'KOR'
Successfully applied multi-CSC.
^This is the message I get after a fresh install using Odin3 with repartition selected. I had used the firmware package JVR.

ysr84 said:
I have a problem saying Cant Mount sdcard
Click to expand...
Click to collapse
Which firmware you tried to flash...and how? If you want more help about flashing follow http://www.hdtechvideo.com

anukilimanoor said:
Which firmware you tried to flash...and how? If you want more help about flashing follow http://www.hdtechvideo.com
Click to expand...
Click to collapse
Hello, I have tried to flash my phone with 'any' firmware as I do not know which firmware my phone was on before.

It maybe a trouble with partition.
You can try to re-virgin your phone by flashing an old eclair (JM8/JM9) firmware always using odin with pit 512, re-partition flagged.
Be careful if using a copy with bootloader.
After that (if phone boot regurarly) you can get any gingerbread firmware, obviusly if you used in the previous step bootloader for eclair firmware, than you'll get a copy of gingerbread with it's bootloader.
But i'm not sure this helps you.
Hope you solve this, guy.

umberto1978 said:
Be careful if using a copy with bootloader.
After that (if phone boot regurarly) you can get any gingerbread firmware, obviusly if you used in the previous step bootloader for eclair firmware, than you'll get a copy of gingerbread with it's bootloader.
But i'm not sure this helps you.
Hope you solve this, guy.
Click to expand...
Click to collapse
What do you mean by bootloader?

Hooolagon said:
What do you mean by bootloader?
Click to expand...
Click to collapse
If you, using 7ZIP, extract the archive PDA.TAR.MD5, from a package firmware with 3 files+pit512, you'll find boot.bin and sbl.bin.
boot.bin --> primary bootloader
sbl.bin --> secondary bootloader
I hope you don't mean what does a bootloader with your question.....

You'll have to try flashing different ODIN or Heimdall Stock builds. Unfortunately, it may or may not fix your problem. Make sure you have a USB Download Jig just in case because you'll probably get times where it looks like it won't turn on and its the only way to get it back up and running. If all else fails and your warranty is still intact, use it. These are the early signs of internal SD Card failure. If warranty is not an option, you should be able to use the external as your primary partition and lose the internal completely. Its what I'm doing currently on my i9000M with the infamous broken internal SD Card. My internal SD Card is gone completely but everything is running under my External SD Card perfectly.

Okay, so it's included within the three files + pit. That's okay, I thought there was more then four files after the extraction.. I am downloading JM8... Will tell you how I get on.

This time it said...
Android system recovery <2e>
Samsung recovery utils
for BML
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
_____________________________________
E:copy_dbdata_media:format SDCARD:
Formatting SDCARD...
format_root_device: /dev/block/mmcblkop1format_r
fsdevice -> /dev/block/mmcblkop1
format_vfat_device -> argv[1] :-F
format_vfat_device -> argv[2] : 32
format_vfat_device -> argv[3] :-0
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcbl
kop1
update media, finished
#MANUAL MODE#
-- Appling Multi-CSC...
Installing Multi-CSC
mps_dat value: KOR
copy_multi_carrier from: KOR
multicsc : can not acces tp /system/csc/KOR/system/
copy_common_data
^That's what happend when I flashed with JM8, (I had only flashed with PDA and repartition unchecked, due to phone and csc missing from the download.)
I will now click reboot system now...

dawgpound6985 said:
You'll have to try flashing different ODIN or Heimdall Stock builds. Unfortunately, it may or may not fix your problem. Make sure you have a USB Download Jig just in case because you'll probably get times where it looks like it won't turn on and its the only way to get it back up and running. If all else fails and your warranty is still intact, use it. These are the early signs of internal SD Card failure. If warranty is not an option, you should be able to use the external as your primary partition and lose the internal completely. Its what I'm doing currently on my i9000M with the infamous broken internal SD Card. My internal SD Card is gone completely but everything is running under my External SD Card perfectly.
Click to expand...
Click to collapse
Could you perhaps guide me on how to do so, I also think my internal SD CARD is also "buggered"..
Thanks in advance..

Woah WOAH WOAH HAHAHA!... Its alive... slightly! It turns on with the galaxy S logo and does some sort of sound thing.. =/ then turns off! But wahay!... Thanks Umberto1978..
I did this by first flashing JM8 PDA with repartition off...
Then flashing JM1 PDA PHONE AND CSC WITH 512 PIT...
on restart this happened..

Sure. This is what I did on my i9000M. Internal SD Card is useless so everything is now running off my External 8 GB microSD.
Go to this page and grab Heimdall and JVT build:
http://forum.xda-developers.com/showthread.php?t=1196179
Heimdall: http://www.glassechidna.com.au/products/heimdall/
JVT: http://www.multiupload.com/QMORULUWRQ
ODIN may work but I haven't tried it out myself and the packages above are made specifically for Heimdall. Set up Heimdall along with its specific drivers (included in Heimdall) to allow it to flash the phone.
- Make sure you have an external SD Card in your phone and make sure its formatted to FAT32.
- Flash the Heimdall JVT build with repartion checked using Heimdall
- Once it reboots, it'll try to format the SD Card but fail to do so and give you an error message. Ignore it and reboot the phone.
- It should now boot into Stock JVT firmware. If you go to your Storage under settings, you'll notice that Internal and External SD Card will be unavailable which is expected. You'll have 2 GB of internal storage for apps and whatever other things.
- You have two options here: 1) Continue using stock JVT; 2) Flash a custom ROM.
So let's say you want to flash a custom ROM like Cyanogenmod or MIUI. Fire up Heimdall again and go back into download mode. Flash the CF-Root for JVT kernel by Chainfire using Heimdall:
http://forum.xda-developers.com/showpost.php?p=15188469&postcount=9
This will allows you to flash CWM files. You can now install Cyanogemod or whatever custom ROMs you like.
Switching the primary partitions:
Cyanogenmod has a setting where you can switch the primary partitions in Cyanogenmod settings.
Cyanogenmod Settings --> Application --> UNCHECK use internal storage --> Reboot. Your External SD Card will now be the primary partition.
For myself, I am currently running Galnet's MIUI ICS. It doesn't have the Cyanogenmod settings above. I instead use the vold.fstab trick to switch the two partitions. If you navigate to "system/etc" folder, you'll see a file called vold.fstab. Open it with Notepad++ or some other note editor. You'll see the following (this is only for Galnet's MIUI, other ROMs will have something similar. Just switch the partitions like below):
Code:
# internal sdcard
dev_mount sdcard /mnt/sdcard/external_sd auto [U]/devices/platform/s3c-sdhci.0/mmc_host/mmc0[/U]
# external sdcard
dev_mount emmc /mnt/sdcard 1 [U]/devices/platform/s3c-sdhci.2/mmc_host/mmc2[/U]
Switch the two underlined around and push the vold.fstab back into system/etc/ and put the correct permissions. Your external card will now be your primary partition and your internal SD card (unavailable) is the external.
So why switch the partitions? You don't necessarily have to but if you want your phone storage to be neat, do it as it changes your sdcard mounts around, etc. You'll also get back USB mounting functions which you can't do with the internal storage being unavailable and the primary partition.
Hooolagon said:
Woah WOAH WOAH HAHAHA!... Its alive... slightly! It turns on with the galaxy S logo and does some sort of sound thing.. =/ then turns off! But wahay!... Thanks Umberto1978..
I did this by first flashing JM8 PDA with repartition off...
Then flashing JM1 PDA PHONE AND CSC WITH 512 PIT...
on restart this happened..
Click to expand...
Click to collapse
Yeah unfortunately, you have the dreaded Galaxy S bootloop. Internal SD Card is probably toast. You can test this by removing the External SD Card and trying to boot. It most likely won't get as far. What happened is that ODIN flashed Android to your external card and trying to boot off it.

I have tried to use heimdall, and once it had loaded and the phone rebooted I did get the error message, however after ignoring this, once I had rebooted the phone it goes back into the boot loop.?

Hooolagon said:
I have tried to use heimdall, and once it had loaded and the phone rebooted I did get the error message, however after ignoring this, once I had rebooted the phone it goes back into the boot loop.?
Click to expand...
Click to collapse
Have you tried reformatting your external SD Card? Just format it to FAT32 and then try again. Also, first boot may take a few minutes. You can verify that its booting fine by using logcat if you have ADB installed on your computer.

Flash jm9 mate, not jm8. Seems to resurrect better. With odin. Pit 512 with Repartition.
Sent from my GT-I9000 using xda premium

Hooolagon said:
Woah WOAH WOAH HAHAHA!... Its alive... slightly! It turns on with the galaxy S logo and does some sort of sound thing.. =/ then turns off! But wahay!... Thanks Umberto1978..
I did this by first flashing JM8 PDA with repartition off...
Then flashing JM1 PDA PHONE AND CSC WITH 512 PIT...
on restart this happened..
Click to expand...
Click to collapse
I am at work but will give this a shot... I also found a lot of people resolved problem by using JM8 with repartition and 512 pit
then with JPM & pit 803 with no repartition ticked...
Use Odin 1.3... 1.8 wont allow you to tick and untick with a repart file...
Will post results tonight... its been two days and i have tried everything...

[Q] N7000 can't see internal memory card

Hello guys!
Help needed on understanding what has happened to my SGN.
ROM: Ultimate N7000 XXLSC Jelly Bean 4.1.2 v5.1 (Thread)
Kernel: PhilZ CWM6 XXLSC XJB 3.75
Yesterday I've decided to encrypt my device (don't ask why :silly, and this try resulted in error (after few reboots), i was told i need to reset my phone. I've reseted it. Since than no internal memory available - message in notification bar: "Blank USB storage: USB storage is blank or has unsupported filesystem". Neither external SD card is accessible.
In recovery mode i can access my extSD card, but can't access, mount or format my EMMC - error: failed to mount exfat /dev /block/ mmcblk0p11 /emmc
I've reflashed the ROM for two times and nothing has changed...
Please, any ideas where should i refer to to understand what is happened (emmc brick?) and how to fix it?? Has anyone faced such a problem??
Many thanks in advance!

Just put ur mem cars in the jacket and copy all its data on ur computer. Format ur card via computer and reinsert it. It will 89% work.
Sent from my GT-N7000 using xda app-developers app

I read a thread last week where someone had the exact same problem.
You will have to search a bit to find it and maybe contact the guy as he
solved it by himself.
What I remember is that the flag for the partition to be seen as encrypted
is in the EFS partition. You need to edit a file in there to set it back to normal.
After that it will be available for a format.
Edit: it might be in this forum or in the GT-P6800 forum, as i got both devices and visit both forums
Found it : http://forum.xda-developers.com/showthread.php?t=2033320&page=2
Good luck.

If you backed up your EFS, as you should ,flash it & reboot.
from the man hiding in your attic..

So here are some new details:
I can't flash any (stock GB) rom via Odin - it stucks on factoryfs (common case with emmc problems)...
but i can flash the kernel (4pda_kernel.tar) thus i can enter CWM. In CWM i can flash a rom (Ultimate N7000), and phone works, despite i'm able to move apps to SD, internal usb storage still unavailable. My PC can "see" the phone's usb storage, but can't format it...
howard bamber said:
If you backed up your EFS, as you should ,flash it & reboot.
from the man hiding in your attic..
Click to expand...
Click to collapse
So, as far as I understand restoring EFS will make it possible to mount emmc in CWM and format it??
But i don't have backup of my EFS, where do i get it to restore? Is it possible to restore EFS from someone else's N7000 backup?

There is a risk that you may cause a problem with emei number if you flask the other phone's efs. I would try to remove and recreate partition 11 using parted. No sure it will work but it should cause no harm. The method is in the guide in my signature.
Sending from my phone

forest1971 said:
There is a risk that you may cause a problem with emei number if you flask the other phone's efs. I would try to remove and recreate partition 11 using parted. No sure it will work but it should cause no harm. The method is in the guide in my signature.
Sending from my phone
Click to expand...
Click to collapse
Dear forest1971 ! I did it! It helped! Thanks a lot! :good:
But some promlem still persists!
Manual re-partition (paragraph 8) resulted in following available internal memory figures:
option 1 ~ 7 Gb; option 2 ~ 4 Gb; option 3 ~ 3 Gb; option 4 ~ 2 Gb; option 5 - did not help. So, at the end, I chaged the numbers in option 1 to increase the "output" of internal memory. I put the numbers close to these (mantioned as a "stock" numbers in the beginig of the manual):
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS;
It worked! I've got back my 11 Gb available! And phone can "see" internal USB storage and format if (in CWM).
The problem itself: walking through these steeps (options), after each try i was still unable to flash a ROM (GB stock) via Odin, it always stucks on FactoryFS or even earlier.
But i was able to flash custom (JB) ROM via CWM from my external SD. It starts and works good!
The problem I've discovered - i can't unmount of format /SYSTEM in CWM on kernel other than "4pda-kernel" (I've tried couple of safe PhilZ kernels (v2.5, v2.7, v3.73, v3.81) - the device stucks!! It also stucks when hit "reboot" in CWM. I cant flash any ".zip" update/mod in CWM - it stucks on "unmounting system" step during flashing.
No such problem exists when return back to "4pda_kernel".
(I found the way out: I'm now on Glory ROM (JB) with PhilZ 3.73 kernel, so if I need to flash some ".zip" update/mod, I first flash "4pda_kernel" in CWM (being on PhilZ 3.73 kernel), than flash the ".zip" file, after that flash the PhilZ kernel back to start the ROM. It works for now.
Question: what could couse this problem?? Is there a way I could overcome this bug and get my "old Note" back (USB memory is back now, formated and works fine)??
And one more question: could i try to remove yellow tringle (reset my custom flash counter) via TriangleAway v2.37?? Or you guys would not recommend to touch it now??
Thanks to you all in advance!!!

Tammerlan said:
Dear forest1971 ! I did it! It helped! Thanks a lot! :good:
But some promlem still persists!
Manual re-partition (paragraph 8) resulted in following available internal memory figures:
option 1 ~ 7 Gb; option 2 ~ 4 Gb; option 3 ~ 3 Gb; option 4 ~ 2 Gb; option 5 - did not help. So, at the end, I chaged the numbers in option 1 to increase the "output" of internal memory. I put the numbers close to these (mantioned as a "stock" numbers in the beginig of the manual):
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS;
It worked! I've got back my 11 Gb available! And phone can "see" internal USB storage and format if (in CWM).
The problem it self: walking through these steeps (options), after each try i was still unable to flash a ROM (GB stock) via Odin, it always stucks on FactoryFS or even earlier.
But i was able to flash custom (JB) ROM via CWM from my external SD. It starts and works good!
The problem I've discovered - i can't unmount of format /SYSTEM in CWM on kernel other than "4pda-kernel" (I've tried couple of safe PhilZ kernels (v2.5, v2.7, v3.73, v3.81) - the device stucks!! It also stucks when hit "reboot" in CWM. I cant flash any ".zip" update/mod in CWM - it stucks on "unmounting system" step during flashing.
No such problem exists when return back to "4pda_kernel".
(I found the way out: I'm now on Glory ROM (JB) with PhilZ 3.73 kernel, so if I need to flash some ".zip" update/mod, I first flash "4pda_kernel" in CWM (being on PhilZ 3.73 kernel), than flash the ".zip" file, after that flash the PhilZ kernel back to start the ROM. It works for now.
Question: what could couse this problem?? Is there a way I could overcome this bug and get my "old Note" back (USB memory is back now, formated and works fine)??
And one more question: could i try to remove yellow tringle (reset my custom flash counter) via TriangleAway v2.37?? Or you guys would not recommend to touch it now??
Thanks to you all in advance!!!
Click to expand...
Click to collapse
There is no brick in your emmc so you can use all the memory which is normal.
You made a mistake to remove and recreate the factoryfs and datafs manually so they now will have a little bit different size (just some bytes) to the stock one.
If you want to get it to original condition, go to Dr ketan tool box in my signature then download stock pit file, then flash it. Then go into recovery and format data and usbstorage. Then you can flash any rom via odin or cwm.
Yes you can use triangle away.
cheers,

forest1971 said:
There is no brick in your emmc so you can use all the memory which is normal.
You made a mistake to remove and recreate the factoryfs and datafs manually so they now will have a little bit different size (just some bytes) to the stock one.
If you want to get it to original condition, go to Dr ketan tool box in my signature then download stock pit file, then flash it. Then go into recovery and format data and usbstorage. Then you can flash any rom via odin or cwm.
Yes you can use triangle away.
cheers,
Click to expand...
Click to collapse
Did it! Flashed the PIT-file you said via Odin (with checkmarks "Phone EFS clear" and "Re-partition", no manual re-partition), device could "see" the emmc and format it (both on "4pda_kernel" and on Philz one), but on PhilZ kernel situation did not change - phone still stucks (trying unmount or format /system )...
Any other thoughts what can be wrong?

Tammerlan said:
Did it! Flashed the PIT-file you said via Odin (with checkmarks "Phone EFS clear" and "Re-partition", no manual re-partition), device could "see" the emmc and format it (both on "4pda_kernel" and on Philz one), but on PhilZ kernel situation did not change - phone still stucks (trying unmount or format /system )...
Any other thoughts what can be wrong?
Click to expand...
Click to collapse
Hi, the description is not clear enough for me.
I understand that the aim is to be able to to flash rom using odin as normally should and to get back the usbstorage. Could have those now?
Another issue is: we should not check "clear phone EFS". I suspect it could cause a problem with the emei number if you clear the efs without restoring the original back up.
So for the above issues more info is needed.
If it continue to get stuck while using odin, then should use dd or hg42 scanner to check the memory.
cheers.

forest1971 said:
Hi, the description is not clear enough for me.
I understand that the aim is to be able to to flash rom using odin as normally should and to get back the usbstorage. Could have those now?
Another issue is: we should not check "clear phone EFS". I suspect it could cause a problem with the emei number if you clear the efs without restoring the original back up.
So for the above issues more info is needed.
If it continue to get stuck while using odin, then should use dd or hg42 scanner to check the memory.
cheers.
Click to expand...
Click to collapse
1) Yes, my emmc is back and works fine! Thank you!
2) Yes, now I'm able to flash ROMs via Odin! Thanks again!
The only problem still persists is that I can't flash any ".zip" file via CWM being on safe PhilZ kernels (haven't tried others, except for "4pda_kernel") if flashing process involves steps regardin "/system". Phone always stuck on that step - "unmounting /system" (also when hit "format /system", "power off" or "reboot" options in CWM).
All these works fine if "4pda_kernel" flashed insted of PhilZ one.
Before the problem with emmc (and manipultions done to resolve it) this "/system" problem did not exist, I was able to flash any ".zip" being on any kernel (including PhilZ ones).
I just want to understand what should i do to overcome this problem with "/system" being on PhilZ kernels?? What could cause this problem, that did not exist before reviving my emmc??
PS:
1) regarding "Clear phone EFS" checkmark - I've checked it after many vain tries to flash PIT files without it (phone just didn't see emmc after flashing files), so I've dicided to try and checked it - it worked!!! I didn't notice any problem with the phone after that... (maybe you know what should i check to be sure everything is ok with IMEI ? )
2) after flashing PIT-file with "clear phone EFS" checkmark I'm able to flash ROMs via Odin (before that it always stucks on FactoryFS...)
Once again, thank you mate for you involvement!

Tammerlan said:
1) Yes, my emmc is back and works fine! Thank you!
2) Yes, now I'm able to flash ROMs via Odin! Thanks again!
The only problem still persists is that I can't flash any ".zip" file via CWM being on safe PhilZ kernels (haven't tried others, except for "4pda_kernel") if flashing process involves steps regardin "/system". Phone always stuck on that step - "unmounting /system" (also when hit "format /system", "power off" or "reboot" options in CWM).
All these works fine if "4pda_kernel" flashed insted of PhilZ one.
Before the problem with emmc (and manipultions done to resolve it) this "/system" problem did not exist, I was able to flash any ".zip" being on any kernel (including PhilZ ones).
I just want to understand what should i do to overcome this problem with "/system" being on PhilZ kernels?? What could cause this problem, that did not exist before reviving my emmc??
PS:
1) regarding "Clear phone EFS" checkmark - I've checked it after many vain tries to flash PIT files without it (phone just didn't see emmc after flashing files), so I've dicided to try and checked it - it worked!!! I didn't notice any problem with the phone after that... (maybe you know what should i check to be sure everything is ok with IMEI ? )
2) after flashing PIT-file with "clear phone EFS" checkmark I'm able to flash ROMs via Odin (before that it always stucks on FactoryFS...)
Once again, thank you mate for you involvement!
Click to expand...
Click to collapse
It's good to know you got it working. And thanks for informing the solution of checking "clear phone efs".
About emei: should check emei number by dial: *#06#
then compare it with the emei number printed in phone carton box or find the number somewhere in the back of the phone after remove cover. Some people lost original emei and only have a generic emei which has many 000...It should not be a problem as long as the phone is working normally, althoug it will be useful to know if "clear phone efs" will cause problem with emei number.
About CWM in some kernel cannot format system. This problem was encountered by some people before. There is a trick by Entropy that seems to helps. connect phone in adb and do:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Then you should be able to format system and install custom rom using Philz kernel.

forest1971 said:
It's good to know you got it working. And thanks for informing the solution of checking "clear phone efs".
About emei: should check emei number by dial: *#06#
then compare it with the emei number printed in phone carton box or find the number somewhere in the back of the phone after remove cover. Some people lost original emei and only have a generic emei which has many 000...It should not be a problem as long as the phone is working normally, althoug it will be useful to know if "clear phone efs" will cause problem with emei number.
About CWM in some kernel cannot format system. This problem was encountered by some people before. There is a trick by Entropy that seems to helps. connect phone in adb and do:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Then you should be able to format system and install custom rom using Philz kernel.
Click to expand...
Click to collapse
Forest1971, you are the MAN! :highfive:
All works perfectly!!! :victory:
My origininal device is back!!!
No problems with IMEI (it is as it should be)!
My eMMC is back (stock partitions)!
I'm able to flash via Odin and CWM (including CWM that goes with PhilZ kernels) - no problem with formating /system in CWM.
THANKS A LOT!!! :good:

bro i have same problem, please give me clear step by step how to fix it, i am a noobs but i understand odin and recovery
Sent from my GT-I8160 using xda app-developers app

reda45 said:
bro i have same problem, please give me clear step by step how to fix it, i am a noobs but i understand odin and recovery
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
On the surface cases may look similar but there could be different problems. So we need more info about the problem before can help.
1. what was the rom and kernel you were using, rooted or not
2. what exactly did you do that lead to the problem
3. what the problem now
4. have you tried some solutions.
5. what do you plan to do to fix it.
.....

forest1971 said:
On the surface cases may look similar but there could be different problems. So we need more info about the problem before can help.
1. what was the rom and kernel you were using, rooted or not
2. what exactly did you do that lead to the problem
3. what the problem now
4. have you tried some solutions.
5. what do you plan to do to fix it.
.....
Click to expand...
Click to collapse
solved! I formatted my sdcard,haha
Sent from my GT-I8160 using xda app-developers app

Problem with G-Note N7000
I have the following problem and I would ask you forest1971 if you can help me.
It's Galaxy Note N7000. The phone was in use but did not see the sim card, there is "Unknown" Baseband and with empty IMEI.
After my attempts to input official ROM GB 2.3.5 phone is successfully fleshed via Odin ( use full flash with .pit file) but when the go on reboot and factory reset, launched a series of errors like this:
E: failed to mount / EFS (files not exists)
E: multi_csc: Can not mount / EFS
your storage not prepared yet, please use UI menu for format and reboot actions.
The phone is now able to when I turn it on, on LCD show "Samsung Galaxy Note N7000" and it freezes
What should I do to fix it

sloper said:
I have the following problem and I would ask you forest1971 if you can help me.
It's Galaxy Note N7000. The phone was in use but did not see the sim card, there is "Unknown" Baseband and with empty IMEI.
After my attempts to input official ROM GB 2.3.5 phone is successfully fleshed via Odin ( use full flash with .pit file) but when the go on reboot and factory reset, launched a series of errors like this:
E: failed to mount / EFS (files not exists)
E: multi_csc: Can not mount / EFS
your storage not prepared yet, please use UI menu for format and reboot actions.
The phone is now able to when I turn it on, on LCD show "Samsung Galaxy Note N7000" and it freezes
What should I do to fix it
Click to expand...
Click to collapse
Flask this efs folder using odin:
http://www.mediafire.com/?uafc086sfh2a3td
see how it goes.

forest1971 said:
Flask this efs folder using odin:
http://www.mediafire.com/?uafc086sfh2a3td
see how it goes.
Click to expand...
Click to collapse
After "succesful" flashing the "EFS_N7000XXKL8_CL840182_REV02_user_low_ship.tar.md5" with Odin. I can't start up my Note7000. It hangs at the bootscreen.
I can still get into downloadmode, can flash all the ROMS with PC Odin succesfull but after booting it gets stuck at the bootscreen.
I can also still go to recovery, wipe data and cache but after rebooting it always stuck on the bootscreen.
If I go to recovery I see the errormessage:
E: failed to mount data <invalid argument>
E: copy_log_files_to_data : : can't mount /data
It is that when flash ICS 4.0.4 and 4.1.2 Jelly Bean phone boot ok and load OS without any errors. Can I use it for Browsing internet, play games but not for call, because phone not recognize SIM card and the Baseband, IMEI and Serial is "Unknown"

sloper said:
After "succesful" flashing the "EFS_N7000XXKL8_CL840182_REV02_user_low_ship.tar.md5" with Odin. I can't start up my Note7000. It hangs at the bootscreen.
I can still get into downloadmode, can flash all the ROMS with PC Odin succesfull but after booting it gets stuck at the bootscreen.
I can also still go to recovery, wipe data and cache but after rebooting it always stuck on the bootscreen.
If I go to recovery I see the errormessage:
E: failed to mount data <invalid argument>
E: copy_log_files_to_data : : can't mount /data
It is that when flash ICS 4.0.4 and 4.1.2 Jelly Bean phone boot ok and load OS without any errors. Can I use it for Browsing internet, play games but not for call, because phone not recognize SIM card and the Baseband, IMEI and Serial is "Unknown"
Click to expand...
Click to collapse
Flash all files from this 5 part gb rom should help give a generic emei for phone to be recognized by network. You may need to flash them in two batches.
http://forum.xda-developers.com/showthread.php?p=20933428#post20933428

Odin failure or hardware failure?

My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
--Copying media files...
E:failed to mount /sdcard (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.
Media files copy failed.
--Wiping data...
Formatting /data...
E: format_volume: rfs format failed on dev/block/mmcblk0p2
Formatting /dbdata...
Formating /cache...
Data wipe failed.
-- Applying Multi-CSC...
Installing Multi-CSC
Applied the CSC-Code 'ATT'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best

frenzisor said:
My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best
Click to expand...
Click to collapse
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.

Booting of External SD card
BWolf56 said:
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.
Click to expand...
Click to collapse
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.

frenzisor said:
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.
Click to expand...
Click to collapse
***First of all, don't touch ROM Manager, it doesn't do well with the Captivate.
Custom recovery is flashed through kernels with Odin 1.18 (or 1.17). You simply grab the .tar file and put it in the PDA slot while you phone is in download mode. (On stock GB, you'll want Corn kernel)
Now my guess is that your external sd needs reformat. Backup w/e is on it (same with your internal if you can access it from your pc) and full format it to FAT32. If that alone doesn't fix it, wipe your internal as well.

[Q] i9000 internal Sdcard failure - help needed

Dear All,
My SGS1 i9000 fails to work properly, any apps FC after reboot. So this is what I did (btw several times):
- Odin flash JVU and rooted kernel including CWM
- saved efs with dd through adb in recovery menu
- wipe and factory reset data, cache, dalvik cache
- format sdcard system cache data datadata boot
After reboot phone keeps looping within the setup menu, FC even apps like skype which should be gone after factory reset. I cannot ADB into the booted phone.
When I mount the USB storage within recovery, I can access the internal SD card from my PC, and see all files, despite I have formated that space several times in recovery and from the PC. Normally I do not get error messages, but now and then a 'E:format_volume failed to unmount "/sdcard"'.
With all that, I'm assuming that the internal MMC might be defective, but obviously accessible, as I can i.e. read or copy files and open them, i.e. pictures. But I cannot delete them. So after spending days reading, I ran across folks who have been dealing with corrupted internal flash. They all suggested to prepare an external SD card with a FAT32 and ext4 partition, and have that plugged in during odin flash and restart, as the device would use that instead of the internal. After that I should fix vold.fstab to allow for camera and galerie to work.
Unfortunately my device seems not to pick the external for the internal during boot, as the internal flash can be accessed (but not written). So I'm looking for suggestions on how to move on like:
- how to finally kill the internal flash, so the external will be picked
- how to fix this cannot write to internal flash problem
- how to change the SW within recovery so it would not touch internal flash during boot but pick the external
- more creative ideas
can you please help
Brgds DerBusIsVoll

Hallo ,
flash pit 512 with odin. This should work.

yaaa pit mapping really important guys!
Sent from my GT-I9000 using xda premium

Sorry - forgot to mention:
- normally, I use the 512 pit whenever I flash the JVU
- I tried to follow other advices like flashing 512 pit with repartition unticked and Odin3 v1.0 ... (http://forum.xda-developers.com/showthread.php?p=30415128)
Maybe I missed something during repartition?

DerBusisVoll said:
Sorry - forgot to mention:
- normally, I use the 512 pit whenever I flash the JVU
- I tried to follow other advices like flashing 512 pit with repartition unticked and Odin3 v1.0 ... (http://forum.xda-developers.com/showthread.php?p=30415128)
Maybe I missed something during repartition?
Click to expand...
Click to collapse
Flash without the JVU. Only the pit. After that flash the JVU and after that the kernel. Dont forget to reboot after flashing the JVU

press thanks if someone helped u, its not much but its priceless
Sent from my GT-I9000 using xda premium

cixty said:
Flash without the JVU. Only the pit. After that flash the JVU and after that the kernel. Dont forget to reboot after flashing the JVU
Click to expand...
Click to collapse
Followed that advice using
- Odin3 v1.85
- s1_odin_20100512.pit
- CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar
- MODEM_I9000XXJVU_REV_00_CL1092175.tar
- GT-I9000-CSC-MULTI-OXAJVU.tar
- CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS
does not work unfortunately. Still FC all apps while stuck within setup after reboot.

DerBusisVoll said:
Followed that advice using
- Odin3 v1.85
- s1_odin_20100512.pit
- CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar
- MODEM_I9000XXJVU_REV_00_CL1092175.tar
- GT-I9000-CSC-MULTI-OXAJVU.tar
- CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS
does not work unfortunately. Still FC all apps while stuck within setup after reboot.
Click to expand...
Click to collapse
Flash without CF-Root. Do you check repartition while using Odin?

cixty said:
Flash without CF-Root. Do you check repartition while using Odin?
Click to expand...
Click to collapse
Ok, here is what I did:
- Flash only PIT, with repartition checked
- Flash only JVU, no PIT repartition unchecked, let it boot, FC's like before
- then flash only CF-Root, repartition unchecked, let it boot, FC's like before

DerBusisVoll said:
Ok, here is what I did:
- Flash only PIT, with repartition checked
- Flash only JVU, no PIT repartition unchecked, let it boot, FC's like before
- then flash only CF-Root, repartition unchecked, let it boot, FC's like before
Click to expand...
Click to collapse
Flash the pit without repartition. Maybe try another rom.

cixty said:
Flash the pit without repartition. Maybe try another rom.
Click to expand...
Click to collapse
Did flash pit without repartition. Did also follow:
Solution:- For i9000, Do the full wipes and factory reset First than Flash JVU ROM once with 512 PIT (TICKED) and Auto boot UNTICKED, do not boot, Flash again ROM with 803 PIT (UNTICKED)
Also had tried to flash Froyo stock, and then move to GB JVU, did not work either. I fear that internal flash is damaged.

I dont think so. My galaxy never got bricked and i flashed 9000+ times. There is always a solution for our galaxy. Try another rom. Maybe JW6 or JW9. Do you have an external sd card in your phone?

u can try to find any solution, but be sure to not getting da MBR error ok
Sent from my GT-I9000 using xda premium

cixty said:
I dont think so. My galaxy never got bricked and i flashed 9000+ times. There is always a solution for our galaxy. Try another rom. Maybe JW6 or JW9. Do you have an external sd card in your phone?
Click to expand...
Click to collapse
Thats encouraging. I had the external SD card out, also the sim card. When I tried to have it used instead of the internal, I had it in.
Now trying to follow http://forum.xda-developers.com/showthread.php?t=2247484 especially:
ONLY PREREQ: BE ABLE TO ENTER "DOWNLOAD" MODE! and have the drivers installed on your pc for your phone to be recognized.
* You can have an empty external SD card in the slot. No harm but better to remove the SIM card if any.
- Use ODIN (i ve used Odin3 v1.83) to flash SEMAPHORE (Semaphore_ICS_1.3.0s.tar ). No PIT file, No partitioning! Simply put the tar to PDA field and flash!
- Reboot into SEMAPHORE CWM and go to section with /data partition! YES! Select size 2GB and SWAP the max 256MB when asked! Exit and restart!
- Enter DOWNLOAD mode again and now flash (you need to find the stock EU region free firmware I9000XXJVU_I9000OXAJVU_OXA.zip which is actually split in 3 tar and not just one!)
- ODIN 1.83 will automatically enable Re-Partition & Auto Reboot & F. Reset Time when you flash 3 files! Leave ALL enabled! Everything else just leave as is and apply below!
You need PIT file 512 for the PIT field!
Then:
i . PDA: CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.m d5
i i . PHONE: MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5
i i i . CSC: GT-I9000-CSC-MULTI-OXAJVU.tar.md5
FLASH above and your phone should come start up normally to STOCK XXJVU firmware!
Click to expand...
Click to collapse
Hmmm, no luck so far. Funny though that partitioning the SD card within CWM should delete all files, but that does not happen. They are still there.

sometimes internalsd can be corrupt when repartition in process been disturbed while upgrading from cm7 to cm9. i ll try to look up for da problem. Even senior member need to use search box!
Sent from my GT-I000 using xda premium

DerBusisVoll said:
Thats encouraging. I had the external SD card out, also the sim card. When I tried to have it used instead of the internal, I had it in.
Now trying to follow http://forum.xda-developers.com/showthread.php?t=2247484 especially:
Hmmm, no luck so far. Funny though that partitioning the SD card within CWM should delete all files, but that does not happen. They are still there.
Click to expand...
Click to collapse
why dont you try another rom never as JVU

compacity said:
sometimes internalsd can be corrupt when repartition in process been disturbed while upgrading from cm7 to cm9. i ll try to look up for da problem. Even senior member need to use search box!
Click to expand...
Click to collapse
This might be the case. I understand the previous owner of the device had tried but failed to use CM, but I do not have details.

DerBusisVoll said:
This might be the case. I understand the previous owner of the device had tried but failed to use CM, but I do not have details.
Click to expand...
Click to collapse
but try mr cixty suggestion, maybe this time Lady Luck on ur side.....peeking...
Sent from my GT-I9000 using xda premium

compacity said:
but try mr cixty suggestion, maybe this time Lady Luck on ur side.....peeking...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Will do, Will try JWB with Semaphore274, and then SAUROM. Just downloading....
Update: Did install JWB & Semafore274, no change unfortunately

compacity said:
sometimes internalsd can be corrupt when repartition in process been disturbed while upgrading from cm7 to cm9. i ll try to look up for da problem. Even senior member need to use search box!
Click to expand...
Click to collapse
Getting closer to the problem. JWB & semaphore274, boot into CWM, start adb shell from pc
Now, execute
/sbin # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 8070MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.8kB 6057MB 6057MB primary fat32 lba
2 6057MB 8070MB 2013MB primary lba
(parted) mkfs 2 ext2
mkfs 2 ext2
mkfs 2 ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: 2
Yes/No? y
y
y
Partition number? 2
2
2
File system type? [ext2]?
writing per-group metadata........
Error: Invalid superblock. Are you sure this is an ext2 file system?
Click to expand...
Click to collapse
To me it seems that somehow /dev/block/mmcblk0 cannot be written to. Anybody an idea on how to fix this?