Related
I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).
This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)
Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.
Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.
I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)
I hadn't at any point played with the ROM.
What should I try next?
And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new
Thanks in advance.
-Steve
RE
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Re: RE
FOSA said:
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Click to expand...
Click to collapse
Unfortunately, no such luck
I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.
Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?
-Steve
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Jorgee said:
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Click to expand...
Click to collapse
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)
I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.
Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!
-Steve
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
thefixer said:
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
Click to expand...
Click to collapse
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Jorgee said:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Click to expand...
Click to collapse
Jorgee,
I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.
Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?
Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?
Regards
Steve
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Jorgee said:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Click to expand...
Click to collapse
Hi Jorgee,
I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.
I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.
One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).
-Steve
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Jorgee said:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Click to expand...
Click to collapse
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!
-Steve
OK, here's what happened when I tried to update with the same Qtek firmware:
Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.
Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:
"Error 113: Extended ROM Update Error"
The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.
-Steve
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Jorgee said:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Click to expand...
Click to collapse
No luck.
I've also tried re-flashing a second time, but this time I watched it to see what happens
As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.
I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?
I'm also wondering whether to have a go at flashing the ROM in one of the other ways?
-Steve
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Jorgee said:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Click to expand...
Click to collapse
Thanks Jorgee. Still no real success, but I think I might be getting closer.
I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).
I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)
radio_.nbf always seems to flash ok
ms_.nbf always fails right at the start, and nothing appears on the phone's screen
nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.
Soft or hard reboots still result in us just ending up 'hung' at the boot screen.
Once again, thanks for your help so far. However, I am beginning to give up hope!
-Steve
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
truongia said:
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
Click to expand...
Click to collapse
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!
One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.
Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)
-Steve
Hi all,
Since last friday I'm the happy owner of an S200, until sunday atleast. After a soft-reset, initiated from windows, my device won't boot anymore. It hangs in the red-green-blue bootloader screen (says: IPL 2.09, SPL 2.09). I've tried soft-resets and hard-resets, but the device would consequently keep hanging in the bootloader.
So for the past few days I've been searching the web and just managed to update the ROM. I was expecting that updating the ROM succesfully would mean my device would boot again, but it still keeps hanging in the bootloader (saying IPL 2.09 SPL 2.15 now, so the update did take place).
Does anyone has any idea whats wrong with my phone? Or how to fix this? Please help.
* bump *
I've been searching further and tried to do a SD dump, but I'm getting the message I don't got enough rights to perform a SD dump. This meens my S200 isn't CID unlocked. Is there any way to CID unlock the device without the need of booting into WM?
The solution to your problem
Hello, if you are having bootloader screen right after starting your mobile (prophet) check if your camera button is depressed since i had the similar problem. In my case i had to disassembly the phone in order to fix it. Right after fixing the button it worked fine
hi syzzer,
i really feel with you - why? - i have the exactly same problem. after i tried to upgrade my rom from o2-germany to another one the device isn't starting anymore and hangs in the beautiful-colored bootloader. and now, if i just even want to re-install the same or another rom, doesnt matter which one, the s200 wont start again. i think this is a really unlucky situation for us to stand alone with our weak pda =) hoping for more help, otherwise we have to take up our warranty and try to get it fixed by the store we did buy it (if a rom-update damage is still in warranty )
good luck
budy!
awechris said:
Hello, if you are having bootloader screen right after starting your mobile (prophet) check if your camera button is depressed since i had the similar problem. In my case i had to disassembly the phone in order to fix it. Right after fixing the button it worked fine
Click to expand...
Click to collapse
in my case, the camera button is not pressed in... i truly don't know what to do hopeless? mhm?
greets!
budy!
hello Syzzer
I have the same problem, but i make a soft reset and it works.
Camera but + Com Button + Power
Wait until message appear.
You Get the message : For Hard reset press send
If you choose other key the system boots normaly.
I had already tried all your suggestions, but nothing seemed to work.
About a month ago I bought a Trinity. In the mean while, I forgot I had put my S200 in my bag and carried it around for a month. When I found it a week ago and started pressing random buttons, it suddenly booted and has been working ever since! The problem has gone as mysterious as it came. I can only imagine there was some hardware failure / dirt in my device that caused the trouble and is now gone / moved to some place it does not do harm. Because I already bought a Trinity, I gave the S200 to my brother. He's been using it ever since and did not have any problems. So keep your head up, there's hope!
I m also having the same problem
Now I am having the same problem, no button is pressed, and I can not install the NVID ROM
Actually I can install only a few ROMs, the NVID ROM was working before on my Neo perfectly but, I think it can be because I have changed many ROMs, from a month, actually I have tried different WM6 ROMs and I used NVID ROMs mostly for Step 1.
Now when I install any ROM, it shows a msg some nbf one after 80% or 95%
It can install the pdaviet first step ROM, but now the problem is that it hangs very much and it can not start Wifi, it has stopped working, a few more ROMs i have tried, but the WIFI is completely stopped.
When I press it in communication manager, it will show busy icon for a few seconds and will not start it in end.(I tried it in both WM5 and WM6, same problem, I also tried after soft reset and hard reset, the problem is still there)
Please someone help me out.
Hi Friends,
My new mobile phone SPV M600 got stuck whil starting showing four lines of messages as shown below.
IPL 2.10.0001
SPL 2.10.0001
GSM 02.07.20
OS 2.10.1.22
Can any one please help me in geting my phone to today's screen.
I also attached the screen shot for reference.
did you try a hard reset ?
Ya I tried both hard as well as soft reset but same screen is stuck again and agian.Can any one please help me in this regard as I am very new to PDA family.
Ok, first things first:
Since you are new to this, are you sure you preformed a hard reset?
It is done by holding power + camera + comm manager buttons (one on the right, two on the left) and pressing with stylus in the reset hole at the same time.
A message should appear asking you to press 'send' (green phone button) to confirm reset.
If this does not help, you may have a serious problem.
Please answer the following:
Is the device fully charged?
Phone will fail to boot if the battery is too low.
Did you install any software right before this happened?
This should have been resolved by hard reset, but just in case I am asking.
Did you change the ROM, attempted CID / SIM unlock?
This could require more serious measures than I can advise on.
I did exactly the same thing which you mentioned.But even then it is stuck at the same screen.
Ya u r right I unlocked my mobile using a software from eBay.The unlock was successfull and I tried to insert T-Mobile sim, it also captured the signal and I was able to make and recieve calls then after that I wantedly switched off the phone and then tried to start it, there got the problem.
Can any one help me in this regard please.
I am having the same problem, but my phone is not sim-locked.
I've got the same problem after attempting smart1_wm6_pp8mb.exe
I'm having the same problem with my G4 QTEK S200:
Attempted to upgrade to WM6 Rom using smart1_wm6_pp8mb.exe
After reboot the phone got stuck at the QTEK Screen
Tried Hard Reset (Camera+Power+Comm+Reset) followed the steps with the same results (bricked)
I also tried re-flashing the rom back to the factory one using RUU_Prophet_220734_2207114_024721_QtekWWE_Ship and ROMUpdateUtility-NoVendorID.exe in Windows Vista with WMDC (Windows Mobile Device Center v. 6.0.6873) and the phone in boot loader mode (tri color screen) with working USB cable, with windows firewall disabled and symantec AV disabled as well, RUU keeps saying error 260 "the update utilitiy cannot connect to your pda phone..." .
Do you think I should try this process using XP instead? No matter what i try i keep getting the error 260
Any help would be greatly appreciated
Got it fixed!
it was definately a Vista issue. once i tried it in XP with ActiveSync it worked like a charm and i got my phone back up and running. also used spb backup and restored all my settings.
ipl/spl screen
i got the same problem with new rom wm6, and the 260 eror, my problem is that i have xp and the activesync does`t connect ...
... means i cant redo the original rom ????
PLEAAASEEE HELPPPP !!
Again My phone SPV M600 got stuck at IPL/SPL screen
Please Can some one advice me how to get my phone back.
I raised the same issue 7 months back after that my phone got recovered automatically and there were no issues till last month. Last month onwards it is again got the same problem and now it is permenantly stuck at that screen what ever you do.
yekanth said:
Please Can some one advice me how to get my phone back.
I raised the same issue 7 months back after that my phone got recovered automatically and there were no issues till last month. Last month onwards it is again got the same problem and now it is permenantly stuck at that screen what ever you do.
Click to expand...
Click to collapse
A rom reinstall on xp solved my problems on that one. retry a couple of times! It may not work the first time! hard reset as well...
Try an official wm5 rom just in case
good luck
Can you please gimme step by step procedure
HI Phil,
I am new to these kind of installations . CAn you please Gimme step by step procedure for ROM installation.
mine is now also stuck, after trying to install new rom. wont connect to active sync either, have i fooked it? tried hard reset etc.
thanks
(with a turned off phone, press and hold camera button then insert USB cable)
then flash provider ROM
RECOVERING FROM ERROR IN STEP 8 WM5->WM6
1. Don't panic
2. Don't panic
3. Unplug the phone
4. Reset with stylus,and keep the Camera Button pressed.
5. A 3 color screen will appear(Bootloader Screen)
6. Connect your device with your PC,and run the NVID(no vendor) WM5 rom.
7. The device will be resetted after RUU(rom update utility)finishes
8. Repeat the WM6 upgrade,from STEP 5..
Click to expand...
Click to collapse
from here http://forum.xda-developers.com/showthread.php?t=310452
hi jay
i seen your post in n00b guys one, i fixed it!!!!, thank you so much, i couldnt remember how to get it to those 3 colours.
thanks again
Colin
Hi Iam unable to get the NVID ROM
Hi,
I am unable to get the NVID ROM. The Rapidshare link that has been provided in the other thread is not working. Can some one tell where can i get the ROM.
collywog19 said:
i seen your post ...
Click to expand...
Click to collapse
no problem mate.
..and yekanth i see what u mean about the dead links. i have the files on my computer at home but i'm posting from my prophet right now, so i can't upload. Try using the "pdaviet temp" from one of the wm6 threads?
(http://rapidshare.com/files/54265407/Prophet_PV_Temp.zip)
Hi Iam able to update the Rom but no use
Hi,
To mention my phone is from orange-UK. I got the orange rom from our FTP site and did the flashing/update what ever you say.But still it is getting stuck at the same IPL/SPL screen. Iam very much worried that I will not get a proper solution for my problem.It will be very grate full if some one resolve my problem.
just seems strange...how did you fix it last time? did it just start working again? A random guess would be that the camera button got liquid spilled on it or is stuck in.
If the camera button is pressed in the phone will go to 3 colour screen every time it is turned on.
It won't do any harm if you try to press/move that button to see if u can "unstick" it, not likely I think but u never know...
I received the "An update is available" pop-up yesterday evening, an update of 4,37mb. After accepting the update it starts downloading and when it finished it asked if I wanted to apply the update
When doing so, the screen turned black and after a while the "Hero" screen popped up. They said it could take up to 10 minutes, but I let it run for 40 minutes without any luck..
Also when I want to go back to the factory settings, it reboots and hangs on the "Hero" screen
If I remove the battery and start it back up it works, but without the update ( so still 1.5 )
I then tried to wipe the machine by pressing the Home, Back and Power button, which worked
So I was back in the phone with a clean install, but the same issue occured
I then called HTC who asked me to perform some steps, but none of them worked and I have to add that they did not sound like they knew what they were talking about..
I asked if there was a possibility to install the 4,37 mb update manually, but that was not the case according to him and asked me if I wanted to make an appointment to have the machine reconfiggured, which means I would lose it for 5 to 10 days
If there is no other solution I guess I will do that, but I first want to see if you guys have any suggestions
I'm thinking about installing RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDriver via HTC Sync ( found in [ROM] Official HTC Hero RUU ROM + Radio Links thread ) but I am worndering; what if this fails and I'm again stuck on the Hero screen, will it affect the current "install" ? Since I can always go back if needed now by removing the battery, I would like to keep that option ^^
Also, if I install that, will my phone still fall under the guarantee of HTC?
Thanks in advance
i have nearly the same problem..after trying to install the 2.1 update OTA i stuck in the HERO screen..hard reset won´t work..fastboot isn´t possible because of "remote : not allow".. also tried it with hboot..useless any other advices?
maybe this helps:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.06.18
Aug 4 2009
For you guys you might need the goldcard method used in my sig.
Started the Bootloader-USB and then the RUU...now installing the rom..hope this will work
well I would like to know if I will still be under the waranty (not sure if that is the correct term, i'm not english ) of HTC if I make such changes and it fails
well guys..starting fastboot and then RUU worked well for me. now having stock 1.5 rom and installing 2.1 OTA
hope this helps some people, too!
what do you mean with starting fastboot?
I downloaded the RUU ( RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDriver.exe ) and it works if I doubleclick it, I can start installing it but I'm afraid to do so
by holding the back button and pushing the end-call button once (while still holding the back button) the fastboot menu will come up. while in fastboot menu, just start the RUU..the update will start.
but i don´t think you´ll need that, since you can boot your phone..i couldn´t, thats why i needed to do it this way
Doubleclicked the .exe
"Checking Custom ID"
"Update Fail"
And HTC Sync is saying I should look for a correct ROM Number
That doesn't look good, does it?
Luckily the phone still starts!
Going to try it with RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe now (since that is the version I need according to htc.com )
same issue
Anyone know which RUU I should try?
Modelnumber: HTC Hero
Firmwareversion: 1.5
Smallbandversion: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.27-8dd6deee [email protected]
Build-number: 2.73.1100.5 146733 CL#61267 release-keys
Softwareversion: 1.0.0.A6288
I am from Belgium by the way ( we had a lot of issues with the update, at least that's what I read on several websites )
mOwtant said:
by holding the back button and pushing the end-call button once (while still holding the back button) the fastboot menu will come up. while in fastboot menu, just start the RUU..the update will start.
but i don´t think you´ll need that, since you can boot your phone..i couldn´t, thats why i needed to do it this way
Click to expand...
Click to collapse
I'm in fastboot, how do I 'just start the RUU' ????
If I try hboot, it does nothing, says it can't find any files...
Help PLEASE!!
Figured it out.
Synced phone via htc sync and installed RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDriver
did the trick!
Called HTC again.. they said I need to wait before the official RUU for Belgium gets released (since they need to remove YouTube from ours )
I just hope that won't take ages
I have quite similar problem. I have installed 2.1 official ROM from Lox, but sometimes, it stucks on HERO screen. I have to pull out battery and boot again, then it boots fine. Is that problem known?
Crexis said:
Doubleclicked the .exe
"Checking Custom ID"
"Update Fail"
And HTC Sync is saying I should look for a correct ROM Number
That doesn't look good, does it?
Luckily the phone still starts!
Going to try it with RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe now (since that is the version I need according to htc.com )
Click to expand...
Click to collapse
You need to use the goldcard method to "trick" the phone into a different number so the 'downgrade' can be issued.
I have t-mobile UK unrooted + simlocked
When i power on phone .. Round red icon comes on screen , then HTC logo & some music , then again tmobile logo comes & move a little & phone hangs there .. not going forward
Hard reset not helping
i have downloaded this rom
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_signed hboot + radio removed .
I make a gold card & rename it to update.zip but updating not starts
HELP
i am a newbie in this
Thanks
anyone know which name to be set in update file
Who can help me here ?
You don't need to rename it to update.zip, just select install zip from sd card.
Download the right rom from shipped rom for your phone and run it from your PC
I don't think you can use the file you mentioned above as your phone is not rooted ( I might be wrong)
foxy6800 said:
Download the right rom from shipped rom for your phone and run it from your PC
I don't think you can use the file you mentioned above as your phone is not rooted ( I might be wrong)
Click to expand...
Click to collapse
Tmobile UK Shipped Rom for wildfire .. i am searching for last 2 days but did not get it ..
http://shipped-roms.com/shipped/Buzz/
tmo stand for T Mobile ( I think)
foxy6800 said:
http://shipped-roms.com/shipped/Buzz/
tmo stand for T Mobile ( I think)
Click to expand...
Click to collapse
Thanks
let me download & check it up
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
is this supports rooting ?
Update comleted by Shipped Rom
but still same position
Round red icon comes on screen , then HTC logo & some music , then again tmobile logo comes & move a little & phone hangs there .. not going forward
so the problem is related to any H/W issue ?
http://img703.imageshack.us/img703/4314/82699533.jpg
this is the condition on phone
what type of forum is this ??
no one reply's ??? Just reading ... Ugghhhh
Have you tried holding the volume key down and switching on the phone
then facotry rest
yes offcourse ... Hard reset was always my first step ..
update with shipped tmobile uk rom .. Then hard reset again but still same
Can you not run unrevoked?
Sent with love from f0xy while mobile!
how can i unrevoked it if USB debugging is not ON ... ...
i think problem is from h/w b/c if shipped rom is flashed OK & phone still have same problem then it must be hardware problem