Well, I got a new Class 10 SD card, Transcend, from an online shop.
First few days it gave me great speeds. ~15mbps. Now, I'm getting not more than 4mbps!
I guess this happened mostly after using Data2SD or Partitioning the SD card
Anyone has any clue?
Hi,
I'd suggest formatting your memory card, then re-partitioning/re-doing whatever you've done to it.
Sent from my very dumb HTC Wildfire S (Stock Euro 2.3.5)
Did that a couple of times already
Well then I really don't know, sorry ...
Sent from my very dumb HTC Wildfire S (Marvel - Stock Euro 2.3.5)
Try using an SD Card reader and check its speed on your PC so that you know whether it's the card or the phone.
Then try a fresh ROM without Data2SD and check the speed.
Do each of the tests more than once cause sometimes there can be anomalies.
Same problem here
Bout a Samsung class 10 ,16gb sdhc and transfered some files to test the speed on my computer
I got 21mb write and 24mb read speed just as it said on the box
made partitions with Minitool to creat ext4 at a 32 cluster size
next thing you know even in windows my speed went down to 1mb/ and 2mb/sec
Anyone know whats going on here ?
Partition Alignment
SharpKami said:
Bout a Samsung class 10 ,16gb sdhc and transfered some files to test the speed on my computer
I got 21mb write and 24mb read speed just as it said on the box
made partitions with Minitool to creat ext4 at a 32 cluster size
next thing you know even in windows my speed went down to 1mb/ and 2mb/sec
Anyone know whats going on here ?
Click to expand...
Click to collapse
There are several factors that could play into it here.
How are you accessing the microSDHC? USB cable to phone / plugged with card reader?
Can you test with a more reliable tool, like CrystalDiskMark?
Windows may be buffering the transfer and giving wrong numbers.
It could be that Minitool did not align the partition(s) properly, as it would have done for built-in SSDs.
Did you shrink the (first) FAT32 partition and create the ext4 at 'the end' of the available space?
On my WFS + SanDisk 16GB, Class 10, I created the partitions with CWM, and DATA2SD (Data2sdV2withA2sdremover_by_jikantaru) had to recreate the ext3 partition, because it was improperly aligned. This is from the data2whateverlog.txt:
Code:
=============================
Fri Nov 2 10:44:17 PDT 2012
=============================
+++ Your Partition(s) are NOT aligned and data2whatever modified them:
----------------------------------------------------------------------
+++ Your SD-Ext Partition started at sector: 29617188
=> your SD-ext partition was NOT 1024k aligned
and it should start at following sector: 29618176
+++ Your Swap Partition started at sector: 30617188
=> your Swap partition was NOT 1024k aligned
and it should start at following sector: 30617600
+++ OLD Partition table of your SD-Card:
----------------------------------------
__________________________fdisk_Partition_table_____________________________
Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 29617187 14808593+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 29617188 30617187 500000 83 Linux
/dev/block/mmcblk0p3 30617188 31116287 249550 82 Linux swap
____________________________________________________________________________
+++ The Partitiontable has been modified
----------------------------------------
__________________________fdisk_Partition_table_____________________________
Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 29617187 14808593+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 29618176 30617599 499712 83 Linux
/dev/block/mmcblk0p3 30617600 31116287 249344 83 Linux
____________________________________________________________________________
+++ The SD-ext partition got formated with EXT3 afterwards:
-----------------------------------------------------------
_________________________mke2fs+tune2fs_output______________________________
Filesystem label=userdata
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
124928 inodes, 499712 blocks
0 blocks (0%) reserved for the super user
First data block=1
Maximum filesystem blocks=524288
61 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.6 (30-May-2009)
Filesystem volume name: userdata
Last mounted on: <not available>
Filesystem UUID: 5e4066d3-bb6c-4ef9-8081-03c03cecfce7
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype sparse_super
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 124928
Block count: 499712
Reserved block count: 0
Free blocks: 475708
Free inodes: 124917
First block: 1
Block size: 1024
Fragment size: 1024
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2048
Inode blocks per group: 256
Filesystem created: Fri Nov 2 17:44:20 2012
Last mount time: n/a
Last write time: Fri Nov 2 17:44:44 2012
Mount count: 0
Maximum mount count: 31
Last checked: Fri Nov 2 17:44:20 2012
Check interval: 15552000 (6 months)
Next check after: Wed May 1 17:44:20 2013
Reserved blocks uid: 0 (user unknown)
Reserved blocks gid: 0 (group unknown)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 611421e5-1bfd-44b8-95d8-8af4c40c053b
Journal backup: inode blocks
____________________________________________________________________________
+++ Filesystem check found no errors - no log attached
-------------------------------------------------------
I checked the speed with RoboCopy over USB to the WFS, it was about 4MB/s.
CrystalDiskMark reports 4.5MB/s write speed over the same connection (with 5 runs of 100MB data).
Try using SD-Booster app
You're right litemaster ! my windows was showing the wrong figures while transferring files .
i tried the sd tester and booster ,speed results weren't all that bad , 10mb read /10mb write.
and in windows it shows 2mb but file transfers at a much higher rate some times 30mb/sec.
Appreciate your your help buddy and Eduardo
P.S... By the way , given the results , this samsung class 10 isnn't that bad. Bought it for £12.00 from amazon.
Related
I use a 1gb sd with a fat32 and a ext2 partition.
It doesn't want to install, tried also the eclair version. Same problem.
Please help me .
This is my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read and Compare FATs
Attempting to allocate 988 KB for FAT
Attempting to allocate 988 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (201623) not correct (201622)
Fix? yes
Next free cluster in FSInfo block (50390) not free
Fix? yes
9 files, 403244 free (201622 clusters)
sh: 1: unknown operand
Using partitioned system
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/mmcblk0p2 is mounted
ext2: clean, 11/120832 files, 15402/481950 begin_of_the_skype_highlighting**************15402/481950******end_of_the_skype_highlighting blocks
Creating a new Data store
256+0 records in
256+0 records out
mke2fs 1.38 (30-Jun-2005)
mke2fs: cannot determine if /sdcard/andboot/data.img is mounted
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0: clean, 11/65536 files, 8286/262144 blocks
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
Click to expand...
Click to collapse
Also adding a third partition as linuxswap makes this install not even see the ext2 partition, thats why I did not add a linuxswap, do I need to?
Try installing it without an ext2 partition, there really is no benefit from using an ext2 partition on a haret install, in fact it may be the cause of your problems, a swap partition may help however, around 64-96 MB is usually more than enough.
The error messages may indicate that the Fat32 partition is not the first partition on the SD card, it depends what you used to partition the SD, some utilities are no good for android SD partitioning, since they may create the partition wrongly, ( as far as android is concerned).
Does anyone know what Android is doing to check the external SD card before producing the error that the SD card is damaged? I get that error after every reboot the card card is then fully functional (camera can write to it, file browsers can access it). I have reformatted the card in the phone and in Windows 7. Here is the output from fsck from a linux box:
[email protected]:/media$ sudo fsck -v /dev/sdb1
fsck from util-linux 2.19.1
dosfsck 3.0.9 (31 Jan 2010)
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
32768 bytes per cluster
596 reserved sectors
First FAT starts at byte 305152 (sector 596)
2 FATs, 32 bit entries
1944576 bytes per FAT (= 3798 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
486032 data clusters (15926296576 bytes)
63 sectors/track, 255 heads
2048 hidden sectors
31114240 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/sdb1: 1 files, 2/486032 clusters
Time to reflash the ROM maybe? (Diet ICS) I'd just like to know what command is being run to trigger the error. It is a 16GB card formated as fat32
ok, while I was spinning my wheels someone else had posted in the Diet ICS thread that this is apparently a known issue with the toggles being used.
I had to make sure my card was formatted to FAT32 for it to recognize my card. try that.
MentalDragon said:
I had to make sure my card was formatted to FAT32 for it to recognize my card. try that.
Click to expand...
Click to collapse
In this case it was specific to the ROM and reflashing the theme fixed it. While I was trying to figure out what was going on and ended up posting this question, someone else was already posting the fix.
Hi everybody..
I have a strange and boring issue with my micro SD card that I use with my smartphone.. Today, while I was reading a PDF book the phone freezes it self: the only solution was to reboot it!
But.. WOW; 'till that moment the phone doesn't recognize my micro-SD any more!! It doesn't give warnings or messages.. nothing.. the only problem is that my SD card is inserted but the phone won't read it..
I mount the micro sd into my Slackware laptop and it still have partitions but they are all read-only! Every thing I try to do (copy files, move, delete etc) fails with a read-only warning!
So I try to format all from the scratch.. but it is not possible!! It doesn't let me format my SD for the same reason: read-only file system!!
WOW!! It's absurd!!
What can I do? is there a solution for that?
I tried to use fsck, badblocks, mkfs but nothing helped!
fdisk -l output
Code:
Disk /dev/sdb: 15.9 GB, 15918432256 bytes
255 heads, 63 sectors/track, 1935 cylinders, total 31090688 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00031a4f
Device Boot Start End Blocks Id System
/dev/sdb1 1 29027343 14513671+ c W95 FAT32 (LBA)
/dev/sdb2 29027344 31027343 1000000 83 Linux
/dev/sdb3 31027344 31090687 31672 82 Linux swap
I have a FAT partition for data, a ext2 one used with Link2sd and a swap one.
This is the result I got when trying to format the second partition..
Code:
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.14 (22-Dec-2010)
/dev/sdb2: Read-only file system while setting up superblock
The same to me. Wish a help!! Thanks
I've read a number of forum posts about how to unbrick a hardbricked galaxy S3 and followed them all and even tried countless times the same method as is suggested, yet I can't get my phone to boot at all. Anyone out there have any advice? I rooted my phone just fine and then flashed Android_Revolution_HD-SGS3_53.0.zip onto it through clockwork mod. Everything appeared to be installing fine and when it came time to reboot, clockwork mod notified me that something appeared wrong in my boot file and I may lose root priveledges. It then asked if I wanted clockwork mod to fix it and I unfortunately said yes. The screen immediately went pitch black and nothing I have tried gets it to show any signs of life.
I have a 64 GB micro SD that I've used with the command
Code:
sudo dd if=Desktop/debrick_sph_l710.img of=/dev/mmcblk0
I then check it with
Code:
sudo fdisk -l /dev/mmcblk0
and get
Code:
GPT PMBR size mismatch (30777343 != 122241023) will be corrected by w(rite).
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/mmcblk0: 58.3 GiB, 62587404288 bytes, 122241024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Device Start End Sectors Size Type
/dev/mmcblk0p1 8192 131071 122880 60M Microsoft basic data
/dev/mmcblk0p2 131072 131327 256 128K unknown
/dev/mmcblk0p3 131328 131839 512 256K unknown
/dev/mmcblk0p4 131840 132863 1024 512K unknown
/dev/mmcblk0p5 132864 136959 4096 2M unknown
/dev/mmcblk0p6 136960 137983 1024 512K unknown
/dev/mmcblk0p7 137984 158463 20480 10M unknown
/dev/mmcblk0p8 158464 159487 1024 512K unknown
/dev/mmcblk0p9 159488 160511 1024 512K unknown
/dev/mmcblk0p10 160512 180991 20480 10M Linux filesystem
/dev/mmcblk0p11 180992 208895 27904 13.6M Linux filesystem
/dev/mmcblk0p12 208896 215039 6144 3M unknown
/dev/mmcblk0p13 215040 221183 6144 3M unknown
/dev/mmcblk0p14 221184 3293183 3072000 1.5G Linux filesystem
/dev/mmcblk0p15 3293184 28958719 25665536 12.2G Linux filesystem
/dev/mmcblk0p16 28958720 28975103 16384 8M Linux filesystem
/dev/mmcblk0p17 28975104 30695423 1720320 840M Linux filesystem
/dev/mmcblk0p18 30695424 30715903 20480 10M unknown
/dev/mmcblk0p19 30715904 30736383 20480 10M unknown
/dev/mmcblk0p20 30736384 30748671 12288 6M Linux filesystem
/dev/mmcblk0p21 30748672 30754815 6144 3M unknown
/dev/mmcblk0p22 30754816 30754831 16 8K unknown
/dev/mmcblk0p23 30754832 30765071 10240 5M Linux filesystem
The phone acts no differently with the flashed sd card than it does without it. Is the only way to fix it with a JTAG?
U need 16gb sd card, debrick image for your phone. Then you can boot into download mode and flash in odin! Get a high quality 16gb card
hilla_killa said:
U need 16gb sd card, debrick image for your phone. Then you can boot into download mode and flash in odin! Get a high quality 16gb card
Click to expand...
Click to collapse
I'm using a 32 GB SanDisk micro sd, could it just be that all the debrick images I've used are just the wrong ones?
Its possible but i think if your phone is 16gb than you need 16gb sd
Hi all,
I recently restored my device from EDL mode using miflash. Its boots up fine to the official stock firmware rom that i recovered to (miui 9.6.4.0) using miflash but after re-installing TWRP i'm unable to install any custom roms.
The output from TWRP:
Code:
Installing MIUI update...
performing update
Installing MIUI update...package_extract_file took 00s.
package_extract_file took 00s.blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524
254427136 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 181701 blocks
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
Decompression failed with BLOCK_LENGTH_2
missing 1222632 bytes of new data
failed to execute command [new 2,326044,326556]
Perform Block Image Update took 04s.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
device name: /dev/block/bootdevice/by-name/system
Filesystem volume name: system
Last mounted on: <not availabel>
Filesystem UUID: da594c53-9beb-f85c-85c5-cedf76546f7a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem flags: unsigned_directory_hash
Filesystem features: has_journal ext_attr resize_inode filetype extents sparse_super large_file gdt_csum
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem os type: Linux
Inode count: 193920
Block count: 774155
Reserved block count: 0
Free blocks: 106382
Free inodes: 189202
First block: 0
Block size: 4096
Reserved GDT blocks: 191
Blocks per group: 32768
Inodes per group: 8080
Inode blocks per group: 505
Last mount time: n/a
Last write time: Wed Dec 31 19:00:00 1969
Mount count: 0
Maximum mount count: 10
Last checked: Wed Dec 31 19:00:00 1969
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
Updater process ended with ERROR: 7
I:Install took 5 second(s).
Error installing zip file '/sdcard/Download/globeROM_v10_whyred_9.2.28_cfg-fmygvtpxbrw.zip'
Updating partition details...
I:Data backup size is 842MB, free: 49040MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
Any ideas how to solve this one?
Resolve after updating MIUI to the latest version was able to flash custom roms again.