[Resolved]: Stuck at Bootloader 1.06, titan_exitbl.exe isn't working. - Mogul, XV6800 ROM Development

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

Related

Problem with RUU

Ok...I have been through all the posts about upgrading etc. I still have a problem and I'm sure that I'm overlooking something....but I can't figure it out on my own. Here is what is happening (it does the same thing with every RUU that I've used...the DST fix...upgrading to WM6....etc)
1. I run the RUU and let it go through its routine (extract files, verify info on pc, etc.)
2. I check the box that says I have read the readme and click next
3. The next screen appears and it has the following steps:
Connect to the USB cable (check)
Establish an ActiveSync Connection (check)
Disable standby and hibernation on PC (check)
Make sure batter is > 50% (check)
Then I check the box and click next
4. I pick the update and click on the update button
5. I verify that I want to upgrade my phone from ROM verion x.xx.xxx to x.xx.xxx and click next
6. The program tells me that I am finally ready to update...and if I am sure I want to proceed to click next...so I click next
7. As soon as I click next...the progress bar comes up on my pc and my phone goes into standby mode (no bootloader...just standby). The progress bar never moves.
8. After a minute or two the RUU give me the ERROR [260]: Connection
9. I reboot my device and repeat steps 1-8
10. I reboot my device and my computer and repeat steps 1 - 8.
Now if I leave my device connected to the usb and close out the RUU after it gives me the ERROR [260], and then run the RUU again...when it is first verifying the information on my pc (before it asks any questions and before it tells me to connect my device) it will throw the device into bootloader mode. If I try to keep running the RUU while the device is in bootloader mode it give me the error that my device is not connected. I have tried and tried...maybe one of ya'll can help me. Thanks in advance
Chris
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
gerald_s said:
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
Click to expand...
Click to collapse
XP
No firewall
I tried to flash the WM6 from AT&T I assume its beta
and no did not install the Olipros bootloader
Ok...I think I found out how to do this...Ya'll can tell me if I'm screwing something up.
I go through all the steps listed above until it gets to the progress screen. When it gets there I manually put the the device in bootloader mode (Power, side ok, and reset). Once I do this...the progress bar starts moving. I will let you know if this works...
Hmmmm
Its not the way it should work but if it works its ok
You should have installed Olipros HardSPL first and then try to flash an official rom. If its working then something with your download is wrong.
What ROM is on there now?
Has the phone been CID unlocked?
Oli's CustomRUU is better, you may want to unpack the ROM and put the NBH in a folder with Oli's RUU and then do the upgrade.
BTW, gerald_s is right, you should not have to do that... what you may want to do is put the phone in Bootloader mode manually (while not connected to the PC), then plug in the USB, then start the RUU. That helps some people with 260 error.
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
You may be trying to flash a rom that includes the radio rom. What is your device? Is it possible that your device is a new x01ht with radio 1.14 and radio bootloader 0182? If yes, then you will get this error when you try to flash a rom with this method because during the flash it will be disconnected by the radio bootloader because it is not overwriteable. If you flash using the NBH file on the microSD, it will skip past radio and radio boot and just flash the other parts of the file.
mikebraeuer said:
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
Click to expand...
Click to collapse
If you are running windows XP, just connect the card to the computer, open MY COMPUTER, right-click the removable disk that is your microSD and then click format. Default in windows xp is to format using FAT32 filesystem which is perfect.
The thing is... if you dont know how to format a drive in Windows, should you be flashing your device yourself?
Which Solution???
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Wantoknow said:
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Click to expand...
Click to collapse
Have you tried flashing with your microSD?
Kevbodian said:
Have you tried flashing with your microSD?
Click to expand...
Click to collapse
I forgot to tell that, I had flashed through extra memory card yet, and could be done!
But I wanna flash ROM against CustomRUU through MS Active Sync as I had used before. Can you help me
i have a problem very similar to Chris. when i check the box "yes activesync is syncronised", and then the progressbar shows up and the phone goes into standby.
i've turned standby of in powermanagement options.
my os is XP
i use active sync v4.5
and this is first time i try this.
i've read something about this bootloader, i can get there but then i cannot sync with active sync. so i kinda stuck.
have been searching the forums and this was the same problem as mine but i don't understand your solutions.
//KufrA
--Problem solved--
i did all things without activesync,
1. start phone in bootloader
2. do the install
3. wait 0% to 100%, and done.
is there a problem with active sync or why do i have to do anything with it at all?

Please help I'm stuck - Radio ROM error 328 invalid command @ 9%

