Android Tablets Forum banner

Amlogic Low level flashing tool

65K views 48 replies 10 participants last post by  chihaha 
#1 · (Edited by Moderator)
WARNING<>
I Haven't tested this on the ELF_II

Its here for the benefit of development, and those who really know what they're doing/don't care how much damage they do
This has come from the Fire 0921 beta firmware, it's designed for flashing multiple devices in one go.
It will also flash blindly (ie with no firmware on the device at all) !

http://dropcanvas.com/2o0zo

it doesn't have 64 bit drivers so I created some libusb ones (GPL ftw
)

http://www.slatedroi...post__p__429899
on the Fire the update procedure fails...

but

but

it gives the option to lowlevel wipe the nand!
haven't tried this on the elf II yet to see if it gets rid of the badly recorded bad blocks.

EDIT

Instructions doc is in Chinese,
here's a vaguely translated version.
 

Attachments

See less See more
2
#4 ·
Very Interesting.....but where do the files come from mentioned in the instructions? i.e. usb_spl.bin and config_progress.xml? If these are a part of the Fire's update package and will they be safe to use with the Elf II?

Also, how do you get out of 'M3-Chip' mode?....I can't seem to get back to normal mode.....
 
#5 ·
Right, as my Elf II has bad NAND, I decided to experiment with this. Very interesting! Hope some of this info helps...

It took some time to get into the USB flashing mode but in the end I got there by pressing Power, Vol- and Home (while tab was on and plugged into USB). You will see the tab power down, ut you won't hear the device unloading in windows - when that happens, press those keys again and screen will stay dark but windows will identify a new device =- M3-Chip' which you can install the drivers for. I have had my pad identifying as 'M6-Chip' before so not sure what difference is - I guess M3 is the chip that boots the system?

You have to download the Fire ROM to get the usb burning files like config_progress.xml, usb_spl.bin etc and create a zip file for updating - all fine - I just removed the Fire Rom and Patch.zip files and replaces them with Ainol 0717 Firmware files, which you have to change the name on to update_qimei.zip. Patch.zip is fine (or you can edit the xml file)

I first tried to erase the NAND as thats what I need with all my bad blocks - Success! It got to 100%! I clicked stop and tried to reboot, but the tab is stuck in the M3-Chip mode - anyone got any ideas?

As I could not get out of M3-Chip mode, I decided to try burning the ROM. I got to step 20 where it says 'update_qimei.zip:bad' here the output from the cmd window:

"busy"
20 / 24
"failed(update:update_qimei.zip):bad"
disk path: "H:"
"failed ,current step is 20 "
---------call System Rescan------------
---------call System Rescan finished----
disk path: "H:"
disk path: "H:"
disk path: "H:"
2 exit

Again I am with a tab that I can't get out of M3-Chip' mode. I suspect there are some fire specific things in the AML firmware that might be making it fail - but the NAND wipe should have worked? How do we get back to 'normal' mode???
 
#7 · (Edited by Moderator)
you should be able to remove the usb cable and hold the power button down

but I'm a bit confused as to exactly what you've used from the fire?
there's nothing from the fire in there from what I can see unless you add them yourself..
the usb_spl may well be a very generic thing, the uboot-orig.bin should be one of the ones that come with a stock fW
but I can't see a lot of binary difference between the elf and fire versions of that one.

the usb_uImage isn't flashed till after the nand wipe using the normal xml and not at all using delete.

the config xml is in the main folder of the tool, as are some examples, including the config_progess_erase.xml

I Don't think you need to flash the uImage at all

EDIT

looking at it, I'd suggest if you really are stuck in M3 to:

change the config erase to

run :false for the usb_spl
and
run :true for the spl_orig

that makes sense to flash the original to me, but that erase should flash the correct old Spl anyway.
 
#8 ·
>update identify
[Port3]DeviceConnected: â•©Âşâ–‘â–„
[Port3]DeviceConnected: â•©Âşâ–‘â–„
AmlUsbIdentifyHost
IOCTL_IDENTIFY_HOST_Handler ret=-116
reset worldcup device
Reset WorldCup Device
ERROR: get info from device failed
aml_close_logfile
Also lots of errors while using, looks like elf2 can't work with it.
Tablet can't be bricked, if you use update.exe
 
#14 ·
Thanks HerX - It does work, but takes ages to get started...

My tab now works and I only have 1 bad block! NAND wipe did do some good!

