Database Develop

danger spl wit cymod rom

someone answer this for me asap please. can u use haykuros danger spl for cymods roms

You can use it, but you dont have to use it.

im asking cuz i just came from the eclair 2.1 rom back to cymod i wiped everything twice and flashed cymod but its been on the g1 screen for about 10 minutes or so now. its the first time since i rooted my fone dats it been on the g1 screen for this long. is this normal or to be expected

Depends, hook up your USB lead and get a logcat to see what its doing.
It does sound a long time, but it does work find with DangerSPL.

lol ok u lost me there, how do i hook up usb lead and logcat and the whole shebang

http://forum.xda-developers.com/showthread.php?t=532719
You need to setup ADB.
and then run
"adb logcat"
From the command prompt.

i think im in the same boat. have never had ANY problems like this. installed manup's first 2.1 rom, ran it for a couple days, decided to restore a nandroid of 4.2.8.1, ran that for a couple days, then i tried the newest version manup put out. i wiped the ext3, and the dalvik-cache folder, stuck at G1 screen. wiped everything and tried to flash CM 4.2.9.1, stuck at G1 screen. nandroid restore works fine. wtf

kscasper13 said:
i think im in the same boat. have never had ANY problems like this. installed manup's first 2.1 rom, ran it for a couple days, decided to restore a nandroid of 4.2.8.1, ran that for a couple days, then i tried the newest version manup put out. i wiped the ext3, and the dalvik-cache folder, stuck at G1 screen. wiped everything and tried to flash CM 4.2.9.1, stuck at G1 screen. nandroid restore works fine. wtf
Click to expand...
Click to collapse
Wipe everything, data - dalvik and ext
Reboot
Wipe everything again and then flash the rom and see if that helps. Sometimes on a single wipe fragments of the old rom can still be present and cause problems just like this.

shadowch31 said:
Wipe everything, data - dalvik and ext
Reboot
Wipe everything again and then flash the rom and see if that helps. Sometimes on a single wipe fragments of the old rom can still be present and cause problems just like this.
Click to expand...
Click to collapse
tried that, thanks, just reinstalled the radio and SPL, then ran a log cat, its just sitting at
C:\Users\K4SP3R>adb logcat
- waiting for device -
I//system/xbin/busybox( 48): +++ "In a world of deceit, open your eyes. Don't
be afraid and you realize......"
I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.2.9.1
I//system/xbin/busybox( 48): --- Executing firstboot.sh
I//system/xbin/busybox( 48): --- Checking filesystems
I//system/xbin/busybox( 48): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 48): Superblock last mount time (Mon Dec 21 08:23:12 2
009,
I//system/xbin/busybox( 48): now = Mon Feb 23 21:14:39 2009) is in the future
.
I//system/xbin/busybox( 48): Fix? yes
I//system/xbin/busybox( 48): Superblock last write time (Mon Dec 21 08:48:07 2
009,
I//system/xbin/busybox( 48): now = Mon Feb 23 21:14:39 2009) is in the future
.
I//system/xbin/busybox( 48): Fix? yes
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2 was not cleanly unmounted, c
heck forced.
I//system/xbin/busybox( 48): Pass 1: Checking inodes, blocks, and sizes
I//system/xbin/busybox( 48): Pass 2: Checking directory structure
I//system/xbin/busybox( 48): Pass 3: Checking directory connectivity
I//system/xbin/busybox( 48): /lost+found not found. Create? yes
I//system/xbin/busybox( 48): Pass 4: Checking reference counts
I//system/xbin/busybox( 48): Pass 5: Checking group summary information
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIF
IED *****
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2: 11/33280 files (0.0non-cont
iguous), 1155/132536 blocks
I//system/xbin/busybox( 48): cp: cannot stat '/data/app-private/*': No such fi
le or directory
I//system/xbin/busybox( 48): cp: cannot stat '/data/dalvik-cache/*': No such f
ile or directory
I//system/xbin/busybox( 48): +++ Apps-to-SD successfully enabled
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
E/flash_image( 140): error opening /data/recovery.img: No such file or director
y
I/DEBUG ( 134): debuggerd: Dec 17 2009 21:34:52
I/vold ( 133): Android Volume Daemon version 2.0
I/vold ( 133): New MMC card 'SU08G' (serial 1883712959) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa
I/vold ( 133): Disk (blkdev 179:0), 15523840 secs (7580 MB) 3 partitions
I/vold ( 133): New blkdev 179.0 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 3
I/vold ( 133): Partition (blkdev 179:1), 14313852 secs (6989 MB) type 0xb
I/vold ( 133): New blkdev 179.1 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 2
I/vold ( 133): Partition (blkdev 179:2), 1060290 secs (517 MB) type 0x83
I/vold ( 133): New blkdev 179.2 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1
I/vold ( 133): Partition (blkdev 179:3), 144585 secs (70 MB) type 0x82
I/vold ( 133): New blkdev 179.3 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0
I/vold ( 133): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:aaaa/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 133): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 133): Volmgr not ready to handle device
D/vold ( 133): Bootstrapping complete
D/AKMD ( 142): akmd 1.6.6 START
D/AKMD ( 142): library version: 1.2.1.1129
Click to expand...
Click to collapse