I have a mogul and have been trying to update the ROM all day with no luck, and could really use some help
I have SPL-2-2.40.Olipro bootloader working ok.
I tried to flash the radio rom 3.27.00 first, but it got about half way and errored. It then had me do the battery removal, reboot procedure and restore which said it completed ok. I then tried the rom again, but now it only goes to 9% and then the mogul resets and i get error [328] invalid command.
I then was able to update the dcd 2.2 rom which completed ok, but now I get the yellow splash screen w/ sprint logo and the no radio message. I've tried loading the radio rom again numerous times from the bootloader, but it does the same thing resetting at 9% error 328
I've rebooted the PC, played with the cable connection which seems to be working as the bootloader will switch between serial and usb.
I also tried restoring to the 2.17 rom which I downloaded from the HTC site, but it only goes 1% and errors out with the same [328] Invalid Command
What can I do to get this working?
So are u sure you have the new unlocker
then flash the rom
and then radio
I think so the file is called "Hard-SPL-MFG" and I get the red, green, blue screen that reads:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
I was able to get the dcd rom to go with no problems, but the radio rom will not go. Like I said it gets to 9% at which point the phone resets and I recieve the error 328 invalid command on the pc.
I saw some others here having the same problem, but wasn't able to find a clear resolution posted
thanks
I also just tried flashing the radio rom via sd card with no luck. I extracted and renamed the nbh file and copied it to the root of a freshly formatted (in FAT) sd card. Whne i start the boot loader I get the white screen and it says loading..... but then just returns to the red,green.blue screen. When i reboot I'm still getting the splash screen with no radio at the bottom
Put your phone in 2.40 bootloader (tri-color screen) and follow these instructions starting from step 4:
http://forum.ppcgeeks.com/showthread.php?t=17667
If that does not work, try it again from step 3.
mogul67 said:
I think so the file is called "Hard-SPL-MFG" and I get the red, green, blue screen that reads:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
I was able to get the dcd rom to go with no problems, but the radio rom will not go. Like I said it gets to 9% at which point the phone resets and I recieve the error 328 invalid command on the pc.
I saw some others here having the same problem, but wasn't able to find a clear resolution posted
thanks
Click to expand...
Click to collapse
hard set your phone(2 soft keys and soft set botton)
and then load it into bootloader(power botton+camera botton) and then try to load the radio like that
bakntyme said:
Put your phone in 2.40 bootloader (tri-color screen) and follow these instructions starting from step 4:
http://forum.ppcgeeks.com/showthread.php?t=17667
If that does not work, try it again from step 3.
Click to expand...
Click to collapse
I've tried that but I can't get the relocker to run? It says no device connected would you like to try copying again? and I'm on the SPL boot screen its connected etc
I've also done the hard reset, gone back into the bootloader and tried the radio rom again, but it stops @ 9% with error 328 and resets the phone
mogul67 said:
I've tried that but I can't get the relocker to run? It says no device connected would you like to try copying again? and I'm on the SPL boot screen its connected etc
I've also done the hard reset, gone back into the bootloader and tried the radio rom again, but it stops @ 9% with error 328 and resets the phone
Click to expand...
Click to collapse
OK, did you try starting from step 4? That means just flashing the Sprint "leaked" ROM.
if I have Alltel should I still use the same method even though it says it's a Sprint rom?
I have the same issue right now
Thank you I was able to get the 3.16 ROM loaded.
next I ran the Hard SPL unlocker and got the bootloader screen, tried the radio rom install and its still quitting @ 9% resetting the phone?
I need to get the radio to work before installing dcd's rom right?
Ok don't worry, I had the exact same problem as you mogul67 and I was puling my hair out for a day and a half.
If you read kmartburrito's original PPCGeeks page:
http://forum.ppcgeeks.com/showthread.php?t=16806
The edit by ImCoKeMaN says:
I have found that if you have issues where your device seems to be bricked and stuck in bootloader before completion of the update you can fix it by flashing via SD card.
To do this there are 3 steps:
First take the .exe file and open it with winrar. There will be a file 3.16.....nbh extract that and rename it to TITAIMG.nbh
Next format a microSD card with FAT 32 (required most are fat16 default) and copy the file TITAIMG.nbh to the root of the sd card with a card reader.
Finally place sdcard in device and reset into bootloader mode. The flash will proceed from the SD card and it should work fine. Enjoy!
Click to expand...
Click to collapse
By "take the .exe" he means open the Radio ROM flasher with WinRAR, btw... I had to think about that one for a second just because it seemed so simple
So head over to best buy and get yourself a cheap MicroSD to SD adapter, throw it in your favorite card reader, follow the steps and you'll be up in no time
THank you for your help that did it, but I was able to just run the 3.16 ROM from Windows with no sd card. After loading that ROM I was able to run the unlocker, hard spl, and then update the ROM
thanks again

P4000 stuck in bootloader

