Develop Bugs

Progress of WM6 for Trinity Project

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

[FIXED!] - BuildOS producing Windows error on opening

I'm really sorry to be starting a new thread, but I've been racking my brains over this problem and haven't got anywhere yet. I know it's not the application so it must be something I've done, just not sure what!
Until today I have been able to use the BuildOS.exe in both Pandora and Core's kitchens without problem. Haven't tried using it for a few weeks, but with the new OS build today tried Pandora. Unfortunately, when I try to open BuildOS, it reports it has encountered a problem and needs to close. It offers the choice of reporting to Microsoft or not (reporting produces no suggested fixes).
Have uninstalled .NET Framework 3, 2, 1.1 and 1 and then re-installed them from Microsoft Update but at each stage the error message has been the same. I've also tried Googling for problems with BuildOS, but each just suggests installing .NET Framework 2. Searching for the error message codes didn't producing anything either.
I'm attaching the first screen of the error message but cannot work out how to copy and paste the actual error (it's unselectable).
If anyone has any ideas at all, I'd really appreciate them as I'm out. Thanks for reading this post and please don't flame unless they're REALLY funny!

The attachment doesnt really give much information..
Try print-screening the error and paste it into paint then cut out just the error and post it.. though im guessing it just says something lke unhandled exception or something like that..
You can also try looking around the system error logs in Control Panel\Administrative Tools\Event Log where you might find some details of the error.
have you installed or uninstalled anything in those few weeks?

the only thing I get from that log file is the mscorelib - .NET Framework...
Maybe try MS .NET Compact FW? I have 1.0 SP3 and 2.0 SP1...

Step by step
Lets try to isolate the problem:
Step 1: Try to use an older version of pandora, if its working something is wrong with your download of the latest version.
Step 2: You said that you haven't use the kitchen for some weeks. What have you installed and/or deinstalled since the last use of the kitchen? Maybe another program on your desktop computer is in conflict with .net or the kitchen.

Problem located, just got to fix it now!
Thanks for the suggestions guys, should've thought of the event viewer myself! D'oh!
The report viewer shows the problem is in my .NET 2 installation, so at least I know where to concentrate now.
Time for the big stick with the nail in it, I think!
Thanks again Sam and matt. I know you're both very busy and really do appreciate you taking the time to help.
EDIT: Sorry Gerald, your post showed up while I was typing. Thank you very much for the suggestion and bringing me back to sanity! Will try an older version first, just in case, and then going to play around with my .NET installations.

mattk_r said:
Maybe try MS .NET Compact FW? I have 1.0 SP3 and 2.0 SP1...
Click to expand...
Click to collapse
Uhh, in my world .NET CF runs on a device.

The problem continues...
Bugger - tried a shortcut and it didn't work! Copied the Pandora setup files and installed them on my laptop, only for that to come up with the same error message!
The laptop has very little installed on it and has only been up and running from a fresh install for two weeks. I've got basic drivers, AVG Anti-virus, Spybot and MS Office 2003 installed and that's about it. It's also completely up to date on MS Updates (I'm anal like that) so has .NETs up to 3.0 installed.
I also tried downloading Core's kitchen onto the laptop but again the BuildOS in that reports the same error.
The error shows under Event Viewer > Application as:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 14/08/2007
Time: 21:07:36
User: N/A
Computer: MINI-LAPTOP
Description:
EventType clr20r3, P1 buildos.exe, P2 0.0.0.0, P3 45fef3bf, P4 mscorlib, P5 2.0.0.0, P6 461eee3d, P7 331e, P8 119, P9 system.io.directorynotfound, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 62 00 75 00 69 00 .b.u.i.
0018: 6c 00 64 00 6f 00 73 00 l.d.o.s.
0020: 2e 00 65 00 78 00 65 00 ..e.x.e.
0028: 2c 00 20 00 30 00 2e 00 ,. .0...
0030: 30 00 2e 00 30 00 2e 00 0...0...
0038: 30 00 2c 00 20 00 34 00 0.,. .4.
0040: 35 00 66 00 65 00 66 00 5.f.e.f.
0048: 33 00 62 00 66 00 2c 00 3.b.f.,.
0050: 20 00 6d 00 73 00 63 00 .m.s.c.
0058: 6f 00 72 00 6c 00 69 00 o.r.l.i.
0060: 62 00 2c 00 20 00 32 00 b.,. .2.
0068: 2e 00 30 00 2e 00 30 00 ..0...0.
0070: 2e 00 30 00 2c 00 20 00 ..0.,. .
0078: 34 00 36 00 31 00 65 00 4.6.1.e.
0080: 65 00 65 00 33 00 64 00 e.e.3.d.
0088: 2c 00 20 00 33 00 33 00 ,. .3.3.
0090: 31 00 65 00 2c 00 20 00 1.e.,. .
0098: 31 00 31 00 39 00 2c 00 1.1.9.,.
00a0: 20 00 73 00 79 00 73 00 .s.y.s.
00a8: 74 00 65 00 6d 00 2e 00 t.e.m...
00b0: 69 00 6f 00 2e 00 64 00 i.o...d.
00b8: 69 00 72 00 65 00 63 00 i.r.e.c.
00c0: 74 00 6f 00 72 00 79 00 t.o.r.y.
00c8: 6e 00 6f 00 74 00 66 00 n.o.t.f.
00d0: 6f 00 75 00 6e 00 64 00 o.u.n.d.
00d8: 20 00 4e 00 49 00 4c 00 .N.I.L.
00e0: 0d 00 0a 00 ....
I know this now definitely isn't a WM6 problem but I'm adding this info in case one of the great XDA Dev minds knows the solution, and in case another user like me experiences the same problem - you're not alone and I'll update the thread when I find the solution!

