Dead Atom - Please help - iPAQ rw6828, XDA Atom Software Upgrading

Hi,
I tried updating my XDA Atom to WM6 using one of the roms from this site. The flash worked up till the last part when it was meant to reboot when something wnet wrong and it crashed.
My Atom is now dead - no reset method works, even the soft reset and camera combo...
i think the bootloader has been corrupted.
So i followed the guides on this site and made the Jtag interface to reflash the bootloader. The cable works fine, the orange LED is flashing - i've installed the software, but every single time i try to flash the bootloader, i get the error below....can anyone help as i want to get my Atom back
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.

anyone? i'm hoping there is something atupid that i've missed out which will get it working again...

HI, I'm having the same problem while trying to update my atom, now my atom dead. Can u Try to help me, since u got experinces of setting up the cable.. I don't knoe how to do the cable things ..pls help [email protected]!

manni said:
Hi,
I tried updating my XDA Atom to WM6 using one of the roms from this site. The flash worked up till the last part when it was meant to reboot when something wnet wrong and it crashed.
My Atom is now dead - no reset method works, even the soft reset and camera combo...
i think the bootloader has been corrupted.
So i followed the guides on this site and made the Jtag interface to reflash the bootloader. The cable works fine, the orange LED is flashing - i've installed the software, but every single time i try to flash the bootloader, i get the error below....can anyone help as i want to get my Atom back
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Click to expand...
Click to collapse
Just try press and hold soft-reset button before run jflashmm.
Cheers,
Benz

manni said:
Hi,
I tried updating my XDA Atom to WM6 using one of the roms from this site. The flash worked up till the last part when it was meant to reboot when something wnet wrong and it crashed.
My Atom is now dead - no reset method works, even the soft reset and camera combo...
i think the bootloader has been corrupted.
So i followed the guides on this site and made the Jtag interface to reflash the bootloader. The cable works fine, the orange LED is flashing - i've installed the software, but every single time i try to flash the bootloader, i get the error below....can anyone help as i want to get my Atom back
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Click to expand...
Click to collapse
Try to reset button before use JFlashMM. I'am same as problem with you. but i use resistance(R) is 390 ohm.(390*4)because voltage is more it damage to CPU or M-system chip, warn about long of wire connector if more long signal is loss. 1st. reset button Avery time as you flash JflashMM (JTAG). anf finally
my atom is incoming .......Good luck to you.

I have a problem when upgrading ROM: whether upgrade rom by SD or ASync, the progress bar always stucked at 36%. Any ideals?

Related

Dead - Hermes - Pls Advise

Earlier today (many hours) my son accidently removed the USB cable from my phone when it was flashing when I'd popped to get drink and he wanted to move it to get something, now my Hermes is dead.
I was flashing a rom (as I have done plenty of times before).
I've tried everything I can think of and read, battery out 20 mins, set 14 0, hard reset, soft reset, re-flash etc...
...the issue is it starts to flash when teh SPL 1.04 loader screen shows, but dies immediatly at 0%.
I can connect via mtty and have done. A few details from my current session...
IPL CRC checksum = 0xB266044D
SPL CRC checksum = 0x3BF03635
CE CRC checksum = 0x3A6882B2
ExtROM CRC checksum = 0xFFDF0212
Radio Image CRC checksum = 0xD30714EC
...is it possible to use mtty to upload an image file, if so what image file should I use and also how? The guide at the Wiki seems to point to the lnbs command but I cannot get it to work.
Would appichate any help here... ...my beloved phone!!!
You cannot solve this problem. Now your ROM does not even have a complete Windows Mobile ROM so how does resetting is going to help. These issues are best to be dealt by cellure carrier or by manufacture warranty. On the Wikis I have read, it clearly stated pressing and buttons or disconnect the USB cable will result in a permanent halt for Windows Mobile devices.
mms6 said:
You cannot solve this problem. Now your ROM does not even have a complete Windows Mobile ROM so how does resetting is going to help. These issues are best to be dealt by cellure carrier or by manufacture warranty. On the Wikis I have read, it clearly stated pressing and buttons or disconnect the USB cable will result in a permanent halt for Windows Mobile devices.
Click to expand...
Click to collapse
I am not sure I spoke about resetting, my question was tho, as I had paritial connectivity, can I use MTTY to upload a file.
It's not a problem tho now, got it sorted.
mms6 said:
You cannot solve this problem. Now your ROM does not even have a complete Windows Mobile ROM so how does resetting is going to help. These issues are best to be dealt by cellure carrier or by manufacture warranty. On the Wikis I have read, it clearly stated pressing and buttons or disconnect the USB cable will result in a permanent halt for Windows Mobile devices.
Click to expand...
Click to collapse
You are an idiot aren't you.
Father L ... I don't know your answer, as I have never had a bricked Hermes - at least not to the extent you do.
Stick around though, and I promise you, you will get a SENSIBLE answer from someone here soon.
mms6 said:
You cannot solve this problem. Now your ROM does not even have a complete Windows Mobile ROM so how does resetting is going to help. These issues are best to be dealt by cellure carrier or by manufacture warranty. On the Wikis I have read, it clearly stated pressing and buttons or disconnect the USB cable will result in a permanent halt for Windows Mobile devices.
Click to expand...
Click to collapse
I suggest you STOP dealing out advice right now...go read up.
(gonna start a new post incase it gets confusing)
Father L said:
Earlier today (many hours) my son accidently removed the USB cable from my phone when it was flashing when I'd popped to get drink and he wanted to move it to get something, now my Hermes is dead.
I was flashing a rom (as I have done plenty of times before).
I've tried everything I can think of and read, battery out 20 mins, set 14 0, hard reset, soft reset, re-flash etc...
...the issue is it starts to flash when teh SPL 1.04 loader screen shows, but dies immediatly at 0%.
I can connect via mtty and have done. A few details from my current session...
IPL CRC checksum = 0xB266044D
SPL CRC checksum = 0x3BF03635
CE CRC checksum = 0x3A6882B2
ExtROM CRC checksum = 0xFFDF0212
Radio Image CRC checksum = 0xD30714EC
...is it possible to use mtty to upload an image file, if so what image file should I use and also how? The guide at the Wiki seems to point to the lnbs command but I cannot get it to work.
Would appichate any help here... ...my beloved phone!!!
Click to expand...
Click to collapse
Please take a look in the wiki at THIS PAGE....
Then take a look in the unbricking thread HERE.
By the looks of it your Radio image is ok so you should be fine to flash a WM5 retail ROM...make sure its a ROM for the correct device type (so for a TyTN use a HTC ROM...or an 8525 use a Cingular ROM etc...)..
The wiki page says to try flashing it TWICE...when it hangs on the first attempt leave it as it is then run the RUU again.
READ THE WIKI and the thread first however do NOT just follow my advice.