Looks like there is a problem with your Ext partition, have you tried repartitioning the card and then checking tomake sure it's been done correctly using parted?

repartitioned both cards, does the same thing on both cards

Are you guys installing the HTC recovery image BEFORE you install CyanogenMod?

Stuck at G1 on any ROM install but nandroid backup of Dwang's 1.15 works fine

i flashed an Eclair ROM about 2 weeks ago from Eugene and manup, worked fine, used it for a couple days. went back to a nandroid of 4.2.8.1 and tried to update to CM's newest when it dropped, got stuck at G1 screen. so i wiped everything(dalvik, ext3) and tried installing a fresh CM 4.2.9.1. stuck at G1 screen. but the nandroid backup works fine.
here's my logcat:
C:\Users\K4SP3R>adb logcat
- waiting for device -
I//system/xbin/busybox( 48): +++ "In a world of deceit, open your eyes. Don't
be afraid and you realize......"
I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.2.9.1
I//system/xbin/busybox( 48): --- Executing firstboot.sh
I//system/xbin/busybox( 48): --- Checking filesystems
I//system/xbin/busybox( 48): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 48): Superblock last mount time (Mon Dec 21 08:23:12 2
009,
I//system/xbin/busybox( 48): now = Mon Feb 23 21:14:39 2009) is in the future
.
I//system/xbin/busybox( 48): Fix? yes
I//system/xbin/busybox( 48): Superblock last write time (Mon Dec 21 08:48:07 2
009,
I//system/xbin/busybox( 48): now = Mon Feb 23 21:14:39 2009) is in the future
.
I//system/xbin/busybox( 48): Fix? yes
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2 was not cleanly unmounted, c
heck forced.
I//system/xbin/busybox( 48): Pass 1: Checking inodes, blocks, and sizes
I//system/xbin/busybox( 48): Pass 2: Checking directory structure
I//system/xbin/busybox( 48): Pass 3: Checking directory connectivity
I//system/xbin/busybox( 48): /lost+found not found. Create? yes
I//system/xbin/busybox( 48): Pass 4: Checking reference counts
I//system/xbin/busybox( 48): Pass 5: Checking group summary information
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIF
IED *****
I//system/xbin/busybox( 48): /dev/block/mmcblk0p2: 11/33280 files (0.0non-cont
iguous), 1155/132536 blocks
I//system/xbin/busybox( 48): cp: cannot stat '/data/app-private/*': No such fi
le or directory
I//system/xbin/busybox( 48): cp: cannot stat '/data/dalvik-cache/*': No such f
ile or directory
I//system/xbin/busybox( 48): +++ Apps-to-SD successfully enabled
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
E/flash_image( 140): error opening /data/recovery.img: No such file or director
y
I/DEBUG ( 134): debuggerd: Dec 17 2009 21:34:52
I/vold ( 133): Android Volume Daemon version 2.0
I/vold ( 133): New MMC card 'SU08G' (serial 1883712959) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa
I/vold ( 133): Disk (blkdev 179:0), 15523840 secs (7580 MB) 3 partitions
I/vold ( 133): New blkdev 179.0 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 3
I/vold ( 133): Partition (blkdev 179:1), 14313852 secs (6989 MB) type 0xb
I/vold ( 133): New blkdev 179.1 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 2
I/vold ( 133): Partition (blkdev 179:2), 1060290 secs (517 MB) type 0x83
I/vold ( 133): New blkdev 179.2 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1
I/vold ( 133): Partition (blkdev 179:3), 144585 secs (70 MB) type 0x82
I/vold ( 133): New blkdev 179.3 on media SU08G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0
I/vold ( 133): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:aaaa/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 133): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 133): Volmgr not ready to handle device
D/vold ( 133): Bootstrapping complete
D/AKMD ( 142): akmd 1.6.6 START
D/AKMD ( 142): library version: 1.2.1.1129
Click to expand...
Click to collapse

