the first real XDA Flame user meeting point
You are not logged in.
Offline
Support Flame hackers:
WARNING : Take the time to understand all of these directions. Do nothing before you read till the end. Be patient, do not hurry, you could destroy your phone. Then follow these steps to flash another version of the operating system into your XDA Flame.
1. You need a MicroSD card with a capacity not larger than 2GB. The cards are often not well formatted. If you experience problems, use the Panasonic SDFormatter V2.0 software to format the card. Download it from the Panasonic Support SDFormatter webpage. It may be necessary to do the full formatting of the card. See SDFormatter's options. Obviously, you will loose all the data on the card, if you have to format it.
2. Place these two files on your MicroSD card:
diskimage.nb0 - this file has to contain the OS image you wish to flash into your XDA Flame,
1xdtgklo.kez - any file named "1xdtgklo.kez". It serves as a password. It may be an empty file.
If you experience problems, place only these two files on the card immediately after having it formatted with the Panasonic SDFormatter V2.0 .
3. Backup all valuable data from your device, they will be erased.
4. Ensure that your device is almost fully charged. To be more secure, connect it to the charger.
(It may not work on battery mode with low power, successfully tried with battery at above 50%, but it works 100% with charger/power on)
5. Put the phone into the "flight mode" (GSM off) before flashing. This is to avoid possible side effects.
6. Reset your device pressing the reset button with stylus while holding down both soft buttons (the two buttons signed by a horizontal line beneath the screen). Keep holding the soft buttons after you release the reset button.
A screen entitled OS Updating (SD) should appear :![]()
On the screen you can read :
UPDATE DISKIMAGE.nb0 via SD CARD
Copy file from micro-SD to RAM:01%
Be patient, do not stop the process. The second screen will appear soon :![]()
You can read here : Erasing Flash:01%
No fear, wait for the third screen :![]()
It reads : Writing to Flash:01%
After the successful reflash of the operating system there will appear very shortly the last screen with the following title:
EBOOT Updating (SD)![]()
It is written here : Image file not found
That is no problem - you did not intend to reflash the bootloader, but only the operating system.
The device will now restart by itself.
The flash sequence takes less than 10 minutes: 1 min to copy the diskimage.nb0 from SD to memory, then 4.5 min to erase the flash memory, then 4 min to copy from memory to flash.
EBOOT.NB0 WARNING : Flashing the bootloader is much more dangerous. You can easily destroy ("brick") your device. So please do not put the file "EBOOT.NB0" on your MicroSD card when there is the "1xdtgklo.kez" password file.
IMPORTANT WARNING : Do not use other files or key presses not mentioned here. Some combinations would destroy your device.
FINAL WARNING : These instructions and information are provided AS IS, no attempt is made to verify correctness or suitability for any purpose. You may use this AT YOUR OWN RISK. The author of this page takes absolutely NO RESPONSABILITY for any harm that may come to you, your property, your data, or anything else arising from the use of this information. If you void your warranty, damage your XDA Flame, that's your own fault. This guide is only for users very experienced with Windows Mobile devices.
END OF INSTRUCTIONS
Cheers :-)
Look here for some more information.
Last edited by devictoria (2008-03-19 13:34:08)
Offline
I am very glad of your announce.
A great step for the Flame community.
Congratulations.
Offline
congratulations .... !!
Offline
great tutorial with pix
Offline
very great work! congratulations!!!
Offline
Then, where can we find an image to flash our flame?
and is the image similar to an upgrade of the window mobile version, for example wm6?
Offline
No, it is more complex. Just changing one file of the ROM could be a problem.
But thanks to devictoria we can take some risk to do something, because we expect to be able to get back and reflash with the original rom.
Concerning the original rom, you have two way to have it : you can have it in your extended rom as a file diskimage.nb0, or you can grab it using the grab_it tool, and cut it based on what we have already written in another thread.
But except if you understand what I say, or if you have a good backround in IT, OS, firmware, let other people do the job for you. We will do it.
Concerning WM6, we need much more. The Flame is the first one device of Arima, with new components like the Goforce, and a lot hardware not often available or that could be specific for this device: tvout, usb host, camera, wifi, bluetooth, sd, and so on. And we have to make that all these piece of silicon will continue to work in the WM6 version. We could have some chance if Arima deliver to Imate the 6160 and the 8150 that would be with WM6, because we can expect that most of the components would be the same, so we could use the ROM of these devices to create a WM6 rom for the Flame.
Another help could come from MWG, if they start to sale a Flame2 with WM6.
Offline
Congratulations!!!
You are my IDOL!!!
Offline
Does DISKIMAGE.NB0 includes also the Extended ROM image or separated?
@Thierry
Asked the above question because just lazy to try extraction. Maybe I should try to extract your DISKIMAGE.NB0 and take a look.
I do not have DISKIMAGE.NB0 in my extended rom like yours.
Although you have sent me your DISKIMAGE.NB0, I would still like to have my own DISKIMAGE.NB0. Till today I have still not got it right by using Grab_It.exe, it just hang forever in the middle of grabbing. Left a message on XDA-Dev regarding this Grab_It.exe, but nobody answers.
Can you provide the step by step instruction of how to use it?
Offline
diskimage.nb0 does not include the extended rom.
I will give you the complete instruction this afternoon (France). But use grab-it 64, read the other thread to know the starting and ending adress, and the file.
If you prefer to wait no problem, and I will compare my adresses with the one published by Medush on 4pda.ru
See you soon here:
http://www.xdaflameusers.com/viewtopic.php?id=33
Offline
The method provided by Arima and discovered by devictoria is secure. I have flashed a wrong diskimage.nb0 and obviously my Flame was bricked during 10 min. Just the time to put the good diskimage.nb0 in the sdcard, and restart flashing.
So there is no risk to try a new diskimage.nb0 if you have a card with the good files.
So that means also that the boot do not control the validity of the diskimage.
I have even with a binary editor modify a little bit the diskimage.nb0, then flash again my flame with it.
And guess what, I am writing this post with my new rom. That means also that we have an highway opened now.
We can take all the risks, we can try what we want.
Thanks again devictoria.
The flash sequence takes 10 min: 1 min to copy the diskimage.nb0 from SD to memory, then 4.5 min to erase the flash memory, then 4 min to copy from memory to flash.
I want to remind you:
- to do a backup before flashing
- to never have on the card or memory the eboot.nb0
Offline
People at 4pda.ru think that I am devictoria. I can assure this in not the case.
They think that because they do not succeed to reproduce flashing the Rom. Probably they do not succeed because their card is not recognized after a soft reset. It was the case for me until I buy a Kingston one.
Offline
I am using 2GB cards from A-DATA. I have succeeded more times to flash the diskimage.nb0 (also that one uploaded by Nexus_Flame on 4pda.ru forum). Unfortunately I do not know what is the reason of their problem (or his, because only one of them seems to have tried).
Offline
Well, i Have kingston 2Gb and Kingston 512MB, when I try to flash with 512 Flame only goes to soft reset, I can't enter bootloader with 512Mb card. When I try with 2Gb I can only enter to bootloader, but can't reflash device.
PS: in my ExtROM missing files diskimage.nb0 & eboot.nb0 I try with diskimage.nb0 from Nexus_Flame
Last edited by murzzz (2007-12-11 10:33:05)
Offline
So that means probably that could depend the way the card is formated. How we can get this information precisely ?
So I ask you question but sure you will say yes : have you created the 1xdtgklo.kez file and put it in your card ?
Offline
Yes, I put 1xdtgklo.kez to SD. When I format card with PC, I can't enter bootloader. When card is farmated in Resco FE I can start bootloader, but can't flash.
Offline
Please send me.uni-tech246@vnn.vn
diskimage.nb0
1xdtgklo.kez
Offline
diskimage.nb0 is 64 mb, so I can not send you. But you can find it, if you read a little bit the forum.
And if you have read this thread, I do not need to send you the kez file. So read this thread.
Offline
thierryb wrote:
People at 4pda.ru think that I am devictoria. I can assure this in not the case.
They think that because they do not succeed to reproduce flashing the Rom. Probably they do not succeed because their card is not recognized after a soft reset. It was the case for me until I buy a Kingston one.
Not people at 4pda.ru... It was just my opinion. I was wrong, sorry. I thought so because after the first post about successful flashing there were no news for a long time. Excuse me.
Offline
No problem. You are welcome.
Offline
It is true, it works.
You MUST format the card with FAT 16.
I used pocket mechanic to format the card (FAT16 and Cluster size 32K) and I managed to make it work.
Ah! Before making "logical format" I have done "low level format," both with "pocket mechanic"
Last edited by HDJ80 (2007-12-13 15:12:08)
Offline
HDJ80 wrote:
It is true, it works.
On XDA-developers you attached your 1xdtgklo.kez in zip format.
But here devistoria says "1xdtgklo.kez - a file named "1xdtgklo.kez", serving as a password. It may be an EMPTY file."
And your file is not empty, there is one SPACE in it and its size is 1 byte.
Offline
pasha1976 wrote:
HDJ80 wrote:
It is true, it works.
On XDA-developers you attached your 1xdtgklo.kez in zip format.
But here devistoria says "1xdtgklo.kez - a file named "1xdtgklo.kez", serving as a password. It may be an EMPTY file."
And your file is not empty, there is one SPACE in it and its size is 1 byte.
devistoria says "It may be an EMPTY file."
devistoria not says "It must be an EMPTY file." ![]()
Offline
Oh, you are write, my mistake...
Offline
I am trying to update my ROM with the latest one posted: R2A_32_WWE-070622-601_diskimage.nb0
I placed the following two files on an empty 2gb sd card (ScanDisk brand)
diskimage.nb0 (64,000 KB)
1xdtgklo.kez (0 KB)
I follow the instructions posted by devictoria very carefully.
I try 3 times - each time it just did normal Hard Reset. But "A screen entitled OS Updating (SD) should appear:" did not happen. Instead I got the warning message about resetting with the normal Yes / No options - I press YES - this give the usual O2 welcome screen and then go through the usual hard set routine to aliegn screen etc. Can you please tell me what I might be doing wrong? I check to see if my SD card is readable - File explorer shows the files on my card. Is it possible that although the card is readable with the WM5 OS it is not accessible for upgrading my ROM? I know some people got problens with ScanDisk. Any help would be much appreciated. Thank you.