Database Info

Place for Newbs to get Started-Want Tilt to Look Like Touch

Any advice? I am new to this whole thing. Have done some overclocking and what not on my PC, but this is a whole different game.
What types of things can I do without risking really f'ing things up?
What I hope is the simplest things I was hoping to do was to make my TILT screen look like the HTC Touch.
I thought about downloading Dutty's tweaks, but I am thinking I might be out of my depth starting out.
I would like to learn some things, but don't want to annoy the veterans that are here. Any direction would be appreciated.
Thank you.

What you could do is read, all the post people have put to do exactly what your asking. All the info is there you just need to search and read or use the wiki.
Have fun
-McMex

Thank you.

Download and run HardSPL on your phone from:
http://forum.xda-developers.com/showthread.php?t=334679
Then choose a dutty rom to install, since you are on a tilt try:
http://forum.xda-developers.com/showthread.php?t=345385&highlight=dutty+tilt
This is all you have to do to have a fully functional htc looking rom with the touchflo cube with the newest drivers and radio for AT&T. I am using this one on mine right now. This rom has everything that you will probably need already installed. Anything else will just be for personal preferences. This rom has an advanced config program which is great but also download kaisertweak for some nice settings.

Thanks for keeping it simple for the newb. I read a couple of things about the "radio" portion being an issue. What does the "radio" tweak mean and will a HARD RESET fix problems if I decide to revert back?
decimusmaximus7 said:
Download and run HardSPL on your phone from:
http://forum.xda-developers.com/showthread.php?t=334679
Then choose a dutty rom to install, since you are on a tilt try:
http://forum.xda-developers.com/showthread.php?t=345385&highlight=dutty+tilt
This is all you have to do to have a fully functional htc looking rom with the touchflo cube with the newest drivers and radio for AT&T. I am using this one on mine right now. This rom has everything that you will probably need already installed. Anything else will just be for personal preferences. This rom has an advanced config program which is great but also download kaisertweak for some nice settings.
Click to expand...
Click to collapse

The radio that comes with this rom will be the one you need. A hard reset only reinstalls the rom you currently have on the phone so to revert back you will have to choose another rom and install it. As long as the rom you install is an AT&T one or one made for the tilt then you won't have to do anything with the radio. If you change and use an HTC ship rom or one of dutty's other roms then you will have to download another radio and install it. Radios self install the same way as roms do.
This is the wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
On this page is the link to the ftp area where you could download the older radio if you decided to go to a non tilt rom.

Did you have any keyboard problems when doing the HARDSPL and installing the dutty rom. Also, which of the dutty roms did you install? Beta 2?

I am still on the Beta 1 and have been too lazy to changeover yet as Beta 1 is solid.
If you really want a good "How To" check out Mr. Van X:
http://www.mrvanx.org/cms/index.php...ask=view&id=65&Itemid=26&limit=1&limitstart=0
Every place he says "Hermes" you just think "Kaiser" or "Tilt". All the steps are the same. It is a great walk-through. He has you download the .net framework first. I know I didn't have it. Then he steps you through hardSPL and finally the ROM.
A few weeks ago I followed this exactly and have never had any troubles. Why a walk-through like this is not in the Wiki for the Kaiser/Tilt I have no idea. It'd be a lot more helpful to newbs (like myself) than the forum fav response, "Read Dammit".

Augster said:
It'd be a lot more helpful to newbs (like myself) than the forum fav response, "Read Dammit".
Click to expand...
Click to collapse
Why don't you write an entry for the wiki? That's how the Wiki is updated and maintained, by contributions by everyone.

afavre said:
Any advice? I am new to this whole thing. Have done some overclocking and what not on my PC, but this is a whole different game.
What types of things can I do without risking really f'ing things up?
What I hope is the simplest things I was hoping to do was to make my TILT screen look like the HTC Touch.
I thought about downloading Dutty's tweaks, but I am thinking I might be out of my depth starting out.
I would like to learn some things, but don't want to annoy the veterans that are here. Any direction would be appreciated.
Thank you.
Click to expand...
Click to collapse
I just used HardSPL and Dutty's Hybrid Rom No 5. I'm not sure what the difference is from his Tilt Beta version but I tried both and decided to go with the Hybrid. Point is, until last night I did not know what a Rom was. I read the forum and followed the directions. Here are links to what I used.
HardSPL (you need to do this first). Everything you need to know is in the first post
http://forum.xda-developers.com/showthread.php?t=334679
Then find a ROM. I downloaded several including the stock ATT rom just in case I decided to go back. The steps for loading a ROM are almost the same as HardSPL, just follow the directions on the screen.
This is a link to Dutty's Tilt Beta ROM (all you need is the link to the ROM at the bottom of the first post). If you want to try Dutty's Hybrid ROM, scroll to the 3rd post made by username "alltheway" and click on the red Hybrid No 5 Rom link in his signature block.
http://forum.xda-developers.com/showthread.php?t=345385
It is very simple to do.

