trying to flash rom, need help - HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting

I the same error as this post, or i think it looks like it
http://forum.xda-developers.com/showthread.php?t=1548255
anyways I pmed him for help but until then I'm trying on my own. So far flashing from sd card proves impossible
I managed to get it to get to the flashing screen running stock rom exe but it's stuck at 0%. So I can't flash with sd card and running from my computer doesn't move past 0%.
Just wondering and hoping I don't have a bricked hd2 . I'm trying to get mtty to work but I can't get it to find USB to connect to, I've installed the drivers (I'm using Win7) but it still can't recognize the phone. I'll try to find a winxp computer later if I can and try it on there
edit: got mtty to work, the task 2a didnt work :S any other ideas? I did notice that I have bad blocks in it that it wouldnt fix

Related

upgrade rom sd card??

hi, i am new on this, this is my problem:
i upgraded the xda 2 from 2003se to wm2005. and now i cant syncronize whit activesync. There is a way to upgrade a rom via sd card?? please help me whit this
never heard about anybody managing it
but even if it will not sync with activesync it should be able to upgrade by bootloader
hi, every time i put it in bootloader mode an error display say that is not detecting the PPC. What i have to do??
no detection
Rene-357 said:
hi, every time i put it in bootloader mode an error display say that is not detecting the PPC. What i have to do??
Click to expand...
Click to collapse
i think your using an incorrect ROM or your using the incorrect phone/unit. this is for himalayas/ andes. i think youmay be using a rom for something else or your phone is something else. correct me if i'm wron seniors....
nope, im very sure that my phone is a hima, and the roms are for hima to. or O2 XDA II
hi, i have exactly the same problem for month, i didn't manage it by now, there mus be way, just keep asking and tell me when you get it
please can someone upload image of sd card prepared for flashing?
I have same problem, in nomal mode and bootloader mode my PC cant recognize my himalaya,
in Device manager my himalaya detected as UNKNOWN DEVICE,
i tried in several PC's but got the same problem,
nt : i use pcsync v 4.0 , 4.2 and 4.5 but
i think its an hardware-error,,
as i said before as far as i know nobody here ever managed to flash their himalaya from a sdcard
one reason it dont work with usb could be a bad cradle or connector
had plenty of those where i had to wiggle with them to get connection
here http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderSdCardFlashing is "how to" flash hima from sd card, so it is possible, unfortunetly i cant connect via usb, so i cant prepare sd card. Btw i think it is clearly software problem in my case, i flashed some bad version (it was for hima), since then problems has releasing, my sms client break down, usb down, canot install corectly many programs, etc. So please, make someone image of prepared sd card, it will be usefull for many others, now my hima is nothing than brick
a sdcard reader is only about 10€ can that not be used?
no, command for backuping rom to sd card must be entered from terminal program from pc using usb
hi, i tried whit some pc,and is the same nothing works.its something whit the rom, because everything started in the upgrade. please someone help us!! if anyone get the sd image please reply here
ANYONE who have hima and right-working os on it can made os backup to sd. It is just three commands as i hope, minute of working, so help pls. Just get mtty (//http://wiki.xda-developers.com/uploads/mtty.exe), connect ppc to pc, and type these (http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderSdCardFlashing) commands.
think here is absolutely clearly guide
http://wiki.xda-developers.com/index.php?pagename=BackupExistingRom
i cannot open by mtty, every time i try by mtty says that i cant open usb port. how i do that??????
you cant, same as me, it must be done by someone with working usb
i cant sync via bluetooth either
i found at ALPIN board very simple using sd-card methode,
http://forum.xda-developers.com/showthread.php?t=341564
maybe next time will able for xda-II that have error connection
yes, of course this method can be applyed for xdaII as well, but still, there is problem that noone is enought willing to do backup image that he don't need for his own reason.

Error 260 when upgrading

First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
okeven said:
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
Click to expand...
Click to collapse
Try a different USB port first, fire the device into bootloader mode manually and see if the device is detected by windows as "HTC USB SYNC"........use a hardwired port NOT a USB Hub aswell.
I tried a different USB port. It is not being plugged in to an external USB hub. I went into the bootloader screen and my computer makes the sound that a USB device was plugged in and it does show in the device manager as "HTC USB SYNC". What now?
Now try to do an update, Sounds like a problem associated with the connection of the device to your machine...usually caused by messed up USB drivers or a conflicting program.
Just tried. Same error again. Tried restarting the computer and tried it again. No dice.
this is the answer
hey man, how u doing. I was getting those errors too, I actually have a Tilt, I got error 200, and 260 trying to change my rom, I was about to give up. then I tried something I didn't think of, I updated my device center software from Microsoft and then miraculously everything worked after that. If you have XP update your Active sync software to the latest one and everything should work after that. Hope this helps.
and one more thing, make sure you install HardSPL v1 (or later when its released) first before trying to install the ROM.
I don't think anything is wrong with your usb drivers
I had actually checked to make sure I had the most recent version already and I do. I cannot install HardSPL either, since it gives me error 260 there also.
Error 260 is an open port error... I believe you have already tried resetting your device, but have you rebooted your pc prior to this procedure... I am grasping at straws for you, since you said you have tried soft resetting to no avail... I believe MrVanx stated to put the phone in bootloader mode and try to run the update utility that way... It works for me...
Can you try this on a different pc? If so, does it work? I have a post on another forum that you might find interesting... I did not compile it on my own, but cannot recall where I got it from... anyway, the link is HERE...
Hope this helps you out...
I have restarted the computer multiple times. I just tried it on my laptop and that did not work. I can boot the phone to the bootloader, but how do I install it from there?
That should be the easiest part... once you have it in bootloader mode, connect it via usb and then launch the update utility...
I get error 260 doing that also. argh!!!
i know how u feel
i had your problem several times. you want to know how i fixed it?
i didn't...
first i tried everything you and the guys mentioned and... nothing. then it worked the next day by itself.
the second time i couldn't connect i was really mad because the errors came sporadically. i tried installing AS, uninstalling, hard resetting the device, changing usb ports, anything logical and illogical and it worked on changing usb ports (but not on the first change).
now i'm at my girlfriends, had no problems until i saw farias new rom and wanted to flash it. guess what connection error
p.s. i've read trough and trough, but i've found no solution
what version and OS?
okeven said:
I get error 260 doing that also. argh!!!
Click to expand...
Click to collapse
yeah, I thought u would dget that again. i don't believe the error is originating from your phone, its more from the computer. what operating system are you using and whats the version number for activeSync or MS Device Center you are using?
I had that error on my home pc and on my girlfriend's laptop prior to updating my device center software. My pc is running Vista ultimate x64 and my girlfriend's laptop is running Vista Home Premium x32. I'm on her laptop right now, the version of device center is 6.1.6965. when I get home I will see which version is on my computer, I remember seeing "beta" on the one I got at home, lol, I didn't know Microsoft sent out beta software through its msupdate.
okeven, someone replied with good suggestions to the thread that u accidentally started over in the kaiser forum. you might want to check that out
I have version 6.1.6965 also. It does not say anything about it being a beta version, but with Microsoft, isn't everything in beta stage?
I did try the "official wm6 AT&T" version. Upgraded just fine. Tried upgrading to another one. Failed with error 260. What is different with the official upgrade program compared to the unofficial ones. THAT is the problem.
help
hi guys,
i have the same problem always the code 260, and also, my tytn's screen become within light, and without any boot number, ni radio, anything appears, please help me,,
thanks,
Finnaly
Hi guys
I also have the 260 problem but i resolved it:
1º- connect pda and make a active sync connection
2º run RUU
3º the 3-color screen will appear and update will stop with the 260 message error. be sure you can install the "qualcomm cdma technologies msm driver" at this moment, by an internet connection.
4º after the driver is installed, the word "USB" will appear in the white strip of the 3 color screen;
5º run RUU again and that´s all!
I´ve tried it in windows 7 ultimate 32-bit
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
lxlx said:
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
Click to expand...
Click to collapse
Hermes use HERMIMG.nbh ... kovsimg.nbh is for Xperia X1 ..
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm

well... i got stuck real fast =_='

wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeForBeginners
i followed it very precise after reading evrything through twice..... and when i run " Easy Hard-Spl v7 beta v0.1" it says: "ERROR[260]:Connection. the update utility cannot connect to your PDA phone. please check that your usb cradle/cable is connected properly between the PC and your PDA phone. check the following, 1that the PC is connected to the PDA phone, 2 that the PDA phone is connected to the pc".... and it is... so what have i done wrong?
260
make sure you dont have the sim card in i have gotten that error from that also you may want to try and flash a stock rom first if you cant find it heer go to either your carriers web site or HTC their sight has many stock roms. ive been doing this a few years now but i am no where as good as most of the ppl here. good luck
didn't work, and now i tryed to do that pc sync as well ono doesn't work
do u have active sync or windows devive center on your computer ? have you been able to connect and view files on the phone through your computer using any of these programs? if so have you gone to htc and tried to flash the stock rom? you must remove sim card and memory card. next do a hard reset use the stylist and stick it into the tiny hole just to the right and slightly above the usb port then follow the instructions on the screen. after that connect the phone to the computer and link to active sync. then reinstall the stock rom. let me know how that works after that you should b able to flash hard spl then download it and just open it on computer it will install on the phone by itself dont load on memory card or phone memory directly let it do it through the computer.good luck let me know how you make out good luck
ps i know it may sound silly to reinstall origonal rom but sometimes there can be a corrupted file preventing you from upgrading, and its good practice lol
Does your phone can run the windows?
I mean does your pphone boots correctly?
or it is in the tricolor screen?
if it works, why you are trying the that new HSPL?
use the olipro version V7
be sure your PC has netframeworks 3.5, your phone dont has the storage card, have enough battery, good usb cable, and Windows XP.
if your device cant boots and its in tricolor screen... please search in the wiki to your country Stock rom and falsh it.. once it boots... apply the HSPL
+ Que PPC...
as you are the master of the hermes maybe you can help me i have a herm 100 that wont get past the screen align on any rom. you tap the X in the corners then it comes right back. i think it may be the radio but i cannot find anything that will work and stock rom doesn't go past 11% on install. spl 1.40. olipro ipl-1.01 m 05 s 04 B o6 . it does connect to active sync and i can open all the folders in it. all the links to radios are dead and i think i have to down grade spl first to install radio but i cant find that. anny help would be great. ive flashed the hell out of my fuse kaiser and pure and no problems but i rely liked this old phone and want to bring it back to life

[Q] Is this a brick, how do I fix

I was trying to flash 2.2 over Bionix with the custom kernals, didnt work and for someone reason the phone wont recognize sd cards anymore either.... tried 3 and none worked.
I get to the stock recovery and it will recognize the adb thing but when I enter that odin thing my computer doesnt notice the phone.
Anyone got any idea what I should do?
RPGbig said:
I was trying to flash 2.2 over Bionix with the custom kernals, didnt work and for someone reason the phone wont recognize sd cards anymore either.... tried 3 and none worked.
I get to the stock recovery and it will recognize the adb thing but when I enter that odin thing my computer doesnt notice the phone.
Anyone got any idea what I should do?
Click to expand...
Click to collapse
Install the drivers relevant for your PC from the ODIN thread and give it a try, try changing the USB ports. Many of them on these complained about this, patience helps. Make sure, you reboot your pc between, uninstall of drivers.

Help!! Can not flash any ROMs

All sorts of issues here.
I am no longer able to install new ROMs on my Aria. In the past I have flashed many ROMs on the phone. Recently I flashed an ICS rom but I did not like the way it was working so I went back to Cyanogenmod 7.1 RC1. Now for whatever reason, I am unable to flash any other ROMs. I put the new rom on the SD card like I always had then boot to CWM, go to install from SD card and it says that there are no files there. Which is not true and its not the SD card because I can still see the files with a file manager. When I select the ROM from inside ROM Manager it goes through the process but stops shortly after starting the install. I have heard that using a different version of CWM may work but when I try to download one from ROM manager it says an error occurred when trying to download. Also when I hook the phone up to my PC it doesnt recognize that it is plugged in other than its charging. (yes it is the original USB cord and USB debugging is on).
A few details: This phone has never connected with my current/new PC. It did work at one time with my old one. While trying to fix this I did a complete wipe of the phone, the first time I hooked it up to my current PC I got the whole new hardware detected thing on my PC and USB debug was active on the phone, but I don't know if I accidently hit a wrong option on my PC but it went right away and has never connected again.
I also noticed that the phone is S-ON, I thought/assumed it was S-OFF before. Could it have some how turned back on? I cant get it back off now since I cant use ADB without USB Debug connected.
I no longer use this Aria for daily use (replaced with One X ) so I am open to some possible "extreme" ideas of trying to fix this.
Thanks for any help. This is driving me nuts.
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
drumist said:
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
Thanks. I will give that a try.
drumist said:
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
Install this first: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try running the RUU again.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
I have tried installing that before (tried again this time too) and it doesn't help. I still have no connection to the phone. I have Windows 7 if that helps anything.
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
drumist said:
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
Click to expand...
Click to collapse
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
chadd74 said:
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
Click to expand...
Click to collapse
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
drumist said:
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
Click to expand...
Click to collapse
Well,sort of good news here. I had tried different USB ports before but thought I would give it another go, it still was not connecting. So in a bit of a fit of rage I took the micro usb cord at shoved it quite hard into the phone. Well the connection flickered. So it appears over the years the USB slot had gotten a nice amount of pocket lint or whatnot jammed tight in there to where it would connect enough to charge but not enough for a PC connection. I cleaned it all out the best I could and what do you know, it worked.
Foiled by pocket lint.... SMH.
I loaded the 2.2.2 RUU and will give the rest of the problems a go tomorrow and post an update. Thanks again for all the help.
Looks like everything is working like it used to.
Thanks again.

Categories

Resources