Database Develop

how to build custom extended ROM?

I've been debating trying my hand at cooking up my own ROM sometime here soon since I've not been entirely happy with the precooked ones. You know what they say, if you want something done right you just gotta do it yourself. ;-)
Anyways, I was thinking that I would probably like to install more software than I can put in just the ROM itself. I know I can do this through the extended ROM but I don't have the first clue where to begin and there doesn't seem to be any sort of tutorials floating around on the subject (or, indeed, of cooking in general). So how DO you create an extended ROM and add programs through it?

Avatar28 said:
I've been debating trying my hand at cooking up my own ROM sometime here soon since I've not been entirely happy with the precooked ones. You know what they say, if you want something done right you just gotta do it yourself. ;-)
Anyways, I was thinking that I would probably like to install more software than I can put in just the ROM itself. I know I can do this through the extended ROM but I don't have the first clue where to begin and there doesn't seem to be any sort of tutorials floating around on the subject (or, indeed, of cooking in general). So how DO you create an extended ROM and add programs through it?
Click to expand...
Click to collapse
There's a great kitchen that i got from the forum. I can't upload it right now, but hopefully someone has some bandwidth to get a link. Search for Wizard extended rom kitchen. I believe Faria put it together. Check out the .pdf it contains for instructions.
Basically, you'll use a tool called Winimage to "inject" files into a file called ext-rom-base.nb. In the image is a text file that tells the installer what to run.
Each file must be selected as "read only" after injecting, or it won't work.
Injecting is basically dragging and dropping cabs or exe's into the file, nothing fancy. Note that each file type is called differently, so watch out for that one.
Also - the cabs cannot require operator intervention - or the installer will hang. Make sure they run and tell you that they're done.
Then when you run nb2nbf_wizard, you can check Ext_rom, browse to the file ext-rom-base.nb, image name is Extension_ROM, and address is 9B000000.
You can create the nb.nbk to include just the extended rom, just the OS, just the Splash screens, or any combination you want.
A bit intimidating at first - but actually very easy. I never messed up my phone once working with the extended rom on the Wizard. I broke my Hermes twice already, and still can't figure it out

ftp://xda:[email protected]/Wizard/Extended_Roms/Extended_ROM_Kitchen/
Enjoy.
Post also moved to wizard upgrading.

hi guys,
I had problem when cooking ext rom. I got ''htc-wizard-ext-rom-maker-kit" by faria from ftp. I did exactly all the steps in faria pdf guide, but after hard reset it didn't work. I don't know why? Anyone help me pls.
My device:
IPL/ISL: 3.08
Radio: 2.19.11
ROM: TNT 3 Pro

Troubles

Hello people,
I gave this short title to this topic because... I'm simply having troubles. Troubles upgrading, syncing, translating.
I have a Qtek2020. It had WM2003 installed. Had, because I finally managed to install WM6.
But let's go by order.
Some days ago I found this awesome fantastic forum full with binaries.
I have some experience with ROM flashing with various devices. I also did upgrade my OS several times on my 2020. And I decided now it's time for WM6. Many people here said it works, and I wanted to upgrade too.
I'm Italian, so you would understand that I prefer using an Italian OS. But I first wanted to install English WM6 to try it out.
I downloaded TofClock AKU 0.7 and tried to install. But then, the first troubles.
I could no way upgrade my device on my home PC, which runs Vista x64. When I put the device in bootloader mode, the upgrade software returned error 101.
So I tried to do the upgrade at office, under XP SP2 (x86 platform), and everything gone fine.
OK, you would say, you got your new fresh OS. I actually don't have musch to complain about TofClock: I really say BIG BIG HUGE THANKS to the genius that did it!
But here's another problem. Still at office, I could no way sync my PDA on ActiveSync 4.5. Windows didn't install the driver properly.
I came back home: as I said, I run Vista x64. Fortunately, Vista downloaded a driver from Windows Update and the whole thing worked.
OK, you would say. You even got your sync relationship at home.
But now that I saw it worked, I wanted to install an Italian version, maybe even cooked a bit, so I downloaded both the Kitchen and the Microwave for m0dding and translation. The firts thing I tried was the Microwave I found at http://forum.xda-developers.com/showthread.php?t=334421&highlight=italian+microwave
I followed the full tutorial literally but I had the following problems:
There was no dump directory. Only dump.src. And dump, filled with tons of files, was required
There was no nk.nb file
There was no 800401-OS.bin file, required by other parts of the batch script
I tried on my Vista x64 and I also tried on a XP SP2 Virtual Machine on my desktop PC. Same result. I found another tutorial. I will probabily try it, but I'm so confused now. Why am I the only one who can't translate his ROM by following literally a tutorial?
Can somebody help me? Maybe with an already-working ROM for Himalaya that I can flash by myself?
At this time, I'm trying to connect my USB cradle to my Virtual Machine using USB over Network, because if I want to do this at home I have no other choice than using XP x86.
Meanwhile, I ask you help with translation. Please! I just need to run it in Italian. I will take care of Kitchen and all the mess that comes with customization later. I only need Italian now, and I need to be able to upgrade. I still have 15 days (by now) of trial license for USB over Network. I could even share my cradle with somebody that is able to do the upgrade remotely, because, as far as I know, if connection breaks during upgrade and the process fails, the Bootloader mode prevents the PDA to become another brick in the wall and the operation can be still tried again.
I will leave my MSN Messenger contact on my profile. You can find me everytime but business days/hours.
Thanks in advance.

