Did I brick my Hermes?? - 8525, TyTN, MDA Vario II, JasJam ROM Development

My problem all started when I try to get BB Connect 4.0 to work on my Hermes. After searching all around, I decided the original ROM that came with my Hermes (4/19/07 version) would not work with BB connect 4 so I decided to install Black 2.5. Being a newbie (I had the phone for all about 3 days), I downloaded Black's .exe package and ran it with the Rom Update Utility provided with the package.
I selected the Force-SSPL option and everything went fine. However, after the installation finished, I can no longer perform activesync with the device. I uninstalled and reinstalled activesync 4.5 multipletimes with no avail. I searched all over the forum and can't find anything on it. I now can't even downgrade or reinstall the package because activesync doesn't recognize the phone anymore.
Please help!!!

Alright guys, after 6 hour of searching on the forum, I figured out what it was. Using this thread: http://forum.xda-developers.com/showthread.php?t=302459 the checkbox under the settings --> Connection --> Usb to PC "enabled advaced network functionality" was checked. Unchecking it solve the problem.

you should also know that putting your phone into boot loader will do the same thing and also makes flashing just as easy or you could have flashed from an SD card. the term bricking means your phone will not turn on period bricking is not what you did. Not doing the research is what i you did,,,

Related

Updating JASJAR

Hi all,
I have been trying to check out the forum here, to try and solve my problem, I literally bought my JASJAR today, and it was giving some wierd behaviour. In an attempt to reload the software (I prefere to reload the entire ROM), something went wrong, now all thats on my screen is "USB" and a lil lower down "v1.01".
ActiveSync obviously not connecting now bcos the OS is not on the JASJAR no more, in my device manager is a "Microsoft USB Sync" under my mobile devices.
I downloaded what I am guessing is WM6, 'JASJAR_WWE_20106_20301_11300_wwe_ship' from another thread in this forum, tried to load that but cant communicate with device cos no activesync.
I have tried the different reset options, like the 2 function keys and the reset on the back, I push 0 to clear, and then it jus goes back to the USB v1.01 thing.
I am running windows vista home basic, with the Windows Mobile Device Center, it synced perfectly with this software, communicated properly with the update tool, until my device reset and activsync lost connection, then i was stuffed.
Any help will be appreciated.
Thanks in advance.
Sounds like it is your first time with the upgrade. What you are seeing on the screen is the bootloader, which is what we use for flashing new ROMs.
ActiveSync or Windows Mobile Device Center (how come you have both on Vista?) will therefore not respond. This is fine, because we use a different program to load the new ROMs.
If you look at the folder you downloaded, chances are that there should be a program called "ROMUpgradeUt" or something similar. Provided that you have not changed anything in the folder, you should be able to flash the new ROM by simply following the instructions in the program.
You can also read this link for more information: http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
Here is an instruction guide on ROM upgrading: http://forum.xda-developers.com/showthread.php?t=269118
how come you have both on Vista?
Sorry, I don't mean to sound like I have both, I recently moved to Vista, and am used to calling it activesync and not WMDC.
Thanks, will have a look
Ok, well I have got it up and running again, only problem now is activsync keeps freezing when I try and sync the device...any ideas?
I landed up using my work computer, which has XP on it, and then used MTTY and that connected fine, on Vista it simply didnt wanna work.
I ran the utility for those 'stuck on serial/usb', and that fixed it. Now I would like to load up WM6, but it keeps getting communication failures.
Thanks for the help guys....I got it working...running on WM6 now...whoo!!

Windows Vista, WM6, and Tethering

