Database Develop

Right file?

Hi there! I want to put the LATEST OFFICIAL SW from SE on my X1i. I bought the phone in Switzerland. It would not appear that it is branded in any way. ROM Version says "1.03.939.8" dated "12/21/08", so I suppose that's old. I tried SEUS but it ****s up with the phone identification, displays the screeen for an hour without any changes. Tried multiple times. Now I'm downloading the following: APP_SW_X1i_GENERIC_CH_CDF1215-3301_KOV_R2AA008 to flash it using MicroSD.
Is this going to do what I want? I wish to keep German Language and Swiss Keyboard Layout, as well as default apps (Opera, StreamingMedia, Panels).
Your help is very much appreciated!

Yep, it's the latest ROM for Switzerland.
But you have that on your phone already...

Lokatho said:
Yep, it's the latest ROM for Switzerland.
But you have that on your phone already...
Click to expand...
Click to collapse
How can you tell? I thought a new SW had been released a few weeks ago... And definitely not in December of last year
BTW I got SEUS to work meanwhile. And it indicated current Version is CH CDF1215-3301. So that would match the ROM i mentioned, but not the R2AA008-Bit. I read a lot about R2A being the new one and R1A the old. So what's with that?
And how am I supposed to determine this Version on my phone without SEUS? I don't see any link to the "ROM-Version 1.03.939.8" I get.
Finally, IF this ROM-Version I downloaded equals the one I am currently running, how can I use it for future updates? The file is .image, so would I rename it to kovsky.nbh and Copy to the MicroSD or do I absolutely need the kitchen? And do I get it right that, with a Hardreset, I am doing exactly the same as with flashing the current ROM? And if I flash a newer ROM (Supposing there will be one in the future), will the Hardreset get me back the old ROM or the new one?

forumleecher said:
How can you tell? I thought a new SW had been released a few weeks ago... And definitely not in December of last year
Click to expand...
Click to collapse
There are only two firmware versions and the first had to be released before the phone was released. So December last year can only be the latest firmware.
But to be sure press START --> EINSTELLUNGEN --> SYSTEM --> GERÄTEINFORMATION --> BENUTZERINFO
There should be the SOFTWAREVERSION R2Axxxx

Oh right... Who would associate Userinformation with ROM Version... Didn't even bother to look at it when I had the device info open. Thanks for the hint! Any answers to the other questions?

forumleecher said:
The file is .image, so would I rename it to kovsky.nbh and Copy to the MicroSD or do I absolutely need the kitchen?
Click to expand...
Click to collapse
A kitchen is needed to cook custom ROMs, but you just want to flash an existing ROM.
You rename the image to kovsimg.nbh, place it on the root of your storage card and boot your phone with the volume down and power button pressed.
Then the bootloader asks you if you want to flash the image.
But this only works with official (signed) images, for custom ROMs you need hardspl first.
And do I get it right that, with a Hardreset, I am doing exactly the same as with flashing the current ROM? And if I flash a newer ROM (Supposing there will be one in the future), will the Hardreset get me back the old ROM or the new one?
Click to expand...
Click to collapse
Nope, that's totally different things.
With flashing a new ROM you place the ROM into the boot loader and with a hardreset you are setting the phone back to the ROM-origin.
Imagine, you have a computer with Windows XP on it -this is similar to your ROM.
Flashing a new ROM is the same as formatting your computer and installing Windows Vista.
Once you have Vista installed and customized the desktop and your files, a hardreset would be the same as reinstalling Vista so all your personalisation would be gone and the operating system would be fresh once more.
The ROM inside the bootloader stays the same when hardresetting. You can't "hardreset back" to an older ROM, you just can "flash back" to an older ROM.