I'm sorry, but the Microwave is for HTC Wizard only, you can not use it for Himalaya.
Download the Himalaya kitchen, find Italian *.dll.04xx files or extract them from the free Microsoft Italian WM6 emulator. Use the quick and dirty way to create Italian ROM as described in
http://forum.xda-developers.com/showthread.php?t=311078
success

I tried that tutorial (still in Virtual Machine). I had error "file temp\dump\imageinfo.bin already exists" when clicking the green arrow in Kitchen. I tried both Anichilius and TofClock's Kitchens
[Add]: I'm trying with HyperCore. I'll let you know

Anichilius kitchen is for Hermes, not for Himalaya
Tofclock worked on several devices
Hypercore is Hermes as well
Get your facts straight before trying to cook a ROM or you'll brick your device

Unfortunately I'm no expert in ROM cooking. It's my first time here. I don't know about the differences between the devices.
As far as I know, most of the Kitchens carry the same program: BuildOS. I found the problem running it. I'm trying to learn everything now by reading the forum.
I dumped TofClock's ROM (OS ver. 6.0) using ImgfsToDump and got all the files. I dumped WM6 Emu too. I found that TofClock ROM doesn't carry the *409.mui files that are inside emulator's ROM, like explained in the tutorial. So when I renamed the files from 410 to 409 and copied them I didn't actually overwrite anything.
Running BuidOS, which is a script that comes with every kitchen with no modifications (I didn't binary compare the files but I think it's the same script), so it doesn't seem to be device-specific, I always got the error "File temp\dump\imageinfo.bin already exists". I tried to find out the reason by reading Hypercore documentation. And it seems, as I thought, that the files I want to build are in conflict with the original files. I tried to understand why. I'm not sure about it, but by the hex address I saw around in the dump files it seems that the ROM is not organized as a file system, where every file is dynamically allocated and indexed in a file table, but they are allocated to raw memory address somehow.
I don't know why. For example, if I want to cook a Windows XP setup CD with my own bootloader I have to simply burn a CD with a modified ntoskrnl.exe file and here we go every XP installation from now on shows my ugly/sweet face (choose the best that suits)
As far as I know, apart from obvious size limits that vary with the device, there's a new limit in ROM cooking: I can't copy&paste files. I thought that the BuildOS script "simply" packed all the files into the ROM rebuilding the file table, adding checksums and other info according to the ROM format (which I don't know), and maybe I'm wrong.
[Add]: I have been trying to get in contact with slumpolo, which is very expert in Italian ROMs. Meanwhile, I read on that tutorial one of his replies: he said that not all ROMs have MUI files. So TofClock doesn't use MUI (btw Windows Vista does, but that's other things), but WM6 emu does, and that may be the reason why they are not compatible.
I know Himalaya devices are a bit "ancient", but I wonder if there's another ROM than TofClock to work on. I may try with it.
I wouldn't like to ask "can somebody [with big big experience] do the translation for me?". I would like to do it myself, but I need tools and knowledge. I think I already got the tools...

