[PATCH][07/15] Spanish hardware keyboard for G1/Dream - G1 Android Development

Ok guys, I was a little tired of copying again and again my slide hardware keyboard layout files for the G1 in every ROM I flashed using terminal.
So I made a little zip file that you can patch right after your favourite ROM directly from recovery.
This patch will work (I've tested it) on every Android version from 1.5 to current 2.2, be it official or cooked ROM (tested it on KingXClick, CM, Cannon at least).
Just copy the attached file to your sd-card root and flash it out from recovery after flashing your ROM-of-choice.
Cheers!!!

Related

When a ROM-based file is overwritten, how does WM access it?

I'm using one of the cooked ROMs in my Touch. It is packed with applications (included in the ROM). I wanted to upgrade one of the prepacked applications to a newer version. When I use Resco Explorer to overwrite one of the apps, I can clearly see that the file was replaced. The newer file is larger in size.
However, when I load that application, the version that is reported is still the older version.
I then removed the new version, and saw that the old version in ROM reverted to the directory.
How does WM handle file access? When I overwrite a file that is in ROM, does WM still somehow read the version that is in ROM? Anyway to change this behavior?
I'm now wondering if I must load the new version to a different/new directory, and change all the short cuts.
Thanks for any help.

ROM Flashing with DMTool

Is anyone here familiar with flashing WM roms using DMTool? I have a device (I can't say which, sorry), that uses this utility for flashing ROMS with a .hex extension (3 files, for radio, OS and ExtRom), and I'm wanting to see if I can update the OS build (comes with WM 6.5 build 21840, which is OLD!).
It's not exactly an uncomplicated process to flash this thing, but I'm fully familiar with it; I just have I've no idea how building the OS .hex file differs from the more common .bin or .nbh files use with EUU/RUU flashing utilities.
Google isn't being very helpful either...

[Q] How to flash latest android version on Polaris

For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
when the system reboots, vibrates twice, I see a text rolls a few lines and stops at
usb_function_register. can somebody help.
attached photo showing screen
thanks
I changed the .nbh file to "polaimg-panel3-240x320-2.6.32-froyo-02-09-10_16"
and now it stops at a different line.see attached photo
Come on guys if someone can help i would really apriciate.
NBH file is use when on the three colored screen.
Seems you doesn't have blank screen, that is work, but you need to flash your radio first, or else the installation will not continue, refer to the guide:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
I did exactly what the guide says. I have installed hard spl and the last radio, but nothing different with the results

[ROM][SD-Boot]CM9 (4.0.4 ICS) Based on munjeni {WIP}

CANCELLED! GOT A NEW PHONE
Tried so many methods , non worked , I'd keep trying until one works , then I could port hTC Aria's CM10 to hTC HD MINI and redo all this again so that we can have 4.1 on our devices. Till then , I'd love it if munjeni or schlund helped me with the process , because it seems that the kernel extracted from boot.img needs modification , and that every OS needs its own initrd , I hope someone can help.
Update:
I found the required file's details , I have the ramdisk , I have the system.ext2 , what I'm missing is the required kernel , 3.0.1 , I just need a download link to that kernel, can't seem to find any.
Hi,
So I recently got into Android Development and so far , everything is good.
What I'm doing is using munjeni's CM9 ROM as a base for me to get the boot.img and the files in the folder /system/.
I tried to use iPlasm's CM9 ROM but I got some extraction problems , which I'll look into later.
I'm also using the initrd found in Shlund's posts , and the original HD Photon (Froyo 2.2).
I compared the two initrds and found out that the Froyo one was smoother and had lots of unnecessary stuff and that the CM7 one is better , but it may freeze , so I'm going to test both for maximum results.
To-Do:​-Ability to Extract zImage from boot.img Done
-Extract system files Done
-Put System Files into system.ext2 Done
-Use shlund's both kernels and see which one works.
-Create a system.ext2
-Extend Data.ext2's size to allow higher storage on higher SD cards.
If you are willing to help on this project...then please help me with these:
I need an empty system.ext2 in ext3 format (so I can put the system files inside).
Or I need someone to be able to empty the system.ext2 that I have which I got from the Froyo 2.2.
Problems :​Currently I'm facing these problems that may get fixed later:
Cannot delete bin and xbin from system.ext2 , which leads to files to be read when they are not needed.
No empty system.ext2 file present.
Cannot Modify the initrd to increase the space , looking forward to use this code:
When using the kernel from munjeni (extracted) all what happens is G1 logo appearing and nothing else.
Bases :​
zImage from mujeni's CM9 from boot.img
iPlasm's boot.img
initrd from either schlund's CM7.2 or shlund's Froyo 2.2
/system/ from munjeni's CM9
HARET_PHOTON7227.exe from PhotonAndroid Developement
Startup File from schlund's Startup.
All help appreciated
I found a 200mb system.ext2 , however , whenever i put files in it , the next time I mount it I loose everything I put inside , but everything deleted remains deleted. -_-
Glad to see you're trying to do some,
You should not try cm7 kernel with CM9, You're trying to make CM9 SDcard version so forget about cm7 kernel (you may do only for comparing)
please, try the munjeni's boot.img from (update 04.Jun. for rom 24.May.2012) or mine, because the munjeni's rom (24.May.2012) boot.img is older kernel. the new one includes bluetooth fix (NOT Handset Car).
what i see in system.ext2 i don't think you should empty or even use them, it should be writing in command (terminal) that will create those files into EXT2 file.
here is an example: http://forum.xda-developers.com/showthread.php?t=1055923
You can collect more informations in HTC HD2 forums which include SDCard versions,
Have fun,
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
thethiny said:
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
Click to expand...
Click to collapse
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
iPlasm said:
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
Click to expand...
Click to collapse
I found the problem , I'm using a new system.ext2 created by me , I put the /system/ files of yours inside , then I took the kernel from your rom , and then I used schlund's initrd (because I compared it to the original initrd and found that the only differences were in :
1-splash screen
2-mounting the sd or mounting the ext/sd
3-order of command execution)
so I found out the Cotulla (the original creator of the init inside the initrd.gz ) has put a G1 .T...Mobile splash screen , and when the kernel is loaded , it is loading it as rom , not as sd boot so it launches the splash screen instead of launching the android bootloader , I'll have a look and see and luckily munjeni will reply to the pm I sent him (he helped me with creating the system.ext2 and the initrd)
thethiny said:
Hi,
may you help me with something?
I have a ramdisk (initrd.gz)
and a kernel (boot.img)
and an zImage (kernel main)
however , I cannot seem to be able to extract the zImage , but I did extract the boot.img and the initrd .
In order for me to make it SD Boot , I should allow SD boot from zImage , but I can't open , do you think you can do that for me?
Click to expand...
Click to collapse
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
iPlasm said:
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
Click to expand...
Click to collapse
ok I already did that , but the zImage extracted from CM7 , doesn't match the zImage from CM7 SD Boot (same ROM , same Dev , diff size).
So I wanna extract the zImage so I can modify the Boot section to SD Boot.
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
iPlasm said:
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
Click to expand...
Click to collapse
Yes I tried , also I'm a Windows User , so I use Cygwin , and none of the commands above worked! I tried using Ubunty 12 and I get error at line 12

Rom Customisation & Modification (PLEASE HELP!)

Hi Guys
I need some basic help/understanding about Android ROM modification.
In particular for an Android MX TV Box - but the questions is generic and applies to any ROM I guess.
The Rom im flashing has the following files (and works perfectly):
factory_update_param.aml
hd18d_mx4.zip
recovery.img
I am able to successfully restore my box with this image (so I know that the image is working fine).
Within the hd18d_mx4.zip there is:
Directotories: data, META-INF, recovery, system
files: boot.img, bootloaded.img, logo.img
I tried to do a very basic step of deleting a single system.apk file from the system/app folder (no other changes) and I am unable to flash this firmware.
Any ides - what am i doing wrong?? It seems like i cant make any modifications to the zip file or there are problems.
I tried using dsixda Rom kitchen, and even if put rom in working directory, and then immediately
Please help - this is driving me mad!! Aaarrghghg

Categories

Resources