Ok I searched on the forums hard for this one so forgive me if this has already been answered. I see to find people with Windows Mobile 6 and Windows XP or people with Windows Vista but Windows Mobile 5.
Since I'm running Vista, I use Windows Mobile Device Center instead of ActiveSync. The functionality of the program is fine, so I have no complaints. However, to upgrade ROMs or anything...I use an XP Machine as it seems Vista seems to think the device disconnects upon the loading of the bootloader. I've read somewhere in the forums that there is a driver update to fix that, but after applying...WMDC doesn't work properly...so I'd save the trouble and use a machine that has XP running instead until a better fix comes along.
My 8525 came stock with a program called Wireless Modem as of ROM 1.34.502.1 shipped, which seems to have been replaced by Internet Sharing.
The Wireless Modem application worked fine after setting up the modem with the Vista driver also found in the forums. I also tested the bluetooth connection and set that up to tether as well and it worked fine.
I finally decided to upgrade after days of reading and I tried to use the Wireless Modem feature. I noticed it wasn't there and tried to use Internet Sharing. The layouts are similar...but when I hook up the phone under USB, my computer doesn't even recognize it as a new device (modem) as I did uninstall the last driver.
When connected via Bluetooth, it recognized the device and installed the driver as Windows Mobile-based device support by default. Under services, only Active Sync is only available...as opposed to before when I had Dial-Up networking available. When I set up a PAN, the computer and device are connected together, however I do get the same problem as some others with a connection that is limited or local only. So the tethering is unsuccessful.
I recently upgraded my Cingular 8525 to WM6BE v1.2 (Cingular Edition)...which I can't seem to find in the threads anymore. I'm also running Radio 1.38.00.11...but I don't think that would affect anthing. I reverted back to my shipped ROM to check for alternate settings that might have helped...then I was going to revert back to WM6BE v1.2 Cingular...then I realized I accidently deleted that custom ROM and I couldn't find it anymore. I was stuck putting on the WM6BE v1.2 on the sticky thread after which forced me to reinstall the data settings/keyboard fix from the cab files. Haven't had problems with them but I did like that customized ROM for Cingular a little better considering I really like "clean" ROMs.
Anyway, I'm attempted to connect via MEdia Net AND Cingular GPRS settings provided by the Cingular Data Settings cab floating around the forums. It works fine it seems...it just seems like the problem is getting Vista to recognize the device as a modem, or at least having modem capabilities.
I guess thats as detailed as I can get right now. Hopefully someone can help now ^_^
You are right. I tried updating rom on Vista's Windows mobile Device and end up damaging my xda2i. The device displays "USB" when connected to cradle and "Serial v1. 01" when not. Do you have a solution apart from upgrading?
Solution on Vista
Hello Guys, I'm running vista too and I bothered 2 hours before getting it done.
So this is one of the "Step-By-Step Instruction Guides".
0. Extract the attached file into a directory of your choice
1. Disconnect your Device
2. Goto Settings > Connections and choose "USB To PC"
3. Uncheck the option there
4. Reconnect your Device
5. Goto your DeviceManager and search for "HTC USB Sync", double click it and choose Drivers
6. Click on the "Update Driver"-Button and choose search on the computer
7. Click "Choose a driver from list..."
8. Click the button to the right (Open from Media)
9. Choose any INF File from the extracted ones.
10. You're done, upgrade your ROM.
11. To Rollback drivers, use the "Automatic Update" instead of Manually selecting (it will choose the newest ones)
12. Recheck the option of step 2 unless you're planning to use the slow variant.
Have Phun and Good Luck
Have I understand right? With this tweak We will be able to applied ROM upgrades to our HERMES from windows VISTA?
Confirmed.
I did already update my ROM in this way.
Cheers,
soniX
EDIT:
Please use HardSPL or something equal to be sure the risk is at a minimum.
And I can not be held responsible for any damage to your Hermes or your Brain
But as I said, for me it worked perfectly, remember to Restore the new Drivers or the Mobile Device Center will not work.
Hmm I don't think you people understand what I was asking...
I already know about that method to update with Vista...I actually tried it yesterday and for some reason it didn't work so I just use an XP Machine for now...but I was just asking merely about TETHERING.
I already have the ROMs of my choice loaded on my device.
In simpler words: How do I go about tethering (Running Internet Sharing) when my computer does not recognize the device as a modem...through USB or Bluetooth.
I'm running WM6BE v1.2 and Windows Vista Ultimate.
Maybe its Wm6BE, but I have used all the other roms (xda live, des, lsvw) and all I do is plug in the usb, start internet sharing and it connects no problem. Have to start internet sharing before wmdc starts. Internet Sharing works great, better than wireless modem. I was not able to use the WM6be due to problems with sbp pocket plus. I am currently using XDA live .30 and Vista Ultimate.
Does the technique in the post above work??
Also once that procedure is carried out can rom updates and RUU programs be used exactly the same as on XP??
If anyone is available to do some screenshots for me for an updated GUIDE, please PM me (i dont use or have a copy of vista )
I enjoy the community so I think I'll do my best to contribute to it. When I get the chance, I'll try to make a guide with screenshots on using Windows Vista and loading WM6.
I'm going to try to switch to LVSW build with his new update today and I'll see how that works out.
I REALLY like the one custom build someone made (I forgot who) with the Cingular connection settings defaulted from the Cingular Shipped ROMs...I wish I can find those files again.
It seems like the people developing the new Cingular data connection cab files are really working hard at getting the default settings as if they just bought their phoes straight from Cingular.
I'll let you know how LVSW goes with Internet Sharing and Windows Vista
sonixwarrior said:
Hello Guys, I'm running vista too and I bothered 2 hours before getting it done.
So this is one of the "Step-By-Step Instruction Guides".
0. Extract the attached file into a directory of your choice
1. Disconnect your Device
2. Goto Settings > Connections and choose "USB To PC"
3. Uncheck the option there
4. Reconnect your Device
5. Goto your DeviceManager and search for "HTC USB Sync", double click it and choose Drivers
6. Click on the "Update Driver"-Button and choose search on the computer
7. Click "Choose a driver from list..."
8. Click the button to the right (Open from Media)
9. Choose any INF File from the extracted ones.
10. You're done, upgrade your ROM.
11. To Rollback drivers, use the "Automatic Update" instead of Manually selecting (it will choose the newest ones)
12. Recheck the option of step 2 unless you're planning to use the slow variant.
Have Phun and Good Luck
Click to expand...
Click to collapse
Also, I've seen this guide posted twice...yours missing one step where I was supposed to "End WMDC.exe Process in Task Manager"
I still can't get Vista to run RUU...do you run the RUU with your device in Bootloader? I think I even tried that once and and still couldn't get it to work with the older Driver.
Not exactly sure what I'm missing or doing wrong...but its definitely after I install the driver. It acts as if I didn't install it at all, even if I check in drive details and its all correct in there.
i tried the method above for upgrading in vista and it didnt work for me...
what am i missing?
Where is it stopping?
Because I did it once, it has to work.
Where is it stopping? - At the bootloader (LSD-Screen with psychedelic colors ?) - or before ?
I will do an upgrade in the afternoon again and this time i will record ALL of my steps.
Hopefully I'll find the recept for the cake.
Cheers,
soniX
Yea it gets to the bootloader screen and I'm stuck as if I never loaded the AS4.5 drivers.
Sorry, too less time today for a screenshot-decorated guide.
I just upgraded my device again (only to proove it does work).
So here is again a guide, which differs to the first one.
I guess there are two ways to do this...
Prequesites:
- Search my previous post and download the USBAS.zip-File
- Extract it into a directory...
- You'll need your device and it has to be connected, too
The first approach:
Change the Serial-Driver
- On the device click Start > Settings, choose "Connections" there and click on "USB to PC"
- uncheck the item for "Enhanced..." there
- Click on OK.
- Now goto your Device Manager.
- Search an Item named "HTC USB Sync".
- Right-click it and choose "Update Driver".
- Choose the second option, then select to choose manually
- Select the directory where the zip has been extracted to and choose any inf file.
Start the Update-Tool
- After the driver-update you need to set the device back to RNDIS-Mode (follow Step 1 and recheck the option)
- Verify that you're running the correct drivers for the RNDIS-Device, the date in the device-manager has to be around January, 17th 2007.
- Start the ROM-Upgrade.
- It should work now.
For me it did not really work to switch from RNDIS to USB-Serial drivers in my localized (thanks bepe for the great work!) german WM6.
So if you have a problem with the first method use this one.
- Start your Device-Manager, we have to be very fast.
- Start the ROM-Upgrade as you've probably done before
- If the bootloader starts up, you'll notice a device/dettached,device/attached sound, this is your sign, goto to you Device-Manager.
- Search for the Entry "HTC USB Sync".
- Update drivers like it's written above.
- If it won't work and the upgrade tool dies with "cannot connect", don't worry. Reset your device (soft) and try again, this time you should not need to update the drivers.
Cheers,
soniX
I'm using XP and a USB cable. USed to work OK before upgrading to WM6 Black but now I get Error 797 on the PC saying modem not found or busy!
mrvanx said:
Does the technique in the post above work??
Also once that procedure is carried out can rom updates and RUU programs be used exactly the same as on XP??
If anyone is available to do some screenshots for me for an updated GUIDE, please PM me (i dont use or have a copy of vista )
Click to expand...
Click to collapse
Take a look here
Code:
http://www.modaco.com/index.php?showtopic=252977
For Vista guide with screen shots, so far i've only flashed HardSPLv4 from inside Vista, but it worked i'm still plucking up enough courage to do a full flash of WM6
Nic
I do this (for Hard-SPL, don't know for other):
I have made what it was written on modaco (http://www.modaco.com/index.php?showtopic=252977), but
1) I was not in bootloader.
2) While active sync try to connect (but it does not succeed because they are not its driver) I've stopped WMDC.EXE and now hermes is connected.
3) NOW I do a flash.
If there is something that is not clear you say it to me.
My method also works (for me)
Can somebody confirm that my method works for vista?
soniX
I'm based also to your method, but it would be more complete to integrate it with the method on modaco.
It seems that most people didn't get the point of this thread...weird considering I put TETHERING in the subject line. However, it is nice to see people trying to help others with Vista to flash. I have the same problem myself but access to machines with XP nullify my real need for flashing on Vista for now.
I'm about to reinstall LVSW's latest ROM set for the billionth time and I'll try out tethering on that. It seems that people who were on WM6BE were having a hard time with Internet Sharing. I'll load a new rom and let you know how it goes.

