Do you have the sdcard mount bug?

---

Hi,
if you have the Huawei U8800 Pro (alias Ideos X5 Pro or U8800+) please try if your smartphone is affected by the sdcard mount bug.
Be sure that you have disabled the "Fast boot" on Settings->Applications->Fast boot (needs to be unchecked).
Then shutdown your U8800Pro and powen on.
Question: Is your sdcard (the external one microsd) correctly mounted? Can you see its content?
If you want your smartphone reads again your sdcard, you need to Reboot and magically Android mounts correctly your external microsd.

Please vote the poll upon this thread!

Regards,

kalo86

While it's unlikely I'll be able to help (the kernel patches I've written in the past have been basic), you should run "dmesg" right after it happens and paste the log here

Thanks qwerty12,
I'm going to post the result.
Be right back,
regards

This is the output of "dmesg": http://pastebin.com/GBWnecwJ

Please try more than one time because the bug is not "regular", it is a sort of random.
But in most cases, about 90%, every power on (after a full shutdown) the external sdcard is not correctly mounted and sometimes Android adverts me in the status bar that the file system is unknown.

Regards

I have 3 different microsd cards:

- Transcend 1GB (no class on the sdcard but > 4);
- Sandisk 4GB class 2;
- Sandisk 16GB class 4.

I have this bug with Sandisk sdcards and NOT with the Transcend one.
I am understanding that our Huawei U8800 Pro wants fast sdcards and my theory is confirmed by several tests.
The Transcend sdcard is the most fast among my sdcards (anyway I don't know the class because it's now written on the sdcard) and I proved its performance with a benchmark software. Its performance are better than Sandisk class 4, then its class is maybe 6.

Regards

Maybe a solution?

---

Hello dear Forum users,

I finally tried a new way for fixing the sdcard mounting problem.
I am used to format sdcard or any king of external drive with the built in format-tool of Windows 7 x64.
Anyway today I tried a new format tool (of course a new format tool for me ), developed by Panasonic, this is the download link:

https://www.sdcard.org/downloads/for...3/sdfmt3_1.zip

I formatted my sdcard with this software and magically the external sdcard is always correctly mounted!

Hoping to help other user,
best regards,

kalo86

Too good to be true i tried this method, has no effect at all..i have tried 2 different cards, class 4 and 6, i guess this bug lives in base huawei 2.3 code.. lets wait for new release from Huawei next week and hope this issue to be fixed.

Originally Posted by kalo86

Hello dear Forum users,

I finally tried a new way for fixing the sdcard mounting problem.
I am used to format sdcard or any king of external drive with the built in format-tool of Windows 7 x64.
Anyway today I tried a new format tool (of course a new format tool for me ), developed by Panasonic, this is the download link:

https://www.sdcard.org/downloads/for...3/sdfmt3_1.zip

I formatted my sdcard with this software and magically the external sdcard is always correctly mounted!

Hoping to help other user,
best regards,

kalo86

Oh, I'm very sorry to hear this
Anyway I changed something on the init.rc file (on the ramdisk of the kernel), so I don't know if the solution is a combination of the init.rc and sd-format tool. What I know is that my combination solved my drastic problem. Watching the status of the poll I have to say that there is for sure a problem on the huawei 2.3.5 base, yes, you're right.
If you want you can try my boot.img, based on genokolar kernel but I deleted lots of script, it's very "light" and like the stock one, except for the root rights.

Moved To Q&A

We now have a Q&A section. Please post all questions there

Download any Linux distribution and open a virtual terminal or terminal. Then do next things on bash:

1. Log in as root with su program by typing "su" and give root password (check distributor help page what is root in Live mode if using such).

2. Use dmesg and tail programs to get device information by typing
"dmesg | tail"

3. Physically connect your MicroSD card to reader

4. Re-use dmesg and tail programs to get device information of connected MicroSD by typing
"dmesg | tail"

5. Read what device was connected (Example /dev/sdb (! Not /dev/sdb1 or anything else number, just /dev/sdX)) from the output what dmesg program gave you when connected the MicroSD card

6. Overwrite whole card with full of zeroes with dd program and zero generator by typing
"dd if=/dev/zero of=/dev/sdX"
!!! IT WILL DESTROY ALL DATA ON CARD AND PARTITION TABLE !!!
and just wait that dd program write the whole card full of zeroes. of= means "Output File" and if= means "Input File". Be very careful that you have correct MicroSD card targeted (of=).


7. After you have cleared the whole card, eject it from card reader and re-insert it.

8. Re-use dmesg and tail programs to confirm the same device file is used

9. use fdisk program to create a new partitions and partition table to the card by typing
"fdisk /dev/sdX"
and press m for help. You need to create a new primary partition (n) and then write it to disk and quit (w). You can print already existing partitions with p as Print.

10. Eject the card and re-insert it

11. Use again dmesg and tail program to confirm new device files and partitions (Example, now there should be /dev/sdb, /dev/sdb1 if created one partition)

12. Generate a filesystem on created partitions and write them to partition table with filesystem tools (fat32 filesystem usually is wanted) by using mkfs.vfat program.
Type "mkfs.vfat /dev/sdX1"

13. Eject and re-insert the card

It should now be working again, with FAT32 partition on it.

P.S You can skip 7-13 parts if you want to do partitions on Windows, I always do it on Unix because Windows might get things still wrong but after the partition table is re-created on Unix, it works on Windows as well.

I have fixed dozens of "broken" cards and sticks by this way.
If you can not get your card listed with dmesg program then that card is physically broken, NAND chip is gone gaga or your card reader is broken as computer does not even recognize the card at all.