nobody? wow....

http://tinyurl.com/yak5vof
DUDE... LEARN TO SEARCH

Problems Flashing (some) Eclair ROMs

I have a G1, currently running Cyanogen 4.2.12.1 (4.2.13.x kills my battery).
Code:
Phone: White T-Mobile G1
ROM: Cyanogen
SPL: Hykuros Death/Danger
Radio: 2.22.19.26i
Recovery: RA-dream-v1.5.2
SD Card: 4GB
Swap: Enabled
Fastboot screen is as follows:
Code:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.26I
APR 20, 2009, 15:30:43
I have played around with dozens of Donut and Cupcake ROMs, and settled on Cyanogen, because it seemed to be the most stable.
Now, with the Eclair ROMs for the G1 finally hitting the scene (now that they have a camera...props to NCommander), you can only imagine how excited I was to give them a shot.
I have had the 'prerequisites' for a while: Haykuro's SPL, SD card, rooted phone, RA's recovery image, etc...completely prepared for the Eclair releases.
There have been a few Eclair roms that have been released recently, and for some reason, some of them will not load. (specifically the one by manup, and one branched off of his by Herver). It will flash just fine, but when it boots, I get errors such as this:
Code:
I//system/xbin/busybox( 47): Setting up swapspace version 1, size = 128185856
bytes
I//system/xbin/busybox( 47): UUID=32afe93b-1747-4f5a-a3de-5485093a54b7
I//system/xbin/busybox( 47): --- Enabling compcache
I//system/xbin/busybox( 47): Failed to open /dev/block/ramzswap0: No such file
or directory
I//system/xbin/busybox( 47): swapon: can't stat '/dev/block/ramzswap0': No suc
h file or directory
I//system/xbin/busybox( 47): run-parts: /system/etc/init.d/06compcache exited
with code 1
I/logwrapper( 47): /system/xbin/busybox terminated by exit(1)
The full logcat is as follows:
Code:
I//system/xbin/busybox( 47): +++ "This is your world, these are your people. Y
ou can live for yourself today, or help build tomorrow for everyone."
I//system/xbin/busybox( 47): +++ Welcome to Android 2.1 / Manup456_ECLAIR_ERD7
9
I//system/xbin/busybox( 47): e2fsck 1.41.6 (30-May-2009)
I//system/xbin/busybox( 47): ext2fs_check_if_mount: Can't check if filesystem
is mounted due to missing mtab file while determining whether /dev/block/mmcblk0
p2 is mounted.
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: clean, 11/249856 files, 396
09/499300 blocks
I//system/xbin/busybox( 47): cp: cannot stat '/data/app-private/*': No such fi
le or directory
I//system/xbin/busybox( 47): cp: cannot stat '/data/dalvik-cache/*': No such f
ile or directory
I/DEBUG ( 140): debuggerd: Nov 20 2009 10:17:15
I/vold ( 139): Android Volume Daemon version 2.0
D/AKMD ( 148): akmd 1.6.6 START
D/AKMD ( 148): library version: 1.2.1.1129
I/vold ( 139): New MMC card 'SU04G' (serial 2420584359) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa
I/vold ( 139): Disk (blkdev 179:0), 7744512 secs (3781 MB) 3 partitions
I/vold ( 139): New blkdev 179.0 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 3
I/vold ( 139): Partition (blkdev 179:1), 6682977 secs (3263 MB) type 0xc
I/vold ( 139): New blkdev 179.1 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 2
I/vold ( 139): Partition (blkdev 179:2), 998601 secs (487 MB) type 0x83
I/vold ( 139): New blkdev 179.2 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1
I/vold ( 139): Partition (blkdev 179:3), 62871 secs (30 MB) type 0x82
I/vold ( 139): New blkdev 179.3 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0
I/vold ( 139): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:aaaa/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 139): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 139): Volmgr not ready to handle device
D/vold ( 139): Bootstrapping complete
I//system/xbin/busybox( 47): Setting up swapspace version 1, size = 32185856 b
ytes
I//system/xbin/busybox( 47): UUID=89298fcc-2d7e-4440-b962-646ec1c0891d
I//system/xbin/busybox( 47): --- Enabling compcache
I//system/xbin/busybox( 47): Failed to open /dev/block/ramzswap0: No such file
or directory
I//system/xbin/busybox( 47): swapon: can't stat '/dev/block/ramzswap0': No suc
h file or directory
I//system/xbin/busybox( 47): run-parts: /system/etc/init.d/06compcache exited
with code 1
I/logwrapper( 47): /system/xbin/busybox terminated by exit(1)
I have tried partitioning my SDCard with different size swap, fat32, and ext partitions...I have tried using ext2, 3, and 4, all to no avail. I have tried different combinations of wiping (before as well as after loading the rom), reverting back to stock firmware and such, then trying, and nothing seems to work.
As I am sure you all can imagine, I am quite frustrated. Does anyone out there know what is causing these issues, and can perhaps point me in the right direction to rectifying them? Any and all help would be greatly appreciated.
EDIT: One thing I failed to mention previously was that I am able to flash Hero ROMs, and from what I have read, the Hero ROMs require the same setup as the Eclair ROMs (Haykuro SPL, ext/swap, etc). Mentioning that, it brings me to believe even more that there is just one tiny item I am missing, but can not pinpoint it.

