Related
did someone tried the dopod wm6 rom on an HTC 3600?
Thanks
I did.
Works very well for me. No bug at all. I'm happy with it.
what about the fix time of the GPS?
any changes in speed of the whole system?
and the battery life time?
Thanks
gerazzo said:
what about the fix time of the GPS?
any changes in speed of the whole system?
and the battery life time?
Thanks
Click to expand...
Click to collapse
I've upgraded my P3600 to WM6 (Australian ROM)
GPS - First detection is slow IMHO. After that it runs great.
Changes in speed - No changes so far I have noticed, in other words it still runs fast
Battery life - Is great depending on your usage. Just disable your infrared. That alone makes a lot of difference.
Where did you get the image ROM?
What is the difference between DOPOD and HTC Australian ROM?
Thanks
gerazzo said:
Where did you get the image ROM?
What is the difference between DOPOD and HTC Australian ROM?
Thanks
Click to expand...
Click to collapse
Does it matter where I got it from?.. Or do you want to know where you can get it?..
http://rapidshare.com/files/42337174/D810_ANZ_WM6_Upgrade_20070709.zip
I do not know what and if there is a difference is between DOPOD and HTC Australian ROM.
I just know that the ROM I used didn't have customized DOPOD screenlogo's/programs etc installed AND that I have only one issue since running this ROM but I think it's WM6 related:
http://forum.xda-developers.com/showthread.php?t=318013
All the OFFICIAL ROMs providing wm6 for trinity, so far, are from Dopod, including the rapidshare link above.
This is why it's called: 'D810' and not HTC P3600 in the link.
You may notice very few Dopod's customization, but it's still a ROM from Dopod, you can see, for instance, some Dopod's ringtones in the alarms and ring lists.
As far as the localized operator settings are concerned, I can't tell, since I did not install their extended ROM, I don't have any either, except for the ring tones I just mentioned before.
Regarding the new ROM performances, I think it has increased a lot from the previous April wm5 release from HTC: faster, better look etc.
The GPS is a little bit faster, but not much faster, but I think it has more to do with the new radio.
For example I could not get any fix with the 1.46.00.01 one from SEA. But it works quite well with the 1.46.20.01, from ANZ.
The most impressive improvement is the wifi connexion, which is stable, and fast. (it was a disaster with previous radios, especially the 1.38.x series.
Just to make myself more clear:
1)
I know all the trinity ROMs are made by HTC. What I meant is not 'made by Dopod' but, branded, designed for Dopod.
2)
I have read here before that wifi has nothing to do with radio but just with the ROM itself. I don't know, but what I can tell is that, the previous wm5 plus 1.38/1.41 radio series had always given me poor wifi performance.
But wm6 with 1.46. series is perfect in terms of wifi perfs.
At last do you think that flashing with an official ROM (Asian or Australian doesn't matter) i will not have any king of strange problem like with the wm6 coocked roms?
I want wm6 but i want all the features work on the device too.
Thanks for your patience, but i'm going to buy my HTC p3600 nad i will do only if i can have a perfectly working WM6 device with working GPS.
Thanks
gerazzo said:
At last do you think that flashing with an official ROM (Asian or Australian doesn't matter) i will not have any king of strange problem like with the wm6 coocked roms?
Click to expand...
Click to collapse
No, there are no garantees.
I want wm6 but i want all the features work on the device too.
Click to expand...
Click to collapse
I use the Australian ROM and all the features of my P3600 work.
Thanks for your patience, but i'm going to buy my HTC p3600 nad i will do only if i can have a perfectly working WM6 device with working GPS.
Thanks
Click to expand...
Click to collapse
Since there are no garantees there is a choice to be made. The P3600 is still unique in his features. It's the ONLY Window Mobile based PDA with 3G enabled and GPS onboard.
And what you do want to consider is that even if HTC releases a WM6 for Europe, there are no garantees that the ROM won't have any flauds.
Exactly, there is never 100% garantee to be fully satisfied and get no default or bug. This is why the reseller is there to offer you a one year garantee, so if you fancy the specs of the device go for it.
I don't want to start any debate about which programmers have more skills and more time to do proper job.
Individual ROM cooks are amazing and none of us will ever reach their skill levels, and they do it for free, just for the pleasure of sharing with us, so we owe them the greatest respect for that.
But obviously , after having tried both, I confirm that there are less conflicts and bugs in the official ROM than in the cooked ones.
Also because they take more risks by adapting applications that where not designed for the device (ex: touchflo and kaiser interfaces in trinity)
But I do believe that new cooked ROM from now on will be far more reliable than they were in before (wm6 ones), mainly because they now have a stable basis (the official dopod release) to make their own developments on.
So the difference might be slighter and slighter in those respects.
Explicit instructions for a dummy
Does this ROM update go as easy as the GPS unlock update?
I've done ROM updates that made you go through several activities and I just screw them up.
I'm looking for the simple version.
Jerry
Tried this and no luck
I have an HTC branded and unlocked P3600
I got this error:
Error 294 - Invalid Vendor ID
This update utility cannot be used for your PDA Phone.
Ideas?
No, it is not as easy as the GPS update ROM, and cannot be compare as you just experienced it because:
- it's not a HTC release, it's a DOPOD release, aiming at Dopod D810 clients, from South-east Asia and Australia-New-zealand.
- the ROM is heavy protected by its SPL to not install onto other CID devices.
- The previous Hard-spl crack doesn't work anymore and if you try to install it: luckily u'll get an error it will refuse to install, unluckily, it will get stuck in the middle of the install and you might even brick your device.
That's why you could not manage to install it. There are plenty of topics over this issue on this forum, you can try one of those workarounds, but take all responsibility if something unlucky happens during the upgrade process.
By the way: SIM unlocked, doesn't mean CID unlock, you can install any SIM card you want from any provider, but your phone's CID still belong to a language, a geographical area, and a manufacturer, which is HTC, not DOPOD ;-)
Come on guys...
read and use your brain..!!
Use this SPL:
http://forum.xda-developers.com/showthread.php?t=293632
and flash this rom. works for me like a charme. I've an normal HTC P3600 German Version - no special unlock.
Pinocchios
pinocchios said:
Come on guys...
read and use your brain..!!
Use this SPL:
http://forum.xda-developers.com/showthread.php?t=293632
and flash this rom. works for me like a charme. I've an normal HTC P3600 German Version - no special unlock.
Pinocchios
Click to expand...
Click to collapse
no chance without spl bla bla stuff?
i just want to excute and install :-(
that is it..
read the link I gave you. it is very simple.
copy this file to your pocketpc and execute it! works in 10seconds..
I clearly should do more reading before attempting this
Well, from you link, i can see that the boot unlocker works but i can't get back to my device because it's stuck in a boot loader rainbow screen.
How do i get it back to the OS?
I told you so...
1)
Don't think it's easy and simple, every one got different skills and experience and you don't help the noobies by saying "flashing a SPL protected ROM is 'easy and simple, just use your brain'...
Better being warned of the worst, if you want to do your best...
2)
There is a sticky thread in this forum about 'how to unbrick or unstuck you phone after having failed to flash the Dopod's ROM.
Read it CAREFULLY and try it out.
3)
Next time you try, use Olibro SPL or, more simple and safe for beginners, try to flash a ROM without SPL/IPL.
hitekfun said:
Well, from you link, i can see that the boot unlocker works but i can't get back to my device because it's stuck in a boot loader rainbow screen.
How do i get it back to the OS?
Click to expand...
Click to collapse
can you give more info on where you're stuck? (what is shown on bootloader screen). i'm assuming you've tried a soft reset to exit bootloader...
it's not that hard to flash a rom, the official dopod wm6 included. follow the guide here which will allow you to flash it without the new spl. it's still recommended to flash hard spl before a ROM flash to be safe.
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.
See the List over here: http://forum.xda-developers.com/showthread.php?t=439566
1.02.25.19 Raphael
1.02.25.27 Raphael
1.02.25.31 Raphael
1.02.25.28 Raphael
1.02.25.32 Raphael
1.03.25.18 Diamond
1.09.25.14 Blackstone
1.05.25.BS14 Diamond
1.09.25.23 Diamond
1.08.25.08 Diamond
1.06.25.29 Xperia
1.09.25.13 Quartz
Anyone tried to install a radio??
It should beposible. Why would raphael be able to flash Xperia radio but a Xperia no raphael radio.
in that thread xperia 1.06 radio link point to a file named "ht*p://www.4shared.com/file/73205809/670e29d4/Raphael_Radio_1062529.html"
I let you try, I don't trust it
theres mention of hexediting the radios here.
http://forum.xda-developers.com/showthread.php?t=443146
xmoo said:
See the List over here: http://forum.xda-developers.com/showthread.php?t=439566
1.02.25.19 Raphael
1.02.25.27 Raphael
1.02.25.31 Raphael
1.02.25.28 Raphael
1.02.25.32 Raphael
1.03.25.18 Diamond
1.09.25.14 Blackstone
1.05.25.BS14 Diamond
1.09.25.23 Diamond
1.08.25.08 Diamond
1.06.25.29 Xperia
1.09.25.13 Quartz
Anyone tried to install a radio??
It should beposible. Why would raphael be able to flash Xperia radio but a Xperia no raphael radio.
Click to expand...
Click to collapse
Yes, I have. I am currently using radio from build 19949. I can definitely say it has better reception in my area. I tried them out before posting them up. However refer to the post http://forum.xda-developers.com/showthread.php?t=455353&page=3 posts: 33-41 for more info.
Here's the link to the radios. I flashed my xperia x1i successfully, but the radio info on the device never changed despite the fact that all the radios had different size and origination: http://www.4shared.com/file/75157477/41406b1f/Radio_ROMs_for_xperia.html
I have already flashed few differents radios from Raphael and Touch HD, they working without any problem. You only need to make NBH file with NBHUtil and make sure in XML of this program there is 0x300 for Xperia radio (orginally Olipro/Cmonex adds 0x301 but it's wrong). If in xml is 0x301 device shoudn't be bricked (if its hardspl) but it will not change the radio.
ell82 said:
... You only need to make NBH file with NBHUtil and make sure in XML of this program there is 0x300 for Xperia radio (orginally Olipro/Cmonex adds 0x301 but it's wrong). If in xml is 0x301 device shoudn't be bricked (if its hardspl) but it will not change the radio.
Click to expand...
Click to collapse
Thank you for this post - I can see it's significant, but as a lesser mortal I cannot grasp the full meaning, so:
1) Olipro/Cmonex wrongly added 0x301 to ... WHAT, please ?
2) we need to edit the XML of the radio nbh file to 0x300 ? Or some other XML file, or ... WHAT, please ?
Could someone start a radio thread. And make these rádio's for Xperia???
ell82 said:
I have already flashed few differents radios from Raphael and Touch HD, they working without any problem. You only need to make NBH file with NBHUtil and make sure in XML of this program there is 0x300 for Xperia radio (orginally Olipro/Cmonex adds 0x301 but it's wrong). If in xml is 0x301 device shoudn't be bricked (if its hardspl) but it will not change the radio.
Click to expand...
Click to collapse
Thank you very much! You answered my question about why after flashing different radio's the version in device info never changed. Now after the xml was corrected, I bricked my device two times soon after flashing the prototype Radio and ATT Fuze one. It tells me that American Rom, supporting the 850 UMTS in ATT Fuze did not like the guts of the x1i. So it very much could be the lack of hardware for it? If only we could try the prototype radio for the same evaluation purposes. How come we cannot flash the prototype rom back on x1i?
mffu said:
Thank you very much! You answered my question about why after flashing different radio's the version in device info never changed. Now after the xml was corrected, I bricked my device two times soon after flashing the prototype Radio and ATT Fuze one. It tells me that American Rom, supporting the 850 UMTS in ATT Fuze did not like the guts of the x1i. So it very much could be the lack of hardware for it? If only we could try the prototype radio for the same evaluation purposes. How come we cannot flash the prototype rom back on x1i?
Click to expand...
Click to collapse
Cmonex said they were signed in a particular way in the hardspl thread, maybe they need hex editing to allow them to flash.
fards said:
Cmonex said they were signed in a particular way in the hardspl thread, maybe they need hex editing to allow them to flash.
Click to expand...
Click to collapse
Thank you, fards!
Could anybody help on this, please. We would all like to test the prototype radio. It could be a software switch that enables 850 UMTS if there is hardware for it. In prototype Rom there were all UMTS bands listed. After flashing the Att Fuze radio onto my x1i I had to go through the "unbricking" process. It did not like the american radio for some reason.
If anyone knows how to edit and flash the prototype Radio portion on x1i, please give us a hint. The device ID does not match when attempting to flash with radio b19949.
Any suggestions would be very helpful. Thank you.
The murk seems to deepen.
I still have a simpleton question above unanswered, but now we seem to have people who do know the answer to that question bricking their device, with evidence pointing to a hardware difference.
Perhaps when we have a genuine X1a radio file to compare with an X1i radio file, we may advance.
For sure, Qualcomm's greed is now stuffing up half the globe.
ianl8888 said:
The murk seems to deepen.
I still have a simpleton question above unanswered, but now we seem to have people who do know the answer to that question bricking their device, with evidence pointing to a hardware difference.
Perhaps when we have a genuine X1a radio file to compare with an X1i radio file, we may advance.
For sure, Qualcomm's greed is now stuffing up half the globe.
Click to expand...
Click to collapse
I'd leave it for a bit if you don't know, as it could get messy. When it's sorted then start playing
However from what I understand (can't help myself I like to play)
the xml referred to is the nbhutil.xml in most of the kitchens (including the kovsky)
Sure I'll be corrected if I'm wrong, but it looks like it allows you to "resign" the radio much the same way as hex editing it does. I linked to the discussion thread on that one earlier.
fards said:
I'd leave it for a bit if you don't know, as it could get messy. When it's sorted then start playing
However from what I understand (can't help myself I like to play)
the xml referred to is the nbhutil.xml in most of the kitchens (including the kovsky)
Sure I'll be corrected if I'm wrong, but it looks like it allows you to "resign" the radio much the same way as hex editing it does. I linked to the discussion thread on that one earlier.
Click to expand...
Click to collapse
Guys it isn't a problem to modify 0x300, but to change the device ID to be able to flash the prototype at least. Some folks flashed with the similar band Radio's from Diamond or Raphael successfully.
I was not able to flash any American (with 850 UMTS support) Radio yet, nor the prototype radio. We need an expertise on further guidance.
fards said:
I'd leave it for a bit if you don't know, as it could get messy. When it's sorted then start playing
However from what I understand (can't help myself I like to play)
the xml referred to is the nbhutil.xml in most of the kitchens (including the kovsky)
Sure I'll be corrected if I'm wrong, but it looks like it allows you to "resign" the radio much the same way as hex editing it does. I linked to the discussion thread on that one earlier.
Click to expand...
Click to collapse
Thank you for the reply. I can easily hexedit a file, but I needed to know which file of course.
I have an X1a on order - supposed to be delivered in maybe 2 weeks. I'm in Aus in an area serviced by the 850Mhz frequency, so I'll be able to give a definitive. When the thing does arrive and everything works out of the box, I'll do a "pcoread" and upload the raw ROM files here.
SE have stated to me in an email that there is no X1a, X1i etc, only an X1. At this point, I'll suspend disbelief. Also the UK retailer I am purchasing from (who has in the past proved reliable and honest) is doing the "funky chicken" about actual supply date, although they say they have stock. I made it very clear to them that if the 850Mhz is crippled, the thing goes straight back for an instant refund ... so we'll see.
HERE´S MY 2 CENTS - HOPE THIS HELPS YOU GUYS:
I have a "european" X1i
I am using my euro-SEX1i on my 850MHz provider: TELEMOVIL-TIGO
I am connecting to 850MHz GSM/EDGE
It "has" the UMTS 850MHz band "listed" in the phone settings menu, but when I manually select it the phone can't connect
I can use 850MHz GSM but not 850MHz UMTS
My ROM version: 1.02.931
My RADIO version: 1.06.25.29
My CPU: Qualcomm 7200A
My Model identity: X1i
My software: "Generic UK"
PS: my provider DOES offer GSM and UMTS over 850MHz, so I am sure it is the phone and not the provider
Found this on the Raphael section: http://rapidshare.com/files/163298875/Raphael_Radio_1.09.25.14.zip
Anyway to convert it to Xperia??
Ok guys, just flashed my Radio. At first I did edit the hex value to 0x300, like described here. I flashed using the default ruu update tool and I got an error, which bricked my device. So I moved to the SD-Card method and flashed directly from it. Same problem - update goes up to 100% and then quits with an error. The device is unusable.
However, when changing just the Raphael value in the nbh file - from RAPH***** to KOVS***** the update worked perfectly fine. I flashed back to the default radio version and now to the newest Touch Pro radio. The new version is not shown in the device information panel, but I can say for sure that it worked. When reception is lost its back in 1 second - before that it took 5-10 seconds. I will report back after using the device outside ...
chalid said:
Ok guys, just flashed my Radio. At first I did edit the hex value to 0x300, like described here. I flashed using the default ruu update tool and I got an error, which bricked my device. So I moved to the SD-Card method and flashed directly from it. Same problem - update goes up to 100% and then quits with an error. The device is unusable.
However, when changing just the Raphael value in the nbh file - from RAPH***** to KOVS***** the update worked perfectly fine. I flashed back to the default radio version and now to the newest Touch Pro radio. The new version is not shown in the device information panel, but I can say for sure that it worked. When reception is lost its back in 1 second - before that it took 5-10 seconds. I will report back after using the device outside ...
Click to expand...
Click to collapse
This is indeed good news, even if it doesnt unlock anymore band, the improve signal would be great.
romeo0119 said:
This is indeed good news, even if it doesnt unlock anymore band, the improve signal would be great.
Click to expand...
Click to collapse
No radio cab will "unlock" the UMTS 850Mhz frequency in the X1i, in my view.
I've posted on this in the 850Mhz thread - the X1i and X1a have differing hardware (likely the radio crystals cured to specific but differing frequencies) and HTC as assembler have separate production runs, as they did for the Touch HD ... my source for this is a very disgruntled retailer.
It's one on-going result of the Qualcomm patent theft US Court decision, of course.
Improved phone reception however is a big plus though, so I will try it, but the post should have listed the radio version number for the Touch Pro cab he installed. Not doing this just adds to the confusion unecessarily.
Anyway, HTC Touch Pro (Raphael) is UMTS 900/2100 only. UMTS 850MHz is not lised (source: HTC.com and pdadb.net).
Regarding UMTS 850, I guess the HTC Touch Diamond 110's radio (North american version) should be "the one" to try.
Curiously enough, Touch Pro and Diamond 110 have the same Qualcomm MSM7201A chip... but different bands ??
If somebody can provide that radio (from the north american diamond OR even better,FROM THE X1A) then I am willing to try it on my Xperia.
This is the only way to find out if the "european" X1i Xperia is UMTS 850 capable or not.
I've a Airtel locked HTC Touch Diamond.the stock fw was real slow so after getting rid of that Airtel lock flashed my fone with XBMod v2 rom.radio that i'm using is 1.09.25.23
now the specs written on the box of the Diamond state that it has the Qualcomm 7206A procy but now when i check thru Device Information on the fone it show Qualcomm 7201A.
Now i wanna know which 1 of these is the correct info.my fone has 7201A or 7206A?
Thnx & Regards,
HellGate
I'm new to this but previously had a AT&T Tilt from HTC and just upgraded to a HTC Tilt 2 (touch pro 2) on At&t, what radio version would i use on the US At&t network? my tilt2 is running WM6.5 pro and the versions numbers are these:
CE OS 5.2.21849 (Build 21849.5.0.63)
i just picked it up Saturday so its running touchflo 3d 2.1.19183217
its relatively up to date i think but i saw the roms running off the Leo touchflo and such and would like that alot on this handset
This is the thread for your question: http://forum.xda-developers.com/showthread.php?t=549939
Any radio listed in the thread that AvengerBB linked to will work on your device with AT&T, though the 4.49.25.17 is a very popular radio. To get the latest Manila 2.5 that's on the Leo, you need to flash a cooked ROM which has Manila 2.5. Most ROMs in this subforum have Manila 2.5, or feature a version of the ROM which has it. Look at the sticky at the top of this forum, called "Flashing your first GSM Rhodium ROM (For Noobs)" on how to do so.
yeah i just ran HardSPL and im wondering if i need to install a new radio first or after the rom in order to keep it there, other than that ive had no problems so far <crosses fingers>
edit: n/m fixed