Database Info

Help with cooking with core kitchen

Well hardly cooking... All I want to be able to do is to take a base ROM that I like (core 2.0n vanilla or perhaps mfrazz's 1.7) and add the programs that I always install anyway. i figure this will make a hard reset easier if needed and give me a little more memory.
Okay... so I downloaded anchillius's rom kitchen and was able to follow all the directions he provided. I used his core 2.0n, which I have been running for a while but unless I am mistaken installing what I produced would basically be the same thing as installing it directly since it is vanilla anyway, right?
anyway I have a few questions...
1. If I dump a ROM like mfrazz's crossbow 1.7 and install that as is, will the reg tweaks that he made still be there?
2. Is there a readily available step by step on how to add programs. I tried google search and couldn't find anything. I know I am being lazy here but hoping that someone will help a brotha out! that and I am really quite busy at work (but not to busy to not be messing with my phone!)

I'm pretty sure that all the reg changes are the same, I cooked Crossbow 1.7 a little, and nothing changed (that I noticed).
And when u say programs, do u mean by cooking the programs into the ROM with cabs, cuz in this tutorial there is a way on how to install programs by cabs
P.S. While were talking about programs, how do I get the settings for a programs that have to register into a package of my cooked ROM? Is it something in the reg entries on my phone? If so, how do I find out what and how do I get it off of my phone and into the package?

Dummy Question - Selfmaking ROM

Hello,
i'm new here. I come from the Sony Community. I getting in the next 2 Days my new TyTN II. So, now i've got some questions about making a own ROM. I have read so many Pages, but i can't find a easy step by step Howto. I would like to write a German dummy Step by Step HowTo. But i understand how it works... I would like to take some existing ROM's (expl. the ROM from Sleuth), but i would like to run a german version with my own Tools.
First of all, i would like to integrate a Tool like 'Where is my Phone' in actual German ROM File from HTC. See wimp-software.co.uk. So if somebody steal my Phone, i getting the new Phonenumber and the GPS Position Data with this Tool. I think, this Tool is very nice.
The problem with this tool is, when someone make a Hardreset, the Tool will be removed from the PDA. Now, i would like to integrate this Tool to a selfmade ROM.
Ok, i'm understand, that someone can build his own ROM and if he upload his ROM to the Smartphone, my Tool will be destroy. But this is a other problem.
Now, let me beginning. Which are the best steps to create this ROM based on a German ROM Release? I think there are 3 Ways.
1. Way: I install the newest original ROM from HTC to my Mobilephone. Then i install my Application like 'Where is my Phone' and i make my Reg. Tweaks (expl. GPS Camerafunction). After i have install all the good things, i make a Dump from my Mobile and i create a ROM from this Dump.?!
2. I install the newest German ROM Release to my PDA. I make a Dump. And i extract this Dump in my PC, so i can manually add the OEM Packages and Reg. Tweaks.
3. I search in the internet for a German actually ROM (System and Radio ROM). And i manually add the OEM Packages. and Reg. Tweaks.
Can you help me, and tell me, which version is the best for me? My Target is, when a new version from HTC will release, i can easy add my Tools to this ROM. But for this, i have to know, how it works.
With Sony Erricsson, there was some ROM Updates, which have some security issue. So with a ROM Version expl. higher than 1.90 you can't downgrade or make a selfmaking ROM. Is this possible with a HTC device? So i have every time to check, when a new Release goes Public, if i can make downgrades, changes and a selfmaking ROM? Or is this with the HTC device no problem?
So, which Version does exist?
I found the fellowing ROM Function:
SPL -> ???
SPLASH -> this looks like the Bootup Screenfile
RADIO -> this is the GSM Version
SYSTEM -> This looks like the OS
I hope some nice guys can help me, to make my own ROM Release. If it works, i would like a very easy Step by Step Manual in German, with pictures. So that every one can create his own ROM with his own language.

Arabizer Problem

EDITED
just found anoher thread about it soz, pls mod remove this

ahassouna said:
Hi all:
i've been playing around with some ROMS lately; some of us do use the arabizer application which enables you to read and write arabic language and also installs some other minor arabic programs on your device.
i have noticed some issues with some ROMS and need help in solving them, here are my observations:
Diamond Roms till V8 work with arabizer, but ofcourse the keyboard issue doesn't allow you to use the arabic keyboard and you need to install the IM default cab to get it to work.
Death Roms till v4.1 do not work at all; you just get install unsuccessfull even before it starts to install on first block, tried:
1- install from fresh upgrade didn't work
2- install from hard reset did not work.
3- installed net cf 2 and chose as default, did not work
4- installed net cf 3.5 on cf 2 and chose 3.5 as default did not work
5- tried on another handset still doesn't work
6- tried intsall on SD card
iat first i thought it was framework issue but i think it's not, it has to be something in the core which i know nothing about.
tried the ryV5 rom also has the same problem as death roms and would not install.
Can anyone help find a solution to this please as it would be great to get it to work on death and ryV5 roms and should be intresting to know why such application would not work, it might help in near future for other applications.
note: i chose to make a thread about this as i cannot post same question in each ROM thread
Regards,
Hasso
Click to expand...
Click to collapse
I have installed In4mobility software on all of the cooked 6.1 ROMs and it is running fine. The only issue I have is it always defaults to Arabic Keyboard, even when in same session but switching between programs. Other than that it is running great. I would install on Main Mem,,,,, avoid installing on SD card, it will become buggy, and might cause freezing.
Do a search for Informobility software. It is not that expensive.

asfoor said:
I have installed In4mobility software on all of the cooked 6.1 ROMs and it is running fine. The only issue I have is it always defaults to Arabic Keyboard, even when in same session but switching between programs. Other than that it is running great. I would install on Main Mem,,,,, avoid installing on SD card, it will become buggy, and might cause freezing.
Do a search for Informobility software. It is not that expensive.
Click to expand...
Click to collapse
i know it works but not the keyboard, and it crashes the device n regular bases and makes it really slow
imaginet arabizer is always the best choice

Basic questions regarding Android ROMS.

sorry if these have been asked many times before, i've searched but cannot find much about it.
new to Android, coming from a WM for the past 8 years background its all foreign to me.
1) what is "adb" and how does it differ from "RC"'s? I presume RC's are just different build numbers for Android.
2) whats the difference between Haykuro, JF's builds? are any of them cupcake? how can i think about them in terms of Windows Mobile roms?
3) if I install one of the above, will the over the air updates still work? if there is an update to the OS (ie cupcake if the rom isnt) can this be applied at all or will i need to "lose everything" and wipe/flash to the new one?
again sorry for the n00byness.

