Related
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.
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...
With the release of various new kitchens for the Herald/Wing, I'm sure there are going to be many newbie cooks with many newbie questions. I'm creating this thread as a place to ask our remaining Chefs questions in a central location to avoid them being bombarded in the various other threads. I define a "Chef" as those cooks who have released many flavors of ROMs, so presumably they know what they are doing, and thay are still cooking for the herald/wing... aka Ivanmmj, Ace10134, Apreichner, IllConcepts, etc. No disrespect intended to those great cooks who have released ROMs in the past, but have gone on to other projects, aka toadlife, ttran001, itje, Papamopps, Dutty, ICP, KidnamedAlbert, ginolin, and others... if you are still around, feel free to participate.
Please limit your questions to issues with ROM COOKING. Take a look at Ace's Guide to Cooking before asking. Then if all else fails... ASK THE CHEF.
Please state which kitchen you are using, which WinMo build, and as much detail as possible. If you get the answer, please update your post so that it is not answered multiple times.
Reserved for later
Reserved for even later
I'll answer
And you've got my GUIDE.
Please link that in the first post, since that'll eliminate a large percentage of questions!!
http://forum.xda-developers.com/showthread.php?t=541504
Ok... I guess I'll ask the first question. I asked this in Ivan's SuperJustKitchen thread because it happened with his kitchen, but I'll ask it here for all the other roaming chefs and WinMo experts.
I cooked a spanish Rom for wm6.5 23016, using the default setting and adding a few items like voice command and .NETCF 3.7. The build was successful as well as the flash. Everything looks OK except that CABs wont install and Themes will not apply.
Ivan says he's looking into it, but I know he's busy. IllConcepts says he encountered this in one of his ROM builds but did not say how he resolved it. I would like to investigate the cause myself, but I'm not sure where to start. Can anyone tell me which program actually does the install of CAB files (when double clicked) so I can verify the file association in registry for CAB files. Also, how exactly are themes applied when clicked in the Today settings panel.
I haven't spent a lot of time on SJK yet. But when i tried it i couldn't install cabs or get an internet connections. Ivan can best answer that since its his Kitchen.
illconcepts said:
I haven't spent a lot of time on SJK yet. But when i tried it i couldn't install cabs or get an internet connections. Ivan can best answer that since its his Kitchen.
Click to expand...
Click to collapse
The CAB issue is only on the 6.5 builds and I'm looking for a fix right now.
The internet connection is because you didn't install and run Network Wizard. I'm going to guess that you use T-mobile. It seems that only T-mobile users run into the "problem" of the internet connection not working. (I think the average tmobile user is used to having a phone that is FROM tmobile and therefore already preconfigured by tmobile.)
lol ya the network config wizard was the cab I tried to install. Once the cab thing is worked out it will be easy sailing!
illconcepts said:
lol ya the network config wizard was the cab I tried to install. Once the cab thing is worked out it will be easy sailing!
Click to expand...
Click to collapse
That gives me the idea of adding EXT packages for each carrier...
ivanmmj said:
That gives me the idea of adding EXT packages for each carrier...
Click to expand...
Click to collapse
That would be cool! I am not 100% sure that it was the network setup i needed. When i would go to Setting/Connections/Connections there was nothing at all. Usually there is an "Add a new modem connection, Set up proxy, etc" But it was completely blank Except for the word connections on top. Usually on "Herald" roms on my wing i can manually do the wap.voicestream and be fine. I could be wrong however.... i am very new at this.
I recently installed the Rom for original windows mobile 6 from this site...I don't knw whether it is windows mobile 6 but it is working very well and I like it but there is a problem..the camera does not become bright like it used to when opened and the screen remains black..when press the capture button it shows an error...I have an htc tytn
adamkhanmian said:
I recently installed the Rom for original windows mobile 6 from this site...I don't knw whether it is windows mobile 6 but it is working very well and I like it but there is a problem..the camera does not become bright like it used to when opened and the screen remains black..when press the capture button it shows an error...I have an htc tytn
Click to expand...
Click to collapse
Well we can't help you if we don't know what ROM you're using. You should really know which ROM you downloaded. But it sounds like you're using an outdated ROM anyways. Get a newer WinMo 6.1 or 6.5 one, they all work fine.
And, this isn't the place for asking that question, anyways. This thread is for asking the chefs on how to cook, not personal issues with ROM's.
adamkhanmian said:
I recently installed the Rom for original windows mobile 6 from this site...I don't knw whether it is windows mobile 6 but it is working very well and I like it but there is a problem..the camera does not become bright like it used to when opened and the screen remains black..when press the capture button it shows an error...I have an htc tytn
Click to expand...
Click to collapse
Wrong forum. Please ask your answer in this forum. There should be a bunch of users more than qualified for helping you out.
thankyou and im sorry for posting in the wrong forum
Hi friends !
I'm usually trying to cook for my Kaiser, using OsKitchen. I could obtain 3 or 4 flashable ROMs -lots of disaster ROMs too- and now I'm trying to obtain a "decent" ROM with everything well located.
Then, I tried (I like Thahny25's ROMs made in Ivan's kitchen but I'ld like to create my own ROM and share it) to use Ivan's SuperJustKitchen, but it seems too difficult for me; also, thus I must spend more space in my Hard Disk as I can't have no shared folders with OsKitchen to cook for Herald/Wing and Kaiser.
So, I wondered to include Herald's files into Oskitchen structure. But as you maybe read on other places, I'm not an expert in this, but on building, landscape and environment (and this is too far from coding, programming, etc.).
Maybe some of you could use OsKitchen to cook for Herald/Wing. Or maybe some of you know "where to place" every file from Ivan's kitchen into OndraSter's one. This is what I'm asking to any charitative aim who can explain this.
Yes, I know I could ask OndraSter but I think he's busy on other things and also he does not know Herald's world but Kaiser's one.
TYhank you and forgive me the inconvenience, if such considered.
I was working on helping the developer port OsKitchen to the Wing earlier, but he got too busy.
It's an incredible kitchen, and I'm sure he'd help you port it to the Wing for us. It's the best kitchen I've ever seen!
http://forum.xda-developers.com/showthread.php?p=4854633
Well, Ivan/Ervius/Bepe kitchen is amazing, but for my degree of expertise, OndraSter's one is better for me.
@ace....
Yes, I remember you wrote something there. Now we must "only" put the files in the correct folders, but I'm trying to take the files from Ivan's structure into OndraSter's new one and I'm missing. Then, it's supposed the kitchen works for any device we want.
afn691 said:
Well, Ivan/Ervius/Bepe kitchen is amazing, but for my degree of expertise, OndraSter's one is better for me.
@ace....
Yes, I remember you wrote something there. Now we must "only" put the files in the correct folders, but I'm trying to take the files from Ivan's structure into OndraSter's new one and I'm missing. Then, it's supposed the kitchen works for any device we want.
Click to expand...
Click to collapse
I guess I might be able to look into it again tonight. I'll see.
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!