I posted this in the forum for the ROM but want to widen the audience. I am installing a ROM using RUU and keep getting communications errors. I have a partnership setup and it finds the phone perfectly. It detects the version and then reboots the phone fine. Both the PC and the Phone come up with the progress bar and sit at 0% for a minute and then I get a communications error and it fails. I tried this on an XP machine with activesync and on a vista machine with no luck. Anyone else ever had a similar issue with some ideas on what I can try?
Thanks,
Chris
tell me you have hard spl.
I don't actually but I did not brick my phone. I can yank the batter for a minute and then put it back in and it boots right back up. Could that utility make the communications issue resolve itself?
hardpl
Ok, I found this and it seems the process for installing this is the same as installing a new ROM and the communications issue happens here too. There has to be something simple I am missing. Anyone? Please!!
Related
When I run the wizard update for rom or radio or anything it says one of two things on my pc, 1. that there is a connection error and or 2. That the program needs to close because it says so. Im sure there is a simple fix to this issue but i just dont know it.
Thanks
I think I know why
After reading through the posts I discovered why I am having so much trouble. Reason being last week I upgraded to Vista, which would explain alot.
Anyone know a way arround this problem?
irishmatt12 said:
Anyone know a way arround this problem?
Click to expand...
Click to collapse
Downgrade to XP...
There are lots of issues with the rom updater and Vista. Unfortunately until a new version of the rom update utility comes out (or some other new method) its going to be an issue.
Not only RUU, WMDC itself sometimes get problems in Vista.
When I connect the Wizard to PC, sometimes WMDC does not show up, and the PPC is not present in My Computer, and you will see a yello exclamation in device manager!
The only thing I can do is to remove the device complete from device manager and let it detects again, then I can use it again for several times.
Hi there, I've been reading your forums since I got my diamond. You have done a great job here.
Until now, I have been able to learn almost everything I now from here. (I'm new to ppc). Nevertheless, I have come up with something I cannot resolve.
I had installed hard spl signed from olinex (1.30). And also upgraded my rom to 1.93 without any problem. But when I tried to do the same with the radio (I want to go from .05 to .08) I get 260 errors over and over.
I use Windows Vista x64 which seems to be problematic but for me worked at first. Anyway I also tried to run it on Xp and go 262 errors instead so no luck with that.
I have tried several things I've already read. Switching USB port, starting the flashing on bootloader, disabling advanced network functionalities from Usb to Pc, ...
The issue seems to be with my PC not dealing with the device when the tricolor screen appears. USB is written in the white band, and Vista seems to recognize an HTC usb device. But when I try to run the CustomRUU when already in the bootloader mode, the app doesn't even recognize the diamond.
Otherwise it recognises it, but when it changes to tricolor screen and the progress bar appears it gets stuck at 0% until the 260 appears.
I think I have run out of ideas right now. Could any of you lend a hand, please?
im pretty sure you need unsigned spl for flashing radios. i dont think radios are signed. i could be wrong, so maybe wait for some more replys before flashing. btw welcome
Thanks. I suppose I'll wait as you said but you are probably right about that. Anyway I suspect that sadly that's not the main problem. I have tried to reflash my rom, just for testing if it worked and ... 260 . Trying to reflash HardSpl or trying to install an unsigned version didn't work either. I've downloaded from different sources to make sure that the file being corrupted was not the problem. I don't know if I'm doing something wrong or I was just extremely lucky the first time it worked
Hi, first of all let me begin by saying that I have spent a long time reading around through the guides and forums about flashing rom/radio to my Rohdium but still face problems. I have successfully flash my old TyTN II and Orange E650 but am at a loss as to why Im struggling this time round!
I flashed the Hard SPL which went 'fairly' smoothly, got there in the end after having problems on WIndows 7 64bit and then succeeded using Xp 32. However when trying to flash a new rom and/or radio I am greeted with an error, that being Error 284. I have tried like I say on Win7 64, Xp32 and when the error pops up my phone gets stuck on the process bar and forced to pull battery out. I then put it back in and it freezes on bootloader. The RUU software trys to recover but it is a loop of the same thing happening (attempts and then crashes). The only way to get out of this mess was strangely reflashing HardSPL which recovers it and allows me to boot to Windows. I have tried flashing a radio and/or rom whilst in sync within windows, I have tried flashing when manually forcing the phone to enter bootloader, I even paid the £10 to get the unlocker which would patch the special radio but that even returns the same error. I have the sim card out and storage card, battery charged over 50%. I even tried the Mtty program (sorry if mispelled, at work now and can't fully remember name!) when it was stuck at bootloader and using the "boot" command it boots as far as Touch Pro 2 logo but then doesn't progress, then i resorted to reflashing HardSPL which allowed me to boot properly. I just don't know what else to try!
Like I said Im sorry if this is obvious to someone but I have tried alot!
Many thanks in advance if someone could help!
* Update: Just tried flashing a radio on my works computer (XP 32) and it flashed no problem!? Wonder why my operating systems had an issue?
** SOLVED! ** - got home and randomly tried again on Win7 64 without using my USB extension cable and plugged into a different USB port directly and it worked! Faulty cable maybe, bad luck, who knows, it works!
Thanks.
Sound like maybe your RUU/update utility may have gotten corrupted. I would try to re-download the rom you want to flash over to your home pc again and try to re-flash.
If that doesn't work, you can always flash your rom through the storage card.
hmmm yea thats possible, will try when I get back in couple of hours thanks! Just seemed weird how nothing was working, different roms (cooked roms or shipped roms) and even the security/sim unlocker that I purchased......mystery!
USB cable tends to go bad easily! That might be the reasion why!
I have been trying for almost 2 days straight to flash a new HardSPL then ROM to my Touch Diamond. I have done everything I can possibly think of but nothing works. I think the problem may be that I am using VMWare Fusion (on a MacBook Pro) running Windows 7. I can establish a connection with WMDevice Center perfectly fine, the RUU puts my Diamond into BootLoader and it says USB in the white area. However, after this step the status bar shows up on the computer for about a minute then I get error 26x (260, 266, 264....) cannot connect to device. I don't know how to work around this. I would just boot from the Internal Storage but I need to be able to flash a HardSPL before I can do this. I somehow was able to flash a new SoftSPL (I'm running SPL-0.64.000 right now). If anyone has any ideas about what I can do please let me know. I've searched the forum, done hard resets, tried JumpSPL v1, tried to boot a ROM from Internal (can't without updated HSPL), everything. I'm out of ideas.....
Im having the same problem i almost slammed mines. At first the activesync use to come out now it doesnt even do that some choose what to open with box comes out. This phone does things random i have no idea why. Everytime it connects i press the update to install the new windows 6.5 on it and the the sound of it disconnecting shows up then it sounds again and then the screen says usb and then on my computer it says theres no htc connected so i wait to see and i get a error after 3minutes of waiting then i got to reset. Its getting me real frustraded.
I am trying to HARDSPL my Tilt 2 and keeping getting not connected errors [264]. I have tried auto and manual. I placed the CAB file on the device and re-ran. I tried it in Win 7 and XP Mode. The deivce is connected, I can browse files thru the PC, Outlook is syncing, etc...
What will happen if I flash a new ROM without HARDSPL?
osu9400 said:
I am trying to HARDSPL my Tilt 2 and keeping getting not connected errors [264]. I have tried auto and manual. I placed the CAB file on the device and re-ran. I tried it in Win 7 and XP Mode. The deivce is connected, I can browse files thru the PC, Outlook is syncing, etc...
What will happen if I flash a new ROM without HARDSPL?
Click to expand...
Click to collapse
It won't flash at all.
Make sure you're running the file as administrator, other than that I have no idea what else you can try.
Hope this helps.
search for "enablerapinew.cab" and install
You need to post in the HardSPL thread, if you are having trouble with HardSPL
Thanks for the replies. I am making progress, but still not there.
I already had the enablerapinew.cab installed and I am using the manual flash method.
I "ran as admin" and it started the flash process. This time I got progress bars on-screen and on the device, but both stayed stuck at 0% until the flash utility timed out and walked me thru the recovery process.
I am using Windows Mobile Device Center 6.1.6965. It shows connected but drops the connection when the flash process starts. I assume this normal.
Any other suggestions.
osu9400 said:
Thanks for the replies. I am making progress, but still not there.
I already had the enablerapinew.cab installed and I am using the manual flash method.
I "ran as admin" and it started the flash process. This time I got progress bars on-screen and on the device, but both stayed stuck at 0% until the flash utility timed out and walked me thru the recovery process.
I am using Windows Mobile Device Center 6.1.6965. It shows connected but drops the connection when the flash process starts. I assume this normal.
Any other suggestions.
Click to expand...
Click to collapse
Hmm at least I helped a little, try updating the Device Centre to the newest, which I believe you acually.
A couple more things to try, one you need an active internet connection (can only assume you have this) and I found this on the HardSPL thread...
"if you get error msg for hard-spl program where it can not connect to device than use the cab that the hardspl program asks you to install on device: especially for tilt2 users.
Once you install the cab (on device), rerun the hard-spl program. DO NOT freak out as your device completely powers off. leave the usb cable plugged into device and computer and follow onscreen prompts."
Also make sure your radio is on (aka you have signal on your phone/it's not in airplane mode) and the basics such as the cable and the USB the device is plugged in to.
Once again, hope this helps
Problem soved. I published my answer in the Hard SPL thread.
http://forum.xda-developers.com/showthread.php?p=6518785#post6518785
Issue solved, Thread Closed