yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] derrickadams:
Glad to see 28XXX make a come back, so far it is working great.

I do agree that the boot up time is much better and over all everything is working great, very responsive.

If I find any issues while at the bowling alley or over the weekend I'll post them.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
Jan 26 don't appear to be up on the mirror site yet...

Have you tried the 2/1/2011 28244 version? If so, can I ask why you want to go back to the 29007 version? IMO this last 28244 version is the fastest, smoothest build yet!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
That does the trick, and many thanks for it.

Every time I think this phone has been as tricked out as it can get, a veteran user shows me something new :)

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
If a user did go from 29007 (in my case, the Jan26, 2011 version) to a current 28244, are the imports of backups compatible: cht and quick link backups?

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] yellowsnowball:
Cool ROM

Wow, this is a really cool ROM. It looks like I have a long way to go before I am ready to flash it. The information is kind of overwhelming at first.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
I'm uploading some of them now. I'll post a link once they are up.

CHT settings are compatible with different builds, but full backups, like full registry settings and complete backups from Sprite backup or SPB backup are not.

Don't worry, we all have to start out somewhere. As long as you read and follow the rules, anyone here would be more than happy to help you along. Good luck!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] skim56732:
For the apps that I have installed, the 29007 provided a more stable platform than the 28244. For some reason, 28244 is causing my phone to run hot and more instabilities than 29007. I had the same situations happen the first time 28244 was used. I thought things would be different with the 28244 (Feb 1) this time around, but it was the same issues.

What is the mirror site? Thx.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mmalka:
Working fine for me.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mmalka:
You don't mention which version of ROM you have. I tested on mine and it is working fine.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Search this thread for "mirror site," and you'll find it. I don't think the 26 January ROMs are listed there yet, so I'm uploading a few of them. TOG 29007 is coming up first in a few minutes.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
I have sent you a PM....
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] skim56732:
Thanks...appreciate it.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
26 January 29007 ROMs

For those of you wanting to flash back to the most recent 29007 ROM from 26 January, keep an eye on this post. I'll be uploading them shortly. Touch of glass is up first.

Energy.RHODIUM.29007.Sense2.5.Cookie.2.0.Jan.26.7z

Energy.RHODIUM.29007.Sense2.5.Cookie.2.0.GTX.Jan.26.7z

Energy.RHODIUM.29007.Sense2.5.Cookie.2.0.DinikGlass.Jan.26.7z

Energy.RHODIUM.29007.Sense2.5.Cookie.2.0.sencity.Jan.26.7z

Energy.RHODIUM.29007.Sense2.5.Cookie.2.0.Touch.Of.Glass.Jan.26.7z

Energy.RHODIUM.29007.Sense2.5.Reference.Jan.26.7z

Energy.RHODIUM.29007.Sense2.5.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.GTX.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.DinikGlass.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.sencity.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.Touch.Of.Glass.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Reference.Jan.26.7z

Energy.RHODIUM.21916.Sense2.5.Jan.26.7z
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] yellowsnowball:
The views seems to be varied heavily. I think I have an idea of what the different builds actually are, but I can't find what the difference is between them. Does anyone know if there is anything different between the two of them other than the speed difference?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rkub:
Have you checked the thread link in CajunFlavoredBob's sig? He tests all the different builds and gives benchmarks. Should have more info there...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] yellowsnowball:
Yea, I saw that and also saw the one for the links to all the ROMs in his sig. Its quite a lot of information to absorb. I was trying not to ask questions until I couldn't find it out for myself, but that thread seems more focused on benchmarking than what the actual differences are, if any at all.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rkub:
Ahh I gotcha, I dunno if anyone has done any comparisons like that... It is quite a bit of info...lol You should ask questions when you like, just make sure to ask them in the correct places. You might want to be asking this question in that thread or another thread more build specific since this isn't really rom related and you can get a little roasted for doing so at the wrong time. This thread isn't really busy right now so not a big deal but always a good idea to remember...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] yellowsnowball:
I see. I was really just wondering if there was anything different between the two builds in this particular ROM. I read back a ways and see that Sense is more up to date in the latest one. Other than that, though, I don't see much different. I wish I could give more than five thanks per day. I have so many people to thank for making this process of flashing as simple as possible. I didn't have any trouble at all. The hardest part was picking out a ROM to flash first. I just went with the reference 21916 version since it was the closest one to stock. I am enjoying Sense on this phone way more than touch Flo 3d. It seems much faster.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jlmwrite:
A different sync problem with Feb 1 ROM

Just flashed from Dec20 28244 Sense 2.5 Cookie 2.0 Dinik to the latest Feb 1 28244 Sense 2.5 Cookie 2.0 Dinik, and ran into a sync problem I haven't ever seen in the past 2 years.