Just did the titan unlocker and now the p4000 is stuck in bootloader with these 2 lines:
TITA100
SPL-1.20.Olipro
i think i need some help
thanks in advance
Marc
edit:
RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_3.42.02_SPCS2.0 4_PPST_0619_Ship.exe >>> would flashing this ROM and Radio save me or my titan?
orangeworx said:
edit:
RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_3.42.02_SPCS2.0 4_PPST_0619_Ship.exe >>> would flashing this ROM and Radio save me or my titan?
Click to expand...
Click to collapse
yes..............
since i'm stuck in bootloader mode, how can i use the ruu update utility ?
i'm getting connectiong failed and only option is to exit utility
any ideas ?
if u are in bootloader connect the usb cable and the phone should say usb at the bottom, just open up the ruu update and it should work just fine
Error 264
update utility cannot connect to your pda
and it says USB on the bootloader screen
SPL is 1.20 olipro
take your SD card out if (with phone powered off) if u have an image on the SD card and retry
no SD card being used at the moment
edit: it seems now it is flashing...
let's say this does work, fact that i'm putting a sprint ROM on my telus phone is gonna be alright?
re-edit: crashed at 11% - invalid command error 290... RUU encountered a communication error
recovery
at 11%, titan reset and went back into bootloader mode, RUU crashed but gave option for recovery which was "successful"
retried the same RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_3.42.02_SPCS2.04_PPST_0619_Ship.exe
and crashed again at 11%
i think i killed my phone
i can't seem to do anything, not the telus wm6.0 ruu nor the one stated earlier...
is there a way i can revert to my previous SPL 1.04 ?
really appreciate the help @ 5:35 AM
got my telus wm6 to run and then decided to up to olipro 2.40
now it won't got past second splash...
radio is 1.32, rom is dcd 3.2.5
now from my understanding of what i've been reading is that i need to revert to olipro 1.20 to be able to flash my radio
and i can't do that since i can't get activesync.
any ideas ?
Get a SD card. Go to WIKI and following reverting to Stock. Then start over on flashing. I have done as you did and fixed the phone.
your phone sounds jacked up, how long is it stalling at 11%, r u giving it decent enough time?
redownload the latest sprint rom from htc america here:
http://216.139.227.226/RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_TITAN_3.42.02_SPCS2.04_PPST_0718_Ship.exe
let it run for at least 20 minutes before deciding it crashed...after 1st boot softreset before letting it run any customizations

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!

CustomRUU and HSPL problem, phone can't get out of bootloader mode anymore :(

