Related
Firstly, let me thank everyone for their help in advance.
Tonight I tried upgrading my ROM to the newest Cingular ROM. I'm on Cingular in NYC and have been having radio problems so I hoped Cingular's optimizations would help. Anyway, I was running the i-mate ROM previously. I have done this many times. During the ROM upgrade, it gave me the usual Device ID error so I restarted the upgrade utility and evertything was good. Well, at 19% progress it stalled, eventually crapping out citing a communications error. The device won't reboot now.
I got the device in tri-color mode and began the process again. The upgrade stops with Device ID error, but now the restart trick no longer works! I also tried updating it with both the original TyTN ROM and the i-mate ROM I was previously using. They all crap out with a Device ID error! Now I have a paper weight because it also won't boot with what was loaded previously, hanging on the Windows Mobile splash screen.
Does anybody have any advice or solution???
Thanks...I'm desperate here!
See this page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Connect to your device bootloader using mtty.exe and issue the commands "set 14 0" and "task 8". This will (hopefully) boot the existing imate rom.
If this does not work run the commands "checkimage" and "info 8" and paste the output here. For more info read the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Alternatively, you can try to flash it using HERMIMG.nbh on SD card:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Thank you...I'm going to try this in just a few minutes. Needless to say...I'm sweating!
OK guys, this is what I got running "checkimage" and "info 8". What do you think?
USB>checkimage
IPL CRC checksum = 0x24C42773
SPL CRC checksum = 0x9382C208
CE CRC checksum = 0x5D6A925D
ExtROM CRC checksum = 0xFFF79D19
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3FB(1019) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19C00
Partition[3], type=0x4, start=0x1CC00, total=0x1DC00
CE Total Length(with sector info) = 0x3A66000
CE CheckSum Length(without sector info) = 0x3980000
USB>
Any clue on what this data means?
Thanks
CJNYC said:
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
Click to expand...
Click to collapse
Your radio is screwed. Format your microSD card and copy the NBH file contained in a rom upgrade (if possible use one that matches your CID). Rename the NBH file to 'HERMIMG.nbh' and put the microSD card on the phone. Power on the phone in bootloader mode and you should see the flash confirmation, press the power button to confirm and wait 30 min. This process is described in more detail here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Good luck
Thanks POF...this will be the first thing I do tonight. I'm keeping my fingers crossed and will report back as soon as I'm done.
Thanks!
OK, that didn't work either. When the bootloader went to load the ROM from the Micro SD card I got the following message...
0028002
Not Allow
Any other suggestions??? Thanks
CJNYC said:
0028002
Not Allow
Click to expand...
Click to collapse
The NBH file you used doesn't match your CID. Use a NBH file that matches your CID.
You can see your CID by issuing bootloader command "info 2".
If you have an HTC branded Hermes (HTC TyTN) your CID will be QTEK_001, then you need an NBH file with this CID, for example "hermimg_QtekNOR_1.18.255.3_Ship.nbh" contained on HTC TyTN WWE rom.
pof...
That's the exact ROM I used and I do have an HTC branded TyTN. When I issue the "info 2" command all I get back is an "HTCSUSB>" prompt. Am I missing something?
Thanks
Probably mtty.exe doesn't parse the output of "info 2" correctly and that's why you can't see the CID, but if it is an HTC TyTN then your CID must be QTEK_001 and there should be no problems with the NBH you used... it is very weird that you get this error.
Did you try the "set 14 0" command to start OS after reset? If you can boot WM5 again you can run GetDeviceData.exe from your device to see your CID, otherwise you can use USB Monitor and look for the output of "info 2" there.
Another thing you can do is to start the TyTN 1.18 ROM upgrade using the normal procedure (RomUpgradeUt.exe), but capture the output of all the upgrade process using USB Monitor, and then export it to text file and attach it here. We will be able to see the error from bootloader and where exactly it stops the flashing process:
1) Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2) Put your device in BootLoader mode
3) Connect device to computer using USB cable.
4) Start USBMonitor.
5) File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6) In the upper part there are two tabs: basic and complete. Click on "Complete".
7) click on RomUpgradeUt.exe and start the Rom Update Process, if everything went fine you should see all the USB traffic output on USB monitor window.
8 ) when rom upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9) Save the file and zip it.
10) Upload the zipped file here or put it on xda-dev FTP if it is too big.
OK, I used USB Monitor and recorded the results of the upgrade attempt, which of course failed. Please see the attached file.
What do you think? Any hope?
Thanks...
-Craig
When the flash utility tries to get the CID from your device it gets this error:
CID: Wait interpreter timeout..
Click to expand...
Click to collapse
Info 2 should return:
Code:
"HTCS" + 8-byte CID + 4-byte checksum + "HTCE"
In your case the output of "info 2" shows this:
Code:
48 54 43 53 00 01 09 8C 5C 30 08 8C 66 17 09 7C HTCS...?\0.?f..|
48 54 43 45 HTCE
Your CID: 0x0001098C5C30088C (...?\0.?)
Output of "info 2" for HTC TyTN should show this:
Code:
48 54 43 53 51 54 45 4B 5F 30 30 31 D6 00 3D 07 HTCSQTEK_001.=.
48 54 43 45 HTCE
Normal CID for HTC TyTN: 0x5154454B5F303031 (QTEK_001)
I don't know what caused the CID to change, and it is not possible to change the CID on a NBH because signature will not be the same and you'll get a signature error. We don't know how to change the CID on the Hermes yet, probably someone will come out with a solution but now I don't know what to do....
Are you able to send back your device under warranty?
I'm going to try to ship it to the HTC repair center in Germany and see what they can do for me. Who knows how long this will take. I might pick up a Cingular 8525 when they are supposedly released on Friday and see how that goes. I'm not happy. I really like this device and simply wanted the Cingular network optimizations.
pof...I really appreciate the help and effort. In another thread, people are complaining that this same Cingular ROM is changing the CID's and locking phones. Oh well, back to the drawing board.
Thanks again!
CJNYC said:
In another thread, people are complaining that this same Cingular ROM is changing the CID's and locking phones.
Click to expand...
Click to collapse
Are you refering to user fun_key, not being able to downgrade after flashing cingular's 1.31 rom? He has checked and his CID remains the same, and I haven't heard of anyone having his phone locked for upgrading a ROM.
I've investigated into it, see my post here:
http://forum.xda-developers.com/viewtopic.php?t=63355&start=25
I guess your problem is that the rom upgrade flashed your bootloader and you cannot use the HERMIMG.nbh from the TyTN rom because it contains a lower bootloader version (1.04) while you have an higher bootloader version (1.06).
You can check your bootloader version by issuing the command "info 7".
Now you have tree options:
- wait for a rom upgrade with bootloader >= 1.06
- send your device to repair center
- wait until some xda-developer finds out how to downgrade the bootloader
I definitely understand this issue with the newer bootloader. Would it not stand to reason that I'd be able to re-run the Cingular ROM that failed or is this simply an issue now with the CID needing to match the original TyTN ROM?
Thanks again!
The TyTN has "flash from microSD" option much like the Wizard. On my 8125, IIRC, an SD based reflash ignored everything and put the base image + bootloader + ROMs back on; completely restoring the device to original factory specs.
I'm not sure if this is the same on the TyTN or not but it may be worth a try. The Wiki on this says that using the HERMIMG.NBH method to restore from SD may or may not ignore CID. At very least you could update the Wiki if it doesn't work
@CJNYC: I'm not really sure if your problem is related to bootloader version, CID or both.
@Sleuth255: He already tried sd-card flashing, if you follow the whole thread.
oops, now I see it. My bad...
Hi everybody,
I bought my V1605(French SFR) today and I decide to unlock it with HTC uni Unlock V1 in order to work with my business SIM card.
At the end of the unlocking I've got an error, telling me to try to install again. After resetting my V1605, It stop on Operator logo. I try hard reset but nothing happened, I'm still stuck on operator logo.
Bootloader is in 1.04.
My V1605 is no longer recognized by activsync, I tried with mtty, but impossible to connect on usb.
I tryed to reinstall the original rom, but V1605 can't be find. Same for other rom.
I tryed everything on hermes upgrade Problem page, but nothing works.
When I try to update rom by microsd, it's not working. I have read the wiki page.
Have you got any idea ? You'll be my hero... I'm really in a dead end.
Thanks in advance,
Geof
- disable usb connections on activesync
- put hermes in bootloader mode and connect to computer usb port
- start usb monitor capture ("complete view")
- start update of original rom (retry two times if it fails first)
- when finish, export usb monitor capture to ANSI text format, and attach it here.
Thanks for your help.
It seems that my V1605 is disconnecting when I try to update
oops! the file shows nothing useful. seems disconnected after the first usb setup packet.
When you put it in bootloader mode and connect to usb port, do you see in the bottom part of the screen the string "SERIAL" changes to "USB"? or it stays "SERIAL" ?
Have you tried a different usb port on the same computer? or even a different computer?
Do you get any error when trying to flash from SD card? do you see the "checking...." ?
I tried on 2 computers and on each usb ports...
When I try to update, it stays on usb and never come to serial.
With the Microsd, there is a very very very fast check on card (less than 1/2 seconde), and it stay on bootloader. It seems that it wouldn't want to launch anything from the Microsd.
I retried to use mtty and it connects, but what to do.
I tried with the himalaya rom to get a better USB monitor file. It stuck on white screen on V1605 at 0% on PC.
G3oF said:
With the Microsd, there is a very very very fast check on card (less than 1/2 seconde), and it stay on bootloader.
It seems that it wouldn't want to launch anything from the Microsd.
Click to expand...
Click to collapse
Try it several times... sometimes it is a bit hard to make the bootloader read the image. Make sure you only put the french voda rom NBH file renamed to HERMIMG.nbh on the microSD card, and nothing else.
G3oF said:
I retried to use mtty and it connects, but what to do.
Click to expand...
Click to collapse
checkimage
info 2
info 7
info 8
set 14 0
task 28
...
USB>checkimage
IPL CRC checksum = 0xAB6DDB32
SPL CRC checksum = 0x3BF03635
CE CRC checksum =
USB>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, Bootloader Version : 1.04
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x5
USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19D00
Partition[3], type=0x4, start=0x1CD00, total=0x1DB00
CE Total Length(with sector info) = 0x3A86800
CE CheckSum Length(without sector info) = 0x39A0000
USB>info 2
USB>set 14 0
Write Nand Success
HTCST ÚÈÒHTCEUSB>
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 461
Storage Total block: 475
Total Bad Block in CE: 0
NeedToEraseBlockStart: 474
Storage format success
As you can see some command not working. It seems those commands interrupted the USB link. Have you ever seen this before ????
I continue to try updating by sd, but seems not working.
Thanks for your help
Do you think I have to send it to technical center ?
Probably it's a good desition if you can't fix it by any other way.
I ask for replacement and thy agreed. I'm surprised but very happy. I'm not sure to try to unlocked it right now ;-). Thanks again for your help
Hi
Recieved this fone from a friend
He Flashed the radio on this phone & now phone get stucks on Windows Mobile Logo .
I dont know which Radio he flashed ...
Now phone also not connecting as he says me ..
I dont know all the details .
this is written when HTC shown on startup .
M 05
S 04
B 05
D 1.18
on Boot Loader
HERM200
IPL-1.00
HERM200
SPL-1.04
so any one advice me correct solution how to repair ..
Thanks
Aamir Zia
try this
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
I did Read all
I make Hard Reset successfully
After that on HTC screen , it says NO GSM Then shows White Screen & nothing after that ..
I also did this
Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt.
Type the following commands (do not copy paste!!!)
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
But still not connecting when i flash to Patched Radio
I got error in the end
Error [222] Device not Responding ..
Who can Help me ...
Can you get into bootloader mode?
Yup !!!
I can go into Bootloader mode
HERM200
IPL-1.00
HERM200
SPL-1.04
Now phone comes back to its Original Condition ( Stucked on WINDOWS MOBILE ) ... after leaving it without Battery for 20 minutes ....
But phone still cannot be read ...
Leave it at least 10 minute on windows mobile logo if its manage to pass it.
Next step maybe you can try fired up MTTY & execute below command
1. task 32
2. info 2
What is the output?
While phone is stucked in Windows Mobile Logo i leave it for 15 minutes
but it didnot passed .
&
When i try to enter this command with MTTY
Software Hangs & not responds ....
aamszia said:
While phone is stucked in Windows Mobile Logo i leave it for 15 minutes
but it didnot passed .
&
When i try to enter this command with MTTY
Software Hangs & not responds ....
Click to expand...
Click to collapse
You can try this but I am not sure whether its works or not.
At bootloader screen, try flash full release roms that matching your Hermes CID. or flasing this patch radio roms
http://wiki.xda-developers.com/index.php?pagename=Hermes_SimUnlock
Well i have written above that when i try to Flash the PATCH RADIO ROM
i got this error
Error [222] Device not Responding ..
Phone cannot be detected by software , even computer detects the driver .
& i dont know from where phone is come from ...
POF !!!!
Please help me out here with HTC Tytn
Here are some details via MTTY
Info 2 is not working
info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, Bootloader Version : 1.04
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x5
USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3FB(1019) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19500
Partition[3], type=0x4, start=0x1C500, total=0x1E300
CE Total Length(with sector info) = 0x3982800
CE CheckSum Length(without sector info) = 0x38A0000
USB>
help ,my phone's hang on too..
but display SPL-1.09,
and supercid is lost.
i can't boot x01ht now.
Aamszia:
Look in the following thread at post numbers 120, 236, 237, 238, and 239
http://forum.xda-developers.com/showthread.php?t=286755&page=12
Once you have used these methods to get access to the PDA, put the sspl on a memory card and run it on the pda.
Once you have done that, plug back in to a usb port and run whichever updates you want/need
Mike
Mike
Can You come on Chat Please
Thanks
Hi aamszia,
What do you need to know?
hi
me too, i m stucked on the windows mobile screen ! i'm in bl 1.09.
Sensation !!!!
We have found a method to restore dead Boot for
Atom, Atom Exec, Rover G5, Orsio n725, HP6815 (may be the all 68xx series).
We found JTAG and developed the recovery technology!
FAQ is translating from Russian and will be written.
Autor's Alex_Beda & 1stMASTER
--------------------------------------
Manual to restore dead BootLoader
Atom, Atom Exec, Rover G5, Orsio n725, HP6815 (may be the all 68xx series).
© Copyright to Alex_Beda & 1stMASTER
PDA-HACK.NET Team http://pda-hack.net
If our article has helped you, you can donate the Web Money
WMID 378286389551
for WMZ: Z396747110007
for WME: E114645323227
for WMR: R351032339900
Thanks to all who helped.
Thanks to Winterice for the technical assistance and moral support.
Thanks to ant 125 for useful information
Thanks to Allbest, deniska.75, Borozavr, Erke for moral support.
Symptoms:
The device is not switching on, not entering bootloader.
(most often after the firmware from a memory card)
React to connect charger.
if the battery insert and connect charger, it orage led must be lit .
if the battery remove and connect charger, it orange led must be flashing.
There is only one way for restore bootloader.
Reflashing flash memory in the PXA272 using JTAG.
This procedure consists of two parts.
Hardware (making cable for reflashing) and software (reflashing).
Hardware part:
This pinouts JTAG of Atom Exec, Rover G5, Orsio n725, O2 Atom, O2 Atom Exec
At O2 Atom (not Exec) is the only internal contacts. Located near the Camera button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are contacts inside the device, near the buttons CAMERA,
for access them, you need to open device.
There are contacts from the outside, near the SIM connector.
All contacts is working
For inside contacts need this connector
http://i218.photobucket.com/albums/cc23/alex_beda/raz012.jpg
You can so using connector from floppy drive 5.25”. (autor vic180)
http://i218.photobucket.com/albums/cc23/alex_beda/PICT0267-.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/PICT0262-.jpg
LPT connector for PC
http://i218.photobucket.com/albums/cc23/alex_beda/LPT1.jpg
Cable length of a 35-40 sm
This connector for outside contacts
Result connector from connector for floppy drive 5.25"
http://i218.photobucket.com/albums/cc23/alex_beda/raz1.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/raz3.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/vid2.jpg
for fixation connector need make this
Or other
http://i218.photobucket.com/albums/cc23/alex_beda/kreplenie.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/vidkrepl.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/vidobsh.jpg
Software part.
[url]http://wiki.xda-developers.com/uploads/RepairBootLoader.zip[/URL]
In attached file is the programm JFlashmm,
in the same directory BOOTLOADER from АТОМ ЕХЕС (ebo_a.nb0) from First Firmware,
and driver the giveio needed for working cable.
If you have O2 Atom (not ЕХЕС), it must be in the folder jflash_mm Deleted file ebo_a.nb0,
copyng the file boot.nb0 from O2 Atom firmware in the jflash_mm folder and renaming this file in ebo_a.nb0.
Before connecting LPT connector , you want to press and hold
micro button near to the sim connector.
http://i218.photobucket.com/albums/cc23/alex_beda/knopka.jpg
For example: sticker on the button.
Ground from LPT connector, connecting on ground the device
(using the crocodile connector)
http://i218.photobucket.com/albums/cc23/alex_beda/ground.jpg
Connect cable to LPT port of PC.
Connect charge to the device
Orange LED is blinking.
If LED not blinking,
Check pressed the micro button.
check fixation the button.
Installing the driver giveio from attached file.
Now you can restore BootLoader.
BootLoader needs to be restored in two places.
Need boot flashing to adress 0 and address 3f400.
In folder jflash_mm there is a file start.bat.
Inside this file:
jflashmm pxa27x32 ebo_a.nb0 P 0 PAR
jflashmm pxa27x32 ebo_a.nb0 P 3F40000 PAR
So file ebo_a.nb0 (boot from атом exec) will be flashing in two places,
To adress 0 and adress 3f40000, data send to parallel port.
Execute start.bat, if all right , you correct making cable,
it must detect processor.
If message screen on "file *.DAT not find", press Soft Reset.
the program will ask you «bla-bla-bla» Y/N? Press Y
-------
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.002
PXA27x revision ??
Found flash type: 28F256L18B
Unlocking block at address 0
Erasing block at address 0
Unlocking block at address 10000
Erasing block at address 10000
Unlocking block at address 20000
Erasing block at address 20000
Unlocking block at address 30000
Erasing block at address 30000
Unlocking block at address 40000
Erasing block at address 40000
Starting programming
Using BUFFER programming mode...
Writing flash at hex address 3fe80, 99.85% done
Programming done
Starting Verify
Verifying flash at hex address 3ff68, 99.94% done
Verification successful!
------------
So too for the second time in firmware to address 3f4000
You can disconnect charger and cable.
Enter bootloader :
Press Camera button, insert battery and press Soft Reset.
If everything was done correctly, it bootloader is running!!!
Now, as usual (almost)
Connect the device to PC.
Run update firmware for you device.
Must go update firmware.
If all right, it .......
Operation system update, bootloader update,
Running update ExtROM, but, it should freezes at 6 %!!!!
Disconnect usb cable from device, Enter Hard Reset!!!
Device must switch on, calibrating touch screen etc.
Run again update firmware for you device.
© Copyright to Alex_Beda & 1stMASTER
Also, you might want to list the hardware we need so we can go look for it.
Ultimate Chicken said:
Also, you might want to list the hardware we need so we can go look for it.
Click to expand...
Click to collapse
Need 4 resistors 100 Om, LPT connector and
old cable for the floppy drive 5.25 ".
This is a great fine. Once you have finalized this one. Please post it in the WIKI. I have constantly updated it with relevant information for our device.
Coola
thnx for this guys....i didnt flash my atom yet because i was afraid of the boot loader problems i ve read in here.now there is no need to worry
greekfragma said:
Coola
thnx for this guys....i didnt flash my atom yet because i was afraid of the boot loader problems i ve read in here.now there is no need to worry
Click to expand...
Click to collapse
The Atom never had a problem with the bootloader. Its the Atom Exec that has it. Also, the solution the common problems with the Atom upgrading has been posted in the Wiki already.
thnx for the fast reply jiggs and sorry for the mis-writing of my post......i have atom exec and i wrote atom just to shorten my post.sorry again for the mess
keep walking mate.u are doing marvelous job in here
oh finally there's solution..i have a dead bootloader o2 ATOM..and service center said i have to replace my BOARD..and it will cost a lot..
keep it up..bro..
thankz..
-=[serialzs]=-
I dont have the O2 Atom and I dont access to the O2 Atom.
The technology will be one, but other pinouts contact (may be)
The time is dancing!!!
Tehnology is working on O2 Atom, O2 Atom Exec, Rover G5, Orsio n725.
TESTED !!!
Nice to hear
See
http://wiki.xda-developers.com/index.php?pagename=HTC_Atom
Problems (Read here before posting on Forum):
Dead Boot Loader on O2 Atom, O2 Atom Exec, Rover G5, Orsio n725
Manual to restore dead BootLoader
Atom, Atom Exec, Rover G5, Orsio n725, HP6815 (may be the all 68xx series).
© Copyright to Alex_Beda & 1stMASTER
Thanks to all who helped.
Thanks to Winterice for the technical assistance and moral support.
Thanks to ant 125 for useful information
Thanks to Allbest, deniska.75, Borozavr, Erke for moral support.
Symptoms:
The device is not switching on, not entering bootloader.
(most often after the firmware from a memory card)
React to connect charger.
if the battery insert and connect charger, it orage led must be lit .
if the battery remove and connect charger, it orange led must be flashing.
There is only one way for restore bootloader.
Reflashing flash memory in the PXA272 using JTAG.
This procedure consists of two parts.
Hardware (making cable for reflashing) and software (reflashing).
Hardware part:
This pinouts JTAG of Atom Exec, Rover G5, Orsio n725, O2 Atom, J2 Atom Exec
At O2 Atom (not Exec) is the only internal contacts. Located near the Camera button.
There are contacts inside the device, near the buttons CAMERA,
for access them, you need to open device.
There are contacts from the outside, near the SIM connector.
All contacts is working
For inside contacts need this connector
http://i218.photobucket.com/albums/cc23/alex_beda/raz012.jpg
You can so using connector from floppy drive 5.25”. (autor vic180)
http://i218.photobucket.com/albums/cc23/alex_beda/PICT0267-.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/PICT0262-.jpg
LPT connector for PC
http://i218.photobucket.com/albums/cc23/alex_beda/LPT1.jpg
Cable length of a 35-40 sm
This connector for outside contacts
Result connector from connector for floppy drive 5.25"
http://i218.photobucket.com/albums/cc23/alex_beda/raz1.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/raz3.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/vid2.jpg
for fixation connector need make this
Or other
http://i218.photobucket.com/albums/cc23/alex_beda/kreplenie.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/vidkrepl.jpg
http://i218.photobucket.com/albums/cc23/alex_beda/vidobsh.jpg
Software part.
[url]http://wiki.xda-developers.com/uploads/RepairBootLoader.zip[/URL]
In attached file is the programm JFlashmm,
in the same directory BOOTLOADER from АТОМ ЕХЕС (ebo_a.nb0) from First Firmware,
and driver the giveio needed for working cable.
If you have O2 Atom (not ЕХЕС), it must be in the folder jflash_mm Deleted file ebo_a.nb0,
copyng the fileeboot.nb0 from O2 Atom firmware in the jflash_mm folder and renaming this file in ebo_a.nb0.
Before connecting LPT connector , you want to press and hold
micro button near to the sim connector.
http://i218.photobucket.com/albums/cc23/alex_beda/knopka.jpg
For example: sticker on the button.
Ground from LPT connector, connecting on ground the device
(using the crocodile connector)
http://i218.photobucket.com/albums/cc23/alex_beda/ground.jpg
Connect cable to LPT port of PC.
Connect charge to the device
Orange LED is blinking.
If LED not blinking,
Check pressed the micro button.
check fixation the button.
Installing the driver giveio from attached file.
Now you can restore BootLoader.
BootLoader needs to be restored in two places.
Need boot flashing to adress 0 and address 3f400.
In folder jflash_mm there is a file start.bat.
Inside this file:
jflashmm pxa27x32 ebo_a.nb0 P 0 PAR
jflashmm pxa27x32 ebo_a.nb0 P 3F40000 PAR
So file ebo_a.nb0 (boot from атом exec) will be flashing in two places,
To adress 0 and adress 3f40000, data send to parallel port.
Execute start.bat, if all right , you correct making cable,
it must detect processor.
If message screen on "file *.DAT not find", press Soft Reset.
the program will ask you «bla-bla-bla» Y/N? Press Y
-------
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.002
PXA27x revision ??
Found flash type: 28F256L18B
Unlocking block at address 0
Erasing block at address 0
Unlocking block at address 10000
Erasing block at address 10000
Unlocking block at address 20000
Erasing block at address 20000
Unlocking block at address 30000
Erasing block at address 30000
Unlocking block at address 40000
Erasing block at address 40000
Starting programming
Using BUFFER programming mode...
Writing flash at hex address 3fe80, 99.85% done
Programming done
Starting Verify
Verifying flash at hex address 3ff68, 99.94% done
Verification successful!
------------
So too for the second time in firmware to address 3f4000
You can disconnect charger and cable.
Enter bootloader :
Press Camera button, insert battery and press Soft Reset.
If everything was done correctly, it bootloader is running!!!
Now, as usual (almost)
Connect the device to PC.
Run update firmware for you device.
Must go update firmware.
If all right, it .......
Operation system update, bootloader update,
Running update ExtROM, but, it should freezes at 6 %!!!!
Disconnect usb cable from device, Enter Hard Reset!!!
Device must switch on, calibrating touch screen etc.
Run again update firmware for you device.
© Copyright to Alex_Beda & 1stMASTER
serialzs said:
oh finally there's solution..i have a dead bootloader o2 ATOM..and service center said i have to replace my BOARD..and it will cost a lot..
keep it up..bro..
thankz..
-=[serialzs]=-
Click to expand...
Click to collapse
hey brother, i was in the same shoes as yours a few days ago.
had a dead bootloader since i upgraded using SD card...
there is a slight chance you can revive your atom this way (which i revived mine)
unplug the battery for a few days - then when you plug the battery in, observe the power light and the hangup button, see if it has a very quick red flash. if it does, you might be in luck.
now, hold the action button (circle button in the middle) and keep plugging and unplugging the battery in the atom. do the same on the power button and the camera button. mine worked with the action button, and it booted into the bootloader menu again!
now im flashing the original rom in the unit =)
How much can be explained?
My method is available for dead bootloader.
Absolutely dead bootloader.
(full erased, flashing the not correct file etc)
kazuni
You message - offtop and flud.
Read forums.
Read documentations.
You bootloader IS NOT DEAD!
If bootloader is dead, this programm is not correct (or no programm) in the ROM.
Programm not working.
Not enter in bootloader.
Flashing with SD card impossible.
Symptoms:
The device is not switching on, not entering bootloader.
(most often after the firmware from a memory card)
React to connect charger.
if the battery insert and connect charger, it orage led must be lit .
if the battery remove and connect charger, it orange led must be flashing.
There is only one way for restore bootloader.
Reflashing flash memory in the PXA272 using JTAG.
Click to expand...
Click to collapse
wow . thanks . although my xda atom never bricked but I'm happy that it will never happend. with your method we never see bricked atom again
alex_beda said:
How much can be explained?
My method is available for dead bootloader.
Absolutely dead bootloader.
(full erased, flashing the not correct file etc)
kazuni
You message - offtop and flud.
- #1 i am not replying your topic, i am merely helping the others and see if my method works.
Read forums.
-duh, who wouldn't read the forum.
Read documentations.
You bootloader IS NOT DEAD!
i didn't say my bootloader is dead or not dead.
If bootloader is dead, this programm is not correct (or no programm) in the ROM.
Programm not working.
Not enter in bootloader.
Flashing with SD card impossible.
Click to expand...
Click to collapse
i am just replying another person, if you have not noticed, i specifically quoted his post, not YOUR thread.
kazuni said:
i am just replying another person, if you have not noticed, i specifically quoted his post, not YOUR thread.
Click to expand...
Click to collapse
Sorry if you are offended
But your method apply for only not absolutely dead bootloader.
if bootloader is absolutely dead -
Not enter in bootloader.
Flashing with SD card impossible.
Device is dead.
Only replace board in Service center,
or reflashing with JTAG.
Is this applicable to Atom Life? I have tried but I got this error:
C:\Boot\JFlash_MM>start.bat
C:\Boot\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 ??
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: FFFF
Lower half reads: 0
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: 0
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: 0
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: 0
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.
Mr. Jiggs... Kabayan. Is there any service center of O2 Atom in the Philippines, my atom life is dead due to SD card upgrade. I am here in KSA where the services is not available. Thanks.
Can I use it for PROPHET!!
alex_beda said:
Sensation !!!!
We have found a method to restore dead Boot for
Atom Exec, Rover G5, Orsio n725, and may be Atom (Atom may be, not tested).
We found JTAG and developed the recovery technology!
FAQ is translating from Russian and will be written.
Autor's Alex_Beda & 1stMASTER
Please wait 1-3 days.
Click to expand...
Click to collapse
Hey Buddy
I know its foolish on my part but can I use this method on my o2 Neo --prophet
It does not boot at all.Al that I get when I put it to wall charger is a ORANGE LED which even remains when I remove the Batt..
Soe time again it diapperars.In either cases the area near the USB tends to get very very HOT.
Sometimes I feel it will just bust because of this heat!!
Pls do reply
This morning I ran the battery dead in my 8525 which I have done several times through out its life.
I get home and plug it in and hold the power button waiting to see the wm6 boot image from the rom I use. No go
All I get is the try color screen reading
Herm100
IPL-1.04
Herm100
SPL-2.10.Olipro
I can get it to switch between serial and usb. Did I corrupt the wm6 rom? Are there any tricks to try to get it to load wm6 one more time to dump my contacts? Can I manually dump the whole rom and pull it apart to get to my contacts?
I have removed the battery and let it sit but on re-inserting the battery it goes directly to the boot loader again.
I have tried the OK - Power - stylus reset button combo and just the stylus reset.
I am searching the forums and google trying to find something but maybe someone has a tip I have overlooked.
I went ahead and tried to flash a new rom from the bootloader and it goes 100% completes and just goes right back to the tri-color screen...
I also tried flashing Hard-splv7 and received a communication error.
Not really sure what to try next if flashing a new rom doesn't help.. Anyone got any suggestions?
OK I attmepted the type 2a brick recovery listed at
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4
Grabbed a copy of nuettyconsole and connected successfully to the phones loader console.
Ran both
set 14 0 and set 16 0
Both writes to the nand are successful but it still only boots back to the bootloader.... I am running out of ideas.
I have attempted to replace the radio rom but I continue to get a communication error.
Anyone have a link to a full stock rom with both radio/os?
I went ahead and flashed a full AT&T stock rom with both radio and wm6. The flash completed and the phone booted into the stock rom like it should. YAY!
The phone customized itself and rebooted only to get stuck right back into the bootloader loop...
Is there something wrong with the nand chips or did I just corrupt the bootloader by chance?
Anyone? Any Ideas?
Ok, finally got some time to work on this phone a bit more. I would like to get it working which I sorta have. Flashing a full(radio/rom/extended) HTC hermes_WWE rom from a xp desktop will get the phone to boot.
When the phone customizes itself it'll reboot and its random if itll reboot properly. Sometimes I have to hard reset the device or pull the battery then I can usually get the phone to boot back up and be completely usable. So I know the phone itself works with sms, 3G data, 3G voice, wifi, bluetooth and seems to run like the day I purchased it.
At this point if I attempt to reflash a cooked rom to the working phone itll finish then drop into the bootloader and will refuse to boot using any tricks until I finally reflash using the full HTC hermes_WWE rom. I was thinking that the bootloader itself became corrupt so I reflashed sspl 2.10 but that did nothing except stopping the rom from loading and leaving me stuck in the bootloader. I have tried the bootloader console access and used commands set 14 0 and set 16 0 to try to force the bootloader to load the OS on reboot all to no avail.
So where should I go from here... what would be stopping my phone from being able to load a cooked rom? Should I reflash the radio? Has anyone heard something like this?
Ok, I decided to get into the boot loader and start dumping everything I can to try to decide if this was a corruption issue. You will notice some strange stuff and if I try to run the command "rbmc" the boot loader flips out spewing garbage for 2 or 3 minutes until finally returning an out of boundary error.
Cmd>task 32
Level = 0
Cmd>info 2
HTCSSuperCID HTCE
Cmd>info 3
HTCSH
Cmd> info 4
HTCSCWS__001Ùü¤HHTCE
Cmd> info 6
HTCST ÚÈÒHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.10.Olipro
Built at: Apr 22 2007 13:32:26
Copyright (c) 1998-2007 Modified By Olipro - Hard-SPL
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x6
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x1F900
Partition[3], type=0x4, start=0x22B00, total=0x17D00
CE Total Length(with sector info) = 0x4675800
CE CheckSum Length(without sector info) = 0x4560000
Lol I might not be of much help. But seeing as noone responded to all of your 5 or so posts. Try getting a new battery, something might've happen to it ?