There is already a great Tofclock WM6 AKU 0.7.0 especially for Himalaya. Download it from http://forum.xda-developers.com/showthread.php?t=331637
and the Xplode Kitchen Tutorial. This kitchen has all files and registry hives extracted and nicely organized. So you don't need to dump them yourself.
Of course you will need the emulator dump. Keep folders well separated and organized.
It does have all the 0409.mui files. If you use the quick and dirty method of simply renaming your mui files/folders to *.0409.mui and overwriting the original ones, you should get a fairly acceptable result. Not perfect, the emulator runs an older version of WM6 than the one in the kitchen. If you want perfect, you'll have to spend a lot of time...
Your big "WHY" question: Intel X86 architecture is very much different than the ARM/Xscale architecture. The ARM is a child from the Acorn RISC processor. So operating systems for X86 and ARM are very different in structure as well. But if you want your pretty face on the Hima bootloader screen, it can be done, search the forum for "splash screen"
Hima is by no means "ancient", it is still one of the best HTC designs ever. All right, the newer models are lighter, have beter cameras and some even 640x480 and a "modern" price tag...
Don't worry, I won't offer to do the translation for you. I'm still trying to create the perfect Dutch ROM.

We talked about the same Kitchen. I tried it too in the beginning. But now I found something more. Many of the 409.mui files in this Kitchen are in subdirectories. So I could simply paste them there and find no error in BuildOS... Maybe... I'll let you know.
BTW the face thing was a joke: I already know how to change a bootscreen and I will do that as last thing once the ROM is stable and Italian.
About the "perfect" ROM, I can accept the challenge and spend some more time on it once created the BASIC Italian Rom, at least...
And I said Hima may be "ancient" because my Qtek 2020 is more than 3 yrs old
Cya 2moro

In desktop PC's I consider 2 years old the equivalent of stone age, I'm really surprised that this hardware has such an enormous life span. I even believe we've yet to discover the full potential of this little beasty.

Lol.
By the way, here's the thing I wanted to show you.
The files in Microwave directory are the dump of emulator, while the files in Work directory are from TofClock.
So I "simply" have to match directories while pasting emu files into TofClock after renaming

djechelon said:
So I "simply" have to match directories while pasting emu files into TofClock after renaming
Click to expand...
Click to collapse
Simple, as long as you're concentrated. Because in the Quick and dirty method both directories have identical names, I once started dragging and dropping in the wrong direction, overwriting Dutch with English...
Next pitfall, some files point to one another
a.04xx refers to b.04xx
I use Ultra€dit to search inside all these files for the string 0413 (dutch) both in plain ASCII and in Unicode. Do not automatically replace, watch in the hex editor if it's actually a string, not a piece of code.
Now edit initflash.dat using a good unicode editor (like ultraedit) and take care to save as unicode. Do not allow the editor to convert it into anything else. Take care that there's only one initflas.dat in your kitchen, the edied one, and not for example an autogenerated backup (Ultraedit can do that...)
Read cooking tutorials on how to edit initflash.dat
Add OEMs (see cooking tutorials)
Cook, burn, test

