Database Info

Linux on ipaq 210/214

Hi. I'm trying to install linux onto my pda as im sick of windows mobile. I've managed to un-tar the Angstrom distro and the boot image file onto their correct partitions. This is how my partitions are set-up:
Disk /dev/mmcblk0: 2059 MB, 2059403264 bytes
4 heads, 16 sectors/track, 62848 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 1 610 19512 6 FAT16
/dev/mmcblk0p2 611 62848 1991616 83 Linux
I boot the SD-card and load linux. But i'm getting a kernel panic as follows:
VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0).
I don't know what to do! I'm really stuck and i cannot stand windows mobile 6, i really cannot. Could somebody really help me please.
Thanks people.

Welcome to forums
As we dedicate only to HTC devices, unless your device is listed on the Wiki
http://wiki.xda-developers.com/
Better try here:
http://www.pdastreet.com/forums/forumdisplay.php?f=12

Color Literati Ereader Android Possible?

I bought a Literati for only $65 shipped and was thinking maybe android could be ported to this device.
CPU:S3C6410 [email protected]
Audio: None
Camera: None
Touch screen: None
Screen: Color 7" unknown X Unknown
Memory
SD: up to 16gig
User: 256mb(black) expandable to 1gb once telnet is enabled.
System: 64mb(i think)
USB
Mini USB: Mode=device
internal USB: Mode=Host(currently connected to a wireless dongle)
Network
Wifi: rt2860sta
3G: None
Ethernet: None
NAND 512MiB 3,3V 8-bit
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00340000 : "Kernel"
0x00340000-0x00d40000 : "resource"
0x00d40000-0x11140000 : "File System 1"
0x11140000-0x20000000 : "User space"
The Bootloader is:
U-Boot 1.1.6-g794ab523-dirty (Aug 23 2010 - 00:52:53) for SMDK6410
The Environment has:
bootargs=console=ttySAC0,115200 loglevel=0 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs
bootcmd=nand read c0008000 40000 300000;bootm c0008000
bootdelay=0
baudrate=115200
ethaddr=[MAC of Literati]
ipaddr=192.168.1.28
serverip=192.168.1.27
gatewayip=192.168.1.2
netmask=255.255.255.0
The Kernel is:
Linux (none) 2.6.24.2 #180 Mon Aug 23 00:49:07 CST 2010 armv6l GNU/Linux
The resource:
It begins with FILE_SECTION04 and then a file directory which shows logo.bin, update.bin, and zImage_rfs.
Here is the development website with more information http://literatidevs.com

Just got one of these today, actually. I looked up and down that board, but didn't find any info on enabling telnet. You have a link handy?

[Q] Can't flash phone from Linux (or Windows)