I have done more trial and errors with this, to absolutely no avail. I am at a 100% loss...surely someone has some clue as to what is going on?

Hi, was wondering if you are using the same SD card and just trying different partitions, what kind of SD card do you have and do you have more than one SD card, because I would suggest trying a brand new freshly partitioned, with no files but the files you intend to flash, on the card.
Let me know.

halfsight said:
Hi, was wondering if you are using the same SD card and just trying different partitions, what kind of SD card do you have and do you have more than one SD card, because I would suggest trying a brand new freshly partitioned, with no files but the files you intend to flash, on the card.
Let me know.
Click to expand...
Click to collapse
I just dug out one of my older SD cards (2 gig, not HC but oh well, its worth a shot...I'll let you know

halfsight said:
Hi, was wondering if you are using the same SD card and just trying different partitions, what kind of SD card do you have and do you have more than one SD card, because I would suggest trying a brand new freshly partitioned, with no files but the files you intend to flash, on the card.
Let me know.
Click to expand...
Click to collapse
Using your recommendation, halfsight, I tried with a different SD card, and came up with the same results. Good thought, but no avail. Any other ideas? Also, is my SPL the proper one? I am told it is Haykuro's. Info is as follows: (also in the OP)
Code:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.26I
APR 20, 2009, 15:30:43

So I received my new 8 GB Class 6 SD Card in the mail today, and tried that card to flash with and such...still having problems. Any ideas?

Lost recovery data.

As the title states, and the logcat. Seemed to have lost part of my recovery, yet my recovery still works, though Im thinking its not working correctly.
Still a Noob, yes Im going back to donut, little worried about this error, or is it just a fastboot a new recovery.img?
Code:
C:\android-sdk-windows\tools>adb logcat
I//system/xbin/busybox( 47): +++ "Pleased to meet you, we came to drop bombs o
n you!"
I//system/xbin/busybox( 47): +++ Welcome to Android 1.6 / Super D-blk 1.10.4
I//system/xbin/busybox( 47): +++ Starting Shadow's Renice
I//system/xbin/busybox( 47): --- Executing firstboot.sh
I//system/bin/sh( 50): rmmod: delete_module 'ramzswap' failed (errno 2)
I//system/xbin/busybox( 47): +++ Shadow Script: wait 140s for process to start
on first boot
I/logwrapper( 50): /system/bin/sh terminated by exit(0)
I//system/xbin/busybox( 47): --- Checking filesystems
I//system/xbin/busybox( 47): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: clean, 41/249856 files, 504
52/499713 blocks
I//system/xbin/busybox( 47): cp: can't stat '/data/app-private/*': No such fil
e or directory
I//system/xbin/busybox( 47): cp: can't stat '/data/dalvik-cache/*': No such fi
le or directory
I//system/xbin/busybox( 47): +++ Apps-to-SD successfully enabled
I//system/xbin/busybox( 47): +++ Running Media to Data script
I//system/xbin/busybox( 47): mv: can't rename '/system/media': Read-only file
system
I//system/xbin/busybox( 47): link failed File exists
I//system/xbin/busybox( 47): *** media2data: ERROR2 making symlink to /data/me
dia
I//system/xbin/busybox( 47): *** media2data: pls report to dev
I//system/xbin/busybox( 47): mv: can't rename '/system/media-bck': No such fil
e or directory
I/vold ( 166): Android Volume Daemon version 2.0
I/DEBUG ( 167): debuggerd: Mar 3 2010 17:56:48
I/vold ( 166): New MMC card '00000' (serial 1892747644) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001
I/vold ( 166): Disk (blkdev 179:0), 15949824 secs (7788 MB) 3 partitions
I/vold ( 166): New blkdev 179.0 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 3
I/vold ( 166): Partition (blkdev 179:1), 14761718 secs (7207 MB) type 0xc
I/vold ( 166): New blkdev 179.1 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 2
I/vold ( 166): Partition (blkdev 179:2), 1000000 secs (488 MB) type 0x83
I/vold ( 166): New blkdev 179.2 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 1
I/vold ( 166): Partition (blkdev 179:3), 188105 secs (91 MB) type 0x82
I/vold ( 166): New blkdev 179.3 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 0
I/vold ( 166): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:0001/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 166): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 166): Volmgr not ready to handle device
D/vold ( 166): Bootstrapping complete
E/flash_image( 173): error opening /data/recovery.img: No such file or director
y