Model No. says H instead of HERM200

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

dead hermes? corrupted radio? Post comments here

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 ).

Flash_f000_2_32.dat ?? Loader needed for Atom Life

C:\Repair\JFlash_MM>jflashmm pxa27x32 ebo_a.nb0 N 0 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
C:\Repair\JFlash_MM>jflashmm pxa27x32 ebo_a.nb0 N 3F40000 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 4 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Check This
Cannot open input file: Flash_f000_2_32.dat
How do i revive this Phones (((
I am in Gr8 tension
what u do with ur phone?
kingofhearts said:
Check This
Cannot open input file: Flash_f000_2_32.dat
How do i revive this Phones (((
I am in Gr8 tension
Click to expand...
Click to collapse
What were you trying to do?
Actually i was upgrading my phone and unfortunately instead of ATOM life i upgraded to different model and i wrote the Eboot file via memory card now only orange light blinking near the speaker and its not recognised on USB although i did all possible efforts to revive my phone but unsuccessful. I made that J-TAG cable and its working fine 100% but the thing is the loader is missing in JFlash_MM through which we program the flash IC. Although it have another different loaders and dat files but the one which i need is missing. ATOM LIFE and ATOM EXEX both have different loaders.
Looking forward to hope for the favorable reply.
Kind Regards
Haseeb
jtag problem
Dear
I am Adil from Islamabad, I have the same problem with my atom life phone.
I repair my phone with the help of repairing shop located Islamabad(blue Area) if you want help, contact me 0345-6501650
madil said:
Dear
I am Adil from Islamabad, I have the same problem with my atom life phone.
I repair my phone with the help of repairing shop located Islamabad(blue Area) if you want help, contact me 0345-6501650
Click to expand...
Click to collapse
Can you please give me the instructions you got from the repairing shop, via email, [email protected]
Thanks.
help!!! Adil
adil pls help me repair my atom life it has a dead bootloader u said u have revived it through a repair shop in islamabad well than pls give me the instructions of how 2 repairs atom life would be really appreciated
thanx a lot
jtag image
could you post an instruction to the jtag image, because my atom life is dead as well and the jtag method under wiki is not working for me.
please help to get atom life back to life
very appreciated.
MrQ

HD2 won't flash any rom anymore

Hi,
I'm in the possession of a HTC HD2 which is unable to flash pretty much anything anymore.
It's using the shipped SPL: 1.42.0000 so I figured I can only flash it with the HTC roms.
I tried doing that but it stops with error 244, Invalid Model ID.
Ok, next step, I bought PSAS to create a golden SD and but the 1.48 stock NBH on the SD card. (renaming it to LEOIMG.NBH). This worked once though but it then stopped at the very beginning and didn't respond anymore.
I retried flashing from sd with that same rom but that failed with the following error code: 00058002
Next I tried to install the HSPL3 from this forum but that resulted in the following error:
CRITICAL ERROR
Flow: 00000003
Error Code: 00000004
Description: Bad Model ID!
I attached a screenshot of the SPL so you can see the weirdness in here.
(I think this is why it fails to flash any rom)
Above the SPL version, there should be the ROM version if I'm correct?
That just shows gibrish...
I've tried numerous methods in this forum.
Is there any way out of this mess?
Thanks in advance for any suggestions!
you have a corrupted model id (top line in bootloader)
i have not seen anyone fix this,,,,, jtag perhaps? warranty?
I think I'm gonna have to try the warranty.
The device was having issues from the beginning.
The sound was stuttering or did sound a bit "electronic", when you tried to go to about this software when it was still working, it just rebooted the phone...
It's a new device, nothing has been done to it yet since well, nothing really works
yea get it swapped. don't mention flashing, of course!
thx m8,
Will sure try that! This being the device is only one week old and hasn't been functioning properly from the beginning.
Greets

Categories

Resources