I'm using the same Vista PC as always with Outlook 2007 and WMDC. The Feb 1 flash went perfectly, and I rebooted the PC after the flash. New partnership established and sync started normally (setup, etc) then it said it was synced after only about 20 seconds. Obviously nothing had synced though.

Rebooted the phone, rebooted the PC, and partnership showed up in WMDC. After a few seconds, it said sync complete again but no appointments, calendar entries, tasks or notes on the phone. After trying a few things, I decided I had a bad flash, so I reflashed -- and the same thing happened when I set up a new partnership.

Downloaded the Feb 1 image again, Task 29'd, reflashed without any issue, and played with the phone for a minute to make sure everything was normal looking. Rebooted the PC, hooked up the phone and set up a new partnership thru WMDC. Chose the sync items (the same as always: 3 months of calendar entries, contacts, tasks, and note) and it successfully saved the partnership info.

But after about 15 or 20 seconds, it said sync complete and still no data on the phone. Hit the sync button a few times; the icon twirled around a couple of times and it said sync complete again with no data transferred to the phone. I thought about mmalka's earlier post where he said took a very long time to sync, so I left everything alone for about 45 minutes, but still nothing.

Flashed back to Dec 20, and this time sync took the usual few minutes with everything I'd requested back on the phone.

So... No one else has reported this one. If I'd had *any* sort of changes in my PC configuration I could blame it on that. But the fact is, I haven't installed or changed anything in a while on my PC, I've Task 29'd and flashed the Feb 1 ROM three times. Since I had a normal sync after reflashing to the Dec 20 ROM, I must have some sort of strange conflict between the Feb 1 ROM and my system.

Anyone?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Thunder Blade:
Hi

I have a question. Can i install this rom without using Task29? I have now stock 6.1 rom. I have HardSPL, if i install this rom now it will not damage phone?

Thanks
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Key is to make sure that HardSPL is applied

Press and hold Volume Down. Press reset with stylus

wait for tri color screen.

Verify that the 2nd line is:

SPL-085.OliNex

Key part of that is the OliNex.

Once you have that, there are no ROMs that can really wreck your phone.

Task29 can normally be skipped.

But, if you have problems that seem really strange and no one else is reporting them, please Task29 and reflash. then see if the problems are there. If they are, then post about them.

I almost never do a Task29.

I have never had a problem that Task29 fixed, so to me, it is normally a waste of time. Occasionaly a user will have something really strange. That is a good time to Task29.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] yellowsnowball:
From what I understand about it, task29 is like formatting your hard drive. It wipes your phone memory clean so you can start over with something fresh. I think this is to keep stuff from getting mixed up when the memory get overwritten, but I could be wrong. I only started doing this stuff this morning.

It seems to me that task29 would be helpful for flashing in between ROMs so that it's fresh and clean every time, see? I don't know if it really helps or not since I just went from the stock ROM to task29 to a custom ROM today though. I'd say do it!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
There must be something in the water down here in NOLA that breeds good new users. :)

This is pretty much exactly the reason we have task29. Some say it works, and some never use it. Personally, I use it between every flash of any ROM. I find that it simply prevents any problems. I haven't found any weird "ghost" problems since I always boot from a clean install. It more of a matter of what works best for you personally. I recommend it to everyone, but it may or may not help you at all.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] yellowsnowball:
I actually live in Terrytown on the West Bank (don't flame me lol), but I figured New Orleans was easier to recognize than Terrytown. Thanks, though. I spent all morning reading about this so I didn't kill my new $300 toy. I kind of wish I had just gone with the HD2, though. This screen is so tiny. It would have been awesome if they had made the HD2 Pro or something with a keyboard. I can't live without a keyboard. It sucks that there are so few devices with such an amazing keyboard like this phone.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
While we're on the topic of flashing, can someone explain to me why there is a consensus that even after task29>newROM, that users should still hard reset. Some experienced users even suggest hard resetting b/w task29 and reflash.

I would figure that a task29 is the ultimate hard reset, but I'm new to all this and defer to experience, obviously.

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rkub:
21916 is closer to stock but 28244 and 29007 (6.5.5 builds) are much more finger friendly. Start/X buttons on bottom with big finger friendly buttons. Must for me since I have fat fingers...lol

I'm with you on both points... Would love a 4.3in screen but not havin a physical kb is a deal breaker for me... Really likin the moto Atrix w/ dual processors but no kb is killin me. I don't see any new dual proc w/ kb tho... Prayin HTC puts out a phone w/ 4-4.3in screen, dual proc, and kb...lol Laptop and entertainment docks would be great too..lol

Sorry for off topic posting but rom is workin perfect and nothin to gripe about... :D
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Alot of us in this thread came from the Fuze (Raphael) (Touch Pro). That had a tiny screen. Only 640x480 and it was narrower.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rkub:
Some of us also came from the original Tilt that had a really crummy screen... I think it was the same size as the Fuze but the resolution was a lot lower...lol I tried using it a litttle while ago and couldn't do it...lol
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Hard Reset vs Task29 vs just flashing.

Strange results that others are not seeing should never be posted without first doing a hard reset or a Task29.

It used to be the general rule to Hard Reset after every flash.

But, then Task29 came along, elliminating the need to do that.

When I first started flashing almost 2 years ago, I was very religous about Hard Resetting after each flash. Task29 was not something really talked about back then.

Then, I started thinking that maybe I could get by without hard ressetting.

Sure enough, I didn't experience any strange problems. Only once did I think I had a ghost, but it was actually some other problem. Hard Reset did not fix it. It was sizing issue on my Fuze with the dialer and issues with the dialer in landscape.

Later, Task29 started getting talked about.

I decided to try it. Started doing it a few times.

Then, after chatting with NRGZ28, I decided it was a waste of time. You will find posts from him saying that he doesn't ever Task29.

I probably have over 100 flashes without a Task29 or a hard reset. (At least 50 anyway).

No strange issues.

And if any come up, a hard reset is easy. XDA_UC sets nearly everything up the way it was. And a hard reset was what everyone used to do before Task29 became popular.

If you want to scientifically compare multiple versions of the same ROM, a Task29 is good, since more will be in a fully known state.

But, most users will not notice anything by not doing either.

Again, strange results that others are not seeing should never be posted without first doing a hard reset or a Task29.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mmalka:
My personal experience: I've been in this "business" for a long time. I started with the old Tilt, then moved to the Fuze and now I have a Tilt2. With every one of them (since Sleuth's WM 6.0 ROM) I always performed a hard reset after flashing, because as JVH3 mentioned, that is what we did by then.

