Related
Hi everyone!
This is my first post, so I hope I get this right!
I've a T-Mobile MDA Compact 2 that has the T-Mo. branded ROM (ROM Ver: 1.12.2.23 WWE; Radio Ver:01.12.20) and I'd like to upgrade this to the latest (I've seen 1.13...) generic ROM easily!
Please consider: I've searched hi and low through these forums for upgrade tutorials, and have tried them out, but many complicate things with Big Storage and Ext. ROM etc. I've tried using the MaUpgradeUt_noID software but, after it reads the device's details (it's current ROM ver. etc), ActiveSync (on the desktop) terminates and I get an error "Error 101: Connection Error"!
All I want is to rid my MDA of T-Mo.'s software!
Currently I've hacked the regestry to change the Dialpad to WM5's default, replaced the Carrierlogo.gif with a blank, etc.
Please, anyone, can you tell me what I'm doing wrong, and why I can't upgrade my ROM!
Note: I've tried to be as detailed as I can! I'm fairly fluent in these sorts of things, so don't be scared about getting techincal, though please explain each and every step, as I've never done this before!
Thanks!
There are no other ROMs for the MDA compact II. This phone is a 'Charmer' and all the other posts in this section are talking about the 'Magician' which although the two look the same they are very different on the inside. A generic ROM is unlikely in the future because so far T-Mobile are the only carrier to produce this phone and most likely no one else will be.
Okay, I'll stick with my hacks for now. Thanks for letting me know though!
you can remove all the branding quite easily. changing the startup logo and editing the extended rom gets rid of most of it and replacing some of the .dlls and graphics with generic ones from another wm5 will get you back to the standard intellipad and dialler with working smartdialling.
All that's allready done! I've just got to change the startup graphic, but I'm not in any urgency, as I rarely restart the device!
Thanks for your input though!
Hi all, My first post so please bear with me...
I've searched the forums but cannot find the answer to this...
Would it be possible for me to simply run the stable and relatively problem-free AKU2.2 Qtek ROM on my Prophet but to have the extra phone functionality provided by the AKU3.x ROMs (ie. the added ability to send/receive business cards or Vcards as text messages)??
What I'm thinking of here is something like a .cab taken from the AKU3.x rom and applied to the latest "authorized" Prophet Rom which I understand to be the AKU2.2 Qtek rom, right?
I have tried most of the AKU3 roms out there as well as the WM6's and although these provide me with the phone functions I need for my workplace, they are still essentially just Beta ROMs with too many bugs and issues for me to run my Prophet reliably as a business phone when at work!
Please could one of you amazing and knowledgeable guys out there let me know if what I'm asking is possible?? And if so, which files would I need to obtain and apply?
Many thanks to you all for contributing to such a brilliant and interesting site!
Moz.
Sort of...
I know it's possibly bad form to reply to one's own posts, however, in case this info helps someone:-
Due to all the issues and niggles with the later ROM's for Prophet as I mentioned above, I have now gone back to Jesterz AKU2.2 R1 ROM - http://forum.xda-developers.com/showthread.php?t=284578
( AND, a *BIG* thanks to Jesterz for a very fine piece of work... It is VERY stable and F A S T!! )
...THEN, I have installed "SunnySoft vCard1.1" (http://www.sunnysoft.com/download.php?idd=108#p108) to enable this AKU 2.2 to have the ability to Send and Receive vCards - AKA Business Cards - via SMS/Text Message!!! I know this is a licenced piece of software (so not free), but believe me, this software works perfectly on top of the stable and standard Jesterz AKU2.2 R1.
I hope this might help someone. Enjoy.
Moz.
sorry for my bad english
i am a prof C++ programer
i know it sounds crazy but with the computer and programing there is no crazy
i just want a perfect rom for the Magician
why we are looking to the wm6 we want any good rom
we got the program
windows mobile 2003 rom editor
we got the rom on club i-mate
we got the cab of all good and great programs
we got one silly prob.
the passcode to edit the rom file
if i get it
give me 30 day to lunch the perfect rom
i think with the united we can make the WM Magician
the russin gays did it and they give us the txx rom right i think we can do it too
So, if i understand you correct your plan is to create a wm6 rom for the magician, right? This would be really cool...
P.S.
kingt0t said:
the russin gays did it and they give us the txx rom right i think we can do it too
Click to expand...
Click to collapse
i think you mean "guys" when you say "gays"
good luck with your project!
Kingt0t, what you want to do ain't something that hasn't been thought before...yes, you can do a WM6 for magician (hell, you can invent a new OS if you wish...lol) The thing is...time.
There's no drivers for the magician hardware built inside any WM6 ROM...(well, not entirely true - there's probable a few WM 5/6 ROMs which might have a few drivers for our hardware - but not all that are required so to make a workable magician ROM).
You probably would need to create drivers for all missing/required magician hardware...oh and above all...you probably would need to create a special/new bootloader because it seems to me that since WM5, the bootloader has changed it's way of loading the Windows Mobile OSes... (They use what is now called IPL/SPL...)
I'm not trying to discourage you...it's just that we (xda community) have heard about so many people with the same thoughts, giving up after realizing the enormous amount of work that would be required so to build a working wm6 magician ROM
Anyway, if you're really into it, then start by studying what hardware the magician has and how it works...
I can give you a few ideias right now:
- The CPU (PXA272) uses what is called a strataflash (It is glued to the cpu), which i believe there's not many models with this concept(if any). Most of them uses what is called DOC (Disk On Chip).
(if this ain't true, please someone correct me if i'm wrong)
- IDK if there's a driver for this CPU model in any other PPC with WM5/WM6...
- You will probably need to disassemble alot of dlls / .sys / Etc, so to figure out the functions names; what do they do; how do they interact with the rest of the OS...etc...
- Last but not the least, you would need to strip out alot of stuff since the magician only has 64Mb ROM or you could study how HARET (for linux) works and how it allows us to boot a SD Card partition image...
oh well...start posting away if you need help...for shure some gurus in here will start dropping you ideias, concepts, tests that were already made...
Best Regards,
Keeper
P.S: honestely, if someday microsoft decides to release the source code for WM2003 (like they did for win9x and windows 2000), then maybe, just maybe, we will be able to compile a modified version with some parts of the WM 5/6/xxx...
Maybe this is a good start, at least for WM5?
Ubiquio 401 has the same PXA272 CPU and 64MB ROM as the Magician, but it comes with WM5. Perhaps the IPL/SPL and CPU drivers that come with the FW will make less work for some smart person to make a custom Magician ROM.
Here is the Ubiquio 401 ROM, maybe somebody can extract some useful stuff from it:
ubiquio-401-v1.12.26.rar
I think it's also the same as the Gigabyte g-Smart i. g-Smart i uses WM5 AKU2. I don't know which AKU the Ubiquio uses.
Gnat,
There's one big issue in all this... When someone wants to seriously mess around with an operating system and it's "BIOS" (aka booloader) having direct access to the hardware is a must. Since we don't know the JTAG test point pins for the magician and knowing that no one is willing to trash their magician so that we can find out where they are located on the magician's PCB, (which would allow us to test various bootloaders + roms, without the risk of loosing our magicians), i doubt that anyone in here is willing to do blind tests with different model ROMs / Cooked roms, without some sort of backup like this one.
Check the last pages of this thread so to see what i'm talking about...(hell, check all this thread so to see what can happen when you flash something and there's a problem with it or along the installation of it...) : http://forum.xda-developers.com/showthread.php?t=319354
So, if you're willing to do this ( http://wiki.xda-developers.com/index.php?pagename=WallabyJTAG )...or know someone that is, then we might be able to start doing something... :-|
If we had JTAG access, we could start using the Windows CE 5.0 Evaluation Kit which would allow us to communicate directly to the hardware via JTAG and test cooked bootloaders and ROMs. (check this link for more info: http://msdn2.microsoft.com/en-us/library/aa447041.aspx )
Keeper
hope this dream come true....WM6 or just WM5 for IMATE JAM
kingt0t said:
sorry for my bad english
i am a prof C++ programer
i know it sounds crazy but with the computer and programing there is no crazy
i just want a perfect rom for the Magician
why we are looking to the wm6 we want any good rom
we got the program
windows mobile 2003 rom editor
we got the rom on club i-mate
we got the cab of all good and great programs
we got one silly prob.
the passcode to edit the rom file
if i get it
give me 30 day to lunch the perfect rom
i think with the united we can make the WM Magician
the russin gays did it and they give us the txx rom right i think we can do it too
Click to expand...
Click to collapse
if you do this, many will make a donation for your hard work...a NEW WM5 or WM6 ROM FOR the MAGICIAN.
Wow, that's a lot of work to find JTAG points. I have even more respect for people like Helmi if he had to find JTAG points for every device he has made a WM5 and WM6 for!
I don't think I will be finding the JTAG points on my Magician - I don't want to kill it! However, if anyone has a dead, fried or water damaged Magician, I will gladly pull the BGA off and trace the JTAG points.
If the JTAG points have a specific "signature" when viewed on an oscilloscope, I would be happy to trace them that way since I do have a 100MHz DSO available.
i hope too, this dream to ours magician
Oh btw...the taxist russian guy which released the 2.01~3TX rom did NOT made a WM6 for the magician - He simply opened up a magician ROM, changed a few icons, sounds, apps and packed it again...the Operating system still is WM2003se.
if you guys want to try and mod your own roms, use the following tools: alpinenbfdecode.pl, splitrom.pl and dumprom. They are available at the itsme website. ( http://www.xs4all.nl/~itsme/projects/xda/ )
Anyway, check this thread...there's a small script on how to re-create the XIP structure: http://4pda.ru/forum/index.php?showtopic=3924&st=1020#entry744997
Once again, this ain't gonna change your OS (there's no WM5/6 IPL/SPL for the magician) - it will only allow you to mod a few things... :-(
Keeper
Zoneaone
It very fantastic for your effort. thanks.
are you still there kingT0T?
ok guys hold on you are not making it easy i think it is mush simpler then you think
we need wm6 for jam
we dont have to edit wm6 to make it work on jam
we can upgrade the wm2003se to be wm6\5
we can find upgrads and some great programs to creat a wm2003se rom "main platform" looks like the wm6 and include some services in it like the voice command and renew the dailer and add some upgrades i think this is mush better coz we will not play with fire we can just try to make the perfect choise in 2003 rom with some upgrades and patches right
okey kingt0t...so what you want to do is something like taxist did...a modded ROM with a WM2k3 kernel core...
Well, one thing that i would suggest that you could start doing, would be a new bluetooth stack based on the WM 2k5/2k6 one (widcomm, i think)...
Anyway, idk russian and has so, i don't understand much of what is said on that link, but what i did understand is that taxist found a way of modifying the programs in a way that he could insert them has XIP (eXecution In Place), without breaking the expected original execution addresses...the thing is: he never revealed how he has done it...
There's a few guys in there that are trying to do what he has done by using the three tools that i've posted previously, but idk if they did acomplished the "XIP chain ROM address redirectioning"...
Regards,
Keeper
kingt0t said:
ok guys hold on you are not making it easy i think it is mush simpler then you think
we need wm6 for jam
we dont have to edit wm6 to make it work on jam
we can upgrade the wm2003se to be wm6\5
Click to expand...
Click to collapse
First prioduce a WM5.0 ROM instead of talking!
Yés kingtot wm6 4 Magician it is not a dream,it is a mirage...
kingt0t said:
we can find upgrads and some great programs to creat a wm2003se rom "main platform" looks like the wm6 and include some services in it like the voice command and renew the dailer and add some upgrades i think this is mush better coz we will not play with fire we can just try to make the perfect choise in 2003 rom with some upgrades and patches right
Click to expand...
Click to collapse
I'm not sure I understand. You want a WM2003SE that only looks like WM5/WM6? But then it can't run WM5/WM6-specific apps... what purpose is that? I hardly see the point. If that's what you want, it already exists and besides, you can just use Wisbar or something similar and make a theme.
WM2003SuperSe must run wm5 apps. it's main task !!!!
still dream or stop
what's going on?
wm6 again became dream
Welcome boys and girls to Ivan's school of cooking.As some of you may have noticed... I have a short attention span and tend not to stick to a project for more than a few days at a time... sooooo, instead of releasing the much awaited kitchen, I decided I wanted to give a class on cooking.
Basically, each week, I will prepare a lesson on a particular part of cooking. I will post instructions on how to do it and you can ask me anything you want on it for that week. After the week ends, I will grade you somehow... or maybe I won't... cause I'm lazy like that. I will upload whatever "ingredients" or tools that you may need for my lessons. Realize that each cook cooks differently with different tools. This is IVAN's way, MY way. As I am a very disorganized person who jumps from one thing to another, you'll notice that my style might be the same way.
Here's the agenda:
Disassemble a WM6 ROM with Hypercore
Disassemble a WM6.1 Kaiser ROM with KaiserKitchen (this is where you can get a lot of the newer ROMs.)
Port a ROM
Rebuilt a ROM
Cook a ROM
Strip a ROM
Advance cooking skills
More stuff
Etc
blah blah
Who knows
So.... Who's interested?
Table of Contents
Lesson 1: Getting to Know Your Device
Lesson 2: Breaking it down OEM style
Extracting your very own OEM folder.
Lesson 3: Getting Personal with Your OEM
Lesson 4: Time to pick up your SYSter's apron
Lesson 5 - Porting the SYS
Lesson 6 - The Glue that Binds us - Building a ROM
im interested i wanna be like itje and make a kick ass rom like touchit
your the man ivan
Count me in.
Totally Interested!!!!
i've been interested for a century
count me in too
Oooh, you are still surprising me! Of course!
shadowleo85 said:
im interested i wanna be like itje and make a kick ass rom like touchit
Click to expand...
Click to collapse
I'm not itje, but ok.
Lesson 1: Getting to Know Your Device
Every cook must first understand the device that they are cooking for. If you don't know how your customer works, you might not know what could be tasty to him/her and what could poison and kill him/her.
The Hardware
CPU: Omap850 200mhz
64MB RAM
QVGA screen (320×240 resolution)
128MB ROM
The ROM is subdivided into multiple parts. Those parts are the following:
The SPL (Think of it as the OS's bootloader.)
The IPL (Think of it as the BIOS.)
The Radio (The "firmware" that controls how a phone talks to the network.)
The Primary Splash (The first image you see when you turn on the device.)
The Extended ROM (Where providers store cabs that are automatically installed whenever you hard reset the phone.) [Format: TFAT16/12]
The OS. (Obviously, the Operating System. This is what most of you will touch.)
That's really the only information that matters and that you will need on the physical stuff. The last point is that the Wing is actually an HTC Atlas. The HTC Atlas is basically a HTC Herald with a modified keyboard and exterior coating. EVERY from both devices is compatible EXCEPT the keyboard driver which if not matched properly will cause some of your keys to not be properly matched up.
The ROM - An In-depth Study
As mentioned above, the ROM is subdivided into 6 parts. When you flash a factory ROM (henceforth referred to as a RUU,) you are flashing all 6 of these parts with new versions. The RUU is composed of the RUU flashing utility and the ROM itself which is stored in a format which we will refer to as NBH. The NBH file is a file that within it holds 6 NB files. Each NB files corresponds to one of the ROM subdivisions. The NBH file is also created with the memory addresses for each of these NB files and thus must match the device which it is being cooked for. The NBH will also have information on the ROM version, the Language version, the DeviceID (which will be HERA**** for any HardSPL'd device) as well as the country ID (which is 11111111 for HardSPL users.)
Your job as a cook will be to package an NBH that will have the following:
Your own cooked OS (Windows.nb/os.nb)
The newest Radio ROM (Radio.nb)
A custom or shrunk* Extended ROM (If applicable) (ExtendedRom.nb)
A splash screen (PrimarySplash.nb)
Under NO circumstance, should you replace the IPL or SPL. The risk of breaking someone's device is too great.
Flashing Methods
Refer to My Guide
Warnings:
You will have to flash your ROM many times a day in order to find and fix bugs. This is not something you can pick up and do in a few minutes. You are requires to have the following:
Time
No/Understanding Wife/Girlfriend
High Fustration Level
The ability to use the search research within the forum
Patience
A knack for figuring out things
Patience
A large PM box (trust me... you WILL be asked the same question 10,000,000 times)
Patience
A Herald/Atlast(Wing)
Patience
Lesson 2 will probably come earlier than next week simply because this week's lesson is only one of knowledge and not of actual work.
*Shrinking the Extended ROM will allow for more Storage space. More on this later.
i'm in for this.. i love your rom, and i want to learn how to make it.
Thank for sharing
ivanmmj said:
Lesson 1: Getting to Know Your Device
Every cook must first understand the device that they are cooking for. If you don't know how your customer works, you might not know what could be tasty to him/her and what could poison and kill him/her.
The Hardware
CPU: Omap850 200mhz
64MB RAM
QVGA screen (320×240 resolution)
128MB ROM
The ROM is subdivided into multiple parts. Those parts are the following:
The SPL (Think of it as the OS's bootloader.)
The IPL (Think of it as the BIOS.)
The Radio (The "firmware" that controls how a phone talks to the network.)
The Primary Splash (The first image you see when you turn on the device.)
The Extended ROM (Where providers store cabs that are automatically installed whenever you hard reset the phone.) [Format: TFAT16/12]
The OS. (Obviously, the Operating System. This is what most of you will touch.)
That's really the only information that matters and that you will need on the physical stuff. The last point is that the Wing is actually an HTC Atlas. The HTC Atlas is basically a HTC Herald with a modified keyboard and exterior coating. EVERY from both devices is compatible EXCEPT the keyboard driver which if not matched properly will cause some of your keys to not be properly matched up.
The ROM - An In-depth Study
As mentioned above, the ROM is subdivided into 6 parts. When you flash a factory ROM (henceforth referred to as a RUU,) you are flashing all 6 of these parts with new versions. The RUU is composed of the RUU flashing utility and the ROM itself which is stored in a format which we will refer to as NBH. The NBH file is a file that within it holds 6 NB files. Each NB files corresponds to one of the ROM subdivisions. The NBH file is also created with the memory addresses for each of these NB files and thus must match the device which it is being cooked for. The NBH will also have information on the ROM version, the Language version, the DeviceID (which will be HERA**** for any HardSPL'd device) as well as the country ID (which is 11111111 for HardSPL users.)
Your job as a cook will be to package an NBH that will have the following:
Your own cooked OS (Windows.nb/os.nb)
The newest Radio ROM (Radio.nb)
A custom or shrunk* Extended ROM (If applicable) (ExtendedRom.nb)
A splash screen (PrimarySplash.nb)
Under NO circumstance, should you replace the IPL or SPL. The risk of breaking someone's device is too great.
Flashing Methods
Refer to My Guide
Warnings:
You will have to flash your ROM many times a day in order to find and fix bugs. This is not something you can pick up and do in a few minutes. You are requires to have the following:
Time
No/Understanding Wife/Girlfriend
High Fustration Level
The ability to use the search research within the forum
Patience
A knack for figuring out things
Patience
A large PM box (trust me... you WILL be asked the same question 10,000,000 times)
Patience
A Herald/Atlast(Wing)
Patience
Lesson 2 will probably come earlier than next week simply because this week's lesson is only one of knowledge and not of actual work.
*Shrinking the Extended ROM will allow for more Storage space. More on this later.
Click to expand...
Click to collapse
Beautiful .... And I already get tons of pm's on aim . yahoo, msn and here asking the same damm questions. So I just tell all get aim and join my chat/tech room ....
Love to cook
Count me in... I would love to learn how to cook 'roms' looking forward to your next lesson...
regards
Prashant
Dopod C800 aka HTC Herald
WM 6.1 Ginolin
Ok I stayed up hoping for more info ... time for a power nap as its 7:00am here in nyc ....
ivanmmj said:
I'm not itje, but ok.
Click to expand...
Click to collapse
yea i konw but ur both neck and neck so i wanna make roms like both of yall
Interested
I'm interested in learning! My work load is crazy lately though so may not be able to stay current on the lessons, so no grading.
It's my birthday, so I didn't stay up creating lesson 2... I stayed up playing video games. lol (I turn 25 today. I'm an "old" man. lol)
Congrats, happy birthday
ivanmmj said:
It's my birthday, so I didn't stay up creating lesson 2... I stayed up playing video games. lol (I turn 25 today. I'm an "old" man. lol)
Click to expand...
Click to collapse
Happy BDay Ivan!
ivanmmj said:
It's my birthday, so I didn't stay up creating lesson 2... I stayed up playing video games. lol (I turn 25 today. I'm an "old" man. lol)
Click to expand...
Click to collapse
Happy Birthday Ivan
A few days ago I posted something on L26 V5 Diamond thread. It was either a very broad subject or a very naive one that nobody cared to write something in reply. Maybe I shouldn't have posted there.
Now I bring the subject here in a separate thread hoping that we would all share our views and experiences with regard to Original/Official WM6.1 ROMs vs the cooked ones. I already apologize if the subject doesn't deserve a thread and leave it to mods to decide whether the thread should remain or be closed.
Here's what I'd posted there:
So far as bugs are concerned, who's the culprit : build 19588.1.1.4 ? or L26_K_D_V5 ??
It seems an error is repeating so often & so regularly that it's becoming a systematic error. What am I talking about?
Well, we usually get so much focused on L26_XXX ROM or Dutty's_XXX ROM ...etc. that we totoally forget about the "Original/Official" ROMs these cooked ones are based on.
Somewhere in the devine XDA text , God once said :
Flash an "original/official" ROM / HR / flash the XXX cooked ROM / HR
The above is now a universally accepted verdict among us frequent ROM flashers. But how many of us do stay upon the "Original/Official" ROM - whether HTC or AT&T ...etc - for 10 minutes (or 10 seconds for that matter !!) ??
We flash the "Original/Official" ROM (whatever version it is - though , we generally tend to flash the Latest Original/Official one) only for the sake of the above said verdict and certainly not to see how that original ROM works on our devices. Understandably, this happens because we're in a hurry to flash the beautiful cooked ones.
What is my point?
How many of the rulings we pass (and the bugs we report) on L26_K_D_V5 have been tested (over a period of a week or so) upon the "Original/Offical" ROM the V5 is based upon (i.e. CE 5.2.19212 Build 19588.1.1.4) ?
Perhaps it's time that someone with an authoritative knowledge of ROMs takes the list of reported bugs/issues of V5, flashes the Build 19588.1.1.4 , rests upon it for a while , and sees if these are native issues of the "Original/Official" ROM or Leo's V5.
Does it sound too idiotic and naive? Maybe. But at least I can claim that I have not seen such thorough comparison between these two specific ROMs anywhere in the forum. Of course, the wise redbandana (God bless him) usually brings us news of (and introduces to us) new Original/Official Kaiser ROMs in separate threads. But what I mean is thorough comparison between these two specific Original/Official and Cooked ROMs.
Cheers
i see your knoweldge and believe that you are on to something, i don't remember what ROM i was on cause i have flashed almost all of them, but when i went to the official of the same build a lot of the same errors were being seen. most times as long as the chef knows of these problems in the official rom they try to cook the fixes into their version but it is not easy to see every bug in a rom by yourself.
tubaking182 said:
i see your knoweldge and believe that you are on to something, i don't remember what ROM i was on cause i have flashed almost all of them, but when i went to the official of the same build a lot of the same errors were being seen. most times as long as the chef knows of these problems in the official rom they try to cook the fixes into their version but it is not easy to see every bug in a rom by yourself.
Click to expand...
Click to collapse
the fact is , up in the heaven , all mods/chefs/very_senior_members know all about these things. My point was to open up a window for us mortals down here to have a clearer idea about what we see in (and pass judgements on) cooked roms.
The undeniable truth is that each chef cooks his rom on a specific original version/build and a clearer knowledge of the original built in each case (and a comparison between the two) allows us mortals to have a better understanding of what the chef has actually done in his rom.
As a very minor and silly example, while in L29 V5 Diamond I am struggling to to see why the "disconnect" button in GPRS connectivity bubble is missing, it would be helpful to know whether this is the "default" option of the original built or is it Leo's - and if it is Leo's, what are the merits/faults of his choice.
You may ask why I don't do such thorough survey myself ? Well, to be honest, I would really die to have such extensive knowledge and expertise. But the fact is, some people are savvys and gurus and some are not. It takes me a lifetime to be as knowledgeable as Dutty or Leo or Alex ...etc. I just hope that in here each of us can bring just a little piece of his/her info to share with others on the subject of this comparison.
Well, I've been using HTC original ROMs for a long time, so here's my report:
Original HTC WM 6.0:
- Great radio (1.27.12.17), GPS fix fast, good battery life
- Skype works
- Cleartype works OK on landscape
- No missing G icon or disconnect button when you click the connection icon
- Feels fast enough (a lot of RAM free)
Original HTC WM 6.1 released on may
- Less than 60 MB RAM available on boot
- Bad radio (1.65.16.25), problems connecting to WiFi with WEP enabled, slow GPS fix
- Skype does not work
- Cleartype does not work correctly on landscape
- Does not feel faster, needs new SPL to avoid random freezes
- No missing icons / apps
Original HTC 3.02
- My favourite unless Nothrills comes up with something better
- Excelent radio (1.58.26.20), best GPS and WiFi
- Skype does not work
- Landscape mode works OK
- Camera can be easily patched or updated to 5.04
All of them come with Office and Onenote, Windows Live, and usual utilities
All of them can be tweaked with KaiserTweak or AdvancedConfig and you get a pretty much fast and estable ROM that just works.
No screen redraw problems, no blank screens, no missing buttons, no missing apps...
vcespon said:
Well, I've been using HTC original ROMs for a long time, so here's my report:
Original HTC WM 6.1 released on may
- Less than 60 MB RAM available on boot
- Bad radio (1.65.16.25), problems connecting to WiFi with WEP enabled, slow GPS fix
- Skype does not work
- Cleartype does not work correctly on landscape
- Does not feel faster, needs new SPL to avoid random freezes
- No missing icons / apps
Click to expand...
Click to collapse
It's amazing that while reading your report on Original HTC WM6.1 , I suddenly felt as if I was reading the threads of some of the new cooked kasier roms! Everything you said (and a lot not mentioned here) are exactly the same problems reported in those threads over and over again.
So next time when one reports in , for example, Dutty's new rom thread that : "Skype is not working" , or "the cleartype in landscape bug" he should know that these are exactly the same issues in the original 6.1 and has nothign to do with Dutty's rom.
I agree with you so much. Amazingly to Cook a rom is a few files added here, a few files deleted. Put in what you want, make a few tweaks to the registry and Whaaa Laaa.
AMazingly, WM6.1 has a lot of bugs. Probably not what Microsoft expected when they developed the software. The landscape issues I try to tell everyone over and over it has nothing to do with what the Cook did, its a WM6.1 problem.
I do not use skype but I am assuming the same thing. I think in this thread, we should add the most common problems that we have so we can start looking into them more deeply.
Obviously the cooks inherit the bugs of the ROMs they use as base.
HTC finally released an official WM 6.1 ROM for the Kaiser, with "improved graphics" but at a cost.
- Bad radio. 1.65 radios are not better than 1.27 or 1.58. Ask anyone about GPS fix or battery.
- They changed a display routine so it's faster, but they screwed cleartype on landscape mode, that was working on previous HTC ROMs
- A lot less memory available, and I do not see a big speed increase in return
- The ROM feels heavier than previous one, the screen switches in one move, but the total time to do the switch is longer than previous ROMs
- Skype does not work, it was working on WM 6.0
Some of these bugs have been corrected by cooks when adding files from other builds. HyperDragon III works OK on landscape, ROMs from L26 and Dutty work with Skype... But they introduce other bugs like the missing G icon, or disconnect button.
I hope they interchange their findings so we finally have a ROM where everything works. I don't care if it gets 1432 or 1512 points on some benchmark, if HSDPA does not work, or the device soft-resets while playing MP3, then I'm not going to use that.
Reading all of this makes me wanna downgrade to 6.0. Until we have a working Android, that is...
Just wanna share with you as I am using an official ROM for a long time now.
Original ROMs are the best as they have every thing working. Yes everything, sometimes a minor bugs are annoying like I was unable to send a vcard as sms using one of the super ROMs.
I think the only point is tweaking. If we tweak the original ROM they will perform as good as the cooked one.
As much as the chefs change in ROM as much as we get bugs. My opinion is chefs should concentrate on main issues and always release lite versions leaving options for users.
I have to admit that I have learnt a lot from cooked ROMs which helped me to tune the original ROM to my best.
msharaf said:
Just wanna share with you as I am using an official ROM for a long time now.
Original ROMs are the best as they have every thing working. Yes everything, sometimes a minor bugs are annoying like I was unable to send a vcard as sms using one of the super ROMs.
I think the only point is tweaking. If we tweak the original ROM they will perform as good as the cooked one.
As much as the chefs change in ROM as much as we get bugs. My opinion is chefs should concentrate on main issues and always release lite versions leaving options for users.
I have to admit that I have learnt a lot from cooked ROMs which helped me to tune the original ROM to my best.
Click to expand...
Click to collapse
Yeah, that's what I have suggested yesterday but met the offence only.
Well, different people, different opinions.
ryncppr said:
I think in this thread, we should add the most common problems that we have so we can start looking into them more deeply.
Click to expand...
Click to collapse
ryncppr, apart from the need to learn more about Original roms, i also came across another strange fact that is widely ignored.
Does anyone care "what" original rom to flash before flashing his desired cooked one? I read many of the threads ; it seems that nobody does pay any attention to this matter. BUT the type of Original rom we flash before flashing the cooked one (depending on our geographical location and the make of our phones), DO CERTAINLY COUNT A LOT.
This is what I noticed and just posted on Dutty's V1 thread :
http://forum.xda-developers.com/showthread.php?t=398271&page=90
Technically, I don't understand why this happens (perhaps you as a good chef could explain this matter in technical terms) , but I have no doubt now that it is crucially important what original rom we flash first.
Bardia Garsha said:
ryncppr, apart from the need to learn more about Original roms, i also came across another strange fact that is widely ignored.
Does anyone care "what" original rom to flash before flashing his desired cooked one? I read many of the threads ; it seems that nobody does pay any attention to this matter. BUT the type of Original rom we flash before flashing the cooked one (depending on our geographical location and the make of our phones), DO CERTAINLY COUNT A LOT.
This is what I noticed and just posted on Dutty's V1 thread :
http://forum.xda-developers.com/showthread.php?t=398271&page=90
Technically, I don't understand why this happens (perhaps you as a good chef could explain this matter in technical terms) , but I have no doubt now that it is crucially important what original rom we flash first.
Click to expand...
Click to collapse
A big problem is that people do not believe you need to hard reset after you flash a ROM. You do. THe process that WM has built in only clears the memory and storage files, leading to useless junk that gets left behind.
I used to think if I flashed a ROM it was completely getting rid of the last rom, which has found not to be the truth. Though a clearing system file is now shown on the screen, it is not truly getting rid of all the old files, hence the problems with putting ROM over ROM.
bad practice
I know it's a bad practice to have, but I very rarely hard reset my phone after a flash, and I have to admit I never flash the originals back to my phonebefore flashing. once in a great while I hit a weird glitch that I can't seem to find a solution for, and so I hard reset to fix it. I guess part of it is that i'm so impatient that I can't stand to wait a few extra minutes. I check the site anytime i'm not working and if there is a new rom available I've downloaded and flashed before looking through the bugs found. I guess i'm gonna start going to originals first and hard reset every time, now to help on that, is there a way that we know of that will automatically do the hard reset one time right after a flash? I know UC wouldn't work cause it runs after the hard reset/flash so it would loop. if we could cook the rom to auto reset once and one time only it would help out those that ocasionally "forget."
on a side note, this was typed through my phone so sorry for any spelling errors there might be and thank you ryncppr for a great rom.
tubaking182 said:
I know it's a bad practice to have, but I very rarely hard reset my phone after a flash
Click to expand...
Click to collapse
The truth is you are a big boy and can handle the giltches/issues. Just take a look at hundreds of posts out there in which people complain and report about some of the most unthinkable issues (e.g. "my phone resets itself every 5 minutes" (Jesus Christ) !! or "when I push the call button my phone starts media player"!! perhaps soon we should expect posts that will read: "after disconnecting the bluetooth headset, our washing mashing stopped working" !
I know that for example Dutty is very serious on his belief on flashing original/HR/cooked/HR every single time one wants to flash a rom - and for god's sake this man really knows what he's talking about.
Sometimes very bizarre things happen when one ignores the above must-do process.
However, my main object here was to invite people to share their bits of info on what a specific original rom does (or might do) to our devices when it's flashed prior to a specific custom rom , and why.
and btw, your spellign is brilliant.
original HTC Tytn II ROM
Hello, since I`ve updates my HTC Tytn II I have too much problems with my internet connection, wifi, gps,...so I would like to upgrade to the previous Version WM 6.0 Prof. (original, german).
Have someone a linke where I could find original (geman) ROMs?
Thanks for your help,
Lou
loubega said:
Hello, since I`ve updates my HTC Tytn II I have too much problems with my internet connection, wifi, gps,...so I would like to upgrade to the previous Version WM 6.0 Prof. (original, german).
Have someone a linke where I could find original (geman) ROMs?
Thanks for your help,
Lou
Click to expand...
Click to collapse
I'm afraid your post has nothing to do with this thread - just wonder why u posted this here !
anyway, you can find the original/official kaiser roms here:
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
HTC & AT&T do different things
Ok, in oder to see the effects of different original/official roms we flash before the custom rom, i did the following and noticed an obvious difference:
1) flashed AT&T offiical WM6.1 CE 3.14.502.1 (built 19209) and then L26 V5
- flashed the same official AT&T and then Dutty's Diamond V1
in both cases, both L26 and Dutty's roms were not functioning optimal on my device. had to deal with many issues (from BT to GPRS to connectivity ...etc. as well as general responsiveness of the device)
2) flashed HTC_WWE_3.28.405.0 and then L26 V5
- flashed the same original HTC and then Dutty's Diamond V1
in both cases , both L26 and Dutty's roms were functioning a lot better on the device. almost %90 of the previous issues were gone.
in both 1) & 2) I used radio 1.65.16.25 and observed strictly the same procedure (usb flashing, same HR, no SD card inserted, no 3rd party app installed ...etc.)
what's going on? i'm now more confident that the type/version of the original or official rom we flash prior to the custom rom affects the custom rom and its behavior on our devices hugely.
this is still widely igonored by the chefs as i've never heard them on their threads mentioning/suggesting what original/offiical rom should be flashed prior to flashing their cooked roms.
I think alot of what you are trying to accomplish here was discussed previously. I have always been a proponent of trying to use Original ROMs in order to better understand what is "original" vs what is cooked and doing all tweaks by myself:
http://forum.xda-developers.com/showthread.php?t=389519
Just stumble upon this. I think this one is quite insightful. But yet we have only Cooked ROM threads, reviews, and comments. Not on Stock ROM... once a while though *wonder why.. LoL*
Maybe we should encourage people who use stock ROM to start a thread for their own stock ROM version and make some reviews among the users? Not so good idea, but not so bad either.
I mean this thread is not only to know what work in 6.1 and what doesn't, right?
And for the current moment maybe we could have common concensus for responding to 'bizarre problems after flashing ROM xx.. bla.. bla bla' with : reflash stock rom -> hard reset -> reflash cooked rom -> hard reset -> still have problems?
Just stumble upon this. I think this one is quite insightful. But yet we have only Cooked ROM threads, reviews, and comments. Not on Stock ROM... once a while though *wonder why.. LoL*
Maybe we should encourage people who use stock ROM to start a thread for their own stock ROM version and make some reviews among the users? Not so good idea, but not so bad either.
Click to expand...
Click to collapse
Schizo, im gonna do it in few days! I'm working on cooked first. But i have in plans to test Stock ROMs...