yashsingh1/xdaforums huggingface dataset:
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Yeah lokiwiz didn't work. The sector for the cid block doesn't seem to be the same for the juno(though it is for a lot of devices). I'm going to see if unlock.exe is in the software package from the excalibur. Thanks!

EDIT: unlock.exe isn't in the excalibur software update
[Non-Touchscreen Windows Mobile Other] pixelwix:
nice ill ckeck in with jocky to see if hes made progress...
[Non-Touchscreen Windows Mobile Other] pixelwix:
nice ill ckeck in with jocky to see if hes made progress...

looks like we might have a spl baypass sometime tomorrow... :)
[Non-Touchscreen Windows Mobile Other] freyes01:
Hi pixelwix

Are you rewriting the CID unlocker that you mentioned at http://xdaforums.com/showthread.php?t=329605 ?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Great!! I also PM'd littleclown about the unlock.exe in the excalibur thread. He said he'd email it tomorrow

Looks like we'll have an early wm6.1 on our phones tomorrow!:)
[Non-Touchscreen Windows Mobile Other] pixelwix:
i''m not jocky is, i pm'ed him about making one for us and he said sure.. i urge you all to donate to him once he's done :)
[Non-Touchscreen Windows Mobile Other] shadowmike:
if this installs on my phone... create a list and whoever contributed will get a donation !
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Should I upload it here? I don't want some other people getting the idea that this is a final version. This is a really early test and I doubt if it will even work properly.
[Non-Touchscreen Windows Mobile Other] pixelwix:
yeah upload it to rapid or mega, pass protect the rar and make sure you stress thats its a beta, that way we don't don't have 500people saying we ****ed up thier phones
[Non-Touchscreen Windows Mobile Other] freyes01:
The image it's probably 50+Mb

If you state that this is an experimental-alpha-install-at-your-own-risk version it shouldn't be a problem.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
EDIT: check latest post for working test rom image!
[Non-Touchscreen Windows Mobile Other] freyes01:
I download the Kaiser version but I couldn't find the CID unlock tool. Do you have it?
[Non-Touchscreen Windows Mobile Other] pixelwix:
not yet still waiting on jocky to send me the files or pm me.

jocky just pm'ed me he said it should be ready in 2-3 hours or so...

i'm just hopeing it works.
[Non-Touchscreen Windows Mobile Other] shadowmike:
so any update ?

downloading the 2 files listed above, also what all is in this build ? the shadows original rom added with files or ?
[Non-Touchscreen Windows Mobile Other] jockyw2001:
pixelwix is testing the SSPL and USPL which I sent him

After he confirms correct working I will upload them.
[Non-Touchscreen Windows Mobile Other] shadowmike:
sweet thats great news.

now should i us the kaiser version or the dash ? if this works and all.

so this unlocker will allow these ruus to install ?
[Non-Touchscreen Windows Mobile Other] pixelwix:
sorry guys, i just got back from the gym... just to update you guys the uspl seem to work i think it flashed ok.. but the rom didn't flash it gets to 100% and and then i get this error [226]: Flash Write

Flash write error happened. Please check your T-mobile Shadow

this was with the excalibur version... so now i have to flash back to the t-mobile one and do the USPL again and try the kaiser one...

just so everyone know everytime you flash an officail rom you have to do the USPL again, its not a hardSPL
[Non-Touchscreen Windows Mobile Other] jockyw2001:
I think the rom you try to flash is too large and is 'overflowing' nand flash.

You should do following test: run sspl and flash uspl, extract (NBHExtract) the OS from an original rom. You'll get a .nb, then make a .nbh out of it (Dark Simpson) and flash it. If that works you know that uspl works bulletproof and what the OS size should be.

You can download the sspl/uspl test versions from here:

SSPL:

Download-Link #1:

http://rapidshare.com/files/105981665/Shadow_SSPL-JumpSPL.zip.html

USPL + RUU:

Download-Link #1:

http://rapidshare.com/files/105981821/RUU.zip.html

Once they are confirmed to work to flash a cooked OS I will publish them in a separate thread.