fastbooted new recovery img. Good to go.

Arabic libraries for HTC Incredible available by Ayman al-Sanad

This was not written by me. It was written by Ayman al-Sanad, username UAE (I believe), who has been working for some time to create workable libraries for so Android devices can properly display Arabic. Oddly there was no thread posted here that I can find so I'm going to go ahead and post it, since I know this is a much-desired feature for many people and at least some people will find it over Google or the like.
As Google has yet to add native support for Right-To-Left languages like Arabic, Persian and Urdu (despite it being the top feature request) Ayman stepped in and created libraries for our usage.
The downloads page is available here: http://ardoid.com/?page_id=5. I'm assuming the libraries will work with any Froyo install. Put the library zip on your SD card, flash it. Reboot will take some time on a black screen.
Big thanks to Ayman for his great work. Evo libraries are also available on his page.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

this is the best news yet!!! i will try right now and report back

Works Perfect !!!!! i can't believe it's finally happening. thank you very much for posting

Dose this works with WebOS (Palm Pre) ?

amjz said:
Dose this works with WebOS (Palm Pre) ?
Click to expand...
Click to collapse
Really? Your in a forum for an ANDROID device, and if that wasn't enough of a hint, the OP says "ANDROID" in the first line.

works perfectly, Thanks for the heads up

