Samsung SGH-i617 (Blackjack II) WM 6.5 ROM Cooking - Non-Touchscreen Windows Mobile Other

Hello, I've currently acquired tools from various threads and am new to cooking, from what I've attempted to do, I was able to dump the WM 6.1 i617 pda.bin and looked around the OEM folder. However, I'm not sure where to obtain a 6.5 pda.bin to merge (if that's what you'd do to cook)..
I'm using nhathoa's 6.1 kitchen in an earlier thread here to take out the contents..and I've been looking at nokser's i600 6.5 pda.bin. What i did was dump the 6.5 bin and then tried to merge the 6.1 bin and then build a new one, but for a file that has consolidated into 7 mb (opposed to the 53+ mb from the factory 6.1 bin) pda.bin.
Now, i'm aware of the hazards to a firmware update..and while yes, I'm taking quite a giant leap here, I would like an expert to confirm my procedures if they would yield a positive result (WM 6.5 on my Blackjack II) or would end up in utter chaos if I were to try and flash this frankenstein of a rom. If not, would anyone be able to steer me in the appropriate direction?
Also, I have heard of a display issue with the Blackjack II on cooked roms with WM 6.5, and I'm hoping to fix it by finding the right combination of files either through experimentation with i600 (Blackjack I) bins or the i637 bins (the Jack I think?).
Let's hopefully kickstart this project!

I wish I could be of more help, but I have not cooked a ROM before. I would however be very appreciative if I could find a polished WM 6.5 ROM for the BlackJack II though. I saw some topics over at another forum regarding the display issues and how items wont be transparent, but I have hope for this project because the Samsung Jack is a WM standard device running 6.5.

ShuckyD said:
I wish I could be of more help, but I have not cooked a ROM before. I would however be very appreciative if I could find a polished WM 6.5 ROM for the BlackJack II though. I saw some topics over at another forum regarding the display issues and how items wont be transparent, but I have hope for this project because the Samsung Jack is a WM standard device running 6.5.
Click to expand...
Click to collapse
I know that we've run into some minor trouble, but using the 6.5 rom, it's fine despite a few minor issues. If you want, the thread is a good read, it might serve your needs and the visuals are good, also comes with the samsung wizpro interface too, albeit a few tweaks necessary to get the text adjusted accordingly.

BJ2 cooked rom
princedwi said:
I know that we've run into some minor trouble, but using the 6.5 rom, it's fine despite a few minor issues. If you want, the thread is a good read, it might serve your needs and the visuals are good, also comes with the samsung wizpro interface too, albeit a few tweaks necessary to get the text adjusted accordingly.
Click to expand...
Click to collapse
can you substantiate what you are refering too?
As far as I know there is NO other roms available for download besides 6.1 standard from AT&t or samsung. NOTHING cooked.
Am I wrong?
And as far as I rmemeber, it's because nobody could flash it to the device.
Please tell me I am wrong as I have killed my kaiser and am back on BJ2 and would LOVE another ROM.

bmunday said:
can you substantiate what you are refering too?
As far as I know there is NO other roms available for download besides 6.1 standard from AT&t or samsung. NOTHING cooked.
Am I wrong?
And as far as I rmemeber, it's because nobody could flash it to the device.
Please tell me I am wrong as I have killed my kaiser and am back on BJ2 and would LOVE another ROM.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=597430
py8, a wonderful contributor to the scene, has created a WM 6.5 cooked ROM for the BJII/i617. This was as of 12/30/09, and so far there's not much development or updates yet. Thing is, there are just minor issues, the worst being (IMO) to be a clock delay which i'm still having trouble with. If you want, the thread is quite the read. I summarized all of our findings on post 2, and if you wish to read up on recent events, read the most recent post on the thread and move back. The first few pages of the thread were related to translating an older py8 rom which was chinese that we tried to localize properly, until py8 developed specifically an ENG/USA rom.

Viva BlackJackers!

Related

Uprade for dummies? A few newbie questions.

