PE Hardware serial console

[JRANGER]

Originally Posted by vldmr

attached are extracted files.

I am not sure i would know how to recreate edgeRamdisk though because of this:

$ file edgeRamdisk.crc
edgeRamdisk.crc: gzip compressed data, was "ramdisk.android", from Unix, last modified: Tue Mar 29 13:17:10 2011
$ mv edgeRamdisk.crc edgeRamdisk.gz
$ gunzip edgeRamdisk.gz

gzip: edgeRamdisk.gz: decompression OK, trailing garbage ignored
$ file edgeRamdisk
edgeRamdisk: Linux rev 1.0 ext2 filesystem data, UUID=e9945e52-a611-494f-8d1e-23ec1f75847c

So what exactly is that trailing garbage i wonder

awesome! Yeah it was originally called ramdisk.android but i renamed the files to keep the, separated...Does that actually make a difference when loading it?

[nikkie]

It looks like gunzip is actually unzipping it to the file itself. If you go past the first few thousand bytes you can see files. In any case, I grabbed init.rc off my edge with adb. It's attached.

[JRANGER]

ok...how do i get adb working...It shows the device as a code when its connected but when i run adb shell nothing works...Sorry im a noob

[JRANGER]

never mind...damn usb keeps disconnecting...stupid wire

[tekknogenius]

Originally Posted by ivanjt

Toyz, tekknogenius,

My parts guy came up with this for you, he thinks the P11157SCT-ND might do be what you need.
http://search.digikey.com/scripts/Dk...t-nd&x=20&y=17

I'll have to get some and try my hand at soldering

[JRANGER]

ok...so my init.rc idea definetly isnt going to work but I have a couple emails into guys who have been working with it and also contacted the clockworkmod developer on twitter so see if he will help if we send him this thing over...Im going to continue to look at stuff and try to figure this out but it jsut doesnt seem like things work as i expect...the mounting doesnt work in adb or im stupid cause i dont really know what im doing
Not sure this thing has fastboot on it but ill keep testing

[vicinc]

managed to cut my case, sort the serial cable, and have terminal working on my borked pe. however I can not start the updating process as niki, see my log please.

[JRANGER]

http://www.linux-mtd.infradead.org/faq/ubifs.html
Information on the ubifs crack pot file system which is the root of most of our problems

[nikkie]

Originally Posted by vicinc

managed to cut my case, sort the serial cable, and have terminal working on my borked pe. however I can not start the updating process as niki, see my log please.

Hi Vicinc.

Looks like your file system has been corrupted according to the log here:

[ 16.404433] EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #4136: : directory entry across blocks - offset=1024, inode=1073783265, rec_len=41760, name_len=131
[ 16.420363] EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #4218: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

It sounds like an fsck might help. From adb:

$ busybox fsck --help
BusyBox v1.15.2 (2011-03-29 10:04:13 EDT) multi-call binary

Usage: fsck [-ANPRTV] [-C fd] [-t fstype] [fs-options] [filesys...]

Check and repair filesystems

Options:
-A Walk /etc/fstab and check all filesystems
-N Don't execute, just show what would be done
-P With -A, check filesystems in parallel
-R With -A, skip the root filesystem
-T Don't show title on startup
-V Verbose
-C n Write status information to specified filedescriptor
-t type List of filesystem types to check

[ptsenter]

Originally Posted by vicinc

managed to cut my case, sort the serial cable, and have terminal working on my borked pe. however I can not start the updating process as niki, see my log please.

Here is a file:
Substitute XXXX..XX with your serial number without BF.
Remove extension .txt.
Then execute

adb push properties /sys/class/graphics/fb2/.

from a directory where you have this file.

You might need to gain RW permissions for that.

[JRANGER]

anybody else notice the alt recovery partition?

$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00080000 "BBM_reserve1"
mtd1: 00100000 00080000 "bootloader-alt"
mtd2: 00100000 00080000 "environment-alt"
mtd3: 00300000 00080000 "kernel-alt"
mtd4: 00300000 00080000 "kernelrecovery-alt"
mtd5: 02e00000 00080000 "maintenance"
mtd6: f5c00000 00080000 "Android"
mtd7: 06400000 00080000 "MRVL_BBM"
mtd8: 00040000 00010000 "bootloader"
mtd9: 00080000 00010000 "bootcode"
mtd10: 00040000 00010000 "environment"
mtd11: 00300000 00010000 "kernel"
mtd12: 00400000 00010000 "kernelrecovery"

Is it possible there is a second button sequence to load the recovery ?

[vicinc]

seems I do not have fb2 folder
# ls
ls
fbcon
fb0
fb1
#

[ptsenter]

Originally Posted by vicinc

seems I do not have fb2 folder
# ls
ls
fbcon
fb0
fb1
#

First,
I suggest you start your own thread dedicated to your device. Info about your device spread all over the places and you hijacking somebody's else thread. Collect all info into that thread. It would be much easier for you and anybody having some ideas to test and share.
Second,
try to run start_epd.sh under /system/esi/bin and check results in /tmp/start.log. And don't reboot after running script.

[vicinc]

I did not hijacked the thread. The thread was about the serial.
my post is saying that I build the cable and worked, (i will send pics of my setup shortly, I used the cable from an old serial mouse).
Also I reported than on my device did not worked forcing the update through. I thought was the right place to report my results, sorry if i disturbed anybody. I know the most knowledgeable people are here on this thread. Unfortunately my system is garbled badly. if anybody knows a way from forcing the update from the terminal I will really appreciate this.

[nikkie]

Originally Posted by vicinc

I did not hijacked the thread. The thread was about the serial.
my post is saying that I build the cable and worked, (i will send pics of my setup shortly, I used the cable from an old serial mouse).
Also I reported than on my device did not worked forcing the update through. I thought was the right place to report my results, sorry if i disturbed anybody. I know the most knowledgeable people are here on this thread. Unfortunately my system is garbled badly. if anybody knows a way from forcing the update from the terminal I will really appreciate this.

Vicinc, running "run boot_user" does force the upgrade. I can't tell from your logs whether you actually ran that in the u-boot prompt (it looks like not, you typed it before the prompt, but did not succeed at getting into u-boot). Regardless, the problem with YOUR device appears to be filesystem corruption. So you have two options, either make sure you get the device into the u-boot prompt, or run fsck on your partitions from busybox from adb.