Do I need to SIM Unlock?
I have been reading through the posts, and I can't find if I must SIM lock my phone before trying to install Dutty's ROM. On my 8125 the general concensus was unlock both. I don't have any need to run other radio's on my phone, and I won't be traveling out of the US.
Also I am currently running SPB Pocket Plus 4.01. Should I do a hard reset before trying to CID unlock and load of new rom?

ShinySideUpAZ said:
I have been reading through the posts, and I can't find if I must SIM lock my phone before trying to install Dutty's ROM. On my 8125 the general concensus was unlock both. I don't have any need to run other radio's on my phone, and I won't be traveling out of the US.
Also I am currently running SPB Pocket Plus 4.01. Should I do a hard reset before trying to CID unlock and load of new rom?
Click to expand...
Click to collapse
No you do not

Brainless & Confused

Sorry guys & gals. New to this but cannot get a handle on the right thing to do. Can anybody help? Yes have read the basics but its not basic to me I am afraid.
I have got an HTC TYTNII from Orange. Need to unlock the sim card lock. Then would like to clear out all the Orange rubbish with a rom flash I think its called (havent got all the words right just yet). However as I paid a few quid forthe phone do not really wish to stew it!! If you know what I mean Harry! Cannot find hardspl etc on so on have ativesync fitted and running. All help greatly appreciated.

This webpage has a ton of files that have been extremely helpful to me so far...
http://duttythroy.lives-in.eu/

dont really know how to help
but
if you want to use hardspl is on the sticky thread
activesync can be downloaded from ms depending on the os you are using.
if you want more help tell me what you need and i will guide you
satiros

Lots of reading
I suggest you do lots more reading.
However, as a starter, go to :
http://www.imei-check.co.uk/kaiser-unlock.php
Pay for the unlocking service.
Then, and only then, install HardSPL
Following that, you can install any ROM you like (for Kaiser / TYTN II)
If you install a ROM based on Windows Mobile 6.1, chances are you will have to install a new Radio coding too. You should install the one for UK Vodaphone on :
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Radio
Don't worry, it works on Orange, I have it on mine.
I recommend the Alex ROM even though it is still a Beta version, it is very good.
After you install the ROM and done a hard reset (keep both soft buttons pressed down whilst pressing the reset button with your stylus) install the radio, then do another hard reset.
Bingo, it's like a different phone.

Thanks for the info have carried out the first bit awaiting reply. Where can I download HardSPL please? Having looked at your recommended ROMs Which one?.. wow some cooking I can see I will be Flashing all day!!

cloudbasher said:
... Where can I download HardSPL please?
Click to expand...
Click to collapse
if you cannot look & find it right there in one of the sticky threads of this forum ... I'd suggest you do not attempt any flashing to your device !!!
as some of those stickies contained mandatory informations that you need to READ THOROUGHLY !!!

problem after upgrading

I Hae A Cingular Htc 2125, I Upgradated To Wm6, Now Shows White Screen, It Works And Its Recognized By Activesync, But Only Show White Screen, Can You Help Me Please!!

elteacher0223 said:
I Hae A Cingular Htc 2125, I Upgradated To Wm6, Now Shows White Screen, It Works And Its Recognized By Activesync, But Only Show White Screen, Can You Help Me Please!!
Click to expand...
Click to collapse
did you follow the apropiate guide for Tornado? At top of this Thread you will see Karhoe's Guide to upagrading Tornado. Go to his site and review that you followed everything step by step.

yes
markanthonypr said:
did you follow the apropiate guide for Tornado? At top of this Thread you will see Karhoe's Guide to upagrading Tornado. Go to his site and review that you followed everything step by step.
Click to expand...
Click to collapse
yes, i followed everything as intended...but i dont know whats the problem