Here's a stab at it (albeit a simple one). When using Pandora, do you have everything in the proper folder structure? The following applies:
(in this example, everything is thrown into a main folder "Pandora")
- Pandora (parent folder)
- BuildOS.exe (file)
- CreateROM.bat (file)
- pkgcommon.dll (file)
- OEM (sub folder)
- ROM (sub folder)
- SYS (sub folder)
- TOOLS (sub folder)
If you don't follow this hierarchy, Windows will shoot an error out at you.
Good luck!

Thanks Taurus, good suggestion. I've also got an inconsequential Readme.txt file in there too, but other than that - all present and correct!
Again, thanks for all your suggestions guys and once I find the solution I'll be sure to post it up.

You run buildOS from the command line, make sure you cd to the folder containing OEM/SYS/ROM and TOOLS .... THEN run buildOS from wherever it is by typing the full path into cmd, or even better add buildOS to the PATH variable .
so you need to follow this kind of procedure:
Code:
cd c:\ROMFOLDER (ENTER)
then...
c:\ROMTOOLSFOLDER\BuildOS (ENTER)
remember ROMFOLDER and ROMTOOLSFOLDER should be replaced by the paths you use.....its a PITA but thats how it runs.

Confused Stu said:
Thanks Taurus, good suggestion. I've also got an inconsequential Readme.txt file in there too, but other than that - all present and correct!
Again, thanks for all your suggestions guys and once I find the solution I'll be sure to post it up.
Click to expand...
Click to collapse
No problem. I just wanted to clarify what I meant, as I don't know if I was that clear.
I've attached a shot of everything the way it should look. Anyhow, it sounds like you have it right already, but I thought I'd just float that your way.

vp3G said:
Uhh, in my world .NET CF runs on a device.
Click to expand...
Click to collapse
It gets installed with VS Team Suite 2k5, probably since it has the CE mobile device emulators included.
Confused Stu - if you're still having trouble with .NET, let me know. I supported this stuff for M$, and know a few tricks to getting it cleaned up and installed.

Only common factor - interface between keyboard and chair!
OK, I've spent this evening wiping and rebuilding my laptop. It's got XP SP2 on it, then added the laptop drivers, the Kitchen and ran all the Microsoft Updates until only the .NETs were left.
Tried running BuildOS with no .NETs installed, and it came up with a message telling me the application wasn't in the correct state and re-installing it might help.
Installed .NET 1 (same message on trying to open BuildOS), then installed the updates for .NET 1 - same message. Installed .NET 2 and immediately got the original error I was getting on my home PC and other laptop! Went on to install the updates for .NET 2 and finally .NET 3 - but the same error kept coming up.
I've now got this same error coming up my Home PC (self-built), my Dell laptop, and my newly rebuilt Medion one! I've got no common files besides the MS Updates and no common components. Beginning to think maybe it's just plain personal!
Matt - if you can help at all with my .NET problems, I'd be ridiculously grateful. Alternatively, if anyone can suggest another avenue I can try please post it up - I'm almost out of ideas!
I've got another fresh install going on at work (Dell desktop this time) so tomorrow I'm going to try installing only .NET 1 and .NET 2 - not even any other MS Updates. Then if i install the updates one at a time I might be able to work out the problem one. Still not sure why I'm the only person affected by this though?

First of all, you are not alone, have a look at:
http://www.google.at/search?hl=de&q...time+2.0+Error+Reporting+Event+ID:+5000&meta=
Now for the bad news: I checked the first ten posts or so, they recommend to debug the code. But as its running on other machines without any problems it must be something within your .net installion.
man, this is strange.

I had a similar problem with BuildOS but with me it happened anytime I tried to add a package to the OEM folder.
Have you made any changes to anything from the Kitchen?
Matt said that you can't just add a package because its signed ( or something).

FIXED!!!!
Allan1 - you're a star!!!!
I've just deleted out the OEM (and SYS) folders, unzipped the v6 kitchen again and it's worked perfectly! Looks like my problem was I was unzipping the v6.1 (beta) OEM over the top of the existing OEM and that was causing my problems.
Don't I feel like a complete doughnut!
Sorry for wasting everyone's time, and THANK YOU very, very, very much for everyone's help and suggestions on this. It's really touching that so many people were willing to try to help me out.
Now commence the "what an idiot" flaming if anyone wants to - it's justified!

No probs!!

allan1 said:
I had a similar problem with BuildOS but with me it happened anytime I tried to add a package to the OEM folder.
Have you made any changes to anything from the Kitchen?
Matt said that you can't just add a package because its signed ( or something).
Click to expand...
Click to collapse
good looking out...just encountered this problem in HYPERCORE....driving me insane why it wasn't working cuz I just built 3 .nb's in the last few hours.
thanks alot

Anyone interested in HTC Raphael ROM Dump? (Dump uploaded)

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

[DEV] Oem channel Id Modifier

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?

Xperia open bootloader: What is this TA / bootloader update protocol?

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.