Ok
Micro drive went tits up the other day. All of the files disappeared with the exception of the pim back ups...
Decided to reformat the drive and thought "oh well might as well reflash the phone at the same time".
Was on michy 2.04 spl 1.2 and stoooopidly tried to use the spl 3.5 r5.1.- forgot that i had downgraded the spl after the camera stopped working after upgrading spl and rom.
Naturally it failed at 98%.
On rebooting it went to the boot splash screen (not the proper boot loader screen) and fell over, Incidentally the splash screen had been corrupted ever since i went over to the michy side but it never bothered me as it worked none the less.
Attempts to reflash give me the 244 invalid model error.
Have tried cemonex's telnet stuff but do not have the option of usb, only com2,3,6. mitty program is in root of drive and have tried various usb leads, no sd card or sim, also disabled usb in active sync- even though active sync doesn't see the ameo.
have rebooted xp sp3 loads of times
Boot loader screen shows
IPL-v1.00
spl-v1.20.Olipro
If i cant even telnet in what can i do??? I often get the really helpfull usb device not recognised...
I know that I am a silly boy but would appreciate any help...
tnx in advance
try this
post 33
looks old but it works
i know i tesed ap4 and got ****ed wfi and model id from it
thanks for taking the time to reply rory
i had already followed the advice in that post but even after following the later postings i could not get to telnet via usb as an option in the mtty drop down list...
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!
So I had an 8525 stored in the closed cause i had another phone.
So I powered it up after charging and its been working great.
About a year ago I had upgraded from WM5 to WM6 the official ATT release update.
I want to get 6.5 now but when I try to flash HardSPL7 it fails.
Before doing this I wanted to make sure I could sync and see my memory card, backup data and all that was successful via USB connection.
When I do the SPL it goes all the way to update it so I click on update and my phone asks me that it will run a program that might be harmful. I click yes and it goes to a rainbow colored screen. After about 1 min. My computer closes the connection to the phone and I get an error saying to check usb cable..etc.
On the phone it still shows USB. If i disconnect it it goes to Serial. If I connect it shows USB again, but the Hardspl7 program just closes out because it can't connect.
What could be the problem.
I have windows Vista
I checked troubleshooting but didn't find anything relavant to my problem.
Phone:
Herm100
IPL-1.04
Herm100
SPL-2.03
Go to page 116, post 1160 of the Hard SPL thred. It will give you instruction on how to flash Hard SPL using the sd card method.
To flash roms using this method, drop the steps using SSPL.exe (Soft SPL).
Cheers...
Solution found, thread closed
Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
I have the same problem!
I want to install HSPL on my device. I cannot install this via SD Card so i tried it with USB. But after the bootloader the connenction was lost. Many times...
Can somebody tell me how to fix this problem?
Thanks
Edet: My device is a HTC HD2
This might not fit your problem, but ...
... try to connect your device to a PC/laptop with USB 1.1 - with my Ameo I have many "connection loss" problems with USB 2.0 speed, which occure only on heavy (data) load on syncing.
Disabling USB2.0 is possible on some machines within the BIOS.
If you got no PC/laptop with USB1.1 you can disable the USB 2.0 related driver in the Windows Device Manager (it works for me, in general). Therefor open the device manager and select the "View" menu -> devices by connection (or similar). Now search for the Athena entry attached to the listed USB hardware. Disable the "most-upper" USB controller the Athena is attached to.
OK, the last description might be confusing, but try.
Good luck (as this solution fits to your problem, as I am not sure)
What worked for me
junooni said:
Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
Click to expand...
Click to collapse
I just spent the weekend trying to unlock my Athena and was having the exact same problem... USB would disconnect, errors 202, 267 . I finally was able to flash the Olipro bootloader, but had a hard time unlocking the radio. My device showed no radio under its properties, so I could not tell what radio version I had. Pressing "phone" would not bring the dialup screen. After so much sweat, I had to put it apart, only to find that the radio board connection to the motherboard was improperly seated, thus was having a bad connection. Once the connection was properly seated, the phone booted up to the emergency call screen, notified that there was no SIM card detected and when I looked in the device properties, the radio version was listed!. I then proceeded to unlock and flash the radio and this time the connection was not lost, the process completed without a glitch.
Hope that helps...
EDIT ON JULY 5, 2010:
AFTER 30 TRYES on 2 days my pda has only enter bootloader mode on two times... and when I connected to my pc didnt appear "USB" on screen.
any help will be grateful. Please. Thanks.
EDIT ON JULY 2, 2010:
MY PDA DOESNT START THE BOOTLOADER
I have make HSPL 1.42 with "success" because "we hacked it " appeared on screen BUT...
that has been the las thing that I have seen on the screen. Now I cannot switch on, neither start in bootloader, and when I connect to pc and I turn on normally the pda in my pc I can see like "new hardware found... qualcomm..." (while on PDA is black screen).
I have try to left the HD2 without battery during seconds, minutes and hours before try again.
I have try to left the HD2 charging all night before try again.
I have try with other batteries (I have 3).
I have try with different with windows 7 and windows XP (for looking what happens if I connect HD2 with black screen.
ANY HELP????
MY PDA DOESNT START THE BOOTLOADER
on JULY 1 I SAID:
(Sorry for my bad english) I have been for 2 complete days trying to solve before post this new thread. Now, the explanation:
I have a Spanish Movistar company HD2.
To enter in bootloader mode I have to be a few seconds (or minutes, it depends...) without battery. When I get into bootloader mode I see:
_______________
PB81100 HX-BC
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
Serial
_______________
So I supose that it isn´t the HSPL installed.
Sometimes when I simply switch on I see HTC logo with white background (I supose that is because it has the task29 made.
When I left the device without battery few seconds (or minutes) and I get into again and I switch on I see too the HTC logo with white background.
I have try to flash some roms through microSD card and the result is allways the same: It changes the screen into a grey and I see "Loading..." but it stays like this infinitely (I have try to wait more than 20 minutes). I have try this with original Movistar Company ROM, original HTC ROM, some radios (more than 6 types), some coocked ROMS (including arthemis, BSB beast, Energy), and the result is allways the same, stays "Loading..."
I have try to flash through PC. CustomRUU Recognizes the device but when it starts to update the device doesnt change screen or sometimes looks like pixelated screen, and on the PC appears like new hardware found (qualcomm CDMA Technologies MSM) and update through pc doesnt start. I have try too when It appears like new hardware found to remove the battery and start on bootloader mode, but update neither starts.
I have try to make HSPL (2 and 3) and the result is allways the same: recognizes the device and on bootload screen apears "USB" in the white part. HSPL tells me what SPL I have ( 2.08.0000|| ) and let me choose 2.08.HSPL BUUUUT when I push continue in the device nothing happens, on the PC appears like new hardware found (qualcomm CDMA Technologies MSM) and HSPL gives me an error (sometimes one sometimes other):
__________________
CRITICAL ERROR
Flow: 00000006
Error code : 00000010
Description: Unknown
__________________
or
__________________
CRITICAL ERROR
Flow:00000002
Error code: 00000003
Description: USB Operation failed
__________________
Thanks to all for your help.
Tryed installing a radio higer then 2.6? Phone wont start without 2.7 or higer
Nakazul said:
Tryed installing a radio higer then 2.6? Phone wont start without 2.7 or higer
Click to expand...
Click to collapse
telling "some radios (more than 6)" I mean that I have try with more than 6 types of radios, but yes, I have try with radios from 2.04 to 2.08.
Thanks Nakazul
but first you need to hspl. you cant flash any of those roms or radios without hspl
enter bootloader (three coloured screen)
connect to USB, wait for 'serial' to become 'USB' - if pc tries to say it is a qualcomm, change USb ports. Use one around teh back of the PC, not one in the front casing.
run hspl ( 2 or 3, doesnt matter which) pick an spl that ends with .hspl, so
2.08.0000 - No, stock, it wont work
2.08.hspl - yes, now you can flash.
now run task 29 (use the shadrac repack)
enter bootloader again, confirm that your spl says 2.08.hspl
flash your rom over USB. Do not use sd card (using sd card is probably how you got spl 2.08.0000 on a non tmous phone)
samsamuel said:
but first you need to hspl. you cant flash any of those roms or radios without hspl
enter bootloader (three coloured screen)
connect to USB, wait for 'serial' to become 'USB' - if pc tries to say it is a qualcomm, change USb ports. Use one around teh back of the PC, not one in the front casing.
run hspl ( 2 or 3, doesnt matter which) pick an spl that ends with .hspl, so
2.08.0000 - No, stock, it wont work
2.08.hspl - yes, now you can flash.
now run task 29 (use the shadrac repack)
enter bootloader again, confirm that your spl says 2.08.hspl
flash your rom over USB. Do not use sd card (using sd card is probably how you got spl 2.08.0000 on a non tmous phone)
Click to expand...
Click to collapse
First, thanks.
I connect to USB, "serial" become to "USB" like allways (qualdcomm hardware never appears when conected with bootloader without start the HSPL or CustomRUU). I start HSPL 2 and I choose "2.08.hspl" like allways. I push continue and PC tells me "new hardware, qualcomm...." (allways on that momment, when push "continue" after choose "2.08.hspl") I change the USB cable to another port and automatically HSPL gives me an error and I only can acept and the HSPL software closes. I have try to change USB port before push "acept" but nothing. Allways appears "new hardware, qualcomm..." con PC while PDA stays with bootloader screen apearing like connected through USB.
Hope you understand all, I really dont know how to explain better.
strange. Is it the stock usb cable?
I think you should try a different pc.
samsamuel said:
strange. Is it the stock usb cable?
I think you should try a different pc.
Click to expand...
Click to collapse
I have try on 2 pc-s. One cpu with windows 7, the other with windows XP.
I have another HTC HD2 (this of Vodafone) and the cable works perfectly. (The died HD2 isnt mine of a friend.)
PD: Shouldn´t it be able to load correctly the stock rom through microSD?
Thanks!
sorry, i dont know what to suggest next. I'll sleep on it and let you know if anything occurs to me.
Thoughts for now, , your original stock rom is probably failing because i 'think' stock spl 2.x will not allow itself to be downgraded to 1.x A few people got stuck before hspl2 arrived.
How about trying a goldcard, with the tmous 2.13 stock rom? that would change the spl to 2.10.0000 and you could try with hspl3, , it could be that the spl is messed up (you shouldn't have been flashing with sd card, it messes with the spl/hspl, even when the flash fails, hspl will still be removed)
have you allowed the qualcomm dirbvers to install when in bootloader mode?
when in bootloader the AMSS is taking over connection so its the snapdraon drivers that your pc is trying to install, which are the ocrrect ones.
Allow your computer to install them, and try it again
g.lewarne said:
have you allowed the qualcomm dirbvers to install when in bootloader mode?
when in bootloader the AMSS is taking over connection so its the snapdraon drivers that your pc is trying to install, which are the ocrrect ones.
Allow your computer to install them, and try it again
Click to expand...
Click to collapse
When I tried to install that driver I make click on continue but doesnt find drivers...
NEWS!!!!!! (bad news...)
I have downgrade into HSPL 1.42 with "we hacked it" on screen, but now cant start the bootloader mode!!!! I have been trying to be without battery during minutes and during hours!!
I cannot star PDA on bootloader mode with or without USB cable conected and with or without SD inside. BUUUT If I turn on the HD2 normally in my PC I can see "new hardware...qualcomm...". What can I do whith this?
Thanks to all for your help!
byAGM said:
When I tried to install that driver I make click on continue but doesnt find drivers...
NEWS!!!!!! (bad news...)
I have downgrade into HSPL 1.42 with "we hacked it" on screen, but now cant start the bootloader mode!!!! I have been trying to be without battery during minutes and during hours!!
Thanks to all for your help!
Click to expand...
Click to collapse
"cant start the bootloader mode" Why not?
Can you just do a reset by poking the reset button (button near battery) while holding volume down? That won't bring up the bootloader??
zkid2010 said:
"cant start the bootloader mode" Why not?
Can you just do a reset by poking the reset button (button near battery) while holding volume down? That won't bring up the bootloader??
Click to expand...
Click to collapse
I dont know why but... I´m during few minutes (I have try during hours too) without battery, I put the battery inside the PDA and I push power button while holding volume down (like allways I have done to enter bootload) and nothing happens. I try again with reset button and nothing.
On both ways the HD2 makes a short vibration but doesnt bring up the bootloader.
When I connect to PC and I turn on the pda normally, pushing the power button (whithout hold the volume down button) I can see on PC like "new hardware found... qualcomm....", but the PDA screen its black. (I have try to connect other HD2 and works perfectly on the same PC with the same cable).
Thanks to all.
FYNALLY AFTER "WE HACKED IT " TO HSPL 1.42 I CANNOT START THE PDA NEITHER THE BOOTLOADER.
I have try lefting the HD2 without battery for a seconds, minutes and more than 8 hours... I have try too with the reset button. Nothing happens, I only can ear the little vibration that allways make. Nothing more...
May be to exist any solution with that 3 pins that are between SIM and microSD card? any connection with them? I dont know...
Will be this the first died HD2?... hope that no... but...
ANY HELP??
THANKS.
I have been 2 days trying to turn on the pda on bootloader mode. I have been lefting without battery during hours before trying to turn on but I has turn on (on bootloader mode) only 2 times and fail when connect to pc.
.
Somebody knows why I cannot start my pda on bootloader (remember it hasn´t any rom inside) in except of 2 times by 30 tryes?
Thanks and sorry for my bad english.
HELP PLEASE, DEAD HD2, NO BOOTLOADER.
is it possible that the battery isnt charged now? my telstra hd2 is stuck on the white htc screen constantly and i know the battery died on it and thought the same as you..i took the battery out for about a halfhour then plug it in and left it for a day and i was back in business with a charge. may be worth trying mate
the-wrangler said:
is it possible that the battery isnt charged now? my telstra hd2 is stuck on the white htc screen constantly and i know the battery died on it and thought the same as you..i took the battery out for about a halfhour then plug it in and left it for a day and i was back in business with a charge. may be worth trying mate
Click to expand...
Click to collapse
I have one cradle for charging batteries and 3 batteries.
The 3 times that the PDA has enter to bootloader has been without being the battery at 100% (between 50% and 60%).
Thanks for your help, the wrangler.
byAGM said:
I have one cradle for charging batteries and 3 batteries.
The 3 times that the PDA has enter to bootloader has been without being the battery at 100% (between 50% and 60%).
Thanks for your help, the wrangler.
Click to expand...
Click to collapse
no prob mate, wish i couldve helped you. ill keep wrackin my brain and see if i think of anything that may help you
Hi All,
I've successully insttaled mmty and tried some commands. all the formating and info commands.
After 2-3 mins. later I got this error message.
errmsg_file.log :Flash NAND DM internal transfer failed: dmov_transfer() errmsg_file.log :bad-block check - error DM transfer failedDMOV dev 0 chan 7 transfer: invalid channel state: 20
I turned off the phone and removed the battery waited for 2 mins. and rum MTTy again.
the same commands worked.
but after 2-3 mins I run another silly command like info 1,2,3... same error messaged apperad on MTTY again.
by the way ;
there is a similar thread here :
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=718611&page=3