This almost seems like a screen problem that's hardware related. Have you tried a different ROM yet?

What ROM did you flash with? Try flashing with Nitrogen's Platinum. I know for a fact that the rom works great. He includes all you need on the download.
First do the Format BINFS, then flash the GSM (Radio), then finally the actual ROM. Once again, make sure you follow the proper procedure step by step on Karhoe's guide

One related question:
how possible is for upgrading process to go in unwanted direction, I have 8310 for two days, and I am eager to try installing WM6, but I am afraid something bad could happen?
Is there some procedure that can reverse it to factory state is something goes bad?

How to...
Goran,
if you want to return to the original WM5, make sure you have downoaded it first. If your new rom update fails and your tornado is stuck in bootloader, you can always flash the original system back. But such problems could only happen because of 1) incompatibility (if you flash a wrong rom) or 2) your new rom (e.g. custom cooked from a kitchen) is too big (more than ~40Mb).
But flashing an original WM5 rom won't put it to the factory state. It'll just flash the same system. The problem is if you can make the SuperCID in a reversable way. It's very hard and long, I even didn't try. I used a simple and fast way. They say you'll lose warranty but in any case the IMEI code will remain the same.
In order for the flashing to go flawlessly you need to make sure you have donre SuperCID and format BINFS. Just read the flashing tutorials, they are on every forum like this.
Flashing an original WM5 rom won't put it to the factory state. It'll just flash the same system. The problem is if you can make the SuperCID in a reversable way. It's very hard and long, I even didn't try. I used a simple and fast way. They say you'll lose warranty this way but in any case the IMEI code will remain the same.
BTW, I recommend you trying WM6.1 - it's nicer, but it's hard to find a version without at least little bugs. For example try BD's s740 Rose ROM. It's quite stable and nice, but it uses more memory than other 'clean' roms. Have a nice flashing!

Hello, George, thanks for the response.
Actually, my impatience has overcome my fear, so last night I flashed it, and all went well. I have used Nitrogen's WM6 Platinum Edition SP1. I think its not 6.1, although it has service pack 1 in it. Looks much nicer that WM5, although I don't like this black square around icons. Maybe I will try later 6.1.

New to windows mobile, would appreciate help.

Hi everyone, I have recently bought a htc touch pro from polish orange provider. I have browsed dozens of topic, trying to make my windows mobile 6.1 life more satisfying, but I have few questions to ask.
1. What does Hard-Spl do ? And can I hard-spl my phone ?
2. To install advanced config, do I have to jailbreak my windows, or do anything to install it ? I don't want to end up with useless phone
3. When I try to upgrade my default opera browser to the newest build, the instlaler cannot uninstall previous version of opera, neither can I because it is not listed in add/remove programs menu. And, if I ignore the warning, I get an error in installling the newest build, but somehow I have 2 opera mobiles listed in programs menu.
Thanks in advance, r4ster.