Problem with ROM updates
The ZIP files on the ardoid.com site worked perfectly with my phone. This was when Verizon rolled out the Froyo update, and i was able to use the same ZIP files for both a stock ROM as well as a custom one.
But couple weeks ago, Verizon rolled out a minor update to Froyo (2.2.1 I think), and it was also picked up by some developers of custom ROMs. Once I applied any of these updates, I am unable to use the Arabic ZIP file anymore.
Here is what I usually do:
- Use the ROM Manager to download the new ROM.
- Reboot to recovery mode and apply the ROM (done automatically by the ROM Manager).
- Verify the ROM is working correctly.
- Download the Ariabic ZIP file from ardoid.con.
- Reboot to Custom Recovery, and manually apply the Arabic update.
- Reboot the phone one last time.
- The phone remains stuck in the HTC Incredible splash screen.
The only way out is to remove the battery, boot into recovery mode, and do a restore.
I tried this approach with the Virtuous ROM 3.1 and the CyanogenMod 6.1. In both cases, I was trying "froyo_incredible_libs_arabic_android_plus_signed.zip".
I also tried the following ZIP files, and they both failed (didn't expect them to work anyway):
- froyo_stock_generic_signed.zip
- froyo_cm_n1_6_1_1_stable_arabic_android_plus_signed.zip
The questions that I have are:
- Is there a dependency for the ZIP file on the actual system image? Does this mean that there has to be a new ZIP file for the 2.2.1 release?
- Is there another preferred way for applying the ZIP file? (I am using ClockworkMod Recover 2.5.0.5).

Quick update
I would like to add one little detail: using CyanogenMod 6.1, most apps have decent Arabic support by default (for example, tweetdeck or facebook). Unfortunately, the browser doesn't know how to join the Arabic letters correctly (doesn't matter if I am using the stock browser, or Dolphin).

