Error creating ext on my sdcard - Nexus One Q&A, Help & Troubleshooting

Hi, I´m trying to configure my new sdcard (sandisk 32gb cl4) but everytime I try to create the ext2 partition on my ubuntu i get this error
Code:
Error creating file system: helper exited with exit code 1: cannot mount /dev/sdb1 at /tmp/job-mkfs-WmyAZC: Invalid argument
Filesystem label=New Volume
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2048000 inodes, 8191996 blocks
409599 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
250 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624
Writing inode tables: 0/250 1/250 2/250 3/250 4/250 5/250 6/250 7/250 8/250 9/250 10/250 11/250 12/250 13/250 14/250 15/250 16/250 17/250 18/250 19/250 20/250 21/250 22/250 23/250 24/250 25/250 26/250 27/250 28/250 29/250 30/250 31/250 32/250 33/250 34/250 35/250 36/250 37/250 38/250 39/250 40/250 41/250 42/250 43/250 44/250 45/250 46/250 47/250 48/250 49/250 50/250 51/250 52/250 53/250 54/250 55/250 56/250 57/250 58/250 59/250 60/250 61/250 62/250 63/250 64/250 65/250 66/250 67/250 68/250 69/250 70/250 71/250 72/250 73/250 74/250 75/250 76/250 77/250 78/250 79/250 80/250 81/250 82/250 83/250 84/250 85/250 86/250 87/250 88/250 89/250 90/250 91/250 92/250 93/250 94/250 95/250 96/250 97/250 98/250 99/250100/250101/250102/250103/250104/250105/250106/250107/250108/250109/250110/250111/250112/250113/250114/250115/250116/250117/250118/250119/250120/250121/250122/250123/250124/250125/250126/250127/250128/250129/250130/250131/250132/250133/250134/250135/250136/250137/250138/250139/250140/250141/250142/250143/250144/250145/250146/250147/250148/250149/250150/250151/250152/250153/250154/250155/250156/250157/250158/250159/250160/250161/250162/250163/250164/250165/250166/250167/250168/250169/250170/250171/250172/250173/250174/250175/250176/250177/250178/250179/250180/250181/250182/250183/250184/250185/250186/250187/250188/250189/250190/250191/250192/250193/250194/250195/250196/250197/250198/250199/250200/250201/250202/250203/250204/250205/250206/250207/250208/250209/250210/250211/250212/250213/250214/250215/250216/250217/250218/250219/250220/250221/250222/250223/250224/250225/250226/250227/250228/250229/250230/250231/250232/250233/250234/250235/250236/250237/250238/250239/250240/250241/250242/250243/250244/250245/250246/250247/250248/250249/250done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
And if I try to create the partition with the amonra recovery it says the partition was created but it wasn´t
and update ext2 to ext3 or ext3 to ext4 tells me to use "adb fs ext3(or 4)"
I don´t know what to do to get it working, my 2gb and 8gb sd card work pretty well with both methods listed above.
thx

"cannot mount /dev/sdb1 at /tmp/job-mkfs-WmyAZC: Invalid argument"
Thats probably the problem but I'm not sure what's causing it. What command are you using? Can you mount the card manually?

I thought there were only class 2 32gb sd cards Where'd you buy it?

I have pictures of the error now:
I can´t create an ext partition in gparted nor in amonra recovery tool
My sd card is a sandisk 32gb cl4 and it doesn´t accept the ext2/3/4 partition but accepts fat32 or linux swap
here are the screenshosts I take:
And someone replied:
It seems to some issue with the ext2 being logical or primary. Paragon seems to work first time for allot of people but then just crashes like in your case.
Mixing these two file system may cause some issues. The only way todo do it is using linux. Check mobile phone forums out they have good guides- avoid the paragon ones.
Click to expand...
Click to collapse
But I didn´t understand
mcp2009 said:
I thought there were only class 2 32gb sd cards Where'd you buy it?
Click to expand...
Click to collapse
Mercadolivre, it´s an ebay but in Brazil. It´s imported from US, brand new product

Im thinking it might be a fake because sandisk only makes class 2 32gb sd cards. Try running hwtest tool to check

mcp2009 said:
Im thinking it might be a fake because sandisk only makes class 2 32gb sd cards. Try running hwtest tool to check
Click to expand...
Click to collapse
I didn´t find hwtest but I tried Crystal Disk Mark
What do you say?

It seems like it could be a class 4 but search around for hwtest tool or "test fake memory card" cuz it might be a class 4 but not 32gbs. Hwtest tool will determine the actual free space and tell you if its a 4gb disguised as a 32gb

Using h2testw

