I feel like an idiot :((( - HTC Vox

I recently (few days ago) bought my S710 (a.k.a. Vox) and it came with the WM5. So I found this forum nad Dr.Gonzo's thread about WM6.1 ROM (http://forum.xda-developers.com/showthread.php?t=384129), DL-ed the necessery sofware and followed the instructions (which seem to me like a peace of cake )
For some unknown reason I cannot finish the flashing of WM6.1, when I have to run the RUU I start the instalation, and after a minute or so (when the progress meter appears) the software says that the device is not connected. I tried this several times, always with the same problem.
what am I doing wrong? Please help me, so I don't feel like described in the subject of this thread.
P.S. and sorry if I made any gramatical errors, english is not my native language.

rbojan said:
I recently (few days ago) bought my S710 (a.k.a. Vox) and it came with the WM5. So I found this forum nad Dr.Gonzo's thread about WM6.1 ROM (http://forum.xda-developers.com/showthread.php?t=384129), DL-ed the necessery sofware and followed the instructions (which seem to me like a peace of cake )
For some unknown reason I cannot finish the flashing of WM6.1, when I have to run the RUU I start the instalation, and after a minute or so (when the progress meter appears) the software says that the device is not connected. I tried this several times, always with the same problem.
what am I doing wrong? Please help me, so I don't feel like described in the subject of this thread.
P.S. and sorry if I made any gramatical errors, english is not my native language.
Click to expand...
Click to collapse
you should firstly uspl your htc s710!(first treath) do do this its necesary that you app unlock your vox(as described in uspl treath) then you can update to any rom!(made for your device!)

...let me explain...
Like in the manual, first I rebooted (hardware reset) the device, then run SDA application unlock, soft reset, copied the necessery files to the root directory, run heret.exe through the .bat file.
the penguin appears on the screen for a short time, then the screen goes dim (like described). this is the moment I should start RUU, which I do, but one of 2 things happen:
1) either the RUU doesn't even recognize the device, and reports to check USB cable. The screen remains dimmed,
2) or it recognizes it, shows the USPL-vox on the device and starts update. At the very begining of update (zero or two %), it says that the device is not connected. the vox screen shows some info, and it's three-colored - blue, green, red (if I remember correctly). the RUU software exits, and then I hardware reser the device, to make it functional, but still with WM5.
what am I doing wrong?
EDIT: It's actually WM6, I needed a program to tell me that

Seems like your USB port on the PC is not working properly with the Vox. Try another Port or better an other PC to execute these tasks.
Could also be the cable - this may be easier to change.

I don't think that is possible, it's the same cable I use for connecting through ActiveSync and it works flawslessly. Any other ideas?
it's a standard USB-miniUSB cable I use for my old motorola mpx200 and my camera, don't beleive there can be a problem there?

Just try it - AS transfers a few bytes - a ROM is several MB. This is no proof.
Windows (ROM Update) also talks to the USB port in a different way than AS, so why not eliminating all parts that are outside the device (you have no other choice anyway).
- new/other USB cable
- new/other USB port
- new/other USB controler (e.g. other PC)

Can you not upgrade new rom from htc site?

Related

problem with flashing under WM6...

Hi everybody,
i have flashed the WM6 underground edition a couple of weeks back. Now i wanted to downgrade to WM5, but without success. I am using IPL/SPL 2.21. After starting the ruu upgrade software the Wizard switches to boot mode. So far so good.... But then nothing happens anymore and after a minute or so the software quits with error 260.
Any hints what to do ??
I have the newest Activesync installed.. I even cannot flash any other Wm6 rom.
Any help would really be appreciated !!!!
Best regards
Batman08
When you reboot your phone, post exactly what version IPL and SPL you see.
Didn't someone once post that there was a difference in USB cables....Grasping at straws, but just a thought!
Hmmm... do you hear the active sync connection bell ring when it reboots into bootloader? At the bottom of the screen, do you see the letters USB near the left hardkey?
Might try another PC, or even a different USB port on the same machine. Sounds like the USB is acting up.
After the phone reboots i can see IPL/SPL 2.11.
I can hear three bell rings with the same low frequency. To
me that is not correct as the connection bell ring should be two tones ?
I can see "USB" on the left side of the Wizard's screen.
I also tried different cables, but no success.
I am using WIN XP with SP2. Upgrading worked flawless
some month back with WM5.
The only thing i had to change was ActiveSync 4.5 as WM6 is only
supported there.
Any hint ???
batman08 said:
After the phone reboots i can see IPL/SPL 2.11.
I can hear three bell rings with the same low frequency. To
me that is not correct as the connection bell ring should be two tones ?
I can see "USB" on the left side of the Wizard's screen.
I also tried different cables, but no success.
I am using WIN XP with SP2. Upgrading worked flawless
some month back with WM5.
The only thing i had to change was ActiveSync 4.5 as WM6 is only
supported there.
Any hint ???
Click to expand...
Click to collapse
ERROR [248~260] : UPDATE ERROR
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
This is taken from the redme inside the RUU
Good Luck
Put the phone into bootloader mode, kill WCESCOMM.exe from process list, attach Wizard, let it install driver, open up RUU and (hopefully) flash.
Also make sure you pull out your SD card while you try to flash your phone.
@neonkoala:
You made my day !!!!!!!! it worked flawless.... Thanks a lot !

Mda compact with serial v1.02 screen

Hi everyone.
After much searching I seem to have got nowhere. Can someone please help.
My mda compact 2 starting playing up yesterday, rebooting on its own, so I tried to install the upgrade from tmobile (ruu charmer). The upgrader stopped and my mda now has a screen that only either says serial v1.02 or usb v1.02.
I've tried rebooting it several times in several different ways without any joy, the screen just remains the same. I tried connecting to my laptop via active sync, but its like it doesn't exist anymore!
I'm about to give up after hours of trying to fix it, so any assistance in very simple terms would be much appreciated!
problem solved
Seems like my problem must have been too basic or too common for anyone to bother to help, so I did some searching myself throughout this site and elsewhere.
However, what I found was thoroughly misleading and unhelpful.
The error messages are also inaccurate and totally misleading. Error 274 might mean pc can't connect to pda, but it also means other things, like your using the wrong upgrade firmware!!. Having serial v1.02 or usb v1.02 on your screen does not mean its a grey and black brick(useless), its simply the upgrade mode screen.
Basically, I made an error in choosing my upgrade. I chose the wrong firmware package from t-mobile thinking what I had was a mdacompact 2, when it actually was just a mda compact. This error was the main issue, yet from this forum I had the idea it could have been a number of things.
One important thing to remember is adhering to all the instructions regarding the installation of the new rom.
Don't bother unless you do the following:
1) Make sure you have a good connection via cradle or usb lead when doing the download.
2) Make sure you close all unnecessary programs on your pc.
3) Dont touch either your pc or the mda during installation.
4) Don't give up after you read misleading rubbish on the web.
5) Make sure you download from the web the correct upgrade firmware!!(very important in my case!)
6) Active sync is not totally necessary during the process.(I turned off usb connection in its setting during my installation).
Hey
I have the same Problem
i tried updating the software on the phone but now i get that screen..
Im still stuck on what exctly to do, I've been googling it for hours!! HELP!!!
matty x