skycamefalling said:
A kitchen is needed to cook custom ROMs, but you just want to flash an existing ROM.
You rename the image to kovsimg.nbh, place it on the root of your storage card and boot your phone with the volume down and power button pressed.
Then the bootloader asks you if you want to flash the image.
But this only works with official (signed) images, for custom ROMs you need hardspl first.
Click to expand...
Click to collapse
So how do I know I am owning a signed image? I downloaded it from this forum, from here: http://forum.xda-developers.com/showthread.php?t=475482 I suppose/hope these are signed?
Why do they use .image Extension and not .nbh straight from the beginning? You sure this will work just by renaming? I don't want to question your statement, never, I just want to be sure I'm doing it right if I just rename the file, put it on the card and start in Bootloadermode. I guess, if the flashing failed, that loader ("SPL" or what it's called) would still work, wouldn't it?
skycamefalling said:
Nope, that's totally different things.
With flashing a new ROM you place the ROM into the boot loader and with a hardreset you are setting the phone back to the ROM-origin.
Imagine, you have a computer with Windows XP on it -this is similar to your ROM.
Flashing a new ROM is the same as formatting your computer and installing Windows Vista.
Once you have Vista installed and customized the desktop and your files, a hardreset would be the same as reinstalling Vista so all your personalisation would be gone and the operating system would be fresh once more.
The ROM inside the bootloader stays the same when hardresetting. You can't "hardreset back" to an older ROM, you just can "flash back" to an older ROM.
Click to expand...
Click to collapse
Still it's hard for me to understand, I don't see a direct comparison to PCs here. So when I'm flashing, the phone somehow stores both the "original" state, that is to be used when hardresetting, as a kind of backup, and the state that is going to be used afterwards, where you install your apps and keep your files etc? Or how does that work? What does the device exactly do when I Hardreset?

forumleecher said:
So how do I know I am owning a signed image? I downloaded it from this forum, from here: http://forum.xda-developers.com/showthread.php?t=475482 I suppose/hope these are signed?
Why do they use .image Extension and not .nbh straight from the beginning? You sure this will work just by renaming? I don't want to question your statement, never, I just want to be sure I'm doing it right if I just rename the file, put it on the card and start in Bootloadermode. I guess, if the flashing failed, that loader ("SPL" or what it's called) would still work, wouldn't it?
Click to expand...
Click to collapse
Yes, these are official images from SonyEricsson. Just put rename it to kovsimg.nbh and put it on the Storage card (everything is explained here http://forum.xda-developers.com/showthread.php?t=446070)
If the flashing fails, for whatever reason, the bootloader will still work and you should be able to flash the image again.
But to minimize the possibility of an error, the phone's battery should have at least 50% power and you must be sure that the image download is complete (sometimes downloads just stop somewhere in the middle). So verify the size of the file from rapidshare.
Still it's hard for me to understand, I don't see a direct comparison to PCs here. So when I'm flashing, the phone somehow stores both the "original" state, that is to be used when hardresetting, as a kind of backup, and the state that is going to be used afterwards, where you install your apps and keep your files etc? Or how does that work? What does the device exactly do when I Hardreset?
Click to expand...
Click to collapse
Your phone has three stages of memory:
1. The ROM (Read only memory):
In this stage lies the image
2. The internal memory
The operating system installs itself onto this memory after flashing with a new image and starting up the phone.
You can also write and read from this memory.
3. The storage card (if available)
A ROM-Image is a file that consists of the operating system (WinMo6.1 in our case) and all the application that SE wants you to have on your phone (panels, games, office application and so on).
This file is flashed into the phone's memory, the ROM. You cannot change this ROM or write anything in it except flashing it with another ROM-Image.
You can compare the image with your Windows Vista DVD. The DVD is like the ROM inside the phone -the operating system is compressed on it and the computer can't write onto it, just read.
When you switch on the phone the first time after flashing (the same as the first time you switched it on after you bought the phone), the operating system installs itself from the image onto the phone's internal memory (the same as your Windows Vista-DVD installs the operating system on your harddrive). Once this is done, all the other application that are contained in the image are installed too (e.g. Word, Excel, the Panels, Solitär aso.).
Now everything the phone needs to work is on the internal memory and the ROM is left in freedom but the image is still in it.
Now, if you hardreset your phone, the internal memory will be formatted. Everything on it will be erased. After that the operating system and all the applications are installed out of the ROM image onto the internal memory again as described above. It's like the first time you switched on the phone after you have bought it.
From now on, everytime you hardreset the phone, the image out of the ROM is installed. And it's always the same one to the point when you flash a new image to the ROM.

Thanks a lot for this very in-depth and useful explanation! I think I finally got it Thanks again for all of your help! Now it's all clear to me I'm so happy ThX!

As the full official upgrades (R2) have a radio upgrade, then I'd seriously recommend that you charge to 100% before flashing.
Some people don't seem to think it does anything, but I think it makes the battery calibration better. Doesn't hurt either

fards said:
As the full official upgrades (R2) have a radio upgrade, then I'd seriously recommend that you charge to 100% before flashing.
Some people don't seem to think it does anything, but I think it makes the battery calibration better. Doesn't hurt either
Click to expand...
Click to collapse
What's that radio? As I already seem to have R2, I should have that thing too, should I not? How can I tell?

How to restore to original?

Hi there,
My brother also has an HD and off course I put a nice custom ROM on it
However, the screen is dead since yesterday.
I already put the original dutch ROM on it, but it shows a nasty green windows screen. I can't get any further beyond allign screen...
My question: when he sends his HD to HTC, they will probably won't fix it, because they can see it's HSPL (?).
So anybody knows how to restore to complete original, without getting into the phone with cabs? I put HSPL on it, the phone is 6 months old.
Any help would really be appreciated!!!!
Thx a lot

mcowly said:
Hi there,
My brother also has an HD and off course I put a nice custom ROM on it
However, the screen is dead since yesterday.
I already put the original dutch ROM on it, but it shows a nasty green windows screen. I can't get any further beyond allign screen...
My question: when he sends his HD to HTC, they will probably won't fix it, because they can see it's HSPL (?).
So anybody knows how to restore to complete original, without getting into the phone with cabs? I put HSPL on it, the phone is 6 months old.
Any help would really be appreciated!!!!
Thx a lot
Click to expand...
Click to collapse
You can restore original SPL and rom without having to get into phone with cabs.
As long as you can enter bootloader screen you can restore stock SPL.

I came across this "step for step" process via a search. I have not tried it yet (and hopefully never have to -
How to reflash Stock/Shipped SPL - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. be sure to first restore stock OS, and stock radio. stock SPL is always to be done last!!
1. download your choice of a stock spl package (ie the original SPL).
2. also download the original hardspl from the attachments in this post. (I presume you already have this?)
3. run the hardspl exe but do not click anything in RUU yet. just let the hardspl EXE extract the files for flashing. (You can probably skip this step)
4. the SPL you want to revert to is a .NBH file, put the stock SPL NBH in the extracted hardspl package, overwriting the original NBH file in it!
5. continue with the RUU (or if needed, run SSPL-Manual.exe manually, then run RUU when it goes to tricolour 1.07.OliNex screen), it goes to 100%, reboots, done.
+6. to verify, enter bootloader mode, see version number on tricolour screen, should now just say 1.14.0000.
that's it.
+7. no worries: if your device is stuck in bootloader mode with Hard-SPL and you need warranty service, you can still flash stock SPL.
As I said, I have not tried this. If this does not work, search on this site or Google for additional info. Hope it helps.

mcowly said:
Hi there,
My brother also has an HD and off course I put a nice custom ROM on it
However, the screen is dead since yesterday.
I already put the original dutch ROM on it, but it shows a nasty green windows screen. I can't get any further beyond allign screen...
My question: when he sends his HD to HTC, they will probably won't fix it, because they can see it's HSPL (?).
So anybody knows how to restore to complete original, without getting into the phone with cabs? I put HSPL on it, the phone is 6 months old.
Any help would really be appreciated!!!!
Thx a lot
Click to expand...
Click to collapse
follow to:http://forum.xda-developers.com/showthread.php?t=431217
then download ship rom to flash your HD.

longnguyen30 said:
follow to:http://forum.xda-developers.com/showthread.php?t=431217
then download ship rom to flash your HD.
Click to expand...
Click to collapse
Thanks for linking to the post, I just added the steps
The OP however says that they have already flashed back to the stock ROM, but that the colours are screwy. This needs the stock SPL restored as well in order to recover normal functioning (or at least so that they can send in for repairs without voiding the warranty).

ClydeB1 said:
Thanks for linking to the post, I just added the steps
The OP however says that they have already flashed back to the stock ROM, but that the colours are screwy. This needs the stock SPL restored as well in order to recover normal functioning (or at least so that they can send in for repairs without voiding the warranty).
Click to expand...
Click to collapse
note that; if you restore stock SPL 114 or 115 please download the same rom version for flashing.
ex: when you restore SPL 114 you must have ship Rom:http://rs68l32.rapidshare.com/files....479.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe
because the different SPL & Rom version will make wrong screen.

wow, thank you very much for the quick and usefull replies!
I installed this ROM:
http://rapidshare.com/files/2189268...6.404.1_Radio_52.62.25.34_1.13.25.24_Ship.exe
So after this I have to install original SPL? Can you guys see which one?
Thanks in advance!

mcowly said:
wow, thank you very much for the quick and usefull replies!
I installed this ROM:
http://rapidshare.com/files/2189268...6.404.1_Radio_52.62.25.34_1.13.25.24_Ship.exe
So after this I have to install original SPL? Can you guys see which one?
Thanks in advance!
Click to expand...
Click to collapse
firstly you must Hard SPL 1.56 Olinex
secondly flashing your rom

And restore with SPL 1.13 I assume?

mcowly said:
And restore with SPL 1.13 I assume?
Click to expand...
Click to collapse
The process of restoring stock rom/SPL is only to be used if you plan to return device. If you are wanting to keep you you mentioned earlier then you would need to put either USPL or HSPL on your device first. I would recommend USPL for you as it would be easier to return to stock SPL afterwards.
Once you have rom on your device, DO NOT restore stock SPL afterwards. You only restore this if you plan to return your device. If you did you would have to go through whole process of putting USPL or HSPL onto your device again to flash another rom.

The phone has to be returned because of screen problems.
I will put SPL 1.13 on it and then flash the earlier mentioned ROM.
Then return to HTC

mcowly said:
The phone has to be returned because of screen problems.
I will put SPL 1.13 on it and then flash the earlier mentioned ROM.
Then return to HTC
Click to expand...
Click to collapse
No probs. Out of curiosity what screen problems do you have? Are they Hardware problems or is it something else which could possibly be fixed through the assistance of xda users

It's the phone of my brother, he tells me that the screen doesn't respond anymore, so he can't get past the calibration!
I'll give an update when HTC fixed this (or replaced it )
Thanks for all the help!

I'm doing this right now. I had been using Dutty's V6 before. I never updated the radio, so Ishouldn't have to change it, right?
Anyway, I flashed the stock RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship.exe rom, and that went fine. I'm trying to flash the stock 1.13 spl, and I get error 202: connection. It thinks it can't see my phone, even though it does the initial connection, and even sees what version (1.56) of the spl is on there. Any ideas?

Ok, I did this: I put the phone into bootloader manually by pressing up when it boots up to get to the tricolor screen. That let me run the 1.13 spl pdate, and it said it completed successfully. However, when it boots ups, it still shows D:1.56 olinex or whatever. Did it not work?

Ok, acutally I think it did load up. The Bootloader shows SPL-1.13.0000. So why does it show:
R1.13.25.24
G52.62.25.34u
D1.56.00.00
Is this ready to send in for service?

scythe000 said:
Ok, acutally I think it did load up. The Bootloader shows SPL-1.13.0000. So why does it show:
R1.13.25.24
G52.62.25.34u
D1.56.00.00
Is this ready to send in for service?
Click to expand...
Click to collapse
If your SPL says 1.13.0000 then you are fine to send phone in for service.
R1.13.25.24 - Radio Version
G52.62.25.34u - Protocol Version
D1.56.00.00 - ROM Version

All queries answered

extract file from *.nbh ( ROM file )

Is it possible to extract mp3 files from the rom file ruu_signed.nbh?

i think what ur looking for is easy, there are plenty of software out there that could give you that. I remember using Koch nbh by dutty for Hermes but works fine for the Rhodium ONLY to extract files and not to combine.
But the real question is: how can cook an nb file back to nbh file? because I would like to go back to WWE rom, and I thought of extract the nbh file and pulling out the windows.nb then changing it back to nbh but this last piece of the puzzle is not available.
I went little crazy and used dutty's tool to convert nb to nbh and tried it on rhoidum as RHODIMG.NBH then putting it on the SD and going to bootloader. it seems to be stuck on loading all the time without going forward.

samery said:
i think what ur looking for is easy, there are plenty of software out there that could give you that. I remember using Koch nbh by dutty for Hermes but works fine for the Rhodium ONLY to extract files and not to combine.
But the real question is: how can cook an nb file back to nbh file? because I would like to go back to WWE rom, and I thought of extract the nbh file and pulling out the windows.nb then changing it back to nbh but this last piece of the puzzle is not available.
I went little crazy and used dutty's tool to convert nb to nbh and tried it on rhoidum as RHODIMG.NBH then putting it on the SD and going to bootloader. it seems to be stuck on loading all the time without going forward.
Click to expand...
Click to collapse
Use something like yang to rebuild the ROM image. You won't be able to flash it until Hard SPL is out.

I dunno if this will work on a rhodium or not, but it works great with dumping raphael roms. You can get anything you want out of them. You can also remove stuff or insert stuff and re-cook. Just read the text file for directions; there's nothing to it.

Farmer Ted said:
I dunno if this will work on a rhodium or not, but it works great with dumping raphael roms. You can get anything you want out of them. You can also remove stuff or insert stuff and re-cook. Just read the text file for directions; there's nothing to it.
Click to expand...
Click to collapse
there is a Trojan horse in first post!

It's the custom ruu, and it's not a virus. You are the millionth person to point this out.

Farmer Ted said:
You are the millionth person to point this out.
Click to expand...
Click to collapse
seems ur keep count, so he deserves a prize being exactly number millionth

Farmer Ted said:
It's the custom ruu, and it's not a virus. You are the millionth person to point this out.
Click to expand...
Click to collapse
Thanks. But anyway its not works with rhodium. It can read and make from *nbh to *.nb, but can`t excrat any files. Any ideas?
BTW. Where is my big pirze to be a millionth

Urgent help pls. "Loading" screen on

OK. Decided to upload a new ROM as my phone was getting slow and unusable.
It's an O2 XDA (Touch Diamond) with:
Touchflo v3 Build 29946
ROM 1.93.206.6 WWE
09/08/08
Radio 1.00.25.05
Protocol 52.29.25.12H
Boot R1.00.25.05
I downloaded Olinex's unsigned developer Hard SPL and I extracted the NBH file and renamed it DIAMIMG.NBH following the advice here:
http://forum.xda-developers.com/showpost.php?p=2707841&postcount=4035
On soft reset I pushed the vol down and back buttons to get the boot loader stripes, then let go.
I now have a screen which says "Loading..." and has done for 20 minutes. I have now got the phone on charge while I wait for some help to see what to do next, just in case this is a critical stage - don't want to brick it.
Reading through again I am concerned that this was a procedure for rom upgrade not Hard SPL install, can someone tell me please?
Thanks in advance for any help.

Well, I ended up taking the battery off to get it to reboot. It seems to boot fine back into the old ROM.
I still intend to upgrade it (to SwiftBL's v7.5) but have a few questions:
1. Can the HardSPL be run from the internal storage card? If so is it simply running the exe from the unpacked zip from within a folder? ActiveSync is a bit too flaky for me.
2. Do I need the SIM card in the phone at any stage of the ROM upgrade?
3. On the original ROM I get a drop down menu to setup the phone to the UK O2 network settings. If I load a new ROM, will I need to know these settings?
Cheers

1. HardSPL cannot be run from storage. Only Activesync or Bootloader
2. No. You can flash without SIM card
3. You can use connection setup on any new ROM. Usually starts straight after initial setup.

OK here's where I'm at now.
Downloaded jockyw2001's HardSPL 1.24
Ran it and it got as far as prompting me to run on the phone. I said 'Yes' and the HTC screen went black as expected.
Next stage was to run the DiamondCustomRUU.exe file which I did but this is waiting for ActiveSync. ActiveSync will not sync with the phone now, I guess because the phone is not 'on'?
Where do I go from here?

Use the Hard-SPL in my sig with your RUU.

Thanks, will do (it's not the one mentioned in the ROM author's description though).
So how do I recover the phone from the black screen now? Is it safe to remove the battery to reset?

Battery pulled after reading this post:
http://forum.xda-developers.com/archive/index.php/t-427945.html
I'll try the SPL you mentioned now.....

Had a good search but can't find out. This Olinex zip contains just one file RUU_Signed.nbh.
Where do I get the other files from to run this?

use the attached . It has the RUU exe and the nbh.

Thanks. This is a signed version I see, was going to use SwiftBL's ROM which requires unsigned.
May take a look at other roms that use signed unless you think that I can load the SwiftBL rom with this version?

[TUT] How to Reconstruct a Rhodium Dumped ROM & Reconstructed ROMs

I take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from wiki.
This is the process to restore your Rhodium (TP2) back to the stock ROM and SPL. This should be enough for you to warranty return your device.
I have "borrowed" all of the examples from various sources on xda. Many thanks must goto jcespi2005 and JugglerLKR who created the guide and packages for the Raphael from which the majority of this is taken. The SPL "relock" procedure was taken from the Hard SPL thread. Credit to cmonex .
Prerequisites
The Rhodium Kitchen version 0.1 (Open the Zip File and read the password from the !!!readmefirst!!!.txt)
WinRAR or 7zip
RhodiumSPLRelocker_079SPL.zip
nbImg v1.1
Warning
avast! home detects buildOS as a virus, I've personally used it on my machine with AV off, and am not infected, but it's up to you.
Overview
You must follow these instructions in the order given. Once you have the Stock SPL you cannot flash any ROM's except the ones that are signed by HTC. For that reason you must restore the ROM first, then the SPL.
Step 1 - Get your Orginal ROM.
If you can find your Carrier's / Supplier's ROM on this wiki page or on their website. Please jump ahead to Step 4 - Flashing back to Shipped Stock ROM.
If you cannot find your ROM on the wiki then download this ROM : RUU_Rhodium_HTC_Europe_1.19.401.0_Radio_Rhodium_3.44.25.27_Signed_Ship.exe and proceed to Step 2 - Dumping your phones ROM.
Step 2 - Dumping your phones ROM
First you need to Dump the ROM from your Phone. Follow the instructions in this thread [TUT] Dumping an Rhodium ROM / SPL to obtain 4 *.raw files.
N.B: Although it might seem obvious to senior members, you must dump the ROM from your device before you flash it. If you have flashed another ROM to your device, then your orginal stock ROM is lost. You have 2 options, wait and see if your carrier will release one, or beg someone else with the same device to dump their ROM and share the *.raw files.
Step 3 - Reconstructing the ROM
-3.1: Extract the Kitchen to a Folder on the root of your PC (C:\, D:\, etc).
-3.2: Open the RUU_Rhodium_HTC_Europe_1.19.401.0_Radio_Rhodium_3.44.25.27_Signed_Ship.exe file with WinRAR or 7Zip and extract the ruu_signed.nbh file and place it in the BaseROM folder of the Kitchen.
-3.3: Place the Part01.raw (XIP) and Part02.RAW (IMGFS) in the BaseROM folder of the Kitchen.
-3.4: Run RhodiumKitchen.cmd in the Kitchen.
-3.5: Enter the following options into the Kitchen:
-3.6: e, b (for Dumped ROM). Press [Space] once complete.
-3.7: c, a (for Cooking a ROM).
-3.8: Press the "Play" button in BuildOS and wait for it to complete.
-3.9: Close BuildOS, Close PagePool Changer and Press [Space] to goto the main menu.
-3.10: You will now have a Flashable NBH file. Press f to Flash.
Now goto Step 5 - Removing Security Unlock
Step 4 - Flashing back to Shipped Stock ROM
If you were lucky enough to find a shipped ROM on the wiki or your carrier's / supplier's website, then just run the "ship exe" and follow the on screen instructions.
Step 5 - Removing Security Unlock
If you have purchased the SIM/CID/Security unlocker by Olipro, you can re-lock your device using the following tool : http://hpcmonex.net/htc/secrelock.zip
Step 6 - Restoring the Splash Screen
This is only needed if you couldn't find your Shipped Exe. If you have your Shipped Exe, you get the splash with it.
You're best creating a seperate folder out side the kitchen for this.
-6.1: Find a shipped exe from another WVGA device (HD or TD2).
-6.2: Extract the ruu_signed.nbh from the Shipped Exe using WinRAR or 7Zip.
-6.3: Use NBH Extract (in the Kitchen\Tools Folder) on ruu_signed.nbh
-6.4: Delete all files, except 01_MainSplash.nb.
-6.5: Use nbImg.exe as follows: nbimg.exe -F 01_MainSplash.nb -w 480 -h 800
-6.6: Delete 01_MainSplash.nb.
-6.7: Use nbImg.exe as follows: nbimg.exe -F 01_MainSplash.nb.bmp
-6.8: Use HTCRT in the Kitchen\Tools to make a NBH file from the 01_MainSplash.nb.bmp.nb file.
-6.9: Put the new NBH file and copy RhodiumCustomRUU from Kitchen\Tools into an empty Folder.
-6.10: Run the RhodiumCustomRUU.exe to Flash the Splash.
Step 7 - Flashing back to Stock SPL
-7.1: Ensure you already flashed stock ROM and Radio, because stock SPL flash is always the last step before sending the device in.
-7.2: Extract the relocker zip and run the EXE on your PC.
-7.3: If you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL signed by our custom cert). The included one is the 0.79.0000 stock SPL.
-7.4: Flash the Stock SPL
-7.5: Verify if it flashed by checking version in bootloader screen, it should say 0.79.0000, not 0.85.OliNex.
Credits:
-jcespi2005 and JugglerLKR for the Kaiser and Raph Kitchens
-Olipro and cmonex for Hard SPL and Security Unlocking
-pof for nbImg
-Everyone in the Readme.

Reserved
(P.S. I've been writing this in another forum for a few days, hence the Thread Date of the 15th - so this is a bump )
Dave

Did the same thing
Used the Ralphael Kitchen, changed the settings to Rhodium added some settings for Rhodium. used a signed Tmobile US Rom.
Nice Tutorial

Sorry, Dumb Question...
-MOD EDIT: Removed Full Quote
I have found my stock ROM, so I can continue with flashing back to stock, but where do I find the stock SPL?

D_monie3 said:
-MOD EDIT: Removed Full Quote
I have found my stock ROM, so I can continue with flashing back to stock, but where do I find the stock SPL?
Click to expand...
Click to collapse
It's the RhodiumSPLRelocker in the Prerequisites or download it from the Hard SPL thread.
Ta
Dave

First, thanks for this. I write a fair amount of documentation of my work as a network admin so I know how time consuming this is.
cdguider has been kind enough to dump and reconstruct the TMoUS ROM so I don't actually need to do this (although I may just for the exercise) but I do want to start learning how to modify this ROM to suit my own needs. Is there a guide up that will get us newbies started on using the kitchen? Hopefully one that explains in detail what each of the kitchen tools are and what they do as well as how the Rhodium ROM is constructed. I prefer to understand what I am doing versus following recipe steps. For example, My Hermes ROM was partitioned into the ROM and an extended ROM where carriers could put their installers. Does the Rhodium have an ExtROM?
OK, back to the search tool.
S

sleonard said:
First, thanks for this. I write a fair amount of documentation of my work as a network admin so I know how time consuming this is.
cdguider has been kind enough to dump and reconstruct the TMoUS ROM so I don't actually need to do this (although I may just for the exercise) but I do want to start learning how to modify this ROM to suit my own needs. Is there a guide up that will get us newbies started on using the kitchen? Hopefully one that explains in detail what each of the kitchen tools are and what they do as well as how the Rhodium ROM is constructed. I prefer to understand what I am doing versus following recipe steps. For example, My Hermes ROM was partitioned into the ROM and an extended ROM where carriers could put their installers. Does the Rhodium have an ExtROM?
OK, back to the search tool.
S
Click to expand...
Click to collapse
No it doesn't.
For help with this Kitchen, see _Alex_'s cooking guides on the wiki for the Kaiser. That's where I started reading and then I just kept going, download kitchens published by other chefs and see how they put stuff together. There are two main types buildOS (like this one) and PRB that uses bepe's platform rebuilder - ervius's visual kitchen is based on it.
Thanks
Dave

i reconstructed the uk orange stk rom all ok very good guide thank you!
i had to do this because i lots the hard reset it just flashes up no immage then back to boot loader i though stock rom would resolve this i rebooted it and still have no hard reset still says no immage boo boo whats going on is it due to the ruu i am using i thried the rhodium one and the v1.1 one what ever it is i also tried dave's wrapper and a kaiser on out the kitchen tools all same results so i guess not any ideas ppl!?

matttytn2 said:
i reconstructed the uk orange stk rom all ok very good guide thank you!
i had to do this because i lots the hard reset it just flashes up no immage then back to boot loader i though stock rom would resolve this i rebooted it and still have no hard reset still says no immage boo boo whats going on is it due to the ruu i am using i thried the rhodium one and the v1.1 one what ever it is i also tried dave's wrapper and a kaiser on out the kitchen tools all same results so i guess not any ideas ppl!?
Click to expand...
Click to collapse
So you are stuck in the bootloader?
What does it say in the bootloader?
Ta
Dave

Sorted it i am such a fool i was doing the wrong button combo!!!!!!
This is fantastic i am now going to have a play at cooking up my own i know i can do this now i will get my head down and work this stuff out i mite have my first rom by xmas

question about step 3.9
"Close BuildOS, Close PagePool Changer and Press [Space] to goto the ."
how can i close PagePool Changer ? it doesnt work.....
and ,which "main menu" i can goto?

leeneo said:
question about step 3.9
"Close BuildOS, Close PagePool Changer and Press [Space] to goto the ."
how can i close PagePool Changer ? it doesnt work.....
and ,which "main menu" i can goto?
Click to expand...
Click to collapse
Just click the [X] in the top right.
Pressing space will take you to the first set of options that the batch file offered you.
Thanks
Dave

leeneo said:
:12
:12.PagePool.Changer.bat
tools\xvi32\xvi32.exe RUU_signed.nbh
GOTO :EOFQUOTE]
this code in RhodiumKitchen.CMD
but , i cant find PagePool.Changer.bat ........
Click to expand...
Click to collapse

leeneo said:
leeneo said:
:12
:12.PagePool.Changer.bat
tools\xvi32\xvi32.exe RUU_signed.nbh
GOTO :EOFQUOTE]
this code in RhodiumKitchen.CMD
but , i cant find PagePool.Changer.bat ........
Click to expand...
Click to collapse
That's a label in the batch file .
Search for it in the RhodiumKitchen.CMD and see what's called from there.
P.S. I don't have this kitchen on this computer so a lot of guess work and memory on my part.
Dave
Click to expand...
Click to collapse

DaveShaw said:
leeneo said:
That's a label in the batch file .
Search for it in the RhodiumKitchen.CMD and see what's called from there.
P.S. I don't have this kitchen on this computer so a lot of guess work and memory on my part.
Dave
Click to expand...
Click to collapse
ok , i see ..
you kind-hearted ! thx
Click to expand...
Click to collapse

yea thanks for the thread dave, When i use these tools to do up my own splash it chops off at the bottom... is there a patcher out yet to fix this?

thx for the tutorial , how can i take new xip/sys and replace the existing?and how can i remove and add prgorams?

joshkoss said:
yea thanks for the thread dave, When i use these tools to do up my own splash it chops off at the bottom... is there a patcher out yet to fix this?
Click to expand...
Click to collapse
Yes, but I can't recall where I saw it . It's not for the TP2 though, maybe HD or TP.
saymyname said:
thx for the tutorial , how can i take new xip/sys and replace the existing?and how can i remove and add prgorams?
Click to expand...
Click to collapse
Porting isn't simple, have a look for some tutorials on using BuildOS and porting.
Adding and removing programs, to add, just create OEM packages, to remove, just remove them.
Have a look at _Alex_'s cooking tutorials on the Kaiser Wiki.
Dave

DaveShaw said:
Yes, but I can't recall where I saw it . It's not for the TP2 though, maybe HD or TP.
Dave
Click to expand...
Click to collapse
yep the tp one has no affect on our splash unfortunatly. i've already posted in theyre thread askign they make it compatible. but just wonderin if you came across anything about this is in your many travels.

Question
Hi everyone ...
First of all Thanks alot for this Tut Dave awesome work.
I dumped my Stock Rom from a unbranded O2 TP2 and rebuild it.
For Cooking i used the signed_ruu from RUU_Rhodium_HTC_Europe_1.19.401.0_Radio_Rhodium_3. 44.25.27_Signed_Ship.exe
It did everything like described and i've got a
signed_ruu.nbh (1.19.207.1) newest o2 Stock Rom.
Should be fine right?
Do i also need to do Step 6 so creating a splash screen?
If anyone needs this rom drop me a message ...