He Guys,
Just my luck I have bought an HTC Tytn with the original Dutch rom and sim unlocked second hand.
I wanted to put a new Dutch rom from HTC on it but I keep on getting the ERROR [244] : INVALID MODEL ID but what I don`t understand is I have used the original Dutch rom from HTC. So I checked the device information and under the tab identity it says;
Model No.: H
Platform: PocketPC
IMEI: xxxxxxxxxxxxxxxxxxx
Shouldn’t the Model No. be HERM200?
Has anyone any suggestions in how I can solve this problem so I can flash any rom I wish.
I have tried al the cid unlock programs I could find and in bootloader it says;
H
IPL-1.01
H
SPL-1.40.Olipro
Thanks in advanced.
Use RAR to unpack the Original Dutch ROM.
Take the NBH file that you get when you unpack the ROM.
Put it in a folder with CUSTOM_RUU from Olipro.
Run CUSTOM_RUU and it will load up the ROM from the NBH file, bypassing the CID check. Should work
Thanks for the reply,
I have tried what you suggested but I still get ERROR [244] : INVALID MODEL ID I have also read these posts http://forum.xda-developers.com/showthread.php?t=322231&highlight=CUSTOM_RUU+from+Olipro and http://forum.xda-developers.com/showthread.php?t=322119&highlight=CUSTOM_RUU+from+Olipro and http://forum.xda-developers.com/showthread.php?t=309707&highlight=CUSTOM_RUU+from+Olipro and tried these suggestions but every time I get the error message. The radio update process was the same for me it will go to 7% and then give the message ERROR [244] : INVALID MODEL ID.
I have also tried the HTC_Hermes_SIM_CID_Unlock_v3a and Hard-SPL-V7 but still get the error message.
I hope I’m doing something wrong if not then I hope you have a new suggestion.
Thanks in advance.
Please set your device in BOOTLOADER MODE and post here your IPL / SPL versions.
Junner2003 said:
Please set your device in BOOTLOADER MODE and post here your IPL / SPL versions.
Click to expand...
Click to collapse
Did you read first post?
VivaErBetis said:
Did you read first post?
Click to expand...
Click to collapse
Ups, missed the bottom - thought it is the signature already! Sorry, haven't had my coffee yet!
Well, looks like the device is CID unlocked!
How about trying to flash an entire cooked ROM?
i would suggest the following:
flash a cooked rom (any)
see if that makes any difference to your model id
then try and flash the native dutch rom
good luck
Hi Guys,
As you suggested I tried a cooked rom the Hermes_WM6_vanilla still get the same error message when I put my device manually in boot loader it shows;
H
IPL-1.01
H
SPL-1.40.Olipro
But as soon as I try an official or cooked rom it shows;
H
IPL-SSPL by des
H
SPL-1.09.ds
I’m now trying Schaps_WM6Pro_WWE_4.00_Full_Beta3.exe and choose for auto detect and it said 1.40 Olipro and in boot loader it shows;
H
IPL-1.01
H
SPL-1.40.Olipro
And after 1% I got the ERROR [244] : INVALID MODEL ID message again.
I think my options are getting slim.
Your ModelID is stored on NAND and can be edited quite trivially (mostly).
how it got corrupted I don't know, however, the important question is; can you get into the OS?
He Olipro,
The device it zelf works perfect I can go anywhere I want even in the OS.
Just lead the way.
Changing Model ID
I have a similar problem in that my Model ID got corrupted during a radio upgrade. I now get the same error (244) and am stuck on SPL2.10 and can't downgrade to fix it. Can anyone tell us how to manually change the model ID in the NAND?
Much appreciated.
Dumping NAND
Ok, I'm a relative newbie so appologies before I get flamed. Thanks Olipro for giving me a clue.
I have now got spl 2.60 on my device but am unsure how to dump the NAND. I've worked out how to dump the 3 partitions from the device to dump the OS but am still unclear which part of the device is the NAND. I've read the Wiki on the memory map but am still not too sure.
Anyone able to give me simple instructions to dump the NAND and once I've done that where abouts is the ModelID stored? Do I do this using mtty?
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=322225
NAND Dump
Thanks Drummer for pointing me in the right direction.
Ive done this bit:
BTW, if you want to do a full backup of you FULL eeprom nand at any time, connect as before and type these commands:
plink HERMES > full.nb (hit ENTER twice)
task 32 (hit ENTER once and only once from now on after every command)
password 0000000000000000 - My device password is BsaD5SeoA which I used instead.
set 1e 1
rbmc me.txt 50000000 7fff800
watch your file grow to 128 MB.
It creates a full.nb file but it stays at 1k!!
** Note I have copied the bootloader file for spl 2.60 on my Hermes and ran that so I can now use that versino instead of the 2.10 thats on my device if that makes a difference and have tried with no joy with either version. Yes I know it says to use 2.30 but I can't work out how to get that on my device due to the ModelID error.
The Model number is contained within the herm1.nb file that was posted by BusStop in that thread. No need for complete NAND reflashing, only that section. You'll see it using a Hex Editor. You should write down your WiFi MAC addess, so you can edit it before flashing the file with the corrected Model number. Now you just have to figure out how to get SPL 1.01 MFG on your device...
Thanks Drummer. I did try flashing the herm1.nb file but of course as I do not have SPL 1.01 MFG it gievs an error. I'll keep trawling through the site and see if I can work out how to get SPL 1.01 onto my device. I'm not going to let this damn device beat me.
Ok so I worked out how to get the ModelID using getdevicedata. Used nbhtool to create a vaild nbh using the ModelID I'd just got and used the spl from 2.30 and it updated that fine.
Excellent.
However did the same with the MFG1.01 and flashed it and......
I now have a dead brick, no power and no response form usb. Time to get a replacement device.
Thanks for all the help I've had. I'm sure it should have worked.
1.) Remove battery
2.) Connect Hermes to charger or USB
3.) Insert the battery while Hermes is connected to charger
4.) Red light should turn Amber
5.) Soft Reset
Thanks for the advice Drummer however:
1.) Remove battery
2.) Connect Hermes to charger or USB
3.) Insert the battery while Hermes is connected to charger
4.) Red light should turn Amber - Nope red light goes out!
Mne shows HHHHHHH
Hi all, i've upgraded my radio and after my model id changed to H.
So, reading some posts i've used NBHTOOL.
1.I've decompiled an original Italian ROM
2.i've obtained a custom nbh selecting only OS and EXTROM and changing my Model number.
3. after that i've flashed the nbh resulting into a write error at 84% and a bricked htc.
Luckily i was able to reflash roms and i processed to second experiment.
I've made a custom rom with only the os, and it WORKED!
so my questions are:
1. can i use my htc even if my external rom isn't flashed (it cames from an old Schaps 4.0 succesful flash)
2. It is safe to proceed installing bootloader SPL using the nbhtool like i did with the os?
In that case i will be able to fix the model id problem by flashinh spl 1.01 and using the wireless fixing method you posted..
Thanks in advance for your reply!
Hi
From my understanding the Ext rom is mainly used for carriers to install there specific addons and customizations so it shouldn't be a problem.
As you can see I did flash spl 2.30 using this method and it worked fine ti was only when something whent wrong flashing 1.01 that my problem happened but I think that may be that I used an nbs file instead of an nb file from what I've read since.
Good luck.
Edit: Just noticed someone on this thread has managed it by going straight ot 2.60 http://forum.xda-developers.com/showthread.php?t=322225
Related
here is what I've done and what happened:
my ROM was HTC 1.18.255.3 07/22/06 with bootloader 1.04 then I ran "HERM_Unlock_v2a.exe" on the device but I didn't use "HTC_Hermes_Radio_for_SIMunlock_v1.16.00.69" to save time and i wanted a CID unlock only.
after "SUCCESS!" message from "HERM_Unlock_v2a.exe", I connected my device via USB to PC and started to upgrade to Cingular 1.31.502.1 08/30/06 with aku 2.6 and bootloader 1.06 but when I get the "ID ERROR",without disconnecting the USB, I switched back to ugrading to previous ROM HTC 1.18.255.3 and the Processe started with no problem untill 98%, then suddenly upgading interrupted a message came saying connection error or somting like that!
since then my device is stuck on windows mobile screen and I've tested solutions in the "Hermes_Upgrade Problems" page and tried using the "Hermes SD Card flashing" method, But It seems impossible to flash my phone agian.
Help me PLEASE,HELP
someone help me please!
POF can't you help me please
I think Pof is away until 3rd december, I have the similiar problems with my second hermes, if you have then use mtty to see if you have an corrupted cid using info 2.
Do you have the original rom to go back on if so that will fix your problem.
I've used mtty to send some commands to my device and it answers to some of them but It just stop responding when I type "info 2" or "info 3".
and i tried this in mtty:
"
USB>checkimage
IPL CRC checksum = 0x9FCC6BEB
SPL CRC checksum = 0x3BF03635
CE CRC checksum = 0xC0E1751A
ExtROM CRC checksum = Total Block= 1024
dwBlockIndex= 1024
Address Error1!!!
Get checksum ERROR!!!
0x0
Radio Image CRC checksum =
"
again It stop responding
also tried upgrading, no matter which ROM I try, it just can't connect to device.
and thanx for your relpy.
hi, since there is NO htc service center available around me I have to do something about it myself but my phone is still dead and I'm using a nokia 1101. PLEASE someone help me, pof are you back? can you help me?
I've tried all in this page:
"http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems"
and this one too:
"http://forum.xda-developers.com/showthread.php?t=280733"
and tested qtek 2020 rom but no use.
from what I've found out my device hang up and stop responding when it gets the "INFO 2" or "INFO 3" or "TASK 32" or perhaps any thing involving CID so no upgrading utility is able to connect to it, the only thing is to connect to it using "mtty.exe" which I've tried any command found here, but no use again.
and my SPL is 1.04
can anyone help me?
mht220 said:
I ran "HERM_Unlock_v2a.exe" on the device but I didn't use "HTC_Hermes_Radio_for_SIMunlock_v1.16.00.69" to save time and i wanted a CID unlock only.
Click to expand...
Click to collapse
Wrong, you also need a patched radio to CID unlock. Running only the exe file without the patched radio has no effect on the unit.
mht220 said:
from what I've found out my device hang up and stop responding when it gets the "INFO 2" or "INFO 3" or "TASK 32" or perhaps any thing involving CID so no upgrading utility is able to connect to it, the only thing is to connect to it using "mtty.exe" which I've tried any command found here, but no use again.
and my SPL is 1.04
Click to expand...
Click to collapse
Please attach usb monitor capture when trying to flash a ROM and a radio ROM. Otherwise can't help you.
here is exported files from usb-monitor:
and tanx for your reply
uuh... there must be something really wrong with it, no response to bootloader commands. If no sd card flashing is possible, I would suggest you to send it to service centre too.
pof said:
...I would suggest you to send it to service centre too.
Click to expand...
Click to collapse
It's a difficult option for me, as I should send it to a foreign country to service center,so are you sure there is no way like erasing somewhere using mtty?
pof said:
... no response to bootloader commands...
Click to expand...
Click to collapse
but it respond to some of them in mtty.exe e.g. "erase", "set" and some other.
pof said:
...If no sd card flashing is possible...
Click to expand...
Click to collapse
no it would stuck in "checking..." forever
tanx
HI,
I have same exactly problem on my spv m3100: since sept06 I've tried every kind of Unlock software,upgrade ROM and method found in xda..In mtty bootloader (spl 1.04) respond at every command but not "info 2","info 3" and "task 32".Sd card method works but if you try to upgrade other ROM,in your screen "loading..." and then "checking..." hangs on because the ROM upgrade must to match CID (I suppose..).I'll wait the next ROM Upgrade and ORANGE won't release it until gen07..
warrio said:
I'll wait the next ROM Upgrade and ORANGE won't release it until gen07.
Click to expand...
Click to collapse
it seems your problem is like mine if so, I don't think ANY normal upgrade can solve your prolem 'cause it can't connect to it.
so don't wait and send your device to service center, if you can.
I'm in your same conditions:there's no repair center here so I have to wait Orange who release a upgrade Rom (I hope asap..).
Hi,
I just got my hermes / tytn yesterday and from the first hour on I try to get the device upgraded to wm6 or english (it came with a german image)
Here is the software versions i currently got on it after installing cid unlock and so on.
rom-version: 1.18.257.2
radio version: 1.16.00.00
protocol version: 32.53.7018.01H
extrom version: 1.18.257.106
I tried to upgrade it with RUU_Hermes_QTEK_WWE_2.11.255.1_102_6275_1.38.00.10_108_Ship
WM6_21005_GER_11500
The detection steps of the upgrade work fine. But as soon as the device boots in the bootloader it just stays at the 4 color screen with the following infos:
IPL-1.01
SPL-1.10.Oli
It doesnt start the upgrade and after a while the program on the pc gives me a connectionerror.
Can you help me to track down the error? I read around the wiki and forums but couldnt find anyone with that error.
Thanks and regards,
Passi
EDIT: just to add: I also tried to install hard SPL7 which didnt work because I get the following error when I start the application on the hermes:
Datei oder Assemblyname'System, version=2.0.0.0,Cultur=neutral' Publictoken=.......
Anyone seen that before?
1. Make sure your XP computer has .NET v2.0 or later installed to use CustomRUU.
2. Upgrade to HardSPL latest version
3. Extract the NBH file from the upgrade (use winrar or 7zip) & flash it using CustomRUU.
ok, that worked now. Only problem now is that the radio version of the image i used wont work and my tytn is stuck at the htc screen now. It shows no gsm for about 1 second at the beginning. I will try to reflash another vendor image using the smartcard method in about 10 minutes. Hopefully that will work.
Thanks and regards,
Pascal
I tried using the flash with sdcard method but somehow it wont work. My bootloader is SPL-1.04. I copied an nbh file over to the card, renamed it to HERMIMG.nbh and reset the device to enter bootloader. It shows loading for a part of a second and then returns to regular bootloader screen.
Any ideas what could be wrong or what could be done to flash the image with the sdcard method?
Thanks for any help,
Passi
Edit:
after reformatting my sd card with my pc i finally got the bootloader to recognize the image. Sadly, still no success at all. The bootloader recognizes the flash file but then gets stuck at the checking.... point. Is there any way around that? Im really out of ideas.
Closing this thread as you already posted in the right one:
http://forum.xda-developers.com/showthread.php?t=286755
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 ).
anyone know what rom is compatible with athe100 SPL 1.10 ?
i know theirs lots of 1.2 and 3.5 spl roms, i tryed to flash a 3.5spl on my phone and now only way i can turn on the phone is in bootloader, i try to flash the phone but it always gets stuck at 1%, can anyone assist me?
cowballz69 said:
anyone know what rom is compatible with athe100 SPL 1.10 ?
i know theirs lots of 1.2 and 3.5 spl roms, i tryed to flash a 3.5spl on my phone and now only way i can turn on the phone is in bootloader, i try to flash the phone but it always gets stuck at 1%, can anyone assist me?
Click to expand...
Click to collapse
Have you took the sim card and memory card out?????
Jay
yes they are both out when tryign to flash, been over a week with out a working athena
cowballz69 said:
yes they are both out when tryign to flash, been over a week with out a working athena
Click to expand...
Click to collapse
try flashing your original ROM which should be found in the wiki section.
ignore what I said below and report back if you were able to load your original ROM
***Ignore this read above**Once your phone is working , do the athena wrapper which should load SPL 1.2
Also read this
http://forum.xda-developers.com/showthread.php?t=429013
yes I tryed to flash the original rom (its a wm5 i beleive to), still gets error after 1%,, downloaded both on the wiki and the ftp site, =\ been over a week so far no clues on why i cant flash, i even tryed to change the mac address using mtty, but instead of going into level = 0 , i get level = FF witch means the phone is locked out from flashing anything threw mtty,
thank u guys so much for responding on my issue
I also tryed doing the unlocker and its a no go
If the error when it stops at 1% is "invalid model id" the solution is here http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
cowballz69 said:
yes I tryed to flash the original rom (its a wm5 i beleive to), still gets error after 1%,, downloaded both on the wiki and the ftp site, =\ been over a week so far no clues on why i cant flash, i even tryed to change the mac address using mtty, but instead of going into level = 0 , i get level = FF witch means the phone is locked out from flashing anything threw mtty,
thank u guys so much for responding on my issue
I also tryed doing the unlocker and its a no go
Click to expand...
Click to collapse
I think this means your phone is not unlocked
with respect to sergiopi , you cant do the mtty script.
I would suggest you msg cmonex or try to talk to her on IRC on the
dxa-devs channel
addendum
seeing that you have nothing to lose, why dont you try flashing the original rom from the sd card using the method in the wiki
cowballz69 said:
anyone know what rom is compatible with athe100 SPL 1.10 ?
i know theirs lots of 1.2 and 3.5 spl roms, i tryed to flash a 3.5spl on my phone and now only way i can turn on the phone is in bootloader, i try to flash the phone but it always gets stuck at 1%, can anyone assist me?
Click to expand...
Click to collapse
I have the same problem.
what I do...
I have ameo t-mobile...windows mobile 5.0
run AthenaUnlocker
Step 1 make all finish noc problem
Step 2 hung up on 60 %
bootloader no problem....but can´t flash original flash always stuck at 1% and reboot...
flashing the original rom from the sd card using the method in the wiki ...
make it, but no do...on screen see
cheking...
loading....
than come on screen
0002802
ching...
loading...
not allowed
sergiopi said:
If the error when it stops at 1% is "invalid model id" the solution is here http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
Click to expand...
Click to collapse
My error when it stops at 1% is "invalid vender id"
my image version is demaged
Re: Ameo from t-Mobile german - repair
________________________________________
hi
what is your CID? use mtty command "info 2" to find out.
for example, if it is TMOB_007, you have to find a shipped athena rom with that CID.
if you cannot find a matching rom, let me know, i can still help,
cmonex
HTCS Þ?ÒtHTCE
please need halp
thx
felix999
read this post http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
read this post which tells you how to run mtty
follow the instructions to start mtty then press enter to get the cmd prompt
then type info 2 to get your CID
depending on this you will be able to flash the apprpriate ROM
lakeman said:
read this post which tells you how to run mtty
follow the instructions to start mtty then press enter to get the cmd prompt
then type info 2 to get your CID
depending on this you will be able to flash the apprpriate ROM
Click to expand...
Click to collapse
in mtty this can read:
when type task 32
become LEVEL: FF
when type info 2:
HTCS Þ?ÒtHTCE
my CID is 1.1
on bootscreen can see this:
ATHE100
IPL-v1.00
ATHE100
SPL-v1.10.RP00
what I do before...
Ameo WM 5.0 >>>>my mistake not update to WM6.0
run AthenaUnlocker
STEP1>>>OK
STEP2>>>by 60 % hang and stopped....
and now have the big problems.....Image ROM of t-Mobile 5.0 german demaged
can´t flash any rom´s
thx for hel or I want to pay bucks for service, when ma ameo live again...
felix999
lakeman said:
read this post which tells you how to run mtty
follow the instructions to start mtty then press enter to get the cmd prompt
then type info 2 to get your CID
depending on this you will be able to flash the apprpriate ROM
Click to expand...
Click to collapse
this is my CID
Cmd>info 2
info 2
Wait interpreter timeout
HTCS Þ?ÒtHTCE
????????
don´t know
felix999
Athena mobile 6 > SPL 1.10
become today a answer from crazy cat, that olipro say must take an rom in athena forum....
I flaswh with so many roms...anytime same error: error 294 - invalid vendor ID.....
My SPL 1.10 >>> can´t find a rom with SPL 1.10
what rom can repair my demaged ameo?????
thx for help
felix999
problem solved with ONLINEHELP from>>>>>cmonex>>>><<:::::>><<:::E:::>><<:::R:::>><<:::F:::>><<:::E:::>><<:::C:::>><<:::T:::>>
thx
felix999
lakeman said:
try flashing your original ROM which should be found in the wiki section.
Click to expand...
Click to collapse
Is this how you solved your problem?
Hello, I am in serious trouble! I got a brand new HTC Athena with Windows Mobile 5.0. I succesfully upgrade it to Windows Mobile 6.0.
All was OK.
Than I was interested to move into Windows Mobile 6.1 and possibly 6.5. At first I did the Athena unlock (3 step process) and all went OK: Antenna 1.5.0, SPL 1.2 OLI....
THAN I DID MY ERROR! I try to upgrade my 6.0 ROM with the Micky 6.1 cooked file with SPL 3.5. After a 92 percent upgrade, the ROM crashed and now I always get a nasty black screen with few lines (No 3 color bands!). When I try to upgrade again the same ROM or ROM for SPL 1.2 I get an error (ID mismatching). I guess the only solution is a hard and full reset of the Windows. But doing only a hard reset with the PDA will NOT change my error message and I will keep see this nasty black screen and I cannot load the Windows ActiveSync application-
I am totally lost. Help please. Any tool for a true full restore/recover??? (I did NOT make any backup!).
This thread might hold a solution to your problem.
Hi
If you follow the instructions exactly in post 33, it will solve your problems. just click HERE
Jay
Hello, those links are basically for corrupted wifi antenna files.-
In my case my HTC Athena crashed the Windows 6 ROM while I was attempting to upgrade, after unlocking the phone, the Athena from version 6.0 to version 6.1
Are you sure I can use the post #33 also for my specific trouble?
Thank you in advance!
this is also to repair your bootloader-infos
if you look at your bootloaderscreen, you will see ATHE100, IPL, ATHE100, SPL. if not, you have to repair it
make sure you flashed the right rom, spl 1 or 3.5
How can the bootloader get repaired?
yes use that link, post #33. fixes both wifi and modelid problems and bootloader problems when you got stuck at 92% of the flashing process.
Cannot re flash ROM
Please help! I tried the unlocker and it failed at 92% and since then I have no WM6. Then I tried to flash the Michy WM6.5 and that failed. I was getting model id errors so I did the mtty and mac1 fix which was succesful. However all I can get now is a grey screen on boot-up. I can get to the bootloader screen and it displays ATHE100, IPL-v2.02, ATHE100, SPL-v1.20. Olipro. From what I have read on the forum at this stage I should run a RUU to flash a WM6 ROM but all that I try can't connect because no OS running to connect with Activesync? Is there a way to flash from the bootloader? The other option seems to be putting an image and flasher on a miniSD but I can't find clear instructions for this or which files?
Please ignore - my battery wasn't charged enough. Replaced battery and recovered device.
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
I have follow the link (thread 33)...., however, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
first, how can I get the mac address of my device? It is NOT written anywhere in the Athena parts (checked in the battery bay and so on.....), and so when I run mtty i am in trouble! I have used a mac address got from my company's manager, but not sure it is ok to use it with the Athena!
Anyway,......I have follow the post link (thread 33)...., and followed the various steps.- However, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Solved!
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
puffo said:
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
Click to expand...
Click to collapse
Can you tell what you've actually done after you've changed ROM with Mtty?
I done the thing with Mtty but just as you described when I reset it now I still get the grey screen. And if I try to update ROM it fails again on 92%
where did you find the upgrade from wm5 to wm6?
the link I found on rapidshare seems not be availabel anymore