I have a imate pda 2k runnign wm5 the original rom. The boot rom is V2.06
I place the phone in boot mode, it comes up in serial and when I put it in the cradel the display chages from serial to usb and the pc makes the usb connect sound (I have activesync running at this point, have tried two different machines one with 4.1 and one with 4.2 beta) I run the updater and it just sits there with the "collecting information" legend at the top of the window. Eventually it goes to error 101 cannot connect.
Any ideas? I want to go to the new Tuma 1.3 because I am tired of loosing email accounts.
Re: Help; Cant update to new wm5 load getting error 101 cant
mlukens2 said:
I have a imate pda 2k runnign wm5 the original rom. The boot rom is V2.06
I place the phone in boot mode, it comes up in serial and when I put it in the cradel the display chages from serial to usb and the pc makes the usb connect sound (I have activesync running at this point, have tried two different machines one with 4.1 and one with 4.2 beta) I run the updater and it just sits there with the "collecting information" legend at the top of the window. Eventually it goes to error 101 cannot connect.
Any ideas? I want to go to the new Tuma 1.3 because I am tired of loosing email accounts.
Click to expand...
Click to collapse
try to use noid.exe to flush your rom
Duh had to remove my sd card
Read though a bunch of posts, the net was take your SD card out while tying to boot. It worked! Thanks anyway
I've searched through the forums and can't find reference to anyone having problems upgrading due to their PC.
I've upgraded ROMs many times before but the most recent venture on my MDA Pro to WM6 (hemi 1.1) has been unsuccessful.
Basically starting 'ROMUpgradeUt' brings up, 'Device Software Update Utility' then clicking next starts the sofware search for the device but then it shuts down with no error message!
I've noticed other ROMs to give me the same problem now (eg Helmi AKU 3.5).
Tried:removing SD card, removing SIM, 'device upgrade mode'(light, power+reset), unchecking usb connection, hard reset, computer restart (XP),
ActiveSync 4.5 5059 working fine, country id error upgrade, tried another MDA Pro same problem.
I've run out of ideas guys.
PS last time i tried to upgrade to WM6 i got stuck on boot screen and had to use the mtty tool to reboot.
I think you should try an other mashine.
SOLVED !
Universal didn't like the different USB port at the back of the computer i was using. I had connected an external hard drive to 'its' port.
This things more touchy than my wife!
AbuGWM5 said:
This things more touchy than my wife!
Click to expand...
Click to collapse
ROFL It's sometimes scary how much I compare my PC to my ex lol...
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.
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,,,
Hi All, I've encountered "Not able to Activesyn" + unable to recognize my Diamond camera after I upgraded my Diamond with "EnergyROM 1.0 Diamond 52109 Phoenix Standard LZX". No matter how much i've tried to reinstall the Microsoft Activesyn 4.5, it doesn't work. That's why i could not downgrade my device back to the previous ROM version. Anyone's suggestion for any other ways to downgrade my Diamond's ROM without relying on Microsoft Activesy/window mobile center?
Please Help
Did you make sure that Start -> Settings -> System -> USB Settings -> Enable faster data syncronization
is unchecked.
you can flash any rom using the internal storage mode.
for more information go to:
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
Yes I did, but still not working. Thanks anyway for the suggestion.
Yes I did, but still not working. Thanks anyway for the suggestion.
im sure you've already done this and it may come across as silly to ask but have you tried a hard reset yet??
I've had this happen once before with a ROM i flashed about 8 months ago now. I did a hard reset and then on the bootup, i cancelled the configuration where it installs the custom apps. This worked for me, might be worth trying.
during flashing the ROM, after i pressed the power button the process remained not progressing at about 20%. It has kept me waiting for more than 40 minutes so far. I'm still waiting.
Thanks for the comment
take the battery out and put it back in, then turn it on again and see what happens. you may also want to try getting into bootloader then see if you can get it to show usb when connected to your pc.
Holding down on Volume down/Reset should enter bootloader.
It work now. I put my Diamond to "USB Trigger Mode" then I pressed the active button. After that i run the ROM file from my PC via the USB cable. Finally my diamond was downgraded.
Thanks you all for your kind help