This is connect to trying to SIM and CID unlock my vario II with version v2a of Pof's tool, however I don't think it has anything to do with the tool itself and appears to be much more fundemental.
When I put my phone in bootloader mode and connect it to my pc it goes through the usual "new usb device detected" stuff, asks to look online for the drives, etc. But after about 5 minutes of looking its says it couldnt find any drivers.
I've had a good search of the site - found a couple of suggestions it can be down to a dodgy usb cable. Tried that and it hasn't helped. I have also tried it on another pc and the same thing happened.
Any ideas?
Thanks.
James
Please ignore me. Repaired activesync from the installation cd and everything's going fine now.
Related
Hi - i tried to update my xda2 (Himalaya) to the uk o2 rom from the installed uk vodafone rom. but it we bellys up. now all i get is a screen showing me serial v1.06 and then when i dock it onto the cradle it shows usb v1.06 (which i have been tols is the bootloader screen -but i am not sure as the xda1 bootloader screen sayd bootloader on it).
I have tried running the rom update again but have had no luck - the computer does not recognise the device - as it says there is no drivers for it (although i have activesync installed) - but was like that since i bought it - just been using bluetooth to install programs.
When i had a xda1 i had the same problem when changing roms and was able to fix the problem by making an sd image using OS IMAGE TOOL. But this program says 'unsupported file format' when i try to make an os image of the nbf files (nk.nbf, ms_.nbf, Radio_.nbf) to my sdcard.
Does ne one know how to make an os image of the .nbf files so i can put them onto my sd card and try and resolve the problem.
any other ideas welcome and much appreciated
thanks steve
much of what you seem unsure of is describet here
http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloader
http://wiki.xda-developers.com/index.php?pagename=HimalayaHowtoCopyRom
like this
"you can connect to the bootloader, either via a serial cable, and use a terminal program like hyperterm. or via usb, and use mtty. make sure you have disabled the serial or usb connection in activesync, before trying to connect to the bootloader."
'usb port cannot open'
tried mitty just gives me 'usb port cannot open' although i have my xda2 in the cradle and pluged into my usb port. when i connect to the usb port it comes up on my screen - new hardware found - no drivers found - and keep popin up as if the xda2 was found then disapears then found. although i installed the drivers when i installed activesync (have both serial and usb turned off in active sync).
have rom upgrade from o2 and extracted the .nbf files
ms_.nbf
nk.nbf
radio_.nbf
is there a way to put them on an sd card so i can put it in the xda2 and boot from that??
not that i know of
my pc always found some ms driver thingy
when i connected my pda in bootloader mode
not sure if it took it off the internet when it found the device
or if i got it with activesync
i think the problem with my computer recognising the xda2 might be down to the cradle, as from i bought it, i have always had problems charging it - depending on what way it is sittin on the cradle. i have purchased a new usb to xda2 lead and hope this will help with this problem.
Just got my 8525 in the mail. I had the newest rom from cingular.
2.15.502.3 04/09/07 SPL 1.09
I tried to use the "HTC_Hermes_SIM_CID_Unlock_v3a"
I was able to get to the RGB screen where it said:
IPL-1.01
SPL-1.40.olipro
After that the progam said the device not connected.
I remove the battery, the program was able to flash to 28% and then
device not connected error again.
This time I remove the battery, reset, but when the program started
to verify my phone, it said error 260: connection. I tried a few times
but still the same. I am sure it's connected because the word changes
from serial to USB when I plug it in. I even try mtty to get out of the
RGB screen but no luck.
Can anyone help? I am almost going crazy!!!
Thanks.
Looks like it's my USB port that's very unstable.
Use another USB port from my PCI card and it finally recognize
my 8525..
whfew...!!!
I am relieved...
Hi!
Recently I try to flash my SPV m3000 using HardSPL and then shelltool (with a rom wm6 HTC Professional)
And now, my pda still on orange page where I can see SPL and IPL version.
(IPL : 2.16.0001 SPL : 2.16.0001)
If I try something :
Hardspl doesnt find my mobile device!
Shelltool doesnt work and still not responding!
Any RUU say ERROR [260] Update error : The update utility cannot connect to your PDA phone!
I try that in bootloader mod. My PC see my device (in "Gestionnaire de périphérique" I dunno how to say that in english!), but Windows Mobile Device Center doesnt!
Can someone help me please?
Thx
I think that basically your device is unknown to windows enter bootloader manually yourself, do not connect it. Then open windows mobile devicecenter and select connection settings and untick the allow usb connections then connect the device and try to flash it.
I also hope you realise that you have a G4 device and are not trying to flash a g3 hardspl go here to get hardspl for g4
http://forum.xda-developers.com/showthread.php?t=332320
windows Vista is not recommended for HardSPL,its not compatible,still got issues.Try to do on winXP pc and use ActiveSync 4.5,there shudn't be any problem.
Well! there's no 'G3 HardSPL' as yet!!! its only 'HardSPL' for G4 devices.
Thx all!
Ill try on XP..
Ill say the result..
So I try.. and always the same message ERROR NO DEVICE DETECTED
I try that with XP Activsync 4.5 and my spv connected in bootloader and connected less bootloader!
So if u have any other idea.. Welcome!
You have connectivity problem,to verify if the phone is establishing connection with pc via usb cable,get the phone into Bootloaders then connect it with pc through usb cable and check small usb appear at the bottom of the Bootloader screen,if its there,than its establishing,otherwise there's a connection problem.Either usb cable is faulty or the mini usb port of the phone is damaged.
...
Its written USB in bootloader and I can see my spv in device manager..
So I explain what I think.. Maybe theres only the bootloader of orange on my spv on no more wm5.. and I cannot flash only the bootloader..
If any idea come.. Already thx!
I installed an "updated" HTC Home Screen Plugin (obviously not for my phone model #) and now my phone is frozen. It will boot up but the home screen is frozen (i.e., non-responsive to any button presses). I attempted to re-flash the ROM using various ones I found for the NEON but all fail for the same reason.
Specifically, connection to ActiveSync is not possible (I connect via USB cable but ActiveSync doesn't recognize device). So what I do is put the phone in bootloader mode and then connect the USB cable. When I do this, the ROM upgrade program recognizes the phone and gets to the point where it shows the screen "Updating the ROM image on your PDA Phone.." and the phone shows a status bar at 0%. However, after a minute the computer screen says "ERROR [262]: UPDATE ERROR" and the phone is stile stuck at 0%.
My question is if there is any other way I can re-flash my NEON300? I've heard that it may be possible to but the nbh file on a FAT32 formatted card. I tried this by naming the nbh file to "TOUCHIMG.NBH" and "NEONIMG.NBH" but neither are recognized by the bootloader.
Thanks in advance for any assistance.
Try changing usb port or even re-installing activesync.
Alot pf people had the same problem on different devices but the cause should be the same.
for example, http://forum.xda-developers.com/showthread.php?t=298516
Let me know how you go.
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
wangobyte said:
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
Click to expand...
Click to collapse
You should have read the WIKI before flashing your device... http://wiki.xda-developers.com/index.php?pagename=Flashing Guide and here http://forum.xda-developers.com/showthread.php?t=355730
Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
I have the same problem!
I want to install HSPL on my device. I cannot install this via SD Card so i tried it with USB. But after the bootloader the connenction was lost. Many times...
Can somebody tell me how to fix this problem?
Thanks
Edet: My device is a HTC HD2
This might not fit your problem, but ...
... try to connect your device to a PC/laptop with USB 1.1 - with my Ameo I have many "connection loss" problems with USB 2.0 speed, which occure only on heavy (data) load on syncing.
Disabling USB2.0 is possible on some machines within the BIOS.
If you got no PC/laptop with USB1.1 you can disable the USB 2.0 related driver in the Windows Device Manager (it works for me, in general). Therefor open the device manager and select the "View" menu -> devices by connection (or similar). Now search for the Athena entry attached to the listed USB hardware. Disable the "most-upper" USB controller the Athena is attached to.
OK, the last description might be confusing, but try.
Good luck (as this solution fits to your problem, as I am not sure)
What worked for me
junooni said:
Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
Click to expand...
Click to collapse
I just spent the weekend trying to unlock my Athena and was having the exact same problem... USB would disconnect, errors 202, 267 . I finally was able to flash the Olipro bootloader, but had a hard time unlocking the radio. My device showed no radio under its properties, so I could not tell what radio version I had. Pressing "phone" would not bring the dialup screen. After so much sweat, I had to put it apart, only to find that the radio board connection to the motherboard was improperly seated, thus was having a bad connection. Once the connection was properly seated, the phone booted up to the emergency call screen, notified that there was no SIM card detected and when I looked in the device properties, the radio version was listed!. I then proceeded to unlock and flash the radio and this time the connection was not lost, the process completed without a glitch.
Hope that helps...