Related
I need someone to test this ROM, because I dont have a BA.
OS 5.1.195 (Build 14847.2.0.0)
STOP !!! ROM IS NOT WORKING
"ftp://xda:[email protected]/Uploads/BLueAngel/WM5_BA_-_AKU2 TEST.rar"
It is possible that you have to reflash the old rom!
Is this based on the Himalaya rom?
How likely is it to turn my BA into a paperweight? LOL
I am donloading it now mate.. Will post any results in about 2 hours
Gruß aus Malta!
Juggs
I used the the newest QTEK Wizard Rom.
There would not be any difference between Him or Wiz OS. Same build same files.
bepe said:
I used the the newest QTEK Wizard Rom.
There would not be any difference between Him or Wiz OS. Same build same files.
Click to expand...
Click to collapse
?? no omap or xscale code optimalisation ?? files can not be the same :|
I ported the German Wizard rom successfully to my Himalaya and I did the same with the WWE version at this rom.
But there could be differences. In this case, the rom would not work.
First Impressions..
OK.. bearing in mind that i only installed the Ivan Rom about 3 hours ago.. My MDAIII is getting a beating tonight.. However...
Ok.. Standard stuff.. Bootloader mode.. Set operater..
The update was relatively quick.. only took about 8 minutes,
Formatted the hive and storage OK..
And it hang on the Windows Mobile Screen!
and it keeps on hanging on the windows Mobile Screen.. :?
No New device Setup.. No shimmer of life.. No backlight.. Just the on/Off button Works
Sorry mate.. Back to the drawing Board!
I have not changed the drivers, only the OS.
I compared a Univesal and Wizard rom and the OS is exactly the same.
That may well be bepe.. But it doesnt install past teh windows Mobie screen...
Something is wrong mate.. normally it should give you that screen you get when the device need to be setup the fist time.. and it doesnt.. It just hangs..
Sorry..
Ok thanks and I'm sorry.
Ahh well! Thanks for your attempt Bepe. It seems he got to the same stage as Mamaich & Tuatara.
bepe said:
I need someone to test this ROM, because I dont have a BA.
OS 5.1.195 (Build 14847.2.0.0)
"ftp://xda:[email protected]/Uploads/BLueAngel/WM5_BA_-_AKU2 TEST.rar"
It is possible that you have to reflash the old rom!
Click to expand...
Click to collapse
***NOTE: To all wanting to test this, the ROM will not finish the BOOT sequence. This is the same or similar problem both mamaich and I have had with undertaking the Himalaya AKU2 Port to date. ***
The device will initialize, gets to the 'boot splash' screen, runs that ...
The "coldinit.exe" is started, since we hear the 'ding' happen ...
At this point the device locks - an animated "dialog" appears to want to be displayed.
The boot process proceeds no further. Presumably crashed.
Additionally, the LEDs are dead/disabled so I can not tell if the phone (RIL, BT, etc.) is still available/operating. Power button or screen taps do NOT relight the backlight, or enable the screen. Presumably locked up.
Ok ... excellent work so far, however the same problem(s) seems to be arising which both mamaich and I have run into when using the Himalaya AKU2 port.
My guess is that this is probably due to the same missing DLL interface calls being available in coredll.dll. There are now 5 additional entry points in the XIP portion of this DLL, and this could be causing the 'hang'.
It looks VERY promising though ... I'm definitaly going to be taking a VERY close look at this ROM as well. The boot sequence is quite dramatically different, and may lead to some possibilities in merging ROMs to avoid the requirements of changing XIP section modules.
P.S> TuMa v1.4 will be out shortly ... it's now combining elements from the Wizard, Himalaya 1.7x & 2.0, Jasjar, Atom, Acer, and the original v3.1 BA from mamaich now. Trying to merge the 'best' of the available elements for a well performing and stable device.
Not a problem.. Just let me know when you want another one tested!
Gruß Aus Malta..
OT: has anyone tried porting Universal rom? is it possible?
@Saintraziel:
Would be the same result.
And a lot more work to do because of the VGA resources.
aku2
Would this give AKU2 functionality for blueangel? (PH20B)
If so I would be happy to test any builds, I am dying to get my hands on a working WM5 with push email on BA.
Cheers...
Can anyone tell me how to use this rom
ftp://xda:[email protected]/Wizard/Roms/Tmobile/RUU_Prodigy_2170702_217_20710_TMO_US.exe
and put it on a xdaIIs?
Do I need to use a noid.exe and if so wihci one should I use?
You can't do it like that - it would be lovely if you could but a rom for the Wizard would need to be ported for it to work on the BlueAngel. To try it would give you a very nice doorstopper.
Ahh thanks for the warning!! So can this be ported from the wizard to the xdaIIs?
I would love to use the WM5 but as far as I have learned WM5 does not support Blackberry Enterprise aka Instant mail, and I have not found any CAB files that will work on my XDAIIs with WM5 installed. I am getting pretty good at upgrading and downgrading tho :-(
All of the TuMa editions are using a Wizard Port (allbeit an old version). They are really quite stable now and I think we're getting close to a rom to stick with
As far as Blackberry support, I haven't seen a BA WM5 rom with it however I imagine it could be ported but then again, I am no porter!
Kind regards
Lee
I found a German BB connect cab that will install on the BA WM5 that ivan made but right at the very end of the install it says cannot load instal module. You click ok and the program tells you it installed. When you go to find the BB settings eve in the BA it is under \windows and when you try to execute it the unit hangs up.
I assume that this cab is looking for the T-Mobile info to complete the install so we would have to have one of the very bright individuals in this forum find out what it is looking for exactly and fix that part of it. The BA WM5 would work with BB connect
Hi
would like to know how is the pda2k WM5 ROM and is it the orignal ROM by IMATE? and if it can be installed on a T-Mobile MDA III?
Thank you
pyk
where?
edit: found it, never seen or heard of it before, i dont think its official.
Ive downloaded it and am flashing it now to see what it is...
to me it just seems to be a clean WM5 rom (build 14343.0.0.0) it has no ramdisk, and apart from a nice w-lan manager absolutly no aditional software/control panels applet above standard wm5. as far as can tell everything is working fine, althought the two noticable differences are that it didnt invoke my extrom and there is no systray.
maybe someone know what this is? (could it be and old vesion)
Is this ROM ever going to be leaked from microsoft (i presume this was how wm5 be started)?
Porting seems to be very unstable from what I have heard
A WM5 rom was never released by microsoft, although it was known to exist. It's highly unlikely MS will create a WM6 dev rom for the BA at all.
Remember, the BA originally shipped with WM2003SE. WM5 was a struggle to get working, WM6 should (by an unwritten law) be unable to run on the BA. But there are some gods out there so you never know.
Many drivers in WM6 are almost exactly the same as WM5 AFAIK. Drivers are normally the big problem, so if you have good drivers for the BA, then it's a possibility.... but don't hold your breath.
V
So was wm5 BA never really created by microsoft?
In that case, who did create it? Did someone do it from scratch?
If they did, why can't they do it in crossbow (wm6 Blue Angel)?
I think it's a bastard son of a Wizard leak.
V
hardingt0110 :
You still didn't read the wiki and the older threads as I told you few weeks ago
But Microsoft is the one who makes OS (WM5, WM2003SE,WM2003,...).
O2, Vodafone, T-Mobile, Cingular... are the ones who adapt WMx to devices.
WM5 for BA has been ported from different (but very similar) device that already comes with WM5 by xda-developers.
You cant buy it (WM6), even if you want So be patient
Biohead said:
A WM5 rom was never released by microsoft, although it was known to exist. It's highly unlikely MS will create a WM6 dev rom for the BA at all.
Remember, the BA originally shipped with WM2003SE. WM5 was a struggle to get working, WM6 should (by an unwritten law) be unable to run on the BA. But there are some gods out there so you never know.
Click to expand...
Click to collapse
The Roms never released for devices by microsoft, the producers use and adapt roms for him devices.
If HTC use Wm6 rom for him devices and Reproduce or advance BA to the WM6 or similar device then we can see WM6.
Other side If anybody can write or adapt device drivers that can be... Core software hasn't any driver i think. May be someone can syncronise Wm6 shell and BA (or resemble device) Wm5 drivers
And may be work
what a dream huh...
BA WM5 base rom is genuine created for BA, and just the OS (with AKU's and stuff) part was aded to this rom ported from another device.This base rom was leaked by one of the operators
I suppose that the needed kernel would be created by someone somehow someday, because basically Microsoft creates the new ROM, gives it to the manufacturers, then the manus will try to adapt the ROM to their devices.
As I saw somewhere on the net saying the ROM can be adapted and flashed to any device, as long as the manus manage to write the necessary drivers.v.v...those kinds of stuff. It sounds logical to me. What do you guys think 'bout this?
nht_max, that's what I thought as well but I never said anything, bowing to those who know more about these things. IMHO it is not needed to recompile the kernel unless it's for a new architecture. Proved the correct drivers can be located and they are compatible with WM6, then it should just work.
Recompiling may be necessary, I think because the new ROM is much different from the old WM5. Though I believe it'll be available some nice day.
Crossbow
nht_max said:
Recompiling may be necessary, I think because the new ROM is much different from the old WM5. Though I believe it'll be available some nice day.
Click to expand...
Click to collapse
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
But i think we should wait a lil more before try experiments like this, we have no any documentation about WM6, we don't know how the things work inside, it is similar to WM5 but defenately not the same. We must learn how it works and then port it and modify it to our own taste.
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
xplode said:
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
But i think we should wait a lil more before try experiments like this, we have no any documentation about WM6, we don't know how the things work inside, it is similar to WM5 but defenately not the same. We must learn how it works and then port it and modify it to our own taste.
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
Click to expand...
Click to collapse
Hi,
have u changed coredll.dll in xip boot?
the devices not boot in same mode if u try aku 3.5 and have coredll.dll of aku 3.2
@Tuatara,
please help me for relocating more space in xip boot
of course not, AKU 3.5 runs fine with the old core without problems, but for crossbow the coredll should be changed in order to work, the thing is that it is bigger than the old core.
I have no knowledge of editing XIP, thats why i am stuck at this point, but i have read here on the forums that the coredll.dll can be changed with one with the exact same size, and the crossbow one is bigger.
xplode said:
of course not, AKU 3.5 runs fine with the old core without problems, but for crossbow the coredll should be changed in order to work, the thing is that it is bigger than the old core.
I have no knowledge of editing XIP, thats why i am stuck at this point, but i have read here on the forums that the coredll.dll can be changed with one with the exact same size, and the crossbow one is bigger.
Click to expand...
Click to collapse
I have tried to run aku 3.5 with coredll.dll for aku 3.2 (not 3.3) and not working....(but perhaps I mistake method)
I know that there is a way in order to increase and relocate the files in xip with dumpromx but I do not know if it works for the modules (old post Tuatara on xda)
and however I have read that it must edit vdata and pdata in the modules for the just address (oki and sp3dev on buzzdev)
but sp3dev and oki not working on blu devices only tuatara have necessary experience on blu devices and I believe can help
xplode said:
Recompiling may be necessary, I think because the new ROM is much different from the old WM5.
Click to expand...
Click to collapse
You may be right about this, i have ported the OS part to BA rom without any changes in XIP section of rom (old core 5.1.195) and the device with this rom does not boot at all, so if the original core 5.2.x is ported to a BA rom it will work correctly, almost all OS files are related to the WM core, and if a function that they seek is not where it should be unpredicted crashes may occure.
Click to expand...
Click to collapse
I don't understand this. Recompiling is only required for a different architecture in my experience, but I've not done much with this platform myself. Is it linking in specific BA drivers or something?
Also the leaked roms are from early beta stage, so they are not so stable and usable as the final version.We should wait a bit for the first official rom and build something stable enough from it for common usage. And i am not talking about BA here i am talking about rom cooking for all devices.
Click to expand...
Click to collapse
I agree 100%, though I'm sure some of you will still tinker around. Interesting stuff.
we can use BA wm5 drivers, they should work fine, WM5 is 5.1.x and WM6 is 5.2.x not a major 6.0.x release do the changes are not so drastic and the drivers should work
look at windows windows 2000 uses the same drivers as xp, windows 2000 is NT5 xp is NT5.1
OK guys, thanks for your help.
So basically the main part of the wm5 rom for the BA was made by an unnamed operator, who decided not to release it, but it was leaked to xda-developers.
Then the developers made the aku's and customisations from scratch / ported from other devices, and combined them to make a full wm5 rom.
Some people (xplode and others) seem to think that the wm5 main part rom can be used to host all the bells and whistles from wm6.
So basically, all we need to do is wait untill an official very stable wm6 rom is made for a Blue Angel like device, port it, and we're all set!
Am I right?
Oh, and one last question: is the name for the main part of the rom a "kernel"? thanks,
Always be faithful in the xda-developers,
hardingt0110-1
Looking at other threads, some think it may be necesary to use sd cards as rom.
I have two sd cards (1gb and 2gb) which I swap between on my BA to allow me to have tomtom maps and movies on my device.
Untill now, I have ignored extrom.
Is it possible for me to install the extrom on both cards, so that I can swap them over when I want?
hardingt0110-1
Still Lurking ...
Hey There ... I thought I might just come out of the woodwork for a little bit ...
sostekit said:
have u changed coredll.dll in xip boot?
@Tuatara,
please help me for relocating more space in xip boot
Click to expand...
Click to collapse
sostekit said:
I know that there is a way in order to increase and relocate the files in xip with dumpromx but I do not know if it works for the modules (old post Tuatara on xda)
and however I have read that it must edit vdata and pdata in the modules for the just address (oki and sp3dev on buzzdev)
but sp3dev and oki not working on blu devices only tuatara have necessary experience on blu devices and I believe can help
Click to expand...
Click to collapse
I've been quite able to make some space in the XIP section by moving files around (to make space for larger boot registries, etc.), but I haven't had any luck with moving around modules. I think it was mamaich (and/or bepe) who managed to get the new core.dll (which has the new LASS_xxx entry points) into the BA XIP section ... but I haven't had the time to see how they managed it.
I do have the source for RomMaster & dumprom, and will be going through the details at some point - when I have the time (which is always lacking). In the same way as figuring out the Acer ROM for mamaich's tools - I'll need to see if we can dump out and 'move' modules & files around to make the space required. This may just have to be a 'one off' manual hex editing job though (fixing the tables).
While in theory the WM5 drivers should work just fine, a number of our "WM5" drivers are still 2003SE versions. How long we can keep using the old drivers is anyone's guess.
In short - as long as the XIP section contains all of the entry points and support calls required by the 'new' OS, and can start the "new" OS, then the OS portion of the ROM can be replaced. This is what we are doing with the BA now. The XIP section is still (effectively) the original leaked WM5 build, with very little, and as little replaced as possible, but just enough in order to boot the "new" OS, which has been put in the remainder of the ROM.
For reference, you can find a listing of the new functions in core.dll from here:
http://blogs.msdn.com/windowsmobiledocs/
As far as I know (from xda-dev & runour mill) the core.dll entry points have not changed between versions wm5/6 ... but that's not to say that some things don't operate differently.
Only time will tell if we can port/hack wm6 on to a Blue Angel.
Hello all
Wm6.1 alpha 1 Ver.5.2.1711 (Build 19202.1.0.0)
Many bugs (high instability)
WM6.1 alpha 2 Ver.5.2.1711 (Build 19202.1.0.0)
Many Bugfixes (Usable)
Accesibility-working
Comm manager-working
T9-working
Power-NOT WORKING (you have to regedit)
WM6.1 alpha 3 Ver.5.2.1711 (Build 19202.1.0.0)
Many Bugfixes (Very Usable)
Accesibility-working
Comm manager-working (without bluetooth) - fix in progress (A4)
Bluetooth working - separate menu
ad2p fixed - proper version
T9-working
Power-working
Suspend -working
XIP - Rebuilded
Caller ID -working
HSPDA-working
GPRS-working
GPS-working (external device)
MMS - working
2 beam in control pannel !!!! - fix in progress (A4)
Please test and tell me if is anything wrong and if you find fixes
WM6.1 Beta 1 Ver.5.2.1711 (Build 19202.1.0.0)
Many Bugfixes
Accesibility-working
Comm manager-working (COLOR with BLUETOOTH)
Bluetooth working - separate menu
ad2p fixed - proper version
About - FIXED
T9 - working
Power - FIXED
Suspend - working
XIP - Rebuilded
Caller ID - working
HSPDA - working
GPRS - working
GPS - working (external device)
MMS - working
2 beam - FIXED
Windows Live - FIXED
you must update Windows Live to latest version
http://rapidshare.com/files/106073863/Windows_Live_10.6.34.2500.cab.html
ROM Links
http://rapidshare.com/files/105874292/MTeoR_-_WM6.1_-_A3.rar.html
http://rapidshare.com/files/106079473/MTeoR_-_WM6.1_-_B1_-_ok.rar.html
Please test and tell me if is anything wrong and if you find fixes
Also released the A4 kitchen
Many thanks to
Bepe - Tools
Mamaich - Tools
Dr Martin Gonzo - support
Garmin - support
futureshock - Test and bugreport
Hi, from where comes the Wm6.1 Roms?!
when you give it me i will try to made other languages too of it
jerpelea said:
Hello all
This is the alpha version of wm6.1
Please test and tell me if is anything wrong and if you find fixes
http://rapidshare.de/files/39013516/MTeoR_-_Splash_Screen.rar.html
http://rapidshare.com/files/98157272/WM6.1_Segoe.cab
http://rapidshare.com/files/104652554/MTeoR_-_WM6.1_-_A1_-_ok.rar.html
tomorow i will release the rom kitchen
and vanilla wm6 & wm6.1 roms
Many thanks to
Bepe
Mamaich
Dr Martin Gonzo
Garmin
for their tools and suport
Click to expand...
Click to collapse
how cook chines ROM?
good job! thanks very much!
Wow Cooooool man good job thanks
hello,jerpelea !
I find this rom in "seting", "Power Management","Accessibility" is bad."regional settings" locale is russian,and lose "systerminfo"
my english is poor,wish you can understand.
Hello lyf1998
fixed accesibility
working on power settings
i know that locale is in rus (is normal)
Where did you find sistem information ?(it is not included in this rom)
I will not cook chinese rom
please learn english, read forum and learn gow to cook or add locales.
I will release the Kitchen so that you could cook yorself an rom
Thanks
jerpelea said:
I will release the Kitchen so that you could cook yorself an rom......
Click to expand...
Click to collapse
Thanks.
呵呵，谢谢。
released
till monday i will release an A3 version
jerpelea is KING!
Hey jerpelea. Thanks so much for getting this out, I loaded it up as soon as I got home Friday night. Observations so far:-
Pros:-
-Very fast loading, much faster than latest WM6.0 out for Mteor
-Very fast running, including loading apps.
-Visually, complete makeover. Much happier with this Today screen than any plugin I've seen.
-All software attempted to far works fine- Route66, Google Maps, Skype (as well as it does on the mteor anyway!).
Issues:-
-msn messenger not installed, however Today screen expects that it is there. When selecting to sign in from Today screen, it comes up with a connectivity issue immediately, however no connectivity issue exists. I can install WLM seperately, but would be ideal to have the sign in from the Today screen as intended. Also when I've installed the latest WLM, there is a strange issue where I cannot do backspace- the 'back' key does not delete text and move the cursor backwards. Makes MSN virtually unuseable for me.
-Phone intermittently does not resume from standby- is frozen. It is still flashing to say that it's on and connected, however no buttons will revive it- the only way to revive is to remove battery and reboot. When phone restarts new messages and emails come in- leads me to believe phone was frozen.
-Phone intermittently wakes up for no reason- have had the phone sitting next to me for a night, and it lights up brightly at random intervals.
I am blown away with this release- it's made my Dopod 595 my favourite phone to carry again, over my Hermes and Asus Halley. A few issues to be resolved obviously, but it's exciting that we're getting such recent builds of WM6 for our Mteor's.
Keep up the great work, holding my breath for the A3 release!!!
does it work with dopod 595 variants with forward facing camera? and also, can you please point us to SuperCID unlock guide? thanks
Dopod 595 & WM6.1 A2
alexnvidia said:
does it work with dopod 595 variants with forward facing camera? and also, can you please point us to SuperCID unlock guide? thanks
Click to expand...
Click to collapse
It sure does work with the 595, albeit with the issues mentioned in my previous post. I'm honestly not sure about the front-facing camera, hadn't tried it yet. Will try tonight and advise.
In terms of getting around the CID issues, there will be 3 registry edits you will need to make (need to copy regedit to phone and run to make changes), and also a piece of software to application unlock. This will make your phone Application Unlocked.
You then put Des' SSPL on the phone, run it and immediately press the power and camera buttons. It will then start with the special SSPL, which gets you around the CID locking. You can in theory update via the update software (RUU) after this, however I have always upgraded via putting the rom onto the memory card as "BREEIMG.NBH". There is packaging software that will allow you to put your own choice of radio, rom, splash-screen's etc together.
In terms of the SSPL process, this is very well documented on the forum. Just take a look. I would not attempt the SuperCID process suggested- which involves loading the Hermes unlock tool to the phone. The hardware may be the same, however the command to enter the bootloader is not, I have bricked my Dopod 595 TWICE doing this- both times having the board replaced (under warranty luckily!). Up to you to attempt if you like- however I just don't see that it's really worth it until there is a dedicated and foolproof process.
Remember that these rom upgrades don't include the radio upgrade- so if you are upgrading your firmware for the first time, best to flash the most recent HTC WM5 upgrade first (incl. radio 1.38.x). Or an extracted Hermes radio rom. Just ensure it includes HSPDA.
If it's your first upgrade, and you don't like the idea of upgrading many times, I'd perhaps wait until a more final WM6.1 for Mteor is released (perhaps A3 or a RC).
I'm far from an expert, but have played with these, and my Hermes a lot. If I can perhaps answer anything else, please let me know...
MMS
jerpelea can u add MMS program to your A3 release???
stuartmclean said:
It sure does work with the 595, albeit with the issues mentioned in my previous post. I'm honestly not sure about the front-facing camera, hadn't tried it yet. Will try tonight and advise.
In terms of getting around the CID issues, there will be 3 registry edits you will need to make (need to copy regedit to phone and run to make changes), and also a piece of software to application unlock. This will make your phone Application Unlocked.
You then put Des' SSPL on the phone, run it and immediately press the power and camera buttons. It will then start with the special SSPL, which gets you around the CID locking. You can in theory update via the update software (RUU) after this, however I have always upgraded via putting the rom onto the memory card as "BREEIMG.NBH". There is packaging software that will allow you to put your own choice of radio, rom, splash-screen's etc together.
In terms of the SSPL process, this is very well documented on the forum. Just take a look. I would not attempt the SuperCID process suggested- which involves loading the Hermes unlock tool to the phone. The hardware may be the same, however the command to enter the bootloader is not, I have bricked my Dopod 595 TWICE doing this- both times having the board replaced (under warranty luckily!). Up to you to attempt if you like- however I just don't see that it's really worth it until there is a dedicated and foolproof process.
Remember that these rom upgrades don't include the radio upgrade- so if you are upgrading your firmware for the first time, best to flash the most recent HTC WM5 upgrade first (incl. radio 1.38.x). Or an extracted Hermes radio rom. Just ensure it includes HSPDA.
If it's your first upgrade, and you don't like the idea of upgrading many times, I'd perhaps wait until a more final WM6.1 for Mteor is released (perhaps A3 or a RC).
I'm far from an expert, but have played with these, and my Hermes a lot. If I can perhaps answer anything else, please let me know...
Click to expand...
Click to collapse
you sound pretty much like a guru here.. it will be very helpful if you can provide the links to the documentation of the CID, SSPL, ROM, or anything relevant here. i know i can do a search, but my 595 is out of warranty and it wouldnt want to risk killing the phone with the wrong process or procedure.. unlike the startrek thread, the superCID and unlocking process are well pointed(links) and explained in the ROM update packages. i find that Breeze's threads are a bit fragmented here..
so if it's not too much of trouble, maybe you can start a new thread explaining the unlocking, CID, SSPL, and Radio upgrades in detail. im sure the admin will make this useful thread sticky for nobs (like me). cheers.
have you looked into wiki?! there are many infos...
CID Unlocking isnt researched sofar that you can use it without starting the sspl from a running device... so that means theres no HARD SSPL yet...
and i think there would never be..
i have tested to flash devs sspl but it didn't worked...
i'm also on the side that the mteor is a smartphone thats not really widly in use... so theres no big community behind they develope!
DEv has done so much with his sspl...
and with wm6 and wm6.1 yet i think thats much more i have ever imaginaryed!
thank you again! but i still do not run rom Kitchen.
is it possible to put in the neo-plugin today app from the mteor wm6.0 roms?
lyf1998 said:
thank you again! but i still do not run rom Kitchen.
Click to expand...
Click to collapse
cant help
i have
.net 2.0
.net 3.5
visual c redistributable
windows XP sp2
Does not work on vista
BR
Hmm....
was what I got trying to upgrade...
techdev said:
is it possible to put in the neo-plugin today app from the mteor wm6.0 roms?
Click to expand...
Click to collapse
Yes but NO i will not include it
You have the kitchen you can include it if you like
This is a vanilla version
I will try to clean it of bugs
Everybody who wants an localisation or an software will have to add it
BR