Cingular 8524, upgrade to 3.12.3.7, in Vista, getting 294 error - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

Alright so I am so frustrated with this...and I am sure there is a simple solution for it. The screen on my old 8525 got messed up and since it was under waranty they sent me a replacement...the screen is ok on the replacement, but the phone isn't working (shows exclamation point next to "wine glass" rather than signal strength bars).... after hours and several phone calls to tech support, High End Devices waranty dept and who knows where else, it was determined that the current ROM version is incompatible with the AT&T network, I have to upgrade. So the version of the ROM on the replacement is 2.15.502.3 which makes wonder why in the world would AT&T send me a phone that would not work on their network? (I'm really trying not to vent here...) Anyways so I go to the HTC website as directed by the Tech. Support person download the stuff and after another hour on the phone with HTC and every possible sollution that they know is tried still can't install. I am running a Vista 64 machine and after getting around all the Vista quirks I am finally able to get to the Bootloader screen (button combination is: Side button [Ok] + [Power] Then push [Reset]...if done correctly your phone goes to the 4 bar boot loader screen, if not your phone soft resets and you have to try it again...) anyways in the bootloader screen it goes to the installation bar on both phone and PC and goes to 1%, then durring that one percent I get the horrible "ERROR 294 : INVALID VENDOR ID" on the PC and the Phone resets.....No matter how we have tried it it is always the same thing...redownloaded the file 3 times, restarted the phone about a gazillion times and the PC about 2 or 3 times. What can I do? I would love to have Ms Windows Mobile 6, but all I really want is a working phone....can anyone please help?
Some more info for those of you that can help:
On "Device Information" screen here is what I have:
ROM version: 2.15.502.3
ROM Date: 04/09/07
Radio version: {blank}
Protocol version: {blank}
On Bootloader screen:
In the top (red) section:
(in white)
HERM100
IPL-1.03
(in yellow)
HERM100
SPL-1.11
and then at the bottom (white) section:
(in black)
USB
(it says Serial when I unplug the USB cable)
I am trying to install the ROM titled:
RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe
downloaded from:
http://216.139.227.230/download/Sof...502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe
found by going to http://www.htc.com, Support, AT&T 8525, Software Download.
Thank you for any help you can give.

u cant be serious......you got an invalid model ID from an 8525 while trying to install an update from at&t itself.
well the solution would simply be to install hardspl (see the sticky) and then install the update. although there are many other easier and faster solutions i think this is the *safest* way. but then the fact that your radio version shows nothing makes me wonder......maybe a corrupted radio or something, which may or may not be related to the invalid model ID error.......anywho, search the forums for error 294 its probably been discussed many times

First of all thanks for your help. So I tried installing the 2.10 - Hard-SPL-V7 and it wont finish the install. I connect the device follow through the installation and when I get to the point where I push Yes on the 8525 the screen goes to the red/green/blue/white bars screen shows
HERM100
IPL-SSPL by Des
HERM100
SPL-1.09.ds
then the Computer shows ERROR [260]: UPDATE ERROR and the installation stops....

error 260 is an open port error, reboot your computer, and try again, if it doesnt work, try a different usb port, also disable watever firewalls or antivirus software you have

Okay so I diabled both the firewall (Windows Firewall) and the antivirus (AVG) and restarted the computer...tried 3 different USB ports...still the same problem....You don't think it could have anything to do with Windows Vista 64 and Windows Mobile Device Center. BEcause as soon as I go into the new Bootloader screen, the WMDC shows that the 8525 is diconnected now...even though it's not. I saw a post on here about installing drivers to get Active Sync on a Vista machine, but the drivers it provides are unsigned and Vista won't let me load them....so what's the next step? And again thank you so much for your help.

Is there any use in putting more effort into this or should I just have AT&T send me a new one?

whether there's any use left is ur decision, dont ask me to help you make your decision.
i know you can install unsigned drivers on vista, i dont know how, use the search. i have also heard that updating wmdc to the latest version helps too.
or you can either try and install hardspl using the microsd card, again use the search.

Related

stuck in boot loader updating to 1.43 on black shadow