Only problem now is that touch is a bit strange - when typing your sometimes get loads of (wrong) chars....sometimes you just get the wrong char. Icons are sometimes not working either - you have to play around a bit to hit the icons slightly off from their real position - anyone know why this might be happening in PA and CM10 (tho to a lesser extent.

Will update all when i've don't this again to see if I can do it better.
 
#16 ·
Seems like that might be true, but I fail to see where the program is actually updating the AML firmware? In usb_spl.bin? Could I replace this file with an Elf II file and where might I find it? ....or is there nothing I can do about this?
 
#25 ·
If you look at the file aml_autoscript thats in the image it contains this:

GADMEI nand scrub script N
if itest ${upgrade_step} > 0 then
nand rom_protect off
nand scrub 0
reset
fi

Which are the same instructions in the erase script in the AML tool

Dont suppose you have any ideas on how I might revive my tab, or do you think i've toasted it as well?
 
#27 ·
hmmmm....mine booted after doing the multipart....i dont even have a device recognised anymore - m3 or m6. You do know that when the multipart recovery runs, you will see it loading the new firmware then it will reboot and do another session of updating the firmware. If you stop the process half way through, it won't work. Hope that helps...
 
#31 ·
i'm going to try a differemt card as well.....let me know how u get on...

I might try Andrew's method as well - the only difference between the two methods is that there is aml_autoscript (which wipes the nand). I'm sure the partition size makes no difference surely? Or does it expect that size partition when factory reset from the sd?
 
#36 · (Edited by Moderator)
time to start playing with this I think

http://openlinux.aml..._uboot_to_board

...

ha

I appear to have a uboot up at least

using the svn I copied the latest uboot.bin as
u-boot-aml.bin

to that folder than ran mksdcard on the drive
(in effect it just does a dd if= )

that's got me some signs of power on at least.

from there I decided to manually

dd the multipart recovery img onto the scard in *nix
(you could use usb-imagewriter if you prefer a gui , that does the same thing)
sod these silly windoze utilities..

and its back to life
 
#48 ·
Hi Fards.....I decided to have a go at getting me Elf II going again - how did you get your uboot working again? Did you use anything from the link above to help you? Mine still just lights up and does nothing...

One thing I have noticed is that my usb connector was loose - in fact came off today when i plugged in! This could have much to do with my problems!
 
#41 ·
When it was getting the lit up screen then it wasn't being recognised by lsusb in Linux. Decided not to bother with windows this morning.
only so Much of not having any control that I can take


if you have a Linux install (even a live distro on a USB stick) then the simplest way for you is to install usb-imagewriter as it's very simple to use.
 
#43 ·
yup if you use that and then look at the sd cardf in something like gparted it will come up with a small partition then a second unreadable fat32 then a seperate unused remainder of the disk ... the windows tool was just rendering the disk unusable.

when I tried using a u-boot-aml.bin (renamed elf-ii uboot) and mksdcard it was lighting up the screen but not recognised over usb at all.
 
#45 ·
did anyone get this message , [T 1][21:08:42]: write data to ram failed! , bricked my gadmei t863 v1.0 , and was trying amlogic tool , but when the script starts to run it has the following problem "[T 1][21:08:42]: write data to ram failed!" , which comes from first line in config.xml , <command sn="0" path="usb_spl.bin" address="0xd9000000" run="true">load spl</command> , i think it may be a problem with memory address or something !! can anyone help guys ?
 
#46 ·
Hi
Amlogic Burning Tool %76 Failed Usb Help

[T 3][10:15:08]: load spl ...
[T 3][10:15:08]: Transfer Complete! total size is 18452 Bytes
[T 3][10:15:17]: load uboot ...
[T 3][10:15:17]: Transfer Complete! total size is 482976 Bytes
[T 3][10:15:23]: test command exec: crc 0x8f800000 482976 37aede47
[T 3][10:15:23]: command exec: crc 0x8f800000 482976 37aede47
[T 3][10:15:23]: sendCommandWithReply: crc 0x8f800000 482976 37aede47 maxCount:30
[T 3][10:15:24]: begin run 8f800000
[T 3][10:15:27]: finish run 8f800000
[T 3][10:15:30]: command exec:set_chgcur 0
[T 3][10:15:31]: command exec:nand rom_protect off
[T 3][10:15:32]: command exec:nand scrub_all
[T 3][10:15:46]: command exec:nand erase 0 2000000
[T 3][10:15:47]: command exec:defenv
[T 3][10:15:48]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 3][10:15:49]: load command: setenv recovery_command --usb_burning
[T 3][10:15:50]: command exec:cmd_in_mem 0x82000000
[T 3][10:15:51]: command exec:save
[T 3][10:15:52]: load uimage ...
[T 3][10:15:53]: Transfer Complete! total size is 4096389 Bytes
[T 3][10:15:59]: test command exec: crc 0x82000000 4096389 8b019e13
[T 3][10:15:59]: command exec: crc 0x82000000 4096389 8b019e13
[T 3][10:15:59]: sendCommandWithReply: crc 0x82000000 4096389 8b019e13 maxCount:30
[T 3][10:16:00]: command exec:bootm 0x82000000
[T 3][10:16:02]: boot uImage ...
[T 3][10:16:39]: cannot find disk!
[T 3][10:16:40]: failed because no connected device ,current step is 16
[T 3][10:26:04]: load spl ...
[T 3][10:26:04]: Transfer Complete! total size is 18452 Bytes
[T 3][10:26:13]: load uboot ...
[T 3][10:26:13]: Transfer Complete! total size is 482976 Bytes
[T 3][10:26:19]: test command exec: crc 0x8f800000 482976 37aede47
[T 3][10:26:19]: command exec: crc 0x8f800000 482976 37aede47
[T 3][10:26:19]: sendCommandWithReply: crc 0x8f800000 482976 37aede47 maxCount:30
[T 3][10:26:21]: begin run 8f800000
[T 3][10:26:24]: finish run 8f800000
[T 3][10:26:26]: command exec:set_chgcur 0
[T 3][10:26:27]: command exec:nand rom_protect off
[T 3][10:26:28]: command exec:nand scrub_all
[T 3][10:26:42]: command exec:nand erase 0 2000000
[T 3][10:26:43]: command exec:defenv
[T 3][10:26:44]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 3][10:26:45]: load command: setenv recovery_command --usb_burning
[T 3][10:26:47]: command exec:cmd_in_mem 0x82000000
[T 3][10:26:48]: command exec:save
[T 3][10:26:49]: load uimage ...
[T 3][10:26:49]: Transfer Complete! total size is 4096389 Bytes
[T 3][10:26:55]: test command exec: crc 0x82000000 4096389 8b019e13
[T 3][10:26:55]: command exec: crc 0x82000000 4096389 8b019e13
[T 3][10:26:55]: sendCommandWithReply: crc 0x82000000 4096389 8b019e13 maxCount:30
[T 3][10:26:57]: command exec:bootm 0x82000000
[T 3][10:26:59]: boot uImage ...
[T 3][10:27:35]: cannot find disk!
[T 3][10:27:36]: failed because no connected device ,current step is 16
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top