Related
Hi people, Im new here,
My name is Mike and I have just bought an O2 xdaIIs and love it. I am wondering about upgrades for it. What would you recommend? All the details are in my sig (i think)
Any help appreciated
Mike 8)
u can try helmi_c aku3.2 which is the latest rls, very fast and stable. it's a very nice ROM. there is some issue with BlueTooth, but the rest is all good.
imatrix
Hi Mike,
visit http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel and browse through forum. U know we cant give u any advice if we dont know what are u looking for (any problems,discontent?)
You can upgrade to the latest version of wm2003se (see the wiki) and than consider if u wanna upgrade to wm2005.
i'd say enjoy your unit using wm2003se for a while.
and when the time comes that you are looking for some more, then go for wm5... and the latest radio version.... it would seem like you have a new phone altogether.
I would take a call depending on the way you use your phone. How much of bluetooth you use, how much of wifi, do you use a stereo headset, do you use a GPS attachment, what kind of applications you run etc. Please note that if you go through the the complete threads of a particular post helmi 1.3 or 1.2 or 1.1 you will come to know the advantages and drawbacks of upgrading and can then take a wise call.
Hope this Helps
imatrix said:
u can try helmi_c aku3.2 which is the latest rls, very fast and stable. it's a very nice ROM. there is some issue with BlueTooth, but the rest is all good.
imatrix
Click to expand...
Click to collapse
Dear Sir,
I'm running Ivan V4R3, may i know which is faster if compare with helmi_c aku3.2. And as my know helmi is pre-install some program, can u specfily. Thanks!
Ivans rom with ramdisk is very stable and fast wm5 version, and i lie it a lot, but AKU updates fixes many bugs in the OS and Security of the mobile device, so i prefer latest AKU 2.3, 3.0 3.2 roms.
The best way to get your rom to fit your needs is to build a custom one with Bepe's ktchen
@Mike
First i want to welcome you to the forums, you will learn a lot here as i did!
First step that you have take is to read WIKI, a lot of stuff is explained there. For you there are 2 possible types of roms, WM2003SE or WM5. By mine personal opinion the best roms by now are Ivans v4 r3 with ramdisk, and Helmi's 1.3 AKU 3.2 roms. You can try and decide for yourself.
Sorry about creating a topic, but I can't find anywhere to ask.
Here I have some questions which I don't understand. Somebody please explains for me:
- What is AKU? It has any difference from ROM?
- BlueAngel doesn't has WM05 ROM, then where does it come from? Is it ported from others series (like Universe)?
Love you all ^_^
- AKU is like a patch for the WM5, take it like the SP2 for WinXp
- BA's WM5 are cooked up from the gurus here. There are attempts to get WM5 onto BA, officially, and "drivers" are written for it. Although the official finally dropped the idea of WM5 on BA, these "drivers" has been leaked to the wild, and the gurus picked them up to cooked up the WM5 for BA.
Hanmin, is my own extrapersonal opinion the these 'drivers' has bin leaked to the wild, like u say, just to create a test environment to valuate if is there the possiblity to solt an official WM2005 for this PDA...
Just an opinion
Thanks these guys very much.
But I still have some unclear things here:
- So where does the "drivers" sit in the ROM? Is that EXROM?
- According to the post of hanmin, then AKU3.2 absolutely is the ROM for BA ?
(Maybe this forum should have a topic like "History of WM5's BA" -_-")
I feel very confusing now.
- I have very vague memory on this, but as far as I can remember, these 'drivers' are information on how to function the hardware of BA. As such, these are definately sits in the main ROM, not the Ext ROM. Ext ROM stuff are generally not system vital stuff.
- AKU is a general term for WM5 upgrade, it does not tie with any device. However, the upgrade files does ties to specific device, example, AKU_version 1234_ROM_setup_for_charmer.exe.
Why do you want to learn history here? There is a good reading if you want to. Go to Magician forum, there is a thread on why there aren't (can't) WM5 for Magician, probably you can find the 'driver' reason for that.
Hie hie. You don't have to explain what drivers are
But there's nobody answer this question for me >_< :
- Who is the release-er of WM05 for BA? HTC or Microsoft
- Is WM05 for BA offical or unoffical?
Many thks
(Helmi, why don't you explain for this poor man? )
As I said in my first post up there, "BA's WM5 are cooked up from the gurus here.", not HTC, not Ms
unofficial
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.
Hey all
My charmer has arrived, and im picking it up tomorrow.
I recently had the joy of playing with two different XDA II handsets, one with an AKU 2.0 rom update and the other with an AKU 3.5 update on it. the AKU 3.5 both looked and performed a LOT better.
What i want to do is the following:
Cook and release a streamlined minimalist AKU 3.x (any AKU 3 version rom, be it 3.1,3.3,3.5)
however, my knowledge in this department is a little lacking.
is there ANYBODY in here who runs a charmer and has a little knowledge in cooking roms?
I'm thinking it would be as simple as the following:
1) extract AKU2.0 ROM from Charmer
2) Remove 'OS' part from the rom
3) extract AKU3.5 ROM from prophet (as this is the closest device)
4) insert the OS from the prophet into the charmer rom
5) Patch with drivers for charmer
6) recompile and away you go!
is there ANYBODY here who is willing to help?!
thank you
helmi_c is seems to be working on it. I have downloaded his AKU3 rom with nottice that it is not yet designed for regular user - and it really isn't Spent two days ressurecting my poor charmer...
nocturne.op.15 said:
helmi_c is seems to be working on it. I have downloaded his AKU3 rom with nottice that it is not yet designed for regular user - and it really isn't Spent two days ressurecting my poor charmer...
Click to expand...
Click to collapse
ive been looking at it too. only 2 things ive noticed is a problem with the sound and internet sharing apart from that its seems fine.
well, i'll be happy if you can provide me a copy for testing - i will send you feedback, of course
Hey
well, once my charmer comes back from repair, needless to say, i will be beta testing a good, clean, stable aku 3.3 wm5 release!
dave, could you provide some sort of quick guide on how to modify the extended rom please?!
thanx
Oh boy, if this gets uploaded would i be able to upgrade to it?
I have tried a few times with dave's other rom but had no luck as i cant unlock my phone due to, i believe, upgraing using the tmobile original file. before cid unlocking it. As i understand it i now have v2 bootloeaders which cant be cid unlocked.
Hi
Hows development of this going now? not heard anything, have PM'd Helmi
would really like to release an AKU3.x rom for the charmer, would be perfect!
an have you any response from helmi? waiting for aku 3.x so long
Well, who needs Aku3 anyway if there's a rom with wm6? ;-)
I wrote a mail to T-Mobile (Germany) and asked them about any planned updates for the Charmer. As soon as I get a response, I'm gonna post it of course.
youser, i wouldnt hold out any hope for a wm6 rom for anything currently out apart from the VERY high end like the universal/hermes
i havent had a response from helmi yet, going to wait out a little while longer.
dave106 appears to have had a 'semi-working' rom on his device albeit minor things not working like camera, but im *hoping* that shouldn't be too difficult to fix.
if dave or helmi could please please please please please (pretty) please post an update on the status of an AKU 3.x update it would be extremely helpful!!
well i'll be jumping ship soon, replacing the casing and ebaying up my charmer as im moving onto the trinity.
is there NO hope for any charmer users at the moment?! will you not help us develope a little?!
if you could provide me with a *test* rom, that has bugs in it, i could probably work on ironing out the bugs (worth mentioning that i only use my charmer solely as a PDA, not as a phone)
please dave! we need help from the masters of xda-devs!
Well, helmi's aku 3.3 rom is available on pdamobiz.com. Speed is excellent, but unfortunately this ROM contains a lot of stuff included :-(
If you can live without some regional settings, which are missing (eg. czech), this ROM might be useful for you.
Hi All.
So here we go again - trying to get Blackberry Connect to work on a new device..... so we've succeeded on the Kaiser and Touch Dual with both original and cooked rom's but I can't get any version to work on the new Diamond - received mine yesterday after frying the mini usb port on my Touch Dual and its one of the 1st things I installed? I've tried all the current fixes (I think) most of them summarized here in Elec.Two's post:
http://forum.xda-developers.com/showthread.php?t=371652
I'm hoping there will be a few others out there working on the same problem - I've just changed my aku back to .1.1.4 - I can get the device to sync when connected using activesync as a pass-through connection but get the "old" data tunnel available message and then it flips to "not connected" .....
I'll keep trying and keep this thread updated but could really use some help!
Hi, Im trying to change the name of this. I would like to change it to HTC-Herm200 or someting else. But I dont know what the build number have to be there. Anyone know ?
this has NOTHING to do with rom development... use some sense people! moving thread!
ROM Development????
Not sure what usap 's post is all about but my question is very much about ROM development? I'm looking for a registry change that will fix the problem that the CURRENT STOCK ROM has that means that bbconnect will not work?
I currently have WWE_1.34.831.1_52.24.25.08_0.93.25 loaded and have tried the standard "Tweaks" from past "ROM Development" but none have worked so far? I'm on constant watch for another ROM release (Cooked or Stock) or a Registry fix to help solve the problem?
ShogunMark - do you really think the thread was in the wrong place???? If its not ROM development then I'm in need of some guidance?
Im tying to change in HEX Editor the Signatures. For example there are DIAM100 (or DIAM10000) and build 19588. I changed it to HERM200 and 19588->17745. I can change it without changing the size of .nbh. But thre are "Diamont" Signatures too and by changing Diamong->Hermes wir have one less character (7->6). It changed the size of the .nbh.
So im trying to flash it to the Diamond nad about 96% OK, but then ROM flash error.
A meaning of it all is that it have to work, because RIM asks the Number and NAME and then when its in the list->OK, NO->pending.
I need some tools like SSPL 1.34 and ROMUpdate Utility that dont asks of CRC or something else.
Please Help
I've seen a few members reporting that they have a later ROM version > 1.35.707.3 - See thread http://forum.xda-developers.com/showthread.php?t=394985&page=12 I have not been able to find this as an officially released ROM and I'm not aware that its been dumped as yet? This slightly newer ROM may help solve the problems and may help usap with his question on the version number?
If there's anyone out there who know's the AKU and the version number for ROM 1.35.707.3 can you let us know???
Thanks
Blob8me said:
Not sure what usap 's post is all about but my question is very much about ROM development? I'm looking for a registry change that will fix the problem that the CURRENT STOCK ROM has that means that bbconnect will not work?
I currently have WWE_1.34.831.1_52.24.25.08_0.93.25 loaded and have tried the standard "Tweaks" from past "ROM Development" but none have worked so far? I'm on constant watch for another ROM release (Cooked or Stock) or a Registry fix to help solve the problem?
ShogunMark - do you really think the thread was in the wrong place???? If its not ROM development then I'm in need of some guidance?
Click to expand...
Click to collapse
he moved the thread as it WAS in the wrong place, blackberry connect isnt related to Diamond ROM Development.
Yes you have to Hex edit the ROM to get it to work, but it doesnt belong in that forum, and to your other question the newer build of ROM is not a newer AKU or build.
walshieau said:
he moved the thread as it WAS in the wrong place, blackberry connect isnt related to Diamond ROM Development.
Yes you have to Hex edit the ROM to get it to work, but it doesnt belong in that forum, and to your other question the newer build of ROM is not a newer AKU or build.
Click to expand...
Click to collapse
I disagree - for most every other device - getting bbconnect to work has been the result of ROM Development - if your familiar with the other device forums - you'll see that Blackberry discussion is often linked with and found in the ROM development forum?
HOWEVER - I dont really care which thread it sits in as long as "we" can work on a solution if there is one available?
FINALLY - Thank you for the information on the Malaysian ROM
Blob8me said:
I disagree - for most every other device - getting bbconnect to work has been the result of ROM Development - if your familiar with the other device forums - you'll see that Blackberry discussion is often linked with and found in the ROM development forum?
HOWEVER - I dont really care which thread it sits in as long as "we" can work on a solution if there is one available?
FINALLY - Thank you for the information on the Malaysian ROM
Click to expand...
Click to collapse
yes the ROM needs to be HEX edited but it has nothing really to do with the "development" of a ROM .
so when we get HardSPL ready and installed i will show everyone how to hex edit the ROM NBH files and then reflash it so bb connect can be used.
Blob8me said:
Not sure what usap 's post is all about but my question is very much about ROM development? I'm looking for a registry change that will fix the problem that the CURRENT STOCK ROM has that means that bbconnect will not work?
Click to expand...
Click to collapse
I'm not sure who to agree with...it really shouldn't matter so much to people.
Dark Fire said:
I'm not sure who to agree with...it really shouldn't matter so much to people.
Click to expand...
Click to collapse
Agreed - It shouldn't matter and here it will stay
I'm hoping for a tweak to the stock ROM (or even a "fixed" stock ROM to be released as I've heard that a next build Rom is due soon - and this has neen the main reason behind the delay in the UK and EU formal release??? Apparently - despite the popularity of "our" site less than 5% of device owners actually change anything on their phone never mind update firmware - official or otherwise? HTC are trying to minimise "support" issues by ironing out as many bugs before the next release - I know for a FACT that they use this site as a major test ground for any new device - so maybe the expansys release was intended after all???)
Thanks again.....
Blob8me said:
I'm hoping for a tweak to the stock ROM (or even a "fixed" stock ROM to be released as I've heard that a next build Rom is due soon - and this has neen the main reason behind the delay in the UK and EU formal release??? ... I know for a FACT that they use this site as a major test ground for any new device - so maybe the expansys release was intended after all???)
Click to expand...
Click to collapse
Yep, all of the evidence suggests that that's the reason behind the delayed release in Europe. New ROM. Hopefully with none of the bugs we've found so far (but I doubt it).
And that's a really interesting fact. It would be both nice and worrying to know that we influence them. (Nice when good devices like the Touch Diamond are announced, but worrying when there are major problems, such as that big driver problem).
Offtop (maybe)
I was playing yesterday with another phone and became the ROM extracted. So Registry and some of the files have the name of it in it. And I changed it to another name (Herm200 and HTC-HERMES) so that after the recreating and flashing the ROM it was everywhere Hermes. But PHONE ROM was dead (No signal, no phone). There were some imei*.pfg and some *.rgu and *.dsm where I changed all to HTC-HERMES and HERM200. So I had to flashing it to normal ROM.
And by the Diamond i worked with not extracted ROM. So i think there are 2 roads to change it: in extracted and not extracted ROM.
What do you think about it?
UPDATE on 1.34.831.1 and bbconnect?
Have just tried all the usual routes with the new EU Rom (details below) having used OliNex's SPL to Flash:
ROM: 1.34.831.1 WWE
Date: 5/25/08
WM6.1 CE OS 5.2.19588 (Build 19588.1.1.4)
Radio: 0.93.25.NS16
Protocol version: 52.24.25.08H
Still no success..... I've seen that there are other Roms also out there such as 1.35.871.5 but not yet available?
I was hoping that the Stock EU Rom would be OK as in the past the Stock "Official" Roms have run bbconnect with no changes and no problems???
If anyone has any other suggestions then your help would be greatly appreciated?
UPDATE ON Elite 1.0 and bbconnect....
Still nothings working - Sigh.....
I've got a specific request in the main Elite 1.0 Rom thread for walshieau to add bbconnect support now that HSPL is released - so hoping it wont be too long now!
walshieau said:
yes the ROM needs to be HEX edited but it has nothing really to do with the "development" of a ROM .
so when we get HardSPL ready and installed i will show everyone how to hex edit the ROM NBH files and then reflash it so bb connect can be used.
Click to expand...
Click to collapse
walshieau - any news on working on a solution now that we have HSPL out???? Can you add bbconnect compatability to the next Elite release????
UPDATE on 1.37.405 and bbconnect
Just added a comment on the main thread for this, the latest WWE EU Rom Release...... still not playing....
USAP - Any more thoughts??
walshieau - come on - you promised to help with a solution.....??? Help me out here????
Refresh......
Just refreshing as I'm getting desperate for a solution as I use the blackberry function for work and really don't want to switch back to my touch dual - has ANYONE had any success on the diamond with bbconnect?
Another "post" refresh.....
I'm still struggling to find a solution for this....???? In fact, I'm starting to wonder if there is a solution at all? Has anyone had any success at all with installing blackberry connect on any of the diamond Roms?
Blob8me said:
I'm still struggling to find a solution for this....???? In fact, I'm starting to wonder if there is a solution at all? Has anyone had any success at all with installing blackberry connect on any of the diamond Roms?
Click to expand...
Click to collapse
me waiting for a solution also. from what i notice, we just need 1 carrier to support bb on the diamond n we r all set. currently this is what i hav experience with the touch n touch dual which i have been able to connect despite local carrier not supporting it.
give a shout out if u do come across a solution though.