Rescued Prophet (aka Happy Unbricking)

I am posting this here since there seems to be way too many threads around here all saying the same thing diffently yet in NO clear way that everyone can understand. I spent 2 days trying to recoved a Prophet from a bad flash.
Symptoms
Prophet stuck in Bootloaded (Tri Color Screen)
Prophet stuck in 2nd Splash (Usually Your providers Splashcreen)
Solution Read as (This is what I did to fix it)
Download a WM5 Prophet\Wizard Official Rom (I still own a Wizard so I used the K-JAM_WWE_216901_2169101_020710_ship rom, the devices are very similiar concerning chipsets with the hardware keyboard seeming to be the biggest difference)
Extract the Rom (if it is distributed in an exe format with a tool like Winrar or 7zip)
Download the Prophet Tools Light package and extract to any folder . This contains both G3 and G4 RUU's (I can confirm this worked on a G4 Device)
Place the Official nk.nbf in the \Utils\Flash folder
Drop the phone into bootloader (Tri Color Screen) mode and connect to PC via usb.
Allow a few seconds for the usb connection to settle and run the RUU specific to your device.
DO NOT TOUCH the device or PC at this point. If your pc is a tad slow, go make some coffee and watch an episode of Big Bang Theory
This should now give you a shiny new (or old ) rom that is bootable which will allow you to upgrade your Prophet to any of the pretty WM 6.1 roms available.
Just a little tip:
If you are worried about messing up the device again use Alternate "Lazy tool" by dioxda. Its easy and it works !
I couldnt make this process any clearer if I tried
heeey...sorry but after this my prophet go death... i cant turn it on, and i dont know how but it seems that i cant charge it no more...
is death... can anybody help me how 2 fix this?
P.S.sorry if my eanglish is not very good.
specto13 said:
heeey...sorry but after this my prophet go death... i cant turn it on, and i dont know how but it seems that i cant charge it no more...
is death... can anybody help me how 2 fix this?
P.S.sorry if my eanglish is not very good.
Click to expand...
Click to collapse
Strange this worked perfectly for me, but when I tried updating to a different rom I got the same problem you are facing now. Just a quick flash on the screen and blue and red LED flash. If I plug it in it just sits there flashing the whole time. I am looking into this as soon as I get a solution I will post it here. Any help guys ?
cornelha said:
Strange this worked perfectly for me, but when I tried updating to a different rom I got the same problem you are facing now. Just a quick flash on the screen and blue and red LED flash. If I plug it in it just sits there flashing the whole time. I am looking into this as soon as I get a solution I will post it here. Any help guys ?
Click to expand...
Click to collapse
Recovery
http://forum.xda-developers.com/showthread.php?t=401326
If at any stage your Prophet fails to start properly or can only enter bootloader follow this:
* Download and install the latest version of ActiveSync (Google for it)
* Download and unzip an AKU2.2 (No Vendor) ROM for the Prophet-any AKU 2.2 will do-from [here | ftp://xda:[email protected]_NVID.exe] or [here | http://wiki.xda-developers.com/index...=Prophet_ROMs]
* Within ActiveSync DISABLE connect through USB (Tools->Connection Settings->Uncheck Allow Connect through USB)
* Put the Prophet into bootloader mode (hold the camera button and insert the stylus into the larger hole next to the power socket)
* Plug the Prophet in via USB
* Run the RUU specific to your device (G3 or G4) from the AKU2.2 folder. If there is only one RUU, use that.
* When it has finished: disconnect the Prophet, and then re-enable the connect through USB in actyivesync before reconnecting the device.
==> if success, will going back into WM5 and then u can use the Lazzy Tool, look at http://forum.xda-developers.com/showthread.php?t=353547
choose WM 6.1 ROM, after u doing that step, u already done with the WM 6.1 SEMOGA SUKSES!
yes it works again ...
Help, please?
Hi guys,
I have a slightly different problem. When I turn on my Prophet, it is in bootloader mode, so I take out the battery, leave for 3 seconds, put the battery back in, turn on the Prohpet.
Bootloader is displayed
Plug into PC with Active Sync 4.5 running (USB disabled)
Windows makes the 'new hardware connected' sound
RUU shows USB in bottom corner
Run the NVID no vender ROM,
Agree to first screen
Agree to second screen
Click Next
Prophet turns off
Windows makes the 'hardware disconnected' sound
Argh
No Prophet, no phone - incommunicado!
When I turn the prophet on now, I just get the bootloader, then it turns itself off after 10 seconds.
Could it be a low battery? - How do I charge it? I have left it plugged in to the power all night!!!
Could it be a faulty phone? - I have been having random resets over the past 3 weeks or so and thought that it was the WM6.1 rom installed, so was trying to put WM5 back on to see if that helps. - I am beginning to think there may be something wrong with the device?
I am trying a few more things from this forum before giving up and buying a new windows smartphone!
Any help would be apreciated!
Regards Mike
Guess it could be a power issue. - I got further just now by using a powered cradle instead of just a usb cable, but still reset at 80% complete. Will leave the phone charging using a wall charger only for an hour and see how i get on with that!
Its Fixed!
Ok,
So it turned out to be a low battery. - I charged the Prophet up for 1 hour and then ran the re-flash and it worked perfectly.
Now I just need to get the Orange rom back on it so its back to normal - Not faffing with WM6.1 - will stick to WM5 as its much quicker and works!
Maybe I was a bit too fast in posting the problem!
Thanks
Mike.

Dead Prophet? Problem with flashing? This could help you!

Hi,
I just crashed my phopret. BUT due to some good ideas of user Users i solved my issue. I want to tell you how.
My history:
I already had the "update package" installed and used several WM 6.1 ROMs.
I love the Diamond rom from vincent. see link
Then i tried to flash my prophet with a rom for the charmer. Hm, bad. It crashed when it tried to restart. Anyway.
I tried to reanimate it. It failed. I stopped for that moment and started again a day after.
Now it runs again. Juhu. I tried every update , orginal ROM, Tera Term etc. But always the same issue:
Bootloader starts but only runs until info screen with the isp number etc.
"The Charmer rom erased everything so there was now Operating system at all."
Even the bootloader was not the original one with 3 colours and I was not able to connect to the PC because it stopped booting.
How to solve this issue:
Download the "Lazy Tool" from here
If you need additional info read this otherwise try it my way
Flashing Tool thread
1. Press Camera Button and Softreset (with stylus).
2. Remove ONLY the Stylus. --> Get the 3 Colour Screen.
3. Connect with Cable to the (this important) USb Port at your Mainboard (native ports).
4. Unpack it.
5. Run "Upgrade.bat" and keep the window opene in the Background
6. Go to "lib" and run the G3 or G4 "Rom update utility"
7. follow the introductions
Finish. You did it. Great job.
To get a good Rom.
Use the update utility and run after a reset the vincent rom.
BE ALWAYS AWARE THAT YOUR PROPHET IS CHARGED. Mine wasn´t once and i wondered why it always restarts again.
Some nice progs are:
Slide 2 View (Album like on the iphone)
Slide 2 Unlock (unlock like on the iphone)
Icontact (contacts like on the iphone)
Touch Response (get a vibration by pressing a button)
G Alarm (good alarm in the morning)
BT Remote (to remote powerpoint by bluetooth)
Thanks to everybody who develops nice tools like the "lazy tool" and shares his/her experiences with WM. Good job Friends.
Greatz,....

Trouble with Hard SPL

Hello this is my first post I'm writing because I'm having trouble putting Hard SPL
on my ATT Fuze. I have XP and I connect the phone to the computer and sync it
then open the SPL program go through the prompts then my screen on the phone turns off, the phone I believe also turns off and I get the error 260 a screen pops up on the computer saying it found new hardware. Any help with what I'm doing wrong would be greatly appreciated.Im kind of freaked every time I get up the nerve to do it and think I bricked my phone.
Did you install Microsoft .NET Framework 3.5 first?
Here is the link to follow steps incase you didnt see it.
http://forum.xda-developers.com/showthread.php?t=448008
Hey thanks for your help after further reading I know I should have posted this in the right section and yes I have framework 3.5 installed I guess one question would be that I installed 3.5 to the computer do I install it to the phone? Also I have been reading the hardspl post I think one of the ideas is to first install the SSPL manual
to the phone is that correct? Then do the hard spl? If this is corect what do they mean by install it? run it? active sync? sorry just want to get this right
This is from memory - so if i miss something, sorry!
You shouldn't get any error messages when you connect your phone to the pc, regardless of what boot state the phone is in.
The manual jump SPL is to be used if your phone doesnt enter the correct state automatically from the RRU.
If you want to use the manual jump SPL, do this:
1) Connect your phone to the PC (ensure it can sync correctly - no connection errors)
2) Copy the SSPL_manual to the phone
3) (on the phone) run the SSPL_manual file
3b) Phone should now go to a blank black screen
4) Run the RaphaelHardSPL-Unsigned_190_1_3.exe on the PC
4b) Follow the PC on-screen instructions
**However**
you say that the phone turns black / screen off when you run the exe normally - this is supposed to happen. You shouldnt get an error here. (this screen off part is what the manual SSPL is going to do anyway).
**
If you still get problems, ensure you are connected to the computers USB port - not via a USB hub, take the SD card & sim out the phone. Maybe try a different PC, different USB lead - always make sure you are following the instructions very carefully - and if you still have problems, let us know & we'll try harder! - remember to tell us everything, if you try 2 leads - tell us! If you get something different, tell us what! You can never give too much technical info when asking for technical help - and the more you have tried, the more interested others become (we all like figuring out a problem!)
Beeble
Thank you so much for your help just to give you an update either way I do it
Manual SSPL or just run the Hard SPL by itself the screen goes black and I know
thats what it is supposed to do. Just to clarify at first I did not know the screen was supposed to go black so thanks for that. Again either way it disconnects and a screen comes up saying it found new hardware from that point at first I was scared to do anything else but but eventually I just clicked YES install the hardware hoping that after I did that it would not disconnect but even saying yes to the Found new harware it would say it could not install any hardware and I'm stuck
from there still getting the error
Again I cannot say enough how helpful people have been even if I have not been able to get hard spl on the phone yet

Categories

Resources