Related
after I've edit the rom of Wm6 , it'll auto off at slashscreen after flash
please correct me if anything wrong ..
here's my steps :
HTC64 Extended ROM Tool , decode the rom and then...
prepare_imgfs.exe nk.fat -nosplit
viewimgfs imgfs_raw_data.bin
BuildImgfs
set _FLATRELEASEDIR=.
rgucomp -o dump\default.hv -nologo > default.rgu
rgucomp -o dump\user.hv -nologo > user.hv
then I've added other wince.nls and fonts in "dump" directory .
and edit default.rgu , user.hv by ultraedit . added "REGEDIT4" at the first line , added some lines on initflashfiles.dat.
then repack :
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\default.hv
copy boot.hv dump\default.hv
attrib -s -r -h dump\user.hv
copy user.hv dump\user.hv
BuildImgfs
make_imgfs nk.fat -nosplit
use HTC64 Extended ROM Tool encode again . and flash .
any problems in these step ? Please correct me , Thanks alot !!
Building roms
Hi,
Ha... here you are,
will try this tomorrow.
Leo
Leies said:
after I've edit the rom of Wm6 , it'll auto off at slashscreen after flash
please correct me if anything wrong ..
here's my steps :
HTC64 Extended ROM Tool , decode the rom and then...
prepare_imgfs.exe nk.fat -nosplit
viewimgfs imgfs_raw_data.bin
BuildImgfs
set _FLATRELEASEDIR=.
rgucomp -o dump\default.hv -nologo > default.rgu
rgucomp -o dump\user.hv -nologo > user.hv
then I've added other wince.nls and fonts in "dump" directory .
and edit default.rgu , user.hv by ultraedit . added "REGEDIT4" at the first line , added some lines on initflashfiles.dat.
then repack :
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\default.hv
copy boot.hv dump\default.hv
attrib -s -r -h dump\user.hv
copy user.hv dump\user.hv
BuildImgfs
make_imgfs nk.fat -nosplit
use HTC64 Extended ROM Tool encode again . and flash .
any problems in these step ? Please correct me , Thanks alot !!
Click to expand...
Click to collapse
I'm building my own WM6 ROMS. The problem that I found is to change the registry. What tools I need to do edit "default.hv" & "user.hv" or modify the registry.
the base tool is rgucomp from m$. Most kitchens build a shell around it because its so quirky tho.
I already download rgucomp.exe, but I need tutorial on how to use it. Is it available somewhere?
It's here but spotty. Mamaich posted about it when he originally built his imgfs tools.
Sleuth255 said:
It's here but spotty. Mamaich posted about it when he originally built his imgfs tools.
Click to expand...
Click to collapse
Thanks,
By the way I manage to do it. For those interested the command like this,
For dumping default.hv & user.hv
Code:
set _FLATRELEASEDIR=.
rgucomp -nologo -o default.hv > default.reg
Edit the default.reg file as you wish & save it as boot.rgu with unicode encoding
Build back the registry hive with this command
Code:
set _FLATRELEASEDIR=.
rgucomp -b
File call boot.hv is created. Rename it to default.hv. Viola you are done
Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.
fireburned said:
Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.
Click to expand...
Click to collapse
have u try msflshtool
Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.
fireburned said:
Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.
Click to expand...
Click to collapse
usually it is in part0 or part1 ... use xipport to see which have the boot.hv & boot.rgu ... u only need those files ... around 20-40Kb files
Then u can put it in ROM folder in ur Kitchen
Thank you cruzzmz for your replies
I used XIPort to extract Windows.nb.part0/Windows.nb.part1.
I obtain this :
Code:
Windows.nb.part0
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
boot.hv
boot.hv.imageinfo.txt
ceconfig.h
ceconfig.h.imageinfo.txt
default.hv
default.hv.imageinfo.txt
initobj.dat
initobj.dat.imageinfo.txt
user.hv
user.hv.imageinfo.txt
\MODULES
busenum.dll
cecompr.dll
ceddk.dll
cereg.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
imgfs.dll
mmtimer.dll
mspart.dll
nk.exe
OMAP850_SDHC.dll
ONDisk.dll
packageinfoapi.dll
pm.dll
ramdisk.dll
rawfs.dll
regenum.dll
romfilter.dll
sdbus.dll
sdmemory.dll
serial.dll
uldrui.dll
updateapp.exe
busenum.dll.txt
cecompr.dll.txt
ceddk.dll.txt
cereg.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
imgfs.dll.txt
mmtimer.dll.txt
mspart.dll.txt
nk.exe.txt
OMAP850_SDHC.dll.txt
ONDisk.dll.txt
packageinfoapi.dll.txt
pm.dll.txt
ramdisk.dll.txt
rawfs.dll.txt
regenum.dll.txt
romfilter.dll.txt
sdbus.dll.txt
sdmemory.dll.txt
serial.dll.txt
uldrui.dll.txt
updateapp.exe.txt
Windows.nb.part1
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm.imageinfo.txt
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm.imageinfo.txt
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu.imageinfo.txt
boot.hv
boot.hv.imageinfo.txt
boot.rgu
boot.rgu.imageinfo.txt
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm.imageinfo.txt
initflashfiles.dat
initflashfiles.dat.imageinfo.txt
mxip_initdb.vol
mxip_initdb.vol.imageinfo.txt
mxip_lang.vol
mxip_lang.vol.imageinfo.txt
wince.nls
wince.nls.imageinfo.txt
\MODULES
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
busenum.dll.txt
cachefilt.dll.txt
cecompr.dll.txt
ceddk.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
fsreplxfilt.dll.txt
hd.dll.txt
HtcFsdspy.dll.txt
imgfs.dll.txt
mspart.dll.txt
nk.exe.txt
ONDisk.dll.txt
osaxst0.dll.txt
pm.dll.txt
ps2fatutil.dll.txt
regenum.dll.txt
The good files are in Windows.nb.part1 ?
Next step : copy boot.hv/boot.rgu in ROM/XIP folder ?
Thank you very much !
And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?
fireburned said:
And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?
Click to expand...
Click to collapse
dont think it is a problem as long as when u do buildOS u dont get any error (hint: if there is error check the temp folder open log.txt)
I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.
Help me please... I tried... But i'm blocked...
fireburned said:
I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.
Click to expand...
Click to collapse
I dont seem to hv that file on my ROM\XIP folder, maybe u can try deleting all files inside XIP except for boot.hv & boot.rgu
then try buildOS again
BTW what is the size of both files?
I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?
fireburned said:
I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?
Click to expand...
Click to collapse
dunno if this can help
If you did something like the following sequence:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
Then the initflashfiles.dat should definitely be in the 'dump' folder.
Did you remember the -nosplit option for prepare_imgfs.exe?
Edit: Just a thought. The initflashfiles.dat is hidden plus the .dat extension is normally used by system files, so could it be something so simple as the fact that your explorer is not showing hidden and/or system files?
Click to expand...
Click to collapse
seems like the initflashfiles.dat is in the dump folder after u do a viewimgfs
You can put initflashfile.dat inside imgfs (for example OEM/OEM_LANG_XXX) and delete it from XIP.
Buildos.exe from Bepe search initflashfiles.dat insiede IMGFS:
cruzzmz : I tried your solution
Code:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
But, in dump folder, i haven't initflashfiles.dat
I tested several solutions, and each time, initflashfiles.dat is in my XIP folder.
cicciocant : I tried to put initflashfiles.dat in dump folder, and run PKGTool, but file is not copy to OEM_Lang_XXXX folder (missing dsm ???), and BuildOS fails, with same error.
I tested to put initflashfiles.dat in OEM_Lang_XXXX manualy, and i have an other error when i try to BuildOS : "initflashfiles.dat is a directory not a file! copying the File!!!"
In my XIP folder, i have :
Code:
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
boot.hv
boot.rgu
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
initflashfiles.dat
mxip_initdb.vol
mxip_lang.vol
wince.nls
An idea ?
And thanks for your help.
seems like my rom that i cooked doesnt have initflashfiles.dat in the XIP folder.
Maybe you can try ask around in hypercore kitchen thread
Thanks cruzzmz, i posted my question.
Hi there,
as anounced her is my first Umbrella Themed Android Rom. It is a mixture of several vogue, dream and saphire roms.
V1+V2:
Here the things i added:
Some apps:
-proPaint Camera (fully working)
-RockOn
-LastFM app
-Custom boot animation and sound (just on first boot so loud)
-Umbrella Themed (more to come, if some graphical advanced people could help me i would be pleased)
-Latest Libs
-Shazaam
-New default ringtone and notification tone
-Kaiser wifi fix
V3:
-new base
-added homeswitcher
-added normal homescreen
-some more fixes and tweaks
Working:
Kaiser (tested by me:
-Data
-WiFi
-Camera (proPaint)
-Audio
-Phone (very responsive)
Vogue: Please tell me and i will add infos!!!
-Data ??
-WiFi ??
-Camera (proPaint) ??
-Audio ??
-Phone (very responsive) ??
I'm no developer i only wanted to give something back to this great community. Thanks goes to: dzo, Zenulator, mssmission, enatefox, pmos, vilord, craig0r, and all the others i forget taht make android on our devices possible
Download Link: Umbrella Corporation v2, with working media ROM
Download Link: Umbrella Corporation v3, Sense od Default Homescreen, fixed one
OPTIONAL:
Here my startup.txt (Change for your carrier to get data!!!)
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=internet.t-mobile ppp.username=tm ppp.password=tm pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Click to expand...
Click to collapse
and my custom.hero.conf: !!just works if your card is partitioned!!
Klick
Have fun!!!!
Changelog:
v1: initial release
v2: fixed no media problem
wow! sounds really great!
any drawbacks?
could you post some screenshots please?
and maybe a small step by step tutorial how to install? (or point me to an existing one - i am a total android noob!)
thank you for sharing!
br,krz
Thanks
Very Very Very nice surprise! Thanksssssssssssssssssss
Just copy all the files to the root of your sd card and download the basefiles from http://code.google.com/p/vogue-hero/downloads/detail?name=basefiles-20091009.zip&can=2&q= (cause i forget to add the conf files from the conf folder) just copy the conf folder from the basefiles zip to the root of your sd card, cause rootfs an zimage from my archive are newer.
Copy the startup.txt fom first post and create a file named startup.txt on your sd card. Then launch Haret.
Enjoy...
Thanx, for all you effort....
custom.hero.conf: !!just works if your card is partitioned!!
What partitions do I have to create for best performance?
oh my god i cant belive this got it running, the startup scared the crap outta me.we are not worthy, my sincere thanks to all the people working on porting android to kaiser, without u none of this would be possible. Thank you JeckyllHavok for maing this awesome design and rom
I got the best performance when i had a secon partition as ext2 and a third partition with linux-swap. Make the first around 100MB and the second one around 80MB
JeckyllHavok, when its all booted up, is it just a blank space with top bar info, or have i done summat wrong
Give it some time first start can take a while. Was the boot animation coming?
i got to the point where if i pressed green answer button, the phone pad would appear, and left and right soft keys control volume, but nothin on home screen
Did the startup setup apears? (I'm testing a new build with working media)
im new to this so bare with me, i get the loading system, with umbrella corp logo, when does this setup come
oh its come up now
Try if a restart helps. For me the black screen apears for 1-2 minutes then it continues Umbrella Boot ani-->Umbrella Logo-->UmbrellaLoading Screen-->BlackScreen-->Setup
just intalled this rom on my kaiser, works good except the LCD colours look a bit strange, its the first rom I get the colours messed up
any solution?
its working, its alive, its alive. Thanx man for all da help
just intalled this rom on my kaiser, works good except the LCD colours look a bit strange, its the first rom I get the colours messed up
any solution?
Click to expand...
Click to collapse
Can you post your default.txt
JeckyllHavok said:
Can you post your default.txt
Click to expand...
Click to collapse
I'v used the one on te first post, just changed the APN
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=internet ppp.username=tm ppp.password= pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Click to expand...
Click to collapse
board-htckaiser.panel_type=1
Try to change this to 2 or 3 and look if it helps
erm you was talkin abt partitioning sd card to give better performance could you give me some more info and instructions on what to do, Thank you
changed it to 2, it works like a charm
Thanks a lot!
The only thing i dot like is the startup sound, animation, but that is the less
Hi Gentlemen,
I'm new to this forum, and recently installed Android on my TP2 (which I've been using for couple of years with WM6 then Win7).
My XD Android (FRX07) works fine [BTW: congrats & thanks to the great developers !!]
Physical keyboard on OS is "qwerty" though (ie, US/UK based), whereas it's "azerty" on my hardware (ie, French).
Does anybody know how to change this ? Thanks !
I went through the parameters and changing language to French didn't work out (must be the digital keyboard, not the physical one), nor did I find any solution on the Forum.
So, Thanks in advance...
Did you try changing the keyboard setting in the start up text?
Browse your SD Card and find startup.txt file
Open it with your favorite text editor
You will find this line looking like this (depending to your model):
[ set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod100_uk" ]
Just replace by :
[ set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod100_fr" ]
without the hooks of course