I think you're going to tell me that the ROM I managed to cook now won't work until I manually edit each single MUI file against 410 pointers... Actually I forgot to paste initflashes.dat, because when i pasted the whole directory I always found out that the names were correctly translated! Yea, just because I pasted it.
I'm gonna use TortoiseMerge to compare initflashes.dat from emu to TofClock.
Fortunately, I can make as many mistakes as I like because if I brick the device I can reflash it using Bootloader mode with a working ROM (which I'll jealously keep on my hard drive in more copies ).
However, I was unable to flash under my XP SP2 Virtual Machine. I'm trying again under Vista, else I'll have to do it at office where it worked last time...
It's really harassing, but it's a fascinating world I'm exploring.

Brick
Oh finally I bricked my device!!!
Hahahaha. OK I managed to build my first Italian ROM but, as expected, the device got stuck on the Windows Mobile logo.
Not bad. I tried a little modification and re-flashed it. Same error. So I gotta restore TofClock original for now... It makes me little sad because I ran in lots, lots, lots and lots of troubles, putting all of my efforts, to build the f***** ROM.
Till my device still lives, I can test as much as I want. By the way, Maggy, I need your help now.
You talked about cross-links in MUI files. I tried to find them. I used UltraEdit and tried to search for "410" (Italian) in the MUI files I renamed into 409, but I can't find anything. I tried with a lot of files, not all files, but no one has cross-links.
Just to see if everything's fine, I'm trying to re-cook the TofClock ROM that came with the Kitchen, with no modifications, not even the bootscreen. It's just a check. It's 3 AM now: should I take a nap? I think so...
Anyway, let's get back to my problems. I noticed that both on Vista and XP (btw I managed to cook&flash with Vista so I can now throw the VM in the bin together with the shareware version of USB Over Network that installed me a harassing driver blocking all USB devices including mouse & key if I don't manually disable driver signature...) the BuildImgfs program... explodes!
Well, actually it consumes too much memory. The heap goes up to 1GB before crashing. I think here is a bug in the script: destructors should be called to free memory from unused object ASAP. .NET and Java have Garbage Collectors, which take care of destroying unused object, but it's not the same with unmanaged code like C++ or whatever used to make the program.
I tried to search, but I found nothing (did I say something about a nap...?). I need, if available, a newer version of BuildImgfs that manages memory correctly and doesn't crash. I saw many people having the same problem. I don't add too many packages: I'm even forced to remove Windows Media Player to let it build!!!
[Add]: as expected, the re-cooked TofClock works. OK I'll go sleep now. Promise!

Dead Xda IIS

Guys, i need some help. Recently i came across the rom update for my xda iis, so i decide to take it out of my drawer and see if i can update it with HELMI_BA_WM6_R0_Public. I followed all the steps and try to upgrade it, after i click on HELMI_BA_WM6_R0_.exe, my xda iis restart on cradle and after that nothing happen. I notice it only appear on the top with the word "serial" and the bottom "v2.06". I have tried in vain to get it working again, please try to help as im very new to this. Im using window Vista.

since apparently, you are not that experienced in flashing your device, i would recommend you use windows xp to flash your device.
then you have a look at this wiki wizard:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
this is a step by step instruction on how to upgrade from wm2003 to wm6.
please follow it precisely, even if you don't see a point in certain steps, they are all important!!!
if you, however, don't understand a step or a phrase, feel free to re-post, and i will explain it to you in more detail.
have fun with the upgrading, one word of advise: take your time, the first upgrade with storage resize radio upgrade, sim unlock and other stuff can last an hour or two (not the upgrade itself, but the process you go through). when you remember the steps and feel like you want a different rom, after testing this one, all you have to do is donload a "nk.nbf" file and flash it, and the entire update takes you 5 minutes then

Hi Chef_tony, thanks for the reply. I went to the link u gave me and from the 1st step on im stuck. It ask me to download both the unlocker and Repart and place it on the phone, but i cant do anything with the phone except for the "Serial" on top and "V2.06" below, it does change to "usb" when i cradle it. please help. thanks again

ok, then at that point you are stuck in boot loader, that happened to me too.
the reason for that might not be that interesting to you now, but it is because vista in the middle of the flashing process vista thinks it needs new drivers, downloads them and then it disconnects the device, something that shouldn't be done while flashing, as everyone knows.
these wiki links explain how to flash from vista using modified drivers, but i wanna tell you in advance, that i personally never got it running, i always use a windows xp machine:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic
so, still i want to state that the best way to flash is a xp computer, if you have access to one, use that to flash your original shipped rom first, to resize the storage (first wizard step) afterwards.
theoretically, a virtual machine, running xp would also work, if you still have an xp cd lying around, you can download virtual pc 2007 from microsoft, it is free and you just need a short time to set up a virtual xp machine, because i can guarantee you, you will flash more than one rom, once you started on the topic.
remember, you need to flash your shiped rom, then you want to flash the helmi rom, then maybe a rom update and probably you are not staying with that rom forever, since it is wm6, there is also wm6.1 and wm6.5 to follow that.
what i want to say is:
- try the flashing with vista option described in the wiki links above
- if that doesn't work, try to get to an xp computer and follow the steps
- flash your original shipped rom first
- then the wiki wizard steps in again