I was trying to upgrade to radio v1.43 in the hope that battery life was improved over 1.41 however when it got to 8% it stopped and gave me an error i can't remember After atempting to recover, it got off the three colour screen now the 3100 stalls on the blackshadow version4 screen (bootloader screen?) and goes no further. I tried reflashing but got a 260 and using mtty, only getting 2 com port options, didn't offer any help.
I'm really sorry to have not been able to sort this with reading through the relevant post but I haven't found a solution. What else can I try?
Hi,
Could you pls advise what is your device made, model, SPL version ... etc.
Also did you try to do Hard reset?
I'm using now black MAJIK (and few days ago black shadow) with radio 1.43 with no problem.
its the SPV m3100 When I decided to go Black shadow I read up on mr vanx and made sure I had all the things I needed. If I remember right, when I came to upgrade to Majik the auto detect found the second option down
SPL-1.04/1.10 - 1.09 Bootloader. I've realized since I had a spaz and ran the RUU from the archive this time. From what I've since read thats not too cleaver.
I have tried a hard reset and took the battery out instead of pressing space.
I dont know if this information on the starter screen is of use
M 05
S 04
B 05 D 3lak
I'm not sure, but hard reset doesnt mean you take the batery out.
Please check that link:
http://wiki.xda-developers.com/index.php?pagename=Hermes_For_Beginners#hardreset
I was in your position (hanged on booting) few days ago, and when i did hard reset, it changes every thing to basic normal condition.
i meant when i did a hard reset when it asked me to press space to reboot I took the battery out. I tried again this time pressing space to reboot but I still get stuck on the loading screen. I can't connect by USB to the PC I'm guessing the drivers on the phone haven't loaded and I'm stuck as to what to do.
Does anyone have any ideas?
try look at it http://forum.xda-developers.com/showthread.php?t=286755
ok I've tried everything I can think of to connect the 3100 to the computer so I can reflash it but mtty gives only com 1 and com2 but no USB and neither those two work, active sync wont connect so I disabled it as suggested and running the radio ruu and wrapper wont querry the device. I am now at a loss as to what to do next someone must know what I should do. Please?
what is your SPL?
try this http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
sl is 1.09 i'd updated it on the previously successful black shadow flash
msn [email protected]
icq 150277111
AIM TazmanFH9
Yahoo bigfathairyboggart
I have tried changing KITL trasport but I am unable to select or chose either option. I have also tried the rversion command in the tri colour screen but nothing happens. I hope I'm missing something nice and simple but I get the feeling I'm not going to be that lucky. Please help
tcSPVm3100 said:
sl is 1.09 i'd updated it on the previously successful black shadow flash
Click to expand...
Click to collapse
I suggest you check again, press and hold the side OK button and the power button...then put the stylus into the hole in the bottom of the unit.
yeah I've done that it's "SPL-1.09"
I had this exact problem yesterday, with the same bootloader too. The phone would not pass the splash and IT refused to upgrade. I ended up downgrading to a shipped wm5 rom (in my case the cingular 1.30.502.1_1.11.00.00) which to my surprise actually worked as no rom radio or spl upgrade moved at al on my phone. Then upgraded back to black majik. I hope this helps.
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
tcSPVm3100 said:
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
Click to expand...
Click to collapse
Just download a WM5 ROM from the wiki page!
ok tried this too no luck.
Trying to use the one from orange (linked to through wikki) I get an 294 invalid vendor error however active sync cannot connect yet of course so is this to be expected?
I have however gotten a connection with mtty which is a step forward dunno what to do with it yet though except trying the password 0000000000000000 command but it not disabling the password. This then lead me to read for a further hour how to change it and I've got to be honest; it beat me. I have No idea what the hell its talking about. My head hurt with so much reading.
I get a no gsm pop up v briefly on loader. I so want my phone back
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
tcSPVm3100 said:
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
Click to expand...
Click to collapse
can u flashing HARD V7?,i think better u have IPL 1.04 SPL 2.10olipro first ,then try to flashing radio?
and did u try SD card.
In bootloader can anyone here connect with active sync? I can't so updating rom and radio flashes in the usual way isn't possible. Trying the hard spl again it tells me to make sure active sync is connected and as it isn't it throws back a 262 update error. 0% on the hermes and that's currently as far as I can get. I have no means with which to access the memory card.
The reason you get an invalid vendor ID is because your CID doesnt match....download a ROM which is for your device (an orange one?)...then try.
You need to read the wiki alot more before trying anything else since you are not aware of the vendor ID error...nor the fact you MUST use HardSPL.
I linked to the orange ROM from wikki and tried installing it. it was while installing THIS ROM SPV_M3100_ROMUpdate_0407.exe I got invalid vendor error.
Installing a recent DL on HARD spl v7 I get a 240 open file error that's one I haven't had before.
With all other attempts they all say they want an active sync connection.
I can not connect to the phone through active sync
so all attempts by me to flash anything to the phone using an RUU fails.