When "recently" Task29 came up, I did not bother with it: I NEVER had any problem that required it. Honestly, I don't even know if the hard reset is doing any good, but just in case I do it - it it worked fine for me until now, why change? So, I never used Task29.

Please keep in mind that I flash A LOT, but each one's experience and results can be different.

Once (and only once so far), I flashed the stock ROM just for the sake of it as some people indicated that it may do some good, but I don't remember seeing any difference for good or bad.

Anyway, in case any of these three methods would not do any good, at least they would do no harm either, so I recommend that each one sticks to whatever is working for him or her.

JVH3's advice is sound as usual: if you see something strange that nobody else is reporting, by all means use one of the 3 methods mentioned. If that still does not resolve, test with the bare ROM before installing or restoring anything. In most cases you will notice that the problem will not happen.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Puff1911:
Feb01 28244 is not working out too well!

ROM: Energy.RHODIUM.28244.Sense2.5.Cookie.2.0.Feb.01

Getting regular black screens with this release.

At least 5 times a day I have to reset the Touch Pro2!

When the screen sleeps and I press power to wake it, i'd see the task bar on top.. but the rest of the screen is blank.

I task29 like a mofo! So much so, that I feel like if Task29 is the blasted problem! lol lol

anyone else having any issues with this one?

I still have the Dec20th 28244 ROM.. I'm thinking of going back to that one.. or to just relax with the 21916! :s
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
Are there other addons that you install? That might be the problem.

I have been running the Energy.RHODIUM.28244.Sense2.5.Cookie.2.0.Feb.01 ROM for 3 days now and have not had ONE problem...especially no BSOD's.

I don't know by your statement if you have tried reinstalling this ROM after a task29...or if you just ran task29 and installed this ROM once.

You are the first to complain of a BSOD...so I would lean towards a bad flash; a bad download; or both.

You might trying to reflash...and if all else fails, re-download and reflash.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
My thanks to those who weighed in on whether a hard reset after flashing is necessary.

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
26 January ROMs

The 26 January ROMs, for those looking to roll back can be found in the following Hotfile directory.

26 January 2011 Energy ROMs
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
Moving Carrier to Taskbar, AT&T Keyboard & Task29

Sorry, dunno how.

****

AT&T Keyboard

Well check the energy_att.cab & energy_att2.cab found in Windows. It seems they do much more than just remap the keyboard. I don't live in USA & AT&T is not my carrier so I don't need links to http://mmsc.cingular.com for example.

I have been using successfully Tilt2HWKeyboard.cab to map correctly the AT&T keyboard + RhodiumKbdControl_GSM_1.4 to map PTT & other keys to taste.

*****

Task29

Well it's a known fact that you flash 2-3 times a day so I understand that 2-3 minutes to run Task29 is a big waste of time for you but maybe not that much for us at stage 1 or 2 of the needtoflash syndrome. ;)

I've been trained by Windows to format & clean install to avoid problems & optimize so removing the SIM, memory card & Task29 is a good investment to make sure one gets a clean install IMO. I also disconnect the phone while it's first booting & after it's settled, I hard reset for good measure & restart the phone. :eek:

