Database Users

Success! Fixed gsm-error in bootloader and 1%-error XDA

Hello,
because my posting in this forum wasn'n answered i tried to fix together with Mr. Wolf from Wolfsoft (www.wolfsoft.de - also great for fast XDA RAM-Upgrades) with the informations i found.
Everytime i write the i did something - i mean - we did it! We worked hard together for this solution.
-----------------
First:
Maybe, surely you can destroy you XDA-ROM more than it was destroyed before. I not guarrante or take responibility for any errors or damages occuring while trying the next steps.
Situation:
I upgraded my german O2-XDA in the wrong way. After this I had the following problem:
- The O2-bubbles appearing after soft- or hard resetting the XDA are displayed for 3 or 4 minutes. In the right bottom corner of the display the Version of WinCE ist dissplayed (3.14), after some times someting more was shown but that seemes to be from a crashed source.
- After the "pling" a white screen with a blue bar on the top is displayed. The screen-light doensn't turn off. Nothing more happened, after 20 or 30 Minutes the XDA performs a soft reset automatically - after this the same problems occuring
Requrements I needed to fix my problem:
- 1 (better 2 SD-Cards with minimum 32MB Capacity)
- XDA Cradle connected to the PC and Power
- in some cases 1 Charging cable (USB or Power) with a connector for the XDA
- The Program A and Program B - Files provided by german O2 website
- The repair.zip-File provided by XDA-Developers
- A second XDA or a SD-Card-Reader connected with your PC
- many time
- Your XDA must have a working bootloader (mine was Version 5.15), try it by holding the Power-button while performing a soft-reset.
What I did:
- After entering the Wallaby-Bootloader an "gsm-error" - message appears after 1 minute of "wait"
- I entered the SD-Card-Menu by pressing the Contacts-Button on the left-top of the XDA
- I choosed Write CE to SD in order to save my original CE in order to avoid unuseful Questions in case of repair-fail by O2-Support
- After this I performed a soft reset an waited for 1 or 2 Minutes after the white screen appeared
- While tis time write the contents of the unzipped repair.zip to the SD-Card using the SD-Card-Reader or the second XDA
- Now i pressed the "Volume" - Button on the left side for many times, after some trys (if it is not working perform a soft reset and try new) I saw a non-working Today-Screen
- Now insert the SD-Card on you have written the files from repair.zip
- There are 2 possibel reactions:
First: You get a message to format your SD - DO NOT!!!! In this case remove your SD-Card, connect your XDA with the Charging Cable and perform a soft reset. It is okay that there is no charging light. After you entered the Today-Screen insert the SD - do not remove the Charging-Cable! Then it will work.
Second: Installing beginns without any problems
Now your Radio Stack-Module will beginn to be updated. In my case I got the 1% Error discussed in the forum.
- Remove the Power cable, connect your cradle with the PC and the Power, perform a soft reset and wait what is happening. After the error occurs don't push the ok-button. Simply press the start-tab (or anywhere other excluding the message). Now take the XDA out of the cradle and after this put it in again, still with the error message on the screen. Now an active sync connection will be shown on both, your XDA and the PC! If you have this case, it looks good.
- If this doesn't work, replace the RSUpgrade.sa.cab-File from the repair.zip with the same named File, whats included in the program_B.exe (extract first, you will find the result in <Harddisk-Device:\Programme\Programm B) and writhe both on your SD
- Soft reset the XDA, ignore all errors, do not put the new written SD-Card in - open the Active sync-connection and delete the both newest files in the Windows-Directory of your XDA. If you can't delete, rename the file. After this perform a new soft reset.
- You will get a "file not found error". Try to temove and insert your XDA in the cradle to get an active sync-cennection. If this doesn't work insert the new written SD
- Try new flashing again again, maybe it works. If not try to push on the screen and remove and reinsert your XDA in the cradle to get a Connection.
- If there is no possibility to get a connection - i do not know any futher solutions - sorry.
If you get the connection, perform the normal Flashing with Program A provided by your Provider. After this is successfully completed you will see the loading-LED again! Congratulations!
If this is completed charge your Battery to at least 70% - be patient, it will take up to 1 Hour!
After this perform Programm B provided by your Provider. If this successfully completes - Congratulations - you are up and running!
I don't know, if I had happy circumstances, but this worked to gat my working XDA back!
If it do not work, use the first SD-Card containing your old CE to copy back your old ROM in order to not loose your support by your Provider. Simply insert the card into your XDA and perform a soft-reset while holding the Power-Button. Everything looks broken but original!
Please feedback in the XDA-Forum-Thread, if it worked at your XDA or if you have any hints for improvements this steps. Thank you!
Best regards from Berlin/Germany to all XDA-Fans like I am!
Miwu