Note: should be only used by those who know what they are doing. I take no responsibility if any of these tools brick your device
[Non-Touchscreen Windows Mobile Other] ND4SPD:
It works now. I thought that I since I had already app unlocked it, I wouldn't need to now. This time I did it and it works. Thank you jockyw2001! I've just been able to successfully update with a custom rom image. I took your advice and just made used the original rom's OS.nb file.
[Non-Touchscreen Windows Mobile Other] jockyw2001:
Well done ND4SPD and good luck cooking your own roms for this qute looking device :)

Another advice is to take a look at the Vox rom kitchen. It's also a TI OMAP850 device and they already cooked a few nice roms. Check out their wiki here.

I will also publish the sspl/uspl files soon in a separate thread. Furthermore, I will soon replace the uspl by a hardspl. That would make it really brick proof.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Thanks jockyw2001 for the advice. Hopefully we'll ge3t wm6.1 working properly on this device. Also, thanks for taking the time to make the sspl and hardspl. I would love to donate, but I don't have any money. Once I get some money, I will make sure to donate to you.
[Non-Touchscreen Windows Mobile Other] shadowmike:
ND4SPD, did you still use one of the original custom rom files found a couple post up or did you use a different one ?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
No, I just took what jockyw2001 stated below:
[Non-Touchscreen Windows Mobile Other] maxima00se:
So after reading all this, do we have a usable rom? Great job guys and thanks for all the hard work! :D
[Non-Touchscreen Windows Mobile Other] pixelwix:
not yet i did the same thing that ND$SPD did and it flashed also. so we have a way to bypass the cid.. now we just need to work on the rom.. been doing a lot of reading on how to build roms... so far i've been able to take the shadow rom take out some of the t-mobile branded stuff add afew oem and it flashed which worked. next step is to actually take all the t-mobile crap out and add 6.1 to it.
[Non-Touchscreen Windows Mobile Other] shadowmike:
Nice Nice. Great Job guys, keep up the good work and I bet XDA will deffinatly make a section for us after this is complete
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I can get a wm6.1 rom made. I think the problem with the rom is that the XIP partition isn't going back into the OS.nb file. I tried writing the XIP file using Xipport.exe to the os.nb that I created, but I don't know if that worked properly.

I know it's not a matter of size of the rom. I created another one without all the t-mo bloatware and it came to about 46MB instead of t-mo's 77MB.

Does anyone know how to merge this back together? I've been reading but can't figure out how.
[Non-Touchscreen Windows Mobile Other] freyes01:
ND4SPD - You are doing a great job.

I wish I can help you....I'm been using and tweaking Windows Mobile devices for several years now but I never learned how to cook a Rom before...
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Thanks! I sent a PM to dr. martin gonzo asking about the xip partition. At the same time, I've been trying random things to try and make it work. (Tried flashing 3 roms today). Hopefully, we can get this sorted out soon!;)
[Non-Touchscreen Windows Mobile Other] pixelwix:
lol i'm stuck on xips also, let me know when you get that done' i'm actually looking into creating a kitchen so everyone can cook thier own rom
[Non-Touchscreen Windows Mobile Other] freyes01:
That would be great....so we can add our own custom apps!
[Non-Touchscreen Windows Mobile Other] freyes01:
I'm been trying to cook my own rom too but I'm having some problems creating the Rom dump with viewimgfs.exe

What version of "Cook Tools" are you using?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Use the tadzio tools. They are an updated version of maimach's imgfs tools. I found out I the address for the XIP I was writing to was actually the read only sector. After using NBInfo, I found it was the first partition instead of the second. As soon as I find the address, i'll post whether or not I was able to successfully write the rom to the phone.

EDIT: Wrong address again...I'm not sure which one is the currect address. Can someone else look at the official rom with NBMerge and msflshtool to find the start address for XIP?
[Non-Touchscreen Windows Mobile Other] Dougall:
HI, I am also working on porting WM6.1 to the shadow after reading a whole lot and following this thread, but I'm having some problems. ND4SPD, what did you use to extract the XIP from the Shadow rom. I tried Rommaster and the hypercore kitchen but I always get errors. And as soon as I figure out how to find the XIP address I'll post it. Thanks.
[Non-Touchscreen Windows Mobile Other] shadowmike:
Guys if I knew how to even start to look for the adress I would, but untill then keep up the great work.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Use msflshtool from the scoter kitchen. Then you can use dumprom
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I've got a working wm6.1 rom image!:D The phone just booted up and I will be testing now. Once I'm sure about it, I'll post for more testing.

