Database Develop

[Q] Reformatting the internal SD

Hey guys, I pulled off a derpwad and messed up my internal SD's partition.
I can enter the recovery mode and download mode, but when I go into recovery, it says
Code:
Can't mount /dev/block/mmcblk0p1 (No such file or directory)
And I was lurking around and found some threads and such. Most saying that they sent their phones back. That's not really an option for me since I've been fighting with Samsung for a bit trying to get them to take it back, but they said I've voided the warranty by unlocking the phone yadda yadda. I can give you the specifics if you want.
I've tried flashing with Odin 1.3, it helped a bit because initially, I couldn't get into recovery. I've tried a few different ROMs, so I won't post them. I couldn't find a stock Android 2.1 ROM, can someone give me a hand?
I think the main problem is reformatting the internal SD to have the appropriate partitions and file systems. I don't know how to do that. I can connect the USB to my computer and make use of adb. I'm pretty tech savvy, but not yet well versed in a linux enviornment.
tl;dr
Internal SD seems corrupted. How do I reformat it correctly?

Hello,
Did you try to flash all the 3 parts of the phone software with odin, with repartition enabled and a valid PIT file?
Download
- PIT 803 file
http://www.multiupload.com/6JX2LEUCTY
- I9000XWJS3 package from samfirmware.com (european for my case), PIT803 version
http://www.hotfile.com/dl/100247999/301207f/I9000_XEN_I9000XWJS3.rar.html
(The pwd is samfirmware.com)
In Odin, tick repartition, for PIT select the PIT 803 file (s1_odin_20100803.pit)
For PDA, choose I9000XWJS3-REV03-ALL-low-CL830616.tar.md5
For CSC, choose GT-I9000-CSC-XENJS3.tar.md5
For PHONE, choose MODEM_I9000XXJPY.tar.md5
Click to expand...
Click to collapse
If all is OK your phone will reboot in recue after the flash and you will be able to format the internal sd from the rescue menu.

zbal said:
Hello,
Did you try to flash all the 3 parts of the phone software with odin, with repartition enabled and a valid PIT file?
If all is OK your phone will reboot in recue after the flash and you will be able to format the internal sd from the rescue menu.
Click to expand...
Click to collapse
I tried that just now and I'm getting a new error.
Code:
Can't mount /dev/block/st10 (Invalid argument)

Their is a post on here regarding fixing sd cards if you search that may help .
jje

CooKieLord said:
Hey guys, I pulled off a derpwad and messed up my internal SD's partition.
I can enter the recovery mode and download mode, but when I go into recovery, it says
Code:
Can't mount /dev/block/mmcblk0p1 (No such file or directory)
Internal SD seems corrupted. How do I reformat it correctly?
Click to expand...
Click to collapse
This is not corruption. It is simply a failure. There is no way to fix this other than to have the motherboard of the phone replaced.
Sorry to be the bearer or bad news, but hundreds have spent hours on it and not a single person was able to recover from the problem.

I have same problem than you, I fix it with I9000XXJPU version.

[Q] Muppet in need of Help

Hi,
I've been a right royal idiot and have spent 2 days trying to get my SGS back into working order.
Flashed Bionix v1.7 Rom (didnt realise it was Vibrant), worked great with the exception that the headset socket logic to be back to front. No audio from external speaker, if you plug in headset you could then external speaker started to work.
I therefore flashed back my origonal ROM with ODIN but on reboot the update failed with can't mount /dev/block/mmcblk0p2 on /data (Invalid argument). After then reading the notes (Yep noob mistake) I realised I should have removed the voodoo lagfix the Bionix ROM had before flashing a new rom.
Having done some investigation it looks like mmcblk0p2 is an j4fs filesystem but nothing I seem to do seems able to change that. Tried to mkfs and ext2 filesystem on it but it seems to be working then aborts saying it wasnt cleanly unmounted and to e2fsck the partition, which I try and it errors with unable to set superblocks on /dev/block/mmcblk0p2.
Any and all help greatly appreciated

Find a full rom that have dbdata.rfs, cache.rfs in it. Flash via Odin with repartition ticked.
Sent from my GT-I9000 using XDA App

JM8 will restore the things your missing

I have tried that, Odin runs through with no issues, but on device reboot it errors with the same. I can boot into clockwork recovery and adb shell. Its really weird, I've done a complete dd dev/zero over that partion. I've mounted it in windows and formatted via that and yet when I reboot and look at the partition via windows, all the data is there. There were a couple of other partions that were j4fs (/datadata) if i wipe that partion using fat.format, when i remount it it mounts as rfs instead of j4fs (great), but when I do the same with /data (mmcblk0p2) it says success on format but when I mount, it still mounts as j4fs...any other ideas?