SPL flash failing

I'm following Mr Vanx's guide for upgrading my Jasjam from WM5 to WM6, but am having trouble with flashing the new bootloader onto the device. It's a second-hand telstra imate. I just bought it off ebay a couple of weeks ago and need to upgrade it to get it to read sdhc memory cards. I can't get it to connect to optus' (my mobile contract provider) mobile internet either, which I did via GPRS on my old phone. I'm hoping by upgrading the OS I can remove all of Telstra's code so It's not trying to connect to telstra's 3g network when I start the web browser.
When I get to the last step of the Hard-SPL installation, where the "updater will flash the new SPL and then restart your device (this will take generally less than a minute)" , the phone restarts almost immediately after clicking yes when prompted on the phone. The screen quickly goes to the bootloader screen, which says
"herm 100
IPL-SSPL by Des
Herm 100
SPL-1.09.ds"
The PC says that it can't connect to the phone and I should check the cable, which is still connected
The phone stays on the bootloader screen until I hit the soft reset, and WM5 boots like normal.
Has anyone else had this happen?
Yup,
Same problem over here. I had the problem before. But i fixed it! The only question is how did i do that? short term memory.
I'm trying to solve the problem. If its solved i will let you know.
Till then hang on
I've been trying again today. Still getting the same result, though I figured out if I just leave it when it gets to the bootloader screen, the pc I'm installing from eventually comes up with Error 260.
I'm thinking now that the XP firewall may be the issue, but I'm having trouble disabling it because it's managed by "group policies" (it's a work computer). I'm going to try either finding out which port to unblock, or starting the pc in safe mode so I can disable the firewall altogether.
I fixed the problem with the following softwaretool Hypercore. Just intergrate the Hard spl from olipro. After this the error dissapears.

help required

Hi guys,
I've got a T-Mobile MDA Vario 2 (Hermes).
i used the "HTC Hermes SIM & CID Unlocker *New* version v3a" tool so i could then load any ROM i want. I followed the instructions perfectly and then ran the unlocker, and that went fine too, however, when i'm trying to change to a particular ROM version, it gives me a "error 101 : Connection Error" after it tries to check the status of the device......it gets to the tricolour bootloader screen absolutely fine and the screen shows the following -
HERM300
IPL - 1.01
HERM300
SPL-1.40Olipro
It sits saying 'Checking the information onyour device..........please wait' for around 2 minutes, then kicks back and gives me the "Error 101 : Connection Error".
I have tried the search function, but there's not a lot i can find on the problem.
Can anyone help?
Thanks
Mark
That drove me crazy too until I finally found a post on another board explaining what to do.
If you notice when the updater is running, your activesync program will exit. Immediatelly restart activesync when you see it exit. It will not reconnect to your device, in fact it will show not connected but that is ok. The ruu is only using the activesync program, not to actual connection to communicate with your device.
I actually created an easily accessible activesync icon on the desktop of my PC so I can restart it quickly. Watch it closely, I have had the activesync program exit up to two times before I ever get the installation underway.
I guess this is normal, based on what I have read elsewhere.
Hope this helps. Let me know if you are successful with this method.

My 7500 with 6.5 on it...please help.

