Hi everybody!
I’ve surfed this forum many times, trying to find topics, where I could get info, such.
What are Radio Rom, Extended Rom, and Extracted Rom?
What they include inside?
To whom belongs files nk.nbf and ms.nbf?
What gives new version, when you do update?
What is Bluetooth version 1.0 ----2.0, is it version of chipset, or is it version of software?
Can you change this version of bluetooth, and a lot of questions, where I can’t find any answers over Word!!!
I have seen many times, instead answers just redirect to old topics.
Where do I know, may be from that time this question about WM5.0 is WORK?
I am myself seen QTEC2020i(XDAIIi) complete with mobile 5.0.
Please, answer how to Search(make sentence) and where(index), or answer to one of the many questions above?
Hi YARMen!
I know the search can be problematic if you do not enter the right keywords and even then it doesn't cover the WiKi which is where you should look for most of the answers.
Here are some quick answers for you:
Radio ROM - The drivers and stuff that control the phone WiFi and BT (all the radio) this is separate from the OS and can be updated by it self.
Extended ROM is a part of the devices FLASH that is hidden (can be unhidden with reg hacks and used to store files so they won't be deleted during hard reset). It is used to store provider customization cabs that install automatically after you hard reset the device.
Extracted ROM is a ROM image extracted from a device. Basically you take all the OS, drivers and stuff and save them to a file on the PC for later use.
To whom belongs files nk.nbf and ms.nbf?
What gives new version, when you do update?
Click to expand...
Click to collapse
Not exactly sure what you mean here. the mbf files are ROM images, and updates are produced by the OEMs. (Original Equipment Manufacturers)
Not sure about BT, but I think it's hardware.
That's it.
radio rom also called radio stack
have the software which also control the gsm/umts phone software
Thank you very much for answers!
Not exactly sure what you mean here. the mbf files are ROM images, and updates are produced by the OEMs. (Original Equipment Manufacturers)
Click to expand...
Click to collapse
When I updated my PDA I used ROM which consisted files ms_.nbf, nk.nbf, and radio_.nbf. I think it get 1, 2, 3 steps to install the softwere.
You can upgrade all of them or just one, moving files from folder, where installer starts.
So I know now what is radio_.nbf, it is radio ROM about that you have told me. Question is what the rest?
And please, if you know, what about version Bluetooth below?
Ok, well nk.nbf is 'main' ROM. It's the OS and hardware drivers for touch screen, LCD etc.
I am not sure but that leaves ms_.nbf to be the extended ROM. I could be wrong though.
Thank you, Levenum.
Good job!
There is a solution of search.
If you want to find exact words or sentences into this forum, or another wiki sites go to Google.com or another search server, put your words in extended search and choose domen(write down) 'forum.xda-developers.com' and etc.
To prevent new users asking the same questions again and again, i decided to write this little FAQ and introduction about ROM flashing.
To all of you who are new to ROM flashing: Don't mind to ask, we all will help you if possible, but you should understood that it is annoying when the same question is asked 20 times a week. So please first search, then ask. Thank you.
If someone finds an error please do not post it, just send me a pm and I will correct it. Additional FAQ entries will be added regulary. If someone likes me to add a question, please send the question and the answer to me via PM and i will add it asap.
Thank you to the whole community, because without all of your information, this FAQ could not be possible.
If you are new to ROM flashing, please read this thread. It will give you information about your device and a short introduction on how to flash another ROM to your phone.
Below you will find the ROM flashing FAQ and the Introduction to ROM flashing.
Please feel free to add links to this thread to your signature using the following code:
[b][url=http://forum.xda-developers.com/showthread.php?p=1790046#post1790043]ROM flashing FAQ[/url][/b]
[b][url=http://forum.xda-developers.com/showthread.php?p=1790046#post1790046]Introduction to ROM flashing[/url][/b]
Click to expand...
Click to collapse
ROM flashing FAQ
ROM flashing FAQ:
Q: What is a ROM?
A: A ROM contains the operating system and often additional software which can be “installed” to your mobile device. Most ROM’s provided by the chefs (people who create cutomized ROM’s) just contain the operating system and additional applications. Shipping ROM’s (ROM’s provided by the manufacturer or official providers) also contain a Radio ROM and a bootloader.
Please notice: A ROM can ONLY be flashed to a device it is made for.
Q: What is a bootloader?
A: A bootloader contains information about your device. It is quite similar to a computer’s BIOS. Official bootloader also have a security option called CID (Carrier-ID) which allows you just to install ROM’s from the provider of your phone. So, if you want to flash another ROM, you first have to turn off this security option by “CID-unlocking” your device. Check the flashing instructions below on how to do this.
Q: What is a Radio ROM?
A: The Radio ROM contains the drivers for the communication devices of your phone. Some ROM’s need one or more specific Radio ROM’s to work properly. Usually the chef, who created the ROM recommends a Radio ROM. But don’t mind, if your Radio Rom does not match, you can always flash another without needing to flash the ROM containing the Operating System (OS) again.
You can check the version of your Radio ROM when you click Start > Settings > System > Device Information or booting your device (there will appear three lines of red text. The Radio ROM version is the number after the R:.
You can download Radio ROM's at the xda-developers FTP-Server in the Uploads/Kaiser/Radio-Folder. Username and password are both 'xda'. To install it, download, extract and execute it. Then follow the instructions on your screen. Flashing a Radio does not delete any files on your device's ROM.
To choose the perfect Radio ROM for you check this thread.
Q: What means CID(-unlock)?
A: All known providers add a Carrier ID to their devices. This CID is added to prevent a device being flashed with a ROM which is not from the provider and/or not designed for your device. Be sure to brick your Kaiser, if you try to flash a ROM designed for a Wizard.
To flash other ROM's, you have to unlock the CID. If you flash another ROM on a CID-locked device, the new ROM will not work properly.
Q: What means SIM-Unlock?
A: Lots of providers want to bind their customers. So they add a SIM-Lock to their devices with only allows to use SIM-Cards using their networks. If you want to use a SIM-Card from another provider, you need to SIM-unlock your device. This can be done by contacting the phone's provider (paid & sometimes free), using a service like www.imei-check.com, or using Jockyw2001's Kaiser SIM Unlocker.
Q: Can I brick my phone by flashing a ROM?
A: To be true… YES. But if you follow all instructions, it is quite implausible that your device bricks.
Q: Does flashing affect the warranty of my device?
A: Yes, but, as long as your device can be flashed again, you will find some help at jcespi2005's thread where you can find dumped original ROMs.
Q: What can I do, if i gain problems with the ROM i flashed to my device?
A: First of all you should inform the creator by posting in the ROM's thread if the problem is not described yet. Then you should wait for an update/fix or, if the issue is a showstopper for you, try another ROM.
Q: Which is the best/fastest/... ROM?
A: Nobody can answer you this properly. There are nearly daily new ROM's here and everybody has different demands to a ROM. If you want to know, which fits best for you, read the ROM description and try the ROM('s). Only you can decide, which ROM is the best (for you).
Q: I own an AT&T Tilt. After flashing another ROM, my hardkeyboard does not work properly.
A: AT&T uses another keyboard layout than HTC. To fix this, install the tilt keyboard fix.cab. You can download it at Dutty's Kaiser CAB Collection.
Q: What is the difference between a hardreset and a softreset?
A: A softreset reboots your device. A hardreset sets all settings back to the ROM's defaults. All of your data, settings and additionally installed programs will be deleted.
Q: What are *.CAB-files and/or how do i use them?
A: Cab-files for WINCE-Devices are different to the files you may have seen (e.g. on your Windows Installation CD). They do not only contain files but also installation information similar like a MSI package. To install them, just copy the *.cab to your Mobile Device and run it from there. Most shipped ROMs delete cab-files after executing, most cooked do not. To be sure, check the registry. If HKLM\Software\apps\Microsoft Application Installer\nDynamicDelete = 0 (DWORD decimal), cab-Files will not be deleted after execution.
Q: I have questions which are not described in this FAQ. What shall i do?
A: First of all search the forum and the wiki (http://wiki.xda-developers.com). Maybe the question has been already answered. If you don't find an answer, create a new thread. As i know from experience, the community will always try to help you as soon as possible.
Introduction to ROM flashing
Introduction to ROM flashing
These are the steps on how to flash your device the first time:
1: CID-unlock your device by following the instructions at pof's HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free)-thread
This needs to be done to flash a ROM to your device which is not created from your provider (or HTC if you own a device with HTC branding).
Additionally you may check persianowns Kaiser HardSPL Walkthrough Video.
If you are running in a white screen running HardSPL, please read this thread.
2: Search this forum for the ROM, you like to flash. Then download and, if needed, extract it.
3. Check, if your Radio-ROM matches the new ROM. If you don't find any information in the ROM's thread don't mind. You can update your Radio ROM later if you gain any problems.
4. Make sure, your devices battery status is NOT LESS than 50%.
5. Connect your device to your computer and wait until activesync/Windows Mobile Device Center recognizes it
6. Last chance to synchronize and/or backup files. All files and databases will be deleted after performing the next step!
(Optional: If you want to save your text messages and/or eMails, use a tool like DotFred's PIM Backup.)
7. Execute the .exe file you downloaded with the ROM.
8. Follow the instructions and DO NOT disconnect your device until flashing is finished.
9. Disconnect your device from your computer.
10. You need to delete the old activesync/Windows Mobile Device Center partnership, because it thinks, your device is not the same as before... and it is right ^^. Deleting an old partnership is only possible, if the device is not connected.
(Optional) If you want to change the name of your device, do that now by clicking Start > Settings > System > About > Device ID. Enter the new name of your device and click on Ok.
11. Connect your device to your computer, create a new partnership and synchronize. Then configure your device to your needs and if needed install additional software.
Congratulations! You succeed flashing your device!
Great FAQ....simple, concise, and informative
Well done
Excellent post bmueller77!
This should clear up a bunch of the questions that are asked.
thanks for that
its hard to find some basic info on here like this, so can we please sticky
Really Good Thank you...
Can you please make a general version of it and put it in general wiki so that it can benefit all not just kaiser guys
Although I am more interested in HTC Elf Touch version []
you could add my video to it http://www.youtube.com/watch?v=UaCt5pUn6iI
shows how to hardspl
verysmartncool said:
Really Good Thank you...
Can you please make a general version of it and put it in general wiki so that it can benefit all not just kaiser guys
Although I am more interested in HTC Elf Touch version []
Click to expand...
Click to collapse
Let's see. I am already working on a more general FAQ version including info on Windows Mobile but, to be honest, a general flashing introduction would be much more complicated and i want to make it as easy as possible for newbies.
I think it would be better, if someone grabs this thing and would edit it for another device to keep it concise. If anyone is interested, just ask me via PM and i'll send you the whole including vbCode.
persiansown said:
you could add my video to it http://www.youtube.com/watch?v=UaCt5pUn6iI
shows how to hardspl
Click to expand...
Click to collapse
Got it. Thank you.
I have made this thread a sticky upon request.
I feel that this info should be ported to the wiki so that it can be found and edited by all.
At the momnet we have FAR to many sticky's in this section which makes finding anything hard to say the least.
Have a look at the BA section (in my signature) to see what I mean.
Aright, will add a general version to the wiki at the weekend.
Thank You but still have a question
Hi, I just got my HTC TyTn 2 as a present from my dad he got it from orange and got it sim unlocked for me. But I don't like it because Orange has their crappy stuff on it I wont the original stuff from HTC on it like HTC Home etc. I've got my phones detail in my signature can some one plz help i jus want to know if i can use it on my rom n radio version. Thanks.
thx
Super! Thank you!
this thread is awesome...it really help a newbie like me
the wiki is also very helpful
keep up the good work
I've been flashing ROMs for a long time. There is one thing I don't know. Does anyone know what is the reason behind stopping flashing RadioROMs at 95%? Whatever RadioROM I want to flash to my Vario III (keeping the standard T-Mobile ROM) it stops. In the RadioROM thread, there were several cases like mine. Can it be that for being able to flash another RadioROM you have to flash a custom ROM like Dutty or Schaps before flashing the Radio? I cannot recall such problems with Hermes.
Thanks for the guide. Also am not new to this I haven't done this in a while. ROM Flash went without a hitch. Keep up the good work.
haamedullah said:
Hi, I just got my HTC TyTn 2 as a present from my dad he got it from orange and got it sim unlocked for me. But I don't like it because Orange has their crappy stuff on it I wont the original stuff from HTC on it like HTC Home etc. I've got my phones detail in my signature can some one plz help i jus want to know if i can use it on my rom n radio version. Thanks.
Click to expand...
Click to collapse
So long as your phone is SIM unlocked as in you can use any sim card in it then you flash it exactly the same as described in this thread. I flashed mine no problems. Does that answer your question or are you just wanting the home screen without flashing? If so Im not sure if thats possible, I heard some people say that you can enable it on orange phones but I flashed mine before I ever tried it.
Excellent FAQ!
Now i can get my hands dirty with that so called "ROM flashing" .
noobie question, but how do i install a cab file? thanks
So i started building this rom for my AT&T Tilt a few days ago and i have run into a few issues i was wondering if anyone else has encounterd them and knows a fix. Ive been doing alot of searching and googleing and haven't found alot of answers.
1st i started out using alex's 3.03 winmo 6.1 htc rom. I had issues with the camera not working with radio 1.65 so i flashed to radio 1.64. But i was still having a problem with the device not doing a soft reset unless i physically push the button. So i searched around and my findings lead me to believe there is no fix for this so i need to use version 3.02. Then i went and got version 3.02 and when i rebuilt the rom everything seemed fine but there is no links to the hardware buttons in the settings applet for buttons. Is this a common issue i cant find anything about this anywhere??!
2nd when building packages sometimes they dont work... Ive built a few packages and they all turn out fine Ive run into some problems with the shortcuts but editing the initflash by hand fixes it everytime. Some packages ive made though just dont work, they install fine but when i run the app i get a component missing error, the weird thing is the cabs i used to intall these packages have no issues what so ever, an example would be frNotepad 1.2 if anyone has ever tried to turn that into a package.
Last question i have is how do you set up a defualt theme I noticed the htc theme package in alexs oem packs sets its self up as the defualt theme i looked through it did a search on cusTSK didnt find much info. So i tried to rename my theme to htc.tsk and just replace the theme file in the htc theme package but that just screwed the whole theme up.
1st i started out using alex's 3.03 winmo 6.1 htc rom. I had issues with the camera not working with radio 1.65 so i flashed to radio 1.64. But i was still having a problem with the device not doing a soft reset unless i physically push the button. So i searched around and my findings lead me to believe there is no fix for this so i need to use version 3.02. Then i went and got version 3.02 and when i rebuilt the rom everything seemed fine but there is no links to the hardware buttons in the settings applet for buttons. Is this a common issue i cant find anything about this anywhere??!
Click to expand...
Click to collapse
Look for the file 47d2a96e-f0dd-40e1-8f5b-a8cdc083a165.rgu and in it is the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Keys. This contains which application the hardware button will launch when pressed.
For the reset issue, 3.03 ROM have some problems. Upgrade to a more newer ROM. I created my own LITE ROM Folder similar to Alex. You can check my post at http://forum.xda-developers.com/showthread.php?t=399733. It is based on 3.28 official ROM.
2nd when building packages sometimes they dont work... Ive built a few packages and they all turn out fine Ive run into some problems with the shortcuts but editing the initflash by hand fixes it everytime. Some packages ive made though just dont work, they install fine but when i run the app i get a component missing error, the weird thing is the cabs i used to intall these packages have no issues what so ever, an example would be frNotepad 1.2 if anyone has ever tried to turn that into a package.
Click to expand...
Click to collapse
When building packages, double check the initflashfiles.txt to make sure the shortcuts are correct. For the component missing error, CAB and ROM Packages is not entire identical. In CAB, you can create the shortcuts without the need for the included LNK in the packages and initflashfiles.txt, but for ROM Packages, you need both files. So basically if the CAB works, it doesn't mean the ROM Package will also work.
Hi,
I had a look over the recovery code in the official android source, and in the cyanogen sources. And one point remains obscure to me.
It seems that in both cases, the flashing program verifies the signature of the zip archive using a public key located in /res/keys.
I use cyanogenmod and it turns out that when I reboot in recovery mode and open a console, there is no /res/keys file.
Can someone explain me where is the trick here ?
One more question. I guess that if there is a public key in the device, there must be a private key used to sign the archives. (Probably kept secret by the carriers to sign their own updates). But I read somewhere that there is some apps available to sign theses updates (something called SignAPK or so). So I guess that either the private key has leaked from the carriers, or that something in the rooting process of the G1 changed the key pair on my device.
Can someone give me more details ?
Thx
Julian
I can't answer your first part, but rooted phones use the ADP1 test keys to sign packages.
Usually the AOSP keys are used to sign zips, if you need instructions, they are here:
http://forum.xda-developers.com/showthread.php?t=471586&highlight=sign
Thank you for your answers, but it seems that I don't need any custom scripts to sign the update.zip, since there is already everything needed inside the android source tree (build/tools/releasetools).
The test-keys are located under build/target/product/security/.
But that doesn't explain why I can't see the /res/keys file when in recovery mode.
Julian
Newer version of recovery(eclair) reads the public keys from /res/keys, but with cupcake, public keys included in the source file, see install.c and keys.inc for more detail.
I sit at the computer for two days, just searching the solution, but nothig.
In the stock, .587 kernel based ROM, which files are the hardware-keyboard config files?
And second question.
Can i copy these files from the stock ROM, and paste it to another "cooked" one? My goal would be to fix the "sym" button, and the arrow keys.
Thanks.
I have the same problem. Did you find a solution ?
o/
I just got my MK16i recently. And to my surprise, there's a mismatch on the physical keyboard of the phone. Anyway, it got it sorted out. Here's the thread on how to fix this.
http://forum.xda-developers.com/showthread.php?t=1690889 (For the keyboard layout of the phone)
http://forum.xda-developers.com/showthread.php?t=1690170 (On how to tweak the config files without flashing)
Credits goes to ameer1234567890 and Kiwyxda