azzledazzle said:
JM8 will restore the things your missing
Click to expand...
Click to collapse
Will try JM8 and let you know
Tried JM8 Odin complete succesfully, on reboot complains about CSC (multicsc : can not access to /system/csc/KOR/system
copy_common_data E:Can't mount /dev/block/stl11 (invalid argument))
cant do anything with stl11 in adb, complains no such device (although /dev/block/stl11 file exists)

I've managed to recover my SGS with a flash of JPU which is a low level package including repartition with 512.PIT. Here's a download link to JPU if it helps. It's a 3 part flash in Odin: http://www.multiupload.com/L79EDKJIG3
Good luck!

bdl1969 said:
I've managed to recover my SGS with a flash of JPU which is a low level package including repartition with 512.PIT. Here's a download link to JPU if it helps. It's a 3 part flash in Odin:
Good luck!
Click to expand...
Click to collapse
Just tried this and error is back to origonal ie cant mount /dev/block/mmcblk0p2.

You didn't accidentally store those files on your Sim or SD card right?
(I know, beginners question but just to be sure )
So you can't use your phone at all atm? Just stuck at recovery screen?

I had this same problem last night in the end used odin 1.7. With older firmware and pit (512) files doing a full repartition and reflash with csc. And modem files this was a jp4 set i believe.
This would not then upgrade in kies so i flashed a jpy firmware over the top just the firmware file this time. Not sure but i think i could have skipped this stage and restored from the clockmod backup. Can anyone confirm?
Then i rooted the phone again then flashed a kernel with clockwork mod support and was able to go to recovery mode and restore with the back up i made before i started messing about, though i suspect a titanium backup or similar would have worked just as well.
Hope this helps you at one point last night all I had was an icon with the phone and a computer thought I had really bricked it this time but given what I've done over the last couple of weeks i am not sure that's even possible.
Sent from my GT-I9000 using XDA App

curioct said:
I had this same problem last night in the end used odin 1.7. With older firmware and pit (512) files doing a full repartition and reflash with csc. And modem files this was a jp4 set i believe.
This would not then upgrade in kies so i flashed a jpy firmware over the top just the firmware file this time. Not sure but i think i could have skipped this stage and restored from the clockmod backup. Can anyone confirm?
Then i rooted the phone again then flashed a kernel with clockwork mod support and was able to go to recovery mode and restore with the back up i made before i started messing about, though i suspect a titanium backup or similar would have worked just as well.
Hope this helps you at one point last night all I had was an icon with the phone and a computer thought I had really bricked it this time but given what I've done over the last couple of weeks i am not sure that's even possible.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just tried with Odin 1.7, the JP4 romset still the same error on mmcblk0p2.
Just for avoidance of doubt in case I'm not doing this correctly,
In Odin I have Re-Partition, Auto_reboot, and F.Reset Time checked, Dump, Phone EFS and Phone Bootuploader Update are not checked. I'm using s1_odin_20100512.pit, and have tried Various European Roms including all the ones mentioned so far.
Fundamentally is the problem not that the filesystem type of the internal SD partition is j4fs? It seems the kernels dont know how to mount this type of filesystem, and for some reason I seem unable to change this. I cant even delete/format the data in these partitions.
cronoz, I believe mmcblk0 is the internal SD memory, which has 2 partitions. The first is a 2Gb Fat partition and the second is a 5Gb ext4(j4fs) partition.

Try using hardcore's kernel. In recovery mode try to disable lagfix.
Good luck
Sent from my GT-I9000 using XDA App

lownoise said:
Try using hardcore's kernel. In recovery mode try to disable lagfix.
Good luck
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
thanks, can you point me in the right direction maybe a link just to ensure I download the correct file.

It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App

lownoise said:
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yep, dont have any problem getting into Download mode

nivenj said:
Yep, dont have any problem getting into Download mode
Click to expand...
Click to collapse
then it's save to try

Yes the file system is the issue but repartitioning should reset that at lest it did for me last night. But only once i found a complete set of files. A *512.pit mine came with odin the main firmware in the pda box the modem file in the phone box and the csc file in the csc box once i had that mine refreshed just fine. If you have the right combination of those then I'm not sure what else you can do tbh
Sent from my GT-I9000 using XDA App

lownoise said:
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well this thas put me a lot further forward thats for sure. So i Flashed speedmod-kernel-k13a-500hz.tar. This now bootsl the SGS. It complains bitterly, force closing just about everything, but it does boot. Just about all apps force close, but I can set debugging mode and get in via adb (although the roms not rooted (JP4) :-S).
I can boot into recovery and choose the speedmod Lagfix option. It correctly identifies that /data is ext4. I disable lagfix and the new config is set to convert data to rfs on next reboot. I reboot and it goes through the conversion, backup of /data /datadb and /cache, it then generates md5 checksum and the aborts saying there is not enough space on internal SD. Not sure how to fix this part. When I enable debug mode I can see 2 partitions in windows a 1.8Gb and 5.3Gb, Both are empty apart from my update.zip in the 5.3Gb partition.
EDIT: Also tried the Yes, with factory reset without backup option, this seems to work but on reboot /data is still ext4 :-S
Any other ideas how to proceed now?
Any Full Roms with the speedmod kernel you could recommend?

nivenj said:
Well this thas put me a lot further forward thats for sure. So i Flashed speedmod-kernel-k13a-500hz.tar. This now bootsl the SGS. It complains bitterly, force closing just about everything, but it does boot. Just about all apps force close, but I can set debugging mode and get in via adb (although the roms not rooted (JP4) :-S).
I can boot into recovery and choose the speedmod Lagfix option. It correctly identifies that /data is ext4. I disable lagfix and the new config is set to convert data to rfs on next reboot. I reboot and it goes through the conversion, backup of /data /datadb and /cache, it then generates md5 checksum and the aborts saying there is not enough space on internal SD. Not sure how to fix this part. When I enable debug mode I can see 2 partitions in windows a 1.8Gb and 5.3Gb, Both are empty apart from my update.zip in the 5.3Gb partition.
EDIT: Also tried the Yes, with factory reset without backup option, this seems to work but on reboot /data is still ext4 :-S
Any other ideas how to proceed now?
Any Full Roms with the speedmod kernel you could recommend?
Click to expand...
Click to collapse
you can try darky's resurrection rom which is a complete rom with pit file 502
http://forum.xda-developers.com/showthread.php?t=940671
If that fails you can also try to flash jpy or js3 with the 802 pitfile
hmm i think the 2 partitions are the main problem....... It's kind off strange that you only can see the update.zip. How did you create the 2 partition???

Ive been trying darkys res rom, the only problem I think though is that it does say that lagfix has to be removed (ie not ext4 partitions) before installing, and that I suppose is the underlying problem of why I cant get it to work.
I just realised it wasnt 2 partitions, its the Internal and external SD cards, the 1.8Gb seemed to be corrupt, I managed to format it via the SGS menu and it shows the correct 8Gb now.s
EDIT: Hmmm just noticed something, its seems that although it appears I can delete and add files to my internal SD card via windows, it doesnt actually do anything on the card. This very strange :-S

[Q] heimdall: how can I flash movinand and emmc files?

Hey guys here is my story:
I flashed my captivate i896 with cyanogenmod cm7 then tried to flash back to stock with a 2.3.4 rom and checked repartition by mistake...after that the mmcblk partition that recognizes all the media in my cellphone was gone, so it doesn`t reads any sd (internal storage, movinand or external sds), it shows unavailable space with internal 16gb, external sds and 0.0k with internal storage.
I have tried to flash with many roms. The only one that could actually boot the phone was a recovery image of i897 speedmode with CWM, but still can recover the deleted partitions. I went into CWM recovery to try to mount or format them, but it doesn't let me.
In conclusion, I though that maybe flashing movinand and emmc files using heimdall could repair my cellphone, I been looking everywhere for information about flashing this files, but couldn't find the files or usufull information about it. I hope someone here can help me.
link to recovery image:
http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide

All you need to do is flash a stock ROM, from Odin or Heimdall, and a pit file. If you want to use Odin to repartition, it's as easy as loading a pit file in the pit slot, then check repartition. If you want to use Heimdall, you will need to be on Linux instead of windows. If you can use the Odin one click jf6 by designgears(not all phones can use it), it will repartition for you.

I already tried that with no luck, because after flashing back to stock the cellphone can't read the sd so it shows me the following message:
E:Failed to mount...

depending on the build number of your phone, which hopefully its an early build, this should work for you. http://forum.xda-developers.com/showthread.php?t=731989

Did it with no luck.

Hi guys, I keep looking everywhere but haven't g found a way to format the internal storage, no even a low level format

Low level format
michaelsucno said:
Hi guys, I keep looking everywhere but haven't g found a way to format the internal storage, no even a low level format
Click to expand...
Click to collapse
Any resolution to this.. I have the same issue and have tried numerous re-flashes with BL and w/o.. with PIT repartition and several different roms.. all to no avail.

[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