Worked ok last night, then it crashed (mad colours on screen), so I had to do a FULL restore of radio and rom (seemed to be stuck in bootloader).
So, reinstalled everything, all good, I just cannot get it to turn on WIFI. I go into comm manager, click on wifi, and it tries to turn it on, then comes back with a X next to the icon.
Also the front today screen plugin (the wifi/bluetooth one) doesnt say WIFI: off anymore. Just has Bluetooth:Off
Any ideas
THANKS!
Try to flash back the rom again..
By the way, what rom do u used?..
I only just flashed it again ..
I used the O2 rom 'Xda_Exec_Upgrade_v1.30.162'
Can you recommend another ROM that might fix it?
Also, does reinstalling a ROM reinstall all the drivers? As I've noticed some things stay resident even after a flash; call timers for one..
thanks
while im waiting for replies, im going through roms
trying different AKU ones now from the ftp
could it be a radio issue?
My QTEQ 9000 are on the same situation, made some stripes on the screen and now can´t detect anything!!
The wifi apears I start it but can´t get any signals!!
Any help please?????
i upgraded radio to 1.14 and still same
Try these ROMs
You can find on the forum, Ivan's and Helmi's ROMs.
They are the latest AKU 3.2 and seems to work just fine as O2 ROMs are just AKU 2.X!
I think the problem lies deeper than a hard reset/rom as well, it must do after installing 3-4 roms, and a couple of radios.
Yes ive tried UNI_AKU3_5_WWE_IVAN_Test2 ROM as well.
Same.
Anyone else got any solutions as to what it might be?
installing the latest qtek rom off buzzdev now, includes full radio/rom/ext rom. if this doesnt work, then f**k it, ive spent enough hours on it, and i'll just get a new one on contract tomorrow.
thanks for the people that replied
what about the driver disk, isnt there a wifi thing on there
maybe im dreaming
Have a look in the network adapters list and see if the Tiacxwln card is listed, if not sounds like it is a hardware rather than a driver problem. It's not unheard of for computer hardware to fail for apparently no reason. This is likely if you have tried different ROMs and none of them work.
I´ve tried upgrade radio to 1.14 and I tried Ivan's and Helmi's ROMs.
and the problem persists!!!
Tiacxwln card is listed.
Strange situation because during one year worked very well and suddenly make some stripes on the screen and now don´t detect nothing!!
Maybe antenna problem??
Help us??
Is there a problem with o2 official rom?.. Heard few people also got a problem if flashing to o2 rom..
Nope, not working, tried qtek roms, a new orange rom, still wifi not coming on.
Yes the card does show in network cards.
Oh well
Any help Please???????????????????????????????
Related
I have a UK M5000 and updated the ROM to the new Orange ROM without problem. It was still slow so I plunged for the upgarde to the Dopod ROM. Since I did this it crashes all the time. Sometimes I can reset it sometimes I have to take the battery off. After a bit it won't even boot at all!
Despite all this I am always able to get to bootloader and reflash it. I have since tried the QTEK ROM and even back to the Orange ROM but now it still is unstable. Is there any known reason for this that I can try.
PS tried task format commands and mtty stuff as most of the time after a crash it sticks at the splash screen in all ROMs.
PPS IT NEVER did any of this before even after the first Orange ROM upgrade.
ANy help much appreciated.
Thanks
James
Not sure if you've cured this by now but I am a UK Orange user with SPV M5000 and went ahead with Dopod upgrade wihout any problems.
Presume you tried Hard Resetting, formatting card etc?
I have the same problem... It starts 2 days ago... Its terrible!
I have T-mobile. Now i flashing with original T-mobile ROM and i hope that everything will be ok.
If anybody knows whats happend???
I thought that the problem is on hardware...
30 minutes ago i flashed with latest I-mate ROM and when after flashing i do hard reset nothing happend. I see black screen and thats all!!!
Yes! With T-mobile ROM it seems to be ok. Now i try to flash with I-mate ROM again.
May be the problem is in the "MaUpgradeUt_noID.exe"?...
MaUpgradeUt_noID.exe
I find out that there are some issues with this file. Is this the same file we used to use during upgrade/change language??? If yes, than why when I tried to dawnload from the buzz web side i find that there said that the file is 365kb but when you dawnload the file is 165 and that is why some people are having problems when upgrade their rom or change operators/languages.
So if I want to change language it sais that you shoul run MaUpgradeUt_noID.exe and than I see in the picture of Magician. Is this NORMAL and should I go forward or WHAT.
Flashing with T-mobile original ROM didn't resolve the problem...
It's still bad...
What the hell is going on with my Universal???
Having done dozens of updates over the past couple of years I've finally had my first problem occur. I've searched the other postings and been unable to find anything which is similar to the effects that I'm getting.
For some reason I'm unable to upgrade the radio rom - just the radio rom, the other roms updates go in perfectly OK.
The universal displays the screen that it's "started upgrading.... Please wait" but then nothing happens. Eventually the the upgrade tool times out. I've tried about 10 different radio roms (ones that I know I've loaded before) but no luck.
All firewalls are turned off, I'm not using vista, direct USB connection, and other roms update OK so I'm really not sure what's happened. It's now left me with a universal with no radio rom at all!
Has anyone any ideas or is it perhaps that this rom has broke in the device?
Try removing the sim card and the SD-card.
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Sprite?
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
ruffruff said:
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Click to expand...
Click to collapse
Yes i had same problems. imo the 1.93 isnt a stable rom(yet) so im back with 1.37.456.2 this one is just perfect,very stable,less memory leakage.
Well, the problem is still on going. I can't flash my phone anymore for some reason, even though I've tried both, unsigned and signed Hard-SPL, which both of them flash fine. However, the phone gives me error [276] update error. So not sure what exactly is going on here.
Also, no, didn't sprite backup, phone's just being retarded, mobilecityonline will repair it, but it will take almost 4-6weeks, I cannot wait that long. What else should i try?
Okay, nope not fixed... Flashed it with 1.37, connected to the network for a few seconds, dialed somebody and no ring or anything, but when i called my phone i could hear my own voice. So I guess i have to send it in for repair. Damn.
berlinberlin said:
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
Click to expand...
Click to collapse
Could you please detail? I've flashed 1.93.xxx just in the day it appeared on the site and after flashing, I've restored the backup made with Sprite Backup to preserve the settings and so on. I wasn't worried about the contacts/calendar since I have them in Outlook, but I didn't want to start all over with settings, install programs and so. I've made the restore in "upgrade mode", restoring also the databases. The result was that I got a verry strange TF3D, displaying "Home" between the operator name and date, and strange behaviour. I've seen also that the animations were taken out so I've flashed back 1.37.xxx.3. Could be any problems generated by the restore operation? Should I use a different restore type (eventually not selecting "restore databases")?
I have had no problem with the new 1.93xx rom.
Touch FLO 3d is quicker (probably because the animation is disabled)..
and the battery life is about 20% better
Radio ROM Anyone
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
mhbr12742 said:
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
Click to expand...
Click to collapse
I am on 05 and has no problem ( have been using it for a day now)
I don't know, but If i plug the diamond into my adapter, the network suddenly works and I can actually make calls and everything's fine and dandy, but just on the battery, I can't call anyone, and if I pull out the adapter when the phone gets a signal, the signal stays but again, can't call anyone because i can't hear anything.
It's an awkward problem. I'm not sure if it's my battery or something. So I'm getting another battery off ebay since they don't sell HTC Touch Diamonds in the U.S. yet.
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
adwinp said:
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
Click to expand...
Click to collapse
Yes, me I had same problem twice - freezes on PIN input screen, second problem with this release is that sometimes PIN screen doesn't appear. Now I'm back on 1.37 and everything seems to be ok
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
THe Problem you've encountered:
1. Random auto reboot
2. Random freeze
3. etc.
It's sounds familiar to me. Well it's maybe have to do with SPL just like the Kaisers do.Well, I said maybe... So, what we did to our Kaiser before is flashing the HardSPL which has the same version number as the ROM flashed. So, if you're using ROM 1.93 then the HardSPL should be flashed is Olinex HardSPL 1.93 or you can try one by one of the developed HardSPL existed in this forum. My saying is, go with HardSPL 1.93 and see what happen. If it's still no go then it must have to do with the ROM itself.
Just my 2cents.
Hi all,
My Diamond is acting weird lately; sometimes (so far it seems at random) when I turn on the device (from standby), the display is grey'ish / scrambled, and nothing works. I have to removed the battery to get it working again.
This happens with all ROMS found here (haven't tried stock rom yet).
Anyone know what this might cause?
I'm running dev. edition SPL from olinex...
Any tips would be greatly appreciated!
/edit; Could this be SPL related?
Maybe perform the hardSPL again?
Reform the battery for a minute. After this hard reset your device a few times.
If this doens't fix the problem use your original ROM and send the device back for repair.
Would be my solution
I have the same problem. Diamond swiches to standby mode and does not resume or just the light switches on and the screen is blank. Sometimes, it even switches off while booting. All the time, I have to remove the battery. And after some "battery remove resets", the error seems to occur more and more often. It also suddenly looses the phone signal but immediately finds a new one ofter 1-2 seconds.
I think it is somehow related to the phone chip-whatever. Because when I turn the phone of it seems to run more stable. Errors are not gone but at least I can use it as a mp3 player then.
I tried lots of roms but none of them worked fine. I even restored the original spl to make sure it is not the spl. But error is still there... stronger than ever
I will send it back to htc. This thing is obviously broken. Its one of the typical qualcomm errors. These chips are... what do you say in english... moody? My old polaris had a similar error. the 3g part of the phone went away.
TerianSilva said:
I have the same problem. Diamond swiches to standby mode and does not resume or just the light switches on and the screen is blank. Sometimes, it even switches off while booting. All the time, I have to remove the battery. And after some "battery remove resets", the error seems to occur more and more often. It also suddenly looses the phone signal but immediately finds a new one ofter 1-2 seconds.
I think it is somehow related to the phone chip-whatever. Because when I turn the phone of it seems to run more stable. Errors are not gone but at least I can use it as a mp3 player then.
I tried lots of roms but none of them worked fine. I even restored the original spl to make sure it is not the spl. But error is still there... stronger than ever
I will send it back to htc. This thing is obviously broken. Its one of the typical qualcomm errors. These chips are... what do you say in english... moody? My old polaris had a similar error. the 3g part of the phone went away.
Click to expand...
Click to collapse
Sounds bad
I'm trying an updated radio rom at the moment, we'll see if it hangs today...
mikkelnl said:
Hi all,
My Diamond is acting weird lately; sometimes (so far it seems at random) when I turn on the device (from standby), the display is grey'ish / scrambled, and nothing works. I have to removed the battery to get it working again.
This happens with all ROMS found here (haven't tried stock rom yet).
Anyone know what this might cause?
I'm running dev. edition SPL from olinex...
Any tips would be greatly appreciated!
/edit; Could this be SPL related?
Click to expand...
Click to collapse
Hi mikkelnl... from what you described, it seems to be a typical problems with the SPL you are using. Depending on which SPL that the original ROM that came with your device, you can resolve by installing the respective 1.37 OliNex HardSPL Unsigned or the 1.93 OliNex HardSPL Unsigned by cmonex.
Try to get it from the same thread that you got the 1.40 OliNex HardSPL-Developers Edition. There is also some explanation on the problems that you are experiencing.
One more thing, Radio 1.00.25.08 also appears to have some detrimental effects on some devices after some usage. And it has a lingering effects too. Try use Radio 07 if you are in Europe or Radio 05 if you ar in Asia...
Having said all these, I must state that these are purely my observations and you really need to try it out for yourselves to know whether it works for you. I have given the same advice to about 5 users experiencing these problems and it had worked for them so far.
Swiftblade said:
Hi mikkelnl... from what you described, it seems to be a typical problems with the SPL you are using. Depending on which SPL that the original ROM that came with your device, you can resolve by installing the respective 1.37 OliNex HardSPL Unsigned or the 1.93 OliNex HardSPL Unsigned by cmonex.
Try to get it from the same thread that you got the 1.40 OliNex HardSPL-Developers Edition. There is also some explanation on the problems that you are experiencing.
One more thing, Radio 1.00.25.08 also appears to have some detrimental effects on some devices after some usage. And it has a lingering effects too. Try use Radio 07 if you are in Europe or Radio 05 if you ar in Asia...
Having said all these, I must state that these are purely my observations and you really need to try it out for yourselves to know whether it works for you. I have given the same advice to about 5 users experiencing these problems and it had worked for them so far.
Click to expand...
Click to collapse
Hi Swiftblade!
Thanks for the reply. I've read about those newer SPL versions, but I didn't think it was the reason for my problems, since I have one of the first Diamonds (can't remember the spl version ). And; the thread mentions "fuzziness issues on some newer diamonds", my screen is not 'fuzzy', it simply is scrambled and the device completely hangs. So I didn't figure that would be the problem
Anyways; I am a bit reluctant to install a new SPL, never did that before...
mikkelnl said:
Hi Swiftblade!
Thanks for the reply. I've read about those newer SPL versions, but I didn't think it was the reason for my problems, since I have one of the first Diamonds (can't remember the spl version ). And; the thread mentions "fuzziness issues on some newer diamonds", my screen is not 'fuzzy', it simply is scrambled and the device completely hangs. So I didn't figure that would be the problem
Anyways; I am a bit reluctant to install a new SPL, never did that before...
Click to expand...
Click to collapse
Hi mikkelnl.. It's really worth a try. the description on the thread is of course vague. It is actually to deal with some discrepancy issues between SPL and the device's specification.
Doing a HardSPL will not affect your rom but it will hard reset it so you get a fresh clean rom. Do perform a backup before you do a HardSPL though. My best bet is 1.37 OliNex HardSPL Unsigned.. Cheerz
Edited: If this HardSPLs can't solve your problems then it might be a hardware issue that you are facing...
Well, I just installed 1.37 olinex, let's see if this helps
Thanks for the input Swiftblade! Now I'll just have to re-setup your 7.0 rom
mikkelnl said:
Well, I just installed 1.37 olinex, let's see if this helps
Thanks for the input Swiftblade! Now I'll just have to re-setup your 7.0 rom
Click to expand...
Click to collapse
Hope it works out for you bro... Good Luck!
Hello,
Today i wanted to try the new 3volution rom for the s620 when i got an annoying bug
I spent most of the afternoon looking for an answer but found none.
Everything works well in the beginning until i got to push the center button for the screen to turn white. It turns white indeed but then activesync desynchronizes and doesnt resync anymore, so im unable to upgrade (either it stops at 3% or with kavana's doesnt detect old rom) and in some cases it says the new flash rom is corrupt..
Its like my 5th flash, and prior to today i never had a problem flashing and upgrading
So i tried reinstalling activesync multiple times, changing cables, even hard resetting my s620 (i got the nrg rose 1.7 rom on it), i even restored my comp on a previous state.. nothing
It just keeps breaking the sync when i push the center button and doesnt resync for the rest of the procedure
If someone has an idea im all ears ^^ and sorry it it has been already posted
Welcome to forums
Try a hard reset or reinstall ROM
Have a deep read here:
http://forum.xda-developers.com/showthread.php?t=537151
Hope it helped,
redownload the rom. then read this http://forum.xda-developers.com/showthread.php?t=493266
3% freeze up it very common
I am seing something similar. If I set my device down without locking it the screen goes completely white. When I first loaded the rom it didnt do it for about a week and now it does it everytime. The only changes I've made since loading the rom is that I installed Google Maps and TCPMP.
Hmm its very weird, i did the hard reset.. well it didnt work..
The 3% error i got that only once
I tried installing the official htc 6.1 windows mobile rom and got the error 244 ...
and same as always, the moment the screen turns white it disconnects from activesync and doesnt reconnect. Imho XP needs reinstalling..
So my theories so far are: activesync is buggy to the core. Ill try flashing on my laptop as soon as i get to it.
Also one thing ive noticed: in all my previous flashes i had the original htc battery.. now i got an extreme energy battery with a blue and white sticker, ill try replacing the original battery before reflashing.
As i said in my first post, this is not my first flash, and i have flashed before to kavana's then rose then kavana's again and it always went smooth.
I have been using the S620 for like one year and a half and never had a prob.
Its an htc version and it was not locked; anyway in belgium locked phones are forbidden to sale
Greetings from the land of the beer and thanks to the developpers
Which Bootloader are u using ?
The official shipped one or the modified one ?
Hmm good question, where can i see the version ? When it boots up i see the nrg rose 1.7 black screen with white writings.
Another weird thing: my keyboard is azerty, so prior to hard reset i had a language pack for french keyb, after the hard reset my keyb works just fine without any language pack installed ... not that it is a problem but i just dont understand ^^