Hi,
I'm trying to upgrade my Nexus S I9020 to ICS -- well, actually,
now I'm just trying to get my phone back. I backed up my phone
before I started, but now I can't even mount my phone on my
computer (Linux) to do a restore.
On power-on my phone immediately goes to fastboot mode, saying
> fastboot mode - no boot or recovery image
I see four options: reboot bootloader, reboot, recovery, and
power off. I go to recovery and I get to a screen with
ClockworkMod Recovery v5.0.2.0 at the bottom and a set of
options. At this point, if I connect my phone to the computer
with a USB cord, I can see it with lsusb,
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 002: ID 1ea7:0002
> Bus 004 Device 002: ID 056a:0011 Wacom Co., Ltd Graphire 2 4x5
> Bus 001 Device 003: ID 18d1:4e22 Google Inc. Nexus S (debug)
but fdisk -l doesn't see anything. Now I execute "mount USB
storage" on the phone and Nautilus (linux file manager) pops up
with a mount at /media/CB59-1402, but there's nothing in it. Now
fdisk -l shows
$ sudo fdisk -l
...
> Disk /dev/sdb: 14.3 GB, 14314094080 bytes
> 64 heads, 32 sectors/track, 13650 cylinders, total 27957215 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: 0x00000000
So the computer found some mass storage there. Now I try to
create a file there,
$ sudo touch /media/CB59-1402/test.txt
> touch: cannot touch `/media/CB59-1402/test.txt': Input/output error
so the filesystem or partitioning or something seems to be
borked. The filesystem is vfat (right?) so I try to fix it with
$ sudo fsck -t vfat /dev/sdb
> fsck from util-linux 2.21
> dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
> open: No medium found
I have the Android SDK installed, so I look to see if adb can see
the phone,
$ adb devices
> List of devices attached
> 3430CA26FCB200EC recovery
OK. Try
$ adb shell
It returns immediately. Try fastboot,
$ fastboot devices
Nothing.
--
I'm really stumped. I got here because the web page for the ROM
said to reformat everything from CMR. I reformatted /sdcard,
/system, /cache, /data, and /boot.
Help!
Thanks,
-Rod

fastboot only works in the bootloader i believe, not recovery. adb may not be working because Android is no longer installed (/system partition). To save the trouble next time, when switching between very different ROMs, all that needs to be done is a data/factory reset, formatting /system and formatting /boot. SDCard is optional, i never do it (data/factory reset gets rid of the .android_secure folder already).
I've not had this problem in linux with being unable to get into the SDCard though, this is what you want to sort out so you can copy a ROM .zip and flash through CWM. Everything besides this is how it should be. Try unmounting it and mounting it manually, something along these lines should work fine:
# mkdir /media/nexus
# mount -t auto /dev/sdb /media/nexus
Now try and open up /media/nexus with nautilus. Good luck.

p999 login problem

need helpe for thes p999 login prblem and info by lg tool
Connecting with P999
For connect with phone you must:
1. Unplug usb cable and reconnect battery
2. Press VolDown-key & PowerUp-key and wait for LG logo
3. Release PowerUp-key and wait for Download logo
4. Release VolDown-key and plug usb cable
Connected
Receiving phone info
Getting phone info
Model: P999
Platform: LG Qualcomm
Software Platform: Android
SDRAM Size: 64 MB + 512 MB
NAND Flash Size: 128 MB + 8 GB
CPU: MDM6200 + NVIDIA Tegra AP20H
Firmware Released: Mar 27 2011 10:12:24
Firmware Compiled: MAR 27 2011 10:00:00
Firmware Version: P9992097/M6600A-SCAUTNZ-2.0.9720T
IMEI: 012571-00-273213-5
Bluetooth Address: B0:89:91:E9:E1:03
Flash Device Name: H8BCS0QG0MMR
Flash Vendor ID: 0x000000ad
Flash Product ID: 0x000000b1
Flash FS Blocks: 0x000001c2
Flash Pages Per Block: 0x00000040
Flash Bytes Per Page: 0x00000800
Flash Bytes Per Spare: 0x00000040
Connect mode: Normal
Info received
Receiving phone info
Getting phone info
Model: P999
Platform: LG Qualcomm
Software Platform: Android
SDRAM Size: 64 MB + 512 MB
NAND Flash Size: 128 MB + 8 GB
CPU: MDM6200 + NVIDIA Tegra AP20H
Firmware Released: Mar 27 2011 10:12:24
Firmware Compiled: MAR 27 2011 10:00:00
Firmware Version: P9992097/M6600A-SCAUTNZ-2.0.9720T
IMEI: 012571-00-273213-5
Bluetooth Address: B0:89:91:E9:E1:03
Flash Device Name: H8BCS0QG0MMR
Flash Vendor ID: 0x000000ad
Flash Product ID: 0x000000b1
Flash FS Blocks: 0x000001c2
Flash Pages Per Block: 0x00000040
Flash Bytes Per Page: 0x00000800
Flash Bytes Per Spare: 0x00000040
Connect mode: Normal
Info received
Restoring to factory defaults
This phone require manual Factory Reset.
For Factory Reset you must:
1. Unplug usb cable and battery.
2. Plug battery and power on phone.
3. Type code 1809#*999# to call Qualcomm menu.
4. Go to "Factory Reset", select "OK" and reboot the phone.
5. Factory reset must be completed after next boot.
Factory defaults successfully restored
Unlocking phone
Unlock: Start
Getting phone info...
Getting phone info: OK
Switching to internal loader...
Switching to internal loader: OK
Sending external loader...
Sending external loader: OK
Switching to external loader...
Switching to external loader: OK
Dumping Security...
Dumping Security: OK
Backuping Security to file: Backups\P999_security_012571002732135_2012-5-5_6-15-53.sbf
Unlocking Security: OK
Flashing Security...
Flashing Security: OK
Switching to normal mode...
Switching to normal mode: OK
Unlock: Finish
Phone successfully unlocked
Don't forget to reconnect battery
Disconnected

Difference storage amount between brands!

I just bought a new Quality micro SD from Samsung, 32GB EVO. I was using a brandless 32GB.
I used Win32DiskImager program (windows) to create images for both SD cards. One has everything installed what I want.
The newer Samsung has only the basic apps like link2SD, rootinternal2external.
The strange part is that there is an difference in the amount of free storage, both are parttioned with the same program.
The only difference is that the amount of partitions:
Black brandless: 3 partitions: Data,App,swap
Samsung: Data , App
But the image file that I pulled from the SD cards is as follows:
Black: 31.691.112.448 MB
Samsung: 31.440.502.784 MB
How come there is an difference?
I want to burn the old image on my new card. I guess I can make a partition of the black SD card about 260MB smaller, then create
a new image again, then burn it. I hope that works.
But is it normal that the amount of storage differs between brands???

I think that yes, regards

[How to] Copy image between different size micro SD
I found a way to copy my larger SD image, made with Win32diskimager, into my smaller Samsung 32GB micro SD:
http://softwarebakery.com/shrinking-images-on-linux
Basicly you have to do:
- Use a tool to access the micro SD and make the last partition XXX MB smaller. This creates unpartitioned space.
- Create a image file from that micro SD: xxxx.img
- Boot into a Linux Operating system, Like Ubuntu 14.04LTS, by installing it on your HD or boot directly from a live CD
- Open a terminal screen. With CTRL+ALT+T, or use the graphical UI to open one terminal.
- in that terminal, execute the command: fdisk -l xxxx.img
- The output of the command looks like the following:
Disk myimage.img: 6144 MB, 6144000000 bytes, 12000000 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: 0x000ea37d
Device Boot Start End Blocks Id System
myimage.img1 2048 9181183 4589568 b W95 FAT32
Now we have to calculate where we want to cut the xxxx.img file. We want to cut away the last part that is not allocated to any partition.
Above you see the line "myimage.img1 2048 9181183 4589568 b W95 FAT32".
The last partition ends at 9181183, in your example it will be different ofcourse, just take the end of the last partition.
If you have 2 partitions, then you have 2 lines under:
"Device Boot Start End Blocks Id System"
in this example we have to cut from 9181183+1. Identify also what the block size is. In our example it's 512.
512 is the block size. In your example it might be different. If it's different, execute below command with a different value.
Now we cut away the empty space that is not used in our xxx.img.
Execute in the terminal screen: truncate --size=$[(9181183+1)*512] xxxx.img
The xxxx.img file is now smaller and can be burned into the smaller device.