r4ster said:
Hi everyone, I have recently bought a htc touch pro from polish orange provider. I have browsed dozens of topic, trying to make my windows mobile 6.1 life more satisfying, but I have few questions to ask.
1. What does Hard-Spl do ? And can I hard-spl my phone ?
2. To install advanced config, do I have to jailbreak my windows, or do anything to install it ? I don't want to end up with useless phone
3. When I try to upgrade my default opera browser to the newest build, the instlaler cannot uninstall previous version of opera, neither can I because it is not listed in add/remove programs menu. And, if I ignore the warning, I get an error in installling the newest build, but somehow I have 2 opera mobiles listed in programs menu.
Thanks in advance, r4ster.
Click to expand...
Click to collapse
I probably can't answer your questions like a pro, but I had a few experience that I can share with you.
1. I don't know what Hard-SPL do, but I guess it's like jailbreak for Windows Mobile device. If you want to flash to a new custom Rom, you need to Hard-SPL it first (don't need to do this if you flash back to the original ROM). And yes, Hard-SPL your device
2. Jailbreak is only a term to unlock your iphone... With a Win Device, you don't need to unlock anything to be able to download and install other software. This is the beautiful part of a Window mobile.
3. Definitively can't help you here... but I know that plenty of thread has been posted for this matter... just do a quick search. However, I strongly suggest (with no responsibility) you to "Hard-SPL" and "CID unlock" your device and flash it to a new ROM. It will make your phone faster and much cleaner. Also, you'll get your new Opera install.
The question now is, which ROM
I suggest NATF's v2.3, but he'll be releasing a v3 today or so. Don't flash to it right away... just flash to v2.3 first and see if v3 is stable or not by reading people posts.
Flashing is not as hard as people claim... just read and be very carefully before you do it. Don't skip any step. The first time is stressful, but after that it's just a daily burger.

pandaboyy said:
I probably can't answer your questions like a pro, but I had a few experience that I can share with you.
1. I don't know what Hard-SPL do, but I guess it's like jailbreak for Windows Mobile device. If you want to flash to a new custom Rom, you need to Hard-SPL it first (don't need to do this if you flash back to the original ROM). And yes, Hard-SPL your device
2. Jailbreak is only a term to unlock your iphone... With a Win Device, you don't need to unlock anything to be able to download and install other software. This is the beautiful part of a Window mobile.
3. Definitively can't help you here... but I know that plenty of thread has been posted for this matter... just do a quick search. However, I strongly suggest (with no responsibility) you to "Hard-SPL" and "CID unlock" your device and flash it to a new ROM. It will make your phone faster and much cleaner. Also, you'll get your new Opera install.
The question now is, which ROM
I suggest NATF's v2.3, but he'll be releasing a v3 today or so. Don't flash to it right away... just flash to v2.3 first and see if v3 is stable or not by reading people posts.
Flashing is not as hard as people claim... just read and be very carefully before you do it. Don't skip any step. The first time is stressful, but after that it's just a daily burger.
Click to expand...
Click to collapse
So, I can flash any rom I want, and still have a fully working phone, after hard spl ?

r4ster said:
So, I can flash any rom I want, and still have a fully working phone, after hard spl ?
Click to expand...
Click to collapse
you have to hard-spl first before Flashing any Rom. Please read those sticky carefully. I do not take any responsibility of what you're doing.
This is what I did (it works for me without any problem)
0- I backup everything I need with PPCPimbackup and outlook
1- I HARD-SPL my device
2- I CID unlock my device
3- Flash to NATF's v2.3 ROM, hard-reset my device
4- Flash new Radio (this step is optional... and to find the best one, you have to test one by one.)
5- Restore my backup
6- Re-install extra software that I need.
Like I mention earlier, these steps work for me, and there are big chance that it will work for you as well... but I do not take any responsibility. Before you Flash to any ROM, HARD-SPL your device. and after flashing your ROM, HARD-RESET it.

pandaboyy said:
you have to hard-spl first before Flashing any Rom. Please read those sticky carefully. I do not take any responsibility of what you're doing.
This is what I did (it works for me without any problem)
0- I backup everything I need with PPCPimbackup and outlook
1- I HARD-SPL my device
2- I CID unlock my device
3- Flash to NATF's v2.3 ROM, hard-reset my device
4- Flash new Radio (this step is optional... and to find the best one, you have to test one by one.)
5- Restore my backup
6- Re-install extra software that I need.
Like I mention earlier, these steps work for me, and there are big chance that it will work for you as well... but I do not take any responsibility. Before you Flash to any ROM, HARD-SPL your device. and after flashing your ROM, HARD-RESET it.
Click to expand...
Click to collapse
Ok, what if the hard spl goes wrong, is there a way to unbrick the phone ?
And thanks for all the help !

r4ster said:
Ok, what if the hard spl goes wrong, is there a way to unbrick the phone ?
And thanks for all the help !
Click to expand...
Click to collapse
Well, first I hope that it doesn't go wrong. And second, I'm pretty sure you can stand the temptation of flashing to a new ROM, so you'll probably going to do it very soon. But Third, So far I haven't seen any thread that someone can unbrick their Touch Pro after a bad flash (he/she didn't Hard-spl before flashing, that's why)... However, there is a way to do it with the Kaiser... so don't lose hope there.
Just READ everything carefully, you have a 99.5% successful rate if you do. I would say that the 0.5% is just your bad luck (example Computer stop working during the flash... but that's just pure bad luck and you can't blame anyone but God)

Flashing OEM before Custom, deeper analysis

Recently, during testing TCP experience a symptom that also confirms my past experience. The most recent one I had was one of the network I connect to (I have 3 SIMs) having issue. This issue is gone after I did an OEM flash & hard reset before flashing again custom ROM.
I'm trying to understand better, thus starting this thread for all seniors and chef to educate us 'flashers' and 'noobs'
Firstly, it was said that Kaiser has different structure that actually flashing OEM before custom ROM is not needed. On Hermes, it's needed.
Question What is the primary differences that requires this?
Secondly, based on TCP's post, it seems that there're some leftover behaviour from previous ROM and hard reset does not take it 100% away. From forensic computing, we know that some data is not totally overwritten and can be recovered using special tool.
Question
Our phone does not use the special data recover tool for sure, but why that behaviour occurs?
When it occurred (in TCP's case), was the setting correct but the behaviour went against the setting, or the setting was incorrect due to the leftover and the behaviour conforming the incorrect setting. Which one?
Flashing OEM: there're so many version of OEM, each has it's own 'flavor'.
Question
What is so different from going direct from custom ROM (which is not bloated, and should perform better) to another custom than going OEM first. And if OEM is flashed, how many times it actually being needed (flashes, hard reset) to ensure its 'clean'?
What is the criteria of 'clean'?
If I bought my Kaiser in Asia, should I go with AT&T stock OEM or it's better to use HK WWE?
Should we go through whole route (SPL, Radio, OS) or just the OS?
I hope by raising this, we can understand our phone better and have a safer flashing experience

anagarika said:
Recently, during testing TCP experience a symptom that also confirms my past experience. The most recent one I had was one of the network I connect to (I have 3 SIMs) having issue. This issue is gone after I did an OEM flash & hard reset before flashing again custom ROM.
I'm trying to understand better, thus starting this thread for all seniors and chef to educate us 'flashers' and 'noobs'
Firstly, it was said that Kaiser has different structure that actually flashing OEM before custom ROM is not needed. On Hermes, it's needed.
Question What is the primary differences that requires this?
Secondly, based on TCP's post, it seems that there're some leftover behaviour from previous ROM and hard reset does not take it 100% away. From forensic computing, we know that some data is not totally overwritten and can be recovered using special tool.
Question
Our phone does not use the special data recover tool for sure, but why that behaviour occurs?
When it occurred (in TCP's case), was the setting correct but the behaviour went against the setting, or the setting was incorrect due to the leftover and the behaviour conforming the incorrect setting. Which one?
Flashing OEM: there're so many version of OEM, each has it's own 'flavor'.
Question
What is so different from going direct from custom ROM (which is not bloated, and should perform better) to another custom than going OEM first. And if OEM is flashed, how many times it actually being needed (flashes, hard reset) to ensure its 'clean'?
What is the criteria of 'clean'?
If I bought my Kaiser in Asia, should I go with AT&T stock OEM or it's better to use HK WWE?
Should we go through whole route (SPL, Radio, OS) or just the OS?
I hope by raising this, we can understand our phone better and have a safer flashing experience
Click to expand...
Click to collapse
i don't have answers for all your questions, but i know for myself since i have a tilt, i flash the stock att rom before i flash a cooked rom, and the stock rom i've been flashing is the full .exe that has spl and radio with it. i feel that the rom your phone comes with should be your rom to flash before flashing a cooked rom and thats why i flash the att rom and not the htc rom on my tilt. Seems like i have alot less troubles when doing this. heres what i do with my tilt:
1.)flash stock att 6.1 rom
2.)tap screen when prompted
3.)hard reset
4.)tap screen/then do the screen alignment
5.)let the customization process do its thing
6.)after it's done and reboots i do another hard reset
7.)flash custom(cooked) rom
8.)tap screen when prompted
9.)do hard reset
10.)tap screen/then do the screen alignment, and i proceed from there with installing my aps and all.
this has always seemed to yield great results for me

