Database Develop

galaxy S cant mount or read internal and external sd cards

hi all.
last few weeks i have been on darky's 10.4.2 rom and all has been well untill this morning. the phone shut off on its own. when restarted it boots fine but i cant mount both sd cards. could anyone shed some light on this issue.

anyone??.
i need to hav this fixed asap.

common guys i realy need some help here. as i am traveling abroad tomorrow.
thanx.

Oh interesting. How you can't mount? Can't mount to PC? Or phone never see sdcard?
Download terminal emulator and type this command
Su
mount -o bind /mnt/emmc /sdcard/external_sd
Oh sorry. Both sdcards? It's more advenced. Can you go to recovery and look if phone detects sdcard there?
Sent from my GT-I9000 using Tapatalk 2 Beta-6

getting into to cwm recovery is a hit and miss. most of the time i get android recovery 3E.

bump.....

Factory reset or odin flash to stock GB firmware. Mount it once and you're done.

i went back to a stock rom and its still the same. any other ideas.

Did you try to connect your phone via usb once @ home screen

yes i did but it still didn't work. the usb thingy showed up on the phone but it still did nothing after.

Hi , you could try just rooting the stock rom to get cwm then mount your drives in recovery.

can i flash the cwm with odin. if so where can i get the files?.

playboy4u2nv said:
can i flash the cwm with odin. if so where can i get the files?.
Click to expand...
Click to collapse
You should be able to find the required Kernel from the following link, then flash in PDA section of odin
http://forum.xda-developers.com/showthread.php?t=1225879
These are stock kernels with voodoo and CWM
Use with caution as these kernels will convert the file system to EXT4 from RFS (stock) on first boot This may cause issues as Voodoo reads from the internal SD and writes there as well.
If you read the first 2 posts on the thread you should be able to make a decision that you are comfortable with.

Lexrsk said:
You should be able to find the required Kernel from the following link, then flash in PDA section of odin
http://forum.xda-developers.com/showthread.php?t=1225879
These are stock kernels with voodoo and CWM
Use with caution as these kernels will convert the file system to EXT4 from RFS (stock) on first boot This may cause issues as Voodoo reads from the internal SD and writes there as well.
If you read the first 2 posts on the thread you should be able to make a decision that you are comfortable with.
Click to expand...
Click to collapse
am still a bit confused as to witch one i should choose. i have I9000xxjvQ currently on the phone. can you pick the 2 best possible matches from the link that you posted. one with cwm would be best.
thanx

playboy4u2nv said:
am still a bit confused as to witch one i should choose. i have I9000xxjvQ currently on the phone. can you pick the 2 best possible matches from the link that you posted. one with cwm would be best.
thanx
Click to expand...
Click to collapse
when on the linked page do a search (find) by holding the "ctrl" and "f" keys this will open a search window then type in JVQ and you will locate the kernel
Gingerbread 2.3.4 Kernel v1.2 - I9000 XXJVQ
I trust that this will assist.

try to only flash csc and pit.
Sent from my SHV-E120L using XDA

romup said:
try to only flash csc and pit.
Sent from my SHV-E120L using XDA
Click to expand...
Click to collapse
Flashing just the PIT is a good way to erase all data on the phone as this will format all the partitions. Using a PIT without full firmware (3 file or 1 file) will result in a softbricked device.
And the CSC is only the carrier/consumer branding and will not resolve the issue of SDcards not being able to be read/mounted.

i tried flashing the file but i still cant mount the the sd cards.

playboy4u2nv said:
i tried flashing the file but i still cant mount the the sd cards.
Click to expand...
Click to collapse
can you now get into CWM recovery?
If so what messages do you get when attempting to mount SD cards?

i cant get into cwm. but in android recovery 3e i keep getting stuff like (E: db---file exsist or something)

Any fix for emmc bug yet?

Hello, 2 make a long story short, I wipe data in cwm5 while on "CF-LPY KERNEL" on ICS(OFFICIAL RELEASE) . And now I can't flash stock rom from both ics & gingerbread. Keep getting stuck @ FACTORYFS.IMG in odin. And I can't access cwm5 anymore and whenever I turn my phone back on it reads " FIRMWARE UPGRADE ENCOUNTERED AND ISSUE, PLEASE GO TO RECOVERY IN KIES & AND TRY AGAIN". And kies is not recognizing my device any insight on this particular issue will help and be greatly appreciated, and one more thing, will a jtag service be beneficial in my situation or I have no choice but to get a new motherboard for my device? And where exactly can I purchase one being that I'm in the united states with no warranty