Current problems:

The Neo interface and the wm6.1 home screen are conflicting with each other, causing no home screen.

Phone reboots by itself after 15-20 secs

Actual phone radio can't turn on (says operation failed)

I think I accidently flashed the image with the new IMGFS but old XIP.:rolleyes:
[Non-Touchscreen Windows Mobile Other] D1P53T:
keep up the good work guys wish i could help but no nothing bout cooking ROMS
[Non-Touchscreen Windows Mobile Other] shadowmike:
Thats great NEWS. Awaiting the test rom, Keep up the great work. When we are done, I definatly will be donating to all the contributed.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Update on wm6.1 rom

After removing the neo plugin dlls and images, I've got a slightly better rom image.

Features/Problems:

phone doesn't go into an endless reboot cycle(start os, wait 15-20 secs, reboot).

Today screen not displaying. Probably some missing dll's

Phone still can't start up.(look at next item) Though for some reason I can access caller id,call waiting,etc settings and change them.

CommManager doesn't start up because it's looking for the Neo commManager causing phone to not start up.

WiFi/Bluetooth radios can start up, but only from settings.

Sometimes status icons/top bar shows only blocks

SDHC is working. Tested with Transcend 4GB microSDHC card

Accidently used the motorola q keypad. (Standard 3 letter per number dialpad instead of SureType)

Very long boot time (from animated t-mo shadow image)

Sim management working (found all sim contacts)

Shortcut buttons on phone work (camera, shortcut key, volume rocker)

Properly syncing with WMDC

Feel free to ask about any feature, I can't think of all of them off the top of my head. :)

Will post more soon... (Still need to use t-mo rom until it's more stable)

To anyone trying to cook a rom (use the -conservative handle on ImgfsToNb, otherwise the IMGFS overwrites part of the XIP)
[Non-Touchscreen Windows Mobile Other] shadowmike:
Internet Sharing, how is that working ? if at all.

and thankyou for giving us an update on progress.
[Non-Touchscreen Windows Mobile Other] kron2:
how is myfaves working and did activesync recognize the phone and if so did you try to sync a file to it to see if it will except installs
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Well, temporarily, I removed myFaves just in case it was trying to call the Neo interface. WMDC was able to sync files and I was able to install Opera Mini through a cab file that I synced. I can't tell you about internet sharing now because I went back to T-Mobile's rom.

Another problem I noticed is that it started doing the power cycles again, except this time the cycles would wait atleast ten minutes. Still not good enough for everyday use. ;)
[Non-Touchscreen Windows Mobile Other] shadowmike:
definatly not good for everyday use. Looks like your getting some progress. and even if we don't have a myfaves interface t-mobile.com with pie 6.1 will allow us to change myfaves numbers at anytime.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
progress update

WM6.1 rom update:

Changes:

Replaced all SYS files with clean ones from wm6.1 emulator image

Found and added xml files for today themes

Features/Problems

Much faster boot

Phone radio works!

No icons on start menu(need to add shortcuts and will give another update)

Phone shuts off by itself after a period of inactivity. (not good)

WMDC can't find device(hopefully remedied when I edit the initflashfiles.dat for shortcuts and such)
[Non-Touchscreen Windows Mobile Other] shadowmike:
Nice. How about the home screen ? 6.1 home or 6.0 neo ? or both ?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Neither. It just gives an error saying that it couldn't load the home screen and that I should go to settings and change it.

But, pie6.1 works!
[Non-Touchscreen Windows Mobile Other] Dougall:
ND4SPD, If you don't mind me asking for your help again, how did get past the "Error, last status: "Creating initflashfiles.dat..."" when running BuildOS?

I have been able to extract the XIP and port it, but I can't build the imgfs. Looking around in the forums a bunch of people have gotten around it, but nobody posts how they did it. Any help would be appreciated. Thanks
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Copy the initflashfiles.dat from the XIP folder to one of the OEM folders like OEMAPPS or OEMDrivers. For it to work, use buildos+packagetools.exe to rebuild the dump

