Related
Hi All
Have a problem with my latest phone. A so called friend told me to upgarde the ROM so as to remove all the T Mobile poop in it. So he gave me the software I started the upgrade all went well stage 1 then stage 2 and finally stage 3. It said Congrats just hit reset and the power button at the same time and its done. Easy Me thought..... Not Easy....... Its now just booting up and screaming at me. The screen wont lite up and nothing else. I have tries to reset over 10 times now.....Anyone got any ideas, have I shot and killed my new phone...
Ta JG
this is not good. do you know which phone you are having? MDA is all the phoen from t-mobile. First identify your phone. Then, you need to know if you are using the right ROM on the right phone. THEN, you have to know are you using the right phone ROM on the phone (eg G3 or G4).
Its an MDA Copmact 11 does that help....
common.. more info. which rom you've used?
Alpine_Ext-1.11.162_Radio-1.04_stuffstripped_Camera_Fixed.
SORRY i AM NEW TO THIS AND i AINT GOT A CLUE WHAT i AM DOIN...HE HE HE
Oh forgot to mention it all went in ok, stage 1, 2, 3 and even told me on my computer it had worked. It was when I tried the power and reset that it all came tumbling down........
JeanGenie said:
Oh forgot to mention it all went in ok, stage 1, 2, 3 and even told me on my computer it had worked. It was when I tried the power and reset that it all came tumbling down........
Click to expand...
Click to collapse
All I would like to do is get the old stuff back then worry about an upgarde later can this be done without me having to do unspeakable things to the phone????
You've just flashed your Charmer phone with an Alpine ROM. If that doesn't kill your phone, I'm not sure what will.
Ok, try this. Hold down all 3 buttons -> power, camera, record buttons, and poke the reset. See if you can get a 3 colours screen.
If you get that, close active sync (stop the process WCESCOMM.EXE), connect your phone to your PC (when it is displaying the 3 colour screen). Then you ought to be able to run the ROM update file (EXE) from t-mobile (check the Charmer Wiki) and that may fix your problem.
hanmin said:
You've just flashed your Charmer phone with an Alpine ROM. If that doesn't kill your phone, I'm not sure what will.
Ok, try this. Hold down all 3 buttons -> power, camera, record buttons, and poke the reset. See if you can get a 3 colours screen.
If you get that, close active sync (stop the process WCESCOMM.EXE), connect your phone to your PC (when it is displaying the 3 colour screen). Then you ought to be able to run the ROM update file (EXE) from t-mobile (check the Charmer Wiki) and that may fix your problem.
Click to expand...
Click to collapse
I have done what you have said, I think...DUHHHH the screen has not lit up but its now showing USB in the top and V1.02 in th ebottem. I have connected it to my computer but active sync has not cut in yet....... I assume I have done it wrong....
hey
you DONT want activesync to cut in
put it in that 'usb mode' that you managed to get and just run the OFFICIAL T-Mobile rom update utility, but make sure to kill the wcesscomm process in windows' task manager.
good luck!
duke_stix said:
hey
you DONT want activesync to cut in
put it in that 'usb mode' that you managed to get and just run the OFFICIAL T-Mobile rom update utility, but make sure to kill the wcesscomm process in windows' task manager.
good luck!
Click to expand...
Click to collapse
I have just downloaded the t-mobile update as below
RUU_Compact ll_2060227_20602110_021921_T-MobileUK_Ship
I have switched off the file as you have said in the task manager. The update laods then says cannot find MDA Device connection error 274.
Could a system restart help?????
Sorry for all this, maybe stick to things I do know in the future, like washing my car.......
hey
get your phone back into that screen which had 'usb' written on it.
then do this:
download and install a program called 'winrar', you've probably heard of it and in all likelihood already have it!
once its installed, right click that t-mobile update you just download and select the 'extract to.../' option that will come up in the drop down menu, let it extract to the folder it does, open the folder in there will be a few files: you want the file which is called something along the lines of 'upgrateUT' or RUU Upgrade UT, it'll be an exe,
connect your phone up to the computer (with it in the USB mode and activesync disabled) and run that exe, it should go through as normal
good luck
(if you want any help just post back! best bet is for you to extract the files and report back with the name of the files in the folder!)
duke: I think he did that. He downloaded the EXE from http://www.tm-phonedownloads.com/download_manager_mda_com2.html
and it seems not able to detect his Charmer.
JeanGenie: Just to make sure, when you run that EXE, you have the phone connected with it displaying USB?
duke_stix said:
hey
get your phone back into that screen which had 'usb' written on it.
then do this:
download and install a program called 'winrar', you've probably heard of it and in all likelihood already have it!
once its installed, right click that t-mobile update you just download and select the 'extract to.../' option that will come up in the drop down menu, let it extract to the folder it does, open the folder in there will be a few files: you want the file which is called something along the lines of 'upgrateUT' or RUU Upgrade UT, it'll be an exe,
connect your phone up to the computer (with it in the USB mode and activesync disabled) and run that exe, it should go through as normal
good luck
(if you want any help just post back! best bet is for you to extract the files and report back with the name of the files in the folder!)
Click to expand...
Click to collapse
okie dokie...have extracted all th efiles and these are what I have got in a seperate folder
EnterBootloader
nk.nbf
README
ROMUpdateUtility
RUUGetInfo
RUUResource.dll
Thats all the files inside the folder
is "ROMUpdateUtility" an EXE file? try running that.
hanmin said:
is "ROMUpdateUtility" an EXE file? try running that.
Click to expand...
Click to collapse
I have and after a few seconds it says error 274 cannot find device....!!!!
well, it is amazing that you can go into the bootloader at all. I'm suspecting that the bootloader is not the Chamer bootloader, hence the ROM update EXE is not able to find it. Where did you download the Alpine ROM. Give exact link.
UPDATE: Look at the post here
http://forum.xda-developers.com/showthread.php?t=269329&highlight=
by 'windowsceportal'. He is able to flash the phone with 'Prophet RUU 2.5.2 noID check' with the DLL RUUResource.dll of Charmer RUU. I'm not very certain, but the noIdCheck may able to help.
UPDATE: As according to this post
http://forum.xda-developers.com/showthread.php?t=280128&highlight=
the bootloader mode that you are having is that of an Alpine (Charmer's bootloader mode is a screen with 3 colours). So, probably the updating program doesn't work. However, as an idea, you may want to try getting alpine upgrading EXE files to load Charmer ROM into the phone. It is an idea, not sure how can this be achieved.
hanmin said:
well, it is amazing that you can go into the bootloader at all. I'm suspecting that the bootloader is not the Chamer bootloader, hence the ROM update EXE is not able to find it. Where did you download the Alpine ROM. Give exact link.
UPDATE: Look at the post here
http://forum.xda-developers.com/showthread.php?t=269329&highlight=
by 'windowsceportal'. He is able to flash the phone with 'Prophet RUU 2.5.2 noID check' with the DLL RUUResource.dll of Charmer RUU. I'm not very certain, but the noIdCheck may able to help.
UPDATE: As according to this post
http://forum.xda-developers.com/showthread.php?t=280128&highlight=
the bootloader mode that you are having is that of an Alpine (Charmer's bootloader mode is a screen with 3 colours). So, probably the updating program doesn't work. However, as an idea, you may want to try getting alpine upgrading EXE files to load Charmer ROM into the phone. It is an idea, not sure how can this be achieved.
Click to expand...
Click to collapse
This is the link i used to get the original upgrade
ftp://xda:[email protected]_Radio-1.04_O2stuffstripped_Camera_Fixed.rar
Does that help any...
JeanGenie said:
This is the link i used to get the original upgrade
ftp://xda:[email protected]_Radio-1.04_O2stuffstripped_Camera_Fixed.rar
Does that help any...
Click to expand...
Click to collapse
Is there anyway of just deleting the Alpine ROM and reinstalling the correct charmer. I, as you have probably guessed aint got a clue what I am doing never lone saying...he he he
Just a thought.......
Plus my new XDA IIi was delieverd today am I being silly when I say I have been told that I can debrand it with the Alpine rom as listed above, dont want to try anything incase this phone goes belly up also....
Hellllppppp...........
Its me again, can anyone make any other suggestions to my problem please. I have tried in vain to do what has been already suggested but it seems either it wont work or more to the point I have no clue as to what I am doing.
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'm running Vista and when I wanted to run the bootloader upgrade on my Dash I kept getting this message error. Error 260. anybody find any way around it? I've tried to manually set th ephone into bootloader mode, same result. help!! PS the error is supposed to mean "port already open" or "open port error" I'd really appreciate any help!
erro 260 - fixed
switches to my wife's laptop that had XP on and it worked like a charm. I'd be glad to assist anybody in the process od de-branding their Dash. Removing the ugly T-mobile paint logo on the unit was easy too.
ERROR 260
Sorry for thislong story....
OK, I've been on looking around the site for a while. I installed the WM6 Beta. I was looking for two days for the WM5 ROM only because I want the little things to work. Finally found it. But now every time I try to flash my phone ack to WM5 bI keep getting the 260 connection error. The readme only says to restart the comp and phone and try again. I have literally, no joke, done this 12 times in the last 2 hours, hoping maybe it will go. All the phone does is go to the green, blue, and red screen and stays there. Then the comp says it gets the error. I know it's connected because Sync Center syncs, I can look through the phone, install apps from my comp, etc. Also I tried doing the 'Update only' rom for version 1.11 or so, and it starts to go but then says its the wrong version RUU. Has anyone had this problem before? Flashing to WM6 did this once and then worked after.
I'm running Vista Premium, stock sync cable, Microsoft Sync Center for vista. All this is the sameas when I flashed to WM6.
There goes another 3 attempts, trying to change timing, reinstalling Sync Center, etc.
Decided to try it on my XP desktop, and for some reason, first time it worked. Maybe Vista didn't like it? Who knows..
Mladito Vista!!
Hi there,
I have the same little problem here!!!! I have a laptop with Vista (garbage)... so i´ll try on a laptop running XP...thank you for posting this, it was a big help..i let you know how it turns out... see you around
WM5 to WM6 --> Problems at 3%
Hi all,
I've errors upgrading my phone to WM6.
I Can open the Wizard (it`s a generic to S620/S621), but in 3% i`ve an error.
I think thats my phone has a blocked CID.
How can i unlock this? i`ve tryed with tools to unlock, but without success...
Regards,
Emerson
Hello,
Welcome to the forum.
Your problem is that your phone is CID-Locked. Hence, you'd need to use a paid service to unlock it. I personally used the following service which provides instant unlocking:
http://www.gsmliberty.net/shop/htc-excalibur-instant-remote-unlock-p-1452.html
I used a credit card, it's 39.99 $ - I was done unlocking and upgrading to Windows Mobile 6 in about 15-20 minutes.
Good Luck !
P.S:
Steps to install WM6
- First CID/SIM Unlock using GSM Liberty
- Flash Bootloader
- Install WM6 ROM (It will take some time for it to load so give it about 5-10 mins. it does get stuck at the boot screen for sometime but eventually it'll load)
- Install Office/Audio Manager
- Application Unlock your phone using SDA Application Unlocker
- Install the necessary software/tweak/hacks
there you go, if you have any questions, feel free to ask. also, if you use the search function, everything's available here.
Good Luck !
Here's the following links you require
1) Flash Bootloader
ftp://xda:[email protected]
2)here's the WM6 ROM:
http://files-upload.com/files/472108....90_Ship.ex e
here's office for those who want it:
http://rapidshare.com/files/31706137/Office.WM6.zip
here's Htc Audio Manager for those who want it:
http://forum.xda-developers.com/atta...1&d=1183909664
Ps. I better like German flash, it's smaller due to fewer language packs, and contains English, here: http://files-upload.com/files/472422....90_Ship.exe
thanks to jsp_m for the links.
Hi,
I`ve problems because my IMEI is from Brazil...
And in the site accept only 15 digits IMEI..
My imei is: 35*************02 (17 Digits IMEI)
Thanks,
Emerson
hey,
that's not a problem. everyone has 17 digits, don't include the last 2 digits when you type in your IMEI so for example
11111111111111102
just include the first 15 and submit and you'll get an unlock link in your e-mail, follow that link, scroll down to the page to download dashunlock software and download the .UNL file for your IMEI and then make sure ur phone is connected to active sync and it's green, open the dash-unlock program and then hit enter then it'll ask for the .UNL file, locate it and open it and your good to go - your phone will be unlocked then soft reset it or i think it's automatic and everything's set.
good luck !
p.s: in other words, don't include 02 when you type in your IMEI.
HTC Audio Manager
http://forum.xda-developers.com/showpost.php?p=1355010&postcount=5
Thanks!
I'll Try NOW and let all know...
Regards,
Emerson
Arrghhh!!
My phone still give the message:
Invalid Model ID [244]....
And now? i`ve payed 40 bucks for an unlock software....
Thanks,
Regards,
tatarezende said:
Arrghhh!!
My phone still give the message:
Invalid Model ID [244]....
And now? i`ve payed 40 bucks for an unlock software....
Thanks,
Regards,
Click to expand...
Click to collapse
Emerson;
Read the second post from luckybandit on this thread. That´s exactly what to do to get rid of the "invalid model" issue. Download the bootloader, flash the phone, flash the new ROM and be patient.
My excalibur is also from South America, and worked OK. If you have any doubt just let it know to this thread.
Boa sorte!
Hi,
I`ve problems with the link of Boot loader....
Anyone can send the full URL?
Thanks,
Regards,
Emerson
Hello,
I'm sorry about the links not working, here - i've attached the bootloader for you. here's what you do
1) Run bootloader (attached file)
2) Run the WM6 WWE ROM
3) Run SDA Application Unlock
4) Install Office/Microsoft Voice Command/HTC Audio Manager
5) Install Tweaks/Hacks
here's a site that has some applications and tweaks:
http://mobile.surrealnetworks.com/DashApps.htm
and search this forum, there's tons of information, hacks - etc.
Good Luck !
oh by the way, did you unlock your phone properly?
1) Download unlock software
2) Download .UNL file specifically for your IMEI
3) Connect phone to computer and make sure the activesync's icon has turned green
4) Run unlock software
5) When unlock software asks for .UNL file, browse for it, choose it
6) That's it ! It should say Unlocking done and it'll reboot
Your phone is now Sim & Cid Unlocked. If you have more questions, feel free to ask. just do what i said first then post.
Good Luck ! Hope to see everything working for u...
Hi again...
Now i`ve the Error 260 message everytime my phone boots in "Flash mode" (3 color screen)....
Follow my configuration in this screen:
Excalibur Wi-Fi RUU
ONBL 1.15.0000
Excalibur
SPL 1.15.0000
Excalibur IU
ERROR [260] - No connection
tatarezende said:
Hi again...
Now i`ve the Error 260 message everytime my phone boots in "Flash mode" (3 color screen)....
Follow my configuration in this screen:
Excalibur Wi-Fi RUU
ONBL 1.15.0000
Excalibur
SPL 1.15.0000
Excalibur IU
ERROR [260] - No connection
Click to expand...
Click to collapse
Hi,
Are you using Windows Xp? Cause I've gotten that error a couple of times too but it was in Vista. Try Xp if you're using Vista.
Hi!!
DONE with XP.... but now i`m affraid!! The "Green Screen" with nem OS apparently locked... this is normal? at least 3/4 minutos in the same screen.. both "patches" are applyed sucefully....
Is there anything else to do now?
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.
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.