XDA Flame User Forum at xdaflameusers.com

the first real XDA Flame user meeting point

You are not logged in.

#1 2008-04-14 01:26:03

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Manual for recovery bricked FLAME

Hi all!

Manual for recovery bricked FLAME

Symptoms: the device didn't switch on after experiments with an upgrade. Reacted only to power unit connection at the inserted battery - the orange led lights up. At this situation to bring the device back to life, only a flash bootloader (eboot.nb0) by means of interface JTAG is needed and possible.

1. Hardware preparation.

Please disassemble the FLAME and extract board. The detailed instruction

You should make a simple JTAG - cable.
http://www.xdaflameusers.com/uploads/688_flame_recovery.jpg

Max lenght this cable is 20-25sm. My variant:
http://www.xdaflameusers.com/uploads/thumbs/688_tools.jpg

Alsoit is  posible to produce some contacts, for example (see foto)



2. Software preparation.

To be required in addition:
1. Micro-SD card and cardreader.
2. Program SDFormatter, download here or here
3. FlameRecoveryTools by Medush smile, download
4. Diskimage.nb0 - any for FLAME. I extract it from official update


Well, now at all of us it is ready. We begin...

1. Extract FlameRecoveryTools on c:\
2. Run c:\FlameRecoveryTools\giveio_setup.exe (It driver for JTAG-cable). Please make sure that driver is installed and started.
3. Attach JTAG-cable to LPT-port your PC and FLAME board.
4. Plug power cable to FLAME board (or USB-cable from PC).

Warning! Do not press the button-indicator of the inserted accumulator!!!!

5. Open cmd-window. (Start-Run-cmd)
6. Go to c:\FlameRecoveryTools\JFlash_MM\
7. Run Start.bat

If everything is OK,  a flash process will start and you should see:
http://www.xdaflameusers.com/uploads/thumbs/688_flameupdate.png

If you see:
http://www.xdaflameusers.com/uploads/thumbs/688_flamejtagfail.png
Please carefully check up correctness and reliability of all connections, a cause of error may be ONLY in it. Don't try to find missing file or any other program mistakes.


Ok, flash process is finished, verification successful, eboot.nbo has been flashed. smile

Unplug all, assemble your FLAME, plug AC-cable and turn on power.

Device is starting with error:
http://www.xdaflameusers.com/uploads/thumbs/688_err_003a.jpg

If you see message "battery is too low" - please wait for  some time...and press reset again ))))

Ok.