You can try to flash with pc odin 1.85 a GB rom with .pit file

Whats the function of this pit file?
Sent from my GT-N7000 using XDA

Cyrion said:
You can try to flash with pc odin 1.85 a GB rom with .pit file
Click to expand...
Click to collapse
funky81 said:
Whats the function of this pit file?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I tried gb stock rom with pit file still getting stuck at "FACTORYFS.IMG" in Odin

Herk718 said:
I tried gb stock rom with pit file still getting stuck at "FACTORYFS.IMG" in Odin
Click to expand...
Click to collapse
I think you are on "superbrick" member .
Just like me a couple days ago. SSC is your solution ... I think.

chantik said:
I think you are on "superbrick" member .
Just like me a couple days ago. SSC is your solution ... I think.
Click to expand...
Click to collapse
Sorry 4 ya lost 2 don't worry bro these devs r good and I have faith in them. If there's a will there's a way they will make it happen trust.....

Herk718 said:
Sorry 4 ya lost 2 don't worry bro these devs r good and I have faith in them. If there's a will there's a way they will make it happen trust.....
Click to expand...
Click to collapse
Yeaach ... you're right.
My Gnote already repaired by SSC 2 days ago .... n off course free of charge .
Now I use GB rom to have save state ... I'm on waiting for devs made some magic to our device

chantik said:
Yeaach ... you're right.
My Gnote already repaired by SSC 2 days ago .... n off course free of charge .
Now I use GB rom to have save state ... I'm on waiting for devs made some magic to our device
Click to expand...
Click to collapse
Did you have a warranty? And where did u go?

If any of you with this brick can still flash kernels, try to flash the LPF CF-Root Kernel with CWM included. Then boot into CWM and within the "mounts and storage" menu, try to run the options "mount /system" and "mount /data". If i for myself try these two mounts, CWM tells me that it cannot find these two folders ("/system" and "/data").
btw: you can go back to original kernel by using the official method explained here
So in this case as some people here mentioned repartitioning within eMMC would manage getting around the bad areas/sectors within the chip by rearranging the partitions using ADB / ADB SHELL, i for myself cannot use ADB SHELL. What i definitely can do is connecting my Galaxy Note to the PC and also get a connection. But as soon as i try ADB SHELL, also ADB tells me something like "/system/bin/sh" not found.

Herk718, the problems you mention in your post are the exact same problems I had...and a lot more "members". I think I've tried every possible "solution" up until today, but without any luck. When it's up to me you can forget those posts advising you to flash this or flash that, it just won't work. Every PC Odin flash will stop at factoryfs.img (pit files won't work either)
As you actually said, we have to wait for a fix specific for this problem or bring you note to a SSC.

Herk718 said:
Did you have a warranty? And where did u go?
Click to expand...
Click to collapse
Of course I have warranty ... but before go to SSC , I flash ICSKernelTest.tar with pc odin to make my binary counter to zero. I'm from Indon****.

Herk718 said:
I tried gb stock rom with pit file still getting stuck at "FACTORYFS.IMG" in Odin
Click to expand...
Click to collapse
i guess there is some solution for this issue , which is use modified pit files
u will get ur note in working condition but few space lost, say 1-2 gb i guess.
search "
"PIT file method to revive your phone" in xda forum
i guess taz what u all lookin 4

greatjazz said:
i guess there is some solution for this issue , which is use modified pit files
u will get ur note in working condition but few space lost, say 1-2 gb i guess.
search "
"PIT file method to revive your phone" in xda forum
i guess taz what u all lookin 4
Click to expand...
Click to collapse
If you have warranty get it. Best way in this condition
Sent from my GT-N7000 using XDA Premium App

nitrate said:
So in this case as some people here mentioned repartitioning within eMMC would manage getting around the bad areas/sectors within the chip by rearranging the partitions using ADB / ADB SHELL, i for myself cannot use ADB SHELL. What i definitely can do is connecting my Galaxy Note to the PC and also get a connection. But as soon as i try ADB SHELL, also ADB tells me something like "/system/bin/sh" not found.
Click to expand...
Click to collapse
Your phone isnt rooted, so you getting this error, try flashing a pre-rooted kernel, i am not sure if it will root a bricked phone or not... no harm in trying : )
Edit: did you flash the kernel provided in forest's guide here post 12?
Flash that kernel, get into recovery mode, connect via adb, repartition, flash gb rom, flash angelom kernel to reset binary count, flash your rom's stock kernel again and claim warranty.
Herk try forest's guide, its got link to hg42's thread about the custom pit method.