msd24200,
That's what I do nowadays, after several times having issue and more convinced after reading TPC's experience.
However, the technicality (how the chipset is being written, what's the 'ghost effect' is being handled by hard reset) etc. intrigues me and perhaps by understanding this, a lot of newbies will 'listen' (as I didn't ) until more flashing started showing funny symptoms

Flashing the stock ROM using the Ship.exe will use the Stock RUU instead of the custom one, so this will also Hard Reset your phone as part of the Flash.
I can't see any reason why a stock ROM would help, where a Hard Reset would not.
Ta
Dave

DaveShaw said:
Flashing the stock ROM using the Ship.exe will use the Stock RUU instead of the custom one, so this will also Hard Reset your phone as part of the Flash.
I can't see any reason why a stock ROM would help, where a Hard Reset would not.
Ta
Dave
Click to expand...
Click to collapse
Dave,
Your response basically answers my last question in another way. To 'stretch' the argument further, how many cycle of hard reset it's required to make the phone 'clean' and load the latest ROM properly?
(Actually, what happen to the phone, the internal drive and the XIP chip by doing hard reset .. ?)

anagarika said:
Dave,
Your response basically answers my last question in another way. To 'stretch' the argument further, how many cycle of hard reset it's required to make the phone 'clean' and load the latest ROM properly?
(Actually, what happen to the phone, the internal drive and the XIP chip by doing hard reset .. ?)
Click to expand...
Click to collapse
Just one AFAIK. As I said, the CustomRUU's we use, don't do a Hard Reset (so your phone isn't wiped when flashing Radio's / SPL's / Splashes). So you have to perform one manually, this should clear any remaining data?
Did I post this link for you to look at before? There's a bit of discussion with stepw on this.
Dave

This is what I learned/understand, the Hermes has an extended rom. This ex. rom gets written to as you use your phone. Flashing a new rom does not over write this ex. rom because not all custom roms come with a written extended rom. So information from the previous rom is left on this extended rom. The only way to clean the extended rom is to flash the OEM rom first, and then the custom rom. Thereby cleaning the extended rom and allowing phone to write new info to the extended rom.
So on the Hermes, if the custom rom comes with an extended rom, there is no need to flash OEM first. If it doesn't, then you need to flash OEM first to avoid freezes and Spontaneous HR's.
The Kaiser does not have an extended rom so there is no discernible reason to flash OEM first. I never do (except on that rare occasion where I am flashing from a new chef and he insists, in his instructions. ) I have flashed over a hundred times, and can count on one hand how many times I have flashed OEM first.

Interesting. I have the HTC RUU, I think I'll start using that to flash ROMs, and use the Custom for radios and SPLs. I'm curious if that will make a difference in needing to flash a stock ROM...

personally, I've never had an issue with just flashing a ROM (no hard resets or stock rom or anything). If I find a ROM I like, I just download it and flash, that's it.

mbarvian said:
personally, I've never had an issue with just flashing a ROM (no hard resets or stock rom or anything). If I find a ROM I like, I just download it and flash, that's it.
Click to expand...
Click to collapse
I have had to do hard resets for other various problems but none were due to a "bad" flash. I find a rom i want to play with and flash it

Flashing stock before TPC's Elite helps me out a lot. Prior to that, I never bothered with hard resets, and never really had an issue.

DaveShaw said:
Did I post this link for you to look at before? There's a bit of discussion with stepw on this.
Dave
Click to expand...
Click to collapse
Dave, no, you didn't .. but thanks that you do .. especially this post is very enlightening. That's exactly what I'm looking for, the understanding of how the hardware being written/overwritten, that should answer the need of flashing OEM or not before custom and if hard reset is required.
Thanks for all that has responded ..

I flash at least 10 times a day, and have never flashed OEM ROM or did a HR after flash!

I never did the OEM thing before either, until I flashed TPCs ROM and had very strange issues. Hard reset (few times!) didn't clear it up either, only after I went back to OEM ROM (ATT for me) and then flashed TPC did all my weirdness clear up.
Perhaps it hasn't been needed before, but maybe going to 6.5 has some special conditions? Or something about the way TPC built his ROM?
Or maybe it's the fact that flashing the OEM includes the Radio so there's some extra stuff being overwritten that doesn't with a custom ROM.
Or perhaps it was just the phase of the moon combined with the low sunspot activity.

curwiler said:
I never did the OEM thing before either, until I flashed TPCs ROM and had very strange issues. Hard reset (few times!) didn't clear it up either, only after I went back to OEM ROM (ATT for me) and then flashed TPC did all my weirdness clear up.
Perhaps it hasn't been needed before, but maybe going to 6.5 has some special conditions? Or something about the way TPC built his ROM?
Or maybe it's the fact that flashing the OEM includes the Radio so there's some extra stuff being overwritten that doesn't with a custom ROM.
Or perhaps it was just the phase of the moon combined with the low sunspot activity.
Click to expand...
Click to collapse
I'm going to try his next ROM with the HTC RUU, to see if that makes a difference at all. I think that this will all get worked out in time. I don't really want to flash stock first, mainly because I'm too impatient to start playing with a new ROM lol. I will if necessary though, only takes a few extra minutes.

anagarika said:
Dave, no, you didn't .. but thanks that you do .. especially this post is very enlightening. That's exactly what I'm looking for, the understanding of how the hardware being written/overwritten, that should answer the need of flashing OEM or not before custom and if hard reset is required.
Thanks for all that has responded ..
Click to expand...
Click to collapse
Anagarika, you started one of the best threads I've seen since being a member. You started with very logical and good questions which are worthwhile to pursue. Your timing is perfect for me as I was trying to think of an approach that would be fruitful. I would encourage you continue to be logical and methodical to get to the answers. Real answers!
If you haven't already considered it, let me mention that it was implied that the flashing tools have limitations... no disrespect to the author is intended in my comment, but while everything he says may be true, the fact is the same tool is used to flash OEM and stock ROMs. So perhaps it was just an FYI for us all or I just didn't get the point.
This is a REAL issue. Before starting up on this board again, I used the previous kit and did my own ROMs and used other ROMs, with my tilt and blah blah. Sorry, not 10 times a day though... yikes dude! This week, when I started up again trying to revive my tilt, it hit me right away with OEM ROMs. So, I downloaded 6 OEM ROMs and the stock ROM. Because of the mood and the mode I was in, I was only looking for success and not experimentation and thus I don't have exact data. But, I can tell you that once I used the stock ROM a couple of previously "problem OEM ROMs" are working.
For me this important information should be used to find out why and how it can be improved..... That is of course if the developers want to continue to develop.

gadgetologist said:
...the fact is the same tool is used to flash OEM and stock ROMs. So perhaps it was just an FYI for us all or I just didn't get the point...
Click to expand...
Click to collapse
Yet Dave said:
Dave said:
Just one AFAIK. As I said, the CustomRUU's we use, don't do a Hard Reset (so your phone isn't wiped when flashing Radio's / SPL's / Splashes).
Click to expand...
Click to collapse
I take that to mean that the tool isn't exactly the same. There is a difference.
Now, the real question, for me (since I don't understand these things) is this:
Is there any difference, large or small, in a hard reset on the phone and the (I think) task 28 command issued by the OEM RUU? Dave? Anyone?

SoberGuy said:
Yet Dave said:
I take that to mean that the tool isn't exactly the same. There is a difference.
Now, the real question, for me (since I don't understand these things) is this:
Is there any difference, large or small, in a hard reset on the phone and the (I think) task 28 command issued by the OEM RUU? Dave? Anyone?
Click to expand...
Click to collapse
No.
Ta
Dave

SoberGuy said:
I'm going to try his next ROM with the HTC RUU, to see if that makes a difference at all. I think that this will all get worked out in time. I don't really want to flash stock first, mainly because I'm too impatient to start playing with a new ROM lol. I will if necessary though, only takes a few extra minutes.
Click to expand...
Click to collapse
I theory it shouldnt make a difference. I rarely use RUU as I know I have fried a MB cuz of that (I am sure I had something to do with it as well)! And had an expensive brick!

gadgetologist said:
For me this important information should be used to find out why and how it can be improved..... That is of course if the developers want to continue to develop.
Click to expand...
Click to collapse
Exactly my point. I didn't want to dilute TPC's thread as he's doing a wonderful job and his thread should be about his ROM
To put it another way is that:
Do we know what exactly being done on our device memory (XIP, NAND, etc.) during a ROM flash, during a Radio flash, during a HR, etc.
By knowing what's happening, we know better what approach to take. For example, most cooked ROM is sized 50-80 Mb (newer ones). Those OEM's are usually about 100Mb. I guess by flashing OEM, it overwrites a lot of the space left behind by previous ROM. However, in my view, flashing custom that has smaller size will have some parts of OEM left over (using space only as comparison). This might be useful if all chef's do the cooking based on OEM and bugs hunting also based on OEM first. This will give almost a 'standard' benchmark against which all other bugs are troubleshot.
I suggest (to myself too) to re-read the thread Dave pointed, especially the post I remarked. I've not yet understood fully what it really means, so I'll do a re-read.
As a side note, I came from UIQ/Symbian before .. and it was discussed they used NAND while WM uses XIP .. (which I don't quite fully grasp also) .. and there's such thing as format internal drive and flashing OS too.