midget_1990_v0_1_vanilla_wm6.rar
I've found this link in the wm5 upgrade forums but without any explanation or comment...
1-What is included in this file?
2-Ripped from which device?
3-Radio compatible with BlueAngel?
4-Every devices may had different hardwares, is that rom had universal H/W
support?
5-Are the Rom makers interesting or working on this rom?
6-Who had test this rom?
7-Which device still use this rom?
8-What is new in this rom?
9-Is there any screenshots here?
10-If someone crash him device when upgrading to this rom, who can help?
11-I know this is not a forum thread but that mean this rom-link not dangerous?
12-Can anybody give some explanations over Windows Mobile 6 (I wrote allways as 6 because this rom is not Windows Mobile 2006 <I've heard somethings on somewhere>)
At the last:
This is the best of Windows Mobile
Powered Devices Fan forum...
This site had very very unique threads, tools, roms, and lots of stuff...
I've BA & use wm5 rom by helmi_c;
what I think about this rom, 3 answers I have:
1-Bluetooth problems with my headset.(msi and motorola h3 too) without BT_Patch. But it's my problem and thats mine choose, i must wait fix. GPS and other BT services works perfect.
2-Wifi problem, sometimes needs to reset. May this problem will never resolve, i can live with this
other side Wifi give beter performance than windows 2k3, really! I think it's come from ram paging pool,
exm: I control my pc with wifi and i can play GTA san andreas from my pda, eheheh, i can show my msn web cam to
my friends
"When they out of my house! range som's 30 m"
but som's pda goes slowing down.I don't know why.
3-Phone sometimes give error while turning on/off flight mode and phone goes to lock while speaking longtimes. But not allways.
now,
There is 5 creators here, and they make wm5 roms whith different roms but they have some problems may the creators can works together and give us a clean wm5 or wm6 rom.
"What a good wish"
Sorry for the long message, but i need some information, may someone can givethis. Because i've belive here.
MANY MANY THANKS READING.
I allready saw too , but it's for Universal, let's hope we will have soon a wm6 for BA
Well they have one for both the Wizard and the Universal now, we just need one for the Blue Angel, come on guys, the suspense is killing us
Will it be possible to port the ROM for BA? 'Cos I saw some post somewhere in 4rum saying it seems impossible???
Will it be possible to port the ROM for BA? 'Cos I saw some post somewhere in 4rum saying it seems impossible???
Click to expand...
Click to collapse
that we dont know yet, also because most of BA developers are changing to Universal at the moment. honestly, I dont see that it's gonna happen soon specially without having enough developers working on it.
There is a ROM out for the HTC Universal and HTC Wizard. There is nothing yet for our HTC BA.
I did have a look porting it, but it looks pretty impossible for me to do -I'd never done it before and there is no base ROM at the moment.
Only thing we can hope for is some of those BA gods do a spiffing job on it!! (We know who they are )
Pray that it'll be quite possible!!!
imatrix said:
that we dont know yet, also because most of BA developers are changing to Universal at the moment. honestly, I dont see that it's gonna happen soon specially without having enough developers working on it.
Click to expand...
Click to collapse
So sad to hear this. All we need are the base cleaned ROM and relevant tools to edit. But like you said, I guess we may be gonna have to wait for long, if it's really possible.
nht_max said:
So sad to hear this. All we need are the base cleaned ROM and relevant tools to edit. But like you said, I guess we may be gonna have to wait for long, if it's really possible.
Click to expand...
Click to collapse
You can edit the crossbow roms with mamaich tools for WM5, but there is more than adding drivers for make WM6 work on BA, the main problem is WM6 core, if someone manage to port it it will work
(Nothing's impossible, but some things are harder to achieve)
xplode said:
You can edit the crossbow roms with mamaich tools for WM5, but there is more than adding drivers for make WM6 work on BA, the main problem is WM6 core, if someone manage to port it it will work
(Nothing's impossible, but some things are harder to achieve)
Click to expand...
Click to collapse
totally agree to that xplode, so hurry up, we are all waiting
anyway plz do your best
alternately you COULD try running xbow on top of wm5 core (similar thing was done for OS X on PC's, until recently for that they used 10.4.8 OSX with 10.4.4 kernel) If this works (it should - kernel for WM5 is 5.1.xxxxx, WM6 is 5.2.xxx, only a 0.1 increment) then you could run crossbow just without the core
without the core rom, are we gonna have most functionalities still?
i dont know - im just brainstorming atm
hopefully most of the features will be separate from the core, remember it's still based on CE 5 and only a .1 increment
Hi guys,
I've been looking at the WM6 leaks for Uni and Wiz with a view to getting something running on BA.
The 2 biggest problems are
- the kernel (nk.exe) is compiled per-hardware platform.
so a WM6 kernel exists for universal, and for wizard, but not for BA
the only reason we were able to run WM5 on BA was because of a leaked
kernel for our hardware platform
- the WM6 roms are much larger than wm5 ones
Even a base set of features seems to need careful packaging and some
UPX compression to fit in the BA's 32mb ROM
Even if the WM6 applications and features could be persuaded to run in the existing WM5 kernel, the result could never be really called "WM6".
Without a proper kernel for BA, I doubt it's really worth the effort.
So we all wait for the right kernel, then thing's done. Think that It's gonna be available someday.
That seems im? Possible.
Why?
Some members already try to tell this
bastard reality but it's true.
Core system = kernel structure
must be emulate to BA's H/W.
The kernel softwares especially written for which device will use it.
but we forget a point!
All of Windows Mobile OS's had a SDK
and they have flexible content.
What i mean?
We have 2 problems.
1- Hardware compatibility.
(Drivers and device functions management )
2- OS infrastructure
(Device based shell and kernel api management.)
Explanation:
1-We're already know all of PocketPC devices had different hardwares. We must make or find or emulate current drivers to our BA...
How?
Too hard... it's an engineer work.
Assembly and C knowledge necessary.
But we have a key:
Every Windows Mobile OS kernel versions
written in same way. May we can use
old drivers? may anyone can emulate them.
2-OS integration and device management structure with shell and kernel api's.
Windows OS's allways use API system with 2 types.
1) Shell api ( Interface )
That used for visual and non-visual OS functions. like DirectX api's.
2) Kernel api (Core system)
To use device funcitons,
accesing Processor, RAM, ROM and
others.
Some Windows mobile versions had same hardwares but they managed
with different API's
Why?
I don't know...
what we need?
We must emulate this API's?
How?
Not hard as first problem but not easy too...
I think there is one way.
We try to hardluck, remake and convert old API's to the new ones.
This is illegal and outlaw. Goes to reverse engineering and Bill gates will angry...
Yes that is impossible as first one.
Windows Mobile 5 OS's can be port but at this time no one have so much information about WM6 kernel and shell systemand nobody did make an explanation about WM6 SDK how it's works.
This comments mixed with what i've earned from internet.
If you don't understand...
Think so as;
is Windows98 have transparency windows?
is Windows XP have 3D desktop? or AURA interface?
I CAN SAY CLEARLY:
This is impossible just yet,
may be next times but not at now.
Note: Universal and BA uses smiliar hw than others.
THANKS.
When will crossbow actually be realeased in final version (leaked or non leaked, but a stable version)?(I know we can't tell whether it will be leaked or not!)
Related
Which is the best WM5 Upgrade
Tuma 1.3
Tuma 1.4(Beta)
Ivan V4R3
I dont think it is Tuma 1.3 coz it loses out on BT and Wifi Perfomance
It cannot be Tuma 1.4 coz it has a bug whil opening Photos and Videos also other problems reported(like icons listed several times, Registry issues)
It cannot be Ivan V4R3 coz it lacks the basic feature of Device Lock(Although I havent checked the OS thruly this was the first fault i came to know abt) "Lt. Gen. Ivan how can u forget such a basic feature"
:idea: Cant someone combine all 3 and make something that can beat wat the OEM's are making :idea:
I feel ashamed to use any of these roms when all my friends use their OEM's that are much better than these
Come-on Guys lets show the OEM's that we are the best :Cheers:
Why would you need to device lock when there's already the default Lock All Except Power Button?
delltech
I dont think you understand how much work goes into creating a ROM with no support from M$. Nobody gets payed for what they do, so they must support themselfs in other ways (i.e going to work). If your that worried about a basic feature like device lock, create it/sort it and post a fix up here. This is after all what XDA-devlopers is all about. Not just leeching other peoples work and *****ing about it missing features...........
delltech said:
It cannot be Ivan V4R3 coz it lacks the basic feature of Device Lock(Although I havent checked the OS thruly this was the first fault i came to know abt) "Lt. Gen. Ivan how can u forget such a basic feature"
Click to expand...
Click to collapse
If you had actually read anything about wuther of the roms you would see that the TuMa versions are based on a ported rom from the Wizard device, hence the wizard's device lock + today screen plugin, however Ivans roms are based on a patched up leaked beta of a origional BA rom, which doesnt include the device lock function and AFAIK doesnt support it. Both ivan and I have tried including the device lock in his rom but it either fails to function or doesnt show, so no luck yet.
In regards to which rom to use may i suggest using Ivans with a 3rd party lock application (i personally use Mort's Mortsaver PE as it is a very powerful and free one, after you have spent 2 minutes configuring it)
@delltech
first read, try than talk
mambojambo said:
Why would you need to device lock when there's already the default Lock All Except Power Button?
Click to expand...
Click to collapse
Try playing a file in media player and putting the phone in ur pocket and u will realize why u need a device lock, and yeah by the way u cant use the power button when u r playing a file in media player or else u need to do a Soft Reset
WWWeed said:
delltech
I dont think you understand how much work goes into creating a ROM with no support from M$. Nobody gets payed for what they do, so they must support themselfs in other ways (i.e going to work). If your that worried about a basic feature like device lock, create it/sort it and post a fix up here. This is after all what XDA-devlopers is all about. Not just leeching other peoples work and *****ing about it missing features...........
Click to expand...
Click to collapse
Excuse me Sir, Just to bring it 2 ur notice, I am a manager with microsoft and i know how to work this around, perhaps i tried patching the OS with a device Lock but the OS fails to Recognize the Exe file, I m not trying to blame someone for missing out on something and i do understand that no one gets paid for it, infact i really appreciate all the efforts all the guys are putting in to help the community, My only concern was that if all the guys work together to make a rom that really has all the features that would be just great (instead it seems they are busy making their own roms by patching different versions of the OG Roms, and last....... I m not a leecher ... i m making my own rom that will consist of a lot more features than the one's listed and that too without any bug... does that sound good or change ur opinion abt me :?:
Midget_1990 said:
delltech said:
It cannot be Ivan V4R3 coz it lacks the basic feature of Device Lock(Although I havent checked the OS thruly this was the first fault i came to know abt) "Lt. Gen. Ivan how can u forget such a basic feature"
Click to expand...
Click to collapse
If you had actually read anything about wuther of the roms you would see that the TuMa versions are based on a ported rom from the Wizard device, hence the wizard's device lock + today screen plugin, however Ivans roms are based on a patched up leaked beta of a origional BA rom, which doesnt include the device lock function and AFAIK doesnt support it. Both ivan and I have tried including the device lock in his rom but it either fails to function or doesnt show, so no luck yet.
In regards to which rom to use may i suggest using Ivans with a 3rd party lock application (i personally use Mort's Mortsaver PE as it is a very powerful and free one, after you have spent 2 minutes configuring it)
Click to expand...
Click to collapse
Sorry abt that dude, if only i had read abt it earlier
But anyways i really appreciate that u r putting in efforts to make things possible
I will surely try the other software u mentioned hope it works gr8 for me as well
sorry delltech
I am not to start a flame war here or anything of the sort, but sure... delltech you work as a manager for microsoft. I believe you, and you have changed my opinion about you...
stop *****ing
Mobile User Interface for the WM6 Wizard ROM. It's something me and some friends are working on. I don't think it will ever be finished though because we're not clever enough, (LOL, sorry guys)
The idea came up after some ROM Cooking trial, the kitchen release and also Molski.
It's creating a Program like in Windows where one can choose what to include in his or her ROM build and burn it.
Just start with:
*IPL
*Radio
*OS (why not a clean one, none phone related)
*programs and stuff to include
All cabs are available, it's just combining it in a nice UI. This also will decrease the threads on custom builds..
Nice idea....
Vilem said:
Mobile User Interface for the WM6 Wizard ROM. It's something me and some friends are working on. I don't think it will ever be finished though because we're not clever enough, (LOL, sorry guys)
The idea came up after some ROM Cooking trial, the kitchen release and also Molski.
It's creating a Program like in Windows where one can choose what to include in his or her ROM build and burn it.
Just start with:
*IPL
*Radio
*OS (why not a clean one, none phone related)
*programs and stuff to include
All cabs are available, it's just combining it in a nice UI. This also will decrease the threads on custom builds..
Click to expand...
Click to collapse
Wonderfull initiative, there are a lot of tools, but a tool to controll them all would be nice
You should also check:
http://forum.xda-developers.com/showthread.php?t=297257
Dutty has programmed a new release of his kitchen..
Looks like he already has done lot of things you are aiming for.
Now it's only compatible to hermes (because of the use of aChef), but I believe it can be transformed to use for a wizard, maybe you guys can work together?
Also this one could come handy too:
bepe's XIPPORT
To replace XIP modules
Best regards,
EqX
Hi gurus,
I'm using a software (designed for my company) working only with netcf1.0. So i cannot use it on Wm6.1.
I have made tests and this software works well only on WM6.0 and less.
So to avoid compilation cost and time, i wish to cook a custom rom like this.
Download kaiser WM6.0 rom : important --> i dont think a WM6.0 jade rom exist
Download Jade WM6.1 rom
replace kaiser drivers with jade drivers
rebuild rom and pray
do you think this can work ?
i know, its a risky business to play with fire
waiting for your opinion about the feasibility of this process
thank you in advance for all your reliable help and feedback
from a developer's point of view:
why not going to get an update of the desired app?
it's quite difficult these days to get 6.0 devices.
NETCF V2 supports NETCF V1 applications with high degree of compatibility.
if it's a clean programmed app, there should be not more to do, than taking the vs2003 project, convert it to a vs2005 project, and run the 2.0 compiler.
I'd rather ask the app's developer for update-costs, than hunting for a ROM with limited functionality (but even more bugs).
ME TOO
I have the same problem with a piece of software for our field engineers, we are a sub contractor and have no control over the software developer. What i have found however is many 6.5 cooked roms work ok
Guys i thought i would start a thread to discuss the possibilities of creating an android rom or the possibilty replacing winmo as the primary os.
i know the current build for x1 is buggy, however the x1 is an outdate device now, i own one only as a testing device for my winmo programming. therefore i cant see why we cant have fun with it...
anyone with thoughts, or references welcome. i have a bit of free time coming up so im looking to jump on the x1 - android bandwagon!
I think more important for now is create krenel that contains all hardware configuration (working WiFi, BT, Camera, GPS, turn off LCD, fast working etc. ) if it will be fulfilled it is possible to think about create android rom
radzix27 said:
I think more important for now is create krenel that contains all hardware configuration (working WiFi, BT, Camera, GPS, turn off LCD, fast working etc. ) if it will be fulfilled it is possible to think about create android rom
Click to expand...
Click to collapse
although it is not a priority it is still interesting to look at...
for instance it would reduce the non helpful post on how to use/install
Reversedhex said:
although it is not a priority it is still interesting to look at...
for instance it would reduce the non helpful post on how to use/install
Click to expand...
Click to collapse
You're absolutely right. But ... who would flash his phone with a rom, which can't use the speaker for ringtones and which drains the battery.
I agree with vdelf - as soon as we see a working kernel worth for daily use, we might look into the issue of flashing android rom.
Bluetooth, GPS and Camera still not working for many htc devices. However, sound, ringtone is of highest requests for X1
I am with _Sensible on this one (not the "outdated"-part ). Android is not ready for primary OS on the X1, but it is not that far away. Why not start to create a rom? IMHO that will take some time, too. And that way we do not have to wait for a rom when the kernel is ready
If speaker and screen issues will solve then may try to cook android rom
drlucky said:
You're absolutely right. But ... who would flash his phone with a rom, which can't use the speaker for ringtones and which drains the battery.
Click to expand...
Click to collapse
I would....
but then again I do have two xperia's so it wont matter if one isn't working properly.
btw this would be a nice time to stop talking about why and start talking about how.
maybe the knowledge can be found in the tp2 forum again....?
thanks for all your thoughts guys. i realise a flashable rom isnt a priority but i was thinking along the lines of vdelf. if we start this development now it may tie in nicely with a functional kernel.
in terms of how to do it...
1. binary image written via a 'flasher' app etc etc.
2. I wonder if we can install an os via android-through-haret? like the install option from an ubuntu live cd?
like i said, i have some free time soon so will do some R+D.
I hope so for that Android ROM .
android as a rom. hmm lookin forward to it. cant wait
dexteral said:
android as a rom. hmm lookin forward to it. cant wait
Click to expand...
Click to collapse
same here - im sick of winmo glitches and problems,been reading alot about this project and i hope that all the x1 hardware works on it.
I'm looking forward for rom too. But not because of WM glitches, but because android will extend life of xperia. WM6.5 is dying os. Most software from actual companies is either for Android or iPhone (and probably for WP7S soon), apps for WM6.5.x and older are becoming rare.
I would really like to see actual rom, but i think you should put priorities on power managemnet, brigthness and sound. I can live with haret until then
Anyone have experience using the fastboot bootloader / recovery options for android roms?
matejdro said:
I'm looking forward for rom too. But not because of WM glitches, but because android will extend life of xperia. WM6.5 is dying os. Most software from actual companies is either for Android or iPhone (and probably for WP7S soon), apps for WM6.5.x and older are becoming rare.
I would really like to see actual rom, but i think you should put priorities on power managemnet, brigthness and sound. I can live with haret until then
Click to expand...
Click to collapse
Totally agree !
_Sensible said:
Anyone have experience using the fastboot bootloader / recovery options for android roms?
Click to expand...
Click to collapse
Im not sure but the key combo to trigger it is set in kernel and need a recovery image, if thats what you are looking for...
1. binary image written via a 'flasher' app etc etc.
2. I wonder if we can install an os via android-through-haret? like the install option from an ubuntu live cd?
Click to expand...
Click to collapse
Cant the android os be cooked into a nbh, so an existing flasher or microsd method can be used?
oh yaaa man me to wud love an android rom it wud be awesome plz work on this hope to see a android rom soon man
@Reversedhex,
Yes, a ROM can be cooked and I don't see why the RUU utility couldnt be used either
I will have a play - I believe this has already been done on the HTC Vogue...
Tinboot is also a possibilty...
Ok,
Ive been looking into this, I reckon the best way to do is to jump on the back of the 'tinboot' bootlader developed on this forum. So far Its only been ported to the Kaiser....however with a bit of R&D it shouldnt be too hard to port to kovsky.
Please check it out
git://androidhtc.git.sourceforge.net/gitroot/androidhtc/tinboot
Oh, I dont suppose anyone has a kovsky nand dump lying around? Or info on the tables?
Well, you know, it 'kinda' works. I've even made a video. But we need to fix panel initialisation (or it's more likely that i've simply messed something up). You can watch. After hanging on the SE logo, it makes two vibrations and the screen covers with strange pattern which means the kernel does start. Maybe i'll work on it later.
http://rapidshare.com/files/371867580/x1.avi.html
Is there such a thing as an original ROM from Microsoft? Would this work on the T2 or would I still need to load drivers and other items to get it to work on AT&T 3G?
6.5.5 or any other similar branch hasn't RTMed from what I know yet. These branches will end up as WM6.6 (WP6.6).
And they are mostly for capacitive touchscren phones, not for our resistive.
Thanks for the reply. Let me re-ask. Where can I find a virgin 6.5.whatever ROM that is close to the base OS from Microsoft before the chefs add their touches? Honestly, I am minimilist and I want to run Titanium with the built in IE and not much else.
Looking at all the ROMs, even the default from HTC, I cannot tell you what is native Windows Mobile and what has been cooked in.
Thanks for your help.
You're gonna have to cook
Get latest build from MS here at Chef Central in huge "Last SYS" thread and dump some stock ROM (2.07) to get drivers. Don't forget to add the base OEM packages as well, like Camera, SensorSDK etc, otherwise most of the stuff like GSensor, ... won't work
http://forum.xda-developers.com/showthread.php?t=681667
This is as close as you'll find.
osu9400 said:
Thanks for the reply. Let me re-ask. Where can I find a virgin 6.5.whatever ROM that is close to the base OS from Microsoft before the chefs add their touches? Honestly, I am minimilist and I want to run Titanium with the built in IE and not much else.
Looking at all the ROMs, even the default from HTC, I cannot tell you what is native Windows Mobile and what has been cooked in.
Thanks for your help.
Click to expand...
Click to collapse
There are a number of stock ROMs in this forum, do a search. However all of these were designed for a specific carrier, and will have the carrier bloatware. MS does not sell their OS directly to the public, so you have to use what the carrier or HTC puts on there.
Actually, it is very simple to remove sense from a stock ROM and rebuild it. Check out the kitchen software programs. The difficult thing about building your own ROM is trying to ADD stuff - that gets complicated.