I tried pushing the libwebcore.so and libskia.so files from the Desire HD ZIP from http://ardoid.com/?p=176
I copied the files to the SD card, then copied them over the original files using ADB. After the reboot, the phone got stuck in an endless loop, and here is what I saw repeated when doing "adb logcat":
W/dalvikvm( 1311): ERROR: Unable to find decl for native Landroid/webkit/BrowserFrame;.clearNativeCache ()V
E/JNIHelp ( 1311): RegisterNatives failed for 'android/webkit/BrowserFrame'
E/webcoreglue( 1311): WebFrame registration failed!
W/dalvikvm( 1311): JNI_OnLoad returned bad version (-1) in /system/lib/libwebcore.so 0x0
W/dalvikvm( 1311): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Landroid/webkit/WebViewCore;.<clinit>
E/Zygote ( 1311): Error preloading android.webkit.WebViewCore.
E/Zygote ( 1311): java.lang.ExceptionInInitializerError
E/Zygote ( 1311): at java.lang.Class.classForName(Native Method)
E/Zygote ( 1311): at java.lang.Class.forName(Class.java:235)
E/Zygote ( 1311): at java.lang.Class.forName(Class.java:182)
E/Zygote ( 1311): at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:302)
E/Zygote ( 1311): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:589)
E/Zygote ( 1311): at dalvik.system.NativeStart.main(Native Method)
E/Zygote ( 1311): Caused by: java.lang.UnsatisfiedLinkError: Library webcore not found
E/Zygote ( 1311): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/Zygote ( 1311): at java.lang.System.loadLibrary(System.java:557)
E/Zygote ( 1311): at android.webkit.WebViewCore.<clinit>(WebViewCore.java:61)
E/Zygote ( 1311): ... 6 more
E/Zygote ( 1311): setreuid() failed. errno: 17
D/AndroidRuntime( 1311): Shutting down VM
W/dalvikvm( 1311): threadid=1: thread exiting with uncaught exception (group=0x4001d7f0)
D/skia ( 1311): purging 6K from font cache [1 entries]
I/ServiceManager( 105): service 'media.audio_flinger' died
I/ServiceManager( 105): service 'media.player' died
I/ServiceManager( 105): service 'media.camera' died
I/ServiceManager( 105): service 'media.audio_policy' died
I/ ( 1312): ServiceManager: 0xaec8
I think the root cause is "JNI_OnLoad returned bad version (-1) in /system/lib/libwebcore.so 0x0", but I am not sure what this means, or how to fix it.