Were you able to successfully put you XIP back into a .nb file? Can you tell me what you did? Whenever I tried I got problems and I still don't know if the rom I've flashed is using the old or new XIP.
[Non-Touchscreen Windows Mobile Other] pixelwix:
guys how are you extracting the xips? i'm still stuck on that
[Non-Touchscreen Windows Mobile Other] ND4SPD:
First use the msflshtool from the scoter kitchen. You will get three parts, the second one is the XIP. Then make a directory called XIP. Then in command prompt, run: "dumprom -x -5 04_OS.nb.part01 -d XIP".

Then you should have the XIP and you can port it from the Q. Another suggestion, for the IMGFS, use the SYS files from the wm6.1 emulator image from Microsoft. It's a lot more stable and cleaner than the Q files.
[Non-Touchscreen Windows Mobile Other] shadowmike:
I was downloading the emulator image last night. Do you think I could dump the emulator and possibly take some progs from the emu and put them on WM 6.0 shadow for those who may not want to upgrade ? with a custom rom
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
i've been following this thread for awhile first id like to say good job : ). That would be awesome to have a working 6.1 rom soon. I was wondering sense you guys have the phone radio working if you would be ok with uploading a test version of what you guys have? And instructions on how to install it, i've never used a non-factory rom before, and I don't even know were to start :).
[Non-Touchscreen Windows Mobile Other] shadowmike:
trust me... when ND4SP feels that it is ready for testing he will upload a test version.

as of right now. I believe he said after 10 mins it will restart and there is no homescreen.

so all in all its pointless to use. atm
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Though I'm about to test another version, the previous version could recieve calls. The circular light flashes when there is an incoming call but it doesn't say it's recieving the call, no ringtone, and you can't answer the call. Same with sending calls, you can dial it, but once it tries to send the call, nothing happens with no status.

Hopefully this will change with this new test because I know for a fact that this rom has my ported XIP on it, instead of the T-mo one. Thank you shadowmike for explaining about the test rom. Wish me luck on this test!
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I got almost everything to work now!!!!!!:D:D:D

Features/Problems

The new sliding panel home screen works

Calling and recieving calls work

SureType works

New PIE 6.1 works

Getting started welcome app works

SDHC works

Comm manager from vox comes up(I can put the previous one back on if you want)

Some settings panel can't be opened

Started turning off after period of inactivity(I think I need to port more of the XIP)

EDIT: Check latest post for newest version

I forgot to encrypt with password, so just reminding, USE AT YOUR OWN RISK!

Make sure you run the sspl first.

When the rom starts up, the today screen will not show up(it is looking for the windows simple theme), go to settings and homescreen and change to sliding panels or sliding panels media.

Report any bugs in this thread.

Fixes for next test version:

Shadow settings will come back. (Accidentally put Moto Q settings instead of Shadow's)

Add wm6.1 splash screens instead of wm6.

Will start up with sliding panels theme

Old comm manager with working WiFi

Will update when bugs are reported.

freyes01, I saw all the customizations you have on your site. Could you make a custom theme for the communication manager? After you dump the t-mobile rom and make packages, the files are in the OEMdrivers folder and all start with cm_xxxxxxx.png
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
awesome :).
[Non-Touchscreen Windows Mobile Other] pixelwix:
nice work man, i guess ill just wait till you have a stable build and just make a kitchen out of that, if you don't mind.. Nice work by the way.
[Non-Touchscreen Windows Mobile Other] kabdallah9:
Great!

hey i just got this rom installed and its great! thnk so much, no bugs to be reported...or at least yet.
[Non-Touchscreen Windows Mobile Other] kron2:
you are the man ......do you have the CID unlock tool.....I hope the bump on your head go's away soon from slamming it on the desk lol:p
[Non-Touchscreen Windows Mobile Other] ND4SPD:
the cid unlock tool is the sspl mentioned a few pages back. Make sure your phone is Application Unlocked if the SDA App Unlock isn't provided with the files.

lol Thanks
[Non-Touchscreen Windows Mobile Other] ND4SPD:
That's great! If you want, I can make the kitchen into a GUI for you after you are done.
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
When i tried to run the update it said the image file was curropted.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
You need to run the SSPL from a few pages back to CID-Unlock it. Otherwise, tmobile's locks prevent the rom from flashing.
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
I know i relized that after i posted :), im waiting for rapideshare to refresh my download ticket...does the sspl rar have a password on it?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
No, it doesn't. jockyw2001 posted that. (who I must thank once again or we would not even have this test build)