8. Put micro-SD card in to your cardreader and run SDFormatter. Select "Full format".
9. Copy the following files to card: diskimage.nb0, eboot.nb0 (for example from my FlameRecoveryTools) end empty password-files rerr003a.kez and 1xdtgklo.kez.
10. Put card into device and start upgrade (press and hold soft-buttons (- and -) and press reset.

11. Finish!

Insert the accumulator into place and turn on FLAME.
Enjoy the working device!  cool

If my article has helped you, you can donate me:
WebMoney WMID 205584530674
WebMoney USD - Z177840443105
WebMoney Euro - E685734257524
PayPal: use recipient name "medush@gmail.com" or CLICK HERE

I'm sorry for my bad English...

Last edited by medush (2009-02-27 10:10:43)


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#2 2008-04-14 04:14:57

terrykb
XFU Team
From: Malaysia
Registered: 2008-01-03
Posts: 678

Offline

Re: Manual for recovery bricked FLAME

Thanks for your great tutorial. I hope I shall never need it but its a great comfort to know that it is there.  Thanks again for sharing smile


Testing ROM_004T_WWE T7 smile
Also: Holux M1000 BT GPS used with Garmin Que
Eten M600 WM5
 

#3 2008-04-24 09:42:08

Steele
Member
Registered: 2007-12-16
Posts: 22

Offline

Re: Manual for recovery bricked FLAME

Tried recovering my flame using the above procedure, I got the following message after running start.bat

JFLASH Version 5.01.007
COPYRIGHT <C> 2000 - 2003 Intel Corporation

PLATFORM SELECTION:
Prcoessor=                   PXA27x
Development System=  Mainstone
Data Version=              1.00.001

error, failed to read device ID
check cables and power
ACT: 1111 1111111111111111 11111111111 1
EXP:  **** 1001001001100101 00000001001 1

failed to read device ID for this Platform


I checked and re-checked the following:
           1. connections and the cable that matches the daigram and the picture
           2. Power and made sure that there is power
           3. also re-initiated the giveio driver just to be sure.

I used 1.5v 100 ohm resistors and used HDD IDE wires for wiring

Not sure what's the cause of the problem. My guess is that the giveio driver is not recognized. I'll try later using safe mode to see if I have a IO conflict in the LPT port.

Anybody got any ideas?

Thanks in advance

Update: giveio does not work in safemode. after playing around the software giveio is loading as com3, which is the likely reason why the hardware is not detected on the LPT port. so far I can't find an instruction how to load it in LPT1. I'll try again later with another PC.

Last edited by Steele (2008-04-24 11:52:37)

 

#4 2008-04-24 22:09:36

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

Try with other computer.

The basic errors:
1. Wrong resistance of resistors.
2. Wrong distributing of a wire.
3. Too long cable (more 20-25см)
4. A bad contact - faulty soldered joint a wire
5. The pressed button-indicator of the accu batery
6. Power is off


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#5 2008-04-25 09:49:29

Steele
Member
Registered: 2007-12-16
Posts: 22

Offline

Re: Manual for recovery bricked FLAME

Thanks Medush.

So far it is the same when trying on a different PC.

I'm doing a new wiring again just to be sure.

I rechecked my previous setup with the list you have made:
1. The resistor is correct 100 ohm with color bar Brown-Black-Brown-Gold (LPT is connected near the Brown stripe and wire to motherboard is connected near gold stripe)
2. Wiring distribution is okay. Checked also wiring with voltmeter to see if there are damages or disconnections in the setup. So far it is okay from LPT pin to end wire.
3. Cable used is 18cm
4. Solder is okay on the LPT plug. except for the flame motherboard. solder cannot attach on the board contacts. Have to use tape to hold the connections in place.
5. Accu button not pressed.
6. Power cable is connected.

I'll make some tests after re-wiring. and let you know any developments.

Thanks.

Last edited by Steele (2008-04-25 09:51:19)

 

#6 2008-04-29 18:30:50

Steele
Member
Registered: 2007-12-16
Posts: 22

Offline

Re: Manual for recovery bricked FLAME

Got the Flame working again.

Earlier used 6 wires on the ground and series them together. This time I series the ground at the LPT pins and used only 1 wire to the motherboard. So far the JTAG worked.

Also found that the contact point TMS on my board is loose the metal fell off the motherboard.

Thanks Medush for the instructions and the support.

 

#7 2008-04-30 00:37:48

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

Congratulations! smile I update my Paypal account wink

Last edited by medush (2008-04-30 01:02:17)


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#8 2008-05-10 18:19:01

wksoo
New member
From: malaysia
Registered: 2008-04-26
Posts: 13

Offline

Re: Manual for recovery bricked FLAME

medush wrote:

Hi all!

Manual for recovery bricked FLAME

Symptoms: the device didn't switch on after experiments with an upgrade. Reacted only to power unit connection at the inserted battery - the orange led lights up. At this situation to bring the device back to life, only a flash bootloader (eboot.nb0) by means of interface JTAG is needed and possible.

1. Hardware preparation.

Please disassemble the FLAME and extract board. The detailed instruction

You should make a simple JTAG - cable.
http://4pda.ru/forum/uploads/img-81215- … covery.jpg

Max lenght this cable is 20-25sm. My variant:
http://4pda.ru/forum/uploads/img-81218-Tools.jpg

Alsoit is  posible to produce some contacts, for example (see foto)



2. Software preparation.

To be required in addition:
1. Micro-SD card and cardreader.
2. Program SDFormatter, download here or here
3. FlameRecoveryTools from Medush smile, download
4. Diskimage.nb0 - any for FLAME. I extract it from official update


Well, now at all of us it is ready. We begin...

1. Extract FlameRecoveryTools on c:\
2. Run c:\FlameRecoveryTools\giveio_setup.exe (It driver for JTAG-cable). Please make sure that driver is installed and started.
3. Attach JTAG-cable to LPT-port your PC and FLAME board.
4. Plug power cable to FLAME board (or USB-cable from PC).

Warning! Do not press the button-indicator of the inserted accumulator!!!!

5. Open cmd-window. (Start-Run-cmd)
6. Go to c:\FlameRecoveryTools\JFlash_MM\
7. Run Start.bat

If everything is OK,  a flash process will start and you should see:
http://4pda.ru/forum/uploads/img-81220-FlameUpdate.png

If you see:
http://4pda.ru/forum/uploads/img-81221- … AGFail.png
Please carefully check up correctness and reliability of all connections, a cause of error may be ONLY in it. Don't try to find missing file or any other program mistakes.


Ok, flash process is finished, verification successful, eboot.nbo has been flashed. smile

Unplug all, assemble your FLAME, plug AC-cable and turn on power.

Device is starting with error:
http://4pda.ru/forum/uploads/img-81222-ERR-003A.jpg

If you see message "battery is too low" - please wait for  some time...and press reset again ))))

Ok.