simple way, get the firmware u want (preferably the oldset GB version) and download the pit files from this page
http://forum.xda-developers.com/showthread.php?t=1667886
then load the pit file with different regains ( 1024000 and 2560000kb worked with my note) and be sure u load 16 or 32gb accordingly.
same time load the firmware in pda , select re-partition option in odin and procceed.... start
good luck....
sometimes even u are sucessfull, the note will be stuck at a boot loop, wat i did was a factory reset at cwm recovery , do it at ur risk......(so its better to use GB firmware)

Herk718 said:
Hello, 2 make a long story short, I wipe data in cwm5 while on "CF-LPY KERNEL" on ICS(OFFICIAL RELEASE) . And now I can't flash stock rom from both ics & gingerbread. Keep getting stuck @ FACTORYFS.IMG in odin. And I can't access cwm5 anymore and whenever I turn my phone back on it reads " FIRMWARE UPGRADE ENCOUNTERED AND ISSUE, PLEASE GO TO RECOVERY IN KIES & AND TRY AGAIN". And kies is not recognizing my device any insight on this particular issue will help and be greatly appreciated, and one more thing, will a jtag service be beneficial in my situation or I have no choice but to get a new motherboard for my device? And where exactly can I purchase one being that I'm in the united states with no warranty
Click to expand...
Click to collapse
Do it only on good hardware laptop
Flash pit file in odin ( admin mode)
After successs flash gb in pda
I am success to recover with this method
Or try hg42 method

[Q][Solved] The system and data partitions are corrupt..should i goto service center?

So i found out about the ICS kernels issue a little bit too late :crying:
and now the /system and /data partitions can't be mounted nor formatted...so it's pretty much safe to say they are corrupt.
My question is: do service centers have the tools to completely restore the lost memory ? or should i proceed with searching for some workarounds via odin?
I am out of my warranty but willing to pay if the service center is caoable of completely fixing the issue WITHOUT replacing the motherboard?
Any help is much appreciated.
---
Now after seven days of this post..i have tried a zillion solutions and the one that actually worked is pit file and instructions by forest 1971 on the 15th comment
But sadly i lost 3 Gigabytes of my memory after this

What do you mean you are out of warranty
If your flash counter is increased,you can reset it
And i dont think it can be fixed without motherboard replacement

@OP
question to you: are you still able to work your way to download mode /recovery mode? you say "workarounds with ODIN" <--- just what exactly do you mean by that?

Should do some partition scan to make sure it is partition damage. Given your wipe using ics and the symptoms it is most likely the case of emmc brick. No way to fix it yet. Only two solutions, repartition workaround or change mobo.
Sent from my phone

I agree, go to the link (just saw it on Xda portal awhile back, congrats to hg42 for his tremendous effort for his contributions and forest as well) --- http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/

forest1971 said:
Should do some partition scan to make sure it is partition damage. Given your wipe using ics and the symptoms it is most likely the case of emmc brick. No way to fix it yet. Only two solutions, repartition workaround or change mobo.
Click to expand...
Click to collapse
Nope i don't think it's the emmc partition because it can be mounted so i don't think it's damaged. Are you sure the service center can't do more than changing the mobo?
letters_to_cleo said:
@OP
question to you: are you still able to work your way to download mode /recovery mode? you say "workarounds with ODIN" <--- just what exactly do you mean by that?
Click to expand...
Click to collapse
I could get to download mode and recovery mode then i tried to repartition using odin -a pit file-but it froze during the flashing process...so i lost access to recovery mode but not download.
workarounds with Odin means repartitioning my internal memory to have another /data & /system instead of the damaged ones
rajsekhar.300 said:
What do you mean you are out of warranty
If your flash counter is increased,you can reset it
And i dont think it can be fixed without motherboard replacement
Click to expand...
Click to collapse
Nope that's not what i mean -my flash counter is still 0- it's just that i bought my phone from another country and the warranty is only valid in that country bu not here...so i am without warranty right now...and it sucks ALOT

try to see first if you can flash one of the files from the link- http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/ to scan your partition. See to it if you have or don't have one of those damn brick blocks inside your phone.