Here is another update..
I tried to copy the libwebcore.so and libskia.so directly without the ZIP file. I basically extracted the two library files to a folder "Arabic/New" on my sdcard. The I did the following steps using ADB:
- remount the system mount as rw.
- copy the files from the SD to /system/lib
- change the permission to 644
- reboot
Here is the capture from my CMD console
===========================
C:\my_program_files\Android\android-sdk-windows\platform-tools>adb remount
remount succeeded
C:\my_program_files\Android\android-sdk-windows\platform-tools>adb shell
# su
su
# ls -l /system/lib/libwebcore.so
ls -l /system/lib/libwebcore.so
-rw-r--r-- 1 root root 4859848 Dec 22 19:08 /system/lib/libwebcore.so
# ls -l /system/lib/libskia.so
ls -l /system/lib/libskia.so
-rw-r--r-- 1 root root 1126112 Dec 22 19:08 /system/lib/libskia.so
# cp -f /sdcard/Arabic/New/libwebcore.so /system/lib
cp -f /sdcard/Arabic/New/libwebcore.so /system/lib
# cp -f /sdcard/Arabic/New/libskia.so /system/lib
cp -f /sdcard/Arabic/New/libskia.so /system/lib
# ls -l /system/lib/libwebcore.so
ls -l /system/lib/libwebcore.so
----rwxr-x 1 root root 5118240 Dec 22 19:11 /system/lib/libwebcore.so
# ls -l /system/lib/libskia.so
ls -l /system/lib/libskia.so
----rwxr-x 1 root root 1126552 Dec 22 19:11 /system/lib/libskia.so
# chmod 644 /system/lib/libwebcore.so
chmod 644 /system/lib/libwebcore.so
# chmod 644 /system/lib/libskia.so
chmod 644 /system/lib/libskia.so
# ls -l /system/lib/libwebcore.so
ls -l /system/lib/libwebcore.so
-rw-r--r-- 1 root root 5118240 Dec 22 19:11 /system/lib/libwebcore.so
# ls -l /system/lib/libskia.so
ls -l /system/lib/libskia.so
-rw-r--r-- 1 root root 1126552 Dec 22 19:11 /system/lib/libskia.so
# reboot
reboot
===========================
After the reboot, the phone gets stuck on the white screen
When I look at the log file via "adb logcat", I see it frozen at:
===========================
--------- beginning of /dev/log/main
I/cm ( 73): Welcome to Android 2.2.1 / CyanogenMod-6.1.0-Inc
I/cm ( 74): _
I/cm ( 75): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 76): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 77): )) _))
I/cm ( 78):
I//system/xbin/run-parts( 68): modprobe: chdir(2.6.32.26-invisiblek-aosp): No such file or directory
I//system/xbin/run-parts( 68): run-parts: /system/etc/init.d/04modules exited with code 1
I/mountsd ( 93): Checking filesystems..
I//system/xbin/run-parts( 68): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 68): e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p1
I//system/xbin/run-parts( 68): Filesystem mounted or opened exclusively by another program?
E/mountsd ( 99): Unable to repair filesystem, disabling apps2sd
I/logwrapper( 68): /system/xbin/run-parts terminated by exit(1)
I/DEBUG ( 108): debuggerd: Dec 12 2010 12:46:44
D/AK8973 ( 115): AK8973 daemon 1.3.3 Start
D/AK8973 ( 115): (Library version : 1.2.1.620)
--------- beginning of /dev/log/system
I/Vold ( 106): Vold 2.1 (the revenge) firing up
I/Netd ( 107): Netd 1.0 starting
D/Vold ( 106): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume emmc state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 106): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
===========================
In comparison, when the phone was booting before, here is what the log would look like:
===========================
--------- beginning of /dev/log/main
I/cm ( 73): Welcome to Android 2.2.1 / CyanogenMod-6.1.0-Inc
I/cm ( 74): _
I/cm ( 75): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 76): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 77): )) _))
I/cm ( 78):
I//system/xbin/run-parts( 68): modprobe: chdir(2.6.32.26-invisiblek-aosp): No such file or directory
I//system/xbin/run-parts( 68): run-parts: /system/etc/init.d/04modules exited with code 1
I/mountsd ( 93): Checking filesystems..
I//system/xbin/run-parts( 68): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 68): e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p1
I//system/xbin/run-parts( 68): Filesystem mounted or opened exclusively by another program?
E/mountsd ( 99): Unable to repair filesystem, disabling apps2sd
I/logwrapper( 68): /system/xbin/run-parts terminated by exit(1)
I/DEBUG ( 108): debuggerd: Dec 12 2010 12:46:44
D/AK8973 ( 115): AK8973 daemon 1.3.3 Start
D/AK8973 ( 115): (Library version : 1.2.1.620)
--------- beginning of /dev/log/system
I/Vold ( 106): Vold 2.1 (the revenge) firing up
I/Netd ( 107): Netd 1.0 starting
D/Vold ( 106): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume emmc state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 106): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/AndroidRuntime( 110):
D/AndroidRuntime( 110): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 110): Heap size: -Xmx32m
D/AndroidRuntime( 110): CheckJNI is OFF
D/dalvikvm( 110): creating instr width table
I/ ( 111): ServiceManager: 0xaec8
===========================
Are there any protection mechanisms that is preventing the phone from continuing the boot. If there is an issue with the library file, then I would expect a more specific error message when the library is loaded. However, it seems that the boot sequence is being aborted even before loading libwebcore.so or libskia.so
By the way, I have my phone rooted a long time ago. I think that was using the "unrevoked forever", and I have "SHIP S-OFF" on the main boot screen.

It finally worked!
I downloaded the ZIP file for the Cyanogn Nexus 6.1.1 from http://ardoid.com/?p=21 (I was starting from a CyanogenMod 6.1 for HTC Droid Incredible).
I repeated the same steps as before, but with the following exceptions:
- I copied the "libwebcore.so" file alone (didn't update the libskia.so).
- I rebooted the phone as usual rather than via ADB.
I am not sure which step made the difference, but at least my phone can boot, and most importantly, I can now see proper Arabic text in the browser. Other apps looks fine as well (tweetdeck, reader, etc.). I was even able to enter Arabic text using the browser (in Google search) and everything looked perfect.
I don't know what I might be missing by not updating ibskia.so, but things look really nice already.
Thanks Ayman for helping me out (via Twitter)!!!