Hi guys, I've been lurking for a few days now - got myself an Xperia X1 recently, flashed it with the latest official release, but I've been having problems from day one with graphics corruptions.
Has anyone else seen anything like this? I got lucky and captured a video of it exhibiting the problem, but it can happen after it's been switched on for some time (hours/days) or sometimes corrupting the bootup splash screen.
http://www.youtube.com/watch?v=NOnsv4_-0rs
comments welcomed
You shouldt make a hard reset....It shouldt help a lot
I've done a hard reset - it does nothing, I've reflashed it with the original ROM (I backed it up before I did anything else) I've reflashed it with a custom ROM from here and with the R2A Generic UK ROM using the Sony Update utility - it makes no difference.
I'm guessing then that no-one else has encountered a similar error?
flash a custom rom (there are many without touchflo) they have updated drivers
I've spoken to the supplier, they're treating it as a quality fault, so it's going back for replacement - hoping that it's a one off issue, looks like i'm the unlucky one
I did try a custom TouchFlo ROM, it didn't make any difference (not sure if it hadupdated graphics drivers or not)
This gives me some time to look into porting Debian across to it
Related
Hi guys...I know there have been numerous reports of this kind, but I can't seem to find the answer.
I don't have this problem myself, but another person does and I thought I'd ask Olipro and the rest of the community for some help and clarification. Also hoping this answer can help anyone else who has this issue.
OK, Someone tried to flash WM6 before using the Unlocker. I know...don't say it. Anyway they now have the black screen of death and the tri-coloured bootloader screen, but are still unable to flash WM6 and obviously cannot use the unlocker until they have an O/S to sync with.
Has anybody encountered this and received incorrect vendor ID and found a way out of this scenario? They have an Austrian T-Mobile Ameo UK, so they can't even use the T-Mob 005 ROM for the UK Ameo (which doesn't require the unlocking of ones device).
Any clues peeps? It would really help a fellow owner out. Cheers for any input. Remember even if you said it before and don't want to repeat yourself again, please just cpoy & paste the answer here so it can act as part of the wiki for future incidents of this nature.
Thanks friends.
I got part of the experience. So I will tell what happen to mine AMEO.
due to some software conflict, my WM6 OS got kill. I was stuck in the tri-colour screen as well.
Since my unit was unlocked before, so refreshing (any) ROM solved my problem. (refreshing the ROM doesn't required activesyn running on yr PPC.)
If can't reflash yr ROM due to vendor_id error, I think the best way is to get the origin WM5 ROM (read it out from another same model) and flash it back.
after getting yr origin OS, then u can proceed unlocker and WM6 upgrade.
Hope this can help.
royalmail said:
I got part of the experience. So I will tell what happen to mine AMEO.
due to some software conflict, my WM6 OS got kill. I was stuck in the tri-colour screen as well.
Since my unit was unlocked before, so refreshing (any) ROM solved my problem. (refreshing the ROM doesn't required activesyn running on yr PPC.)
If can't reflash yr ROM due to vendor_id error, I think the best way is to get the origin WM5 ROM (read it out from another same model) and flash it back.
after getting yr origin OS, then u can proceed unlocker and WM6 upgrade.
Hope this can help.
Click to expand...
Click to collapse
Thanks Royalmail. I'll pass it on.
the sda-music, (or maybe sda only? how may i find out what device it is? its labeled "T-Mobile SDA" but seems to be the sda.music...) which is my girlfriends phone, produces many freaking errors lately.
so i decided, to not only hardreset the device, in fact i wanted to reflash the device with WM5 or 6 so there would be some nice software and feature additions.
But i read two posts, at least, that mentioned the authors device being bricked during flash-process...
now i wanted to know if the tornado is really that vulnerable.
and what is better flashing wm5 or wm6, is wm5 more stable and final than wm6?
i think the device is shipped with WM2003(se?).
is there any possibility to back up the existing rom and extrom (if there is one), to have the original rom anywhere backuped? (to reflash it, if anything isn't nice with wm5/6)
greetings
hoping for some answers.
garfield
hi there, i was wondering if you can help me solve my problem. im new to the o2 xda mini s phone. i just got this phone and its been flashed to wm 6. it keeps on freezing when i try to log onto msn or move items frmo my pc to the wizard.
is there anyway to fix it or better of to downgrade to its proper version. please reply promptly. thanks TIA
do you need any info on the phone? ill be happy to provide you if u can help me out !
jst a thought
one reason that you phone is freezing basically is that the wizards motherboard is not made to handle the wm6. its just like installing windows xp into a very old computer, the whole system lags down.
there is a way to downgrade it if you are interest. jst let me know.
I and a couple hundred or more people on here would probably beg to differ you on that opinion. I've been using windows mobile 6 on mine since just after it came out and I can't say as I've ever had a hardware related issue because of it. There have been a few software issues here and there, but they've always been fixed by someone on here.
I would guess that you may have an issue with an older version of WM6 and would probably be easily fixed with a newer version that you can find in the WM6 area of the wizard section. Before you go flashing anything though, do some reading in the stickies in the WM6 section to make sure you're flashing a new ROM correctly. There are 2 different versions of a wizard, a G3 and a G4 and each has it's own way of flashing. If you flash it incorrectly you could end up ruining your phone.
Hi,
I just wanted to tell you about a problem i had with my device.
I had the Khanx wm6.1 vanilla ROM for the last month.
Two days ago I flashed my device with udk R1.
everything was working fine.
I decided to "downgrade" my device to the Khanx old version.
after the flash everything is working good EXCEPT for the phone sounds.
I can dial (or receive) and make one phone call. After that, I can make phone calls but can't hear the tone (waiting,busy,etc...). The people on the other side can't hear me too.
Everytime I press the END button or the send button I can't hear any sounds whatsoever.
I flashed my device again with Khanx's ROM and nothing worked.
I messed with every single setup that I know on the device but nothing worked.
Currently, I got the udk R1 and I'm waiting for the new Khanx ROM (I just LOVE his ROMs).
Anyhow, is there anything that you can think of that I didn't do or done in a wrong way? did somebody encountered that same problem before?
Have a great day
Jam
Check Radio Version, Hard Reset
Latest WM6.1 roms are supposed to work only with the latest radio 1.59.42.15
http://forum.xda-developers.com/showthread.php?t=426203
Please make sure what currently runs for you, since these can be flashed independetly but sometimes are bundled.
Incompatibilities after downgrading are likely and discussed in above mentioned thread.
Two things come to mind:
1. Try a hard reset after flashing
2. also downgrade radio for example to Murata for the time beeing on downgraded rom
just wanted to say that I used Murata radio and it solved the problem.
sqeeza - thanks for you help.
Hi guys, sorry if this is mentioned anywhere else but I searched and couldn’t find anything.
The problem with my HD2 is that the sense ui has moved up a bit as shown in the picture.
I have this problem both with 1.43 and 1.48 firmware. When I hard reset everything is fine, but after a bit of use and a restart this happens. For example with 1.48 fw when I updated "MS my phone" it required a restart, after the restart this happened. Only the sense ui is affected.
Has this happen to anyone else? Is there a solution?
Thanks in advance
subgr said:
Hi guys, sorry if this is mentioned anywhere else but I searched and couldn’t find anything.
The problem with my HD2 is that the sense ui has moved up a bit as shown in the picture.
I have this problem both with 1.43 and 1.48 firmware. When I hard reset everything is fine, but after a bit of use and a restart this happens. For example with 1.48 fw when I updated "MS my phone" it required a restart, after the restart this happened. Only the sense ui is affected.
Has this happen to anyone else? Is there a solution?
Thanks in advance
Click to expand...
Click to collapse
Hi! I had the exact problem on my HD2 when it was running Windows Mobile, now when it has been almost 3 years since you wrote this, there was an update for this. I can tell because it looked proper when I took a last look at Windows Mobile on my HD2
NRG WM6.5.x is a cure to that & gives about the best real world use experience you can have on the HD2 ...