Amr Shibiny said:
Nope i don't think it's the emmc partition because it can be mounted so i don't think it's damaged. Are you sure the service center can't do more than changing the mobo?
Click to expand...
Click to collapse
The term emmc brick just refer to brick cause by the buggy kernel which cause damage to some partition such as system or data or usb storage (that is part of the emmc).
if you can get to recovery then try to use the scanner from hg42 to identify area of damage, as suggested by Cleo. Maybe flash a custom kernel could help to get into recovery again.
Also, it seemed you have used a custom pit file could you give more detail which one you have used?

So i took my phone to service center and they told me the only thing they can di is changing the Mother board.
I took my phone home for further debugging and tried that memory scanner by hg42 only to find that i need the recovery mode to perform that scan
My recovery mode was lost due to an incomplete bootloader flashing
i falshed many kernels and flashed the same bootloader again but nothing seems to work
Any suggestions for good bootloaders? remember my phone is an ICS GT-N7000

Amr Shibiny said:
So i took my phone to service center and they told me the only thing they can di is changing the Mother board.
I took my phone home for further debugging and tried that memory scanner by hg42 only to find that i need the recovery mode to perform that scan
My recovery mode was lost due to an incomplete bootloader flashing
i falshed many kernels and flashed the same bootloader again but nothing seems to work
Any suggestions for good bootloaders? remember my phone is an ICS GT-N7000
Click to expand...
Click to collapse
If you really think there is a problem with wrong bootloader, then can try to flash the correct one from Dr.Ketan's toolbox below. There are both gb and ics version. I think using gb bootloader is ok.
http://forum.xda-developers.com/showthread.php?t=1801341
Then download and flash a kernel in .tar format using PC odin.
For ICS: flash hydracore standard kernel from link below:
http://forum.xda-developers.com/showthread.php?t=1749863
For GB: flash 4-pda kernel from this link:
http://www.mediafire.com/?smwswkxwa3u3p4s
after flash kernel try to get into recovery using the three button.
see how it goes.

forest1971 said:
If you really think there is a problem with wrong bootloader, then can try to flash the correct one from Dr.Ketan's toolbox below. There are both gb and ics version. I think using gb bootloader is ok.
http://forum.xda-developers.com/showthread.php?t=1801341
Then download and flash a kernel in .tar format using PC odin.
For ICS: flash hydracore standard kernel from link below:
http://forum.xda-developers.com/showthread.php?t=1749863
For GB: flash 4-pda kernel from this link:
http://www.mediafire.com/?smwswkxwa3u3p4s
after flash kernel try to get into recovery using the three button.
see how it goes.
Click to expand...
Click to collapse
After further reading in similar posts i am starting to think the bootloader isn't the problem....but the problem is i can't think of any other reason. It's definitely not the rom since there is not even a system partition right now and it isn't the kernel because i tried many (speedmod, franco...) and got no response. Any ideas?
Any way, I'll give it a shot using these links..hope it works

forest1971 said:
If you really think there is a problem with wrong bootloader, then can try to flash the correct one from Dr.Ketan's toolbox below. There are both gb and ics version. I think using gb bootloader is ok.
http://forum.xda-developers.com/showthread.php?t=1801341
Then download and flash a kernel in .tar format using PC odin.
For ICS: flash hydracore standard kernel from link below:
http://forum.xda-developers.com/showthread.php?t=1749863
For GB: flash 4-pda kernel from this link:
http://www.mediafire.com/?smwswkxwa3u3p4s
after flash kernel try to get into recovery using the three button.
see how it goes.
Click to expand...
Click to collapse
Well, the problem wasn't the boot loader after all
Tried all that and didn't work. I still can't access recovery mode on my device.
I tried usb debugging but there seems to be something wrong with the "adb shell" command. Whenever i write it it shoes a black screen on cmd..when i try to write something it's written without '#' or '$' in the beginning and when i press Enter the line i wrote is rewrote again and that's it. What does this mean?
Right now i need any help available to get either recovery mode or adb to work
thanks in advance

It seems you have tried to connect adb while the phone is in download mode, so it will not work. Adb requires the phone in recovery mode, which is still the problem so far.
I would try to flash the original pit file from dr.ketan toolbox, together with one of the above kernel again. see how it goes.
Sent from my phone

forest1971 said:
It seems you have tried to connect adb while the phone is in download mode, so it will not work. Adb requires the phone in recovery mode, which is still the problem so far.
I would try to flash the original pit file from dr.ketan toolbox, together with one of the above kernel again. see how it goes.
Sent from my phone
Click to expand...
Click to collapse
Nope..no effect
I tried it once with <repartition> ticked and another without it being ticked
I think you should know too that when i type "adb devices" the result is : "<big number> recovery". I don't know if this means i have recovery or it's just nonsense.

