Hi! I got a serious problem with my Trion. I unlockedthe device with HTC Hermes SIM & CID Unlock – v2a.After this, I started the upgarde software for upgrading to 1.35.255.102. My device fell from the table and USB connection was lost at the stage of 5% upgrading. Device now starts only in bootloader mode, stating SPL-1.09. When I try to restart the flash, it tells me: Invalid Vender ID. I tried to fix the problem with the solution recommended in Wiki :
Problem 4: Device is stuck in bootloader mode (tri-color screen)
Disable ActiveSync: connections -- settings -- uncheck "Allow USB Connections"
Remove the battery, put it back in, connect the USB cable, power on the unit (this should allow the USB port to be opened again)
Wait a minute or two, if you get a message that device cannot be recognized just close and ignore it
Open mtty.exe and select "USB" from the dialog box, then hit Ok.
You should see a white screen, hit enter and you should see a prompt like this: "USB>"
Type set 14 0 (do not copy and paste!!!) and hit enter
Soft reset with stylus
OS ROM and radio version should be back and OS functional, the unit isn't a BRICK anymore!
but no success. Can anybody help me there?
attached the USB log file. please help
research12 said:
attached the USB log file. please help
Click to expand...
Click to collapse
Corrupted CID and bootloader 1.09. If you can't boot the OS send it to service centre to repair.
thanks, pof. I appreciate your reply even though it was the answer I was afraid of...
I am sorry to give that answer, there is so many people with the same probelm, but still haven't figured out a way to fix this...
you don't have to be sorry at all. you are a great help with most things here in the forum.
Related
I don't know why I use HTC_Uni_SIM_Unlock_v1 with my phone !!!!
Now I can,t use IT. During the boot stops same seconds after the windowsmobile screen. It's impossible to contact it.
Read "Problem 5: Device shows NO GSM when booting" on the Common Upgrading Problems in HTC Hermes" wiki page. Solution is there for you
Maybe we should post a warning along with the Universal SIM Unlock tool instructions... such as
DON'T EVEN THINK ABOUT USING THIS WITH A HERMES!!!!!!!
There seems to be at least a couple of new victims every week!
I follow solution n°5 but I have a broblem with the bootloader. The Buttons are correct ?
Thanks
domomedia5 said:
I follow solution n°5 but I have a broblem with the bootloader. The Buttons are correct ?
Click to expand...
Click to collapse
Yes: SIDE OK + POWER + STYLUS RESET
I not be able to connect via USB the phone ! The radio rom 1.20.31.10 don't recognize my phone
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
is this the correct rom
thanks
Yes, this is the correct rom:
If you get a "ERROR 120: COUNTRY ID ERROR", do not disconnect the device, run MaUpgradeUt_noID again.
when I arrive to the window from ver. to ver. there are no description of the version !
what can I do
No problem, this is normal it is because the device is in bootloader mode.
how many minutes I had to wait
no more than 30min
It's stop from 30 minutes on cheching information on your device !?!?!
If the Hermes screen shows "Upgrade Radio Stack Please wait........." just wait until it finishes, if not, reset your device and put it back in bootloader mode, and run MaUpgradeUt_NoID again.
Make sure you've previously run the 'erase' commands in mtty sucessfully:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you can not success with radio upgrade, do a full rom upgrade using a rom matching your CID, start the upgrade from bootloader and make sure usb connections in activesync is disabled.
Hi guys, I have some experience with rom flashing, and I did it today as usual - flashed HTC 1.35 ... Update stopped at 1%. I tried everything I could to finish the update (It wasn't my first time ). Now, after restart TyTn is flashing with LCD (black & white) & camera led. I can't do anything, even turn it off. Seems like a problem with bootloader. What should I try before i send it for repairing? Do you have any experience with T-Mobile UK? I'm the legal owner of PDA, but I don't have any receipt. Should I contact seller (ebayer) or post it to T-Mob straight away?
Thanks in advance, Jack.
Anyone please?
Check out the wiki for Tytn upgrade problems
I also had this problem, upgrade stopped at 1%....Left it for an hour and no progress. Had to stop update, which then left me at the boot loader screen (tri-color) screen. Tried Hard reset as mentioned above, no luck, still stuck in boot loader, tried to reload rom..got error 262 upgrade error
I had just run the unlocker and set device to super CID, and thought maybe that was my problem, but it wasn't
Luckily the wiki had the answer
Problem 4: Device is stuck in bootloader mode (tri-color screen)
>Disable ActiveSync: connections -- settings -- uncheck "Allow USB Connections"
Remove the battery, put it back in, connect the USB cable, power on the unit (this should allow the USB port to be opened again)
Wait a minute or two, if you get a message that device cannot be recognized just close and ignore it
Open
mtty.exe and select "USB" from the dialog box, then hit Ok.
You should see a white screen, hit enter and you should see a prompt like this: "USB>"
Type set 14 0 (do not copy and paste!!!) and hit enter
Soft reset with stylus
OS ROM and radio version should be back and OS functional, the unit isn't a BRICK anymore!
I had to reload the rom. step 8 did nothing, but return me to bootloader. This time the rom upgrade took about 45 minutes to complete. Weird, but it worked...This is first time in at least 4 rom upgrades with this device and at least 50 other rom upgrades that I ever encountered any issues.
POF...Thanks for the great wiki
http://wiki.xda-developers.com/index...ame=HTC_Hermes
Unfortunately, when it hanged on 1% connection was totally lost. Everytime I tried to run rom upgrade/unlocker/spl downgrader is said no connection. Now I don't have bootloader screen, only flashing LCD & camera diode. Any suggestions?
If you can't get the bootloader running then a service center will be the only solution I think.
Has anybody found the solution to this problem, my phone is doing the same thing. Can't get it into bootloader and screen & camera flash just blinks? I tried everything but to no avail.
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
jackass_ass said:
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
Click to expand...
Click to collapse
It's bricked trying to update it!!! If i could just get it to the bootloader, i can probably revive it but can't do anything. Can't access USB or nothing, I'll guess I'll send it off to a repair center.
Are there any good repair centers in the US???
I installed an "updated" HTC Home Screen Plugin (obviously not for my phone model #) and now my phone is frozen. It will boot up but the home screen is frozen (i.e., non-responsive to any button presses). I attempted to re-flash the ROM using various ones I found for the NEON but all fail for the same reason.
Specifically, connection to ActiveSync is not possible (I connect via USB cable but ActiveSync doesn't recognize device). So what I do is put the phone in bootloader mode and then connect the USB cable. When I do this, the ROM upgrade program recognizes the phone and gets to the point where it shows the screen "Updating the ROM image on your PDA Phone.." and the phone shows a status bar at 0%. However, after a minute the computer screen says "ERROR [262]: UPDATE ERROR" and the phone is stile stuck at 0%.
My question is if there is any other way I can re-flash my NEON300? I've heard that it may be possible to but the nbh file on a FAT32 formatted card. I tried this by naming the nbh file to "TOUCHIMG.NBH" and "NEONIMG.NBH" but neither are recognized by the bootloader.
Thanks in advance for any assistance.
Try changing usb port or even re-installing activesync.
Alot pf people had the same problem on different devices but the cause should be the same.
for example, http://forum.xda-developers.com/showthread.php?t=298516
Let me know how you go.
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
wangobyte said:
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
Click to expand...
Click to collapse
You should have read the WIKI before flashing your device... http://wiki.xda-developers.com/index.php?pagename=Flashing Guide and here http://forum.xda-developers.com/showthread.php?t=355730
Hello everyone,
is that it will do some days I want to restart my qtek 2020 v0.6. It was purchased and screen
Black bootloader mode with serial or USB v0.6. I tried hard reset but nothing is there.
When I run the rom flash main with HimaUpgradeUt_noID.exe or HimaUpgradeUt.exe
it refuses to nk.nbf, it makes me country id error 120 or error 112 connection error.
But against n I've no problem for the Roma Radio_.nbf and ms_.nbf the flash is going well until the end.
With mtty.exe I could write the original rom on the sd card and I put on my pc with ntrw_494.exe.
The Roma PPE cause a password to open with ER2003edit.
I wanted to start the application xdadev_all_unlock-v1.6_138.exe or xdadev_all_unlock May-v1.5.exe my pc tells me that this is not a valid win32 application.
As against this for me xda2unlock.exe met:
XDA Developers XDA2UNLOCK tool v1.2 XDA Developers XDA2UNLOCK tool v1.2
This program will extract the unlock code from your XDA II. This program will extract the unlock code from your XDA II.
For this to be possible, a few steps are necessary: For this to be possible, a few steps are necessary:
1. 1. The XDA II needs to be put in bootloader mode. The XDA II needs to be put in bootloader mode.
NOTE: THIS WILL WIPE ALL YOUR DATA SO FIRST BACK-UP! NOTE: THIS WILL WIPE ALL YOUR DATA SO FIRST BACK-UP!
You enter the bootloader by holding the Power button and the Action button You enter the bootloader by holding the Power button and the Action button
while pressing the stylus in the reset hole on the bottom. while pressing the stylus in the reset hole on the bottom.
In the bootloader mode, the display will be gray and say Serial at the top. In the bootloader mode, the display will be gray and say Serial at the top.
2. 2. Next put the device in the USB cradle. Next put the device in the USB cradle. The display will now say USB The display will now say USB
and the first time Windows will detect a new device. and the first time Windows will detect a new device.
3. 3. Disable USB in Active Sync in 'File -> Connection Settings' Disable USB in Active Sync in 'File -> Connection Settings'
Now the device is ready to extract the unlock code. Now the device is ready to extract the unlock code.
Type YES when you have completed the above steps and want to continue: yes Type YES when you have completed the above steps and want to continue: yes
Communication port opened. Communication port opened.
waiting for radio bootloader waiting for radio bootloader
reading first block... reading first block ...
reading second block... reading second block ...
The phone seems unlocked already! Seems unlocked the phone already!
Do not forget to enable USB in Active Sync again! Do not forget to enable USB in Active Sync again!
Press enter to close.... Press enter to close ....
For truly all information of PDA on the origin of the country id and that exact version
there is the device data.txt but for creation must be initiated HimaGetDeviceData.exe that tells me that this is not
win 32 application invalid.
And finally, after searching hard I tried with hex editor on the original rom, change the first line, but there is nothing ...
That is my question is how empty the memory of the PDA to install a new (windows) to
it can restart normally?
norinsimpel,
I really tried to read and unterstand your post, but you mixed up languages, your own post and parts of a program manual, so that it is all FUBAR.
Could you please edit it, e.g. in this way:
1. The problem in French
2. The problem in English
3. Description of your device, the ROM you have now, the ROM you want to flash.
I´m shure this would make it much easier to help you...
sorry for the language.
I am belgium, and I use google to translate.
I have a qtek 2020 bootloader V1.06
I do not know the original rom, It does not light.
I can not use HimaGetDeviceData.exe with devicedata.txt to know the exact rom
because it does not turn
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...