Is the E895 the same a a910 ?

[tmop69]

Ok, so I'll just reflash from 0xA0000 to 0x4000000 if needed. And now what firmware you suggests/want to try?

[sabrod]

Ok, so I'll just reflash from 0xA0000 to 0x4000000 if needed. And now what firmware you suggests/want to try?

Hum, i know a few about e895... Maybe ask Keta122, i also seem to remember the first fw vkin posted was working on a910 and e895, but i'm not sure of course...
That firmware was quite slow in fact, but vkin or Keta122 are probably the experts you need to ask for this...

[tmop69]

Hum, i know a few about e895... Maybe ask Keta122, i also seem to remember the first fw vkin posted was working on a910 and e895, but i'm not sure of course...
That firmware was quite slow in fact, but vkin or Keta122 are probably the experts you need to ask for this...

ok, I've just sent an message to ask for. let's see.

By the way, for restoring a phone FW, the command:
./boot_usb flash 0 firmware.bin
is NOT the correct one! I've totally killed an A910 unit... The boot_usb command does not protect the 640K of the bootloader and when it reads the flash it seems it cannot read correctly the boot loader area (I've tried with various phones and the first 640K are all full of 0xFF values. So reflashing starting from 0x0 will make the phone unusable. So, it necessary to start flashing from 0xA0000 unless you a have a dump with the correct infos for the boot loader area.

[sabrod]

Oh, shit!!
What exaclty happenned??
Bootusb is supposed to protect the place! At least to warn the user...
Where did you take it from?
Hum, on A910, first 640k are full of datas! There are plenty of littles CG's...
0x0 is a place to be carefull with... the MBM location ( bootloader ) too is crucial.
You wrote the datas at the wrong place??
Took a backup starting from 0xa0000 to write at 0x0 ?

Arff! It happenned quite the same thing to me once... On an A910 too!

One thing i learnt is to always name the backup files with the offset they are supposed to start ....
For example an A910 kernel CG is : A910-kernel-0xa0000 ( the size of the file tells bootusb where to stop, of course. )

Maybe some jtab cable and software could revive the phone, but it would need some experimentation, and knowledge for this...

[tmop69]

I've downloaded from the link in Backups - OpenEZX. I've used to dump the Barbados fw and also the A910 and a couple of E6. After killed the A910, I've noticed that all these file dumps have the bootloader area filled with 0xFF value. So, in fact, it's quite strange.
I have 2 identical A910 and in the past days I've tested one of the A910 fw on this site. Althought the flash completed successfully (using RSD tool) at 100% the phone was not booting correctly (just stopping at the initial Moto logo). But the bootloader was working. So, I've dumped the 64MB of the other A910 and tried to replace to the non working unit. Of course, I've started writing the whole 64MB file, starting from 0x0 killing the phone, since the file was plenty of 0xFF values in the 640K boot block area. So, the mistake was not related to the use of the tool, but to not have previously checked inside the file before flashing it.

I wondering now if there is another version of the usb_tool that is dumping correcly the bootloader area and where is possible to find the memory maps with the addresses for the various areas of the phone flash memory?

I don't think I'll try the jtag recovery, but just save some spare parts and trash it away.

[sabrod]

Ok, too bad...
Pick bootusb's binary there : http://people.openezx.org/wyrm/boot_usb ( always use the latest unless you know why you don't )
Also getting started wiki page tells you how to build it, bootusb is relatively simple to compile... once you've downloaded a 2.6.29 kernel's source tree

Yes, keep at least the case, as they are relatively rare... ( you can send me the bricked A910 board if you like ).jtag seems doable, but the thing is: Where are the testpads, and is there any on the board!!!!???

[tmop69]

ok, I'll try with the boot_usb on your link. I've just noticed that the version I used is different (the file name is "boot_usb_svnr2421") althought downloaded from the same site. Let's see if with this I'll get a correct dump of the bootloader area.
Also because I want to try to see if I can fix two E6 (both "engineering marketing" models) that do not like to be flashed with RSD. One is booting, but on the main screen is always showing a "system busy" error messages when you try to enable the antenna (I think the kernel is looping in logging mode). The other is blocked after the initial logo due to a block in the flashing process (it always stops at 26% of the process...). It was working ok before I tried to flash... yes, I'm definitely not lucky with this process on the EZX platforms!

[sabrod]

Hehehe... Wel it was my old compilation of bootusb, and i linked it because it was supposed to be protected!! l Also, at the time i uploaded it i suspected not all bootusb binaries were protected so i choose to link that one for the safety of the phones
Seems i was wrong!!!

Maybe the marketting phones are not 100% identical to the hardware sold to mass market??

You could try to boot an openezx linux kernel?
if you set correctly the correct machid it is supposed to run on the devices...

To try some qtopia rootfs :
1) partition and format an ext2 partition on an SD ( rootfs).
2) download and extract to the Sd' rootfs this: http://ezxdev.org/qtopia/testing/Ang....rootfs.tar.gz
( angstrom rootfs tuned for qtopia.)

3) Extract this as well on the rootfs: Index of /muromec/image/2009-06-06 ( latest qtopia release from muromec)

4) muromec recommend this kernel: http://people.openezx.org/muromec/im...9-06-14/zImage and extract all the modules from http://people.openezx.org/muromec/im...-14/mod.tar.gz to the rootfs as well....

5) copy that file to the rootfs too (supposedly in / bin, but i dunno where, sorry, but you will see some mux ( gsm network)non fatals errors if you don't ! But might power off the device after 1 minut of use...( watchdog )
http://people.openezx.org/muromec/mux

6) config scripts to launch qtopia are there and have to be placed to /etc/ http://people.openezx.org/muromec/init.d_qpe and http://people.openezx.org/muromec/default_qtopia

7) utility to calibrate the touch screen.http://people.openezx.org/muromec/pointercal


all copyrights goes to Muromec http://ezxdev.blogspot.com/

[tmop69]

... the boot_usb in your link wants GLIBC 2.4 and the Knoppix live DVD 5.1 has the 2.3! That's frustrating.... it will be surely a nightmare to install on it the correct package (with all the usual mess of dependencies). I need to find another live distribution to test, surely it will be faster.

Anyway, for you other question, this phones has some differences in the case (especially the backcover, in the area of the camera has a different design), the boot screen shows the "PENGLAY" label instead of "MACAU" and the fw is CSCEZX_N_01.00.14I_11.70.13I.

[sabrod]

well, you coul dcompile the latest bootusb, it is a matter of minuts...
The problem is that you need space to extract the latest linux kernel... ( bootusb needs to search for some files in that mess )
I suppose everything is installed on knoppix to do so? (needs a package maybe... libusb-dev?? it's tiny...)

So penglay is the barbados? Ok, sory i was wrong, i just still don't know what the barbados could be... Thanks for the precision!!