Related
HI
I AM IN NOW BIG TROUBLE
I HAVE O2 WITH SPLASH ON SCREEN AND HANGS THERE
all i done is upgarde downgrade from version 1.600 /1.66/1.72
all giving same errors
error 114 while erasing radio rom
this is RUUL LOG
9:54:14 Write block133
09:54:19 Update Stage 3 complete
09:54:34 Begin Stage 4
09:55:04 Radio Erase retry 1
09:55:34 Radio Erase retry 2
09:56:04 Radio Erase retry 3
`
THEN ERROR
NEED GUIDANCE
its a nogsm on screen
No GSM
1.72 wwe
thanks
no one has problem before ?
how to do with mmc card
why lauch vwrsion does not communicate with xdaII
i got Xda_II_LaunchROM_v10311
alos Xda_II_Upgrade_v16050
but this two cant communicate
also i put himupgradeUT in same folder but it gives error bed chacksum
i am becoming crazy now
OK.. can u tell me what version you have now? and what version are you trying to upgrade.. lets make this step by step.. i will try my best..
srtange
i had put my phone on charger after two hours
windows start up scrren appeared
also if i allow to reset phone hangs on O2 screen
its work ok now but without gsm
this is information
i got O2 XDAII
ROM VERSION 1.72.00WWE
ROM DATE 03/15/04
RADIO VERSION NOT AVIALABLE
PROTOCOL VERSION NOT AVIABLE
ExTROM VERSION 1.72.181
IDENTITY
Model No. PH10B
Platform: pocket pc
imei: not aviable
i cant flash radio part
my boot loader is 1.03
thanks and regards
Oh My God i dont know how to upgrade the bootloader... i think the problem is your bootloader cuz its not updated.. it sgould be 1.06 and all of that will work fine.. i dont know how to upgrade the bootloeader...
Hi,
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
Please help.
Thanks
If your device is still working ok as a PDA then hopefully it just screwed up the radio update of your device.
Try reflashing the Radio only
Look Here
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Post back with results
Regards
S.K
EDIT: Sorry only works on 1.04 bootloader only. Afraid your gonna have to wait for Pof to come up with a 1.06-1.04 workaround
Hi S.K,
Thanks for the info. I have now tried installing the HERM_1.20.31.10_type2_radio_fixed upgrade but unfortunately the radio upgarde crashes also. It all seams to go well, (after using MaUpgradeUt_noID.exe twice) the phone says "Upgrade Radio Stack Please wait" and the progress bar appears on the PC but then after 10 mins I get an ERROR 114: RADIO ROM UPDATE ERROR.
Do you think this might be becuase the last upgarde partly installed bootloader 1.06?
Any other suggestions - I'm desperate to get the hpone on M3100 working again.
Thanks
Read here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Please post USB monitor capture, otherwise can't help u.
Hi Pof,
Thanks for the offer, I will sort out the usb software on Monday. Are there specific actions that I should try, obvioosly I will usb monior everthing I do but I want to keep it to the point and not waist yr time trailing through huge log files.
Cheers
BTW - I have tried all options of recovery, such as attempting to install the latest radio and trying to install the new rom from an sd card, trying several roms and using imei unlocker - all without any joy.
I think the problem is that I have partially installed radio and bootloader 1.06 so I can't fix the problem.
Thanks again.
@wotthefok:
For me is faster to look at the usb log file, then I exactly know why the upgrade fails, otherwise I have to decode it from your feedback and I can't be really sure. Check the "upgrading problems" page on the wiki, if none of the steps there seems to fix your problem, post USB monitor log please.
Log Files as requested
Hi,
I have captured information using usb monitor and attached the zipped log files for your attention.
The first is called USB_monitor_log_Herm_120Radio_twice. This log details attempting to install the HERM_1.20.31.10_type2_radio_fixed upgrade, and running it twice - just in case.
The USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_twice.zip details attempting to install the RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship upgrade, simply using the standard ROMUpgradeUt.exe method. This generates the expected Vendor ID error.
My primary focus is to install the radio upgare or download my bootloader to 1.04. The PDA part of my m3100 does now freeze occasionally but at least functions whereas the phone is completely dead.
Thanks in advance.
Please attach capture in *ANSI TEXT FORMAT*, the .lgs file you zipped is totally unuseful
Edit -> Export and Save as type "ANSI Text files".
Also make sure you export in "COMPLETE" view, see the wiki for more details.
OK, Spot the novice.... I have now created a txt log file that captures activity of me running the 120 Radio upgarde - but only once this time. I still had to zip the file due to it's size. Hope this is OK.
I'll send the other logs within the next couple of hours. Please let me know if the output I have sent so far is acceptable?
Thanks
wotthefok said:
Please let me know if the output I have sent so far is acceptable?
Click to expand...
Click to collapse
No, it's a "basic" capture, you have to export a "complete" capture:
Start USBMonitor.
File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
In the upper part there are two tabs: basic and complete. Click on "Complete".
Right, Try again (duh!) OK, I've tried to keep the log files names as self-explanitory as possible... USB_monitor_log_Herm_120Radio_run1.zip is the r20 radio upgrade, 1st run and USB_monitor_log_Herm_120Radio_run2.zip the second run - without disconneting or resetting the device.
USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_ran_twice.zip is the Cingular upgrade run via the ROMUpgradeUt.exe, again run twice without disconneting the device.
Hope I got it right this time.....Please let me know if there is anything else I can do.
Thanks.
This time you got the captures right
- You're on bootloader 1.06: You don't have 'rtask' command, you won't be able to do any radio upgrade only.
- Your device is not CID unlocked (Security level=FF, unprivileged)
- The bad flash caused the CID area to corrupt (CID: Wait interpreter timeout)
- When flashing a full ROM you get a CID not allow (255) this is because your corrupted CID doesn't match the CID on the ROM.
The radio part is screwed, you could have fixed this if you where in bootloader 1.04 by flashing a full ROM, but as you are in 1.06 you can't because of CID checking. But you're lucky because the OS ROM is intact and you can boot the OS, you should be able to downgrade to bootloader 1.04 from OS and flash a full ROM after, which will hopefully fix your radio.
Just wait until a solution to downgrade bootloader is available (I'm working on it).
Hi,
As I suspected.... Suppose it's not all bad news though - just means that I have to be patient and use my communicator once more. Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
I have already got a IMEI-CHECK sim unlock from where I originally got the M3100 unlocked from Orange to work on o2. That said, I have run either unlocker 2 or 3 with the .unl that I know worked I now get
HTC HERMES v3c unlock
Starting communication.........
Checking device..............ERROR
The device you try to unlock is not supported.
Please contact your supplier site.
Device is rebooting
Press any key to quit this application.
I'm currently chatting to the guys at IMEI-CHECK re this problem.
Anything else I can do to assist you in anyway??
Cheers
wotthefok said:
Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
Click to expand...
Click to collapse
They have it (M3100v3cUnlock.exe), but it will not work on your device because your IMEI is corrupted and their unlocker will not be able to read it and to check/compare with the .unl key file.
Hi,
Just a quick update. The guys at MIGsofT LTD have VERY VERY generously said they'll have a look at the problem for me so my phone will be winging it's way to them today.
Thanks for your assistance and helping me be certain of the problem and to better understand the root cause.
Hope this information will prove useful to others.
Another quick update...
The guys at IMEI-CHECK (MIGsofT LTD) have rectified problems with my handset and managing to reinstall bootloader 1.04 in the process!!
They also turned my phone around in under three days and only charged me the cost of postage! I had previously been a customer of theirs but it was still a very generous and helpful offer and I would certainly pay for the service than have a duff handset - after all £250 + for a paperweight is rather excessive....
If you're experiencing a problem like mine why not get in touch with them and offer them money to have a look at your handset? No Guarantees but it seemed like my last chance, for a while anyway.
Praise to IMEI-CHECK for a brilliant service - they are King of the day !!
I bought a new HTC Softbank X01HT phone from China and bought it back to New Zealand. I have successfully changed all the settings to NZ network, except quite often it won't ring when someone calls me... I have got sms/txt working, internet access working, i can make calls, and sometimes i can receive calls...
If i take the battery out and restart it, I get a message which says "Your current operator 53001 is not supported. You should obtain an update from your device vendor..."
The countries pre supported are Ausi, hong kong, INdo, Macau, Malaysia, Philippines, Singapore, Taiwan, Thailand..... but not New Zealand.
My ROM version s 1.23.707.4
Rom Date 07/21/06
Radio Version 1.16.00.00
Protocol Version 32.53.7018.01H
Model Herm200
Pocket PX
Vodafone have been no help as they say they don't support parallel imported items, nor were Imate, same reason, kind of expected that.
Any ideas? this phone is really cool, but if i can't receive calls or roam with it, its basically useless for me...
ROM upgrade?
upgrading your device's ROM (and radio ROM) will probably fix your problem.
you should COMPLETELY read the wiki here at http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes and also Mr Vanx *excellent* upgrade guides at http://www.mrvanx.org/cms/
read BOTH before you try to upgrade or risk bricking your device. however, a ROM upgrade will probably fix your device.
does not seem like your device is SIM-locked (or else it wouldn't work at all with your SIM), but you might want to read http://forum.xda-developers.com/showthread.php?t=301952 nonetheless
Sounds like you've got one of the Dopod roms installed. There are a few things you can try before upgrading the rom and radio.
1. Ignore the message. Just install the operator settings for your carrier manually or with a pre-made cab file. Some of them are listed here http://wiki.xda-developers.com/index.php?pagename=Hermes_provider_cabs , others you'll probably have to search for.
2. If installing your own settings still causes a conflict try deleting the other settings or use Bandswitch to disable them.
3. Try a hard reset and then, just before the customisations start, do a soft reset. The stuff Dopod put in their extended rom won't be installed but you'll also lose the 'operator not supported' message. You'll also have to manually input your carrier settings.
4. Upgrade to one of the wm6 roms but, as SkyyBoy says, be careful. Definately run Olipro's hardspl 2.10 (hardspl v7) and read Mrvanx's guide before beginning.
Oh yes, could you extract the 'you got message' sms notifies and post it here. I think it's kind of cool, but I'm too lazy to downgrade my rom just to get it.
I've just downgraded to the same ROM as you and I'm fine sending and receiving calls using my O2 and Vodafone sim cards (both from UK). I'm currently in UK but have also used this rom in China without problems.
The only difference between your and my setup is that I currently have radio 1.38.00.10. Yours is 1.16.00.00 which is (I think) the radio which comes with pof's CID/SIM unlocker - because the original shipped radio with this rom is 1.06.00.10. This suggests that the phone is super CID (a good start).
The radio is a bit old (which could be the problem) so I'd suggest upgrading it to at least 1.27.00.00 - but you'll have to read the threads and do some experimenting to find the best one for you. You can get the radios here http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms.
Before you upgrade the radio use olipro's hardspl 2.10 (V7) http://forum.xda-developers.com/showthread.php?t=296722. An error during radio upgrades is the quickest way to brick your phone and hardspl 2.10 will allow you an easy way to recover from this.
I am facing the same problem in order to add TIM Brasil, however I am not finding any cab file with the configurations
Someone could help me, please please?
This is becoming a common issue and there are a lot of people with a bricked Hermes devices, usually because of a WinXP crash, bad USB port, USB hub or pulled USB cable while flashing.
This thread is in the aim of finding a solution to all these common problems: if you are the owner of a bricked hermes, please post your comments here instead of opening a new thread.
There seems to be 3 types of bricked (or dead) hermes devices:
Type 1 bricks: Corrupted radio area: No GSM, No CID, no IMEI
Usual reason for that is flashing whent wrong when RUU was flashing the radio stack (GSM.nb). Other reason can be that you flashed radio from another device (universal unlocker run on hermes, for example).
Within the type 1 bricks, there seem to be two variants:
Type 1a:devices which can boot windows mobile but can't use the phone functions.
Type 1b: devices which can't boot windows mobile and are stuck while booting, see also type 2 bricks below.
Type 2 bricks: Stuck in boot process
Usual reason for that is that flashing went wrong when the RUU was flashing any rom part different than IPL and SPL. Symptoms can vary depending on which is the ROM part affected. The most common is OS because it is the bigger part. Radio is the second most common.
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
Type 2b: When the phone boots, it stays in subslpash screen (htc or operator logo)
Type 2c: When the phone boots, it doesn't pass the windows mobile logo
Hybrid Bricks: combinations of both type 1 and type 2 bricks
These usually have a corrupted radio and are stuck in bootloader, unfortunately these are very common too, and the most dificult to repair.
We made a wiki page long time ago whith the solutions that have worked for some people to fix bricks, unfotunately these solutions do not work for everyone, some devices are more bricked than others
First thing you have to do is visit this wiki page and follow the process explained: Common upgrade problems
If you can't repair your brick after following the process, please provide a USB monitor capture in ANSI text format (this is explained on the wiki page too) as this is the only thing that can give us a real idea on what your exact problem is. Please don't come crying and say "help me" because we can't help you if you don't provide useful information, you are in front of a big problem and you will have to loose some hours reading and experimenting before repairing your brick. If you are not willing to loose some hours reading, go and send the device to the service centre for a repair as it is the only valid solution most of the times.
Hopefully after research of everyone in this thread we can find new solutions for some of the bricks
EDIT: Please use axiom's comment below as a template for your comment and attach USB monitor capture: If your bootloader is 1.04 attach capture when trying to flash an extracted radio ROM and when trying to flash a shipped rom update. If your bootloader is 1.06 or 1.09 only attach the usb monitor capture of the shipped update.
EDIT (2007-03-22):
After more than 3 months since this thread started and more than 660 comments, we have now solutions for some bricks, so I compiled the most common on this unbricking guide:
How to unbrick your bricked hermes
Please spend some time reading through the wiki and thread comments before posting desesperately, otherwise you'll get no answer.
The following info may help in isolating the problem and keeping the clutter down.:
I'm including my info.
Model: O2 XDA Trion
ROM Before Flash: Dopod 1.23.707.4
Radio Before Flash: 1.16
Bootloader Before Flash: 1.04
Flash failed at: 6%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
Hi, I've managed to brick my Hermes as well.. First time on any of my HTC Devices....
Model: Vodafone v1605
ROM Before Flash: Voda Launch ROM
Radio Before Flash: Not sure
Bootloader Before Flash: 1.04
Flash failed at: 8%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
You may already know this, as I posted it in all over the other threads of people with bricked hermes, but I'm posting again to make sure every piece of information is concentrated on this thread, and see if finally this can get us somewhere
HTC bootloader returns data encapsulated in a block between HTCS (start) and HTCE (end), before the HTCE there's always a 4-byte checksum of the data. You're getting a timeout when you query the bootloader for the device's CID, so the output you see is "F" which means failure (T means success) encapsulated in this HTCS/HTCE block, plus the checksum. The CID is read from the security area of the device, found on radio, but the wrong flash corrupted the radio area.
As the CID is not returned, the error you get when flashing the ROM is "CID Not allow (255)". The security level depends on CID, as the device has CID corrupted, the security level returned is FF (255), which means you can't bypass CID check in bootloader.
You both have bootloader 1.09 which does enforce CID checking (as opposite to bootloader 1.04 which has a known bug to circumvent this). This bootloader also only allows updates with bootloader version > 1.09 (and no such bootloader exists yet).
Bootloader 1.04 allows to flash unsigned code in radio with radio bootloader command 'rwdata', but radio bootloader is accessed through command 'rtask' and this command has been removed in following bootloader versions.
All the commands to flash code in bootloader 1.06 and above require the code to be signed (the commands are 'wdatah' and 'lnbs'), and bootloader checks the signature before the code is actually flashed on the device. So modifying a 1.04 bootloader to show itself as 1.10 is not possible because it will return a certificate error and will not be possible to flash.
Command 'lnbs' doesn't check CID, but it is only enabled if device has security level=0, and as your radio is corrupted and your seclevel=FF it will not be possible to use this command to fix it even if you had a signed bootloader, so 'wdatah' is the only command that would allow you flashing code, but 'wdatah' requires a NBH header to be sent, which contains the CID of the update and is checked against the missing CID on your device and will never match (even if you could modify the NBH header and have a valid signature after).
In conclusion, my recommendation to you is that you send the device to service centre to get it repaired and don't try to fix this by yourselves, as you will go nowhere.
Many thanks for explaining it so succinctly Pof, much appreciated. With this error I've learnt a heck of a lot more about the ROM flashing process... I guess it may be time to send the unit for repair!
This is the full report after I soft rest my phone while the USB is still connected. Would any one know what the rest of the data means? I did it in the morning then just left it for the day to see what would happen, I just got back from work.
onj: can you use axiom comment as a template to provide information?
radioerror.txt: I see you're using the Himalaya upgrade utility there... rbmc reads data from memory, but I don't know what is at 0x70010000. It would be better if you can provide a log of hermes RUU.
Model: x01ht
ROM Before Flash: i-mate
Radio Before Flash: 1.07.03.10
Bootloader Before Flash: 1.04
Flash failed at: 0%
Flashing ROM: JASJAR_WWE_19096_19505_11300_AKU_3_2_ship
Flashing Radio: 1.13.00
Bootloader After Failure: 1.04
CID Before Failure Super CID: success
CID Corrupt: don't know
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: stalls
Current Device Status: unusable
I will upload the usbmonitor with using
RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP
the upgrading dies after info 3
computer says ERROR [222] Device not responding
that's with all the RUU's that I use and even the full upgrade ROM
Hi, I have a herm 200 an i have a Type 2a bricks (it goes directly to bootloader mode tri-color screen).
But i upgrade with the rom (ME_DT_WWE_1182553_106_10303_Ship) and all run good. but 3 moths later i have the type 2a bricks.
I try with that solution (http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems) and others and NOthing.
In screnn say herm200 ILP-1.00 and Her200 SPL-1.04.
ps: sorry my english is very bad.
@onj: Oh ****! You where trying to flash an HTC Universal ROM in your HTC Hermes!! These are different devices, most probably that's what screwed it.
From your attached file I see bootloader does not answer to any command.
@landtd5: please use axiom comment as a template, and attach USB monitor capture when tryng to flash a shipped rom and a radio rom.
Yup, I upgraded with the wrong Rom. After going through the forum for the past 2 weeks I realized what I did. I guess it's time for me to send it to the shop
thanks for you help pof
jash431 Dead Tytn
I had tytn with this rom
"TYTN_me_dt_wwe_1182553_106_10303_ship" which has bootloader 1.04
And I upgraded with
"RUU_HERMES_HTC_WWE_1.35.255.2_1.35.255.102_1.08.00.10_SHIP"
during upgrade stopped and after that I cannot do anything with it
It never answer to any solutions .
Please help me .
USB monitore is attached here .
jash431 said:
USB monitore is attached here .
Click to expand...
Click to collapse
This is not useful: You saved LGS file, please follow instructions in wiki, you need to EXPORT as ANSI TEXT file. Also please use the 1st comment as a template to provide useful information.
Jash431
I exported in ansi text
@jash431: doesn't return anything... when you connect to bootloader on mtty, do you see the USB prompt? does it answer any commands?
Jash431
I'm sorry . this is complete one .
yes I can work with mtty.exe and my info 2 is "HTCSF kEØ(HTCEUSB>"
jash431: hybrid brick with corrupted radio and bootloader 1.09. Send it to repair centre.
jash431
is it theorically possible to fix my tytn . I mean maybe in future someone make a downgrade or SuperCID rom !! .
Because in my country doesn't exist repair center (Iran) . So what can I do ???
then keep it until something is found to fix this, creative solutions to the problem will come to your mind after looking everyday at a $500 brick.
Jash431
Thanks pof for your answer . I'll check my private message every day , for your solution and I remember you whenever I see a 500$ . ( Of course 500$ doesn't exist but you do ).
Hello,
I have a big problem with my german HTC Mozart ( T-Mobile version ).
2 weeks ago I flashed a RUU Rom to unbrand my mobile.
With this Software version my mobile is still branded and don´t work correct.
I would write more about the problems whith my mobile and this firmware, but my English is to bad….
After that I can´t flash any other Rom.
I tested to Install many other Roms, but the RUU installer every time says “Wrong Model ID”.
Then I looked my Phone Informations and see:
OS Version: 7.0.7004.0
Firmware revision number:2250.09.12803.111
Hardware revision number: NA
radio software version: 5.52.09.16_22.33a50.10U
radio hardware version: 0.0.0.0
Bootloader Version: 1.28.2250.3(113810)
Chip-SOC: 2.2.5.0
With the Rom, I flashed should be something wrong…
The Information on my Boot Mode Screen ( Rainbow) should be wrong, too
MOZA100 SS-BC (4K)
SPL-1.28.2250.3(113810)
MicroP (LED) 0x07
Touch C1(v69)
SD SANDISK 15193MB Class0
Partition Info-v211v413
In a german forum I found the same problem , but there are no solution.
Also I tested, to flash with a Goldcard.
I read all instructions to create a Goldcard an how to use it in this forum.
I think my created Goldcards are all OK but the USB HOST Screen every time says:
1. Loading
2. Checking…
3. And 3 second Later Serial on the bottom of the Display, but nothing else is happens..
Any Ideas?
so you have this problem for two weeks now?
what rom did you flash?
check the mozart forums:
http://forum.xda-developers.com/forumdisplay.php?f=779
and maybe this will help you:
http://forum.xda-developers.com/showpost.php?p=12120618&postcount=6
Yes, i have this problen for 2 weeks now.
It was a unbranded T-Mobile 1.28 rom.
Thanks, i have found someone else, with the same Problem, but no Answers.
see here
I have my Goldcards created with Ubuntu and Windows... Ubunto to find the CID and Windows, to create it...
And it seems to work, because the mobile is loading and checking the rom of the goldcard, but 3 seconds after checking... is the serial messeage in the bottom of the display and checking.. on the top, but nothing happens...
I had the same problem with my HTC 7 Trophy, flashing a new ROM did not work, and it changed the Model ID of the Phone. Once that has happened there is no way to flash a different ROM.
I tried various tools to try and get the Model ID changed back, if you use MTTY you can read the Model ID, but I don't think you can change it with that tool.
In the end I had to send mine to back to HTC to get the mainboard replaced.
hm sounds very bad..
but i think i saw the awnser somewhere...
try checking other wp7 devices forums,
hd2 people are very active..
hd7 people too...
somewhere ive read about some "force rom download mode" by pressing camera button on boot too, dont know if there was truth in it...
you say you had the t mobile 1.28 installed or you did try to install it?
it is not "unbranded" if its from tmobile (or do i get the term unbranded wrong?)
i belive there are 3 different t-mobile roms: TMO-DE, TMO-CZ, TMO-AT
these are all branded roms,
if you want unbranded you get: HTC-EU or HTC-Generic
ive used this method to unbrand my mozart from tmode 1.25 to tmode 109 to HTCEU 1.28
if you come from TMODE (as a german you should) you may want to try the 109 rom (works without goldcard)
so that i understand right, you can use the OS but you cannot make calls because of the cooked radio?
Hi, I have a German rom 1.28 installed, because i only can choose German or English language, but I do not remember which version it was. I think I previously had to install a 1.09.
However, there is something not been in order.
I think that the "force download mode" for this time is just for Zune, but I try to search for more information.
If I could flash any firmware I would do, but there is the problem with my "Model ID".
I think, the goldcard method is the right way, but it don´t works.
To eliminate errors about my hardware ( selfmade y-cable and hama 19in1 usb-cardreader ) I have ordered a delock y cable and a single usb-sd reader to try it on weekend again, but I think, the hardware is not my problem.
But i can test it not before weekend, because I´m a truck driver and only on the weekend at home.
Phone calls can I do with this firmware.
My display is out, if I choose a phone number. This time I only can hang up with the headset or by take out the battery
It works again until the other person accepts the call or the mobile hangs up automatically after 8 or 10 rings.
The volume of the headset ( earphones and micro), with this firmware is to quiet, too.
There are many problems….
somebody else with 1.28 and problems?
you dont need goldcard to flash back to stock rom
you should be able to flash any stock tmode rom without goldcard.
try to flash 109 without goldcard.
I´ve tried to install the
“RUU_Mozart_TMO_DE_1.09.001.16_5.50.09.15_22.23.50U_Signed_by_ansar”,
but after 1% my mobile reboots and the RUU Installer says:
244 wrong “MODEL ID”
are you sure it is a german Mozart?
this rom you flashed is made for unbranding.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=817691
just saying....
that suxx have you tried this?
Zetabit said:
Problem Solved!
Here are the steps I took to resolve the issue I was having, with the Mozart stuck at bootloader, "Enter USB Host...".
First I formatted the SD-card, then used my brothers Android phone with ASTRO File Manager to extract the CID code from the SD card.
1. Insert the SD card into the Android phone
2. Start the ASTRO File Manager
3. Navigate to sys/class/mmc_host/mmc1/mmc1:aaaa (instead of aaaa there could be something else as well)
4. Long press on the 'cid'-file
5. First select Open as, then Text
6. Then select File-Editor
7. Write down the number 1 to 1 onto your PC/Mac
Once I had the CID code, I used http://psas.revskills.de/?q=goldcard to generate & email me the goldcard image file.
I formatted the SD card at this point, FAT32, 4096 sector size.
I then used HxD Hex Editor and Disk Editor to copy the goldcard.img into the first sector the SD card.
Heres how:
1. Run HxD as Adminstrator
2. Open the SD card by going to Extras > Open Disk > Physical Disks (important) > Removable Drive. Make sure Open as Read only is unchecked.
3. Open the goldcard.img by going to Extras > Open Disk Image.
4. From the goldcard.img, Select All and Copy all bytes.
5. Paste into the first 384 bytes of the SD card - offset(h) 0x0 - 0x170.
Next I copied a European ROM on the the SD card (in explorer as you would with any file) and rename it to MOZAIMG.nbh
With the Y-cable I booted the phone and to my disbelief it started and successfully reflashed the phone.
http://www.youtube.com/watch?v=0t_xNdf9DeQ&feature=player_embedded
Hope this helps!
Click to expand...
Click to collapse
there has to be a way to fix it.. or maybe not
the other guy said he got his mainboard changed, maybe you broke it.. damn...
@pik.
I have tested to flash the "RUU_Mozart_TMO_DE_1.25.111.05_5.50.09.18_22.24.50_RELEASE", but after 1% the same problem "Invalid Model ID"
@webwalk®
I have created the gold card according to these instructions.
I have no Android phone, so I have the part to find out the cid solved with an Ubuntu Live CD and my built-in Cardreader.
The goldcard seems to work, since it goes from loading in checking..., then it is always the same on serial
Edit: Yes, I´m sure, that it is a German HTC Mozart.
i've the same problem with 1.28
can someone help us?
i have the same question
my hardware version is also NA
dsmps said:
Hello,
I have a big problem with my german HTC Mozart ( T-Mobile version ).
2 weeks ago I flashed a RUU Rom to unbrand my mobile.
With this Software version my mobile is still branded and don´t work correct.
I would write more about the problems whith my mobile and this firmware, but my English is to bad….
After that I can´t flash any other Rom.
I tested to Install many other Roms, but the RUU installer every time says “Wrong Model ID”.
Then I looked my Phone Informations and see:
OS Version: 7.0.7004.0
Firmware revision number:2250.09.12803.111
Hardware revision number: NA
radio software version: 5.52.09.16_22.33a50.10U
radio hardware version: 0.0.0.0
Bootloader Version: 1.28.2250.3(113810)
Chip-SOC: 2.2.5.0
With the Rom, I flashed should be something wrong…
The Information on my Boot Mode Screen ( Rainbow) should be wrong, too
MOZA100 SS-BC (4K)
SPL-1.28.2250.3(113810)
MicroP (LED) 0x07
Touch C1(v69)
SD SANDISK 15193MB Class0
Partition Info-v211v413
In a german forum I found the same problem , but there are no solution.
Also I tested, to flash with a Goldcard.
I read all instructions to create a Goldcard an how to use it in this forum.
I think my created Goldcards are all OK but the USB HOST Screen every time says:
1. Loading
2. Checking…
3. And 3 second Later Serial on the bottom of the Display, but nothing else is happens..
Any Ideas?
Click to expand...
Click to collapse
i also have this problem,somebody say that use the "JTAG"can fix it.
does anybodu solve this problem on mozart?
regards
please help if you can i cant flash any rom and i want to go to dft
please help i cant flash anything please any solution
my problem is very similar to yours. i have tmob de mozart too and this vender id error after flashing an official europe rom....
i ordered goldcard tools from amazon but they arent here maybe in three days. but i think it would be the same problem as yours.
->
i had at first the dynamics7 1.00 mango rom installed on my htc mozart.
after that i made rspl to 1.28.
after that i tried to install RUU_Mozart_S_HTC_Europe_5.12.401.02_5.71.09.02a_22 .51.50_RELEASE. the flashing started. than the phone restartet and installed spl 5.12 but the flashing doesent went to finish because of vendor id error.
now i cannot flash any stock tmob de or htc europe rom because of vendor id error. (clear because of spl 5.12) but the slspl rom doesent work, too. every flashing stops at 1%....
PD 67100 SS-BC (4K)
SPL-5.12.2250.2 ( 135167) MNG
os 7.10.8107.79
firmware 2250.21.51301.401
hardware 0004
radio 5.71.09.02a_22.51.50.21U
radiohardware A.102.0.D4
bootloader 5.12.2250.2 (135167)
any solution for me? is it maybe possible to send lower spl via cabsender?
Don't use wrong ver
aggelosss5 said:
please help if you can i cant flash any rom and i want to go to dft
Click to expand...
Click to collapse
Be carefull with DFT i halfbricked my bootloader, now I cant flash any rom, can't use the phone.
I am looking for new method maybe JTAG is the only way out of this.
Thank if helpful:good: