I'm running the new Cyanogen release 3.9.6. After running the command I get this status screen
Code:
# rzscontrol /dev/block/ramzswap0 -s
rzscontrol /dev/block/ramzswap0 -s
DiskSize: 24388 kB
NumReads: 1
NumWrites: 0
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 0
GoodCompress: 0 %
NoCompress: 0 %
PagesStored: 0
PagesUsed: 0
OrigDataSize: 0 kB
ComprDataSize: 0 kB
MemUsedTotal: 0 kB
"GoodCompress: 0 %"? What's wrong? Does this mean it's not working?
Thanks
yes it means its not working
cyanogen stated there were some issues with 3.9.6 so don't wory about it
Compcache was updated to 0.6 in this build. Your current scripts wont work.
Here's how to enable it:
Code:
modprobe ramzswap
rzscontrol /dev/block/ramzswap0 --init
swapon /dev/block/ramzswap0
To get stats:
Code:
rzscontrol /dev/block/ramzswap0 -s
No more compcache talk now
Click to expand...
Click to collapse
cyanoge's words from his thread
hope it helps
senaia said:
cyanoge's words from his thread
hope it helps
Click to expand...
Click to collapse
That's what I followed, but no luck.
where does it swap?
Hi,
I'm pretty new to compache... But where does it store the swap info...
I have a linux swap partition on my sd card, i was wondering does it swap there or somewhere else?
to me it looks like /dev/block/ramzswap0
But i don't know where that actually is. Seems like on the ex3 partition i have.
Did you check right after you enabled it? Because if you did then it did not have time to swap anything. Check in few min. That did the trick for me. If you did not enable it and tried to run stats you would get some kind of error, something along the lines of can't finde ramzswap0, does not exist.... can't remember exactly
Good luck
Hi all,
I'm still working trying to work my openvpn:
Link related to thread:
http://forum.xda-developers.com/showpost.php?p=8347800&postcount=3
http://code.google.com/p/android-openvpn-installer/issues/detail?id=2
Now, some info about my config:
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Check load of tun.ko
#lsmod
tun 11088 0 - Live 0xbf203000
Path to busybox:
# which busybox
/system/xbin/busybox
Path to Openvpn:
# which openvpn
/system/xbin/openvpn
Links for openvpn due harcode
# busybox ls -la /system/xbin/bb
total 8
drwxrwxrwx 1 0 0 0 Oct 20 03:17 .
drwxr-xr-x 1 0 2000 0 Oct 20 03:18 ..
lrwsrwsrwt 1 0 0 60 Oct 20 03:14 ifconfig -> /system/xbin/ifconfig
lrwsrwsrwt 1 0 0 56 Oct 20 03:17 route -> /system/xbin/route
# busybox ls -la /system/xbin/ifconfig
busybox ls -la /system/xbin/ifconfig
lrwsrwsrwt 1 0 0 60 Oct 20 07:19 ←[1;36m/system/xbin/ifconfig←[0m -> ←[1;32m/system/xbin/busybo←[0m
# busybox ls -la /system/xbin/route
busybox ls -la /system/xbin/route
lrwsrwsrwt 1 0 0 60 Oct 20 07:19 ←[1;36m/system/xbin/route←[0m -> ←[1;32m/system/xbin/busybox←[0m
Path to tun.ko module
# busybox ls -la /system/lib/modules
busybox ls -la /system/lib/modules
total 152
drwxrwxrwx 1 0 0 0 Oct 20 07:19 ←[1;34m.←[0m
drwxr-xr-x 1 0 0 0 Oct 20 02:19 ←[1;34m..←[0m
-rwxrwxrwx 1 0 0 154447 Oct 20 12:19 ←[1;32mtun.ko←[0m
Busybox Version:
# busybox
busybox
BusyBox v1.17.1 (2010-08-12 23:44:34 CDT) multi-call binary.
Openvpn Version based on first link
# openvpn
openvpn
OpenVPN 2.1_rc15 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] built on Jan 21 2010
Now, my openvpn connect, but cant get ip address , i mean, on GUI interface of openvpn after connect, still like "connected to mydomain.com as"..
if a try to launch via terminal (adb shell) after write "openvpn --config <path to my *.ovpn config file>, freeze the screen and nothins happens...
This is the final phase for each connection, looking on my logfile:
Wed Oct 20 09:13:40 2010 TLS: Initial packet from XXX.XXX.XXX.XXX:YYY, sid=caddb5cd 96066b25
Wed Oct 20 09:13:43 2010 VERIFY OK: depth=1, /C=CO/ST=CU/L=Bogota/O=Favernet/CN=NASVPN/[email protected]
Wed Oct 20 09:13:43 2010 VERIFY OK: depth=0, /C=CO/ST=CU/O=Favernet/CN=FavernetVPN/[email protected]
Wed Oct 20 09:13:56 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 20 09:13:56 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 20 09:13:56 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 20 09:13:56 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 20 09:13:56 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Oct 20 09:13:56 2010 [FavernetVPN] Peer Connection Initiated with XXX.XXX.XXX.XXX:YYY
Wed Oct 20 09:13:57 2010 Initialization Sequence Completed
I'm not good with this, but i don't know what else need verification..any suggestions?
http://forum.xda-developers.com/showthread.php?t=729531 >> This is a DEVELOPMENT section, not GENERAL. Do NOT post questions here!
try here: http://forum.xda-developers.com/forumdisplay.php?f=748
Moved to Q&A as not development
OK, so I have been at this for a while now, trying to figure out how to pull boot.img. We need this in order to get a custom recovery image made.
The problem is that most of the help that's out there refers to doing a dump based on identifying the proper /proc/MTD. It's never that simple though. This phone doesn't have it (and we don't have a map of where to go from here).
Here is the partition info:
Code:
major minor #blocks name
7 0 13545 loop0
7 1 202829 loop1
7 2 31217 loop2
7 3 18743 loop3
7 4 13545 loop4
179 0 15679488 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 28672 mmcblk0p5
179 6 204800 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1024000 mmcblk0p12
179 13 1572864 mmcblk0p13
179 14 12288 mmcblk0p14
179 15 12599296 mmcblk0p15
179 16 15622144 mmcblk1
179 17 15621120 mmcblk1p1
254 0 13545 dm-0
254 1 202828 dm-1
254 2 31216 dm-2
254 3 18742 dm-3
254 4 13545 dm-4
Can anyone with a few more years on me in this racket give me a heads up on this? Perhaps a mapping for us to get started? Yeah, I know I'm totally wet behind the ears, but someone has to get this thing rolling. Hopefully that doesn't mean I'll be the first to brick my phone (had a close call tonight).
See what's mounted by typing "mount" first. It'll show you what mmcblk0pX maps to what (mounted, that is).
thecubed said:
See what's mounted by typing "mount" first. It'll show you what mmcblk0pX maps to what (mounted, that is).
Click to expand...
Click to collapse
ok, so here was the output (of what i assume is the relevant part):
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p12 /system ext3 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
So 12 is system, 13 is data, 6 is cache, and 5 is persist. What I'm not seeing is boot. Am I missing anything here?
To find unnamed partitions, you might want to dump them to your SD card and try mounting the partitions on your PC.
You can copy a partition to a file on your SD card by using "dd if=/dev/block/mmcblk0pX of=/sdcard/mmcblk0pX.img bs=1024"
Then on your desktop, you can try running fdisk to see what the partition type is and issue a "mkdir /mnt/test" then "mount -o loop -t <type of partition from fdisk> /path/to/mmcblk0pX.img /mnt/test".
From there, you should be able to investigate what's in those partitions by poking around in /mnt/test on your desktop. Once you're done, "umount /mnt/test" to close the image file.
Referring to your list of partitions and sizes, partitions of 2048 blocks or less are probably not worth your time investigating, however I may be wrong.
Also, quick tip: mmcblk0 (with no pX) is the entire onboard storage as one unit. Don't bother dumping that to your SD card, since it contains all partitions, but will be a really big file and a big mess to figure out the partitions and mount it.
Good luck!
Outstanding, and THANKS A MILLION for the help. I've been banging my head against the wall here...
I should probably hit the sack, but I had started pulling those already, so I've got a head start.
Okay, good luck! I don't have this device, but a friend is getting one here soon (not sure how soon though) so I'm interested in getting CWM ported and some groundwork laid for CM7/etc on it.
Whenever you get time, I'm interested in seeing what you find the partitions are...
Thanks!
Went ahead and put a little more time into it...
used your method for dumping each individual partition.
A listing with file sizes:
Code:
2048 mmcblk0p1 4096 mmcblk0p11 2048 mmcblk0p2 4 mmcblk0p4 24576 mmcblk0p8
4096 mmcblk0p10 12288 mmcblk0p14 7168 mmcblk0p3 4096 mmcblk0p7 8192 mmcblk0p9
My common fdisk result (for all files) is:
Code:
fdisk -l mmcblk0p11
Disk mmcblk0p11: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf6908d66
Disk mmcblk0p11 doesn't contain a valid partition table
Maybe I need to look at this again when I'm a little less tired, but this is the result of every image file.
P11 looks to be just a placeholder partition. Try p3, p8, p9, and p14.
Usually /boot is a lower number partition...
If you could upload the dumps of those partitions somewhere, I may be able to tell you which is which. (PM the link, don't post public- I'm not sure how XDA would feel about that).
This shouldn't be too hard to identify which is which. If you're well versed in hex editing, you could run those images through a hex dumper and check the file's magic numbers. I'm not too familiar with this device, but I'd say it can't be much different than the HTC boot.img format. Grab a boot.img from somewhere and see if the first couple of bytes match up on the dumps you've got.
From there, that should give you a clue with which is which. I'm betting you'll find which is the kernel by just doing a "strings" on the dumps and looking for things like "kernel" or "linux".
Good luck!
EDIT: after doing some reading, looks like some of the partitions are the fastboot type. Fastboot images = kernel + ramdisk. And, at least one of those partitions will be the Qualcomm AMSS partition for the radio chipset. Do a "strings <filename> | grep -i qualcomm" (or replace qualcomm with things like 'amss' or 'radio') to find which is which.
QualComm didn't turn up anything, so I changed the search to "comm." I don't have much time to look at this, but here's a quick dump:
mmcblk0p1 = radio?
Code:
mmcblk0p1 | grep -i comm
Device Transfer: Failed to queue the transfer command
DMOV Issue Cmd: Command issued
DMOV Request not Valid: Command list not on 64-bit boundary
DMOV Request not Valid: Invalid number of commands
DMOV Get Chan %d Error: Command error occured
DMOV Get Chan %d Error: Command-phase bus error occured
DMOV Stop Handler: cannot stop channel %d, commands pending
DMOV Stop Handler: cannot stop channel %d, issuing commands
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
mmcblk0p2 = boot?
Code:
strings mmcblk0p2 | grep -i comm
QC_SMEM_PROC_COMM_CQ
ip_uint32 idev_comm_open( void )
dt_uint32 dt_CommOpen( void )
void idev_comm_close(ip_uint32 h)
void dt_CommClose(dt_uint32 h)
ip_commStatus_e idev_comm_queryCloseStatus(ip_uint32 h)
ip_commStatus_e idev_comm_queryConnectStatus(ip_uint32 h)
dt_CommStatus dt_QueryConnectStatus(dt_uint32 h)
const ip_int16 idev_comm_secureInitContext( void )
const dt_int16 dt_CommSecureInitContext( void )
void idev_comm_secureDeleteContext( void )
void dt_CommSecureDeleteContext( void )
EP0 command reply was not sent correctly %d [%d:%d]
Device Transfer: Failed to queue the transfer command
[AUE] update common code block (size):
[AUE] update common code block do_a_swap_ccb(size):
[AUE] Error: get common code block range
[AUE] Error: get common function block range
DMOV Issue Cmd: Command issued
DMOV Request not Valid: Command list not on 64-bit boundary
DMOV Request not Valid: Invalid number of commands
DMOV Get Chan %d Error: Command error occured
DMOV Get Chan %d Error: Command-phase bus error occured
DMOV Stop Handler: cannot stop channel %d, commands pending
DMOV Stop Handler: cannot stop channel %d, issuing commands
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
void idev_comm_connect(ip_uint32 h, ip_char* addr, ip_uint16 PortNum, ip_int32 TimeOut)
void dt_CommConnect(dt_uint32 h, dt_char* addr, dt_uint16 PortNum, dt_int32 TimeOut)
void idev_comm_send(ip_uint32 h, ip_char* SendBuf, ip_uint32 SendLen, ip_int32 TimeOut)
void dt_CommSend(dt_uint32 h, dt_char* SendBuf, dt_uint32 SendLen, dt_int32 TimeOut)
ip_commStatus_e idev_comm_querySendStatus(ip_uint32 h, ip_uint32* SentLen)
dt_CommStatus dt_QuerySendStatus(dt_uint32 h, dt_uint32* SentLen)
void idev_comm_recv(ip_uint32 h, ip_char* RecvBuf, ip_uint32 RecvLen, ip_int32 Timeout)
void dt_CommRecv(dt_uint32 h, dt_char* RecvBuf, dt_uint32 RecvLen, dt_int32 Timeout)
ip_commStatus_e idev_comm_queryRecvStatus(ip_uint32 h, ip_uint32* RecvLen)
dt_CommStatus dt_QueryRecvStatus(dt_uint32 h, dt_uint32* RecvLen)
const ip_int16 idev_comm_setSecureInfo( ip_int32 protocolID, ip_uint32 cipherSuites[], ip_int32 cipherSuitesSize, ip_char certificate[], ip_int32 certificateSize)
const dt_int16 dt_CommSetSecureInfo( dt_int32 protocolID, dt_uint32 cipherSuites[], dt_int32 cipherSuitesSize, dt_char certificate[], dt_int32 certificateSize)
ip_commStatus_e idev_httpTerminateAsync( ip_httpInterface_s *httpInterface )
CH9: Received vendor specific command for device, but no handlers registered
CH9: Received reserved command for device, but no handlers registered
[AUE] Info: no common code block, this is not ARM region, do zipping instead
Info: no common func block, this is not ARM region, do zipping instead
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
cdc_handle_encapsulated_command
encapsulated_command_complete
hfat_common.c
EP0 command reply was not sent correctly %d [%d:%d]
CH9: Received vendor specific command for device, but no handlers registered
CH9: Received reserved command for device, but no handlers registered
The others returned nothing.
Just for shoots and giggles
I expanded the search for the word boot on 02, and here is what it revealed:
Code:
strings mmcblk0p2 | grep -i boot
/sys_boot/keystore/key.str
/sys_boot/keystore/store.pt
sys_boot
; Time Stamp unavailable from boot loader.
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_aarm_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_hash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_hw_init.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_mc_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_flash_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_setup_mpu_dal.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_adsp_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_load_ramfs.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_sd_img_update.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
boothw_target.c
sys_boot
smem_boot_init: version %x does not match all procs!
boot_elf_loader
boot_elf_loader_factory
boot_sec_elf_loader
boot_sec_elf_loader_factory
boot_flash_trans_nand
boot_flash_trans_nand_factory
boot_flash_trans_nor
boot_flash_trans_nor_factory
boot_flash_trans_sdcc
boot_flash_trans_sdcc_factory
boot_flash_dev_nor
boot_flash_dev_nand
boot_flash_dev_sdcc
clkrgm_mpss_boot.c
/mmc1/IMAGE/APPSBOOT.MBN
/mmc1/IMAGE/BOOT.IMG
/mmc1/IMAGE/EMMCBOOT.MBN
EMMCBOOT.MBN
BOOT.IMG
/sys_boot/IMAGE/
/sys_boot/IMAGE2/
/sys_boot/IMAGE3/
bootsymmetrickey
E/boot/qcsbl
F/boot/oemsbl
F/boot/osbl
G/boot/appsbl
H/boot/apps
I/boot/modem
J/boot/modem_fs1
K/boot/modem_fs2
L/boot/fota
M/boot/qcsbl_cfg
P/boot/adsp
01, same search:
Code:
trings mmcblk0p1 | grep -i boot
sys_boot
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sflashc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_shared.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk_settings.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ddr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
sys_boot
smem_boot_init: version %x does not match all procs!
E/boot/qcsbl
F/boot/oemsbl
F/boot/osbl
G/boot/appsbl
H/boot/apps
I/boot/modem
J/boot/modem_fs1
K/boot/modem_fs2
L/boot/fota
M/boot/qcsbl_cfg
P/boot/adsp
02 - search for "home"
Code:
strings mmcblk0p2 | grep -i home
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_aarm_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_hash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_hw_init.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_mc_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_flash_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_setup_mpu_dal.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_adsp_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_load_ramfs.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_sd_img_update.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jslave/core/jusb_core.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jslave/dcd/dcd_tdi_4x.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jos/jos_bus.c
01 search for home
Code:
strings mmcblk0p1 | grep -i home
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sflashc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_shared.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk_settings.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ddr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
Remembering that factory reset is the sole function of the boot-loader on this device, I did a search for "factory"
02:
Code:
mmcblk0p2 | grep -i factory
boot_elf_loader_factory
boot_sec_elf_loader_factory
boot_flash_trans_nand_factory
boot_flash_trans_nor_factory
boot_flash_trans_sdcc_factory
01 - no results
I think we have a winner? I'd *almost* place money on 2 being boot, but I need a little insight here.
I should be able to pass you these files tonight. I'm just limited right now as I'm at work and remoting in on a slow connection.
Great work!
A few possible corrections:
Thought #1: From what I've read, AMSS (the radio) has multiple 'nvram partitions' where configuration is stored. The partitions with size 2048 look like those.
My updated guess:
P1 = hardware bootloader (like HBOOT on a HTC device)
P2 = second stage bootloader (references to android and wm_ldr)
The actual AMSS firmware is usually above 10MB in size, so the radio firmware is most likely a larger partition.
Thought #2: /boot is quite possibly a fastboot image. Those are usually compressed, hence you will not find any strings in it. It would be all binary.
If you can, run "hexdump -n 32 <filename>" on each of the dumps, and paste the output here.
With that hexdump information, I can tell you which partitions have the fastboot magic number and which are AMSS configuration partitions or ext3 filesystems.
As a side note, I wonder if this device supports fastboot commands... you could potentially try something like "fastboot reboot recovery" which should be harmless to see. Of course, you'd need Google's fastboot tools on your machine first though. (http://android-dls.com/wiki/index.php?title=Fastboot)
If it turns out that fastboot works, a nondestructive way of testing if the device is signed would be to extract the recovery image and replace it's ramdisk with one containing Clockwork. It may be as simple as "fastboot boot <newimage>" to boot the new image without actually changing anything on the phone.
Anyway, get those hex dumps, then we'll see where that leads...
Great work!
Alright - I'll get on that tonight when I get home (probably about another 2.5 hours from now including dinner).
The other thing that's been rattling around in my head, and I know I shouldn't be jumping this far ahead (nor do I want to derail this thread), is I (and the entire community) need to make some modifications to the android.policy.jar thus completing the migration from Bing on this phone. One string would make all the difference Unfortunately, it is odexed. I'm guessing this has many dependencies, and the best method to go about this would be to pretty much deodex the entire O.S.. Obviously, that's not something I feel comfortable with doing until we are completed with this, but my thought process is on track for what I need to do, right?
I also need to research if it is possible to dump my entire phone as an image as part of an Android AVM, so I don't end up bricking my phone. I had my entire phone lockup and go black last night. About had a heart attack.
Obviously, this takes precedence, but just wanted to throw all that out there while it was fresh in my mind (things get lost quickly - I have twenty browser windows open juggling about a dozen different thought processes).
Hex Dumps
P1:
Code:
0000000 dcd1 844b 1034 73d7 435a 7d0b ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020
P2:
Code:
0000000 000b 0000 0003 0000 0000 0000 0000 0450
0000010 31f8 0013 31f8 0013 31f8 0463 0000 0000
0000020
I'll have to do the fastboot install at home.
majorpay said:
Alright - I'll get on that tonight when I get home (probably about another 2.5 hours from now including dinner).
The other thing that's been rattling around in my head, and I know I shouldn't be jumping this far ahead (nor do I want to derail this thread), is I (and the entire community) need to make some modifications to the android.policy.jar thus completing the migration from Bing on this phone. One string would make all the difference Unfortunately, it is odexed. I'm guessing this has many dependencies, and the best method to go about this would be to pretty much deodex the entire O.S.. Obviously, that's not something I feel comfortable with doing until we are completed with this, but my thought process is on track for what I need to do, right?
I also need to research if it is possible to dump my entire phone as an image as part of an Android AVM, so I don't end up bricking my phone. I had my entire phone lockup and go black last night. About had a heart attack.
Obviously, this takes precedence, but just wanted to throw all that out there while it was fresh in my mind (things get lost quickly - I have twenty browser windows open juggling about a dozen different thought processes).
Click to expand...
Click to collapse
I believe I saw that it has been deodexed on stetsonaw's Twitter page. You may want to get in touch with him
Yeah, I saw he had claimed that over on androidforums. I should start checking that area more often. I put a post out to feel it out and see if he might be willing to throw it my way I think ultimately he is waiting patiently in the wings waiting for us to get done with this so he can release the ROM he is working on.
Just wanted to say keep up the good work. I plan to look into this more when I get home but sounds like you are definitely on the right track. Excited to see more progress soon.
I just got into the scene as this is my first droid phone but I have been reading up as quickly as possible to contribute to making roms.
OK, so I am back in the saddle.
I have run a ./fastboot reboot, and as expected, no response. (says waiting for device) I believe I still need to modify my hosts.
I expect you've seen my hex dumps. Any thoughts?
Edit: Phone went into "Download is in progress. Do not disconnect cable."
Real? I don't know, but this is hindering me from moving forward.
majorpay said:
P1:
Code:
0000000 dcd1 844b 1034 73d7 435a 7d0b ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020
P2:
Code:
0000000 000b 0000 0003 0000 0000 0000 0000 0450
0000010 31f8 0013 31f8 0013 31f8 0463 0000 0000
0000020
I'll have to do the fastboot install at home.
Click to expand...
Click to collapse
Great- now I just need hexdumps of the other partitions I listed: P3, P8, P9, and P14.
P1 and P2 are of little interest to us, we're looking for the one containing recovery and the main kernel+ramdisk.
As soon as we identify which is the recovery partition, we'll be super close to finding whether recovery is signed and one step closer to porting CWM.
PS: Fastboot reboot may have put your phone in download mode. If you're stuck in it, just try using "fastboot reboot recovery", then from there you should be able to select "reboot" and end up in Android again...
p3
Code:
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000020
p8
Code:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0000020
p9
Code:
0000000 4e41 5244 494f 2144 66ac 0038 8000 0020
0000010 fb21 002f 0000 0120 0000 0000 0000 0110
0000020
p14
Code:
0000000 4e41 5244 494f 2144 66ac 0038 8000 0020
0000010 8cd9 0033 0000 0120 0000 0000 0000 0110
0000020
And ./fastboot devices consistently shows nothing. I added the device per Ubuntu guide, and restarted udev, but still nada.
Edit... I missed something on fastboot (I added the wrong device). I'll go back and recheck.
Edit 2: Still no luck.
As an update, it appears that holding the power button with the volume button up puts the device into what looks like a fastboot state (only when plugged into usb).
Edit: Maybe this is just a recovery mode / Emergency mode.
It is designated by a sign that reads: "Download is in progress. Do not disconnect cable."
According to my usb device information, it shows up as a LGE USB CDMA Modem.
Code:
lsusb
Bus 001 Device 025: ID 1004:6200 LG Electronics, Inc.
51-android.rules
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="<my username>"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004",ATTR{idProduct}=="6200", OWNER="<my username>"
"./fastboot devices" shows nothing
Has anyone else tried?
I backed up ICS boot.img and system.img before upgrading and then restore after flashing V20A.kdz but it doesn't boot. Just stays at the non-animated LG logo.
arararagi said:
Has anyone else tried?
I backed up ICS boot.img and system.img before upgrading and then restore after flashing V20A.kdz but it doesn't boot. Just stays at the non-animated LG logo.
Click to expand...
Click to collapse
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
RuedasLocas said:
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
Click to expand...
Click to collapse
It works if I also restore the MBR from XP.
arararagi said:
It works if I also restore the MBR from XP.
Click to expand...
Click to collapse
Here you don's have that "if"... sorry
Found this in another thread
gordon0001 said:
well, since no one answered i figured out the new kernel (3.1) is the issue. replacing the kernel with the old kernel (2.6) in recovery.img solved the problem, but partitions dont get mounted and couldnt get them mounted, since i barely know the internals of a linux kernel and the kernel ramdisk
Click to expand...
Click to collapse
I tried doing the same thing and just catting the resulting recovery image to boot.
It starts up and adb works, however only external SD on Tegra is accessible.
Code:
~ # find /dev/block/
/dev/block/
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
/dev/block/mmcblk0p1
/dev/block/platform
/dev/block/platform/sdhci-tegra.2
/dev/block/platform/sdhci-tegra.2/mmcblk0p1
/dev/block/platform/sdhci-tegra.2/by-num
/dev/block/platform/sdhci-tegra.2/by-num/p1
/dev/block/platform/sdhci-tegra.2/mmcblk0
/dev/block/mmcblk0
~ # cat /proc/partitions
major minor #blocks name
179 0 15351296 mmcblk0
179 1 15347200 mmcblk0p1
From dmesg:
Code:
<6>[ 3.855253] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.855433] sdhci: Copyright(c) Pierre Ossman
<4>[ 3.856721] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 3.856848] mmc0: no vmmc regulator found
<7>[ 3.858202] Registered led device: mmc0::
<6>[ 3.861711] mmc0: SDHCI controller on platform [sdhci-tegra.3] using ADMA
<4>[ 3.863024] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 3.863145] mmc1: no vmmc regulator found
<7>[ 3.864473] Registered led device: mmc1::
<6>[ 3.866846] mmc1: SDHCI controller on platform [sdhci-tegra.0] using ADMA
<4>[ 3.867178] tegra_gpio_irq_set_wake() called
<3>[ 3.867284] sdhci sdhci-tegra.2: SD card wake-up event registrationfailed with eroor: -22
<4>[ 3.868587] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 3.868706] mmc2: no vmmc regulator found
<7>[ 3.870035] Registered led device: mmc2::
<6>[ 3.872372] mmc2: SDHCI controller on platform [sdhci-tegra.2] using ADMA
<7>[ 3.872860] Registered led device: button-backlight
<4>[ 3.872961] keypad_led_probe success
<6>[ 3.874563] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.875491] usbcore: registered new interface driver usbhid
<6>[ 3.875681] usbhid: USB HID core driver
<6>[ 3.876370] logger: created 256K log 'log_main'
<6>[ 3.876608] logger: created 256K log 'log_events'
<6>[ 3.876939] logger: created 256K log 'log_radio'
<6>[ 3.877259] logger: created 256K log 'log_system'
<4>[ 3.972419] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 3.972635] mmc0: error -110 whilst initialising MMC card
<4>[ 4.085800] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.086013] mmc0: error -110 whilst initialising MMC card
<4>[ 4.213528] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.213657] mmc0: error -110 whilst initialising MMC card
<4>[ 4.379808] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.379939] mmc0: error -110 whilst initialising MMC card
This is how things should look (from the new kernel):
Code:
~ # find /dev/block/
/dev/block/
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
/dev/block/mmcblk1p1
/dev/block/mmcblk1
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p13
/dev/block/mmcblk0p12
/dev/block/mmcblk0p11
/dev/block/mmcblk0p10
/dev/block/mmcblk0p9
/dev/block/mmcblk0p8
/dev/block/mmcblk0p7
/dev/block/mmcblk0p6
/dev/block/mmcblk0p5
/dev/block/mmcblk0p4
/dev/block/mmcblk0p3
/dev/block/mmcblk0p2
/dev/block/mmcblk0p1
/dev/block/platform
/dev/block/platform/sdhci-tegra.2
/dev/block/platform/sdhci-tegra.2/mmcblk1p1
/dev/block/platform/sdhci-tegra.2/by-num
/dev/block/platform/sdhci-tegra.2/by-num/p1
/dev/block/platform/sdhci-tegra.2/mmcblk1
/dev/block/platform/sdhci-tegra.3
/dev/block/platform/sdhci-tegra.3/mmcblk0boot0
/dev/block/platform/sdhci-tegra.3/mmcblk0boot1
/dev/block/platform/sdhci-tegra.3/mmcblk0p13
/dev/block/platform/sdhci-tegra.3/mmcblk0p12
/dev/block/platform/sdhci-tegra.3/mmcblk0p11
/dev/block/platform/sdhci-tegra.3/mmcblk0p10
/dev/block/platform/sdhci-tegra.3/mmcblk0p9
/dev/block/platform/sdhci-tegra.3/mmcblk0p8
/dev/block/platform/sdhci-tegra.3/mmcblk0p7
/dev/block/platform/sdhci-tegra.3/mmcblk0p6
/dev/block/platform/sdhci-tegra.3/mmcblk0p5
/dev/block/platform/sdhci-tegra.3/mmcblk0p4
/dev/block/platform/sdhci-tegra.3/mmcblk0p3
/dev/block/platform/sdhci-tegra.3/mmcblk0p2
/dev/block/platform/sdhci-tegra.3/mmcblk0p1
/dev/block/platform/sdhci-tegra.3/by-num
/dev/block/platform/sdhci-tegra.3/by-num/p13
/dev/block/platform/sdhci-tegra.3/by-num/p12
/dev/block/platform/sdhci-tegra.3/by-num/p11
/dev/block/platform/sdhci-tegra.3/by-num/p10
/dev/block/platform/sdhci-tegra.3/by-num/p9
/dev/block/platform/sdhci-tegra.3/by-num/p8
/dev/block/platform/sdhci-tegra.3/by-num/p7
/dev/block/platform/sdhci-tegra.3/by-num/p6
/dev/block/platform/sdhci-tegra.3/by-num/p5
/dev/block/platform/sdhci-tegra.3/by-num/p4
/dev/block/platform/sdhci-tegra.3/by-num/p3
/dev/block/platform/sdhci-tegra.3/by-num/p2
/dev/block/platform/sdhci-tegra.3/by-num/p1
/dev/block/platform/sdhci-tegra.3/by-name
/dev/block/platform/sdhci-tegra.3/by-name/UDB
/dev/block/platform/sdhci-tegra.3/by-name/CAL
/dev/block/platform/sdhci-tegra.3/by-name/FOT
/dev/block/platform/sdhci-tegra.3/by-name/MLT
/dev/block/platform/sdhci-tegra.3/by-name/DRM
/dev/block/platform/sdhci-tegra.3/by-name/UDA
/dev/block/platform/sdhci-tegra.3/by-name/NVA
/dev/block/platform/sdhci-tegra.3/by-name/USP
/dev/block/platform/sdhci-tegra.3/by-name/MSC
/dev/block/platform/sdhci-tegra.3/by-name/CAC
/dev/block/platform/sdhci-tegra.3/by-name/APP
/dev/block/platform/sdhci-tegra.3/by-name/LNX
/dev/block/platform/sdhci-tegra.3/by-name/SOS
/dev/block/platform/sdhci-tegra.3/mmcblk0
/dev/block/mmcblk0
~ # cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15351296 mmcblk1
179 49 15347200 mmcblk1p1
And dmesg:
Code:
<6>[70:01:01 00:00:08.609] sdhci: Secure Digital Host Controller Interface driver
<6>[70:01:01 00:00:08.609] sdhci: Copyright(c) Pierre Ossman
<6>[70:01:01 00:00:08.609] sdhci-pltfm: SDHCI platform and OF driver helper
<4>[70:01:01 00:00:08.609] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.609] mmc0: no vmmc regulator found
<7>[70:01:01 00:00:08.609] Registered led device: mmc0::
<6>[70:01:01 00:00:08.609] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<6>[70:01:01 00:00:08.609] sdhci-tegra sdhci-tegra.0: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<6>[70:01:01 00:00:08.609] sdhci-tegra sdhci-tegra.0: Error: tegra3 io dpd not supported for sdhci-tegra.0
<4>[70:01:01 00:00:08.609] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.609] mmc1: no vmmc regulator found
<7>[70:01:01 00:00:08.609] Registered led device: mmc1::
<6>[70:01:01 00:00:08.619] mmc1: SDHCI controller on sdhci-tegra.0 [sdhci-tegra.0] using ADMA
<3>[70:01:01 00:00:08.619] Failed gpio lp0 enable for irq=405, error=-22
<3>[70:01:01 00:00:08.619] sdhci-tegra sdhci-tegra.2: SD card wake-up event registrationfailed with eroor: -22
<6>[70:01:01 00:00:08.619] sdhci-tegra sdhci-tegra.2: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<4>[70:01:01 00:00:08.619] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.619] mmc2: no vmmc regulator found
<7>[70:01:01 00:00:08.619] Registered led device: mmc2::
<6>[70:01:01 00:00:08.619] mmc2: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
RuedasLocas said:
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
Click to expand...
Click to collapse
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
ircalf said:
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
Click to expand...
Click to collapse
I confess that I was "unhappy" in that expression
ircalf said:
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
Click to expand...
Click to collapse
i guess his point was that what the o.p tried to do didnt make sense, so what he said was in the same context, also its obvious that with new bootloader that it would not boot with the previous boot,img otherwise we wouldnt have such problems like not being able to use the v20a bootloader with the previous v10 firmware
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 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: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Rastikan said:
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 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: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Click to expand...
Click to collapse
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Do you see small text appear on the screen after loading it?
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
jcsullins said:
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Click to expand...
Click to collapse
Ok, from the 'Palm mode' ( POWER + HOME + VOLUME-UP ) for about 30 seconds ...
Code:
dfu-util -d 0830:8070 -R -D moboot-dfu-20150128
jcsullins said:
Do you see small text appear on the screen after loading it?
Click to expand...
Click to collapse
Yes!!! Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time ( although I was getting some access through SSH )
jcsullins said:
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
Click to expand...
Click to collapse
Code:
(bootloader) [2100] a6_test: batt valid=1 percent=0 voltage=3225680
(bootloader) [2110] a6_test: batt temp=19 current=-312 coulombs=0
Although it does says 0 percent, I did let it charge the whole night ( as your tpdebrick tool suggests )
jcsullins said:
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
Click to expand...
Click to collapse
Yes, I see ( finally) stuff on the screen! Again, Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time.
http://forum.xda-developers.com/attachment.php?attachmentid=3139872&stc=1&d=1422547266
Now can I go ahead and load-up or run your full toolbox software and reformat/setup the entire flash device for Android ?