I'm new on the forum, very informative but I could'nt find an answer to this situation. I have a HTC Advantage 7500 that originally came with mobile 5 on it and last year I successfully upgraded it to mobile 6. Couple of days ago I wanted to try something new so I upped it to 6.5 via a link on this site somewhere. The rom update went smoothly but I would like to go to 6.1 because for one the micro drive is not seen under the 6.5 that I have plus it has a slow response to screen manuvers and such. Now when I try to install mobile 6 or 6.1 it says please wait while the update takes place but my device restarts and the error #260 box comes up that says the update utility cannot connect to your PDA phone. Please check your USB connection. I would appreciate any help or suggestions. I know maybe I was wrong to try the mobile 6.5 on this. confused:
Since you are able to use 6.5, (it was a spl 3.5 version unless you
had found and used a spl 1.2) your phone should be having spl 3.5.
You need to search and download 6.1 spl 3.5 rom to change it.
Oh...Welcome!!
pdajoy said:
Since you are able to use 6.5, (it was a spl 3.5 version unless you
had found and used a spl 1.2) your phone should be having spl 3.5.
You need to search and download 6.1 spl 3.5 rom to change it.
Oh...Welcome!!
Click to expand...
Click to collapse
Thanks for your reply. I do now have the file 6.1 spl 3.5 but my device on 2 separate computers it just starts the update restarts my 7500 then the error message about USB connection. I didnt get this error the last 2 times I updated my device. Thanks in advance.
Taking it your pc (Windows XP) with anti virus and firewall disable.
Try flash back previous rom and have the device working first before going
any further.
Best to use same usb cable and port from same computer for your flashing. It helps to isolate problems in future.
Ensure device battery charge is above 60%, at least.
Remove SIM and memory cards before flashing.
I am sorry to hear that you're having problems with your device......however, the problem you've mentioned sounds quite familiar to me but I don't remember how I actually got mine fixed.
I have no idea what OS you're using but
try this:
re-installing activesync/device center then put your device in bootload mode (by holding down the camera button...fully....then press the reset button, keep holding camea button until the colored screen comes up. connect your phone to your computer and let it install the usb drivers.
after thats done, unplug, wait....replug and start up acticesync/device center make sure they're connected/synced then try changing the rom again.
hope that helps.
Thank you all so much. I did these things and it still restarts and goes right back in mobile 6.5 giving that same error message #260 box comes up that says the update utility cannot connect to your PDA phone. Please check your USB connection. Can it be a bad usb cable I'm using I wonder? Interesting my SPL version right now is 1.10.
that's the problem...your SPL should be 3.5 if you're on wm6.5. it is interesting that you got that instead of "invalid Model id" error. all in all I think the same method should solve your problem.
do a search for "invalid model id" and check out the post by cmonex she did a great job in creating a salutation. hopefully you had Hard SPLed your phone and that you had a home network that you had connected your phone so you can get back your phone's MAC address.
EDIT:
Also change your USB cable....I don't trust it, it's possible that it could be the problem. however, seen as your SPL isn't what it should be it the cable is not the problem (but change it anyway)
lennie said:
that's the problem...your SPL should be 3.5 if you're on wm6.5. it is interesting that you got that instead of "invalid Model id" error. all in all I think the same method should solve your problem.
do a search for "invalid model id" and check out the post by cmonex she did a great job in creating a salutation. hopefully you had Hard SPLed your phone and that you had a home network that you had connected your phone so you can get back your phone's MAC address.
EDIT:
Also change your USB cable....I don't trust it, it's possible that it could be the problem. however, seen as your SPL isn't what it should be it the cable is not the problem (but change it anyway)
Click to expand...
Click to collapse
Thanks so much! I will do this. I wonder why I have a spl 1.10? This is confusing with Win Mobile 6.5?
lennie said:
that's the problem...your SPL should be 3.5 if you're on wm6.5. it is interesting that you got that instead of "invalid Model id" error. all in all I think the same method should solve your problem.
do a search for "invalid model id" and check out the post by cmonex she did a great job in creating a salutation. hopefully you had Hard SPLed your phone and that you had a home network that you had connected your phone so you can get back your phone's MAC address.
EDIT:
Also change your USB cable....I don't trust it, it's possible that it could be the problem. however, seen as your SPL isn't what it should be it the cable is not the problem (but change it anyway)
Click to expand...
Click to collapse
I am using a new usb cable and the same thing happens. It says its starting to update the rom then it restarts my 7500 and error 260 comes up saying that it cannot connect to my device check your usb connection. I don't understand...

How do you load a ROM from tricolour screen?

Am having a problem with unlocking a Hermes using the SIM_CID Unlock version 3A
I appear to be stuck in a loop with the unlock process. I appear to have got as far as having installed OliPro (while still being at bootloader 1.01) but keep getting error 262 UPDATE FAILED
I can then recover to the tri-colour screen and process as far as RECOVERY SUCCESSFUL
But I cant get as far as updating the radio or whatever else it unlocks towards the end of the process and no new ROM loads (if that is what the unlocker does?) The percentage screen appears but doesnt progress at all. Then I get ERROR 262 again.
Is starting to the bootloader screen a sign of a bricked Hermes? I can get SERIAL to show and can get it to change to USB on that screen when I plug it into a computer but cant get any proper communication with the unit from the computer with that screen in place: ActiveSync obvoiusly wont start. As I left the 3A unlocker, it said RECOVERY SUCCESSFUL but does that necessarily mean that I have a brick now? I thought that the installation of olipro by SIM_CID unlock version 3A means that the unit is now hard-unlocked?
(Yes, I did try Hard-SPL-V7.zip but cant set up any communication between the exe file and the tricolour screen)
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
I thought that tricolour screen meant that it is ONLY starting in bootloader mode?
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I am a bit lost: How do I get into bootloader mode? I thought that it starting in the tricolour screen meant that it had started up in boot loader mode? Is there some combination of pressing buttons and 'on' switches like on my Blue Angel?
As it appears to have got stuck in a mode while in an upgrade process which didnt work when this error occurred, when I get it started, what should I flash to get the bootloader updated, the SIM and CID unlocked so that I can choose which ROM to flash? Should I continue with the SuperCIM_CID unlock or Hard SPL?
I have fully unlocked another Hermes before and have been playing around with ROMs but this one seems to have worked out differently: I was under the impression that loading OliPro meant that it was unlocked?
(Sorry about that answer: I will try RUU_Unwrapper.exe again)
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I did what you said and immediately I unchecked the tick in USB, I heard that the computer was establishing communication with the Hermes
But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??
V7 still wont run but v3A still will!
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: This device both will and wont coopeate at the same time. But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE on error 260\.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: (Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
(Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
The computer IS communicating with the device (as I said it does give the 'ding' showing that the computer knows it is there) but it wont hard reset! It just goes straight to the tricolour screen immediately on startup. Even using a three hand method of pressing both buttons, pushing the reset in and putting the battery in at the same time gave the tricolour screen. And Windows Explorer cant get into the device. It seems to see it but there is no tree at all. So I cant use the Post 1160 method to flash from an SD card.
Even more baffling, i have now flashed a stock ROM successfully and v7 STILL wont communicate with the Hermes!! In desperation I even moved the directory to the root of C: Are some of these devices encrypted differently from others? So suddenly it boots properly and I immediately did a hard reset and erased everything and now Guess what? It hangs at the Windows Mobile screen! Needing a hard reset all over again
Should I just keep on trying Super SIM and CID unlock again and again until it works? (I assume that I have no longer got OliPro on it, though it does show a SPL of 1.40) There must be a way of unlocking this unit but this total non-cooperation doesn't seem to be covered in the Wiki. Is there a version of the Hermes like the Wizard which is more difficult to unlock than the others?
Sorry to reply again when no one gave any ideas on my last posting but I am wondering, horror of horrors, whether this might be a hardware problem?
I am now stuck at the tricolour screen ( 1.01, SPL 1.40.Olipro)) which turns on whenever I put the battery in. Connecting to the computer doesnt make any difference and obviously I keep getting ERROR 260 which seems to be a connection error meaning that the computer either isnt connected to the device (or that some software is conflicting somewhere, which is unlikely as flashing to the stock ROM did work before I tried to run V7 again)
Is there any possibility that running SuperCID&SIM unlock (which has never completed) caused all of this and is there any rescue procedure or should I just assume that this is a hardware problem now (or should I do a fresh posting)?
Is it inherently suspicious that tricolour turns in when I just put the battery in AND that even though SERIAL changes to USB on the Hermes, running the v7 hard update utility causes ERROR 260? [Or cant you run V7 when you already have OliPro installed somehow?]
There IS communication: Though I reported in my last posting that I could flash the Cingular ROM, flashing to the Cingular ROM now gets consistently stuck at 14%, sometimes with an ERROR 264!

Categories

Resources