Amr Shibiny said:
Nope..no effect
I tried it once with <repartition> ticked and another without it being ticked
I think you should know too that when i type "adb devices" the result is : "<big number> recovery". I don't know if this means i have recovery or it's just nonsense.
Click to expand...
Click to collapse
in that case try to type in CMD:
Code:
adb reboot recovery
see if it has any effect (to reboot phone in recovery).
---------- Post added at 10:56 AM ---------- Previous post was at 10:45 AM ----------
If it does nothing, then I would now try to flash the custom pit from hg42 in the file attached (unzip it first to get .pit file), together with a suitable stock rom from dr.ketan thread (http://forum.xda-developers.com/showthread.php?t=1424997) and repartition box checked.
This PIT will leave the former system and data partition unused. after flash, try to get into recovery and wipe and try to boot normally. see how it goes.
Note: to make sure to avoid unsafe ICS kernel, should always use gb rom for reviving the phone and only upgrade to ics when it is working.

forest1971 said:
in that case try to type in CMD:
Code:
adb reboot recovery
see if it has any effect (to reboot phone in recovery).
---------- Post added at 10:56 AM ---------- Previous post was at 10:45 AM ----------
If it does nothing, then I would now try to flash the custom pit from hg42 in the file attached (unzip it first to get .pit file), together with a suitable stock rom from dr.ketan thread (http://forum.xda-developers.com/showthread.php?t=1424997) and repartition box checked.
This PIT will leave the former system and data partition unused. after flash, try to get into recovery and wipe and try to boot normally. see how it goes.
Note: to make sure to avoid unsafe ICS kernel, should always use gb rom for reviving the phone and only upgrade to ics when it is working.
Click to expand...
Click to collapse
It Worked!!! It f***ing Worked !!
Now my phone is back to business...but it lost 3 Gigabytes of memory right now
Thanks a billion for your patience forest1971
So is there anything not allowed after this solution? like rerooting, flashing via odin, flashing via cwm or downgrading to Android 2.3?
and btw just to understand more...why did you specifically give me this pit file? this is from hg42's collection, right? there are a lot of files in this collection and one should be chosen based on the result of the memory scanners, right? How did you know that's the one for me?

Amr Shibiny said:
It Worked!!! It f***ing Worked !!
Now my phone is back to business...but it lost 3 Gigabytes of memory right now
Thanks a billion for your patience forest1971
So is there anything not allowed after this solution? like rerooting, flashing via odin, flashing via cwm or downgrading to Android 2.3?
and btw just to understand more...why did you specifically give me this pit file? this is from hg42's collection, right? there are a lot of files in this collection and one should be chosen based on the result of the memory scanners, right? How did you know that's the one for me?
Click to expand...
Click to collapse
Good to know you made it !
You can do all things as before. Hope it will be running well.
I helped cases before, so can pick a suitable pit file !
Sent from my phone

forest1971 said:
Good to know you made it !
You can do all things as before. Hope it will be running well.
I helped cases before, so can pick a suitable pit file !
Sent from my phone
Click to expand...
Click to collapse
I see
Do you know too the best way to downgrade?
Don't want to mess it up again

Amr Shibiny said:
I see
Do you know too the best way to downgrade?
Don't want to mess it up again
Click to expand...
Click to collapse
The best way is using PC odin to flash pre-rooted gb rom from dr.ketan:
http://d-h.st/HJM
Or you can flash other stock gb rom which is suitable for your country from Dr ketan' thread as well (post 2)
http://forum.xda-developers.com/showthread.php?t=1424997
Using gb rom with a custom kernel such as FM or Abyssnote seem to work well, smooth and no problem. Or you can use some custom gb rom such as rocket v22 or other gb custom rom from link below:
http://rootgalaxynote.com/category/galaxy-note-roms/page/4/
cheers.

forest1971 said:
The best way is using PC odin to flash pre-rooted gb rom from dr.ketan:
http://d-h.st/HJM
Click to expand...
Click to collapse
But this is a .img file...i searched for the way of flashing it and i found i should use fastboot. For some reason fastboot isn't working. Is there a way of flashing it via Odin?

[Q] EFS Mounting Problem

Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?

arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.

YES, I DID
eduds said:
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.
Click to expand...
Click to collapse
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:

arjunkdas said:
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:
Click to expand...
Click to collapse
No, I'm talking about original firmwares, not custom ROMs.

DDXL1 and DDLD4
eduds said:
No, I'm talking about original firmwares, not custom ROMs.
Click to expand...
Click to collapse
I flashed both of these baseband versions of GB..and DDULP8 baseband of JB..you want me to try flash more baseband versions?

did u solve it ?
arjunkdas
Click to expand...
Click to collapse

NO
amr diab said:
did u solve it ?
Click to expand...
Click to collapse
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?

arjunkdas said:
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?
Click to expand...
Click to collapse
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u

amr diab said:
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u
Click to expand...
Click to collapse
Ok man! I'm also on it!

arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.

Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.

arjunkdas said:
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.
Click to expand...
Click to collapse
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.

http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!

NO Backup EFS
amr diab said:
http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!
Click to expand...
Click to collapse
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!

Doubts
Patlcs said:
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.
Click to expand...
Click to collapse
My phone is the 16 GB version. I'm having some weird doubts. I beg your pardon if I'm asking noob questions but I need to know them.
Ok, so here's how I flashed JB 4.1.2
In the JB package I downloaded, ther was only .tar file and nothing else. The baseband version is DDULP8. So everytime I flashed JB, I did with .tar file alone and no pit file.
Now, whenever I flashed back to GB 2.3.6, I flashed by selecting three files in the DXLD1 download package. PDA file, CSC file and an 8GB pit file. I flashed with these files at the first place and the phone boots up, works well. But the internal storage is shown as 3.91 GB. To solve this, I downloaded a separate 16GB pit file and flashed the phone by just selecting the 16GB pit file. After I rebooted my phone, it shows 11.1 GB internal storage.
My doubt is, do I need to select the 16GB pit file and check repartition while flashing JB 4.1.2?
Or just check repartition and flash with .tar file alone?!

Didn't solved
Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
tried it..didnt solve the problem!

arjunkdas said:
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!
Click to expand...
Click to collapse
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.

amr diab said:
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Click to expand...
Click to collapse
Tried! Still getting steup wizard stopped message!

arjunkdas said:
tried it..didnt solve the problem!
Click to expand...
Click to collapse
try to flash .pit file alone

Patlcs said:
try to flash .pit file alone
Click to expand...
Click to collapse
tried that too!

[Q] bricked N7000. how to get working again

I tried upgrading my international N7000 to CM10.3 following the instructions in
http://wiki.cyanogenmod.org/w/Install_CM_for_n7000
but now the phone won't even boot into the recovery, all it shows is
Samsung
GALAXY Note
GT-N7000
/ \
/ | \
/--*-\
When i tried flashin from my Mac iusing Heimdall,
the download finished on the mac, but on the N7000
it still showed the blue line etc. I waited a lng time and tried
rebooting, but got the above.
Re-flashing in Heimdall had no effect.
I then tried flashing
hardcore-speedmod-ics-recovery-n7000.tar
using Odin 3.185 from my VMwars Fusion XP install,
and that seemed to finish ok, but no luck either.
I looked for the latest CWM 6.0.4.3 recovery, but I cannot find any
odin-flashable format for it, and of course I cannot use the sdcard
as I cannot even boot into any recovery as is.
Can anyone suggest next steps?

sejtam said:
I tried upgrading my international N7000 to CM10.3 following the instructions in
http://wiki.cyanogenmod.org/w/Install_CM_for_n7000
but now the phone won't even boot into the recovery, all it shows is
Samsung
GALAXY Note
GT-N7000
/ \
/ | \
/--*-\
When i tried flashin from my Mac iusing Heimdall,
the download finished on the mac, but on the N7000
it still showed the blue line etc. I waited a lng time and tried
rebooting, but got the above.
Re-flashing in Heimdall had no effect.
I then tried flashing
hardcore-speedmod-ics-recovery-n7000.tar
using Odin 3.185 from my VMwars Fusion XP install,
and that seemed to finish ok, but no luck either.
I looked for the latest CWM 6.0.4.3 recovery, but I cannot find any
odin-flashable format for it, and of course I cannot use the sdcard
as I cannot even boot into any recovery as is.
Can anyone suggest next steps?
Click to expand...
Click to collapse
1st things 1st. Why would u use heimdall or odin? And what is your current ROM before trying to flash CM 10.3, was it stock? You should have looked for CWM recovery or Philz safe kernels as base when doing ROM flashing ESPECIALLY custom roms. From what you said, then can you still boot into download mode? I have no knowledge of heimdall so just download Stock Firmware, flash it with odin and see if you can boot your N7000 first.
The worst case scenarios is you are experiencing emmc bug-brick. go to the thread and read carefully to deduce your type of 'brick' and find solutions there. Good Luck.

I was on a stock 4.0.4 (but rooted). I originally tried flashing the cwm from the sd card, but after starting to load it it also just hung,
so I looked for an alternative..
I found a post on stockroms (http://forum.xda-developers.com/showthread.php?t=1424997) but the links all point to hotfile.com. which my browser says it cannot find. is hotfile dead? Is there an alternative?

sejtam said:
I was on a stock 4.0.4 (but rooted). I originally tried flashing the cwm from the sd card, but after starting to load it it also just hung,
so I looked for an alternative..
I found a post on stockroms (http://forum.xda-developers.com/showthread.php?t=1424997) but the links all point to hotfile.com. which my browser says it cannot find. is hotfile dead? Is there an alternative?
Click to expand...
Click to collapse
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app

same problem
Jackwu696 said:
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
i have the same problem , only mine loads into the recovery menu , ive tried finding a working odin to nstall it back to factory.
when i had this problem last night , i wasnt sure what i done but i managed to install a custom rom and that worked but now i seem to be getting status 7 error ,
my computer wont recognise my phone so i cant do anything that way . any ideas or links to solutions will be appreciated

i have the same problem

conanbrapp said:
i have the same problem , only mine loads into the recovery menu , ive tried finding a working odin to nstall it back to factory.
when i had this problem last night , i wasnt sure what i done but i managed to install a custom rom and that worked but now i seem to be getting status 7 error ,
my computer wont recognise my phone so i cant do anything that way . any ideas or links to solutions will be appreciated
Click to expand...
Click to collapse
I'm sorry so did u succeed or did you not succeed in installing the custom rom? If your custom rom boots fine then all u need is to search for solving status 7 error thread. My advice to all noobs is to always try n avoid installimg anything except stock rom in odin. Always read and re read before flashing anything that's beyond your knowledge. Basic knowledge of flashing cusroms is :
1. ALWAYS make sure you're on SAFE and COMPATIBLE KERNEL. Most rom threads ALWAYS Include threads/links to a specific recovery/kernel to use. Read n RE READ that.
2. Wipe everything IN RECOVERY mode before flashing a rom.
Sent from my GT-N7000 using XDA Free mobile app

fixed miine
Jackwu696 said:
Go to sammymobile.com if I'm not wrong. Download the stock firmware there. Rooted but do u have cwm installed? Rooted doesn't mean you have cwm installed.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
Jackwu696 said:
I'm sorry so did u succeed or did you not succeed in installing the custom rom? If your custom rom boots fine then all u need is to search for solving status 7 error thread. My advice to all noobs is to always try n avoid installimg anything except stock rom in odin. Always read and re read before flashing anything that's beyond your knowledge. Basic knowledge of flashing cusroms is :
1. ALWAYS make sure you're on SAFE and COMPATIBLE KERNEL. Most rom threads ALWAYS Include threads/links to a specific recovery/kernel to use. Read n RE READ that.
2. Wipe everything IN RECOVERY mode before flashing a rom.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
im not Sure what i did , i unbricked (soft) and successfully installed kitkat not sure exactly how but it worked.... still have root too ... had and error about needing to wipe data for suib i think but thats the only fallback i fell into

conanbrapp said:
im not Sure what i did , i unbricked (soft) and successfully installed kitkat not sure exactly how but it worked.... still have root too ... had and error about needing to wipe data for suib i think but thats the only fallback i fell into
Click to expand...
Click to collapse
If you're able to boot up properly n prompted to wipe, then do it. But do it in recovery not on device.

Ok, I downloaded one of the stock kernels for my internatinal N7000, but flashing that with Odin 3.185 hangs about 3/4 through (has now been
sitting there for >60 mins).
Looks like I am screwed?
The file I found is KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5
I f I wanted to try flashing this with Heimdall, I'd need to know partition numbers I think
Where can I get those?
Or should I get another file?

sejtam said:
Ok, I downloaded one of the stock kernels for my internatinal N7000, but flashing that with Odin 3.185 hangs about 3/4 through (has now been
sitting there for >60 mins).
Looks like I am screwed?
The file I found is KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5
I f I wanted to try flashing this with Heimdall, I'd need to know partition numbers I think
Where can I get those?
Or should I get another file?
Click to expand...
Click to collapse
Before that, do u have KIES installed? KIES is NOT compatible with odin and will cause potential trouble. So is some firewall and antivirus apps. You need to disable all of them before using odin. Please search the thread http://www.sammobile.com/firmwares/ for stock rom site.
Sent from my GT-N7000 using XDA Free mobile app

Ok. I downloaded two stock roms from sammobile:
[email protected] 1 mathias staff 808649674 May 9 10:53 N7000XXLT5_N7000MBCLT1_MBC.zip
[email protected] 1 mathias staff 750466356 May 9 10:50 N7000XXLRL_N7000OXELR5_MBC.zip
but both fail with some (unreadable, apparently character set issue) error under ODIN.
I found this:
http://droidangel.blogspot.sg/2012/01/samsung-galaxy-note-gt-n7000-all.html
which shows how to do a full flash , including PIT file, but the links again go to hotfile which seems to be down.
http://hotfile.com/dl/140099962/b9e0d63/Q1-20110914_16GB.pit.rar.html
Where can I get a) separate
CODE_N7000xxxxx_CLxxxxxxx_REVxx_user_low_ship.tar.md5
MODEM_N7000xxxxxx_REV_00_CLxxxxxx.tar.md5
GT-N7000-CSC-MULTI-xxxxxx.tar.md5
and the PIT file?

sejtam said:
Ok. I downloaded two stock roms from sammobile:
[email protected] 1 mathias staff 808649674 May 9 10:53 N7000XXLT5_N7000MBCLT1_MBC.zip
[email protected] 1 mathias staff 750466356 May 9 10:50 N7000XXLRL_N7000OXELR5_MBC.zip
but both fail with some (unreadable, apparently character set issue) error under ODIN.
I found this:
http://droidangel.blogspot.sg/2012/01/samsung-galaxy-note-gt-n7000-all.html
which shows how to do a full flash , including PIT file, but the links again go to hotfile which seems to be down.
http://hotfile.com/dl/140099962/b9e0d63/Q1-20110914_16GB.pit.rar.html
Where can I get a) separate
CODE_N7000xxxxx_CLxxxxxxx_REVxx_user_low_ship.tar.md5
MODEM_N7000xxxxxx_REV_00_CLxxxxxx.tar.md5
GT-N7000-CSC-MULTI-xxxxxx.tar.md5
and the PIT file?
Click to expand...
Click to collapse
Of course you fail... When using ODIN, U should have downloaded the .tar. if you downloaded a zip. then unzip it first to get the tar file, then you flash it with odin. All requests are included in the stock.tar And PLEASE DO NOT Play with PIT files if you don't know what you are doing.
So now what you need to do is. :
1. DISABLE KIES (Uninstall it better), Your firewall, antivirus.
2. Install CORRECT Samsung USB driver. (Search keyword "download samsung N7000 usb drivers")
3. Unzip your zip file and extract the tar.file.
4. Run ODIN as Administrator (Right click/run as)
5. Go to download mode. connect your device to Pc/laptop.
6. Wait until Odin detects your device, click AP/PDA and choose the tar file you extracted.
7. DO NOT tick partition.
8. Let it run

Of course I unzipped the zip to get a SINGLE .tar.md5, but flashing that fails on factoryfs about 3/4 through. consistently.

sejtam said:
Of course I unzipped the zip to get a SINGLE .tar.md5, but flashing that fails on factoryfs about 3/4 through. consistently.
Click to expand...
Click to collapse
Try updating your odin. Use the newest vers. And try and read this https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNGd2e3iG5hkDeo0KyAjGuCSfQSLUw . If All fails then it's a confirmed SUPER-BRICK and there's nothing except samsung service centre can help you now... Sorry for not being able to help more..

Thanks. That led me to
http://forum.xda-developers.com/showthread.php?t=1656635
where I found the PIT file, but for ROMs pointed to http://forum.xda-developers.com/showthread.php?t=1530501
which again points to hotfile and fileserve.com , which (besides being under maintenance) says
FileServe can only be used to download and retrieve files that you have uploaded personally.
which makes it useless for finding ROMs...

sejtam said:
Thanks. That led me to
http://forum.xda-developers.com/showthread.php?t=1656635
where I found the PIT file, but for ROMs pointed to http://forum.xda-developers.com/showthread.php?t=1530501
which again points to hotfile and fileserve.com , which (besides being under maintenance) says
FileServe can only be used to download and retrieve files that you have uploaded personally.
which makes it useless for finding ROMs...
Click to expand...
Click to collapse
His link to ROMS were basically the same ones you can download at sammobile.