I've been using nueSPL 2.47 for a while, along with DCD 3.2.6 and the 3.42.50 radio. Then, yesterday, when I did a soft-reset, it went into the boot loader. Any subsequent attempt to boot resulted in the same.
When I plugged my phone in to my laptop via USB, I hit the reset button and it booted fine. Everything would function normally.
So, I thought maybe it was nueSPL 2.47, even though it had been working fine for a couple months. I went back to 2.40, and had the same symptoms. I have since returned to a relocked stock radio and ROM (sprint's newest - _HTC Mogul (Sprint)_RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_TITAN_3.42.02_SPCS2.04_PPST_0718_Ship).
It exhibits the same behavior. I then tried going up to DCD with 2.47 and 3.42.50, and back again: same behavior.
Now, I've read about similar behavior and the titan_exitbl solution. No matter what the state of my phone is in (boot loader, or booted up) with USB connections disabled on two seperate vista machine machines, the titan_exitbl program throws the same error: 'Cannot open the USB port... Make sure activesync is disabled, etc.'
I can use my phone, but should it ever need to be reset, I'm out of luck unless my laptop or I carry my power cord with me everywhere. Any suggestions?
Resolved in a way
So here's an update: I called sprint tech support and they were pretty much lost. They suggested I take it into a local sprint authorized repair place. The guy there looked at it for about a second before saying that He'll send away for a new one for me. (Free for me because I have the insurance).
So, if you have a similar problem ever, take it to the sprint store.
Related
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.
Hi Folks,
I'm stuck in the tri-color screen for bootloader 1.06.
I have DCD 3.2.0 w/3.42.02 radio on the XV6800 and was trying to upgrade to radio 3.42.30. My system is Vista 32-bit.
I ran the Titan Relocker and it put SPL-1.06.0000 back onto the device and was planning on then putting 1.2 onto it.
Running titan_exitbl.exe says "Cannot open USB port. Please make sure, that USB connection in ActiveSync is disabled."
Unfortunately it is now stuck and even after ending the Sync Center service I can't get titan_exitbl.exe to pull it out of the Boot Loader.
Ideas? Thank you!
I could fire up an old XP laptop and try it from there.
Loaded ActiveSync 4.5 on an XP laptop, disabled USB connections, ran titan-exebl.exe and the device is booting now.
I'll continue on and see what else I can screw up.
Loaded SPL 1.20
Loaded 3.42.30
Loaded SPL 2.40
Device is back to working! Off to see if GPS is back after being lost with 3.42.02.
titan-exebl.exe
Where can I find titan-exebl.exe? Google doesn't turn up any results other than here?
titan_exitbl.exe
Never mind... just located it on my own hard drive!
Cheers!
Stuck on Bootloader
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Try changing your spl back to 2.40.
Throwing it back into the tri color screen again and flash the sprint stock 3.35
But put it on the root of a fat32 formatted micro sd card in the flavor of under 2gb.
Just run the exe from your computer it will extract the files from the exe to some location on your computer, normally the ruu update folder.
There will be a ruu_sighned.nbh file locate it and copy it to the fat32 formatted card rename it TITAIMG.nbh
Let the phone boot into the bootloader and it should detect the file on the sd and update the rom for you, by stating loading ......
Then will prompt you to update press power key.
Sense you are not on sprint don't let the first time custimizations run ... pull battery once you get to your mobile today screen on first boot...
Use active sync or the sd method to update your rom to whatever you wanted originally.
Most full updates from carriers the ones that flash both the radio and rom will run regardless of the boot loader thats on the device.
Happy flashing
Just thought I'd toss in here that GPS does work, but I have to use GPS Viewer to get a lock on the satellites first.
softwind said:
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Click to expand...
Click to collapse
please i have this problem how to fix this?
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
drewcam888 said:
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
Click to expand...
Click to collapse
Thanks!!! Ok, i cant remember eactly what is the v radio but i think 3.35 or 3.42 i cant remember exactly it's one of these. the SPL 1.06 Locked i cant unlocked i cant use titan_exitbl.... the SD update doesnt work stuck on loading.., i cant update from pc stuck 0% then Recovery Error help me. I My phone is bricked? Sorry for my english....
Did you try to install 2.4 unlocker?
drewcam888 said:
Did you try to install 2.4 unlocker?
Click to expand...
Click to collapse
Yes, i try from SD and nothing stuck on loading... from windows with RUU nothing 0% stuck and then UPDATE ERROR[262] now i don't know to do
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
drewcam888 said:
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
Click to expand...
Click to collapse
Ok, but how run from windows? If i cant connect via activesyncs the phone is on SPL mode i cant out of that and the msdos windows say "No device conected" when press enter from windows i cant unlock. Any idea? I'll try 2.47 but how run from windows with the phone en SPL Mode?
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
drewcam888 said:
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
Click to expand...
Click to collapse
Look i cant run Hard-SPL-MFG (Olipro 2.40 Unlocker) because when i run the Bat Or MSDOS Windows say "No device connect" question me if i want retray copy the file.
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
drewcam888 said:
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
Click to expand...
Click to collapse
No luck, method A SD Card Loading.. then cheking... then show a number corner 00028002 and say down Not allowed.
Method B, via PC and RUU then ERROR INVALID VENDOR ID.
Any idea? Thanks bro.
I think my phone is bricked... noway load the rom... i've tried load bootloader unlocked via SD last option and nothing!! damn this is so
I made an attempt to what I thought was an upgrade to my x7501, i have wm6 i wamt 6.1. I ran the unlocker oilpro and the phone seemed fine, then I rebooted the device. I never noticed any thing other than a program that installed on the phone. The oilpro never completed. Now I can not start the device. it seems like i have no power. I have $300 to the person who can fix it this week. I live in washington dc and I need this phone fixed. my email is [email protected] no bull ****ters please, I dont have time. there is no 3 color bars etc...
Hi,
After using athena_unlocker, my X7500 also ran black after reboot without any loading screen, but since the x7501 is now supported by athena_unlocker (I presume you've downloaded the latest version at XDA), it should be possible to re-update a x7501 ROM.
You should at first try to download the original HTC x7501 ROM and re-update your device:
http://download.america.htc.com/RUU_Athena_HTC_US_2.19.453.4_105_1.47.51.00_Ship.exe
or one of those ROMs at xda (which are for x7500, though)
http://forum.xda-developers.com/showthread.php?t=314672 ; reply#4, I used T-MOB005 - version with spl,ipl and etc
- press power on button on the x7501 for at least 3 secs even if you can't see a thing
- connect x7501 with USB and make sure that ActiveSync is running (of course, it won't connect!)
- start ROMUpdateUtility.exe from the downloaded ROM-version (you must have administrator rights)
In case the ROMupdateutility doesn't find the x7501 (connection error, still black scren), try the following:
- press the camera button on the right, hold it and press reset button for some time - the boot loader screen (Olinex v1.20 in your case) should appear, then you can proceed with the original ROM re-update.
- accept all warnings and update, with me, it did connect and updated the ROM since the SPL had already been installed by the unlocker before (just no ROM => black screen)
Afterwards, my device at least started again so I could finish the unlocking process, it finally worked.
I can only tell that it worked for me 2 times, first original ROM => Olinex SPL1.2 => Athena AP4.0/Olinex SPL3.5, in both cases the same black screen occured (however, the bootloader is already installed on the device, so an update will work). It seems that the boot loader has some problems to upload the ROM itself, so only the new boot-loader version is on the device, you have to upload the ROM separately...just give it a try.
Regards,
Will_990
hgreen70 said:
I made an attempt to what I thought was an upgrade to my x7501, i have wm6 i wamt 6.1. I ran the unlocker oilpro and the phone seemed fine, then I rebooted the device. I never noticed any thing other than a program that installed on the phone. The oilpro never completed. Now I can not start the device. it seems like i have no power. I have $300 to the person who can fix it this week. I live in washington dc and I need this phone fixed. my email is [email protected] no bull ****ters please, I dont have time. there is no 3 color bars etc...
Click to expand...
Click to collapse
Remove sim and SD card
Remove battery for few mins then replace battery(sometimes it doesn't seat properly)
Plug in the mains charger and see if the charging light comes on.
If so try to boot into bootloader.
If you see the tricolor screen, connect to the computers usb port and run the original rom from the links above.
Good luck
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!
[Q] I don't want to say "Bricked"..but it sure is "very uncoopertive"...HELP
Hello HDGods,
I sure hope help will be available; i've now spent hours going thru the posts and can't seem to find a working solution to my problem. Basically, my HD2 won't boot.
Story: Italian HD2 unbranded, "H3G" sim, bought 2nd hand about eight months ago. Wanted WWE so I decided I'd try my luck with a cooked rom only a few days after getting the phone. Installed HSPL, 2.08.50 Radio and LIA_ROM _Series_V1.7_23563_Regular_WWE...It worked beautifully for several months; as time went by, I installed several apps (Tomtom, quick GPS, TCPMP, tried installing manillaTV with no success, + a few more apps bundled with the ROM). A few weeks ago, I began experiencing freezes and self-reboots. Sometimes the phone would hang on the "HTC" splashscreen and would require a batt-out to reboot.
I figured some apps had started to conflict and the little HD2 that could had become somewhat bloated so last week, I decided it was time for a flash overhaul...that's when it all went down the crapper...
Now:
-I am able to access bootloader, hard reset, flash radios and roms, no problem. It just wont boot afterwards.
-I tried task 29 and MTTY between flashes, no improvement.
-I tried several cooked roms and their recommended radios, as well as HTC roms, nothing will boot.
-I have had "Invalid Vendor ID" and the dreaded 0002802 error messages when trying to flash HTC roms that were not region appropriate.
-I tried reverting back to factory rom and 1.42 SPL by flashing the original [ITA] rom thru a freshly formatted 2gb SD card (leoimg.nbh), it gave me an "Update successful", the device booted, got me thru the initial setup screens then immediately froze when it got to the "home" screen. Soft reset got me back to square 1; hanging on the "HTC" whitescreen, with the RGB data being displayed, but going nowhere passed that.
Everytime I flash something, whether it'd be thru USB or SD, it never "stalls" during the flashing process, the changes are always reflected in the RGB data being displayed, yet, i'm still going nowhere.
My now-too-familiar bootloader is displaying
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
...and the toggle between Serial and USB is instantaneous when I connect/disconnect the cable...
please don't tell me I have a rainbow-screened paper-weight...
Little Update,
re-flashed with original ROM from SD this morning except i removed the SIM. It booted perfectly, got passed the setup screens and NO FREEZE. It connects to WiFi, everthing seems to work, all seems well. I shut down and put the SIM back in and, NO BOOT, stuck on splash screen with RGB...
My network is "3", so HSDPA, I was wondering if this requires specific radios?
I'll keep testing...with different SIMs and radios...
i'm beginning to think this might all be related to SIM failure...we'll see...
It definitely seems to be hardware related since you have tried so many different combinations of ROM and Radio. The SIM thing narrows it down I think... I'd try other SIMs...
Love the way you titled the thread, "un-cooperative"...
how about those battery pins? take a look at them and make sure they aren't bent and/or misaligned. fiddling with the sim forces you to fiddle with the battery and that may have caused the pins to align better, until you slipped the sim back in.
only reason i'm saying so is that i've read some threads about boot up and charging problems that were caused by bent battery pins.
Unfortunately, i think i've run out of options...the only one I didn't try being the so called "goldcard"; is worth the try at this point or, as I read, HSPL replaces the gold card process?
If it's worth it, how would one go about getting this tested?
If you can access to the bootloader your device is not bricked !
So..
You must install the lastest HSPL. If you have the lastest, re flash this one !