Okay, I'm absolutely new to the PDA-Dev stuff. I'm a normal desktop software developer and I only use the PDA's as a normal user ;-)
I have the german T-Mobile branded MDA Pro.
So here are my first questions:
1.) Here in the forums we have a few threads about WM6 on the
- WM6 kitchen release
- Jwrightmcps Crossbow
- Final ULTIMATE - No Bugs HTC Universal WM6 ROM
- Universal WM6 Professional Rom
So, on a first look this is oabsolutely verwhelming. What is the right choice? In other words: When wanting to upgrade, what is the most stable version?
2.) What is this AKU stuff that's mentioned in nearly every post? I can't find a clear explanation of what this really is.
3.) I want to upgrade in a legal way. Loosing support on my MDA is not the problem, but I want a legally licenced WM6 on my pda. So where can I get that?
Are there any other hints, tips & tricks you would suggest for starting with that?
I think you on the wrong forum man!
You need Microsoft website
The only legal version of WM is WM5.
reed this
http://www.xda-developers.com/modules.php?name=News&file=showarticle&threadid=294142
1) Really, the only 'stable' ROM is WM5, WM6 will have some problems, but they are getting better.
2) I actually haven't figrude that one out yet... I assume its the version number or something... never really been important.
3) Short answer you can't, long answewr talk to t-mobile.I'm not aware of any carrier releasing WM6 for the universal, but for a legal upgrade you'd have to get it from your carrire (and most likely have them do it)
Okay.. well.. then.. hrm.. just ignore point three.
Back to point 1.) I do not want a rock stable WM6 on my MDA Pro. But when it comes to different WM6 versions/distributions to choose from, I want the most stable of them. So which one is the one to go for?
To Point 2.) I thought about some version numbering too, but I'm not pretty sure about that. But when it's not really important, why making the difference? ;-)
Is video call important to you?
There is still no known stable Video Call on WM6 yet except for the Video Call Beta by Jwright.
I think there is only 2 known source (correct me if I am wrong) of WM6 for Universal floating around in many forums. The one by Helmi (older AKU) & the one by Ivan (newer AKU). The rest are just variants of this 2. With Plus & Minus features, some bug fix, etc.
CWKJ said:
Is video call important to you?
There is still no known stable Video Call on WM6 yet except for the Video Call Beta by Jwright.
I think there is only 2 known source (correct me if I am wrong) of WM6 for Universal floating around in many forums. The one by Helmi (older AKU) & the one by Ivan (newer AKU). The rest are just variants of this 2. With Plus & Minus features, some bug fix, etc.
Click to expand...
Click to collapse
There are 3 bases:
The "Old" base (helmi 0.1, midget 0.1[.1], JWright, etc)
Ivan's new ROM (Ivan V1,2,3)
Midget's new ROM (Midget 1.0, Ivan's customisation of Midget, PDAViet (Latest)
My recommendation (and I think this is the fourth, possibly fifth, time I've said this - grab all the ROMs that are stickied to the forum - and test them all. If you're concerned about stability during your tests then get a spare phone to use.
And if you're trully concerned about stability and legality - stick to your vendor's version of WM 5
PhoenixHawk:
I 'was' in the exact same position as you. I'm a software developer, have never upgraded a ROM before and all these "Crossbow", "WM6 Final", "WM6V3.??", "No Bugs", "Final", etc, etc, had me somewhat scratching my head.
In a total nutshell, I did the following:
1
Followed this guide : http://wiki.xda-developers.com/inde...tion On How To Upgrade with Bootloader method
(i.e., downloaded WinRar, and "MaUpgradeUt_noID.exe")
2
Downloaded the first RAR file from this thread : http://forum.xda-developers.com/showthread.php?t=305512
3
When part 2 had downloaded, I copied the "MaUGradeUt_noID.exe" into the "NOCID_RUU_flasher_xda-devs" directory which is from the extracted RAR file.
4
Copied the "nk.nbf" file from the "Uni_WM6_v3_Ivan" directory into the "NOCID_RUU_flasher_xda-devs" directory from the extracted RAR file.
5
Double-clicked "MaUGradeUt_noID.exe" in the "NOCID_RUU_flasher_xda-devs" directory.
6
Started to worry as the program flashed my ROM.
Some 10 minutes later I had a fully working, zero problem HTC Universal running what looks to be a rock-solid stable version of Windows Mobile 6.
Hope this messages, coming from someone who has never done anything like this before is both easy to follow, 'n00b proof' and proof that it can be done from someone with zero-experience.
I'm sure there's a load of pro's and con's in which ever ROM is downloaded, but I took the chance at what I thought would be an easy to follow option, read as much as possible and it seems to have paid off.
Hope this helps,
J
TehPenguin said:
CWKJ said:
Is video call important to you?
There is still no known stable Video Call on WM6 yet except for the Video Call Beta by Jwright.
I think there is only 2 known source (correct me if I am wrong) of WM6 for Universal floating around in many forums. The one by Helmi (older AKU) & the one by Ivan (newer AKU). The rest are just variants of this 2. With Plus & Minus features, some bug fix, etc.
Click to expand...
Click to collapse
There are 3 bases:
The "Old" base (helmi 0.1, midget 0.1[.1], JWright, etc)
Ivan's new ROM (Ivan V1,2,3)
Midget's new ROM (Midget 1.0, Ivan's customisation of Midget, PDAViet (Latest)
PhoenixHawk said:
Okay.. well.. then.. hrm.. just ignore point three.
Back to point 1.) I do not want a rock stable WM6 on my MDA Pro. But when it comes to different WM6 versions/distributions to choose from, I want the most stable of them. So which one is the one to go for?
To Point 2.) I thought about some version numbering too, but I'm not pretty sure about that. But when it's not really important, why making the difference? ;-)
Click to expand...
Click to collapse
My recommendation (and I think this is the fourth, possibly fifth, time I've said this - grab all the ROMs that are stickied to the forum - and test them all. If you're concerned about stability during your tests then get a spare phone to use.
And if you're trully concerned about stability and legality - stick to your vendor's version of WM 5
Click to expand...
Click to collapse
Your answer should be like above.
PhoenixHawk need the second part, not me.
I thought Midget's was derived from Ivan's, so I was wrong.
@J
You are right, once you get the first working, you can read on or try as many until you are happy with one.
I'll give it a try.
I don't have a spare phone, so my regular one will have to keep up with me ;-)
But first things first: Currently I have some problems getting my MDA Pro syncing with my Vista client. The mobile device center just won't recognize my pda when it's connected. And I can't start about thinking flashing the rom until that's not working... anyone a clue?
PhoenixHawk said:
I'll give it a try.
I don't have a spare phone, so my regular one will have to keep up with me ;-)
But first things first: Currently I have some problems getting my MDA Pro syncing with my Vista client. The mobile device center just won't recognize my pda when it's connected. And I can't start about thinking flashing the rom until that's not working... anyone a clue?
Click to expand...
Click to collapse
Take some advice (I didn't listen, thought I was better than everyone else and ending up bricking my phone everytime).
Do NOT use Vista. For the sake of an hour's additional work in either installing another harddrive or swapping it temporarily, do everything within an XP environment.
Trouble free.

What can i do with my Kaiser?

hello to all of you.
first of all, as everyone, i want to thank everyone who is working hard to make our phones more interesting...
i have a TYTN II - Kaiser
windows mobile 6 professional build 5.2.1620
Rom Version 1.56.405.5
Radio Version 1.27.12.11
Protocol Version 22.45.88.07H (if it's even relevent)
i want to first of all if is there any fix for the bad sound on BT?
is there an update to windows mobile 6.1 and what is the difference? i didn't find an update to my rom version...
doe's WM 6.1 fixes the BT bad quality?
and now, i want to know what can i do to make my kaiser more intersting and fun.
please write me everything that come's in mind.
Thank You very much!!!
tlccksww said:
hello to all of you.
first of all, as everyone, i want to thank everyone who is working hard to make our phones more interesting...
i have a TYTN II - Kaiser
windows mobile 6 professional build 5.2.1620
Rom Version 1.56.405.5
Radio Version 1.27.12.11
Protocol Version 22.45.88.07H (if it's even relevent)
i want to first of all if is there any fix for the bad sound on BT?
is there an update to windows mobile 6.1 and what is the difference? i didn't find an update to my rom version...
doe's WM 6.1 fixes the BT bad quality?
and now, i want to know what can i do to make my kaiser more intersting and fun.
please write me everything that come's in mind.
Thank You very much!!!
Click to expand...
Click to collapse
It's ok guys I got this one.
http://www.google.com/advanced_search?hl=en
alltheway said:
It's ok guys I got this one.
http://www.google.com/advanced_search?hl=en
Click to expand...
Click to collapse
LOLz.
You need to do nothing, just send me your phone.
i know it's quite a big question but it would be nice to get some ideas.
things you tried and happy with it.
and an advice about the WM 6.1...
thanx
he's already told you what to do. Anyway, here is another hint, read the stickies & wiki.
tlccksww said:
i know it's quite a big question but it would be nice to get some ideas.
things you tried and happy with it.
and an advice about the WM 6.1...
thanx
Click to expand...
Click to collapse
It is a big question, but all your questions are answered in this huge forum already, so you have to go and do some reading and searching for yourself and you will find all your answers, plus more and you will learn a lot. You will see what people said about 6.1 and you will see waht people said about BT just by reading other threads.
Dude, theres official BT fix to download from the HTC: (Bluetooth Hot Fix (for HTC TyTN II) )
http://rapidshare.com/files/77706792/Kai06492.CAB.html
When it comes to "what You can do with You device" the limit is the limit of Your imagination. The people at xda-developer is doing magic, but please use the wiki's and the search function like:
http://wiki.xda-developers.com/
From this wiki You select the device of Your interest (Kaiser) http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
Now You have the world in front of You: Reviews, Discussions, Hacks and tweaks, ROM upgarding etc.
tlccksww said:
hello to all of you.
i want to know what can i do to make my kaiser more intersting and fun.
please write me everything that come's in mind.
Click to expand...
Click to collapse
1. the vibrate function can provide you hours of enjoyment, with proper placement (external or internal, your choice)
2. install as many programs as possible, filling up both main memory and storage card, using them once or twice then never use them again. after flashing a new rom, install a new assortment of software you probably don't need.
3. re-encode your favourite pr0n to ppc scaling and impress your friends with today's pocket pr0n.
4. port over wm5 from the wizard (blinding speeds, you won't be sorry)
5. read ALL the stickies in Kaiser upgrading area of forum (this isn't near as fun as the other suggestions, but you'll be able to answer your own questions, and be comfortable in the knowledge that you can hack your phone "without any help")
1 and 3 make a nice combo too!
Yes there is a WM6.1 upgrade, i am using Shaps at the moment and it seems to work fine for me.
WM6.1 doesnt give you a huge amount new, Shaps 6.1 rom for me has been stable and quick, i dont tend to install much on my phones though other than the included stuff. I do a few bits and install TomTom. 6.1 has threaded sms which is nice but has some annoying little issues, like i cant seem to find a way to forward sms messages any more. bit annoying.
Flicking through some of the other forums people seemed to be muttering about not being able to sync there 6.1 phones with ex2003, i use ex2007 though so i cant comment, mine works fine.
Havent noticed any bad sound quality over bluetooth. Be more specific though, do you mean stereo bluetooth or just normal.
I use the htc home plugin looks nice and works well.
Hope i have helped.
Rob
ps. Remember before you rush out and start flashing roms, read the wiki and things. You have to do stuff like hard spl and things first.
If i were you i would do it in this order.
1. hard spl
2. sim unlock (if needed)
3. wm 6.1 rom
4. radio rom
zetajunkie said:
1. the vibrate function can provide you hours of enjoyment, with proper placement (external or internal, your choice)
2. install as many programs as possible, filling up both main memory and storage card, using them once or twice then never use them again. after flashing a new rom, install a new assortment of software you probably don't need.
3. re-encode your favourite pr0n to ppc scaling and impress your friends with today's pocket pr0n.
4. port over wm5 from the wizard (blinding speeds, you won't be sorry)
5. read ALL the stickies in Kaiser upgrading area of forum (this isn't near as fun as the other suggestions, but you'll be able to answer your own questions, and be comfortable in the knowledge that you can hack your phone "without any help")
1 and 3 make a nice combo too!
Click to expand...
Click to collapse
You are one sick and twisted individual and I like it.
Start with the beginning of the internet at www.www.com and read through the entire thing.
I like to turn on wifi, 3g, gps, and bluetooth and use my kaiser to keep my coffee warm.

wm6.1 for shadow/juno

Even though some of us shadow/juno users don't have a section up here yet, are there any works in progress for wm6.1? I know they have it for the dash so I am not sure how much different it would be for the shadow/juno.
ya i would seriously love this haha i really want a 6.1 shadow rom with threaded text messaging
I would like to see it too
I would love to see a Juno/Shadow section
we've been fighting for an htc s640 forum for a few weeks now, they just ignore us lol, so i doubt you guys are going to get one as well anytime soon heh..
we're also poking around for a wm6.1 rom, no luck
dont' worry guys, you're not the only ones!
It sure would be nice to have our own section for the JUNO/Shadow, and I find it hard to believe that none of these ROM cookers have not been working on a WM6.1 custom rom for the shadow.
The 3125 has been a staple of the smartphone community for too long, and anyone who has used the shadow can appreciate the larger screen and better camera found in the shadow.
Come on y'all...........it's time for some JUNO/Shadow love
I guess we will have to start learning how to "cook" roms.
I'll try to learn something and post it on my website: http://www.freddyreyes.com/forums
There isn't that much to regular cooking of roms. The problem is porting it from another device(which I have no idea how to do). Here are the things you need to do to mod the rom after you have that very important step figured out:
Extract rom (extracted versions are floating around in this forum somewhere...(Check Calling all T-Mo Shadow users thread)
Dump rom into bin files and then convert to normal files/folders
Add/remove files as needed
Create XIP chain with working Shadow drivers (Don't know how to do that)
Convert fiel back to a bin file and recreate os file (nk.nbh)
I can do all of these steps except creating the new XIP chain. I have no idea where to start with that.
I just remembered, you also need to make any drivers in the actual rom that don't work universally to work for the shadow.
If someone can teach me some of the things to do to port the rom, I'll try and do it.
I don't understand why they won't make us a new section
ND4SPD said:
I just remembered, you also need to make any drivers in the actual rom that don't work universally to work for the shadow.
If someone can teach me some of the things to do to port the rom, I'll try and do it.
Click to expand...
Click to collapse
How can I give you the drivers? Do I need to "dump" my Rom and extract the files?
Here is the post that you mentioned: http://forum.xda-developers.com/showthread.php?t=351660
Well, I've got the shadow dump, but I don't know how to edit any drivers from a different devices wm6.1 to work for the shadow
Maybe Kavana (http://forum.xda-developers.com/member.php?u=373268) at the Excalibur forum can give us a hand. He ported 6.1 to the Dash.
Ok. What device's wm6.1 should we try and port and what build?
I know that there are currently 3 builds of wm6.1, but I don't know if they all have to do with smartphones(maybe only for ppc). Which should we use?
There are 2 that could work. The Dash is very similar to the Shadow. It has wi-fi, bluetooth, camera...however the camera is only 1.3 Mp and the other issue could be the "sure type" shadow's keyboard.
Dash (Smartphone)
http://forum.xda-developers.com/showthread.php?t=374890
Tornado (Smartphone)
http://forum.xda-developers.com/showthread.php?t=375670
The only problem I can see with using the dash is that it's landscape oriented and the shadow is portrait oriented. It doesn't matter to me though..
spl
i would say use the vox. there is a 6.1 build for the vox. and also not rain on this but, even if you make a build how are we going to flash it? spl will be locked i'm guessing and as far as i know nobody has come up with a jump or hard spl yet for the juno
Does anyone know if Lokiwiz works for the shadow? We could CID unlock it with that, right?
I tried that on my old Wizard and it worked not sure about the Shadow....
EDIT: I thought it CID unlocked my phone. I'll try something else. I downloaded the vox SYS and OEM folders that contain the rom image. (I'll start replacing all the parts tomorrow. Thanks pixelwix for reminding about the cid unlock and the Vox rom suggestion.

Original vs Cooked ROMs

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...

Clean Plain WM6.5 anyone? Begging the cooks!

Hi guys,
long time reader, first time poster.
I decided to register because it really galls me.
For past couple of weeks I'm trying all the WM6.5 roms here, and despite the names like "plain" "naked" and such, none are really plain or naked, or they are unstable or miss something or have other problems like they are "not well cooked".
Is there any cook out here who can cook really plain/clean WM 6.5 rom, perhaps with Mobile Office, but without any other apps whatsoever?
I'm using excellent eOS.4.888.Fire rom for 2 years now, and it is aging. I want to upgrade to WM 6.5 but I can't find anything like it.
I just can't believe it is so hard to cook a plain rom with office and without anything else, why do all the cooks have to include extra apps that they like? Is it so hard to cook a rom without them? I don't understand.
I beg you, o Great Holy Cooks of XDA, anyone of yous: please cook a one plain and stable English WM 6.5 rom for our Kaisers! Please!
I will gladly donate to make your effort worthwile, and I'm sure many other xda users would do the same, as almost every rom thread here have the same question about "is it clean/plain and stable rom"... and I believe it shouldn't be that much of work for those who already know how to cook!
try ahmedfikry
http://forum.xda-developers.com/showthread.php?t=618767
clean and plain
wm 6.5 like stock rom with office mobile 2010
What is it you consider a clean ROM? No manila? What apps dont you want? For me most of the ROMs on here are clean..
feckineck said:
wm 6.5 like stock rom with office mobile 2010
Click to expand...
Click to collapse
You can install the new office on a stock ROM. So why cook it?
clean
there is no 6.5 stock rom for kaiser.
no files other than those requierd to run.
no audio or pictures.
feckineck said:
there is no 6.5 stock rom for kaiser.
no files other than those requierd to run.
no audio or pictures.
Click to expand...
Click to collapse
Exactly!
This is what I consider plain and clean:
example from eOS.4.888.Fire rom:
forum.xda-developers.com/showpost.php?p=2729087&postcount=1
- Windows Mobile with its own apps (Active Sync, Calendar, ...)
- very few HTC apps that are specific to Kaiser's hardware features (QuickGPS, Bluetooth, wifi ...)
- MS Office and its neccessary apps
I don't want any audioboosters or other "cook's favorite apps" to take up space in the rom. Make the rom with UC and we can add anything else ourself, at hard reset
clean plain
just the os no htc or ms soft just winmo 6.5
Since Kaiser has a native 6.5 kernel, you get better performance cooking in everything that you want installed, but I'm sure you know well enough. Anyway, I can do this for you once or twice (only once or twice due to limited spare time on my part).
Tell me which build you want and a detailed list of every package you want and I will leave out everything else.
Clean Plain WM6.5 anyone? Begging the cooks
whats the least programs you can make it with no ms soft even office or pics or audio files .
we arent cooks or we would do it ourself thanks in advance.
I can take out every sound, pic, and document and AFAIK, it will still boot. Please keep in mind though, it does not give better performance with 6.5 NK to install things like Adobe reader, Java, Office, or .NET after flash. You will get better performance by cooking them in the rom. OTOH, I believe Manila, Phone Canvas (and anything else with many picture files) are better to be installed after flash instead of cooked in.
As to your question, I only have to leave in a few packages for the rom to boot, but many things will not work if not cooked in (DRM, I believe is one of them).
selyb said:
I can take out every sound, pic, and document and AFAIK, it will still boot. Please keep in mind though, it does not give better performance with 6.5 NK to install things like Adobe reader, Java, Office, or .NET after flash. You will get better performance by cooking them in the rom. OTOH, I believe Manila, Phone Canvas (and anything else with many picture files) are better to be installed after flash instead of cooked in.
As to your question, I only have to leave in a few packages for the rom to boot, but many things will not work if not cooked in (DRM, I believe is one of them).
Click to expand...
Click to collapse
leave in anything that has to be cooked in

Categories

Resources