It might seem a little "all-over the place". jockyw2001 intends to make a new thread with a finalized version, and maybe a HardSPL too.
[Non-Touchscreen Windows Mobile Other] benjaminries:
Cool

This sounds so awesome.

I'm curious what you meant, ND4SPD, a few posts back when you said you would be including "Shadow settings" in the next release. Maybe I'm a n00b for asking, but forgive me: does this include the Neo interface?

Obviously the holy grail of a WM6.1 Shadow ROM would be to allow us to switch back and forth between the new "slide" and old "neo" homescreen interfaces. The problem, as I understand it, is that both interfaces make use of the same HKLM\Software\Microsoft\CHome and HKLM\Security\CHome registry keys, and perhaps the same \Windows\CHome_*.png image files. (I haven't seen a 6.1 device before, but I'm hoping the clsid codes are unique). So we would need to find a way to make the themes coexist in the registry.

I think you're on the right track to build a stable "vanilla" WM6.1 ROM that uses the new "slide" homescreen and ignores "neo" for now. I'm wondering if we can eventually bring the Neo interface back in as a parallel option, renaming all the CHome registry keys to have an "N" in front of them, and take a similar approach with the PNG files. I'm going to start messing with the Neo registry and homescreen XML files to see if this is possible. Is this helpful, or am I going down a pointless road?
[Non-Touchscreen Windows Mobile Other] shadowmike:
if freddy doesnt get to the theme ill hit it up..

downloading this over the air sucks.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I think that's a great idea. What I meant by "Shadow settings" was the stuff in the settings menu.

I like your idea about the two interfaces coexisting. We probably could build a little exe that switches between the two interfaces:

Here's what we would problably need to do:

Create two separate packages for the CHome files

Add the neo plugin dlls back into the OEM folders

When toggling between plugins, have an exe rename the dlls used by one so that windows can't find them and rename the others so windows can

We can also add in all the Neo image files since the wm6.1 sliding panels doesn't use files named that way
[Non-Touchscreen Windows Mobile Other] Dougall:
Wow! You're making great progress I still cant get mine to boot, but I will definately test yours as soon as I can. Have you gotten the Neo interface to work in WM6.1 or is it just the Normal home screen?

Great work btw.
[Non-Touchscreen Windows Mobile Other] BZ19:
what to do

hey i've got the sspl files and the testing version dowloaded. Exactly, what do i do now to get this testing version running on my shadow? Thanks.:)
[Non-Touchscreen Windows Mobile Other] benjaminries:
That's one approach, but creating the switcher exe would be beyond my expertise. I was hoping for something simpler:

1. Start with the premise that the chosen Homescreen theme (in its XML) references the HKLM\Software\Microsoft\CHome key, which references subkeys for each Neo page (ie. CMessages, CLinks, etc.), which reference PNG files in the Windows directory and a CLSID for registered DLLs that govern functionality (allegedly using Flash, I read somewhere).

2. Find all references to HKLM\Software\Microsoft\CHome in the old Neo XML and replace with HKLM\Software\Microsoft\NHome. Copy CHome key and subkeys to NHome. Subkeys can still be CLinks, CMessages, etc. Rename any referenced PNGs or DLLs whose names are also used by the new 6.1 "slide" theme, and change appropriate references in NHome subkeys.

3. Copy modified Neo theme, NHome registry keys, PNGs and DLLs to new ROM.

In theory, this would mean that when the user changes home-screen theme from the settings applet between "Neo" and "Slide", no registry keys, DLLs or PNGs would need to be switched, because they would all coexist on the device. No switching exe required!

The kink in the whole plan is whether or not references to CHome registry keys are entirely within the scope of the Neo Home-screen XML file, or whether they are hard-coded into some DLL somewhere. If the later is true, my whole plan is blown... unless we find the DLL where that registry location is hard-coded and mod it.

But in theory, we should be able to get all files and registry keys to coexist on the device by giving them different names, with no swapping utility required. Perhaps we should look to those who have ported the Neo interface to other devices (HTC Hurricane?) for guidance.
[Non-Touchscreen Windows Mobile Other] shadowmike:
ill try and look into what i can to help. im going to be installing this soon