Problem is solve, thank you so much chef_tony. my next question is...where can i get wm6.1 rom as all the link i had is dead

according to another user, this thread's links are still working:
http://forum.xda-developers.com/showthread.php?t=403421
but it does not contain office. (you can still try other office download links, if you need it)
just by the tiny size of the extrom i would say there is hardly anything contained, but anyway, that is a rom i used too, and it is quite nice, also look up IOLITE stuff in this forum for extra apps.
make sure to repost if everything went to plan

I found a working wm6.1 pro on another website and its working great! It contain office as well. Thing now is i didnt adjust the memory and i didnt have enough space to install every software that i had
This is the link http://www.4shared.com/file/66810499/8a61be24/HTC-BA5220758WWE_v302_25M_PP-16M_RAMdisk_a.html?s=1
By the way chef_tony, you happen to have any idea how to open up BA, cause i would love to clean it up on the inside.

1. the thing is, the storage resize is important for 2 reasons:
- sure, with the resize you woulld have 16mb more storage memory for installing programs and storing stuff
- you still have your original extrom on the device, which is not compatible with newer roms, meaning, instead of simply copying the extrom to an sd card to have a basic setup and installing programs you need to install cabs manually
which is why i said to follow the steps precisely, now you have 16mb of space you simply can't access from wm6 at all, and for a resize you'd have to go back to wm2003 first but give your rom a try first, maybe it is not the perfect one for you after all, then you still have the opportunity to re-flash.
2. i am glad you found a valid link, many people post their roms to hosters that take it down after a while, expecially when there are no more downloads of that item, and so, many links posted here half a year ago are not working anymore, which is sad, since there are still a lot of people, including you, that would like to go to wm5, wm6 or wm6.1 and not just the newest wm6.5 builds, but, whatever, you found your rom and hopefully kept the files stored on your pc for future reflashing...
3. there are two basic disassembling guides for the BA:
- the official service manual (also good for repairs, since they explain each step):
http://www.4pda-service.ru/netcat_f.../BLUE ANGEL/HTC_Blue_Angel_Service_manual.pdf
- the manual made by a forum user:
http://www.land-of-kain.de/ppc/mda3/disassembly/
i am glad it all worked out for you so far and you will realize that this old device has a lot of potential, when you keep it up to date (and clean ).

Thanks you so much for the help. I'll try to update if the link is dead someday, by the way..i have 43mb storage and 84mb programme, is that good or bad?

the program memory is normal, but the storage should be 16 mb more, so instead of 43.XX you would have 60.30mb.
that is the extrom resize mentioned before.
- you need to flash your original rom for that
- then copy the "xda-developers unlocker" and the "repart_doc.exe" to your device. (attached below)
- you install the extrom unlocker
- then you go to start menu and extrom unlocker
- you execute "unhide"
- then unlock
- then start the repart_doc and set the size to 128kb
then you can lock the extrom and hide it again.
maybe in that process there is a soft reset required, i don't remember.
the reason why you do all that is because the extrom memory is hidden and locked and contains a bunch of cabs, that install automatically, when you hard reset the device.
so after that, you can reflash your wm6 rom, and you'll see, that after you resized and formatted that space, your memory dialogue will show 60.30mb of storage memory (plus it gives you the opportunity to install wm6 extroms from the sd card).

Upgraded Qtek 9090

Well, I'm new here in the forum, come and ask for help from everyone, because I tried everything, and frankly I'm kinda tired of reinstalling everything without being able to update my QTEK WM6, when he ta with WM3 SE, follow the tutorial here, but always get stuck at the run the update because it does not show the version being installed and not installed on the device, therefore I can not continue.
Sorry for bad English!
I await help! = \

Look oque appears when I try to go anyway!
Apparently the software to using is not appropriate for the QTEK9090 WM3 SE.

well, i would guess, either your device is not in bootloader mode or your activesync is not successfully killed, also have a look at these detailed instructions and make sure, you are performing every step in that order, because people seem to reduce the upgrading to 5 steps and miss out on other important steps and then wonder, why they got close, but could not actually upgrade. this should help you:
http://forum.xda-developers.com/showpost.php?p=4706441&postcount=2