1) what is "adb" and how does it differ from "RC"'s? I presume RC's are just different build numbers for Android.
adb is a way of telnet'ing from your pc to the phone, this gives you root access.
2) whats the difference between Haykuro, JF's builds? are any of them cupcake? how can i think about them in terms of Windows Mobile roms?
Haykuro and JF's builds are based on the android development branch, they are basicly updates that are based on googles on going improvements to the phones OS. Hayjuro's is based on a port from the upcomming saphire phone. Treat them as different "flavours" like schnaps etc
3) if I install one of the above, will the over the air updates still work? if there is an update to the OS (ie cupcake if the rom isnt) can this be applied at all or will i need to "lose everything" and wipe/flash to the new one?
Current custom roms change the signing keys so OTA updates are not updated onto the phone. You would have to manualy change the rom yourself.
Hope this helps
Imp

thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
also if having to reflash with new version, presumably that would wipe everything? is there a way of backing stuff up or are backups not as bigger deals as they are for a WM based OS.

The ADB build you refer to is essentially a rooted version of the ROM that came with the non-T-mobile branded developers phone.
Regards,
Dave

Impossible said:
adb is a way of telnet'ing from your pc to the phone, this gives you root access.
Click to expand...
Click to collapse
Err no. adb (Android Debug Bridge) is a tool for debugging Android devices both physical and virtual (in an emulator instance). One of its features is to give you interactive shell access, but this has nothing to do with telnet.
Haykuro and JF's builds are based on the android development branch
Click to expand...
Click to collapse
Also wrong. JF's builds are based on officially and unofficially released current branches, not development branches. Also, they are not ground-up rebuilds of the source code in as much as they are just modifications to existing releases to add root and other goodies.
Haykuro's builds appear to be coming from some private source close to HTC. These are not based completely on the open source development branches either.

thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
Rc33 is the current US G1 tmobile rom, Rc9 is the current UK G1 tmobile rom and the ADB1.1 is the developers rom thats carrier free. Think of these are the different between a WM "clean" rom and a carrier rom (such as att)
also if having to reflash with new version, presumably that would wipe everything? is there a way of backing stuff up or are backups not as bigger deals as they are for a WM based OS.
As for destructive flashing... the G1 can do non wipe upgrade but IMO I prefere a clean (wipe before) install. As default the G1 roms store images/music/bookmarks and other customisations to the sd card and if your syncing your contacts with gmail, they will be restored after your rom update, so even with a wipe>install you dont loose much (you loose things like text's, mms's and installed apps)