Very detail.....thanks a lot ! :lol:

Tried your solution but i don't know which files i should delete cause when i delete the latest two files i get no error message...
When trying to install Programm a anywway i get a Connect Power Message and the installation stops.
Edit:
I managed to get the file not found error by renaming the RsUpgrade executable but still get the Power Adapter not plugged in Error...
So it would be very important to know which Programm A you used.

Hello,
@ianrush
Have you been able to get an active sync connection as I described?
You have to delete the file causing the Radio-Stack-Update after restart, I think they are located in the Windows directory of your XDA. If you let your XDA order the files by date the 2 newest files are the ones for updating the Radio Stack and causing the 1%-error. In deleting these files you can get your XDA booting without starting the gsm and getting the Active-Sync-connection. To break up the Installation you must delete these files (i remenber that on (the one that must be renamed) was only 35k or in this area, the other one was much larger).
After deleting and restarting by soft reset you don´t get the 1%-error-message, but another one like "The file can´t be found). But if you see this message (do not press okay!!!!!) you can use your Active-Sync-Connection to flash with Programm A and after this programm B.
The files (germen version) are located here.
Klick at the link "Download Software-Update" and accept the conditions by clicking "Akzeptieren". After this a new window is displayed for downloading the Software. The versions are:
CE: Version 3.19.01 -
Radio Stack Version 4.21
"Teil 1" means Programm A
"Teil 2" means Programm B.
Remember, it is the german version with some german specials like the "Homezone". But you can turn it off and while I see, that you are from Austria, I think you won´t have any problem with the language...
Isn´t it very strange, that 2 german speaking people trying find solutions in english??? :?
Best regards from Berlin!
Michael

I have no problem starting an Active Sync Connection, my problem is, that i get this odd Error Message which tells me to plug in the Power Adapter, which is obviously connected...
There is a much easier way of getting rid of the Flash Prog bei simply deleting the RsUpgrade link in the Auto Start Folder in the wwindows directory and its also possible to start an Connection via AS.
My real problem is the battery charge check before the real flashing of the RSU.
I tried it with the mentioned O2 files and also with Tmobile.at/de files.
A solution may be to "crack" the installation file or to write a small prog wich tells PPC that the battery is chraged.
Many thanks for your help, but it didnt solve the problem for me.
PS: Well its an English Forum so i think we should stay in that language

Oh, I forgot to write that one.
The charging light, wich may be an indicator for the XDA-OS for the supplied Power came back as we installed the O2 Radio Stack via the Active Sync-Connection bevor performing Programm A - Upgrade. Try to perform Program B - Update first, in our case we got our lovely orange light back and then performed the Programm A and Programm B - Update again!
Regards again!
Michael

Didn't work for me either.
The BIG question is how the hell did you get your XDA charging his battery again ? I believe that this will help many people to get their 1% Flash failed problem solved.

Hi !
I will try this method tomorrow.
Sebi

Hello,
I do not know why, but after (failed) installing Programm B after connecting via Active Sync first it worked . Maybe because of the working version-combination of Radio Stack and CE.
Regards
Miwu
@Sebi Please post if it is working!

Hi !
Don't work for me.
My problem is same this:
Posted: Fri Aug 29, 2003 19:26 Post subject:
--------------------------------------------------------------------------------
I have no problem starting an Active Sync Connection, my problem is, that i get this odd Error Message which tells me to plug in the Power Adapter, which is obviously connected...
Click to expand...
Click to collapse
Best regards
Sebi

miwu
I followed your steps and got the following message on my device:
The file "\Windows\RSUpgrade.exe" is in use or is in ROM. If the file is not in ROM, please close the application using the file.
Please advise

Anaq8i,
if this messege appears then rename the file "\Windows\RSUpgrade.exe" with an new name like "\Windows\RSUpgrade_used.exe" restart the device and follow the further instructions.
Hope that helps
Regards
Michael

miwu,
I cannot rename it, nor can I delete it, I think because it is in ROM. Please keep in mide that the I have not closed the error message after the 1% halt.

I reached the point were I can access my device and can sync with my PC. If I try the Programme A install, I get the message " WARNING 001: POWER ADAPTER NOT PLUGGED IN, Please plug the power adapter into your Pocket PC". Every time I try the RSU upgrade I get the 1 % error. Any suggestions will be appreciated