Well, I stopped at the next part because I was concerned:
"
6. Click "Format now!"
7. Soft reset
8. Go back to the Extrom Tools
9. Lock "
10. "Hide"
11. Now proceed with "Upgrading to WM5 / 6 device" "
Format does not reset the contents of some memory? XD
And so, my device is already unlocked, just that I do not know if this release is the same as reported in the tutorial, because the release did was running a program, and only, I put no chip here and recognize.
Well these are my doubts before proceeding, take better now than screw up =).
And thank you for your help buddy!

And type, that WM6 signature, it is recommended?
Thanks =)

i don't understand your problem with that.
that part is about the extrom, and whether you format the extrom during using the device does not matter, because it is only used after a hard reset. the extrom is a special hidden partition that contains cab files, provided by your carrier or the phone manufacturer, that are supposed to customize or brand the device after the initial start. since that is never used again and only contains crap in the first place, it is recommended to delete that partition and merge it to the storage space, to be able to install more stuff.
also, you should not be afraid to format any partition, because when you flash a new rom, you format the entire device anyways. if there is still stuff, you don't want to lose, you should make a backup asap.
also, in case that was misunderstood, that unlocking has nothing to do with sim-lock or anything.

Hmm, then this procedure is only if I want to increase the storage space? I could skip that part?

you could skip that part, but why would you want less storage space. you know, the gigantic ram partition is not there in any build above wm5, you only have 43mb of storage space, why not make it 60mb, it is more. that extrom partition cannot be accessed from a higher operating system, there is no advantage in keeping it. it could even result in problems, when installing the newer roms' extroms, because they are supposed to be on the sd card and for some people, they don't work, if they didn't take care of the old extrom first. and now is the only opportunity to do it. once wm 6.5 is flashed and you realize, you're running out of storage space, after installing internet explorer, office, .net framework, maybe another browser and your pim data, maybe an mp3 ringtone, you'd have to go back to wm2003, increase the storage size, and then flash wm6.5 back and install everything all over again.
so, extrom resizing:
PRO
+ significantly more space
+ faster running device
+ no problems with installing wm6.5 extrom
+ no old baggage which you cannot use
+ you will probably do it anyway, now it takes 3 minutes to do it
CON
- no downside here
i see that since you are a rather new member and probably don't know, what every little step is for, but i put that in the tutorial for a purpose, so people don't make the same mistake i made: to skip that and go to wm6 directly, i regretted it and had a lot of work going back and clearing out the mistakes done before. this is a one time only process, whenever you decide to flash another rom, you will only need to do the "upgrading a wm5/6 device part", which will take about 10-15minutes overall. also there is no need to worry, this process is completely reversible, whenever you feel uncomfortable with your custom rom and for any reason you want to get back to the factory defaults, you can do that, so you have nothing to lose here
i hope these were enough reasons for you to keep going and follow procedure

I deeply appreciate your explanation, now I just wait for rapidshare free slots that I could download the necessary files and try again an update, yes, I'm afraid of running out of equipment, I'll try it again ^ ^.
When I start the procedure again and any problem I may have or if God willing I can update I've been posting here.
Again for the help

How can I tell you, thank you for your explanation was fine, because I almost died here at the time that tava installing WM6, gave the fall of light, more then I redid the procedure and installed by a faster ^ ^.
Chef_Tony, taking advantage, you recommend me some programs or games? ^ ^
And to make the topic too, you understand the Audiovox smartphone? It is similar to the QTek, a client of mine has this machine that only the poor ta destruidinho, the touch and cracked his ex-owner tried to install WM6 on the device as it is not possible and now the device does not leave the screen colors, enter the serial screen and everything, only that it will be to recover from that?
Sorry for the inconvenience.
The model is the Audiovox PPC 6600.
Anyway, thank you for all patience and clear ^ ^!
------------------------------------------
Interestingly, you can change the items on the Home screen? Why is a lot of things that do not use and would be interesting to place objects that use it '-', I liked the format, just do not like the items, just wanted to change items xD

[Q] Things to do/save BEFORE flashing ROM

...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.

efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?

mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.

Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a

I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?

tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy

I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.

Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin

No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.

Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!

OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.

So... let's say that you didn't save your android id before you flashed... will that cause problems?

beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.