thefunkygibbon said:
thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
Click to expand...
Click to collapse
What you're referring to is the ADP not ADB.
ADP = Android Dev Phone
ADB = Android Debug Bridge

very helpful guys, thanks. as for over the air updates is that just for OS based stuff or do apps too? (do apps even update themselves?
if you have installed apps to the SD card then wiping the device is even less of a problem i assume

If you install JF's RC33, (or RC9 if you are in Europe), you will have a phone pretty much exactly like the official ROM, except you will have root and multitouch.
If you install ADP 1.1, you will have a dev phone with multitouch and root, but you won't see protected apps.
If you install Haykuro's H build, you will have HTC's "cupcake" phone with lots of added goodies and root.
If you install Haykuro's or the Dudes G build, you will have the Google "cupcake" phone and root.
The "cupcake" builds are very usable and stable, but there are still a few bugs being worked out on them.
With any of the builds, you will also need to use the radio version for that build. (RC 33 and RC 9 are using the radio you probably already have).
The radio can be flashed either before or after, and it won't touch anything on your phone, but it will reboot twice, so don't panic if you do that and see your phone hanging for a few minutes on a different screen after the first reboot.
With all of these versions, you can also put your apps on your SD card with a little more work.
If flashing a different rom, first sync your contacts, then use something like power manager or astro to back up your apps to your SD card, that makes it easier to get everything back. You will definitely want to do a wipe to avoid problems.
It is possible to go back to official roms after updating, but you will lose root, and I don't think you will want to go back. Often times you will get the modified updates here before they are even released officially!

Wow thanks, thats pretty much cleared up my questions!
.
With any of the builds, you will also need to use the radio version for that build. (RC 33 and RC 9 are using the radio you probably already have).
Do the files provided in the threads usually contain the radio's too are they seperate downloads/installs?
With all of these versions, you can also put your apps on your SD card with a little more work.
If flashing a different rom, first sync your contacts, then use something like power manager or astro to back up your apps to your SD card, that makes it easier to get everything back. You will definitely want to do a wipe to avoid problems.
Its something i'm used to with WM phones, but its always a complete ball ache resetting everything up and installing everything.
Is it at all possible to have some kind of OTA updates hosted system set up elsewhere (such as you or me) which could deploy the updates for these "hacked" roms, much in the same way as tmobile etc do?

Do the files provided in the threads usually contain the radio's too are they seperate downloads/installs?
It will say in the threads if you need to install the radio seperately. On most of the newer builds you will need to install it.
Is it at all possible to have some kind of OTA updates hosted system set up elsewhere (such as you or me) which could deploy the updates for these "hacked" roms, much in the same way as tmobile etc do?
The only roms which notify you of updates are the JF ones. There is an app on here that you can install which will let you know if there are updates. So far, it is all do it yourself as far as updating goes.
I don't know if it is possible without a lot of work to have the updates pushed automatically to your phone. At the moment, there are so many roms, some of which are updated more than once per day at times.
I have no idea what pushing them automatically to you phone involves, maybe someone else here does.

Easy Update ?

Hello all,
I've been using android for a while now, running haret, and I get more and more convinced to remove my Windows Mobile to flash android on the NAND.
I'm daily looking at the froyo for vogue thread, but before flashing, I have some question in order to good understand :
- the current froyo thread has about 1 new release per day, how do you guys update the rom without loosing all your parameters and apps ? Or do you reinstall and re-set everything ? I don't want to do this every day ...
- will there be a tutorial, or can somebody put me here some explanations, to install froyo to nan. Cause I don't get everything with the nbh, the install ... what should got where, how to install, what is the utility, in what order to do everything ?
Thanks in advance.

For backup you can use titanium backup (now included in latest froyo) and you can simply follow superjvm guide.

Thanks l1qu1d, I think I'll try it this evening, since my current warm donnut is completly corrupted after trying to update google maps app ...
So, I will be forced to re-install everything ...
Do I also need to install the latest "radio" for the polaris.
And again, could someone just briefly explain me what is this nbh that dzo is alwais updating, I think it has a link with the zImage i'm using for haret, but I'm not sure ... I just would like to understand.

Th nbh file is the flashable version of kernel+bootloader+initrd. It's for nand install but it doesn't contain the whole sistem.