Code:
The media is likely to be defective.
104 MByte OK (212992 sectors)
31.1 GByte DATA LOST (65282048 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
31.1 GByte corrupted (65282048 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000058f2600
Expected: 0x00000000058f2600
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 5.76 MByte/s
Reading speed: 8.80 MByte/s
H2testw v1.4
Is it fake or broken?

paolobacci said:
Code:
The media is likely to be defective.
104 MByte OK (212992 sectors)
31.1 GByte DATA LOST (65282048 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
31.1 GByte corrupted (65282048 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000058f2600
Expected: 0x00000000058f2600
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 5.76 MByte/s
Reading speed: 8.80 MByte/s
H2testw v1.4
Is it fake or broken?
Click to expand...
Click to collapse
I'm thinking fake. It's basically saying that 31.1gbs was fake. Can you get a refund?

Soooo, where did you buy the card? Cheap on ebay?

Yes, I´ll do that

khaytsus said:
Soooo, where did you buy the card? Cheap on ebay?
Click to expand...
Click to collapse
MercadoLivre it´s a br ebay
The vendor will get me refund and I´ll buy another one.
Thank you guys

Related

[GUIDE] SD card partitioning for rooted phones

Behold... a long awaited partitioning guide
WARNING! This GUIDE is to actually learn something not just to copy/paste commands!
Requirements
rooted phone
busybox installed
parted (optional)
backup your SD card (optional)
calculator
Click to expand...
Click to collapse
Background
Before we begin partitioning, we need to elaborate some key points:
block storage units are divided into logical blocks known as sectors
sector has a size of 512 bytes
NAND flash chips are divided into blocks known as erase blocks
our SD cards consist of those NAND flash chips and controller
erase block on our SD cards has a size of 128 kB, that's 256 sectors
CHS (cylinder, head, sector) alignment has an insignificant importance here
1st sector is sector 0 (not 1) and is used as MBR (master boot record)
1st partition begins at cylinder boundary to maintain MS-DOS compatibility
raw access to block storage units is done via special block device files under /dev/block directory
our SD card is represented by block device file /dev/block/mmcblk0
Click to expand...
Click to collapse
Instructions
Here I will provide you with two methods of partitioning. For 1st method you will be using fdisk utility which is part of busybox and for 2nd a standalone utility called parted will be used. Both methods can be used in normal mode via adb shell or some terminal app. I will explain both methods using adb shell as it is more convenient and handy than typing commands via touch keyboard on your phone.
1st thing to do before you begin is to unmount your SD card via "Settings->SD & phone storage" and then you issue "adb shell" command ony your PC. 2nd thing you will do is erasing of your SD card (actually you will erase just first few erase blocks of your SD card) using dd utility:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0 bs=131072 count=16
...that will overwrite 1st 2 MB of your SD card with null characters. Next you may begin with partitioning.
fdisk
As I already stated, fdisk is a (interactive) utility that is part of busybox so I will assume it is available under /system/xbin directory. Now you can run fdisk with device file of your SD card as parameter/argument:
Code:
fdisk /dev/block/mmcblk0
...this will bring you some notes on your screen you should not worry about and a command prompt:
Code:
Command (m for help):
...which you can leave at any time by pressing CTRL+C. Next you will change unit display type to sectors:
Code:
Command (m for help): [B]u[/B]
Changing display/entry units to sectors
...and print your SD's current info (this is info of my SD card actually, yours may vary):
Code:
Command (m for help): [B]p[/B]
Disk /dev/block/mmcblk0: 8018 MB, 8018460672 bytes
4 heads, 16 sectors/track, 244704 cylinders, total 15661056 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
...and you write down the number of sectors. In my case it is 15661056 sectors of 512 bytes which is exactly 7647 MB if we divide them by 2048. For example you would take 7000 MB for fat32 1st partition and 647 MB for ext 2nd partition. and it is handy that way coz megabytes are divisible by our SD card's erase block size which is 128 kB as stated before. Calculation would give you start sector for 2nd partition and this would be 14336000 (7000*2048).
Now you need to create 2 primary partitions:
Code:
Command (m for help): [B]n[/B]
Command action
e extended
p primary partition (1-4)
[B]p[/B]
Partition number (1-4): [B]1[/B]
...now there's a catch. You will be offeread a start of 1st partition at 1st to 2nd cylinder boundary which is sector 16 in my case and you push it to SD card's erase block boundary (256):
Code:
First sector (16-15661055, default 16): [B]256[/B]
Last sector or +size or +sizeM or +sizeK (256-15661055, default 15661055): [B]14335999[/B]
...and continue to the next partition which should also be primary:
Code:
Command (m for help): [B]n[/B]
Command action
e extended
p primary partition (1-4)
[B]p[/B]
Partition number (1-4): [B]2[/B]
First sector (16-15661055, default 16): [B]14336000[/B]
Last sector or +size or +sizeM or +sizeK (14336000-15661055, default 15661055): [B]15661055[/B]
...now print what you have just done:
Code:
Command (m for help): [B]p[/B]
Disk /dev/block/mmcblk0: 8018 MB, 8018460672 bytes
4 heads, 16 sectors/track, 244704 cylinders, total 15661056 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 256 14335999 7167872 83 Linux
/dev/block/mmcblk0p2 14336000 15661055 662528 83 Linux
...it looks OK but you need to change 1st partition's hex id which needs to be fat32 (c):
Code:
Command (m for help): [B]t[/B]
Partition number (1-4): [B]1[/B]
Hex code (type L to list codes): [B]c[/B]
Changed system type of partition 1 to c (Win95 FAT32 (LBA))
...now you're am set, print again your configuration and write changes to SD card:
Code:
Command (m for help): [B]p[/B]
Disk /dev/block/mmcblk0: 8018 MB, 8018460672 bytes
4 heads, 16 sectors/track, 244704 cylinders, total 15661056 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 256 14335999 7167872 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 14336000 15661055 662528 83 Linux
Command (m for help): [B]w[/B]
The partition table has been altered!
There's a possibility you would need to shutdown and power on again your phone at this point. Do not reboot via adb or some 3rd party app!
Click to expand...
Click to collapse
parted
Parted is one of interactive partitioning utilities that can also use external formatting utilities. It can be found in some recovery images but can be copied to your internal phone storage and run from there in normal mode too. To run it you have to use your SD card's device file as a parameter/argument:
Code:
parted /dev/block/mmcblk0
...and you will be presented with an interactive shell:
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
I probably shouldn't mention that there's an interactive help available and that it is invoked by issuing "help" into shell's command prompt. Next thing to do is making a MS-DOS disklabel:
Code:
(parted) [B]mklabel msdos[/B]
...and switch to display sector as a unit:
Code:
(parted) [B]unit s[/B]
Now you can print some useful info:
Code:
(parted) [B]print all[/B]
Model: SD USD (sd/mmc)
Disk /dev/block/mmcblk0: 15661056s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
Mind and write down the size in sectors (15661056 in my case).If you divide number of sectors by 2048, you get how big in MB is actually your SD card (7647 in my case).You should mind that erase block of your SD card is 128 kB and all of your partitions should start at the beginnings of those erase blocks. It is safe to say that 1st partition should begin at sector 256 and 2nd at any MB boundary. Let say you want 512 MB big ext partition and the rest for fat32 one. Mind tho that 1st partition is to be fat32! So we say 7135 MB for fat32 1st partition and 512 MB for ext 2nd partition. Now you calculate the start sector of 2nd partition... number of MB for 1st partition multiplied by 2048 should give you the number (14612480). And you are set for partitioning:
Code:
(parted) [B]mkpart primary fat32 256 14612479[/B]
(parted) [B]mkpart primary ext2 14612480 15661055[/B]
...and print result:
Code:
(parted) [B]print all[/B]
Model: SD USD (sd/mmc)
Disk /dev/block/mmcblk0: 15661056s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 256s 14612479s 14612224s primary fat32 lba
2 14612480s 15661055s 1048576s primary ext2
...and quit:
Code:
(parted) [B]quit[/B]
Click to expand...
Click to collapse
At this point you have partitioned your SD card but not yet formatted it. Format fat32 partition with mkfs.vfat and ext partition with mkfs.ext2:
Code:
mkfs.vfat /dev/block/mmcblk0p1
...and:
Code:
mkfs.ext2 -m0 -b4096 /dev/block/mmcblk0p2
If there is a mke2fs utility on your phone system (standalone - not part of busybox), you may use it to format second partition as ext3:
Code:
mke2fs -j -m0 -b4096 /dev/block/mmcblk0p2
...or even as ext4 (if your mke2fs supports that):
Code:
mke2fs -j -m0 -b4096 -Oextents,uninit_bg,dir_index /dev/block/mmcblk0p2
Click to expand...
Click to collapse
Blayo,
thanks for the post. You always manage to take things to an entirely different level of understanding
Is this guide for the successful implementation of the latest data2ext scripts in roms ? in comparison to methods like the Rom Manager and partition through recovery ?
No, it is general guide to better understand partitioning etc.
BlaY0 said:
No, it is general guide to better understand partitioning etc.
Click to expand...
Click to collapse
I totally agree! After going through parted I think it's the best way to partition your SD, you have complete control!
I can't wait will my new SD card arrives, and give this a shot!
The Kingston 16GB class 10 sucks even when set-up to the best parameters and the reason for that is simple: Although class 10, it is like 4 times slower than my 8GD sandisk mobile ultra Class 4 when random writing and 3 times slower when reading...
So Thanks BlaY0 for this cool guide/lesson
I have problem with fdisk . when i press p i got this info and there a no sector:
PHP:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 16.0 GB, 16001269760
4 heads, 16 sectors/track, 488320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Did you change units display to sectors?
Thanks, with the "u" option comes later in your manual
A last newbie question: i have now 2 part. and formated the FAT, but i dont know, how to get the "mke2fs" on the phone to format the Linux part.?
Sorry Blay0 but Linux is another Word for me...
tasar said:
Thanks, with the "u" option comes later in your manual
Click to expand...
Click to collapse
Thanx, I have changed that.
A last newbie question: i have now 2 part. and formated the FAT, but i dont know, how to get the "mke2fs" on the phone to format the Linux part.?
Sorry Blay0 but Linux is another Word for me...
Click to expand...
Click to collapse
If you have busybox on your phone you also have mke2fs or mkfs.ext2 as these two are part of it. If you have CM based ROM there should already be standalone e2fsprogs in /system/bin directory and if you have a stock based one, you can find mke2fs_recvy + e2fsck_recvy in /system/bin directory. In B ROM you have all e2fsprogs available in /system/xbin directory.
Many thanks!!! Now i install your 0.5
Code:
# mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat: not found
help?
Try "busybox mkfs.vfat"...
BlaY0 said:
Try "busybox mkfs.vfat"...
Click to expand...
Click to collapse
Code:
# busybox mkfs.vfat /dev/block/mmcblk0p1
busybox mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat: applet not found
its ok, before you replied i tried doing it in recovery and i believe it worked, but i think i missed a digit in my partitioning and it was only 98mb for my fat drive instead of about 988 or something (1gb) so ill try it again and let you know
EDIT: ok yeah i had the digits wrong so now its formatted/partitioned correctly. now im gonna apply the data2ext thing and see what happens. i didnt actually do anything about my darktremor a2sd so ive probably got bits and pieces of all my apps missing but if **** starts to screw up ill just put a fresh copy of cm on since ive ruined all my apps basically already
EDIT: alright its working, thanks heaps!
DT has some commands to disable itself.
As for mkfs.vfat... it is part of busybox but not necesarily. There are several versions lying around the internets. Type just "busybox" and you'll see all the utils available in it.
BlaY0 said:
DT has some commands to disable itself.
As for mkfs.vfat... it is part of busybox but not necesarily. There are several versions lying around the internets. Type just "busybox" and you'll see all the utils available in it.
Click to expand...
Click to collapse
Code:
# busybox
busybox
BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Copyright (C) 1998-2009 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.
Usage: busybox [function] [arguments]...
or: function [arguments]...
BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.
Currently defined functions:
[, [[, arp, ash, awk, basename, bbconfig, brctl, bunzip2, bzcat, bzip2,
cal, cat, catv, chgrp, chmod, chown, chroot, cksum, clear, cmp, cp,
cpio, cut, date, dc, dd, depmod, devmem, df, diff, dirname, dmesg,
dnsd, dos2unix, du, echo, ed, egrep, env, expr, false, fdisk, fgrep,
find, fold, free, freeramdisk, fuser, getopt, grep, gunzip, gzip, head,
hexdump, id, ifconfig, insmod, install, ip, kill, killall, killall5,
length, less, ln, losetup, ls, lsmod, lspci, lsusb, lzop, lzopcat,
md5sum, mkdir, mke2fs, mkfifo, mkfs.ext2, mknod, mkswap, mktemp,
modprobe, more, mount, mountpoint, mv, nc, netstat, nice, nohup,
nslookup, ntpd, od, patch, pgrep, pidof, ping, pkill, printenv, printf,
ps, pwd, rdev, readlink, realpath, renice, reset, rm, rmdir, rmmod,
route, run-parts, sed, seq, setsid, sh, sha1sum, sha256sum, sha512sum,
sleep, sort, split, stat, strings, stty, swapoff, swapon, sync, sysctl,
tac, tail, tar, tee, telnet, test, tftp, time, top, touch, tr,
traceroute, true, tty, tune2fs, umount, uname, uniq, unix2dos, unlzop,
unzip, uptime, usleep, uudecode, uuencode, vi, watch, wc, wget, which,
whoami, xargs, yes, zcat
yeah so that mkfs.vfat isnt there and neither is parted
and then when i go to android recovery
Code:
# busybox
busybox
BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
Copyright (C) 1998-2008 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.
Usage: busybox [function] [arguments]...
or: function [arguments]...
BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as!
Currently defined functions:
[, [[, arping, ash, awk, basename, bbconfig, bunzip2, bzcat, bzip2,
cat, catv, chattr, chgrp, chmod, chown, chroot, chrt, chvt, cksum,
clear, cmp, cp, crond, crontab, cut, date, dc, dd, deallocvt, depmod,
devmem, df, dhcprelay, diff, dirname, dmesg, dnsd, dnsdomainname,
dos2unix, du, dumpkmap, dumpleases, echo, egrep, env, ether-wake, expr,
false, fbset, fbsplash, fdisk, fgrep, find, fold, free, freeramdisk,
fsck, fuser, getopt, grep, gunzip, gzip, head, hexdump, hostname,
hwclock, ifconfig, ifdown, ifup, insmod, install, ip, ipaddr, ipcalc,
iplink, iproute, iprule, iptunnel, kbd_mode, kill, killall, killall5,
last, length, less, ln, loadfont, loadkmap, losetup, ls, lsattr, lsmod,
makedevs, md5sum, mdev, mkdir, mkdosfs, mkfifo, mkfs.vfat, mknod,
mkswap, mktemp, modprobe, more, mount, mountpoint, mv, nameif, nc,
netstat, nice, nmeter, nohup, nslookup, od, openvt, patch, pidof, ping,
pipe_progress, pivot_root, printenv, printf, ps, pscan, pwd, rdate,
rdev, readlink, readprofile, realpath, renice, reset, resize, rm,
rmdir, rmmod, route, run-parts, sed, seq, setconsole, setkeycodes,
setlogcons, setsid, sh, sha1sum, showkey, sleep, sort, split, stat,
strings, stty, sum, swapoff, swapon, switch_root, sync, sysctl, tac,
tail, tar, tcpsvd, tee, telnet, telnetd, test, tftp, time, top, touch,
tr, traceroute, true, tty, tunctl, udhcpd, udpsvd, umount, uname,
uncompress, uniq, unix2dos, unzip, uptime, usleep, uudecode, uuencode,
vconfig, vi, watch, wc, wget, which, who, whoami, xargs, yes, zcat
and boom, a lot more stuff is there (except parted.. but it works anyways, and mkfs.ext2 is missing, and doesnt work). it should be okay to do everything in recovery anyways right? and i can just use mke2fs -m0 -b4096 /dev/block/mmcblk0p2 to format the ext2 partition?
EDIT: just tried the parted method and i dont think it works, i get this
Code:
(parted) mkpart primary fat32 256 2813951
mkpart primary fat32 256 2813951
mkpart primary fat32 256 2813951
(parted) mkpart primary ext2 2813952 3862527
mkpart primary ext2 2813952 3862527
mkpart primary ext2 2813952 3862527
(parted) print all
print all
print all
Model: SD SU02G (sd/mmc)
Disk /dev/block/mmcblk0: 3862528s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 256s 2813951s 2813696s primary lba
2 2813952s 3862527s 1048576s primary
anyways i used the first method and its fine, although the partitioning isnt spot on accurate, i just put on data2ext for cm6 and my available space is 504mb instead of 512mb and i checked all my calculations and everything, ah well close enough. thanks again!
It looks OK.
Sent from my HTC Legend
Need some help.
There's a possibility you would need to shutdown and power on again your phone at this point.
Click to expand...
Click to collapse
Possibility?
I got this:
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7973 MB, 7973371904 bytes
4 heads, 16 sectors/track, 243328 cylinders, total 15572992 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 256 13475839 6737792 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 13475840 15572991 1048576 83 Linux
Then i got
Code:
Command (m for help): mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat /dev/block/mmcblk0p1
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
The same with the mkfs.ext2 -m0 -b4096 /dev/block/mmcblk0p2
And now the phone says than my flash is empty or uses wrong format, dont want to mount it and want to format it. I press cancel.
if i make p again it shows:
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7973 MB, 7973371904 bytes
4 heads, 16 sectors/track, 243328 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
What is my mistake?
UPD: Seems like it worked with the parted
Spoiler
Code:
C:\androidsdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# dd if=/dev/zero of=/dev/block/mmcblk0 bs=131072 count=16
dd if=/dev/zero of=/dev/block/mmcblk0 bs=131072 count=16
16+0 records in
16+0 records out
2097152 bytes transferred in 0.568 secs (3692169 bytes/sec)
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos
mklabel msdos
mklabel msdos
(parted) unit s
unit s
unit s
(parted) print all
print all
print all
Model: SD SA08G (sd/mmc)
Disk /dev/block/mmcblk0: 15572992s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
(parted) mkpart primary fat32 256 13475839
mkpart primary fat32 256 13475839
mkpart primary fat32 256 13475839
(parted) mkpart primary ext2 13475840 15572992
mkpart primary ext2 13475840 15572992
mkpart primary ext2 13475840 15572992
Error: The location 15572992 is outside of the device /dev/block/mmcblk0.
(parted) mkpart primary ext2 13475840 15572991
mkpart primary ext2 13475840 15572991
mkpart primary ext2 13475840 15572991
(parted) print all
print all
print all
Model: SD SA08G (sd/mmc)
Disk /dev/block/mmcblk0: 15572992s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 256s 13475839s 13475584s primary lba
2 13475840s 15572991s 2097152s primary
(parted) quit
quit
quit
Information: You may need to update /etc/fstab.
# mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat /dev/block/mmcblk0p1
# mkfs.ext2 -m0 -b4096 /dev/block/mmcblk0p2
mkfs.ext2 -m0 -b4096 /dev/block/mmcblk0p2
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
65536 inodes, 262144 blocks
0 blocks (0%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
playahate said:
Need some help.
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7973 MB, 7973371904 bytes
4 heads, 16 sectors/track, 243328 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
What is my mistake?
Click to expand...
Click to collapse
I got this too... seems I forgot to enter the "w" command to write the partitions.
Absolutely. You neet to write the partition table exiting fdisk. And you can't execute mkfs.vfat and mke2fs inside fdisk shell! It's the same as you would try to microwave your sandwich in the fridge... it won't work that way...
agrrrrr. didnt see the next line with the w.
anyway i made it by parted. very good guide, very good rom =)
lil question: can i make ext3 or ext4 at any time? (after using data2ext).will it work correctly or wipe all data? or just when i make partitionong?
Yes. Just search the interwebs on how to convert ext2 -> ext3 -> ext4...

[Q] samsung galaxy s 8GB bug or normal?

i just got my samsung galaxy s today in UK. i started the phone and went to settings/sd card and phone memory to check it's memory storage
it says there that the sd card is 5.77gb and internal memory 1.84gb or something..
now, how does this make an 8GB galaxy s phone????
help!! is this NORMAL?? or should return it back?? it says 8gb from where i bought at argos.co.uk.
8gb quoted = ALWAYS less when formatted.
An example : 16gb iPad is actually 14gb. The size is an unformatted size before formatted for use.
Sent from my GT-I9000 using XDA Premium App
yetep said:
8gb quoted = ALWAYS less when formatted.
An example : 16gb iPad is actually 14gb. The size is an unformatted size before formatted for use.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
i dont understand T_T so this is normal???
what will happen if i press format USB storage on settings?? do i get the 8GB or lower?? will 5.77gb increase??
The 8 GB are splitted into 2 parts:
1) 6GB Storage
2) 2GB Apps (internal memory)
Sent from my SGS with Simply 3.5 Revolution ROM
scapula101 said:
i dont understand T_T so this is normal???
what will happen if i press format USB storage on settings?? do i get the 8GB or lower?? will 5.77gb increase??
Click to expand...
Click to collapse
If you formatted the SD card you will lose only your data. The extra is used to store other stuff to make it work. You won't be able to get 8gb out of it. If you want more memory you can get a decent size memory card cheap on play.com
[Q] [i9001] Where are the 8Gb?
I have a SGS+ and I am also questioning where are the 8Gb advertised in the specs.
Here is the output of 'df' in the Android Terminal Emulator:
Filesystem Size Used Free Blksize
/dev 176M 64K 176M 4096
/mnt/asec 176M 0K 176M 4096
/mnt/obb 176M 0K 176M 4096
/system 442M 343M 99M 4096
/data 1G 396M 962M 4096
/persist 4M 4M 796K 4096
/cache 98M 4M 94M 4096
/efs 4M 92K 4M 4096
/mnt/sdcard 4G 1G 3G 32768
There is only 4GB for internal sdcard and even with the system partitions the total size only adds up to ~6.05GB.
Where are the missing 2GB?
normal

[Q] Completely Hosed - Recovery Impossible?

Yeah, yeah. Sounds like a million other posts. I am a unix/linux sort of guy, so I'm quite familiar with navigating and working in *nix based operating systems.
Here is the synopsis:
Without an SD card, the device will not boot. I can hear the USB cycle and I'm stuck at a black screen. Sounds normal so far.
After booting up CWM, I can adb in. My first step was to check devices.
/dev/block # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop5 mmcblk0p2 ram10 ram15 ram6
loop1 loop6 mmcblk1 ram11 ram2 ram7
loop2 loop7 platform ram12 ram3 ram8
loop3 mmcblk0 ram0 ram13 ram4 ram9
loop4 mmcblk0p1 ram1 ram14 ram5
As you can see, there are a few missing block devices. I proceeded to mount each of these. Only mmcblk0p1 had anything on it: the boot partition, as I expected. Mmcblk1 was the device name for the SDCard, which deviates from what I would have expected. Blk0p2 contained nothing and was not mountable.
Next, I tried to do a 'mknod' to create the devices. This was successful to a degree, but did not actually create working devices. I attempted to mkfs.ext2 on them, that failed. For grins, I tried it on p1 and p2. The only one that worked was p1.
At this point, I decided to try and flash the boot.img I retrieved from here: "mrm3.net/nook-color-recover-any-bricked-device/" and see what I could do to get the device up and running - any self booting would be an improvement, I thought. This too failed. The 'dd' was successful and the partition now contained boot info, but when i tried to boot up, I still received a black screen:
/dev/block # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
144522+0 records in
144522+0 records out
73995264 bytes (70.6MB) copied, 44.914978 seconds, 1.6MB/s
/dev/block #
When I try to flash ANY rom, I get failures - obviously because there's no place for them to flash to.
'dmesg' doesn't contain any useful information. The device seems hosed. The last rom I was running was Cyanogen nightly #69, which wouldn't allow me to mount SDCard or do anything useful. When I tried to install nightly #80, I found that the device was no longer usable.
Hopefully this was thorough enough, I refrained from typing out the obvious stuff, but please feel free to suggest things. I'm stumped. I still think it can be saved, but I don't have a ton of hope.
Thanks a lot for giving this a read. I really hope someone can help out.
--
j.k
Ill add you to the list with everyone else here of people who are more advanced than I. But one of the fist things I learned about the Nook is that its pretty much impossible to brick. I'm sure someone from the list will be by to help soon.
I really hope so.
Logically, if the device nodes can be recreated, I could flash a new mod in. Perhaps I'm going about that the wrong way.
sangandongo said:
Next, I tried to do a 'mknod' to create the devices. This was successful to a degree, but did not actually create working devices. I attempted to mkfs.ext2 on them, that failed. For grins, I tried it on p1 and p2. The only one that worked was p1.
Click to expand...
Click to collapse
Have you verified that the partition table is actually intact/correct? No point trying to create device nodes if the underlying devices aren't there. What does "fdisk -l /dev/block/mmcblk0" give you, and how does it compare to the standard layout?
Maybe check notes with the OP of this thread -- appears that both of you have essentially the same problem.
jll544 said:
Have you verified that the partition table is actually intact/correct? No point trying to create device nodes if the underlying devices aren't there. What does "fdisk -l /dev/block/mmcblk0" give you, and how does it compare to the standard layout?
Maybe check notes with the OP of this thread -- appears that both of you have essentially the same problem.
Click to expand...
Click to collapse
Sorry, I should have included that earlier. The partition table is b0rked. I also had attempted applying the zips from the [ZIP][RECOVERY] EMMC Recovery Repair thread to no avail.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 15260 488312 b Win95 FAT32
/dev/block/mmcblk0p2 15261 242432 7269504 83 Linux
Not to sounds like a smartass (or maybe a dumbass) but have you tried to restore back to stock?
Yes. In my initial post, I stated that no restoring via zip works.
Currently I am attempting to rebuild the partition table as mine is hosed. I get the following output though, which is troubling by comparison to what I should be seeing:
~ # busybox fdisk /dev/block/mmcblk0
busybox fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 242432.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 15260 488312 b Win95 FAT32
/dev/block/mmcblk0p2 15261 242432 7269504 83 Linux
Command (m for help): d
d
Partition number (1-4):
Right, virtually all .zip restore files are filesystem-level recovery and assume that the partition table is unchanged.
Try forcing the geometry using "fdisk -H 255 -S 63 /dev/block/mmcblk0"
Before I write this, does the following look like what you'd expect? I mean, it makes sense considering...
Code:
~ # fdisk -H 255 -S 63 /dev/block/mmcblk0
fdisk -H 255 -S 63 /dev/block/mmcblk0
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 61 488312 b Win95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 17)
Partition 1 has different physical/logical endings:
phys=(1023, 3, 16) logical=(60, 202, 14)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 61 966 7269504 83 Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(1023, 3, 16) logical=(60, 202, 15)
Partition 2 has different physical/logical endings:
phys=(1023, 3, 16) logical=(965, 205, 8)
Partition 2 does not end on cylinder boundary
jll544 said:
Right, virtually all .zip restore files are filesystem-level recovery and assume that the partition table is unchanged.
Try forcing the geometry using "fdisk -H 255 -S 63 /dev/block/mmcblk0"
Click to expand...
Click to collapse
What he said. Texas Instrumentss OMAP devices such as the nook require that media, whether sd, mmc, etc, be formatted with particular geometry. One that's set up, you can create the partitions normally and forget it ever happened. Remember that the first partition should be FAT, and this is where the kernel (uImage) and ramdisk (uRamdisk) as well as bootloader (u-boot.bin) and pre-bootloader (mlo) go.
See here for more info.
I believe the version of busybox available to me on this 3.0.2.8 CWR SD image is too old to accomplish what the instructions on this post state: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
I've been unable to find a bundle of the binaries yet, but I'm still looking. That being said, I changed the geometry of the partition table and wrote the changes, then tried to dd again - fail.
sangandongo said:
Before I write this, does the following look like what you'd expect? I mean, it makes sense considering...
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 61 488312 b Win95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 17)
Partition 1 has different physical/logical endings:
phys=(1023, 3, 16) logical=(60, 202, 14)
Partition 1 does not end on cylinder boundary
<snip>
Click to expand...
Click to collapse
You mean you wrote the partition table as shown above? That won't work. You need to run fdisk with the corrected geometry, delete the existing partitions, and create new ones. Those warnings say that your partition LBA's are still aligned to the incorrect geometry.
What happens when remove all if the partitioning on the emmc, format it, and repartition it? For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean. Also, anyone tested for bad blocks? One of my laptops decided to take a **** and the only way I'm able to install an os on it is by installing ubuntu on half the hard drive. Maybe if it is bad blocks we could repartition around them?
Sent from my PC36100 using Tapatalk
RileyGrant said:
What happens when remove all if the partitioning on the emmc, format it, and repartition it? For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean. Also, anyone tested for bad blocks? One of my laptops decided to take a **** and the only way I'm able to install an os on it is by installing ubuntu on half the hard drive. Maybe if it is bad blocks we could repartition around them?
Click to expand...
Click to collapse
Save the FUD for somewhere else....
RileyGrant said:
For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean.
Click to expand...
Click to collapse
LOL, just about any operating system will write an unsuitable partition table if the end user commands it to do so. No, the OP has omitted details about what he did to get into his situation, but there is no chance it just happened on its own (i.e., his partition layout is technically valid but unbootable by OMAP). If we're going to hazard wild guesses, I'd say he was trying to install Backtrack or some other non-Android Linux distribution.
Hahah I only used linux as an example because ubuntu its all I have run for a coupe years now. but you sir are completely oblivious too the fact that evo users, thunderbolt users and now nook users have reported the same issue and symptoms, always on gingerbread. A self corruption of internal memory.
Sent from my PC36100 using Tapatalk
jll544 said:
LOL, just about any operating system will write an unsuitable partition table if the end user commands it to do so. No, the OP has omitted details about what he did to get into his situation, but there is no chance it just happened on its own (i.e., his partition layout is technically valid but unbootable by OMAP). If we're going to hazard wild guesses, I'd say he was trying to install Backtrack or some other non-Android Linux distribution.
Click to expand...
Click to collapse
In this case, I believe it was caused either by "fixing permissions" while using Rom Manager, or by doing it in CWM. This was in an attempt to get out of CM7 nightly #69, which all but rendered my system inoperable.
I agree with you though: there's likely no reason why linux would cause corruption on a disk. If anything, an app might be to blame, but it would have to explicitly do so.
That aside, I am very close to getting my Nook fixed. I rebuilt the partition table this morning after loading busybox 1.18 onto my SD card. ran 'fdisk' with the proper geometry, deleted the existing partitions, built each out to standard specs, then changed the filesystem id for each. After that I did a mkfs.vfat and mke2fs on the appropriate partitions and wrote the configuration.
I rebooted, did a dd of a 1.0.1 boot image to mmcblk0p1 and of a system image to mmcblk0p5 and tried to boot, but I'm still getting a black screen.
Here is my current partition table after I resized it and marked the partitions with their respective types:
Code:
/busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
I made the Fat32 Partitions using mk.vfat and the linux partitions with mke2fs -j -L <label>. Something still just isn't right.
Blah. I get so OCD about this sort of ****. I need to just go outside and play, this is driving me nuts.
sangandongo said:
Blah. I get so OCD about this sort of ****. I need to just go outside and play, this is driving me nuts.
Click to expand...
Click to collapse
It's not booting because you're missing your /rom partition. There is no data in /mmcblk0p2, which init calls for all your device info. Hopefully you have a backup of that as well. Without it, you won't be able to run any roms with your nook color.
And unfortunately that is a partition that is not good to share with anyone else besides each individual nook owner because is contains all the unique Device identifiers for your Nook. If two people would have the same Device info and you're both logged into your B&N stock, it will error out on the B&N server side and de-register your device and the other person as well.
If you need further guidance, PM me and I'll see what I can do to help to resolve your /rom partition issue.
-Racks
I DD'd every partition off my friend's Nook. Every one. Just to see if I could get this puppy running. Still black.

[Q] Question ?

Hello All,
just a silly question in my mind .. why do SGS GT-i9000 has 2GB dedicated ROM ?
i mean whats the purpose or function of it ? can any1 please explain and eleborate in detail ?
all the other phones have storage , RAM and CPU .. only this phone has 2GB ROM which i didnt see in any other phone why?
It has been reserved to install game and apps.
Sent from my GT-I9000 using XDA App
can we reduce this size. 1gb to rom & 15gb to sdcard.
Users with Ideos X5 do it.
Anyone know linux commands, may you see script below.
fdisk /dev/block/mmcblk0
d
1
d
2
n
5
1708032
n
1708033
1953792
t
2
b
w
mke2fs "-F", "-j", "-b4096", "-m0", "/dev/block/mmcblk0p2 (what is -j flag ?)
mkfs.vfat "-v", "-n", "SDCard, "/dev/block/mmcblk0p1"
is it work?
Thats my partition table.
Moderator pls dnt merge posts I need get access to devs topic. Thank you.
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 169004 32 168972 0% /dev
/dev/block/mtdblock3 81920 2388 79532 3% /cache
/dev/block/mmcblk0p2 1935192 291380 1643812 15% /data
/dev/block/mmcblk0p1 13660864 11975456 1685408 88% /sdcard
/dev/block/mtdblock2 192000 131920 60080 69% /system
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16005464064 bytes
1 heads, 16 sectors/track, 1953792 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1708032 13664224 c Win95 FAT32 (LB
A)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1708033 1953792 1966080 c Win95 FAT32 (LB
A)
Partition 2 does not end on cylinder boundary
~ # fdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 13.9 GB, 13992165376 bytes
4 heads, 16 sectors/track, 427007 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ # fdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
Disk /dev/block/mmcblk0p2: 2013 MB, 2013265920 bytes
4 heads, 16 sectors/track, 61440 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p2 doesn't contain a valid partition table
~ #
I try create custom partition size for my phone i897
With Simplistian help I can get partition Info of my phone
#df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 169004 32 168972 0% /dev
/dev/block/mtdblock3 81920 2388 79532 3% /cache
/dev/block/mmcblk0p2 1935192 291380 1643812 15% /data
/dev/block/mmcblk0p1 13660864 11975456 1685408 88% /sdcard
/dev/block/mtdblock2 192000 131920 60080 69% /system
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16005464064 bytes
1 heads, 16 sectors/track, 1953792 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1708032 13664224 c Win95 FAT32 (LB
A)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1708033 1953792 1966080 c Win95 FAT32 (LB
A)
Partition 2 does not end on cylinder boundary
~ # fdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 13.9 GB, 13992165376 bytes
4 heads, 16 sectors/track, 427007 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ # fdisk -l /dev/block/mmcblk0p2
fdisk -l /dev/block/mmcblk0p2
Disk /dev/block/mmcblk0p2: 2013 MB, 2013265920 bytes
4 heads, 16 sectors/track, 61440 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p2 doesn't contain a valid partition table
androiderrr said:
It has been reserved to install game and apps.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
but why ? whats the cause behind it ?
phones that dont have dedicated and assigned ROMs can also have games and apps ... for e.g. SGS 2 doesnt has dedicated ROM it only has 1GB RAM and Dual core 1.2Ghz cpu but we still install apps and games into it .. which means they are stored directly to SD card or Internal memory of phone ..
but I havent gone through any solid answer from anyone that why 2GB dedicated ROM given to SGS GT i9000 ?
does that mean we can only install apps games etc upto 2GB volume on our SGS i9000 ? not more then that ?
Yeah we can install games and apps only upto 2GB.But thats more than sufficient.Dont u think so?Even one day if u run out of space u can install as many apps as u wish on extranal SD card.
Sent from my GT-I9000 using XDA App
androiderrr said:
Yeah we can install games and apps only upto 2GB.But thats more than sufficient.Dont u think so?Even one day if u run out of space u can install as many apps as u wish on extranal SD card.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
so that means other androids like SGS 2 etc , apps and games are installed directly into phone's internal storage ( internal SD card ? ) plus with that we can choose the option to install apps and games to external storage ( external sd card ) as well ?
1 more question .. does it really makes any difference to install apps or games into phones internal ROM or external sd card ?
what i mean is does this makes any impact on performance or on anything ?
salmanghiyas said:
so that means other androids like SGS 2 etc , apps and games are installed directly into phone's internal storage ( internal SD card ? ) plus with that we can choose the option to install apps and games to external storage ( external sd card ) as well ?
Even with galaxy s you have option to install apps wherever u like internal memory(you have 2GB for that) and on external sd card
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
salmanghiyas said:
1 more question .. does it really makes any difference to install apps or games into phones internal ROM or external sd card ?
what i mean is does this makes any impact on performance or on anything ?
Click to expand...
Click to collapse
Hardly any noticible difference on performance..
Sent from my GT-I9000 using XDA App
androiderrr said:
Hardly any noticible difference on performance..
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
TQVM androiderrr
salmanghiyas said:
Hello All,
just a silly question in my mind .. why do SGS GT-i9000 has 2GB dedicated ROM ?
i mean whats the purpose or function of it ? can any1 please explain and eleborate in detail ?
all the other phones have storage , RAM and CPU .. only this phone has 2GB ROM which i didnt see in any other phone why?
Click to expand...
Click to collapse
When the SGS was first released, we didn't have the possibility of loading apps to SD card, this only came with the later releases of Android.
The phone being released with 2GB was one of the things that made it the best phone at that time.

semi-brick EMMC problem?

I have an early HD+ that had been updated to an Android 4.2 and then 4.4 using AndroidForNook's AFN semi-commercial SD cards.
It was slowing down and crashing more - I guess with Google's Chrome and other 'almost system' updates.
I decided to go for a CyanogenMod distro - many weeks ago now. I don't remember exactly which - not the most recent, Android 4.4 type, probably 10.xx. I made an SD card - I am a very competent Windows admin and CMD user. Know next to nothing of Unix/Linux/Android systems. Used the same SD card that worked with AFN. Consequently Nook would get as far as showing B&N Nook splash screen w/o SD card inserted; or AFN's menu that would respond to volume and N buttons, but stick at "loading ....." whatever I'd chosen with the ORIGINAL AFN image on the inserted SD.
Followed a couple of weeks of trying several 'recovery' images that mostly did not get as far as screen output. Apparent resolutions focused on SD card boot issues - which I followed at length, ordered new SD cards etc.
TWO things still produce results: a no-EMMC SD recovery that boots to TWRP - but that seemed to work only ONCE; and when part booted with the ORIGINAL AFN SD I can get a shell session as root via ADB. Below are some of my findings...
====================================
File system commands like mount, parted, dd hang when dealing with /dev/block/mmcblk0
====================================
Relevant parts from the kernel boot-up log???
<6>[ 2.412078] mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.412567] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
<6>[ 2.412872] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
<6>[ 2.413116] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
<4>[ 2.415679] Alternate GPT is invalid, using primary GPT.
<6>[ 2.415863] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
<6>[ 2.418334] mmcblk0boot1: unknown partition table
<6>[ 2.419281] mmcblk0boot0: unknown partition table
<4>[ 2.666687] mmc1: host does not support reading read-only switch. assuming write-enable.
<6>[ 2.685424] mmc1: new high speed SDHC card at address aaaa
<6>[ 2.686248] mmcblk1: mmc1:aaaa SU08G 7.40 GiB
<6>[ 2.705169] mmcblk1: p1 p2 p3
<4>[ 2.924194] mmc2: card claims to support voltages below the defined range. These will be ignored.
<4>[ 2.943786] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 2.944488] mmc2: new SDIO card at address 0001
===================================
Can not mount SDCARD in the current half-booted state. looks like fstab is not read at startup; however /etc/recovery.fstab exists and is readable.
~ # mount sdcard
mount sdcard
mount: can't read '/etc/fstab': No such file or directory
====================================
Don't really understand what below implies - can read an ACTUAL GPT partition table off an ACUTAL storage device?
cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 13500416 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 306176 mmcblk1p1
179 26 613376 mmcblk1p2
179 27 6831104 mmcblk1p3
==============================================
SO - does the above imply a SERIOUS problem with the emmc MAG2GA memory device (thanks to a bug in some distro...); or do I need a proper rebuild of the GPT partitions that will finally allow the Nook to boot properly from a recovery SD and accept an original B&N 2.1 image?? I do have my serial number and don't mind a bogus MAC address in the /ROM directory.
Many thanks in advance. Chris
You probably are subject to the TRIM bug. It can happen even when running from SD since the SD install uses part of emmc for support and gets trimmed with a trim command. If so, there is no fixing it. Only solution is to try a noemmc SD install.
Sent from my SM-T707V using XDA Premium HD app
Thanks; and is there a known stable no-Emmc image?
Leap - you are a star on here for your quick responses. Thanks. Also what is a definitive diag I can run to confirm the Emmc is ruined?
I presume it is worth trying to find the fastest SD the Nook will reliably work with to run the OS from?
Chris
frankenstein30 said:
Leap - you are a star on here for your quick responses. Thanks. Also what is a definitive diag I can run to confirm the Emmc is ruined?
I presume it is worth trying to find the fastest SD the Nook will reliably work with to run the OS from?
Chris
Click to expand...
Click to collapse
No, fastest is not the best. Get a SanDisk class 4, which is probably what that SD you have is. And I don't really know the test for bricked emmc. Verygreen had a test I think in his noemmc thread.
Sent from my SM-T707V using XDA Premium HD app

Categories

Resources