Hi,
it's done!!!
Today i discovered the JTAG pins of HTC hermes.
My device got bricked and was not able to boot anymore. Not even the bootlader came up.
Anyway i decided to do some investigation, there was nothing to loose
Thanks to Lt.Cmdr.Ivan who discovered the JTAG pins on the universal hardware.
(It made the step successful!!!)
See the attachment!
(had to make a zip because high-resolution pix )
These are the testpoints to access Hermes main system Samsung MPU and recover OS bootloader!
To get access to the GSM chipset please have a look in the second post!
You may use this package to access the platform.
http://210.118.57.197/Products/Semi...or/ARM9Series/SC32442/JtagFlash_Prog_Code.zip
EDIT: If the link is not working, see attachment (backup package form samsung site, source code included)
See the documentation in the archive for information how to build a LPT adaptor, to use this software!
EDIT: The software tool has been modified to handle the /WP issue.
See attachment MSP_HERM.zip!
What ever happens to IPL/SPL on your device, it can be recovered quite easily now, using the JTAG method!
EDIT: Added Olipro's 2.10 (Hard-SPL V7) for completeness.
This is a pure binary file, ready to flash via JTAG. Thanks again to olipro for this beautiful bunch of bits!!
EDIT: Due to the numerous questions of some users how to go through this, here's what has already been written down all over the thread.
Follow these steps:
1. Disassemble your device (link to the Hermes Service-Manual is in the wiki).
2. Locate the JTAG pins on PCB (download/extract htc_hermes_jtag.zip -> look at the picture)
3. Use a very small soldering iron and attach some wires to the testpoints (only experienced users should do this!)
4. Use one of the wiggler clones (LPT-adaptor) to built up a connection to the JTAG pins using LPT port of your host pc.
Please have a look in the software documentation for the schematics (JtagFlash_Prog_Code.zip -> Source files and doc included).
Whatever your adaptor would look like, follow the pin assignment, that is used in the schematic (e.g. LPT pin 2 -> TCK, LPT pin 3 -> TDI, LPT pin 4 -> TMS, LPT pin 11 -> TDO)
5. Partly assemble your device and insert fully charged battery. Check all connections and press and hold power button on hermes (min 2sec.).
Though the device won't start if your bootloader is bricked, this step is necessary to activate internal power supply.
To check if power is O.K. measure the VCC pad (VCC ~ 3.15V).
6. Use the modifed samsung software on your host (download/extract MSP_HERM.zip -> MSP_HERM.exe is a command line tool)
Please make sure that the processor is recognized. If not check all connections again!
7. Grab IPLSPL210_OLIPRO.zip, extract it and put the file the directory where flashing software is located.
8. Use flashing software (MSP_HERM.exe) and try to reflash your NAND.
type: MSP_HERM.exe /f:IPLSPL210_OLIPRO.bin
type: 1 to choose the flash type
NAND flash type on hermes is k9f1g08 and should be recognized
type: 0 K9f1g08 Program
Start page and block must be set to 0
9. Be patient and cross fingers while flash is programmed.
Alternatively you may grab some coffee or beer and relax!
10. Enjoy the rebirth of your device.
Credits:
A warm and healthy "Thank you!" goes out to pof, cmonex, cr2, the_dipe and the others who gave useful hints or helped testing.
Regards,
scholbert
HTC Hermes GSM JTAG pins
Hi again,
after a lot of wicked things had been done with my device, i decided to lift another secret.
Anyway i spent some time to do some investigation and managed to trace the JTAG testpins of the GSM chipset on the hermes!
So it's done!
To be 100% secure, this has again to be verified with some software.
Work is in progress!
To solve the "noGSM" issue we need a bullet proof flash tool to rewrite the radio bootloader.
Hopefully we could get the necessary information to do so!
Maybe someday all these "no GSM" devices could be brought to life again...
at least if it's software related issue (e.g. broken Radio bootloader)!!!
See the attachment for the pin location!
(had to make a zip because high-resolution pix)
These are the testpoints to get access to the Qualcomm GSM chipset and possibly fix broken radio bootloader!
Information about missing signals
TRST_N = could not be found (seems to be N.C.)
RTCK = could not be found (will only be needed for special debugger)
Mode0 = N.C.
We need your help!
If anyone got information about the JTAG chain of MSM6275 (BSDL file) or similar info, please PM me!
scholbert
I have used JTAG on my linksys router when I bricked it.
It's actually pretty easy to make a cable for JTAG and uploading a ROM.
Did you actually manage to revive your tytn?
Flash access
Hi,
it seems to work fine with the program from the samsung site.
I just flashed IPL & SPL to my device.
See the screenshot
scholbert
thanks for this ill look into this. im still trying to figure out which part messed up on my phone. no power anymore not even charge light. dead. hardware? i think i burnt a capacitor coz it died while charging/connected to usb. Also i just flashed a radio rom but it was successful... before it died out. is yours the same case that it did not even show life of accepting power? thanks.
i was looking at the schematics and i think i need a technician for that but if i can revive my dead phone using that since im going to try and find the messed up capacitor anyway, ill learn and research.
Congratulations!! this is a great and useful finding
Thanks
Hi again,
thank you for adding a link to this thread in the wiki!
Unfortunately my device still won't start
There maybe anything else broken.
Anyway, the JTAG thing worked very smart, programming is quite slow though.
O.K. but that's the bit banging (i just remember, once flashed an image to the skeyepad and it took nearly half a day using an LPT adaptor).
sphynx88 said:
i was looking at the schematics and i think i need a technician for that but if i can revive my dead phone using that since im going to try and find the messed up capacitor anyway, ill learn and research.
Click to expand...
Click to collapse
@sphynx88:
What schematic are you talking about???
Do you got a schematic for hermes???
Regards,
scholbert
Scematic
Hello sphynx88,
do you have a scematic of Hermes? I'm an technican and I'm used to JTAG programming. So if you have the scematic and I can have a look at it, perhaps I can help you bringing your hermes up again.
Greetings Pudl
More info
Hi,
first i'll have to quote myself:
scholbert said:
it seems to work fine with the program from the samsung site.
I just flashed IPL & SPL to my device.
Click to expand...
Click to collapse
There are some problems with rewriting flash on my device.
After some more investigation, i found out that my device still got OLIPRO'S IPL (version 1.04) but SPL is not HARD-SPL anymore (version 2.10 "Hard-SPL")
SPL was rewritten to original bootlader (version 1.04).
I made some memory dumps using the JTAG tools and compared the output with the binary files.
IPL and SPL do not match, that's why my device is not booting anymore.
For some reason i am not able to rewrite IPL with the samsung programmer.
There are no errors, everythings seems nice, but IPL remains unchanged after programming. No idea why
Maybe there's something special on hermes hardware, that protects NAND to be rewritten per default.
O.K., now that i found out what's wrong with my device, i'll have a look in the programmers source code, to understand what's going on.
I'll keep you informed about my progress
scholbert
...after having a look around, i'm quite sure that my flash is kind of blocked.
This maybe caused by damaged hardware .
If anyone would try to flash some bits to his damaged hermes, please let me know.
This would clear up if the the software provided by Samsung may be used to flash the hermes hardware and fix broken bootloaders.
At least flash content can be read out via JTAG, that's proven .
scholbert
I have bricked my hermes too.
I will try to flash IPL and SPL with the JTAG programmer.
How can I build a bin file for the programmer from an official RUU_signed.nbh or from the extracted 00_IPL.nb and 01_SPL.nb?
Hi,
bauner said:
I have bricked my hermes too.
I will try to flash IPL and SPL with the JTAG programmer.
How can I build a bin file for the programmer from an official RUU_signed.nbh or from the extracted 00_IPL.nb and 01_SPL.nb?
Click to expand...
Click to collapse
It's sad that your Hermes got bricked .
Maybe it will be the first device revived by JTAG flashing.
Here we go:
00_IPL.nb and 01_SPL.nb are already binaries.
Refer to the memory map in the wiki to know where the contents have to be placed.
So you might flash them seperately or build one file to flash (see attachment).
To make it easier have a look in this slightly modified table, it shows the block numbers of NAND flash ( :
Code:
------------------------------------------
0x50000000 Page0
Block0 IPL
0x5001ffff Page63
------------------------------------------
0x50020000 Page0
Block1 SPL
0x5003ffff Page63
------------------------------------------
0x50040000 Page0
Block2 SPL
0x5005ffff Page63
------------------------------------------
0x50060000
... not used
0x5009ffff
------------------------------------------
0x500a0000 Page0
Block5 CID, S/N
0x500bffff Page63
------------------------------------------
0x500c0000 Page0
Block6 WLAN
0x500dffff Page63
------------------------------------------
0x500e0000 Page0
Block7 MainSplash
0x500fffff Page63
------------------------------------------
0x50100000 Page0
Block8 MainSplash
0x5011ffff Page63
------------------------------------------
0x50120000
...
Good luck !!!!
scholbert
Thanks a lot for your help I flashed my IPL/SPL an now my hermes is working again
Hey
bauner said:
Thanks a lot for your help I flashed my IPL/SPL an now my hermes is working again
Click to expand...
Click to collapse
Congratulations!!!!
So everything went fine using the provided tools?
Did you use a wiggler (clone) for the job?
Best regards,
scholbert
yes everything worked fine with this tools.
I used this Interface:
Holly Gates' Schematics for the JTAG Dongle
Im sorry to have replied for so long but i gave up on my hermes and have not been checking. ill subscribe to this thread. After crazy searching and one site leading to another i did find what i think was schematics for the hermes. a service manual. it was in chinese and i couldnt understand it but i saw one for my samsung one which was in english and i think it really is the service manual with schematics. ill try and retrace my tracks. cross fingers.
anyway, in my case, the phone died. not bricked. something inside short circuited. it was on and charging via usb then the next thing when it reached 100 coz i was pretty sure it was 90 the time i started installing apps, it just died. no turning on, no nothing not even the rlod. i opened the case and i think there might be a fuse to the left of the charger entry, maybe changing it would simply fix the whole problem. i dont know but hopefully my cpu isnt broken so i may even have two phones.
JTAG flashing proven, my device definitely broken
Hi,
...anyway, in my case, the phone died. not bricked. something inside short circuited.
Click to expand...
Click to collapse
same with my second device, sphynx88.
Something hardware related is damaged.
I may use the flash tool a 1000 times, the flash seems unaccessable for programming. Maybe the WP-pin stucks to GND on my device
Anyway it's nice to access the device via JTAG, also debuggers may be used
Have fun!
scholbert
I know what's wrong
Hi again,
can't stop my investigation and like to bring my dead hermes to life!
I started to look around and i found the WP testpoint
So i made sure what i assumed, the WP pin of flash is tied to ground.
This prevents NAND flash to be rewritten -> write protection!
I made some further measurements and found out, that there must be a general purpose pin responsible for this function. Obviously this pin is set low during basic setup, maybe it's done in IPL (after reset all pins are tied low by internal resistors).
The only way to find out which pin is responsible for write protection, is to set some of the GP output pins to high level and and measure the voltage level at the testpoint (maybe it's GPC4 because it's very close to WP).
So this goes out to pof or olipro who already done a lot reverse engineering on this platform
Any idea which pin is used for NAND write protection on hermes????
Regards,
scholbert
Related
I am new of the forum, I have just purchased a nm8 used magiacian (t-mobile MDA) it is I bring a problem.
The preceding owner has begun an updating of the rom that has not gone to good end and the device doesn't now set out anymore and from the following error:
USB V1.00 (if connected USB).
Serial V1.00 (if disconnected).
Bootloader mode ?
What must I do for going on?
I hope in a help
Best regards Luca
help
I pray you helped me, the first post is from beginners, but believe I have followed the standard procedure.
unloaded the rom
unloaded no-id
always tried upgrade more times failure.
HELP !
for the beginning you should use a standard ROM to get familiar with the device.
just go to the t-mobile website, downloads, chose your device type and then look for files named softwareupdates or so.
they will be in zip-format.
there will be an application in there. just go into bootloadermode, connect your device and start the upgrade. it's completely guided and will last about 20min.
although most of the ppl that read/write in this forum didn't install the eROM, I think you can start with all the cusomization stuff. If you have become more familiar with your mdac, you can try other modified ROM's.
just ask if you have more questions
greetz Stefan
i have to say that using standard rom (jam rom downloaded from club imate)
the upgrading applications hangs.....
and leave magician in booting mode, ready to be erased....
i was desperaded, but last experiences with motorola phones and its firmwares advice me to try again
so i had to launch againg that apps and it starts erasing actual rom....
i think there is a bug in few roms.... may be only in its installer
Have tried with the T-mobile rom but doesn't even go with that!
Caslu,
Have you tried a hard-reset?
If so: I guess you've got a decent TMO magician rom downloaded. So get maupgradeut_noid.exe from the ftp. Extract all the files from your TMO shipped-rom & put them in a directory, so you get some .nbf files, enterbl.exe & maupgradeut.exe. Now put the maupgradeut_noid.exe in the same directory. Connect your magician to the usb. It should read usb v1.00, if your magician isn't in bootloader press camera&power&soft-reset at the same time for a few secs. till you get the usb or serial reading.
After connecting it to the usb execute the maupgradeut_noid.exe twice, first execute might give an error 120 second should finish.
If this fails make sure you got a magician & not a charmer.
If it's a magician return it, cause I think it's broken. Hey why buy a device that's in an inconclusive state??
Regards, M
I think really that It broken.
Have picked it because little cost!
non one reply .......
caslu said:
I think really that It broken.
Have picked it because little cost!
non one reply .......
Click to expand...
Click to collapse
Download the latest shipped ROM for the country your magician was first sold in.
Ensure Activesync is in the normal mode (USB check is ON).
Run the executable ROM update program.
Hello,
I have a HTC Wizard without bootloader. So that device cant not come up. I've searched on the net, m-system give many tool to dump from another then write it again.
But i dont know how to plug DOC into PC? What hardware did you use? How many $ for this? And are there another way to fix that?
THanx for your help
I think this might require jtag.
Not my field
V
i'm thinking the same thing
well, anyone here tried it yet?
pmquan said:
Hello,
I have a HTC Wizard without bootloader. So that device cant not come up. I've searched on the net, m-system give many tool to dump from another then write it again.
But i dont know how to plug DOC into PC? What hardware did you use? How many $ for this? And are there another way to fix that?
THanx for your help
Click to expand...
Click to collapse
VJ is right, you need Jtag programmer to reprogram a IPL/SPL erased DOC, but Jtag can not be connected to DOC directly, so you need to know abut test points to connect Jtag probes to it...
I wonder if HTC has embedded ON-Board DOC programming interface in its devices, because this technique makes DOC reprogramming more easy by connecting some testpoints to initiate on board DOC programming mechanism for onboard mini USB connector...
Hi folks,
Take it easy on me, first post and all....
Looks like i made the standard mistake and bricked my XDA orbit
I can get to the bootloader menu but cannot get any ROM to load beyond 3%.
The phone is owned by my employer and I need to sort it ASAP before the IT dept find out!!!
O2 are not interested in helping out as I cannot prove its under warranty and it now boots to a T-Mobile boot screen!!
Does anyone know where I can send it to get repaired, anyone out there prepared to sort it for a reasonable fee....???
Any help appreciated!!
Thanks
mcstorey said:
Hi folks,
Take it easy on me, first post and all....
Looks like i made the standard mistake and bricked my XDA orbit
I can get to the bootloader menu but cannot get any ROM to load beyond 3%.
The phone is owned by my employer and I need to sort it ASAP before the IT dept find out!!!
O2 are not interested in helping out as I cannot prove its under warranty and it now boots to a T-Mobile boot screen!!
Does anyone know where I can send it to get repaired, anyone out there prepared to sort it for a reasonable fee....???
Any help appreciated!!
Thanks
Click to expand...
Click to collapse
I guess you flashed it without cid unlocking it with USPL - did you not read my thread http://forum.xda-developers.com/showthread.php?t=306904
(forum rules read read read and more read)
Best option is to send it to imei check http://www.imei-check.co.uk/
they will cid unlock it for you and reflash original rom - and blag it with your boss
220v through the charging socket and ask for a new one!
Thanks Chaps!!
Have read through this forum through and through but alas a little too late!!!
Thanks for your advice though, will keep reading........
220v sounds like a last resort??
Someone else suggested a few seconds in the microwave!!!!
Did contact imei-check pasted response below:-
Hello,
Do you mean XDA neo or exec? If so we do *NOT* support this device at all. In case it is a XDAIII, XDAIIs, XDAIIi, XDAmini it only can be repaired from service centre by chip replacement.
So we are very sorry but we can not offer any solution for the device (it doesn't matter what version).
Regards,
IMEI-CHECK Team
This doesnt look to good?
Does anyone have any success with these guys and the Orbit?
Thanks again.
mcstorey said:
Thanks Chaps!!
Have read through this forum through and through but alas a little too late!!!
Thanks for your advice though, will keep reading........
220v sounds like a last resort??
Someone else suggested a few seconds in the microwave!!!!
Did contact imei-check pasted response below:-
Hello,
Do you mean XDA neo or exec? If so we do *NOT* support this device at all. In case it is a XDAIII, XDAIIs, XDAIIi, XDAmini it only can be repaired from service centre by chip replacement.
So we are very sorry but we can not offer any solution for the device (it doesn't matter what version).
Regards,
IMEI-CHECK Team
This doesnt look to good?
Does anyone have any success with these guys and the Orbit?
Thanks again.
Click to expand...
Click to collapse
I have read posts where they have sent their artemis to imei check - the reponse sounds confused - saying they do not support neo or exec but what about orbit?
I would contact again saying you have an o2 orbit = artemis they may have got confused if you just put down o2 orbit.
btw a wm6 rom for the orbit will be released soon - no dates yet - as its an official rom it will fix your orbit.
There are some posts here of people sending their artemis to imei check http://forum.xda-developers.com/showthread.php?t=294950
http://forum.xda-developers.com/showthread.php?t=315526
Originally Posted by "psanas"
"*this is a copy, it is not my work at all* just thought it would be helpful as it helped me restore my bootloader.
Your device is bricked, if and only if, your device won't start normally... even if you press soft-reset, hard-reset, or even bootloader mode buttons. Usually a brick is caused by improper ROM upgrade, and using tools that modify the ROM. Before panicking, do the following:
Brick Test:
Make sure your device has ample battery charge. If you're not sure plug it in with the wall charger for at least 10min
Remove your battery for at least 1 minute
Replace your battery while observing the LED lights
If the LED blinks once upon battery insertion, you might have hope yet
The only way to upgrade on a semi-brick device, is to upgrade through bootloader mode. No bootloader mode, No upgrade possible - period.
Entering Bootloader Mode on Semi-Brick Atom:
Remove battery for for at least 1 minute
Press CAMERA+RESET(stylus) simultaneously
Insert battery while still holding the buttons
Release the buttons at the same time (You should see bootloader screen)
Note: Failure to hold the buttons at the same time during battery insertion will cause it not to work
Manual to restore dead BootLoader (http://wiki.xda-developers.com/index...ame=BootLoader) Rover G5, Orsio n725, O2 Atom, O2 Atom Exec, HP6815 - Tested . (may be 68xx series)
© Copyright to Alex_Beda & 1stMASTER
PDA-HACK.NET Team http://wiki.xda-developers.com/theme...//pda-hack.net (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.
http://i218.photobucket.com/albums/c...roverorsio.jpg
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/c...eda/raz012.jpg
You can so using connector from floppy drive 5.25”. (autor vic180)
http://i218.photobucket.com/albums/c.../PICT0267-.jpg
http://i218.photobucket.com/albums/c.../PICT0262-.jpg
LPT connector for PC
http://i218.photobucket.com/albums/c..._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/c..._beda/raz1.jpg
http://i218.photobucket.com/albums/c..._beda/raz3.jpg
http://i218.photobucket.com/albums/c..._beda/vid2.jpg
.
for fixation connector need make this
Or other
http://i218.photobucket.com/albums/c.../kreplenie.jpg
http://i218.photobucket.com/albums/c...a/vidkrepl.jpg
http://i218.photobucket.com/albums/c...da/vidobsh.jpg
Software part.
http://wiki.xda-developers.com/theme...BootLoader.zip (http://wiki.xda-developers.com/uploa...BootLoader.zip)
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/c...eda/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/c...eda/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 (http://wiki.xda-developers.com/index...ame=BootLoader).
BootLoader (http://wiki.xda-developers.com/index...ame=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 (http://wiki.xda-developers.com/index...agename=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"
*this is a copy, it is not my work at all* just thought it would be helpful as it helped me restore my bootloader.
Your device is bricked, if and only if, your device won't start normally... even if you press soft-reset, hard-reset, or even bootloader mode buttons. Usually a brick is caused by improper ROM upgrade, and using tools that modify the ROM. Before panicking, do the following:
Brick Test:
Make sure your device has ample battery charge. If you're not sure plug it in with the wall charger for at least 10min
Remove your battery for at least 1 minute
Replace your battery while observing the LED lights
If the LED blinks once upon battery insertion, you might have hope yet
The only way to upgrade on a semi-brick device, is to upgrade through bootloader mode. No bootloader mode, No upgrade possible - period.
Entering Bootloader Mode on Semi-Brick Atom:
Remove battery for for at least 1 minute
Press CAMERA+RESET(stylus) simultaneously
Insert battery while still holding the buttons
Release the buttons at the same time (You should see bootloader screen)
Note: Failure to hold the buttons at the same time during battery insertion will cause it not to work
Manual to restore dead BootLoader (http://wiki.xda-developers.com/index.php?pagename=BootLoader) Rover G5, Orsio n725, O2 Atom, O2 Atom Exec, HP6815 - Tested . (may be 68xx series)
© Copyright to Alex_Beda & 1stMASTER
PDA-HACK.NET Team http://wiki.xda-developers.com/themes/default/images/http.pnghttp://pda-hack.net (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.
http://i218.photobucket.com/albums/cc23/alex_beda/JTAGroverorsio.jpg
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.
http://wiki.xda-developers.com/them...a-developers.com/uploads/RepairBootLoader.zip (http://wiki.xda-developers.com/uploads/RepairBootLoader.zip)
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 (http://wiki.xda-developers.com/index.php?pagename=BootLoader).
BootLoader (http://wiki.xda-developers.com/index.php?pagename=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 (http://wiki.xda-developers.com/index.php?pagename=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
I bricked my Xda Atom Pure which i bought second-hand yesterday by trying to hard reset it to clear the memory.
It got stuck at bootloader screen while folowing the above procedure and my pc would not recognise it. I choose option 1; Module debugging mode, pls where do i go from here? its too late to loose this phone. pls help!!!
plz help!!!
Plz help me i My o2 atom dead cannot enter in Bootloader too...plz help!!!
video
can u send a video how to do all thiss or tell step by step plz
i have the same problem can not enter to boatloder mode(tried everything)
i m frm india here we didnt have o2 atom exec. customer care.
plz need help???????/
this methode can be applied on htc magician???
this methode, can be applied on htc magician??? the bootloader is the same?
There is a procedure for Trinity device ?
There is a similar procedure for recover crash bootloader on trinity device ?
When i enter on Bootloader mode (Power+Camera+Reset-stylus) only led blue blink on my test trinity device.
Thanks in advance for your help.
need help
pls,,,my atom is dead, coz when i upgrade is fail,,,show pls the vidio,,,so i can try at my atom
me too
cant bootloader,i try any way but cant..............
Hi All, I am trying restore dead bootloader on my 02 Atom.
have followed all the hardware set up instructions but I can only get to the point of the blinking LED with no response from the software.
Maybe I have misunderstood the English in the instructions. Would really appreciate if some good soul could give me a better translation.
Look forward to a response, many thanks in advance.
psophan said:
cant bootloader,i try any way but cant..............
Click to expand...
Click to collapse
What no lettering on the screen like -->>> V1.0, USB, or SERIAL ..? if you still look like that , it means your device is saved !!!! I also never experienced anything like that and my O2 can live up to this moment ...!!
thank friend
Hakim Rahman said:
What no lettering on the screen like -->>> V1.0, USB, or SERIAL ..? if you still look like that , it means your device is saved !!!! I also never experienced anything like that and my O2 can live up to this moment ...!!
Click to expand...
Click to collapse
But im sucess already
you're welcome
psophan said:
But im sucess already
Click to expand...
Click to collapse
justify still be saved !
this tutor only for PC Desktop user ha?
Possible make JTAG VIA USB? can u tell me how to?
Hi everyone! This is my first post and I would like to thank You all for great job done on this forum, I'm rather beginner but already gathered a lot of knowledge by reading various posts
My first post will be about HTC Universal, that came to me few days ago. From first look it's an amazing piece of hardware and I would like to make it working, because (obviously) it is not
Uni's characteristics:
Black O2 XDA Exec
NAND Flash - DiskOnChip G4
Uni's behaviour:
after turning on is showing bootloader screen with some artifacts and following info:
R 1.17.00
G 42.53.P8
O D. 08.81 TML
can access bootloader menu (three yes/no settings, KITL) - same artifacts are here too
combination of backlight+power+reset gives black screen
hard reset doesn't change anything, screen with O and X is ok, with no artifacts
device is not recognized by PC so I cannot flash it (dev 0000, ven 0000 on windows / cannot enumerate on linux) - USB transmit lines are ok because situation changes after choosing KITL mode (every other is unrecognized)
Already done:
I thought it may be damaged USB port, but I succesfully managed to make it work after choosing KITL mode from bootloader menu (backlight? + reset). It doesn't accept any commands through mtty but at least installed in windows as HTC Sync Device (not remember correctly?) and showed some prompt in console (KITL$ ?).
I didn't really know what KITL is so i googled for other methods of unbricking and found amazing discussion between scholbert and roglio in topic about rescuing uni from scratch via JTAG. So I remodelled my adapter to the same as Wiggler2 and connected to mainboard. However, my situation, if I understand correctly, is not the same as scholberts or roglios was. I have working IPL and partially working SPL, that is, I think I have
Is there any method of writing SPL into ram and running it in this situation? Maybe then USB will be working and let me flash new firmware? I found solutions like this for some other HTCs but I don't really know how to load something into RAM, because it looks like it is unaccessible at the moment (errors in openocd, zeroes readed by urjtag). I'm working with newest openocd version, it recognizes PXA270 without problem, same as urjtag.
Or is it possible to restore Uni via KITL mode? Maybe I try to download software required in topic about Hermes and run it at some free time, but I have to connect my old windows box to internet
I'll be very thankful for every answer and I hope that this Uni will work once again
P.S.: I'm sorry if some of statements are not understoodable, I lack possibility of using english daily and practicing it, so my english is little poor
Best Regards, Karol
#------
Ah, yes, I forgot. Not black screen after combination of backlight+power+reset, but Serial + v2.01. Does not react to USB. If I connect USB first, then reset, it's "USB v2.01" - device not recognized. The same with SD card inserted -> reset -> "USB v2.01" -> took card -> unrecognized...
Welcome to forums,
Have a read on the thread just above this one, you´ll find almost all you need
Hi!
Thank You for your answer. I have already read this and other topics regarding "stuck at bootloader" and other problems, and tried all the provided solutions, with no luck
The main problem is usb not working properly. I'd rather not suspect hardware damage, because it works in KITL mode.
#---
I've done some more research. Downloaded and installed Platform Builder, and following instruction for hermes (changing only processor type) tried to run system through KITL, but with no success, image (awfully small - about 900kB) was downloaded to device, but there was no answer from it - KITL screen have not changed.
After few tries I focused on another method - based on tomal's SDFlash_G3. I took 416 byte header found later in topic about SDFlash (OllieD's) and connected it with decrypted official nk.nbf image from O2 and later with one from tomal's rom.
My device was reacting kind of strange while trying to recognize rom from card. For first, it haven't tried at all, not until I !removed! MMC card! (instead of this later I was hovering the sd card slot pin responsible for card detect).
Then, there was two scenarios:
first, when I took card too fast after entering bootloader, it showed message about too short rom
second, where I waited some more seconds, it showed error about sections=1 and not allowing to update
So I searched about this section=1 error and found that it is incompatibility between 416 byte header and rom image - header points that there should be more sections in rom, but there is only one.
Don't really know how to change it, is there any documentation about header structure?
In topic about SDFlash_G3 there was mentioned that this method is "without 2nd device", but I haven't found anything about "with 2nd device", is it worth giving a try?
Can someone provide me with mmc/sd card image (compressed of course) with backup from G4 Universal device done with d2s command?
I'll be very thankful for any help.
Best regards, Karol