Hi. I wanted to install Android on my HD2 but for that I need radio versions 2.08 - 2.12. And currently my radio version is 2.06 so I wanted to flash it to 2.10 or one of them between 2.08-2.12. For this I used Custom RUU. Everything went well untill it said installing, and it went to 4% and then suddenly my phone reboots and then on my computer it says "Error 270. The image file is corrupted. Please check your Update Utility."
Well what have I done wrong?
Nilee said:
Hi. I wanted to install Android on my HD2 but for that I need radio versions 2.08 - 2.12. And currently my radio version is 2.06 so I wanted to flash it to 2.10 or one of them between 2.08-2.12. For this I used Custom RUU. Everything went well untill it said installing, and it went to 4% and then suddenly my phone reboots and then on my computer it says "Error 270. The image file is corrupted. Please check your Update Utility."
Well what have I done wrong?
Click to expand...
Click to collapse
Did you have install HSPL on your device?
Yes I have installed HSPL. But if you have installed HSPL, is it then supposed to show "HSPL" somehere on the bootloader screen? Because on mine it doesn't.
But then that's weird because I did install HSPL and it even said succesfull. But still I get the same error when I try to flash the radio.
Go into bootloader by holding the VOL- (down) button, while pressing the End Call button to boot up your phone from being all the way turned off.
Check on your bootloader (tri-color) screen for the letters HSPL and the name Cotulla.
If these things are not present, then for some reason you don't have HSPL installed.
If this is the case, stay in bootloader, and re-run HSPL, and then check again in your bootloader to make sure you have HSPL, and then re-flash the custom_ruu
Chances are it just didn't take because your phone didn't have HSPL for whatever reason. You might want to re-download the radio ROM just to be sure you didn't get a corrupted/incomplete download.
Good luck
oops ignore plz
but what a shame that my pc even doesnt play with custom ruu.nothitng happen when i click.i have everything installed.
huggs said:
Go into bootloader by holding the VOL- (down) button, while pressing the End Call button to boot up your phone from being all the way turned off.
Check on your bootloader (tri-color) screen for the letters HSPL and the name Cotulla.
If these things are not present, then for some reason you don't have HSPL installed.
If this is the case, stay in bootloader, and re-run HSPL, and then check again in your bootloader to make sure you have HSPL, and then re-flash the custom_ruu
Chances are it just didn't take because your phone didn't have HSPL for whatever reason. You might want to re-download the radio ROM just to be sure you didn't get a corrupted/incomplete download.
Good luck
Click to expand...
Click to collapse
Ok, then my HSPL isn't installed. But that's real' weird. Because when I install HSPL everything goes okay and it even says "Succesful" etc. I've tried to install HSPL for like 4 times and it always says installation completed, but however it doesn't show anything like HSPL or Cotulla on the bootloader screen. And I do have SPL 1.42.0000, which is required to install HSPL. And I also disabled my anti-virus so what have I done wrong?
By the way: When I go to bootloader mode it always goes to a grey screen first with blue words "Loading" and after a few seconds it says "Not allow" and after that it finally goes to bootloader mode. Is it supposed to be like that or what's wrong with this?
Nilee said:
But then that's weird because I did install HSPL and it even said succesfull. But still I get the same error when I try to flash the radio.
Click to expand...
Click to collapse
did you use hspl3 and not changing the dropdown from its default 2.08.0000 which is stock. run it again and make sure the dropdown ends .hspl
saurabh88 said:
but what a shame that my pc even doesnt play with custom ruu.nothitng happen when i click.i have everything installed.
Click to expand...
Click to collapse
anti virus program give you a hit when you first downloaded it?
many times the file gets disabled so you need to download it again, even if you turned off the av or told it to allow customruu.
also right click and "run as administrator" even if you are logged in as admin.
Nilee said:
By the way: When I go to bootloader mode it always goes to a grey screen first with blue words "Loading" and after a few seconds it says "Not allow" and after that it finally goes to bootloader mode. Is it supposed to be like that or what's wrong with this?
Click to expand...
Click to collapse
there's a leoimg on your sd card (or your phone thinks there is) but it isn't starting. remove the card.
Ok, well I used HSPL 2 and it installed correctly. HSPL 1 however didn't work for me. After I installed HSPL 2 it clearly said something like HSPL 2.08 on the bootloader screen. So I tried to flash to a new radio with CustomRUU. It all went well, untill it was installing and suddenly said: CONNECTION ERROR CRITICAL ERROR or something like that. It also said that the USB cradle or something was unconnected, however it was still connected and I didn't even touch it. After that my phone rebooted and went into bootloader mode again. The weird thing is that it doesn't say HSPL 2.08 anymore. Now t says SPL 1.42 again so the HSPL went away or something. I tried to reboot the phone (using the red button at the back of the phone) but it went into bootloader mode again. Well, all it does is go into bootloader mode. I can't even get to the normal thing again, only the bootloader mode. What the hell have I done wrong?
By the way: If I'm in bootloader mode all it says is this:
HX-BC
SPL-1.42.0000 XE <-- (before this it still had HSPL but now it went away)
MicroP-Wrong Platform (0x0)
MicroP(TOUCH) 0x30
Can anyone help me? Have I bricked my phone??
Just a question/suggestion,
Did you already thought to use/install the latest stock ROM 3.14 !?
the reason of this suggestion is this stock ROM have Radio 2.15.50 already integrated (no need of HSPL) and it's compatible with Android.
Well I didn't, I will try to do it. But I don't know how. Because my phone is still only able to get into bootloader mode. And it won't even charge it's battery..
So do I have to put the Stock ROM on my SD now, and flash it from the SD card?
I don't even know how much battery my phone still has..
Nilee said:
Well I didn't, I will try to do it. But I don't know how. Because my phone is still only able to get into bootloader mode. And it won't even charge it's battery..
So do I have to put the Custom ROM on my SD now, and flash it from the SD card?
I don't even know how much battery my phone still has..
Click to expand...
Click to collapse
You can flash stock ROM when you are in bootloader mode.
kurt-willems said:
You can flash stock ROM when you are in bootloader mode.
Click to expand...
Click to collapse
How?
By the way, my phone is in bootloader mode but it won't connect to the computer using a USB cable, it also won't charge it's battery.
Nilee said:
How?
By the way, my phone is in bootloader mode but it won't connect to the computer using a USB cable, it also won't charge it's battery.
Click to expand...
Click to collapse
Ok, then rest you the flashing over SD.
Make attention to use the right stock ROM; use your S/N to get access at your stock ROM on the HTC webpage.
deleted please ignore
Ok so I just extract the .exe and take the .nbh file of it and rename it to leoimg.nbh and put it on SD and start flashing?
Nilee said:
Ok so I just extract the .exe and take the .nbh file of it and rename it to leoimg.nbh and put it on SD and start flashing?
Click to expand...
Click to collapse
Yes; that"s it.

Categories

Resources