8. Put micro-SD card in to your cardreader and run SDFormatter. Select "Full format".
9. Copy the following files to card: diskimage.nb0, eboot.nb0 (for example from my FlameRecoveryTools) end empty files-passwords rerr003a.kez and 1xdtgklo.kez.
10. Put card into device and start upgrade (press and hold soft-buttons (- and -) and press reset.

11. Finish!

Insert the accumulator into place and turn on FLAME.
Enjoy the working device!  cool

If my article has helped you, you can donate me:
WebMoney WMID 205584530674
WebMoney USD - Z177840443105
WebMoney Euro - E685734257524
PayPal: use recipient name "medush@gmail.com"

I'm sorry for my bad English...

hi there,

       i do a j tag and all sucessful,and only the last step :i copy  the disimage.nbo and eboot.nbo and create 2 file forrerr003a.kez and1xdtgklo.kez
after the eboot 100% finish it turn off and on.but the screen still show err-003a, and hang over there.......

 

#9 2008-05-10 20:14:55

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

wksoo

You use invalid filename. True name is diskimage.nb0
Please correct and re-flashing this file.


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#10 2008-05-13 18:29:20

tora_tiger
New member
Registered: 2008-01-15
Posts: 3

Offline

Re: Manual for recovery bricked FLAME

Hi.my flame is not power on.Can I recovery it?

 

#11 2008-05-13 18:57:14

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

tora_tiger wrote:

Hi.my flame is not power on.Can I recovery it?

Why your device does not join?
It after flashing?
Or other reason?
The battery is charged?

If the device has died after a flashing - use my method for recovery.

Last edited by medush (2008-05-13 18:57:50)


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#12 2008-05-14 18:28:07

tora_tiger
New member
Registered: 2008-01-15
Posts: 3

Offline

Re: Manual for recovery bricked FLAME

Thanks your message.
I was flashing other eboot.
Now power LED is OK.
But can't power on.
I well be do it.
Thanks

 

#13 2008-06-10 07:55:11

afeng11
Member
Registered: 2007-12-17
Posts: 53

Offline

Re: Manual for recovery bricked FLAME

I have bricked my O2 Atom Life,it absolutely dead now ,how can i recover it?can you send me e-mail to afeng114@163.com,thank you!

Last edited by afeng11 (2008-06-10 07:57:02)

 

#14 2008-06-10 11:50:17

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

afeng11 wrote:

I have bricked my O2 Atom Life,it absolutely dead now ,how can i recover it?can you send me e-mail to afeng114@163.com,thank you!

You can try this metod: http://forum.xda-developers.com/showthread.php?t=336278

I want to advise you create new topic in http://pda2u.ru/forum/index.php?s=& … p;cal_id=0 (like English smile )
This forum - a place of a meeting of the professionals having wide experience on reanimation of devices


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#15 2008-06-10 15:40:15

afeng11
Member
Registered: 2007-12-17
Posts: 53

Offline

Re: Manual for recovery bricked FLAME

medush wrote:

afeng11 wrote:

I have bricked my O2 Atom Life,it absolutely dead now ,how can i recover it?can you send me e-mail to afeng114@163.com,thank you!

You can try this metod: http://forum.xda-developers.com/showthread.php?t=336278

I want to advise you create new topic in http://pda2u.ru/forum/index.php?s=& … p;cal_id=0 (like English smile )
This forum - a place of a meeting of the professionals having wide experience on reanimation of devices

thank you,first,i didn't know jtag point in atom life,and atom life is m-system's DOC,so flashmm software can't fit to Atom life!any advise?i can read any russia,sorry!

Last edited by afeng11 (2008-06-10 16:09:54)

 

#16 2008-06-10 15:52:33

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

afeng11 wrote:

thank you,atom life is m-system's DOC,so flashmm software can't fit to Atom life!any advise?i can read any russia,sorry!

Flame is DOC too and jFlashMM connected to this device successfully.
Create a new topic in English, we will respond also to you in English.
If you have errors at connection JTAG - write about them in detail, lay out a screenshots...


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#17 2008-06-10 16:13:08

afeng11
Member
Registered: 2007-12-17
Posts: 53

Offline

Re: Manual for recovery bricked FLAME

medush wrote:

afeng11 wrote:

thank you,atom life is m-system's DOC,so flashmm software can't fit to Atom life!any advise?i can read any russia,sorry!

Flame is DOC too and jFlashMM connected to this device successfully.
Create a new topic in English, we will respond also to you in English.
If you have errors at connection JTAG - write about them in detail, lay out a screenshots...

sorry,i didn't know the jtag point in atom life,can you tell me?thanks!
http://xdaflameusers.com/uploads/thumbs/698_image_001.jpg

i want create a new topic,but i must register first,but i can read any russia,sorry!


this was my message when i use jflashmm:
D:\Flame\ATOM EXEC JTAG\RepairBootLoader(EXEC)\JFlash_MM>jflashmm pxa27x32 ebo_
.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: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 4 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat

This program supports flash devices defined by DAT files
contained in the same directory as the executable program.

If the file cannot be opened, there are four possibilities:

1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
     constructed filename. The first numeric value in the
     filename is the device ID. Verify this value with the
     component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
     devices. Make sure that you are using the correct
     platform data file.

Last edited by afeng11 (2008-06-11 08:58:44)

 

#18 2008-06-10 16:22:11

thierryb
XFU Team
From: France (Le Vesinet)
Registered: 2007-08-14
Posts: 1032

Offline

Re: Manual for recovery bricked FLAME

Hi afeng, please open a new topic even on XFU if you want, but this thread is dedicated to the Flame. Thanks

 

#19 2008-06-10 18:31:52

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

I create new topic here: http://pda2u.ru/forum/index.php?showtopic=338&st=0

afeng
All discussions only there, on English.

thierryb
Sorry for offtopic.

Last edited by medush (2008-06-10 18:46:59)


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#20 2008-07-05 11:59:55

thananan27
New member
Registered: 2008-07-05
Posts: 1

Offline

Re: Manual for recovery bricked FLAME

please help me xda stealth it dead con boot

 

#21 2008-07-06 06:20:57

cctay
Member
Registered: 2008-07-06
Posts: 16

Offline

Re: Manual for recovery bricked FLAME

My 02 Flame became bricked after 2nd time of loading to WM6.1 (1st time ok but after few day found something decided to reload os) -screen shows "completed" and freeze (unlike 1st time reset system itself), so I power off and on but no response anymore....no light nor screen...have try thousand of methode but still completely no response at all....sick !
anyone know the pin config beside the SIM card holder for 02 Flame ? does it related to JTAG ? -so that we don't need to dismantle to access to JTAG signals !
also the JTAG use 25pin D-Shell, how to convert to 9pin D-Shell ? -only old computer still using 25pin D-Shell !
Thanks for any feedback !

 

#22 2008-07-06 10:50:40

dwalin
Member
From: 1/6th part of sushi
Registered: 2008-02-14
Posts: 35

Offline

Re: Manual for recovery bricked FLAME

cctay, i have recovered my bricked flame manually according to medush's instructions just three days ago. this method works, just do everything like it described here.
as for the cable, afaik that's not com port jtag use but lpt port. i don't know any computer to use 9-pin connector for lpt. fortunately for me, my laptop does have it so it wasn't a problem. dunno if some usb-lpt adapter would work.

 

#23 2008-07-06 11:25:52

cctay
Member
Registered: 2008-07-06
Posts: 16

Offline

Re: Manual for recovery bricked FLAME

Thanks dwalin, I mistaken that is a serial port, but just wonder anyway to access to JTAG without completely dismantle motherboard !

 

#24 2008-07-07 18:31:10

medush
Member
From: Moscow
Registered: 2007-11-05
Posts: 48
Website

Offline

Re: Manual for recovery bricked FLAME

thananan27 wrote:

please help me xda stealth it dead con boot

Please go to www.pda-hack.net and create new topic. Here is only XDA FLAME.


O2 XDA FLAME. It is recovered from absolutely dead state.
My job will save to you 200-300 USD. Estimate my job and support  - donate with PayPal
 

#25 2008-07-19 19:24:58

alen909
New member
Registered: 2008-05-20
Posts: 7

Offline

Re: Manual for recovery bricked FLAME

About a week ago i was flashing my Flame with the WM6.1 ROM and during the OS Upgrade process it freezes at 10% of ''erasing flash''. I opened the eboot.nb0 file with an editor and inside there are some words like ''erasing flash failed'' etc etc, i don't get these it just freezes at 10%. Does this happen to anyone before??? and is there a way to enter some king of menu with the rerr003a.kez file or some other and reach the ''Format flash'' option what i found in eboot.nb0 under ''Arima engineer menu''. The only key combination i discovered with the rerr003a.kez file is the winkey and reset, it's showing some kind OS Reconstruct with the image not found error and continues to the err-003a screen.
With the wdzkfnma.kez and i key combination, in the menu i found the select boot device option, when selecting USBFn as first  boot device, the device get recognized by the computer as a USB piece of hardware but i don't have any driver for this, does anyone know where to find some kind of driver and what it is for?. I hope it's something like mtty.exe for the HTC devices.
Is there a way to format the flash of the flame (better without erasing the eboot.nb0 area)??
Thank you for any answer to this...

Last edited by alen909 (2008-07-30 15:03:48)

 

Board footer

powered by PunBB
hosted by SYNAPTICATe