So I thought about opening this thread to discuss the technical progress of the "WM6 for Trinity" project...
Hopefully we can keep it technical only!
Goodluck
It's a dead end . Thank you
Just some of my experiences with that....
Porting the Kernel:
I think it makes more sense to use a device which already has a WM6 ROM for experiments on that tropic.
What I've tried...
Device: Universal
ROMs: Full working WM5 and WM6
1. I extracted the kernel from the WM5 ROM
2. I implanted it into the WM6 ROM
3. The offset of the boot partition header is written to one place of the Kernel, so I changed that to match the WM6 ROM
4. Flashed the ROM
Result: Black screen
this shows that the Kernel is not compatible...
theoretical issues:
- it did not work cos I only replaced the Kernel, but not the other OEM files
(don’t think so, cos the other OEM files should be stand alone drivers)
- there is another offset written to nk.exe
(no, cos I wrote a program to completely reorganize the boot section [except of the kernel] and it worked after changing the one known header offset)
- I missed something else or made a mistake...
(No one is perfect)
At first one terminology agreement: when I speak about (wince 5.x) kernel I speak 'bout nk.exe only (mun_rus counts as a kernel all stuff in boot partition. Formaly (excepting some modules/files) this is correct too but a bit uncommon). As near as I can tell bepe as well calls kernel nk.exe only. Please correct me if I'm wrong.
Now my expirement:
rexipped kernel from trinity rom placed in to the hermes one. result: two splash screens then halt. Splash screens means that kernel succesfully passed at least OEMInit. But nothing more. There are two possibilities:
1) kernel is not compatible
2) i've screwed up something during rexipping. complete toolchain is not ready yet and operation is semi-manual. However I have positive expirence in transplating kernel from one WM5 rom to another (with the same rexipping).
I'm giving up particular task of bringing WM6 for trinity for now. And continue to work on rexipping toolchain. Would it make any good for trinity or not it would be useful on many other tasks.
bepe said:
3. The offset of the boot partition header is written to one place of the Kernel, so I changed that to match the WM6 ROM
Click to expand...
Click to collapse
If you are placing sections on different addresses there are many more addresses that should be fixed except romhdr. In addition there is need to fix extensions ptr and copyinfo as well.
(no, cos I wrote a program to completely reorganize the boot section [except of the kernel] and it worked after changing the one known header offset)
Click to expand...
Click to collapse
I've tested your program: either I've missed something or it is unable to rexip (put sections on different places and perform fixups) modules. However boot partition produced after straightforward unpack->pack procedure on 100% working trinity wm5 rom refused to boot.
Oh, no, don't give up!
Seems like you know your stuff, can you just team up with the others, or point them into the right direction (if you think they are straying?)
As near as I can tell bepe as well calls kernel nk.exe only.
Click to expand...
Click to collapse
right, kernel is the same as nk.exe... ok, let’s use nk.exe
If you are placing sections on different addresses there are many more addresses that should be fixed except romhdr. In addition there is need to fix extensions ptr and copyinfo as well.
Click to expand...
Click to collapse
Yes, I placed every possible section to a new place except of nk.exe... that was part of the experiment to see if there are more addresses...
... and there are not, because the rom worked after that
3xcopyinfo and extensions... yes, that’s clear offsets are part of the header... as I said my tool reorganized that without any problems
I think you misunderstand what I meant:
the physical address of the boot section header is written to the NK.exe
this is the beginning of a boot section:
FE 03 00 EA 00 00 00 00 | 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00
45 43 45 43 68 BB 19 80 | 68 BB 19 00 00 00 00 00
red it the offset of the boot section header...
next you’ll see a part of the nk.exe o32[0] data (MODULES\nk.exe\S000)
77 00 73 00 5C 00 00 00 | 68 BB 19 80 00 00 00 00
00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 | 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 | 6D 00 73 00 63 00 6F 00
could this be the problem why your nk.exe port did not work?
I've tested your program...
Click to expand...
Click to collapse
I did not finish the program... it worked for me with my universal rom... I think mun told me it would work on hermes too, at least dumping rebuilding...
sorry,
However I have positive expirence in transplating kernel from one WM5 rom to another (with the same rexipping).
Click to expand...
Click to collapse
that means you must have changed the header offset inside nk.exe
or it was the same offset... but dnot think so
Oh, no, don't give up!
Click to expand...
Click to collapse
Breaking through to bring WM6 on trinity without appropriate fully-working toolchain is just a useless waste of time: now it takes 'bout couple of hours to rexip module (or kernel wich is by some means a module too) check if everything is done correct (and still no warranty of that) and put it to rom. Moreover I'm hm... 80% sure that I've transfered kernel properly in my expirement wich means that probably there is no need to break through at all
From another side with toolchain finished it would be possible to bring WM6 to trinity (or any other modern WM5 device) in minutes or surely state impossibility of that.
if you think they are straying
Click to expand...
Click to collapse
I've clearly stated that at least lwsv is straying but nobody listened / However we have contacts via pm and I'm ready to provide some not too time consuming help.
ps:
@bepe
Result: Black screen
Click to expand...
Click to collapse
just noticed it. I can't be sure 'bout universal but on himalayas and trinity first splash is drawn on early stages of OEMInit (wich is called on very early stage of kernel startup). Black screeen using kernel surely compatible with hardware 99.9% means that kernel even have not started.
bepe said:
that means you must have changed the header offset inside nk.exe
Click to expand...
Click to collapse
as well as many others. pointers to data/code in any moved section should be fixed. And in romhdr pointer to extensions (wich are located in kernel, in trinity/hermes rom just after pointer to romhdr) should be fixed as well. And if you move any section wich copy list points to (nk.exe data section for example) it should be fixed too.
The XIPPort tool dumps a xip section and rebuild it identical, just the order of the TOC entries and the copy entries is not the same.
Also the "realloc P" part works perfectly, without changing something it should allocate the things the same way as MS did it using Platform Builder.
just how I've done it:
1. I dumped the xip.bin
-> rebuilding or reallocating using my tool would result in a identical xip section
2. I deleted the two modules: hd.dll, osaxst0.dll
-> both are not needed, just for debug info
3. Recalculated the whole xip section using my tool
-> reallocating in this state does not create a identical xip section because the deleted modules are using the place next to nk.exe... but reallocating means to fill that with the other modules, so everything after the first nk.exe section is on a new place
4. also the romhdr offset has been changed, so I changed it inside nk.exe
flashing, and the rom is working
Also the "realloc P" part works perfectly, without changing something
Click to expand...
Click to collapse
it is good. until you do not need to reallocate modules sections (because of overlapping regions for example) or you are not moving the kernel. But if you do you should refixup affected module images to get working rom.
flashing, and the rom is working
Click to expand...
Click to collapse
Very strange..I changed nothing then I cliked "realoc P" and flashed new boot section, but my wizard stucked on spl screen. Any thoughts? I compare maps, after realloc procedure it were some chages in Trueffs real addr area
I started to compare some data inside nk.exe of tytn and trinity
I was very impressive when i saw GPS in tytn's kernel)
tytn's wm6 nk.exe (Built on Dec 17 2006)
Code:
...
[color=red].text:8000528C 00000018 unicode [D :: GPS] [/color]
.text:800052A4 00000018 unicode [D :: RIL]
.text:800052BC 0000001A unicode [D :: SIR ]
.text:800052D8 00000018 unicode [D :: FIR]
.text:800052F0 00000016 unicode [D :: CF]
.text:80005308 00000024 unicode [D :: SERIAL_BT]
.text:8000532C 0000001E unicode [D :: SERIAL]
.text:8000534C 0000001C unicode [D :: AUDIO]
.text:80005368 00000022 unicode [D :: BACKPACK]
.text:8000538C 0000001A unicode [D :: WLAN]
.text:800053A8 00000016 unicode [D :: SD]
.text:800053C0 0000001E unicode [K :: KERNEL]
.text:800053E0 00000018 unicode [D :: SPI]
.text:800053F8 00000020 unicode [D :: BATTERY]
.text:80005418 0000001E unicode [D :: TOUCHP]
.text:80005438 00000018 unicode [D :: KEY]
...
trinity's wm5 nk.exe (Built on Dec 12 2006)
Code:
...
.text:80005AB4 00000018 unicode [D :: GPS]
.text:80005ACC 00000018 unicode [D :: RIL]
.text:80005AE4 0000001A unicode [D :: SIR ]
.text:80005B00 00000018 unicode [D :: FIR]
.text:80005B18 00000016 unicode [D :: CF]
.text:80005B30 00000024 unicode [D :: SERIAL_BT]
.text:80005B54 0000001E unicode [D :: SERIAL]
.text:80005B74 0000001C unicode [D :: AUDIO]
.text:80005B90 00000022 unicode [D :: BACKPACK]
.text:80005BB4 0000001A unicode [D :: WLAN]
.text:80005BD0 00000016 unicode [D :: SD]
...
There are much simmilar but in diffrent offsets. Hmm probably we can try use tytn's kernel in some way
mun_rus said:
I started to compare some data inside nk.exe of tytn and trinity
I was very impressive when i saw GPS in tytn's kernel)
Click to expand...
Click to collapse
Nothing impressive in that most htc devices (especially such kindred) share common codebase. If you look deeply you can find even wallaby echo in modern devs firmware.
Hmm probably we can try use tytn's kernel in some way
Click to expand...
Click to collapse
Yes we could. As devices are very similar kernels are the same for 99.9%. But very similar does not mean identical: at least gpio purposes are different and I've strong feeling that there are another minor hw diffs making impossible direct usage of hermes kernel. And as you have some reveng experience you could imagine how hardcore task would be finding out that differences and fixing them (and what probabilities of getting stable working kernel at the end are).
I don't want to tread out of my depth, but could you just explain what it is that HTC would need to do to customise the WM6 Rom for Trinity? Is it just one file (whatever XIP is or nt.exe??)? I mean how much of a big job would it be for them?
This leads on to my second paragraph; is there anyway of slyly contacting an engineer at HTC to syphon off this file (presuming it is a small file that would give you the answers you need)? Is this frowned apon in the xda-developer industry? Or is this common practice? Do any of you know someone at HTC? Could Orange leak this file? Or would they just get HTC to write their ROMS?
I don't want to stand here flaunting myself in my nappy but I just don't know about these things...
Thanks for answering
what it is that HTC would need to do to customise the WM6 Rom for Trinity?
Click to expand...
Click to collapse
I'm almost sure that nothing except they've already done. But I'm sure as well that they are not going to release WM6 for trinity: look they have a bunch of (not so different) new devices needed to be sold and releasing new os for (olready sold) old devices would not be a very wise idea from a sales department point of view.
No, I'm sure there won't be an official release, but I was talking more about an unofficial leak of a file.
Looks like the progress is slow
FuzzMunky said:
No, I'm sure there won't be an official release, but I was talking more about an unofficial leak of a file.
Click to expand...
Click to collapse
There is no wm6 for trinity yet...even test rom
mo7al said:
Looks like the progress is slow
Click to expand...
Click to collapse
Yes..it's so. Now have to make my tests with wm6/wm5 roms on my wizard...Try to realease my thoughts and ideas..Im going to recieve trinity till end of nex week or begin of week after. So, i hope progress will speed up
On the basis of which we shall do updating Rom for HTC_Trinity, I have already made and have successfully tested on Hermes - http://forum.xda-developers.com/showthread.php?p=1165177#post1165177
Related
can someone please point me to where i can get ROMs for the new iPAQ 211.
i would like to upgrade to 6.1 if possible. (HP isn't gonna do it....)
thanks
hx2000???
http://forum.xda-developers.com/showthread.php?t=383173
no, like the 210, 211, 212, 213 or 214...
No such beast exists. You are stuck with 6.0 until someone hacks it. But what is wrong with the version you have?
Alan
alan sh said:
No such beast exists. You are stuck with 6.0 until someone hacks it. But what is wrong with the version you have?
Alan
Click to expand...
Click to collapse
Not exactly wrong. But the existing ROM is simply very BUGGY. It can´t compare to the cooked one I´d installed on my past Loox C550 device. There´d be no end to whatever goes wrong with Wi-fi and Bluetooth, CF card support, power management , general instability of the system, various software incommatiblity issues etc. But so far we have to live with it.
Hikoki said:
Not exactly wrong. But the existing ROM is simply very BUGGY. It can´t compare to the cooked one I´d installed on my past Loox C550 device. There´d be no end to whatever goes wrong with Wi-fi and Bluetooth, CF card support, power management , general instability of the system, various software incommatiblity issues etc. But so far we have to live with it.
Click to expand...
Click to collapse
Yup, my 211 is now on the shelf and waiting for an update. My hx4705 is now back in service with Kozura's WM6.1 v5 ROM. I have lost more data with the 211 than ALL the IPAQ's I have used over the years...combined. It is a sad day when the 'development ROM's - not to be used for daily operation' are more stable than the ROM in this new device!
So, I hear that the 21x series bootloader is difficult. Does anyone have details of what the roadblocks are?
dceggert said:
Yup, my 211 is now on the shelf and waiting for an update. My hx4705 is now back in service with Kozura's WM6.1 v5 ROM. I have lost more data with the 211 than ALL the IPAQ's I have used over the years...combined. It is a sad day when the 'development ROM's - not to be used for daily operation' are more stable than the ROM in this new device!
So, I hear that the 21x series bootloader is difficult. Does anyone have details of what the roadblocks are?
Click to expand...
Click to collapse
if you know how to enter the bootload mode of hp21x,I can make a rom for you
bluegatar said:
if you know how to enter the bootload mode of hp21x,I can make a rom for you
Click to expand...
Click to collapse
Hi,
a friend has an ipaq 214 and has difficulties with the original rom (CF-GPS, Wlan).
Therefore I'm also interested in a 6.1 ROM.
I'll call HP on monday to get support - maybe I should ask them how to get into the bootloader mode (if there is any)?
Is there anyone who could really make WM6.1 rom for 214?
That would really be something...
i'm looking for english rom for hp 214. Can someone upload it?
bluegatar said:
if you know how to enter the bootload mode of hp21x,I can make a rom for you
Click to expand...
Click to collapse
We need ENGLISH Rom!!! First thing - find rom, bootloader - is next task.
if you tell me how to copy my rom from pda, i can send you
http://www.handhelds.org/moin/moin.cgi/HpIpaq214HowTo
Looks like someone has figured out how to put their Ipaq 214 into bootloader mode. Their page says to hold down the Calendar & Windows keys and then soft-reset.
Any luck with a 6.1 rom for ipaq 2xx yet?
bluegatar said:
if you know how to enter the bootload mode of hp21x,I can make a rom for you
Click to expand...
Click to collapse
Any luck yet making a wm 6.1 rom for ipaq 21x?
I have the English ipaq 211 version and would really like to try 6.1 to see if it fixes any of the 6.0 instability issues.
Here's the link again the other poster referred to for getting into bootloader mode on the ipaq:
http://www.handhelds.org/moin/moin.cgi/HpIpaq214HowTo
Thanks! tom
Good work. Now the work is how to get the rom file.
My most wantted thing is flashing the 212 to the chinese rom.
Hi,everybody, I have got the ipaq 212 english rom. And I can extract it.
Can somebody give me the ipaq 214 Chinese rom?
The method is :
HKLM\Security\Policies\Policies
valuename '00001001' was set to dword:2, change it to dword:1
use pdocread tools to do this:
pdocread -l
"
224.38M (0xe060000) DSK1:
| 1.50M (0x17f000) Part00
| 2.13M (0x220000) Part01
| 57.88M (0x39e0000) Part02
| 162.88M (0xa2e0000) Part03
1.91G (0x7a1fc000) DSK2:
| 1.91G (0x79f00200) Part00
1.88G (0x78800000) DSK3:
| 1.88G (0x787e0600) Part00
24.75M (0x18c0000) IPQ1:
| 24.75M (0x18bf000) Part00
STRG handles:
handle e6f4f7da 24.75M (0x18bf000)
handle a701d116 1.88G (0x787e0600)
handle 4796c202 1.91G (0x79f00200)
handle 67c8652a162.88M (0xa2e0000)
handle 67c9a11a 57.88M (0x39e0000)
handle 07c9a0f6 2.13M (0x220000)
handle a7c9a0ae 1.50M (0x17f000)
disk e6f4f7da
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a701d116
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4796c202
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 67c8652a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 67c9a11a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 07c9a0f6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a7c9a0ae
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
"
then
pdocread -w -d DSK1: -b 0x800 -p Part02 0 0x39e0000 Part02.raw
the part02.raw is the rom file
I can use viewimgfs tools to extract the part02.raw file.
Now can some body flash the rom ?
You can download the english rom file from this
http://bbs.pdafans.com/viewthread.php?tid=649400&extra=page=1&filter=type&typeid=240&area=
Can somebody try to use pdocwrite command to write the ROM?
finally something is moving with 21x roms....
great news, now we just need to find someone smart, to make wm6.1 rom!
thank you everyone for informations!
WODP
The good news is I have got the English and Chinese ROM file.
The bad news is :when I try to write the ROM with pdocwrite tools, it failed, the pdocwrite tools said "media protected". So I can't flash the rom file to the machine now.
So we need the solution of get the ipaq to the bootloader mode or the way to update with sd card.
Can someone help ?
wizard_mini said:
The good news is I have got the English and Chinese ROM file.
The bad news is :when I try to write the ROM with pdocwrite tools, it failed, the pdocwrite tools said "media protected". So I can't flash the rom file to the machine now.
So we need the solution of get the ipaq to the bootloader mode or the way to update with sd card.
Can someone help ?
Click to expand...
Click to collapse
I'm assuming that you've already tried this http://www.handhelds.org/moin/moin.cgi/HpIpaq214HowTo
Hi guys,
I just tried out the HTC Touch Pro, aka Raphael today.
it is seemly blazing fast as compare to HTC Diamond/Victor...
I have also found out it has a newer radio as compare to the 1.00.25.3 that we are having on Diamond.
Here are some photos, i will add in the snapshots later of the os later...
here's the link to the dump for part00.raw to part02.raw:
http://www.fs2you.com/files/a58787a1-4e64-11dd-a84e-00142218fc6e/
Guys, thanks for the mirrors. Hope the dump is useful one way or another.
Once i have the pre-release version of the rom, i will upload it. but might takes weeks to months before i can get my hands on it.
http://www.filefactory.com/file/062f...M (00to02).zip
http://www.zshare.net/download/15042237a31e9b75/
http://www.mediafire.com/?yybn0wtzgtm
what's the OS build in this one?
C:\Diamond>pdocread.exe -l
457.50M (0x1c980000) DSK1:
| 3.12M (0x31f000) Part00
| 4.38M (0x460000) Part01
| 109.50M (0x6d80000) Part02
| 340.50M (0x15480000) Part03
STRG handles:
handle 6fdd38da340.50M (0x15480000)
handle afeac736109.50M (0x6d80000)
handle 4feac712 4.38M (0x460000)
handle efeac6ca 3.12M (0x31f000)
disk 6fdd38da
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk afeac736
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4feac712
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk efeac6ca
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dumped Completed. But I am not sure i can release this dump since there is HTC Debugs tools in them.
htctouchp said:
what's the OS build in this one?
Click to expand...
Click to collapse
wow, you are fast.
give me a minute here.
i am still dumping the rom.
i will attached the screenshots laters, with device info and windows version. btw, its not retail version.
a screenshot of the bottom edge (like the last screenshot above) but side by side would be great, just to compare the depth differneces. ROM and radio versions would be good too!
@ruffruff:
It'd be nice if you could post the dumps on mediafire.
I guess the radio should be compatible with the Diamond's since it's basically the same hardware; did anybody find out how to dump / flash radios on the diamond yet?
vlad69uk said:
a screenshot of the bottom edge (like the last screenshot above) but side by side would be great, just to compare the depth differneces. ROM and radio versions would be good too!
Click to expand...
Click to collapse
is this the one you are looking for?
btw, i apologised for my poor, lousy photo taking (taken with Nokia N82)
I must have one, is there possibility to buy raphael somewhere.
adwinp said:
@ruffruff:
It'd be nice if you could post the dumps on mediafire.
I guess the radio should be compatible with the Diamond's since it's basically the same hardware; did anybody find out how to dump / flash radios on the diamond yet?
Click to expand...
Click to collapse
hi adwinp,
mediafire will be out of the question as i am in a part of the world where mediafire seems to in-accessible to me. i will try to find a space to upload the parts.
but, is the rom useful in anyway? and which parts are the useful ones? sorry as i am no cooker, just learn to dump roms.
ruffruff said:
is this the one you are looking for?
btw, i apologised for my poor, lousy photo taking (taken with Nokia N82)
Click to expand...
Click to collapse
Perfect, that's just what i was looking for, thanks ruffruff
ruffruff said:
hi adwinp,
mediafire will be out of the question as i am in a part of the world where mediafire seems to in-accessible to me. i will try to find a space to upload the parts.
but, is the rom useful in anyway? and which parts are the useful ones? sorry as i am no cooker, just learn to dump roms.
Click to expand...
Click to collapse
Part00.raw, Part01.raw and Part02.raw
If you have an FTP I can mirror it for you.
hi ruffruff.. eagerly waiting for you to post the rom so we all can port to our devices
ruffruff said:
wow, you are fast.
give me a minute here.
i am still dumping the rom.
i will attached the screenshots laters, with device info and windows version. btw, its not retail version.
Click to expand...
Click to collapse
Love if you could post the radio, current one on Diamond is really poor.
adwinp said:
Part00.raw, Part01.raw and Part02.raw
If you have an FTP I can mirror it for you.
Click to expand...
Click to collapse
i am uploading the parts onto a fs2you.com
btw, i am uploading the entire thing ...
maybe i shouldn't. i will upload part 00 to part 02 as requested.
stay tuned but be patient as my connection ain't that fast.
fs2you is slow
If mediafire isn't available for you, I'd recommend filefactory, zshare or badongo.
You can compress with 7zip (lzma achieves better compression than rar, zip)
adwinp said:
fs2you is slow
If mediafire isn't available for you, I'd recommend filefactory, zshare or badongo.
You can compress with 7zip (lzma achieves better compression than rar, zip)
Click to expand...
Click to collapse
Hi bro,
I have uploaded the files to
http://www.fs2you.com/files/a58787a1-4e64-11dd-a84e-00142218fc6e/
I will try your recommendations when i get home.
but in the mean time, please bear with the speed on fs2you.com
one other thing is that, this is not a retail rom.
hopefully it will be useful for the cookers in the xda community.
or else, i will be making a fool of myself and going through meanless hassle to upload the rom
Thanks for the effort.
You are of course encouraged to post any updates.
^.^
ty so much ruffruff, looking forward for some great cooker to combine the advantage from this rom to our DIAMOND rom
If anyone manages to download this, plz upload it to mediafire, badongo, filefactory or zshare.
fs2you breaks the connection after a few Mb's.
adwinp said:
If anyone manages to download this, plz upload it to mediafire, badongo, filefactory or zshare.
fs2you breaks the connection after a few Mb's.
Click to expand...
Click to collapse
uploading to mediafire 22 minutes remaining
HTC WP7 NBH Dump/Rebuild:
NBHImageTool
flash.store.bin Dump/Rebuild (dumped as os.nb in NBHImageTool):
(tool creation pending)
IMGFS Dump:
Combine xidump with the attached cecompr_nt.dll supporting XPH
IMGFS Build:
Combine imgfsfromdump with the attached cecompr_nt.dll supporting XPH
XIP/ULDR Dump:
dumprom works well for this.
XIP/ULDR Build:
(tool creation pending)
I'll be posting updates in my twitter, which you can reach by clicking the image in my signature below.
That's great
Thanks
awesome, best of luck;]
Thank for this
thanks. let us know if you need something...
i'm sure we can get more donations if needed...
Good luck in your attempt my friend.
A small appreciation from my side
Transaction ID: 3HV21374WY1903845
Relocation Module SYS/Dump:
Creating tools...
Command Dump IMGFS:
Code:
xidump imgfs.bin
Create Packages from Dump:
Combine Packagebuilder with the attached cecompr_nt.dll supporting XPH
Another method Dump XIP:
XIPPort - Bepe's
Region PagePool:
during the detection..
Generation File imageinfo.txt:
Command:
Code:
iitp [ -p physfirst ]
Download: IITP - imageinfo.txt producer.
XPR to XPH Compression:
Open the file os.nb.payload in HEX Editor. Find this Lines:
Code:
F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC ř¬,ťăÔ+M˝0‘nŘO1Ü
01 00 00 00 01 00 00 00 01 00 00 00 34 00 00 00 ............4...
08 00 00 00 00 02 00 00 00 10 00 00 58 50 52 00 ............XPR.
And change to:
Code:
F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC ř¬,ťăÔ+M˝0‘nŘO1Ü
01 00 00 00 01 00 00 00 01 00 00 00 34 00 00 00 ............4...
08 00 00 00 00 02 00 00 00 10 00 00 58 50 52 00 ............XPH.
Save this file. Get this library cecompr_nt.dll (attached in first post), then insert to TOOLS folder from your Kitchen ROM.
Download cecompr.dll (attached) and overwrite it in your XIP.
Useful module to compress XPH:
You're doing great work,
I hope you'll succeed.
Good luck
lets keep this on track, roms will be developed as they can be, asking for specific hardware won;t make any difference and only take the threads off track.
this is a nice clean thread for the real WP7 work going on, looks like we have sorted the compression issue,
looking forward to what Da_G finds with the JTAG on the HD2.
chrispilot2293 said:
why do you say that about Topaz how do you know that we wont get it.
Click to expand...
Click to collapse
Lots of posts in the other threads on this topic. There's lots of reasons but the main one is that non-Cortex A8 (ie Snapdragon) devices are not capable of executing code compiled for the ARMv7 instruction set. WP7 is compiled under ARMv7. To recompile for ARMv4/5/6 would require the original source code to WP7 which there's practically no chance of getting. Even IF that somehow leaked out, it would still run so poorly that it would be unuseable.
good luck da_g. endevours from indian in australia
What is difference between XPR and XPH? More importantly, I'd love to know how to rebuild cecompr_nt.
Does your cecompr_nt_xpr_xph.dll still support lzh?
If XIP/ULDR can be dumped w/ existing tools, what prevents existing tools being used for reconstruction?
gguruusa said:
What is difference between XPR and XPH? More importantly, I'd love to know how to rebuild cecompr_nt.
Does your cecompr_nt_xpr_xph.dll still support lzh?
If XIP/ULDR can be dumped w/ existing tools, what prevents existing tools being used for reconstruction?
Click to expand...
Click to collapse
No.... only XPR/XPH
Just made my donation. Just for the effort your giving. Thanks.
Just sent you a donation, looking forward to rocking my HD2 with Win7! Thanks man!
didn't the leaked spec sheet of wm7 state armv6 and above?
am i just behind the times
thanks for everyones work
Da_G said:
HTC WP7 NBH Dump/Rebuild:
NBHImageTool
flash.store.bin Dump/Rebuild (dumped as os.nb in NBHImageTool):
(tool creation pending)
IMGFS Dump:
Combine xidump with the attached cecompr_nt.dll supporting XPH
IMGFS Build:
Combine imgfsfromdump with the attached cecompr_nt.dll supporting XPH
XIP/ULDR Dump:
dumprom works well for this.
XIP/ULDR Build:
(tool creation pending)
Click to expand...
Click to collapse
Amazing work Da_G! Thanks for sharing your knowledge!
zole2112 said:
Just sent you a donation, looking forward to rocking my HD2 with Win7! Thanks man!
Click to expand...
Click to collapse
It is not certain that it will work, dont get your hopes up or your kickers in a twist if it comes do nothing.
Silently hoping it does however but we shall have to wait and see.
ID transazione: 6NA49355LX5868833
A small gift for your great work
Please let us Know if Donations can help, I would invest $100 or even more so that the HD2 sees the Light.
and Please guys, we invested and accepted donations to buy an HD2 Plus the Trace32 App, so let's focus on developing Win 7 for HD2 currently, later, I think that other devices can reap the benifits too.
Best of Luck to you Da_G
Will
Hi everydbody,
i'm working on a software to change oem and channel id for windows store (8.0, maybe 8.1...)
i've managed to see surface pick, or lenovo pick on my asus vivotab, but i don't know other oem channel ID.
in order o make a database, i need help !
could you go to: (win+R)
%localappdata%\Packages\WinStore_cw5n1h2txyewy\AC\Microsoft\Windows Store\Cache\0
and post in reply this file with your pc model in comment :
0-Channel-https∺∯∯next-services.apps.microsoft.com∯browse∯6.2.9200-1∯670∯Channel.dat
this file doesnt contain any personal data, juste channel and Oem ID
thanks!
feherneoh said:
09 AA 98 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Lenovo B560
Click to expand...
Click to collapse
Hi ferneoh
thank you, if you replace 09 AA 98 by 97 C5 98 for exemple you willhave access to samsung picks.... but i can't download from oem store for now...
My Surface RT only have file "0-Channel-https∺∯∯next-services.apps.microsoft.com∯browse∯6.2.9200-1∯670∯Channel∯Surface%20RT.dat"
ฺู™ 0 0 0 0 1 0 9 8 9 4
That all from it.
That file is a binary data file. Opening it notepad doesnt represent the actual data (although it does attempt to parse it as plain text anyway).
I'd love to be able to use this to install Nokia's proprietary apps onto my Surface... please make this happen!
Anyone looked into this, yet?
While looking for a way on linux to update my bootloader to use a real recovery partition, I found this little gem:
munjeni said:
Here is aditional trick to install openbootloader without needs for emma:
Code:
//===========================================================
// Rhine S1 Boot Config Data
//
// Config Data Description: http://metadoc.sonyericsson.net/?DOCS=1/15935-5/FCP1191274 PA2
// Honami
//
//
//
// Created: 20150417 1730
// Author: Magnus Strandh, 23048553
//
// Specification document: 8/159 35-LXE 108 010, Rev PA4
// Format:
// [TAPartition<HEX8>]{1}
// [UnitID<HEX32> UnitSize<HEX16> Data<HEX8>{UnitSize}]{n}
//===========================================================
02
// this enables recovery mode (aka installs openbootloader)
0000084f 0054 1A CE 28 00 01 00 06 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 05 00 05 83 02 00 10 02 00 05 85 0A 00 02 00 A9 09 BE BA A9 09 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01
000008fd 0001 00
Click to expand...
Click to collapse
I would like to understand more about this protocol. Was it created by Qualcomm? Sony/Ericsson?
What tools use this protocol? I understand that Androxyde's FlashTool is supposed to do the right thing when it finds this in a .ta file packed within an .ftf file, but FlashTool is huge, and I don't like the idea of reading all of its source code just to find the parts that relate to this protocol.
The Config Data Description URL above is broken; metadoc.sonyericsson.net no longer exists. Is the referenced document still available somewhere? Is there any other documentation?
I just tried my luck googling Markus Strandh at Ericsson and found this profile at LinkedIn. Job desription says
Senior Sw Architect at Sony Mobile Communications
Click to expand...
Click to collapse
. So he might as well be the author of the document. And if he is he might know where to find that file you're looking for.
In case you don't have a LinkedIn account let me know
Thanks. I don't do LinkedIn, but I might try to find his contact info once I know a little more.
I'm hoping someone here (@munjeni? @Androxyde?) can chime in with which programs are known to apply these files.
I found munjeni's newflasher today. The source code is far easier to understand than Flashtool, and although it doesn't answer all my questions, it does help reveal how these bootloader config files are supposed to be applied to a device. Nice.