Related
I used the guide supplied here for updating my XDA IIs with the latest O2 firmware but still got the country ID error. After a bit of messing around I found that the following worked.
Download v131139 from:
" http://www.my-xda.com/downloads/Xda_IIs_v131139_upgrade.exe "
Then download O2_Asia_14000_923_11200_SHIP from :
" ftp://xda:[email protected]_Updates/O2_Asia_14000_923_11200_SHIP/ "
Extract the downloaded zipfiles and the resulting *.exe files to their own folders so you get 2 folders with the following files:
BaUpgradeUt.exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
Now open the new O2_Asia_14000_923_11200_SHIP folder and edit the file RUU.conf with a text editor (Notepad) and add the following line to it
[CHECKCEID_TYPE]=1
After adding the line save the changes and close the text editor.
Still in the O2_Asia_14000_923_11200_SHIP folder rename "RUU.dll" (version 1.5.0.0) to "RUU.old".
Find the RUU.dll file (Version 1.4.8.0) that is in the Xda_IIs_v131139_upgrade folder and put a copy of it into the O2_Asia_14000_923_11200_SHIP folder.
Now put your XDA IIs into Boot Loader mode and place it in the cradle.
Run BaUpgradeUt.exe and hey-presto the upgrade will run correctly (or at least mine did and I'm running with no problems so far).
I guess that this process will also work with any other XDA IIs/BA ROM upgrades but i've not tried.
Hope that this is all clear enough.
Radio version,Protocol Version and imei disappear
Somebody please help me (sorry with my english, and i'm the newbie too)
after I was upgrade my xda ii s with the newest ROM,the first time its look success, then I install the software, when my xda soft reset for the 2nd time, at booting there "no GSM" then I look in setting>device information > the information about Radio Version and Protocol Version disappear. When I upgrade my Xda iis, I follow the intruction below :
Extract the downloaded zipfiles and the resulting *.exe files to their own folders so you get 2 folders with the following files:
BaUpgradeUt.exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
Now open the new O2_Asia_14000_923_11200_SHIP folder and edit the file RUU.conf with a text editor (Notepad) and add the following line to it
[CHECKCEID_TYPE]=1
After adding the line save the changes and close the text editor.
Still in the O2_Asia_14000_923_11200_SHIP folder rename "RUU.dll" (version 1.5.0.0) to "RUU.old".
Find the RUU.dll file (Version 1.4.8.0) that is in the Xda_IIs_v131139_upgrade folder and put a copy of it into the O2_Asia_14000_923_11200_SHIP folder.
Now put your XDA IIs into Boot Loader mode and place it in the cradle.
Run BaUpgradeUt.exe and hey-presto the upgrade will run correctly (or at least mine did and I'm running with no problems so far).
I guess that this process will also work with any other XDA IIs/BA ROM upgrades but i've not tried.
For those of you who want to customize wm6.1, here it a simple ROM kitchen to do so. Beginners, please wait for my GUI release. It is much simpler to use. This isn't that hard, but it takes a little bit of time on your side.
The basics:
All software and regedits are contained in folders called OEM packages. These are in the OEM folder.
All operating system stuff is in the SYS folder. I've also moved the shadow drivers here so you don't have to mess with them.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Copy the OEM package to the OEM folder.
Do NOT delete the OEM packages you don't want. You will choose them later in a different way.
NOTE: You can always download premade OEM packages from XDA-Develoers. There are tons of options.
If you want to make a regedit.
Create a new folder in the OEM folder and convert it into a package using Package Creator 5.4.
Open the RGU file inside with notepad
Edit like following. Note that this isn't the way to comment in regedit files:
Code:
REGEDIT4 <-----Make sure this is always the first line
------Leave one line blank here-------
[HKEY_LOCAL_MACHINE\Software\Example Software\Example Key] <----- Navigate to keys like this
"Example String" = "test" <-------- Write values with quotes. Strings are given with quote after the equal sign.
"Example Directory" = "Windows\\test.jpg" <------ Use \\ to indicate a \ between directories. Otherwise, the ROM build will not work.
"Example Number" = dword: 5000 <----- use dword: to indicate a number or hex value.
<----- You can add more reg entries after the first one. Make sure to specify a different key when needed
-----leave 2 lines at the end of file------
For Sliding Panels:
Leave ROM as it is.
For Neo interface:
Replace Chome folders and bronze folders in SYS folder with the ones attached below.
Select Neo Interface in the buildos step.
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
Self-explanatory from here.
Post any questions/problems here.
link: http://www.sendspace.com/file/ap9n8w
NOTES: The inlcuded T-Mobile Edition Package is my beta version. Feel free to build on it. You might also notice the empty placeholder folder for my N33D4SP33D Edition rom that I haven't worked on yet.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Click to expand...
Click to collapse
I found the program but get many errors when I start it up on my computer.. Im currently running Vista Ultimate. I went into control panel and changed the enviroment to emulate WinXP when the program runs and still get many errors..
Is there a vista friendly program out there or alternative available?
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
ND4SPD said:
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
Click to expand...
Click to collapse
Great! yours works thanks alot now to get my feet wet in all this lol
I got this error
'Error building default.hv and user.hv! (see imto "BuildOsX-log.Txt")
i can't see anything in there. What now. Thanks
Do you mean there's nothing in the BuildOsX-lot.txt? There should be. A few lines from the last, or the last line, there should be the registry file that messed up and on which line it messed up on. The file is given by the GUID, or that long string of numbers and letters that you see.
no, there is nothing what tell me what to do. so what should i do with that error.
i will make stick this thread.Hope next times will see some roms with this kitchen
Thanks tom. I'll make sure to post my GUI kitchen soon to let more people create ROMs a lot easier.
kormanb1123 said:
no, there is nothing what tell me what to do. so what should i do with that error.
Click to expand...
Click to collapse
what kind of things did you modify or add? Maybe I can help based on that.
I get the same error for the following:
InitRegistry FAILED in file ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu" within a few lines of line 359.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Looked through each App in the OEM folder until I found the matching rgu number, which in my case is the HTC DirectShow. Took that out of my ROM build, ran again and it states that it completed.
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
This may sound like a stupid question, but hear me out. I have used BuildOS in the past for an Apache from PPCGeeks\PPCKitchens. Once the ROM is finished creating in that version it auto prompts to update your device.
After the ROM is done in your version, I then selected the Package Tool tab and pointed it to the "temp" directory and it did it's thing. Now I am at a loss for what to do next. I see a .nb file temp\dump\ROM directory but i don't see a .nbh file. Do I use the NBHTool even though PHOEB is not listed?
ND4SPD said:
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
Click to expand...
Click to collapse
I'm not too worried about the directshow, I just that maybe the other guy was getting the error for the same reason so figured I would pass on my resolution.
Sorry, I guess I didn't completely read you post. For the HTC Rom Tool, use the exacalibur settings. Those are the exact same as the Juno.
all I have is o4_osxip.nb.exe in the temp folder no nbh is this the right nb. file I use with
htc tool I put exacalibur settings but don't no what to put in firmware contents
do I put o4_osxip.nb.exe in system and none in the ipl spl and splash and 0x800 radio
ok i did this
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
ok where is the rom all i have is o4_osxip.nb.exe in the temp
i have no file imgfs-new.bin in the temp all i have is 04_OSXIP.nb.exe and cecompr_nt.dll and CECompressv4.dll
and where would i look for the batch file
Thank you for your works, ND4SPD
but i can not download your kitchen, it says reached the 4G limit.
because i want to know is there any wrong method i used.
My issue is :
when buildimgfs, the total sections can not bigger than 1B200.
when i put too many files into the imgfs file, the buildimgfs will quit without any info.
but the 71M imgfs.bin have about 22000 sections.
do you have issue too ?
Is it because my PC have only 1G RAM, not enough to do the building?
@Hikey: I have that same problem too. It's the way t-mobile packaged the rom. I'm going to try using the dopod rom for the base next. It might be the PC too. I only have 1GB of RAM, maybe it isn't enough.
@kron2:
run buildos
download this zip: http://www.sendspace.com/file/xuhlc5
copy the files from the zip archive to the temp directory.
open up the cmd that's now in the temp directory.
type the following:
Code:
ImgfsFromDump imgfs-old.bin imgfs-new.bin
Sit back and relax. If this finishes without crashing like Hikey said, do this:
Code:
ImgfsToNb imgfs-new.bin 04_OSXIPN.nb os.nb -conservative
Now you can run the htccert program in the main directory of the kitchen to build the rom. When you are done making the nbh, copy it to the RUU folder and run the update utility.
Please rate this thread if it was useful...
I know that stuff like this has been posted before but I have never seen a full guide begining to end on how to backup your rom so here is the complete guide (with links) beginning to end of how to backup your WM6X ROM on HTC's Shift to an NBH
To do this you will need a HTC Shift (dir), and basic knowledge of Windows Mobile, Vista, the command prompt and Syncing a WM device with a computer.
NOTE: I am NOT sure if you need HardSPL on the device to flash the ROM back onto your Shift (if someone could let me know that would be great), my guess is that you do as the created nbh will not be signed with HTC's Cert - HardSPL can be found here http://forum.xda-developers.com/showthread.php?t=406606 and is compatible with GSM Shifts only (x9500)
If anyone has any suggestions as to how this post could be improved or tell me if something needs a more in-depth explanation, let me know - Thanks.
First you will need to Liberate your shift; instructions on how to do this can be found here: http://www.modaco.com/content/windows-mobile-news/266537/liberate-your-htc-shift/ (this step will "unlock" the restrictions on windows mobile - this is not necessary but makes installing RAPI tools and other files easier later.
Download HardSPL (we are not going to install HardSPL in this post, but the download includes RAPI that is needed prior to the next step) from here: http://forum.xda-developers.com/showthread.php?t=406606
When the download has finished extract the contents and copy EnableRapi.cab to your device (To do this select Settings from the today screen > USB Tool > Options > Detach from Vista > Options Attach to Vista - yes detach is not always required but seems to solve some issues with syncing).
Your device will now appear in "My Computer"; copy the file somewhere to your device then switch to Windows mobile and run the file.
Download the latest version of itsutils from: http://www.xs4all.nl/~itsme/projects/xda/tools.html (Look under download section) then follow the instructions on http://forum.xda-developers.com/showthread.php?t=382609
After you have followed the instructions there you will have created RAW files of your Windows Mobile ROM (on the post you will notice the the code window in color - these may be different depending on your device and may need to be changed)
Now we need to convert the raw file to an nbh to do this you will need to download the shift kitchen from: http://forum.xda-developers.com/showthread.php?t=422914 then extract the files from the rar archive (using winrar, winace etc)
On some computers the below operation may fail saying "Error loading dll msvcr71.dll" so you should download and extract the attached zip file (msvcr71.zip) to the Tools directory
When you have done that put the *.raw files created by itsutils into the BaseROM directory and run the !BEGIN.cmd file
Select option 2 when asked to rebuild a ROM and follow instructions.
When the command has completed run the !COOK.cmd file; When a window appears titled BuildOS Click on the Play button and wait for the process to complete then close the BuildOS window
Follow further instructions; until another window appears, Select Shift as the "Target Device" and under "OS" select os-new.nb, then click "Build NBH!",
A window will appear asking you to save the NBH - DO NOT CHANGE THE PATH as it kept crashing when I tried to save elsewhere and call the file RUU_Signed.nbh
Copy the file RUU_Signed.nbh where you want and download and extract CustomRUU.zip (attached) to the same path
To restore the ROM all you need to do is Sync with Vista and run CustomRUU.exe
Feedback is always welcome,
Thanks,
Kris
*RESERVED*
All done! But when performing this process
BuildOS Click on the Play button and wait for the process to complete
I have Error window:
Error: File `ROM\XIP\boot.rgu` not found.
and when I click `OK` - process stops!?
What is wrong?
All done without errors!
Previous Error was under XP on D:\ with many subdirs to `shiftkitchen`.
Now all OK is under Vista with `shiftkitchen` in root of C:\
Thanks!
Little question. I am backuping original Russian ROM... an in the ending window (when I choose "Shift" and "os-new.nb") there is Language:WWE. Is there have to be something else?...
sardonix said:
All done without errors!
Previous Error was under XP on D:\ with many subdirs to `shiftkitchen`.
Now all OK is under Vista with `shiftkitchen` in root of C:\
Thanks!
Little question. I am backuping original Russian ROM... an in the ending window (when I choose "Shift" and "os-new.nb") there is Language:WWE. Is there have to be something else?...
Click to expand...
Click to collapse
When you flash your ROM it will be the Russian ROM ... the WWE setting there and the version are just what is displayed in the ROM flashing tool (CustomRUU.exe)
I had the Spanish version and used this process beginning to end - and it says WWE in the flasher but still installs the Spanish version
Kris
Kris, thanks! Believe that I`ll not have reason to use it. But with this reserved ROM it is composed to make any ROM manipulatios.
Thanks once more!
can i request this to be a stickey?
thanks
Great work i00
I have added it to the WIKI and the FAQ thread.
I confirm that you DO need to install HardSPL on the device PRIOR to flashing the ROM back onto your SHIFT.
it's work
someone got shipped UK rom backup ?
kgx said:
someone got shipped UK rom backup ?
Click to expand...
Click to collapse
Radio is here .. will upload the ROM shortley
http://rapidshare.com/files/232295760/Shift_Origional_UK_Radio.zip
Regards,
Kris
kgx said:
someone got shipped UK rom backup ?
Click to expand...
Click to collapse
Orig UK ROM can be downloaded here:
http://rapidshare.com/files/232298625/Shift_Origional_UK_ROM.zip
Regards,
Kris
Sorry when I try following your tutorial,
I have not os-new.nb file what could I do wrong?
Back-up the rom and radio files
Hi i00, absolutely great guide, thank you for the hard and tidy work!
Since I'm a beginner in this area, before doing the dump job myself, kindly ask you to advise if the dump operation leaves the Shift unchanged on the winmo side and I can use it further, i.e. it is a read-only operation OR do I need to load back (flash back) the resulting back-up files (ROM and radio)?
Thank you!
rom
Hi all
i just bought a brand new shift and want to have a back up of the ROM
I've exacted 4 parts of the rom, but unable to convert it back into a NBH
i cant seem to figure out if i need the RUU_Signed.nbh , and where do i get it from, i thought i was making RUU_Signed.nbh from the 4 raw part files.
if anyone can re upload the complete UK ROM.NHB i would be grateful
i have uploaded the 4 part files and the boot loader
www(dot)filedropper(dot)com/rawfiles
part00.raw
part01.raw
part02.raw
part03.raw
SPL.nb
also do i need hardSPL to even load the original back up rom?
thanks
is this the file i need to include in my baserom folder?
forum(.)xda-developers.com/showthread(.)php?t=1875806
Need Radio ROM GPS+Phone Modded 1.27
here is my error code:
Welcome to Kaiser ROM Kitchen
-----------------------------
Please choose the way for Kaiser ROM Kitchen to work:
Enter 1 if you want just to cook ROM
(RUU_signed.nbh required in BaseROM folder)
Enter 2 if you want to rebuild and cook dumped ROM into flashable ROM
(RUU_signed.nbh, dumped part01.raw and part02.raw required in BaseROM folder)
Please choose 1 or 2: 2
Could Not Find C:\kaiserkitchen\baserom\os.nb
Could Not Find C:\kaiserkitchen\baserom\0*.*
Path not found - C:\kaiserkitchen\temp
The system cannot find the file specified.
The system cannot find the file specified.
=== NBHextract v1.0
=== Extract contents from HTC NBH files
=== (c)2007 xda-developers.com
=== by: pof & TheBlasphemer based on itsme perl scripts
Error: Could not open 'RUU_signed.nbh'
The system cannot find the file specified.
The system cannot find the file specified.
1 file(s) copied.
1 file(s) copied.
Press any key to continue . . .
First of all I would like to thank those who posted tutorials and ROMs for language changes and "4deft". It really works fine if you do it correctly.
I want to add a clarification for language change. It's very easy to assume from reading the related posts that the Hard SPL should be copied to the diamond and installed from there. IMPORTANT.. Everything is done from your PC! Here are the more precise steps:
1. Create a folder in My Documents called Diamond Language Change for future reference. (Recommended, not essential)
2. Download the Hard SPL to above directory on your PC
3. Extract the zip file to a new directory by the same name as the SPL file
4. Download the desired language ROM version to the Language Change folder and extract the zip file to a directory of the same name as the downloaded ROM file
5. From the extracted folder in step 3 run the romupdateutility.exe and make sure to read and follow ALL prompts
6. From the extracted folder in step 4 run the romupdateutility.exe file (it will have the same icon as step 5) and wait.
7. If you did this right, in about 10 minutes you will see the start-up screen on your Diamond and it will prompt you into initial configuration and settings. THEN YOU ARE DONE
8. Remember, all these steps are done from the PC and not within the Diamond
I hope this helps some other newbies like myself!
I flash from old C-ROM (JP) to C-ROM 6.6 (KK)
and get "status 7 error" :crying:
what's the solution?
aa00aa00 said:
I flash from old C-ROM (JP) to C-ROM 6.6 (KK)
and get "status 7 error" :crying:
what's the solution?
Click to expand...
Click to collapse
Status 7 = Bad updater script
There are two ways to correct the
status 7 error. I'm going to tell you the
easier one (atleast i think so )
So, you need a computer for that.
Now, lets begin.
Step 1. Copy the ROM zip file to your
computer and extract it using your
favorite unzipping software.
Step 2. Once unzipped, browse to the META-INF/com/google/android
directory. You will find two files called
“update-binary” and “updater-script”.
Step 3. Rename “updater-script” to
“updater-script.txt” and open with your
favorite text file editor.
Step 4. Get rid of the line starting with “assert” to next semi-colon. Usually
this is the first line or one of the first
lines at the top of the text file.
Step 5. Save file.
Step 6. Rename “updater-script.txt”
back to “updater-script”.
Step 7. Rezip all the files you’ve
unzipped.
Step 8. Copy the new, edited zip file to your phone.
Step 9. Try re-installing ROM, now it
should install fine without Status 7
error.
Ps :- I'm assuming that you are rooted and have a KK recovery already.