Note to new users to Task29: phone will be stuck on the main boot flash screen so you need to put the phone manually in Bootloader mode to be able to flash the new ROM:

"Remove the back cover from the phone.

Hold the Volume Down button.

Use the stylus to press the reset hole.

Or if the device was powered off, press the power button whilst holding down the Volume Down button."

"Hard Reset (This cannot be performed while the device is connected/charging)

With the device turned off, press and hold the TALK/SEND and END/HANG UP buttons, then the press and hold the POWER button until you see this message on the screen:

"This operation will delete all your personal data, and reset all settings to manufacturer default. Press VolUp to restore manufacturer default, or press other keys to cancel."

Release the TALK/SEND, END and POWER buttons.

Press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset."

+1.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Joe Bleau:
Feb 01 ROM Tweak: Slider Box Fix

Edit 2011-04-26: You can find a new cab that includes eac's mod for the level 2 slider box (the one seen in the music library for example) in this post: Slider Box Mods - eac & JB's.

A follow-up on the Feb 01 ROM Tweak: Home Cleaning Toolbox post.

Before & after:

It was bugging me that in the Feb.01 & other NRG ROMs the slider box was cropped on the left side when resting on the Home icon. I guess it's to compensate the fact that when you move the slider to the right all the way to Settings, it gets off center more & more in relation to the app icon. But I don't care about that since I spend much more time looking at it on the Home page.

It took me a couple of hours to figure which manila files were responsible for the slider box itself (1cd2f8ef_manila and 695552fb_manila) & how to edit them (CFC - THE Manila/TF3D Image Editor and Photoshop), cab them & testing them on Feb.01 but it was fun: learning a lot of stuff along the way. While I was at it, I trimmed the excess gray on top of it & made two cabs:

1- Sliderbox Fix JB.cab modifies only the Slider box.

2- Sliderbox Fix & Curtain Removed JB.cab modifies the Slider box + it removes the curtain for a cleaner look IMO.

How to install:

1- Remove any cabs that you may have installed to modify the Sliderbar (like Sliderbar Curtain Remove JB.cab from my previous post for example) & restart the phone. > Home > Slider bar to Settings > Application > Remove Programs.

2- Copy either cab to the memory card & then install them from there with Start > Total Commander

to the Device

. Restart the phone if it does not do it automatically to apply the change.

Note: To revert to NRG's default Slider box, just un-install the unwanted cab & restart the phone.

:cool: Feedback is always appreciated as it's our only reward for this work. :cool:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] devehman:
Hard keys

I recall finding a program earlier that let me choose what my hard keys do after holding or tapping them, but I can't seem to find it again. If it wasn't my imagination, what is the program and where is it located?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
It was tarkim's key remapper.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
New theme

We will be getting a new theme for the ROMs soon. I'll post some screen shots tomorrow afternoon of what it's going to look like. I've been trying to work some issues out of the theme tonight. I just wanted to give everyone something to drool over. I'm posting a teaser of my weather page on CHT. More to come tomorrow.

EDIT: Also note that this page isn't even complete yet... ;)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Puff1911:
I've done the Task29 and reflash several times.. but I figured it mighta been one of the extra programs that I have installed

ORIGINALLY I had installed

Auto Call Recorder 1.2.4

ReliRescue

WinMoSpeed 1.04

MS Voice Command 1.6.23562

After my post I removed MS Voice Command 1.6.23562 and installed 1.6.19209

So far everything seems to be stable..

I'll keep you posted!

Thanks for the advice!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
@Joe Bleau

Re: Shift of Home Icon. Found your cab this morning and it works great. Successfully shifts the icon slightly to the right for full visibility.

Many thanks for taking the time to investigate and make this cab.

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
I have been using Voice Command 1.6.23562 for several months and install it through xda_uc with every flash.

I have had no stability issues.

I doubt its configuration was the problem, but

What did you have set its configuration?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
Bluetooth Channels and ROM Flashing

Can ROMs switch around the channel numbers in the phone's internal bluetooth?

When I flashed a TMobile HTC Touch Pro 2 to Energy.RHODIUM.29007.Sense2.5.Cookie.2.0.Jan.26.7z, the bluetooth channels were different than a previous flash.

I can confirm this since the Linux obextool command needs to have recipient's channel typed in. After flashing, I could no longer send files to phone until I switched the channel number from 1 to 2.

Ditto for tethering in Linux: the proper channel went from 3 to 4.

I'm not complaining b/c suddenly, the obexftp command in my Linux machine works, and I don't have to use the buggy obexd command.

But the flashing of the ROM produced a dramatically new bt layout--even file transfers via XP Pro SP3 needed a repairing of the phone.

I thought channels were channels, hard-coded.

Can anybody enlighten me?

And if anybody uses the unholy union of Linux and WinMo, I'd love to have any of their observations.

Jake