Hi anaq8i,
please try to rename the file by using the Active-Sync-Connection an the Explorer of your big Desktop-PC. The file cannot be in the rom, it is located in the ram of your device in order to get deleted after upgrading. Try to rename the file this way, then perform a soft-reset (not a hard one) then you will get an error-message that sonds like "the file ... cannot be fount", then put your device in the crade for active sync and try to install the original Programm B of your Provider (not the file from repair.zip). That worked at my XDA.
Please answer how it worked.
Regards this time from Hamburg/Germany
Michael

thanx a lot, have the same error, now all worx fine!

czeky thanks for answer. I am glad that my description was helpful Doe it work for other users?

@ czeky
would you also please be so kind and tell us if u tried any other steps than mentioned by miwu ?
If i treally worked with your XDA there you must have done something different then anaq8i, Sebi and i did...

miwu
I reached the point that I can boot my XDA and can sync with my PC. But I still cannot install /upgrade the RSU software, I still get the 1% error. If I try to install Porgramme A, I get the "POWER ADAPTER NOT PLUGGED IN" error message. I never reached the orange light stage on the XDA.
Anything else I should do?

@anaq81
Did you try to rename the described file via Active Sync? I posted it some day ago ...

Magician: turn on only in bootloader, can't be flashed

Please, help me in the following situation
I bought Qtek s100 It turns on only in bootloader mode. What was before I don't know.
Now I try to reflash it via PC. I unpacked rom 1.12 from imate and put there file MaUpgradeUt_noID.exe and then ran it. The utility can't see the device information (it is normal) but it can't see the informatin about the rom I'd like to flash. I click @[email protected] but it says it gather information about the device and nothing happened.
I tried to run again about 20 times, but nothing helped.
I tried to flash it via card using rom-image but there is no invitation to reflash though I flashed via card more than 20 times other htc devices and then everything was ok.
I ran mtty 1.42 and gave command d2s, but it said unknown command. Then I gave d2s command then the device turned off.
I have qtek s110 with broken display. Is it possible to change rom-memory?
Is it possible to get service_manual for magician?
Thanks

First of all, did you back up your current ROM to SD before Flashing new ROM.
1. Yes. It's VERY GOOD. Disconnect your device from PC. You need to insert SD with your ROM to the device and Turn On. Press Power or Cancel button (i didn't realy remeber try all). After that device will flash ROM form SD.
2. No. It's VERY BAD. You need to know start address form what device should start after Reset. Sory here i did not know what it is.

Ñïàñèáî çà ïîìîùü!
Ñóòü â òîì, ÷òî àïïàðàò ñ êîìïà øèòüñÿ íàïðî÷ü îòêàçûâàëñÿ. Ïîïðîáîâàë øèòü îáðàçîì ÷åðåç êàðòó (îáðàç ñíÿò ñ t-mobile 1.01). Íà îáðàç íèêàêîé ðåàêöèè.
Äàëåå ïðîáîâàë ñíÿòü îáðàç ñ ïðîáëåìíîãî àïïàðàòà. Àïïàðàò âûêëþ÷àåòñÿ. Åñëè ñ mtty äàòü êîìàíäó øèòüñÿ s2d, òî mtty ãîâîðèò, ÷òî êîìàíäà íåïðàâèëüíàÿ

Hi,
Read this http://forum.xda-developers.com/viewtopic.php?t=46628 about the SD flash
M

thanks, but te problem is the device doesn't want to work with card. No reaction on the card with rom-image, turning off when typing d2s

Don't know where you bought & how much you paid for it (sure hope it's less then a new screen), but sir I guess you're scr*w*d.
Maybe you can replace your broken S110 screen with the one from the S100. There's a rar file on the board, with a detailed description & pictures on howto disassemble your magician, think it's called disassembly.rar.
EDIT You can find it here http://forum.xda-developers.com/viewtopic.php?t=44841
M

thanks, but I think the screen is alive, it shows usb or serial and etc.
As far as i know, there is some diagnostic tests to understand where is the problem. how to activate it?

Diagnostics
Sorry I don't know of a diagnostics test. But you can have a bootloader without a working rom. Since you bought the S100 in a bootloader state, that's very suspicious to me. & that's why I advised you to replace the broken screen on your S110 with the one from your S100.
Hope you can sort it out & if you happen to run across a diag. pls update the wiki with it.
Regards, M

HTC Hermes JTAG pins

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

RESTORE BOOTLOADER ON Rover G5, Orsio n725, O2 Atom, O2 Atom Exec, HP6815 - Tested

*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?

[Q] Partially bricked Universal

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