Hello guys i have just moved from HTC Wizard Thread because i have sold my old Wizard and have bought my brand new T-Mobile MDA Vario IV. Flashing, Dumping, etc on Wizard was really simple. But in Touch Pro i cant get through the all things. Maybe it is my not very good technical english or something. All i do is just reading and reading and cant get through. So I have still my stock ROM for Vario IV wich is even slower than Wizard custom ROMs, so its annoying a lot and it is still slow after i made all the registry tweaks! I would like to flash new faster ROM but i do not want to do it until i am sure i could reconstruct my stock ROM in case of some warranty isues. First thing i want to say is that i use Windows Vista Bussines x64 so maybe all my problems are in the case of 64bit drivers, but i did not find any compatibility information about all the utils.
1. I went to the thread how to dump and reconstruct Touch Pro ROM. I made all the necesary things but i cant even extract any raw file still get ITReadDisk error which i find in the thread but i did not get any solution.
2. I have downloaded T-Mobile ROM from czech T-Mobile official pages extracted the file RUU_signed.nbh, but i do not know how can i extract it. ROM kitchen did not help, or even if i can use it to reconstruct :-(
3. I tried NBHextract file but i think it is not usable for Touch PRO. I got few files SPL, 2x MainSplash and OS image, all *.nb, but i am not sure if i can use it to reconstruct original ROM.
Point of this, why i want ot do it is: I want to load HardSPL but i want to have backup of my stock SPL if i need to revert my warranty. Any help would be appreciated
I use Calkulin's Kitchen, which makes it easy to extract the RUU_signed.nbh and rebuild it. See the thread here or download the kitchen.
What program did you use to extract the ROM from your device? I used pdocread which worked great. Not sure if that works on Vista x64.
rsw686 said:
I use Calkulin's Kitchen, which makes it easy to extract the RUU_signed.nbh and rebuild it. See the thread here or download the kitchen.
What program did you use to extract the ROM from your device? I used pdocread which worked great. Not sure if that works on Vista x64.
Click to expand...
Click to collapse
I used pdocread.exe file but anytime i tried to dump rom i got the ITReadDisk Error, and any RAW file was not made just the first one with 0B size. Also i have downloaded the Raphael kitchen from http://forum.xda-developers.com/showthread.php?t=411915 and my Symantec endpoint security reported Trojan Horse in RaphaelCustomRUU.exe in Tools directory.
Sounds like it is not 64bit compatible. Any reason your running 64bit Vista? Unless you have a need for it your not going to see much performance difference on a desktop, just a hassle of compatibility problems with hardware that doesn't have 64bit drivers.
If you use Calkulin's Kitchen you will need the imgfstools from the Raphael kitchen you downloaded. They have been patched to allow ROMs to be larger than 128MB.
reason i run 64bit vista is that i have 8GB of RAM because i need to run multiple os in vmware. Will try it from win xp in vmware...
Anyway. Can i flash original ROM with all its parts shipped from T-Mobile to a device which has HardSPL applied? If i did that on HardSPLed HTC Wizard, i would have brick it...that is why i am asking.
Related
Hi there- I inherited an SX56- but can't seem to download new proggies to it! Not too sure if it has PC2002 or 2003, but i can tell you it has:
ROM Version 3.17.03 ENG
Radio: A.20.10
I tried using installing ActiveSync- but I guess I need a serial key or something.
Since I couldn't find a post on how to build with current updates- can someone reply or re-direct to a post that lists what I need to make this baby current so I can install some of the cool utilities for this PDA?
Thanks again!
PS: Im running XDA-developers SW on this baby!
activesync can be freely downloaded from ms's site
and require not serial
if it ask for code when you connect your pda it's the pda's
user set code it wants
ok- got the latest active sync- 4.5 build. I still can't seem to successfully run .msi files or .cab files to and from the sx56. I tried dropping the .cab files to different directories- since its probably looking for PPC2002 files as well to run the program. I also downloaded CNET framework v2.0.2...still can't seem to install programs onto the pocket PC
any ideas?
Cheers!
i think msi files was ment to run from the pc not the ppc
I'm trying to port WM6 AKU 0.7.0 to Atom Life devices. Almost all XIP modules were relocated well, however, giisr.dll always conflicted with coredll.dll. (hd.dll and oxast0.dll also conflicted with others, but they are not core files and can be deleted to avoid issues.) The same problem happened when people tried to port WM5 AKU 3.5.2 to Dell X51v devices, but they later managed to solve it prefectly. No documents about this problem could be found. Please help me. Thank you very much.
BoomerCE said:
I'm trying to port WM6 AKU 0.7.0 to Atom Life devices. Almost all XIP modules were relocated well, however, giisr.dll always conflicted with coredll.dll. (hd.dll and oxast0.dll also conflicted with others, but they are not core files and can be deleted to avoid issues.) The same problem happened when people tried to port WM5 AKU 3.5.2 to Dell X51v devices, but they later managed to solve it prefectly. No documents about this problem could be found. Please help me. Thank you very much.
Click to expand...
Click to collapse
did you connect device in KITL mode to PC with PB6? How did you trace it to giisr.dll? you can also try to just change single module coredll.dll
Actually, this is my next step for the ATOM, but have not started on it yet.
Thank you very much, Mr. Jiggs
About this problem, seems I can't solve it now... I'm going to study further.
Another question is, how can I change the version information, including OS Version, build, AKU, and Language of the ROM file? (Read by bepe's package tool as shown in the picture, not in Version.TXT. I heard that this is stored in some DSM files.) Thanks!
BoomerCE said:
Thank you very much, Mr. Jiggs
About this problem, seems I can't solve it now... I'm going to study further.
Another question is, how can I change the version information, including OS Version, build, AKU, and Language of the ROM file? (Read by bepe's package tool as shown in the picture, not in Version.TXT. I heard that this is stored in some DSM files.) Thanks!
Click to expand...
Click to collapse
Although we can change the version in the DSM, the Atom does not reflect it, and only bepe's package tool can detect the change. For me, it is not advisable to change it. Just use the official files, and they will be reflected.
Hey, you have a new package tool. Where did you get it?
Seems that current version of SRPX tools cannot work properly. I just extract Atom Life's original XIP using MSFLSHTOOL, SRPX2XIP it and then XIP2SRPX, then replace it back (note that I didn't edit anything), and flash the image. The device simply don't boot.
BoomerCE said:
Seems that current version of SRPX tools cannot work properly. I just extract Atom Life's original XIP using MSFLSHTOOL, SRPX2XIP it and then XIP2SRPX, then replace it back (note that I didn't edit anything), and flash the image. The device simply don't boot.
Click to expand...
Click to collapse
how did you do it? step-by-step... Did you use format I send breakdown.bat?
All tools (including the package tool) that I used came from Scoter Kitchen, and your batch had some bugs that it couldn't work. Of course I know how to use these tools, and I successfully extracted and dumped Atom Life's original XIP (WM6 AKU 0.2.1).
And I still need your help editing the version info in DSM because if I don't change it, Package Tool will cause trouble in my complete localization in Atom Life's ROM. (Base ROM: 0404 - Chinese Traditional, Object: 0804 - Chinese Simplified. Now all related keys in registry modded, all modules in IMGFS successfully edited, and .0804.MUI files I placed in fully worked. Flashed and worked perfectly.) Thank you very much.
So it proves that XIP2SRPX tool has bugs and cannot be used on Atom Life's XIP2.
Here is the project I'm working on... Please help me with the only file giisr.dll... Thank you very much!
http://rapidshare.com/files/58185699/XIP.rar
Hello.
I have a question.
I installed WM 6.1 and i really like it. it took a long time till i set everything up and it works really great. Now i want to try some other ROMs. Can i make an image-file of my OS? without SPL and IPL? I have intalled Wizard Service Tools.
I tried to make a back up of my OS with the Option 'READ ROM-> OS Image (bdk 1)'. Then tha programm worked about 10 minutes and created a '*.nb' file. It's 58 MB big.
I have 3 questions:
1. Is that my ROM? i've only seen *.nbf files till now. That's why i am a little bit confused.
2. Is it a safe ROM? no SPL and IPL?
3. How can i flash this ROM back when i need it?
Please answer me.
Thanks in advance
Stefan
I was hoping for the same thing, i have ran several ROMs since joining an i am tired of re-entering the information for my email accounts, passwords, etc. it would be nice if this is possible.
Hi, i made WST and i can answer that
The OS backup produces a 'decrypted' image file that can only be flashed using WST (or pdocwrite.exe). You can, however, 'encrypt' it using a nbf tool and then use a RUU to flash.
BUT... that is the same as keeping the original nk.nbf since the OS image is the same as a CD with WinXP; It comes only with the OS and you must install all the other sw and personal data.
If you want to make backups be sure to backup the User Area that can be read with a image program and some files can be recovered.
I recently have found that to have a rom fit for my needs and to work properly with my exchange server settings, etc. that I need to rebuild roms (easier than starting from scratch). I am not planning on re-distributing them, they are mainly for my use, and others that use a specific exchange server setup like I do.
Anyway onto my main question:
Using the different tools I have found through Google and xda-developers, I have started to extract the radio nb file so that I can build a new NBH with the radio and the rom. I have also toyed with the idea to do the SPL into the NBH so that I don't have to worry if it has been flashed or not. I also will be flashing the roms from my microsd card (which I have been doing with my modified rom already).
Thank you in advance!
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Trancecoder said:
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Click to expand...
Click to collapse
Got it, thanks for the quick reply too!
I noticed your signature, and saw that you have the rilphoneauto. I see an EXT and OEM type file, but I am only familiar with cooking in cabs and making minor entries. I wouldn't know where to begin to add in an OEM or EXT to the roms that I modify/re-cook.
They're basically directories with a slightly varied structure that you put in an appropriate kitchen directory and then select inside the kitchen UI. If you're using the new "visual" kitchen, you should use the EXT package; otherwise the OEM. There are tutorials all over the forums explaining how to use them. I'm probably not the best person to do it anyway since I've only been cooking for a little while
YES I have searched and read before I posted..
I am attempting to cook my own roms for my Exec, I have d/l and installed a number from here and enjoy the process, so I have downloaded the files as suggested and tried to cook.
I can dump the rom OK and sort and fiddle through the files with no issue, but when I then try to build the rom, BUILDOS.EXE comes up with an error
BUILDOS has encountered an error and needs to close...
I found you had to move the OEM and SYS folder back up one level, but then when you run the buildos it now fails with external component has thrown an exception
Windows XP SP3 up to date with patches
Any ideas most appreciated
no one?
Is the kitchen empty?
BuildOS.cmd
To build:
1. Execute BuildOS.cmd (requires .NET to work)
2. After the entire process, your new ROM will be found in \FLASH folder
Nongs said:
To build:
1. Execute BuildOS.cmd (requires .NET to work)
2. After the entire process, your new ROM will be found in \FLASH folder
Click to expand...
Click to collapse
Obviously you have no idea... Have you in fact done this and obtained a result?
The process is complicated and requires much ammendment to the source data to be even able to dump the rom, but to then edit, re-assemble and produce does NOT work using the kitchen indicated in the original posting.
If YOU have been able to do this, then please feel free to document the full an correct steps taken and the changes you made.
buildos
Yes I have.
I would like to recommend you to read
http://forum.xda-developers.com/showthread.php?t=345735&page=5
since post#47
I think same as your problems.
I have cooked by Atom 6.1 cooking set, never found those problems.