Restore official ROM

Hello,
first of all, i want to thank you all for this great forum.
I have a small problem. I have bought a few days a HTC P3600. Everything was working fine.
Yesterday i tried to upgrade to wm6 using MARY 3.4.1 with sucess following the upgrade guide in trinityguides.info.
I have installed the Des’ Crash-Proof SPL and then flash the MARY 3.4.1 ROM.
Until now everything is working fine except the active sync. I tried to AS with the usb cable but it won't connect. It gives me the following error:
"Communication Error:Cannot start communications with the desktop computer. Remote Networking could not start due to a critical error (Error 608). Please reconnect your device. If the problem persists, restart your device using the instructions provided by the manufacturer."
I've googled it and tried all the suggestions that i could find, with no success.
If i connect via BT there is no problem.
The problem is that i want to put back the official ROM from HTC and if i can't connect with active sync via usb, i can't restore it.
BTW, if i put back the official ROM, the Hard-SPL is also flashed to the original??
Thank you
cabexas said:
Hello,
first of all, i want to thank you all for this great forum.
I have a small problem. I have bought a few days a HTC P3600. Everything was working fine.
Yesterday i tried to upgrade to wm6 using MARY 3.4.1 with sucess following the upgrade guide in trinityguides.info.
I have installed the Des’ Crash-Proof SPL and then flash the MARY 3.4.1 ROM.
Until now everything is working fine except the active sync. I tried to AS with the usb cable but it won't connect. It gives me the following error:
"Communication Error:Cannot start communications with the desktop computer. Remote Networking could not start due to a critical error (Error 608). Please reconnect your device. If the problem persists, restart your device using the instructions provided by the manufacturer."
I've googled it and tried all the suggestions that i could find, with no success.
If i connect via BT there is no problem.
The problem is that i want to put back the official ROM from HTC and if i can't connect with active sync via usb, i can't restore it.
BTW, if i put back the official ROM, the Hard-SPL is also flashed to the original??
Thank you
Click to expand...
Click to collapse
Try an other usb port on your computer.
And yes, offical rom restore everything (ipl,spl,radio,os)
I have already tried that.
The only thing that i can remember that i didn't tried, is connect in a different computer, but i will try that as soon as i get home.
thanks
try another ROM. got that activesync issue also with every Mary ROM.
You can find it in UDK rom thread
Active Sync Error 608
Try this to solve the problem:
Quote:
Originally Posted by nanni100
I solved cause my Windows Firewall was damaged and not customizable, then i found a reg file to solve this problem, installed on pc and reboot. On startup i saw the window of Win Firewall who asked me to unlock Activesync i said yes and turn off the firewall
I have a ethernet router with DHCP enabled
Then i configured the phone:
-Enabled Advanced Netword Function
-Go on Setup, Wi-Fi, Network, Remote HOST- NDIS
-Select the Specific IP Address like this:
IP Add: 169.254.2.1
Sub Mask: 255.255.0.0
Gateway: 169.254.2.2
and on the other page put only on the first DNS: 169.254.2.1
on the pc lan connection i leave the dhcp enabled "Obtain IP Address from serv" also for DNS (obviously cause i have the DHCP enabled on my router)
And MAGICLY all start works FINE!!!
After hours and hours spent on configurations, the problem was "simply" the windows firewall, but also the configuration of Remote Host-NDIS is important
Hope that can be useful for other
Right now i don´t have the MARY rom but the TUGA V3 ROM and problem continues. I have already tried to setup Remote HOST- NDIS like that and it didn´t work too.
Anyway thanks for all your help.
Thanks
Use the SD Card Method...
I use the SD Card Method. MUST BE FORMATTED AS FAT32 first. (As per willowxda's post. Thanx Willowxda)
Copy SSPL_TRIN.exe to your SD card's Root folder. (Included in ZIP File)
Rename the RUU_signed.nbh file in your OEM Rom to TRINIMG.nbh
Copy TRINIMG.nbh to your SD card's Root folder.
Run SSPL_TRIN.exe from your device.
Allow it to Flash and Restart as needed.
Works like a charm...
cabexas said:
Hello,
first of all, i want to thank you all for this great forum.
I have a small problem. I have bought a few days a HTC P3600. Everything was working fine.
Yesterday i tried to upgrade to wm6 using MARY 3.4.1 with sucess following the upgrade guide in trinityguides.info.
I have installed the Des’ Crash-Proof SPL and then flash the MARY 3.4.1 ROM.
Until now everything is working fine except the active sync. I tried to AS with the usb cable but it won't connect. It gives me the following error:
"Communication Error:Cannot start communications with the desktop computer. Remote Networking could not start due to a critical error (Error 608). Please reconnect your device. If the problem persists, restart your device using the instructions provided by the manufacturer."
I've googled it and tried all the suggestions that i could find, with no success.
If i connect via BT there is no problem.
The problem is that i want to put back the official ROM from HTC and if i can't connect with active sync via usb, i can't restore it.
BTW, if i put back the official ROM, the Hard-SPL is also flashed to the original??
Thank you
Click to expand...
Click to collapse
it is very simple but it took me too long time to figure out.
My PC hangs several times, I thought it is related to DMA or to IRQ interrupt requests for the microproccessor, but failed to solve it. This problem never happened to me while I was having the Qtek ppc, and even when I used the official HTC ROM when I bought this TrinTy. Then I started to check everything related to USB connection till I catch it. it is very silly, just to clear one checkbox.
Here what worked for me:
Click Start > Settings > Connections > USB to PC
you will find a checkbox......Just uncheck it. --------> Thats to disable advanced network functionality.
I believe it should work for you.
Try POWER + CAMERA + SOFTRESET (this enter the bootloader mode) and then install the ROM you like ... you will get no errors !!!
Click Start > Settings > Connections > USB to PC
you will find a checkbox......Just uncheck it. --------> Thats to disable advanced network functionality
Click to expand...
Click to collapse
That was the first things that i tried to do, but with no luck.
Yesterday, i did what nightfear suggested and it worked fine.
As soon as i restored the official rom, AS started to work like a charm.
That is a strange issue, but for now it's resolved.
Lets see if the problem doesn't come back when i put WM6 on it again.
Thank you all for your help.
Mini SD card must be formatted in FAT32 for flash update to work
I have been trying to upgrade flash via SDCard but it did not work no matter how hard I tried (switch btw hardspls).
Then I realised that I have to format the SDCard to FAT32 so that the Hard SPL can recognise the card in bootloader prompt.
I am using Hard SPL 1.30

[Question] 260 error when updating ROM

Okay, I've searched alot to get this thing solved. When I try to update my rom, the update starts normally, but then my telephone screen turns black, my gets disconnected, windows tells me it has found new hardware. The update failes and returns error 260 (connection lost). When I soft-reset the telephone afterwards, it returns to it's old shape.
Info about my telephone.
Rom: 1.93.404.1 NLD
Radio: 1.0025.05
PC: Windows XP SP 3, Active Sync 4.5
I tried to update with this rom: RUU_Diamond_HTC_NLD_2.03.404.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I also tried to update to Hard-SPL but that gave me the same error.
PLease guys does anyone of you know how to fix this? (personally I think it's windows xp which is screwing up).
Thanks in advance, I appreciate all help.
Yours, Martijn.
Even the tiniest tip may help (A)
I had the same trouble with that rom, I tried from internal memory and it worked. Search the wiki I am sure the info is there.
"ERROR [260] : UPDATE ERROR
This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again."
This is what the WIKI tells me. But I have tried that. How did you manage to perform the update on the internal storage? Because I tried that with hard-spl but it wouldn't work.
Besides I only have .exe files for the Hard-Spl and the official rom from HTC.
Thanks for your reply though.
EDIT PART, just read this on another thread in the wiki:
ERROR 260 (Update Error):
"Your phone is not connected to ActiveSync. Check your connection or restart the phone. Also make sure in ActiveSync that "Allow USB connections" is checked (under File->Connection Settings). If this still doesn't help, then remove the memory card and SIM card before flashing."
I'm going to try this now, if it worked, I'll let you know
Just found out I have a CDMA version or something, I'll try google for the problem now.
Get the rom image from your temp directory and look here, found in the wiki
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
dickenz said:
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
Click to expand...
Click to collapse
It looks alot like your problem yes. But last time the hardware installed correctly, then the patch I found for CDMA models on ppcgeeks failed, and my telephone got bricked. So I'll need to get that fixed first. After that I'll sure think twice before I try another rom update :/
Thanks for all the help though, and I have to advice everyone to not use the hard-spl for cmda users from ppcgeeks unless you're 100% sure it fits your model!

Hour 3 of unsucessfully attempting to update Rom

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.

Categories

Resources