Related
I've just been trying to upgrade my ROM today, I've been reading all the info on the wiki for the past few weeks, decided that i'd try, and cautiously attempted upgrading to 1.35.255
I'd already performed the unlocking and super CID, and i checked via mtty, and info 2, all was good!
Unfortunately during the flashing, the RUU kept stopping around 1% i followed the recovery steps, all was not lost, again i tried, got to 5% this time......Every time it stopped it said it had a 262 error, anyway, I'm now trying to flash the hermes via the SD flashing method (maybe what i should have done in the beginning!)
I've got my card with HERMIMG.nbh on it, and when i boot up into bootloader....it briefly flashed on the screen no image file.....
And i've just tried again, and it flashes the tri colour screen...then briefly loading.... and then back to the tri colour screen.....
When i boot up normally, it just gets stuck on the windows mobile splash screen....
Anyone offer any advice???
Thanks in advance.
JD
BEFORE POF DOES IT...SEE http://forum.xda-developers.com/showthread.php?t=286755 <--THERE
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
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
Please help..
I have the HTC P4000
I have downloaded these before I started from here:
http://www.lifesnotsogood.com/dcd1182
Bootloader: titan_SPL_2.40-olipro.exe
Carrier file: dcd Telus Carrier 20080706.cab
Radio: Titan Radio ROM 3.42.30.rar
Rom: dcd_titan_3.2.0.exe
Kitchen: dcd_titan_kitchen_3.2.0.rar
Then started to follow this:
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
I. Prepare with EPST:
- Done
II. Install the correct bootloader
- I did this and it told me I had 1.04, so according to the instructions, I ran the titan_SPL_2.40-olipro.exe file and followed its instructions..
Got to the screen where it said to uplug and plug back in, except when I plugged it back in, it never resynched.. Active synch stayed grey.. But I followed the instructions anyways, and it said that it flashed successfully.. (Even showed the bar on my phone go across, but very quickly..)
Except when it restarted, it kept going to the coloured bootloader screen, which says:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
And then sits there and does nothing..
So I went to:
III. Radio Upgrade
-> B. Change the radio with a full carrier Radio & OS ROM flash
--> B. Flash via the USB
It again ran me through that same grey screen, but still no active synch connection. Now when I restart my phone, it shows the HTC screen, with this info:
M 09
P DCAAXAM-4350
R 3.42.30
D 2.13
And some other set of numbers that I can't read..
And then it goes to the TELUS screen and it sits there. I can still go to the bootloader fine if I use the POWER-CAMERA-RESET option, but my phone doesn't start. It stays on the TELUS screen.
What do I do now. Have I bricked my phone?
Boot to the bootloader, and you should see the bottom of the screen go from Serial to USB mode when you plug in the mini USB cable.
You should be able to flash at this point using the RUU.
If you are still having problems then, you need to go into ActiveSync, and uncheck 'Allow usb connections'...
You updated the bootloader and radio, but you didn't update the ROM. Just go into the bootloader and flash the ROM now and it should be fine.
He doesn't need to uncheck the allow usb connections..
Ok, now it says:
Verify that you want to update ROM version from:
Image version: (blank)
to
Image version: 3.42.30
I clicked next, it showed the progress screen.. Went to 8% then my P4000 restarted and this error came on my RUU:
ERROR [328] INVALID COMMAND
P4000 is still stuck on the TELUS screen..
That's not the ROM, that's the Radio. You need to flash the ROM. Run dcd_titan_3.2.0.exe with your phone in bootloader mode and connected via USB.
Cool, now I'm in WM 6.1, waiting for customization.. I want to do this right.. Thats the next step?
Thanks alot man..
Make sure you install the Telus Carrier cab now.
This is gonna sound dumb..
But how do I do that? The FAQ doesnt mention anything about this..
I've extracted "dcd Telus Carrier 20080706.zip" and see a few files..
Do you know how to install a cab file (application) on your phone?
Yes I do, but I'm in the custmozation screen.. From what I know, I shouldn't be continuing past this..
No, it's only when flashing the stock Sprint roms that you have to worry about customizations. It's fine when flashing a custom rom.
Set it up, when it boots to the today screen, copy dcd Telus Carrier 20080706.cab to your phone, then run it to install. Then soft reset.
Ok I continued by it anyways.. and now im in, I installed the carrier cab file using my microsd, restarted..
Doesn't seem to be activated or anything.. I dialed a # it says to press *611 to activate,.. that doesn't work, was there a diff thing i'm supposed to dial?
Ah, I got it.. its *22803 Restarting..
Cool, now I'm up and running.. But I need the kitchen now right?
I followed the FAQ, and it says to do this:
V. Kitchen
Run BuildNB.bat to execute BuildOS
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
When I run BuildNB.bat it comes up with an error saying:
"Windows cannot find RomUpdateUtlility"..
240sxer said:
Cool, now I'm up and running.. But I need the kitchen now right?
I followed the FAQ, and it says to do this:
V. Kitchen
Run BuildNB.bat to execute BuildOS
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
When I run BuildNB.bat it comes up with an error saying:
"Windows cannot find RomUpdateUtlility"..
Click to expand...
Click to collapse
Uhh... are you just flashing to DCD 3.2.0 ROM, or are you trying to flash your own version (kitchen) of that ROM? If you just want to flash to his ROM, then you're done.
Cool, now I'm up and running.. But I need the kitchen now right?
Click to expand...
Click to collapse
No, you're all done. You either install the premade rom (which you did) or a rom you cook from the kitchen. One or the other.
ya, do what he ^^^^^ said...
Thanks guys, I really appreciate it. All is well now. It's just that the FAQ wasn't that clear.
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!