Alright I'm finally going to throw a post up, go ahead and get all your "use search" "it's on search" "it was in a thread" out of the way now, cause I've gone through 76 thread pages of reading and searches and I can't find an answer that works.
I am continually getting the ERROR 262 in RUU everytime I attempt to use it to flash.
- I am running Vista 64bit (not sure if that is the problem or not)
- Using WMDC 6.1
- I have uninstalled and reinstalled WMDC 6.1 a total of 7 times
- I have used every single USB port on my computer.
- I have restarted a total of 15 times, both the computer and hard resets of the phone.
- I have tried both the Unlocker (I'm not sure if I have to unlock a second time or not after my WM 6.1 update) and just the ROM Update.
- I have tried doing the forced bootloader mode (Power+Camera+Reset) and simply allowing the program to do it on it's own.
Everytime it drops into Bootloader (3 color) mode, it drops Activesync and then obviously errors out because of lost connection. I've tried simply running the program and never unplugging the USB cable, I've also tried unplugging the USB cable when the DOSprompt part of the batch tells me to. Everything I've read says to do this, but I don't remember doing this for the 6.1 WM Update. It also doesn't make sense.... if you unplug the device, it's going to drop activesync everytime....
I've just updated every program, reinstalled everything more then 5 times, done countless resets, tried every USB plug and nothing is working. Hopefully this is something easy I'm just overlooking -- or something easy like "It doesn't work with Vista 64" so I can at least get an answer.
Again, I apologize if this was answered somewhere previously. I genuinely tried for 3 hours using search, on and off XDA, so that I wouldn't have to post a question thread but never found a "fix" that worked.
Thanks in advance.
Traumatique said:
Alright I'm finally going to throw a post up, go ahead and get all your "use search" "it's on search" "it was in a thread" out of the way now, cause I've gone through 76 thread pages of reading and searches and I can't find an answer that works.
I am continually getting the ERROR 262 in RUU everytime I attempt to use it to flash.
- I am running Vista 64bit (not sure if that is the problem or not)
- Using WMDC 6.1
- I have uninstalled and reinstalled WMDC 6.1 a total of 7 times
- I have used every single USB port on my computer.
- I have restarted a total of 15 times, both the computer and hard resets of the phone.
- I have tried both the Unlocker (I'm not sure if I have to unlock a second time or not after my WM 6.1 update) and just the ROM Update.
- I have tried doing the forced bootloader mode (Power+Camera+Reset) and simply allowing the program to do it on it's own.
Everytime it drops into Bootloader (3 color) mode, it drops Activesync and then obviously errors out because of lost connection. I've tried simply running the program and never unplugging the USB cable, I've also tried unplugging the USB cable when the DOSprompt part of the batch tells me to. Everything I've read says to do this, but I don't remember doing this for the 6.1 WM Update. It also doesn't make sense.... if you unplug the device, it's going to drop activesync everytime....
I've just updated every program, reinstalled everything more then 5 times, done countless resets, tried every USB plug and nothing is working. Hopefully this is something easy I'm just overlooking -- or something easy like "It doesn't work with Vista 64" so I can at least get an answer.
Again, I apologize if this was answered somewhere previously. I genuinely tried for 3 hours using search, on and off XDA, so that I wouldn't have to post a question thread but never found a "fix" that worked.
Thanks in advance.
Click to expand...
Click to collapse
Try another computer. It does work with Vista 64 (I've done it many times), but there's no point in beating your head against the wall for this. There are so many things that it could be you might as well try another computer so that you at least now it is the computer and not your Vogue.
-GT
You phone is not unlocked and you are trying to flash a custom ROM.
Try following the instructions in this thread found about halfway down the first page of the forum.
http://forum.xda-developers.com/showthread.php?t=508544
atoz350 said:
You phone is not unlocked and you are trying to flash a custom ROM.
Try following the instructions in this thread found about halfway down the first page of the forum.
http://forum.xda-developers.com/showthread.php?t=508544
Click to expand...
Click to collapse
Be it locked or unlocked is beside the point. As I stated before, I unlocked it once for the WM 6.1 upgrade and being as I wasn't sure if I had to do it again, I attempted to do it again.
Regardless of if it's trying to flash the ROM, or use the Unlocker, the same thing always happens. Windows Mobile Device Center (ActiveSync) drops connection once the phone goes to the Bootloader (3 color screen), and it errors out 262 (Connection Lost).
I have attempted to give as much information as possible so I can get input on if I'm missing a step or if it's simple bugging out. I will try what gt! suggested and attempt this on a different computer. However, from the information I've given can anyone confirm that I'm at least doing the correct steps -- there's just some gremlin popping up keeping me from completing it?
Thanks again.
Flash via SD card. There are instructions in CodyBear's FAQ thread.
From experience...use a blank or backed up card.
Traumatique said:
Be it locked or unlocked is beside the point. As I stated before, I unlocked it once for the WM 6.1 upgrade and being as I wasn't sure if I had to do it again, I attempted to do it again.
Regardless of if it's trying to flash the ROM, or use the Unlocker, the same thing always happens. Windows Mobile Device Center (ActiveSync) drops connection once the phone goes to the Bootloader (3 color screen), and it errors out 262 (Connection Lost).
I have attempted to give as much information as possible so I can get input on if I'm missing a step or if it's simple bugging out. I will try what gt! suggested and attempt this on a different computer. However, from the information I've given can anyone confirm that I'm at least doing the correct steps -- there's just some gremlin popping up keeping me from completing it?
Thanks again.
Click to expand...
Click to collapse
CONNECTION DROPS BUT............ it should be installing new drivers.
When i flash my phone on windows 7 it loses connection when it enter bootloader just like you.
And by the time the drivers for the qualcomm chip on my htc touch vogue gets installed (this is the recognized driver when your phone is in bootloader)
the RUU rom updater/installer times out.
After it times out for me i make sure that the driver for the qualcomm chip (the driver that is seen by windows when your phone is in bootloader) is installed, i run the updater again.
Now it should run through smoothly again.
Alternate method:
Flash by ur sd card.
or
Try a different computer.
start it up on serial mode then plug it in to USB, go to device manager make it search for new devices. Driver should start loading and start RRU, if all else fails use the SD CARD for The Flash
Alright, well now I guess a second question looms. I was going to take everyones advice and attempt to flash with the MicroSD Card, but now I'm having problems with that one as well.
Yes it has to be 2GB or less and formatted FAT32
I always find my original 512MB works perfect for flashing from
as to how to get it to your card...
Extract the ROM you want to use
Find the largest *.NBH file and copy it to your desktop
at the desktop rename it to VOGUIMG.NBH (I believe the caps in naming is important)
Copy that file to the root of your formatted FAT32 2GB or less SD Card
enter bootloader mode and it should go from there.
Click to expand...
Click to collapse
Those are the directions on the FAQ. I have the original 512mb card, formated to FAT32. I went into the Unlocker RAR, found the Voguimg2.nbh, renamed it to VOGUIMG.NBH as instructed in the FAQ. Placed the file on the freshly formatted MicroSD Card, put it in the phone and went to bootloader mode and... nothing.
I attempted putting the card in, then going to Bootloader. I tried going to bootloader, then putting in the card. I tried putting it from USB to Serial and vica versa. Tried hitting all the buttons. Nothing happens, it just hangs out on the 3 Color Screen.
Am I missing something, or am I just cursed to not flash my phone more then once? Heh. Thanks again for all the help.
[EDIT] For clarification, since I don't know if I have to unlock before every flash or not, I'm just attempting to unlock it again and hense only using the Unlocker ROM. It was previously flashed for the 6.1 update, but I figured it couldn't hurt to try the unlocker again so that's been the ROM I've been trying to run currently.
Traumatique said:
Alright, well now I guess a second question looms. I was going to take everyones advice and attempt to flash with the MicroSD Card, but now I'm having problems with that one as well.
Those are the directions on the FAQ. I have the original 512mb card, formated to FAT32. I went into the Unlocker RAR, found the Voguimg2.nbh, renamed it to VOGUIMG.NBH as instructed in the FAQ. Placed the file on the freshly formatted MicroSD Card, put it in the phone and went to bootloader mode and... nothing.
I attempted putting the card in, then going to Bootloader. I tried going to bootloader, then putting in the card. I tried putting it from USB to Serial and vica versa. Tried hitting all the buttons. Nothing happens, it just hangs out on the 3 Color Screen.
Am I missing something, or am I just cursed to not flash my phone more then once? Heh. Thanks again for all the help.
[EDIT] For clarification, since I don't know if I have to unlock before every flash or not, I'm just attempting to unlock it again and hense only using the Unlocker ROM. It was previously flashed for the 6.1 update, but I figured it couldn't hurt to try the unlocker again so that's been the ROM I've been trying to run currently.
Click to expand...
Click to collapse
As explained in Cody's FAQ, once your phone is unlocked to flash, it stays unlocked. The only thing you MIGHT want to do other than just flash the new ROM is to flash a stock ROM, then the new ROM.
Go ahead and try putting the VOGUIMG.NBH from the ROM on the card and see what happens. From what I remember, you should have the card in the phone then put it into boot mode. I believe that was what I did for my first flash ever.
What method did you follow when you flashed to 6.1? Has anything changed about what you are doing now?
Also it might be important to know that when flashing via USB on a 64-bit machine the RUU program will give you an error about not working on a 64-bit computer. Just ignore the error and click ok, it will pop up a few times just keep hitting ok and it will work. That error pops up even though it's false.
when i first tried flashing a custom rom, i extracted the downloaded file and when i clicked on the ruu i had the same error... i then tried just running the downloaded file without extraction and it worked fine.
same thing happend 2 me Just run the RUU do not extract files!!!!!!!((-;
Barogi44, JFive1182 -- You are both princes among men.
The Unlocker will only run on the first auto-extract of the file. You cannot run the batch from the extraction folder afterwards, eventhough all it does is auto-extract the contents and then auto-run the batch file.
Out of curiosity... and being infuriated I went and tested this again just to see. On 3 other computers the same thing happened. I have no clue why it would bug out that way... or if it was written that way that's a pretty bad design.
In any case, someone should put that in the FAQ. You have to let it start the process from the auto-decompressing RAR, you can't start it again after the fact by running the batch file from the extracted folder. If it said this anywhere, the 3 guides I read never mentioned that (nore the unlocker's thread at ppcgeeks) so I didn't catch it.
Thanks again for everyone's input, and obviously JFive1182 & Barogi44 for actually letting me know how to make it work!
your welcome
Traumatique said:
[..]The Unlocker will only run on the first auto-extract of the file.
[...]someone should put that in the FAQ. You have to let it start the process from the auto-decompressing RAR, you can't start it again after the fact by running the batch file from the extracted folder. If it said this anywhere, the 3 guides I read never mentioned that (nore the unlocker's thread at ppcgeeks) so I didn't catch it.[..]
Click to expand...
Click to collapse
Bump for emphasis. I had the same problem.
Tutorial said this: "Use WinRAR and extract both the files into separate folders,"
ONLY extract the NFSFAN rar.
Related
Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.
Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)
Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.
Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?
Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing
try to flash your phone with some official rom and after that flash it with any other you want!
manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.
also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.
I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.
Bye,
the bottom of the sreen mast say "usb" not serial.
it seems there is a problem, if it states serial. as it should say usb. try THIS
Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?
WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.
if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!
Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?
ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh
racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.
woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**
Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.
hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..
I actually have a new phone coming today because I had no idea what to do and when I called neither did Verizon.
I seen the GPS fix thread, downloaded all the necessary files, ran the first unlocker (.40) and it errored half-way through the process, I figured big deal I'll just run it again..
Well, my USB would show on the phone screen but in the bootload mode the unlocker programs couldnt detect my phone at all and I couldn't get out of bootload mode whether I hit soft reset or took out the battery. So I decided to try going ahead an upgrading, I tried the next step on the list (sprint rom) but the upgrade would error as well, then I tried the verizon one, error, and the just tried jumping back to the NFSFan ROM and it didn't even begin to error it said it wasn't allowed or something.
Anyways, I had no idea what to do... took it in to the store, they looked at it for awhile then told me to call a number, I tried the number and they attempted to wipe it from their side and couldnt do anything so they told me they'd send another one being I was still in my 1-year warranty.
Is this how you brick a phone? Having an error during an unlocker/upgrade? Or could I have fixed this if I asked here before I sent for a new 1? I don't mind because I'm hype for a brand new phone, I just wonder if it can be fixed incase this ever happens again.
next time use coke 2.31
vin255764 said:
next time use coke 2.31
Click to expand...
Click to collapse
to do the gpsfix you have to use coke .40, its not like its some old outdated thing the thread is from august everybodys been using it, all i want to know is if theres no return once an error occurs in the middle of an unlocker?
j18yo said:
to do the gpsfix you have to use coke .40, its not like its some old outdated thing the thread is from august everybodys been using it, all i want to know is if theres no return once an error occurs in the middle of an unlocker?
Click to expand...
Click to collapse
There is a fix
what is showing on the bootloader screen for the unlocker?
Also you may want to reflash a shipped ROM. I have had this happen on both Titans and Vogues and reflashing from the bootloader screen always solves the problem.
I'm assuming you have to flash via the SD card right? Because I tried doing it through the USB and all the ROMs would error because the unlocker never fully finished, I mean before all this my phone was unlocked by the 2.31 and I had the newest NFSFan running I just decided to go back for the GPSFix..
The bootloader screen wasn't froze, it showed the usual..
Upper right corner says "RUUNBH"
Then to the left top it says..
VOGU100
SPL-0.36.0000
CPLD-3
and Serial at the bottom until I put the USB in and it turns to USB.. but it doesn't get picked up by the unlocker if I try to re-run it
I guess I answered my own question.. to fix it I'd have to run the unlocker again from the SD Card so it finish's without error since the USB won't pick up right?
My problem is I've never ran anything from the SD card.. if anyone can tell me how you go about loading up an unlocker or ROM from bootload on the SD I'd appreciate it, this way when I get my new phone if I run into a similar problem I can fix it
j18yo said:
I'm assuming you have to flash via the SD card right? Because I tried doing it through the USB and all the ROMs would error because the unlocker never fully finished, I mean before all this my phone was unlocked by the 2.31 and I had the newest NFSFan running I just decided to go back for the GPSFix..
The bootloader screen wasn't froze, it showed the usual..
Upper right corner says "RUUNBH"
Then to the left top it says..
VOGU100
SPL-0.36.0000
CPLD-3
and Serial at the bottom until I put the USB in and it turns to USB.. but it doesn't get picked up by the unlocker if I try to re-run it
Click to expand...
Click to collapse
Try installing this driver on your XP computer http://www.4shared.com/file/101893703/a59b72a/WindowsHTCdrivers.html if you have Vista let me know and I'll give you a link fvor that one. It should then allow you to communicate via USB. Also to answer your next question on flashing from the SD. It is simple you copy the NBH file from a ROM to Root directory of a FAT32 card 2 gb or less. Rename the file to VOGUIMG.nbh place the card into PPC and place into bootloader mode. Then follow the instructions.
j18yo said:
I guess I answered my own question.. to fix it I'd have to run the unlocker again from the SD Card so it finish's without error since the USB won't pick up right?
My problem is I've never ran anything from the SD card.. if anyone can tell me how you go about loading up an unlocker or ROM from bootload on the SD I'd appreciate it, this way when I get my new phone if I run into a similar problem I can fix it
Click to expand...
Click to collapse
All you do is put the .nbh file on the root directory of the memory card(use a newly formatted/clean card). It may delete anything else on the card while flashing.
I would take out the battery. Put in the SD card then turn the phone on. If, like you say, you are stuck in bootloader mode then it should start flashing as soon as it powers up.
Thanks everyone, I received my new phone this was mainly incase it happened again, but I also figured out why I ran into my problem..
During the unlocker I thought I knew the process being I'd done it multiple times, I skipped the part where I unplug the phone from USB and plug it back in so it's no longer connected with ActiveSync... thats why my unlocker error'd, so make sure you don't do that lol
What was messed up is my computers been acting like a piece of ****, it wouldnt even read my SD card so that I could put a file on it, but I don't think I'd wanna do it that way I have all my stuff on my SD card if it erased it I'd have been pissed..
ActiveSync does work, for awhile I thought the USB was only charging my phone because my new one wouldnt pick-up ActiveSync.. no idea why.. but if I plug it in and wait around 10 minutes it finally connects.
Hi all!!
Ever since I got my Sprint Vogue, I have spent God only knows how many hours looking for and gathering information regarding this phone (flashing instructions, unlocking, SuperCID, etc). There are a few sites that have fairly comprehensive guides as to how to do this, but there are very few posts in the Vogue Section here at XDA-Developers.
Having said that, I figured I would create my own "How to Flash Your Vogue"-Thread. This is a multi-step process and I cannot emphasize the importance of following every step down to the "T", that is unless you are looking for a silicone-skinned brick...
Who is this guide for?
*Anyone with a CDMA version of the Touch. [highlight]That means no GSM[/highlight]
*Noobs and Seniors alike.
*People who have trouble flashing their devices.
*Anyone looking for links to more information.
*Curious people in general.
*Anyone willing to get rid of the nasty stock rom and looking for a newer and cleaner OS (notice that I never said more stable, so do not blame me afterwards ).
[highlight]Please keep in mind that there is always a chance of bricking your device with these procedures. I will not be in any way, shape, or form responsible if you damage your device while doing this.[/highlight]
Got your coffee? Alright, let's do this.
Step 1. Preparing the device
As with every phone, you have to make sure that you have the following things done before flashing:
* Battery charged at least 50%.
* All the necessary programs (see next post).
* Instructions handy.
Make sure that you back up all your information (contacts, e-mails, files).... essentially, anything that you would like to keep post-flashing. You can do this via Active Sync/Mobile Device Center or via third party software (PIM Backup is really good)...
You will have to reinstall every last piece of software in your device as it will be hard reset. Some programs may work if installed in a SD card directly, but a lot of them write things to the registry and copy files to the device, which they require to run. Long story short, keep all your cabs and exe files in a safe place so you can restore later if needed.
Step 2. Unlocking the Device (HardSPL)
Unlocking the device is done so that you can flash custom roms in your devices. The unlocker that you are about to download and use was provided by "ImCoKeMaN" at PPCGeeks. If you are interested in the full thread, please click here.
If you have read the above link, you will see two versions of the HardSPL (0.40 and 2.31). Simply use 2.31 as it works fine with most devices.
[highlight]To use this under Windows XP,[/highlight]
1. Connect your device to your computer and make sure it is synced with ActiveSync.
2. Download and extract the contents of the zip file, which is an exe. Let it run to completion. You will be prompted to disconnect and reconnect your device at one point in the process. Do it... don't worry
3. It will look like it is flashing a rom via a RUU. Do not disconnect the device after it is done!!!!!
4. Once it is done flashing, you will see a prompt that says that it will run exitbl. DO NOT DISCONNECT YOUR DEVICE. At this point, open ActiveSync, go to File>Connection Settings> Uncheck "Allow USB Connections". Continue following the on screen instructions and let it finish.
5. Go to bootloader once more to verify that it worked. You should see 2.31 CoKe MFG.
[highlight]To use this under Windows Vista/7 x64 (thanks jitajt),[/highlight]
jitajt said:
connect your device to WMDC (it's not necessary to set up device, just connect without setting up device)
then right click on the 2.31 unlocker and run as administrator
follow the directions, you will get an error about sleep.exe not being compatible with x64 but just hit ok and continue, (you will get about 10 of them)
then just keep following the directions in the command prompt and it will put your phone into bootloader then you have to disconnect and reconnect when it tells you to. and it will flash your phone and reset it. then your done you can close the command prompt and disconnect your phone.
I did it just like above and I have not had any problems.
Do this at your own risk as I am not responsible for your phone
Click to expand...
Click to collapse
Step 3. Flashing your Roms
The time has finally arrived. You sat down patiently through the unlocker and you are now ready to take the leap of faith into what you believe will bring your device to a new level of usefulness (also known as getting rid of that nasty, bloated, stock rom )
The process is relatively simple:
1. Download the RUU package from this post. I am only posting this because some cooks only post the rom nbh files rather than the whole package.
2. Go into the threads and look for whichever rom you prefer. Look at my signature to learn which one I am using. NFSFan (my current one) is by far the best one I have tried so far. You can download it from here
3. Put your device in bootloader mode and connect the device to the computer. [highlight]Once in bootloader, activesync will NOT see the device. If the RUU gives a connection error, try to run it with the devices in regular mode (with ActiveSync connected)[/highlight]
4. Open the Romupdateutility.exe and follow the steps.
5. Once it is done flashing the rom, disconnect it from the computer and hard reset it. To do this, simply hold "Send" + "End Call" +Stylus in the reset hole for about 3 seconds. It will prompt you to erase all the data and restore to factory defaults. Press "Enter", which is the center button in the directional pad. Once it is done, press "Send" to reboot.
Congratulations, you just flashed your first rom for Vogue
Step 4. SuperCID
This step can be skipped if you are not thinking of doing anything as far as your radio (such as flashing radios other than the ones intended for Vogue). This is also used to do other things such as modifying certain important things on your device such as the NV files, which is information that will not be discussed here. However, if you are interested in finding out more, simply google it, there is a ton of information out there.
Anyways, back to SuperCID... here is the procedure (thanks to hpnasik at mobile-files.com for the post)
1. Download the following special rom . This is an Alltel rom with radio 3.37. This was specially prepared to be able to reduce the Security Level of the device to level zero.
2. Download mtty since you will need it. Do not worry if you do not how to use it. You will have a step by step in this guide.
3. Flash the Alltel rom from above.
Now comes the fun part...
4. Disable USB in Connection Settings of Active Sync
5. Boot The Phone holding power button and camera button to enter bootloader.
6. Phone Will Display Serial in Bottom
7. Connect Phone to PC
8. Phone should Display USB instead of Serial in Bottom
9. start mtty.exe
10. Select All Default and Connect to USB in drop down box and Shoot the Following Commands (All Commands are case Sensitive)
11. run command rtask a : After this Command Phone will not Display any thing
12. run command echo_on : even though nothing is shown to screen
13. run command readCID : in Sprint it will display SPCS_001
14. run command writeCID 00000000 : Set CID Value to 00000000 replaces SPCS_001 in Sprint (This make PPC Radio Security Level to Zero)
15. run command readCID : This will Display the Update CID as 00000000
16. run Command retuoR : This will return to Original Boot Loader State
Congratulations, you just SuperCIDed your device. Original thread with the instructions can be found here if you are interested.
Step 5. Flashing your radio.
Now that your device has been SuperCIDed, you will have the opportunity to flash radios that have been ported to this device (ie. there is a version of the 3.42.40 radio for the Titan, which has been ported to the Vogue). There are two ways of doing this:
Way 1: Do it by flashing via RUU (same as with flashing a rom)
Way 2: Flash via microSD card. Simply put whichever radio that you wish to flash in the root of a 2GB or less microSD card formatted to fat32. Rename the radio to VOGUIMG.NBH and put your device in bootloader. The flashing will start by itself.
Way 3 (I know I said two ways...): There are a few stock roms that come with new radios. One of them can be downloaded directly from HTC and it is for the Sprint Touch. This one comes with Radio 3.42.30
The other one is for Bell Mobility and this one comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options seem much easier?? I have run into the problem where my device would not let me flash other radios than the one that I had. SD card method did not work and the RUU started out fine but quits at 8% rebooting my phone and displaying Error 328 in the RUU on the PC. Anyway, here are the links...
Sprint rom with radio 3.42.30
Bell rom with radio 3.42.50
Verizon Stock Rom
All Shipped Roms (All Carriers) - Thanks conflipper!
All Above Radios zipped
The newer radios perform a little better and give out better GPS signal (faster locks)....
Hang on a sec... did you just say GPS?!?!? But my Vogue does not have a GPS.... It does, just read a little further and be happy
Step 6. Enabling GPS, Returning to Stock, and Carrier Cabs
As I said before, there is a GPS hidden on your device. Now, if you are like me and went straight to the specs of the phone to confirm, you will probably try to call BS on this. Long story short, there are a few custom roms which have this "tweak" already implemented (like the one I am using from NFSFan). If you require some more info, I will post it later...
[highlight]Location must be on or else your GPS will not work. To activate it, go to Settings>Personal>Phone and change the Location setting to ON instead of 911 (thanks for pointing it out, th3lolz)[/highlight]
[highlight]For Verizon Users[/highlight]
br125 said:
For those of you with the official mr1 update from verizon that cannot get their gps working:
My xv6900 came with the official update and I got it working, it involves downgrading to a NON-GPS radio, then back to a gps radio...
go here: http://forum.xda-developers.com/showthread.php?t=533639
now the instructions are going to imply that you must load the unlocker before each flash... bs don't worry about that
1. flash the .40 unlocker
2. flash the non-gps rom (reset before customization)
3. flash the 2.31 unlocker
4. flash the vzw rom (reset before customization)
5. flash any custom rom or android rom
that's it, time consuming, but it works
*ignore the multiple flashing instructions, its completely unnecessary, I've never flashed more than once with no problem ever....
I also suggest keeping the vzw radio, but do as you will, I like the 3.37.38 radio.. ain't broke don't fix it
lastly, just make sure you RESET BEFORE THE CUSTOMIZATIONS RUN...... that is what locks your gps.
good luck!
ps. the verizon radio rom that is in that post is for the "leaked" 3.37.37 radio, I reccomend using the official update from verizon here for the 3.37.38 radio rom instead:
http://www.pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon Wireless
RESET BEFORE CUSTOMIZATIONS
Click to expand...
Click to collapse
[highlight]How to Relock you phone[/highlight]
If, for whatever reason you need to return your phone for repair/replacement, you will need to relock it. To relock your phone, simply run the unlocker 0.40 and flash the stock rom of your carrier.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
[highlight]Carrier Cabs[/highlight]
Thanks to Codybear for gathering all of the cabs with settings for various carriers. But since the link went down, here is another one courtesy of LMiller1708
https://sites.google.com/site/vogueroms/vogue-files
This information was only gathered by me and I take no credit whatsoever other than trying to put it in a one stop thread. Thanks to the following people
Shadowmite
ImCoKeMaN
mindfrost
NFSFAN
Codybear
joshkoss
and a bunch of people that were involved in developing all this...
Thread sticky'd as requested
Peace,
Josh
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
dwigginstm said:
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
Click to expand...
Click to collapse
How exciting!! My first victi...erh patient
Did you put the device in bootloader mode? If you did and it is connected to the PC, you should see USB on the screen of your device. Also, do you have ActiveSync on your XP machine? You will need it for the drivers on this step. Changing USB ports sometimes help as well. And one last thing, do not use a USB hub, go directly through the USB ports in your computer. Good luck!
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
yes i have activesync set up with the phone and pc, but when i put the phone in bootloader mode and connect it the pc recognizes it but not activesync. is there another program i can unlock the phone with?
dwigginstm said:
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
Click to expand...
Click to collapse
Do not worry about ActiveSync. While you are in bootloader, the device is not running WM, which is why your computer only sees it as a USB device. This is perfectly fine. ActiveSync will not recognize it.
Please, follow the instructions in my post for unlocking. Read it thoroughly and try to understand it, else you will end up bricking your device.
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
dwigginstm said:
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
Click to expand...
Click to collapse
that is a message in the RUU. do not pay attention to it. good luck...
so i finally got the unlocker to start and it begins the ten minute process and stops then show a 262 error code ive done this over and over again
Let's go from the top. I just saw the message that you were talking about. The unlocker does ask for ActiveSync as you pointed out and it is asking you to connect the device to the computer. Then it asks for you to press any key when that is done. So, try that and you should see the word "initializing" with a dotted line getting longer for about 20 seconds. Do that.
The RUU will start up afterwards. The prompt will tell you that it is going to flash a new SPL, and if I am not mistaken that is where you are getting stuck.
Just out of curiosity, which version of the Vogue do you have? (Alltel, Bell, Verizon, Sprint, US Cellular)?
no internet
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
terrancextc said:
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
Click to expand...
Click to collapse
You downloaded a cab. Simply put it in your SD card and run it by tapping on it. Don't unzip it...
Unlocker is not 64 bit compatible... grrr....
Helo dear friends.
Well I just wanted to get some Hebrew in my Hero.
I have the Orange hero in Spain. Upgraded to official rom - 2.73.61.5, worked fine.
Now i am trying to downgrade it, so i can root it, so i can add all the fun stuff (including hebrew).
Did the gold card, since i understood that this hero is CID locked. (and maybe i am wrong). Then failed few times with error 140 when tried the 1.76.405.6 and 1.76.405.1 rom downloads. Then tried to downgrade to 2.73.405.5 rom as someone suggested here... and the process started happily, downloaded Splash1 ok, system ok, userdata ok, boot ok, bootloader ok, then GOT STUCK ON "Radio-V2 - updating" (at about 85%.. froze!)
(I attached a picture).
This happened few times, sometimes never even started to download, was just froze at the beginning of the process with: "zip header checking..."
So every-time this happened i had to disconnect it, pull the battery out or something, and try again. (I also found out that for some-reason things moved forward when restarting windows which by the way, works on parallels, mac ...)
Now the hero is stuck on the white error screen i guess, pictures attached.
Mmmm... hope someone can suggest something... straight and to the point, i feel i am going circles will appreciate allot.
Thanks in advance
Cheers!
First off ... KEEP THE PHONE PLUGGED IN! (So the battery doesn't die... If i remember right... fastboot chews through battery)
Next.. how long has it been stuck?
Well, first time for 30 minutes of no movement, then at the rest of the attempts i kept losing my patient each 20-30 minutes... in a process that might take 10?
yeah the battery ran out once..
thanks.
Trying again, now it's stuck on "system - updating". 20 minutes.
Please help.. someone?
Should i try another rom? any suggestion for Orange Spain?
Someone experienced problems via Parallels ?
Parallels as in your trying this from a VM? I would bet thats your problem! While it techincally shouldn't make a difference... I would try with real PC!
yes, virtual machine...
Ok, and that PC, should it have all the drivers for the phone? i mean now that the hero is stuck, would a different computer recognize it?
I should just download the rom to the computer and try to install it?
thanks.
You'll want to install the USB drivers (The HTC Sync download from htc.com likely has these included...)
If the VM still see's it - any PC with the drivers installed correctly will see it.
If you get the the custom recovery image flahed, you'll be able to do everything from your mac after that...
ho really? can you elaborate a bit on that? start with: " custom recovery image flahed"
Thanks.
Details @ http://forum.xda-developers.com/showthread.php?t=561124
Thanks. and this i do after i downgrade successfully the rom (with lets say a proper PC?) ?
Do i need to root after downgrading?
As far as I remember - Yes - you will need to root the phone, then:
adb remount
adb shell rm /system/recovery.img (If this fails with file not found dont worry about it)
I seem to remember needing those when I rooted my hero ...
Thanks kiall, resolved it at the end, without downgrade, no PC, just pushed the Recovery to the formatted sdcard, flashed it and the modaco rom and then radio and hebrew fonts, all is ok now...
Thanks for you time.
Hello everyone, it's me again...
Please read this first, as it is the reason why I started MTTY. http://forum.xda-developers.com/showthread.php?p=10487426#post10487426
I used this guide to MTTY http://forum.xda-developers.com/showthread.php?t=540290
I did exactly as described in the guide, exept for the "Remove Watermark" thing, as it is for windows x65 and x84. I have a 32 bit system.
I used the Energy.DIAMOND.28244.Sense2.5.Cookie.2.0.Dec.21.7z ROM
I used the "flash from internal storage" method. Again, I did exactly as the guide described. I did change the ROM name to what is described in the guide, and when i did that, my pc warned me if i changed that which was after the .xxx , the program couldnt work properly anymore. I continued anyway because I was pretty sure it would work. I changed the name to DIAMIMG.nbh
Maybe that's what's wrong?
I used the MTTY program, and selected USB.
I typed: set 14 0
I typed: task 29
In the guide, only one file failed to be erased. I had four un-erased blocks.
I typed: task 8
I immediatley disconnected my device and held vol down and back for over 2 minutes. The startup screen came, which displayed TouchDiamond as normal, but this screen stays there forever, no matter what I do.
The only thing I can do is enter bootloader. Then, when i hook my device up to my computer, "serial" changes to "usb". When i check control panel--> device manager, I can see my device is hooked up. When i disconnect, it isn't there anymore. That means my pc still recognizes my htc.
Is there any way to fix this? Was it a wrong ROM version? Was it a Wrong HardSPL version? Please help me.
I've made a backup before I even started with the Hard SPL, but i'm not sure if thats the ROM, or the settings and some files on my internal storage. It's about 30-60 MB.
Please help me.
Also, I have downloaded the original rom from htc, but i'm not sure how to flash this, as activesync doesn't recognize my HTC device.
Again, please help me. There has to be a way.
Thanks in advance
connect ur diamond to pc and flash from PC
btw u can still get ur original rom from htc netherland site....use ur serial number in ur device
I downloaded the rom from the htc site. i just flashed it and it works.
Now how to flash the energy rom? im still not sure which method to use, because it's now working like the htc one. it's a .z7 file. The htc rom was just double clicking and following the instructions. It may sound stupid, but i dont want it to happen again
Happy it's working again tho.
glad ur device is working again. and dont worry if it happens again. becoz you can bring it back with htc rom always.
if i may suggest, how about you try a non-energy rom jus to kick in the confidence in you.
try another custom rom....then you can be sure if its really ur device or the energy rom file that is corrupt.
some users hav had issues with their energy rom files downladed being corrupt
Arthedes said:
I downloaded the rom from the htc site. i just flashed it and it works.
Now how to flash the energy rom? im still not sure which method to use, because it's now working like the htc one. it's a .z7 file. The htc rom was just double clicking and following the instructions. It may sound stupid, but i dont want it to happen again
Happy it's working again tho.
Click to expand...
Click to collapse
Hi there...
File with z7, it's compressed file. You need to extract it first to a new folder. Then you can try to flash again.
Hello again.
I did notice when i first downloaded the energy rom that it was a 7z file. But when i tried to unzip it, there was no such option in the drop down menu. This is my mums pc, so I think it's not installed on this pc.
I'll try to unzip it today after school.
If it doesn't work then, I'll try to flash a few other roms, just to be sure.
I'll keep you updated. Thanks for the fast replies tho^^
It's working! I just used 7Zip and ran the RUU included with the ROM. Ill try several as maxsence 2.5 is a bit sluggish, ive tried two, but the 23699 build doesn't have cookie 2.0
Really happy and thanks for the replies, guys(or gals)
see...i told you so...this is called the "CROSS CHECKING"....
now do you (or everyone else) believe me when i say there are some energy rom files that are corrupt or refuse to flash to diamond.
no, it was not corrupt, I was just so stupid not to unzip it first, that's all.
There may be some files that are corrupt, but i haven't witnessed one.
Now i know how to, i'm one die-hard flashin' mother******
TY^^
Arthedes said:
no, it was not corrupt, I was just so stupid not to unzip it first, that's all.
There may be some files that are corrupt, but i haven't witnessed one.
Now i know how to, i'm one die-hard flashin' mother******
TY^^
Click to expand...
Click to collapse
thank God if you're aware of your shortcomings...
I'm proud of people who really gentleman