I guys, I've tried upgrading my JasJar with Xda_Exec_Upgrade_v1.30.162, using MaUpgradeUt_noID and when update was complete I cannot load my JasJar anymore. I am using hard reset, but when choosing "0" off the boot screen - noting happens and screeen remains black.
Can someone please help me with this issue?
Thanks a lot in advance,
Best regards,
Stazik
Try reflashing it again. If it does not work, try reflashing back to the i-Mate ROM.
Whats the version of your bootloader (the screen with serial at the top changing to usb when plugged into usb)? If it is 0.56 or something else below 0.6 thats an already known problem.
I had similar problems with my O2 upgrade.
Try:
- Turn off USB in ActiveSync
- Hold Power/Light and press reset button
- Run the upgrade again
Thank you very much for help and support, guys!
When I try flashing my JasJar with Bootloader update or JASJAR_WWE_13076_164_10900_wwe_ship I get the same error message: Error 101 Connection Error. And also when I disable ActiveSync USB and plug my Jasjar into USB - I get a message from windows saying the device was not recognized...
The only I can get from JasJar is a black screen, except when I press two soft buttons and reset - that gives me a screen with 0 and x to choose. Neither of choices helps thou.
Any help is appreciated. Thanks a lot.
you didnt answer the question re the boot loader number.
when your screen is grey or starting to reset, there are numbers on the screen. what are they.
if it is less that 0.6 your in trouble and assistance is different to if your boot loader is 1.0 or similar.
My screen doesn't change from gray except when I do hard reset. And then I hit two buttons and reset, then press 0 the message Clearing now appears and then everything returns to gray again.
How can I tell the version of bootloader in this case?
Thank you in advance!
they are hard to see, if the screen is grey, the numbers are black.
f the screen is blue/coloured, the nmbers are probably red.
Thanks for help guys,
I brought my JasJar for service today, somehow they were able to put older ROM in there. Now I've upgraded bootloader, hopefully newest ROM from i-mate going to fit without problems )
Well I've killed my Jasjar upgrading I was installing the bootloader update. It sat there saying "Checking information on your device" for about 30 minutes after the update started (notes said it would take 10 so I figured something was amiss - disconnected & rebooted my PC.
Now when I turn the Jasjar on I get the USB/Serial screen referred to above and (good news I figure) it has v1.00 at the bottom. How do I fix this?
TIA
Sheesh. I did a search (I know I should have done that first) and found the answer here
Took a while to find a copy of mtty to download, but found that at http://buzzdev.net
Once I'd done the Set 14 0 and tried the boot loader update again it took seconds so something definitely went wrong the first time.
Related
PLEASE HELP!!!
I try upgrade my Dopod 900 to WM6 by using http://micmeo.com/UNI/WM6/900_WWE_20...0_wwe_ship.zip, but after the upgrade success 100%, i disconnect the USB, and hard reset the PDA, then the PDA cannot bootup, it alwaus showing the black screen...
When i try hard reset again, i can see the display show option 0 to reset and option X to exit, but try both keys which back to the same black screen...
I also try press power+light+reset, but no responses at all... when i plug in the power cord, the light for charging not on as well...
PLS HELP....
dopod900xxx said:
PLEASE HELP!!!
I try upgrade my Dopod 900 to WM6 by using http://micmeo.com/UNI/WM6/900_WWE_20...0_wwe_ship.zip, but after the upgrade success 100%, i disconnect the USB, and hard reset the PDA, then the PDA cannot bootup, it alwaus showing the black screen...
When i try hard reset again, i can see the display show option 0 to reset and option X to exit, but try both keys which back to the same black screen...
I also try press power+light+reset, but no responses at all... when i plug in the power cord, the light for charging not on as well...
PLS HELP....
Click to expand...
Click to collapse
Try to enter the bootloader mode (power+light+reset). From what you have described it appears that you should not have problem entering the bootloader mode. Please remember that in bootloader mode yor screen is dark and only when you look very carefully you will be able to read the word "Serial" on the top of the screen and bootloader version number at the bottom. If there is inssuficient illumination in the room it is quite possible to think that the screen is blank. There will be no backlight. Once you are in the bootloader connect to your PC (before connecting please open Active sync on your PC uncheck the "Allow USB" connection in File / connection setting) Once connected the word "Serial" on the top of the screen will change to "USB". It is advisable to use only the original cable. Also connect the cable directly and not through a hub. Now reflash the rom and do a hard reset. I have faced problems by softreset after upgrade please try hard reset.
Hopefully your problem will be solved by a reflash.
Best of luck
From my past experience you have to flash to the original manufacturer rom first. Then you flash to whatever rom you want.
hope this helps
Thanks all, I'm now be able to re-flash the ROM and upgraded to WM6....
Here comes another issue... after i run the first setup and reset the PDA, it stuck on the Windows Mobile screen, any clue?
thanks again.
dopod900xxx said:
Thanks all, I'm now be able to re-flash the ROM and upgraded to WM6....
Here comes another issue... after i run the first setup and reset the PDA, it stuck on the Windows Mobile screen, any clue?
thanks again.
Click to expand...
Click to collapse
From the file link you have specified, http://micmeo.com/UNI/WM6/900_WWE_20...0_wwe_ship.zip it seems that you are using Jwrightmcps' WM6 2.01.08 WWE Rom Release.
I too have lock-up problems but only during boot-up. The frequency of this happenning is about 30% and why it happens is still unknown since the lock-up happens at random stages during the booting sequence. The only solution that I know of for now is to simply do a soft-reset repeatedly until the device boots up properly.
nvatvani said:
From the file link you have specified, http://micmeo.com/UNI/WM6/900_WWE_20...0_wwe_ship.zip it seems that you are using Jwrightmcps' WM6 2.01.08 WWE Rom Release.
I too have lock-up problems but only during boot-up. The frequency of this happenning is about 30% and why it happens is still unknown since the lock-up happens at random stages during the booting sequence. The only solution that I know of for now is to simply do a soft-reset repeatedly until the device boots up properly.
Click to expand...
Click to collapse
This appears to be a common problem as seen from different posts. Thankfully things are ok after reset.
yes, after reset few times, it works... and everytime it hangs, need reset few times...
dopod900xxx said:
yes, after reset few times, it works... and everytime it hangs, need reset few times...
Click to expand...
Click to collapse
You might find this of interest - it refers to the problem of hanging after soft reset in the 2.01.08 WWE Rom:
jmallen said:
I had this problem also. I found pulling out the battery for 5 or more seconds solved this for me every time.
Give it a try. Good luck
Click to expand...
Click to collapse
It may be solved in later versions.
d_ranade said:
Try to enter the bootloader mode (power+light+reset). From what you have described it appears that you should not have problem entering the bootloader mode. Please remember that in bootloader mode yor screen is dark and only when you look very carefully you will be able to read the word "Serial" on the top of the screen and bootloader version number at the bottom. If there is inssuficient illumination in the room it is quite possible to think that the screen is blank. There will be no backlight. Once you are in the bootloader connect to your PC (before connecting please open Active sync on your PC uncheck the "Allow USB" connection in File / connection setting) Once connected the word "Serial" on the top of the screen will change to "USB". It is advisable to use only the original cable. Also connect the cable directly and not through a hub. Now reflash the rom and do a hard reset. I have faced problems by softreset after upgrade please try hard reset.
Hopefully your problem will be solved by a reflash.
Best of luck
Click to expand...
Click to collapse
boss ... please help me ..... i have a dopod 900 ..... but it can not enter bootloader or hard reset .... ditancap usb cable, charger lights flash .... Please help keep the boss. ... thank you
Welcome to forums
Have a read on my signature link, you´ll find a lot of interesting information to recovery your Universal.
Good luck,
flash with tomal roms
Welcome to forums
Tomal ROM´s are indeed fast and stable
manybe you can nmsm your original rom again
Try update bootloader to 1.01 _ttp://rom-update.ru/programs/dd48795954c166e9431f4127c130d474.exe
German Qtek 9000 CID unlocked, hardSPL'd
running MaxStegiROM
Tried to upload D-Two's ROM.
Everything went fine, upload 100%
then: upload error.
screen went black, no reset works
no USB or Serial to be read on dark screen.
Tried battery out (battery is charged), no reaction.
When connecting to PC the red charging LED lights up for
some minutes, then goes off.
PC says connected unknown device ain't working properly
(other Qteks are recognized properly)
Trying to re-flash gives connection error when pressing "update".
Any idea?
Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help
Tried to upload the software on my MDA Pro and all of a sudden the screen on the MDA goes blank. I've tried master reset and i press 0 and it says clearing or whatever. Then it goes to the USB/Serial Screen and it reads v1.01 at the bottom. What do I do?
Hi, could you please post some more details? e.g. Which version was originally on the Universal and which version did you flash....
Cheers
Michael
Hi,
You just need to run the Upgrade again. As long as it says USB when you have it connected, no harm is done.
Cheers,
vma
No...There is definately some damage done. Its stuck on the boot load screen Where it says Serial at the top and V1.01 on the bottom. I just got it new in the box untouched and totally screwed it up trying to update the software to "UNI_TMUK_130114_130232_11003_WWE_BL101_Ship" I dont know what the original rom software was at all. It went to the grey screen that it is stuck on now and the power nor reset button works. The letters are still there in black on a grey non lit screen. Master reset (soft keys+rest) brings me to the screen but after i press 0 it says clearing now but goes right back to the serial/v# screen(boot load mode)....thats it...
Look it's not damaged. It boots to the bootloader. So long as it has the bootloader it's COMPLETELY recoverable.
1st thing you need to do is look here.
Scroll to the bottom and use method 2... It's a LOT easier and has saved my bacon many times!.
Psi
Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.
Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work
Try a Vodafone branded stock rom before mtty.
Regards,
Carty..
He already tried a stock rom....
Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.
Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.
Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware
u have to only push thoose 2 buttom then it will work because u go to rescue mode
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey
Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!
Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!
Hi All
I posted this in another forum... but hope its better suited here.
My Father has an SPV M5000 (HTC Universal). He has unlocked the SIM lock from IMEI number some time ago.
Recently it started going screwy and so he did a soft reset and then it wont turn on at all.
He has let me play with it and if I try a hard reset it comes up with the screen saying "press 0 to restore...", but if you press 0 it says "clearing now" and then appears to switch off. If you press x it also appears to switch off.
You can enter bootloader mode and it displays SERIAL on the screen - when you plug it in to a PC the screen changes to USB. But when I try connecting using MTTY I get no USB port - although selecting COM5 seems to open a command prompt window - but to be honest I dont know where to go from here.
If I try a soft reset it seems to do nothing - although the orange charging light blinks once.
With it connected to a PC in bootloader mode I was able to reflash the ROM and it went through all three stages correctly and indicated it had been successful - but when you finish with a hard reset it appears to turn off.
Before I use it to wedge my living room door open, can anyone offer any advice? I have perused the forum, but cannot find anything which seems to match the fault I am getting.
I know its not the battery as I have the same model and the battery is new.
I suppose if nothing can be done... does anyone have any ideas what to do with it now?
Thanks in advance
SlipMat
Perhaps you can find something on the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
Hope it helps,