Related
Hi all,
I need to know if someone can help me to bring to life again my lovely JasJam,that was working great until this morning.
The problem is this one:
I was going outside the country this morning (I am in Czech rep. now and I went to Slovakia) and on the way back I realize that my hermes (herm100,spl2.10 olipro,RADIO 1.57,schaps 3.54bITA) was without any signal. I tried an other SIM card and the result was the same.
Once at home, I tried to reinstall schaps,everything was ok,except the signal still missing.At this point,I tried to reinstall the Radio and the bar was still at 0% and after 3 minutes it gave me error 262 and now is with the screen always on (illuminated) on the KITL page and it doesn't start anymore...
please,someone with a good heart,help me.
http://forum.xda-developers.com/showthread.php?t=286755
back a live any hermes ( that's as worked whith my hems)
I don't know that's work but try install any official rom from HTC that's have radio information and then you can install any other. but extrat the signedruu. (that's the rom file) and then put the file into a sd card start your herm by pressing simultaneous the power, and ok button and prissing the reset hole whith the stylus pen and follow the steps it's very easy.
thank you Zefo,
but I am Stuck on the bootloader page, I cannot insert a original Rom because ActiveSync doesn't recognize the phone.
Being in the Bootloader page is fine. Just run the RUU Wrapper, it will connect.
What caused the problem? I am a little worried as I am going to Tenerife on Friday and I am running Radio 1.54.07.00 as well (I assume thats what you meant when you said 1.57)...
Is there any reports of going abroad messing up your phone when its been modified with new radio/rom?
Hi Allan,
I would like to run RUU,but ActiveSync doesn't connect my phone,so when I launch it,they don't communicate. The computer see the device,but ActiveSync not, infact, If I try it,Itgive me error 260 Update Error (I used Hard SPL v7)
Stick what you need to flash on a MicroSD card and stick it in the phone, you should be able to boot off of that.
Theres instructions somewhere in the forum on it all.
I got the axact parameters of yours Hermes, STARFURY, it changes only the rom (mine is/was schaps 3.54b).
I am not able to find what you suggest me but I cannot go on the SD if the phone doesn't turn on the OS...How can I do?
Get a usb cardreader plug your microsd card into an sd card adaptor, then plug that into the cardreader and the cardreader into hte PC. Transfer the stuff onto the microsd card and stick it in the phone,.
but I have just to put the 2 files RUU Wrapper (Bootloader) on it in the main root??and how can I make them start?
I was able to go into the OS but I am still with no GSM and if I try to update it,it stops at 12% also with original ROM.
Can anyone give me a link where can I see where the radio chip is located on the mainboard please?
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..
Hi
I have a HTC Cruise(Polaris), I tried a view roms from the Polaris section, but I prefered goig back to my old rom. So when I tried to flash the Dutch Dumped Rom I got stuck at 15% I rebooted the pda. So now all I see are tree colors.
When I try to upgrade the phone to the WWE release version I get: "error 294 invalid vender ID". After it hits 1%.
- How can I CID unlock this phone?
- Joe
With Polaris_WWE_B_20273_1_3_3_V09_Lt_Swtos I get a ERROR [262] : UPDATE ERROR. Even when I retry. Also with the RUU_Polaris_HTC_NLD_SEA_1.28.404.2_radio_sign_25.69.30.05H_1.58.25.14_Ship
anyone can help me out?
Extract the RUU_Signed.nbh file from the downloaded ROM and try flashing from a microSD card. Directions can be found on the boards.
Extract the RUU_Signed.nbh file from the downloaded ROM and try flashing from a microSD card. Directions can be found on the boards.
Click to expand...
Click to collapse
i renamed the RUU_Signed.nbh and pushed down the camera button and rebooted, but doesn't work. Could you shed some light on this?
I have a completely different suggestion. Have you tried a hard reset BEFORE you attempt the burn?
I do not know or have experience of your hardware. I have burned new ROMs on two other makes of PDA and experienced the same problem. A hard reset or return to factory state works.
I have concluded that a burn often fails because the new image does not have enough memory space on the PDA to load the new ROM image and the small program that executes the burn. If you don't go back to the "factory state" by removing all your own installed programs and data first, then there may be insufficient memory to complete the burn. Precisely where it fails in the burn depends upon how much spare memory is available, so in other cases it will fail at a different percentage of the burn.
Worth a try?
solved it with mtty
Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Same Thing happened to me :S wtf??
xevier69 said:
Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Click to expand...
Click to collapse
Hi have you tried to flash from the internal storage?
Have you tried flashing with internal storage method?
Exactly the same problem here, so I tried to flash to a really old original HTC ROM after the failure and it flashed fine
So I thought I would try upgrading over the top of an original ROM, had the same error , bloody HTC
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Though I bricked my phone when it happened, never seen that error before despite many ROM flashes
I have now tried tommytaos ROM which is supposed to be very close to the original but some with some tweaks.
http://forum.xda-developers.com/showthread.php?t=479049
It installed just fine on my phone. Seems HTC have broken their ROM
xevier69 said:
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Click to expand...
Click to collapse
it's the best way to flash the rom and the safest...
From Suiller thread:
the standard procedure to cook a ROM is made trough activesync program, I mean that the .nbh file is pushed into the phone trough activesync, across the usb cable, but this procedure can give some troubles:
1. it takes long time, about 10 minutes
2. it's a bit unsafe (even if the procedure can be always restored safely)
3. it's possible only with Windows OS (NO Linux nor *BSD, et cetera...)
I don't know why this is not well known but ALL producers (like HTC) give the possibility to upgrade the rom/firmware without having MS windows (thanks GOD someone knows that there aren't only windows users).
This faster procedure can be done also with *nix variants (or whatever you use) because the ROM update is made directly by the phone.
The procedure is very simple, it will take just 2 minutes, can be done everywhere & is good for cooking radios too (very fast in this case)
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
notes:
* be sure to have at least 10/20% of charge, anyway the whole procedure will take about 2 minutes, so you must be ensure that your mobile will stay turned on for at least those 2 dirty minutes (just in case you can attach the power AC/DC too), don't panic if something goes wrong... read few lines below
* like told you above the same procedure is good for cooking Radio too, of course Radio are smaller and it will be really fast (about one minute!)
* you don't need windows anymore or activesync, is enough just to copy the file into the storage card (transfers WITHOUT activesync are faster)
* it's possible to make a reset simply by getting off the stylus and pressing the small red button under the stylus carrier
* don't worry if something goes wrong... any cook failure can be always restored, the important thing is that you don't fail hardspl flash... but you have to do it just one time in your life
special note about hard-spl:
if you have signed-only hard-spl I strongly suggest to upgrade to an un-signed one, personally I tested many & I can confirm that the "good ones", at least in my experience, are the Olinex 1.37 or 1.93, you can find a copy here
remember also that you can NOT brick your device if you have a good hard-spl (like the ones I mentioned above) & flashing directly from phone is really faster (also good for flashing radio)
so the only one thing you should take care is when you change/upgrade the hard-spl, but you have to do this step just once, I'm using this hard-spl from about 6 months & I was able to flash everything (plus dozen recovers for failed flash)
for rom/radio upgrades you can safely also reboot/remove cable/turn off your phone while flashing ...every lost flash can be always restored safely, it's enough to restart your device in boot mode & restart flashing, also with cable trough the classic RUU (to put device in boot mode simply reset & keep pressed Vol_Down button)
In the hope this procedure can be useful at least to save time
if you have the official rom which is a exe file you can extract the rom file using winrar.
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Flashing using the Internal Method is the safest and most convenient way to flash. Spread the word.......
xevier69, Thanks for your thread
Having just purchased Oli's security unlocker... I was annoyed about this problem with a HTC official rom!
But your method has solved this issue!
Thanks again
Thanks guys it works perfect!
This just happened to me too and the only roms i have ever flashed:
1.37 official spanish: came with the phone
1.37 official WWE
1.93 official WWE
and now 2.03 official WWE fails.
WTF... One would expect the upgrade not to fail, right?
I wonder if they are checking for HardSPL to be original too!?
Anyway thanks for the workaround
This worked for me to
Cheers
xevier69 said:
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Click to expand...
Click to collapse
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Cheers
Hi!
The same thing happend to me too... I think it's because of the serial number we have entered when we have downloaded that 100 MB ROM Update file from the HTC support site... well i think it doesn't match with the serial and IMEI of the phone that the upgraded rom checks at the end of the update process... so i think it's kind of a protection against piracy developed by htc... taiwanese idiots!
Hi!
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
miriamscorob said:
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
Click to expand...
Click to collapse
read all posts please
works like a charm folks! thank you!
g0x said:
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Click to expand...
Click to collapse
I made this too for testing First flash: Error, Second time: Ok
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.