Android Tablets Forum banner

[ROM] [4.2.1] Novo7 Flames 0201 Official AML Firmware

251K views 361 replies 112 participants last post by  kj_najd 
#1 · (Edited by Moderator)
Novo7 Flames 0201 Official AML Firmware

QM Screen:
Download Link1
Download Link2

File: Ainol-E4-20130131-qimei-usbburning.zip
Size: 280,339,646 bytes
Modified: February 5, 2013, 10:02:10
MD5: 948089FA311077BD5A4B91326113EB15
SHA1: 0014FE49DA12A9636B6D15F28F07BACAB6DC1EA0
CRC32: 8D58CB96

TM Screen:
Download Link
Mediafire (Thanks to fuser-invent)

Flash tool:
AML Flash Tool (USB-Burning-tool-v1.6.2.0128):
Download Link1
Download Link2

Flash Tutorial:
bbs.ainol
myphone (Thanks to Frontier)
post #14 (Thanks to dd_yulius)

TWRP Custom Recovery (Thanks to CT our mother of ROM
)
TM
QM

File Transfer
MTP
ADB

android.process.acore pop up error after setup Google Play?
put this Contact.apk to /system/app/ and chmod rw-r--r-- (Thanks to hithotguest)

Stuck with this firmware?

Try This

Original Thread:
bbs.ainol
 
See less See more
1
#41 ·
Today I continue testing my Flame-QM with AML ROM 0131 (JB 4.2.1):
- Internal Storage become 12GB
- I can not flash to other ROMs... Vol - and Power doesn't work

- Audio and visual works great with HDMI
I plug in to my LED TV LC32LE240

- Skype 3.0.0.6181 works without "green screen"
and quality of voice call depend on volume (mic) setting and network mostly
- Rear Camera is flip (left to be right) but not mirror.
- Front Camera only have 2 option for Picture size, VGA and QVGA

- Battery level reached 3% but I didn't wait until shutdown... at 4% and 14% notification appeared (maybe vary) ...
- I still can not send-receive data via BT with my notebook (I have tried official or unofficial rom), but I can live with that

- Now I can Unmount USB storage (via OTG)

- Now testing sleep mode with wifi on...

Regards
 
#49 ·
You can't, they moved to the /data/media layout (like 'high streets' brand and nexus devices) so there's no more a partition to be exported via ums.
They did this for the multi user, that's why i was saying that without the datamedia thing mu is only a giant workaround and should be avoided.
 
#57 ·
Someone have go back to other FW after instal this one ?
Tried to go back to "Happy Spring Festival" 0130 without succes.

Skype works, Youtube works , startup much faster , but it is not compatibile with a lot of apps , have preinstaled chineese apps, CIFS Manager not working.... that is the main issues why i want to go back to oldest soft.
 
#74 · (Edited by Moderator)
Just sharing my experience after flashing this official Android 4.2.1 aml firmware and using it for 1 day.

What I like :

1. Top in the list is - the battery indicator problem is solved. I was able to use the tablet until my battery indicator reached less than 10% and when the warning appeared asking me to connect to the charger.

2. The annoying "popping" sound that happens every now and then when touching the screen is gone.

3. A few things about the new version of Android 4.2.1 which I won't go into yet.

What needs improving :

1. The screen turns on from standby could be faster if possible.

2. The need to manually include "contact.apk" in the /system/app/ and setting the rw-r-r permission to it. (BTW, let me thank 'highotguest' for the tips)

3. ..... Camera??

That's all I can say for now.

Thanks to all.

Also looking forward to any improvements by our great developer, Christian Troy and Fei Yu based on this new ROM.
 
#75 ·
How I managed to put and copy of 'contact.apk' in /system/app according to the tips given by highotguest.

Since, I am not a geek, I did not use the terminal emulator program to push (copy/paste) and chmod (setting the rw-r-r permission).

Instead this is what I did.

1. Open es file manager and in the settings, turn on root function.

2. Copy the file, 'contact.apk' over to the /system/app folder.

3. Right click on 'contact.apk' and select properties.

4. once you are inside properties menu, you should be able to change the file permission to rw-r-r

5. Close as file manager and reboot.

When the tablet reboots, something is being updated. From then on, I was able to sign in Google play without getting the error messages.

Hope this helps.
 
#77 ·
hello!
i just moved to this version.
i think its super nice. i actually dont mind the small text, i like it. the benchmarks are significantly higher but that could also be attributed to having about 25% higher cpu clock speed.
here's whats wrong for me.
1- camera, has absolutly no quality. its like this on each rom. i dont get why put a 5mp sensor and give only vga quality as option.
2- need to get a build prop of nexus7 sig or sgs2 idk which, but many apps on store (mainly games) wont let me install on this sig.

basically thats that bothers me now. o.w its super nice and fast, flash works out of the box, i.e streaming putlocker n such.

it does heat a bit but i actually dont use this tab for gaming a lot so i dont get to where its actually a bother. video playing capabilities are smoother and faster imo.

have a gr8 week!
 

Attachments

#78 ·
shoot i wanted to install this firmware to create a 4.2 comp zip with real multi user support, only for the fire but I can't.

I tried following all rules but if I select the "erase nand" thing after it finishes the device is not recognized anymore, if I unplug and replug it to flash the zip without the erase nand thing it fails loading uboot and I have to flash the unbricker.

If I try to flash directly the zip without erase nand before that it stays at 77% for something like 10/15 minutes, after that i turn if off and procede with the unbrick again.

Terrible firmware delivery system.
 
#79 ·
The system is a bit picky, but it works.
Let's start from the beginning (you can also read my tutorial in myphone.gr using Google translate - see OP).
Start by selecting "erase nand" AND "no hub support". The tricky part is to put the device in uboot loading mode; assuming that you've already installed the necessary AMLburningtool USB drivers, press and hold either POWER+VOL- or POWER+VOL+ until you see AMLtool recognize your Fire. Flash the first part and when it finishes (indicated by a GREEN port icon), press STOP and disconnect the tablet.

Next, uncheck "erase nand" but leave the other option checked (no usb hub) and try the same procedure again (POWER+VOL- or POWER+VOL+) until the tool recognizes the tablet. Then START and flash the actual ROM.
 
#82 · (Edited by Moderator)
Can I just say to all those who have had problems with the Amlogic burning tool getting stuck at 77%-86%. I found the solution for me was to run the flash tool under Administrative privileges.

Before I did that I found my device would re-connect in windows with "WPD FileSystem Volume Driver" driver (instead of the "WorldCup_Device" driver) at the end of the firmware install process (between 77%-86%) & the flash tool wouldn't continue as it couldn't find the device (and would eventually timeout).

Once I ran it as an Administrator it went all the way through the firmware update process without a hitch.
 
#86 · (Edited by Moderator)
i was coming from feiyu hsf, i'll try with 1211...

btw did you run it with the two passes? before wipe nand and after without wipe nand or you gave it straight the zip?

because here it hangs always at 77%:

Code:
[T 0][11:39:20]: Transfer Complete! total size is 4704256 Bytes<br />
[T 0][11:39:26]: test command exec: crc 0x82000000 4704256 cc9e1542<br />
[T 0][11:39:26]: command exec: crc 0x82000000 4704256 cc9e1542<br />
[T 0][11:39:26]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
when crc checks the sent recovery... it doesn't get an answer back

edit: no difference, always stucked at 77%.

Fuckin' ainol, if at least they'd release the kernel code I'll be doing it by myself.

The problem here is the new bootloader, the one like the Hero, that's why you have to flash it using a PC.
 
#88 ·
i was coming from feiyu hsf, i'll try with 1211...

btw did you run it with the two passes? before wipe nand and after without wipe nand or you gave it straight the zip?

because here it hangs always at 77%:

Code:
[T 0][11:39:20]: Transfer Complete! total size is 4704256 Bytes<br />
[T 0][11:39:26]: test command exec: crc 0x82000000 4704256 cc9e1542<br />
[T 0][11:39:26]: command exec: crc 0x82000000 4704256 cc9e1542<br />
[T 0][11:39:26]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
when crc checks the sent recovery... it doesn't get an answer back

edit: no difference, always stucked at 77%.

*perfect' ainol, if at least they'd release the kernel code I'll be doing it by myself.

The problem here is the new bootloader, the one like the Hero, that's why you have to flash it using a PC.
Are you unbricking & then running the flash tool again? Or have you tried the power off/Volume- power combination & then attempt re-flash, without un-bricking? In other words trying to re-flash, using the bricked device (after stuck at 77%).

I can replicate the 77% stuck process, but when I power down/Volume- power up & try again it goes through OK. I haven't needed to run the un-brick process.
 
#90 · (Edited by Moderator)
Yes I've tried, it gets stuck, I hit stop, unplug and turn off the device, turn if on with power+vol-, connect to usb (it's recognized as chip M6 and detected on another port), hit start again, uboot failure.

Tried on a native windows 7 (as admin, no av and no firewall since i never use 7) and an emulated xp.

That's the log from xp

current pc version is: xp
current tool version is: v1.6.2.0128
-----importUpgradeFile-----filenameC:\Documents and Settings\Alan\Desktop\Ainol-E4-20130201-tima-usbburning.zip
[T 0][14:51:56]: load spl ...
[T 0][14:51:57]: load uboot ...
[T 0][14:51:58]: test command exec: crc 0x8f800000 520348 4e80a205
[T 0][14:52:01]: command exec:set_chgcur 0
[T 0][14:52:02]: command exec:video dev bl_off
[T 0][14:52:03]: command exec:video dev disable
[T 0][14:52:04]: command exec:sf probe 2
[T 0][14:52:05]: command exec:sf erase 0 1000
[T 0][14:52:06]: command exec:nand rom_protect off
[T 0][14:52:07]: command exec:nand scrub 0
[T 0][14:52:18]: command exec:nand info
[T 0][14:52:19]: command exec:defenv
[T 0][14:52:20]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 0][14:52:21]: command exec:setenv recovery_command --usb_burning
[T 0][14:52:22]: command exec:save
[T 0][14:52:24]: load uimage ...
[T 0][14:52:30]: Transfer Complete! total size is 4704256 Bytes
[T 0][14:52:38]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 0][14:52:38]: command exec: crc 0x82000000 4704256 cc9e1542
[T 0][14:52:38]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
[T 0][14:53:33]: command exec once more: load uimage
[T 1][14:54:40]: load spl ...
[T 1][14:54:40]: Transfer Complete! total size is 18712 Bytes
[T 1][14:54:49]: load uboot ...
[T 1][14:54:50]: load uboot ...
[T 1][14:54:51]: load uboot ...
[T 1][14:54:52]: load uboot ...
[T 1][14:54:53]: load uboot ...
[T 1][14:54:54]: load uboot ...
[T 1][14:54:55]: load uboot ...
[T 1][14:54:56]: load uboot ...
[T 1][14:54:58]: load uboot ...
[T 1][14:54:59]: load uboot ...
[T 1][14:55:00]: load uboot ...
[T 1][14:55:01]: load uboot ...
[T 1][14:55:02]: load uboot ...
[T 1][14:55:03]: load uboot ...
[T 1][14:55:04]: load uboot ...
[T 1][14:55:05]: load uboot ...
[T 1][14:55:07]: load uboot ...
[T 1][14:55:08]: load uboot ...
[T 1][14:55:09]: load uboot ...
[T 1][14:55:10]: load uboot ...
[T 1][14:55:11]: load uboot ...
[T 1][14:55:11]: load uboot failed 15 times,maybe because the spl code run err
[T 1][14:55:12]: failed because no connected device ,current step is 1

When it fails there's no other option then unbricking it since it always goes in m6 chip mode.

They're great in screwing things, I have to admit it. The light sensor is another example, it was perfectly working and now in direct noon sunlight doesn't report more than 10 lux

The cute thing is that if I wanna bypass that shitty software and flash bootloader.img from that rom it finishes in chip m6 mode too.
 
#94 ·
Yes I've tried, it gets stuck, I hit stop, unplug and turn off the device, turn if on with power+vol-, connect to usb (it's recognized as chip M6 and detected on another port), hit start again, uboot failure.

Tried on a native windows 7 (as admin, no av and no firewall since i never use 7) and an emulated xp.

That's the log from xp

current pc version is: xp
current tool version is: v1.6.2.0128
-----importUpgradeFile-----filenameC:\Documents and Settings\Alan\Desktop\Ainol-E4-20130201-tima-usbburning.zip
[T 0][14:51:56]: load spl ...
[T 0][14:51:57]: load uboot ...
[T 0][14:51:58]: test command exec: crc 0x8f800000 520348 4e80a205
[T 0][14:52:01]: command exec:set_chgcur 0
[T 0][14:52:02]: command exec:video dev bl_off
[T 0][14:52:03]: command exec:video dev disable
[T 0][14:52:04]: command exec:sf probe 2
[T 0][14:52:05]: command exec:sf erase 0 1000
[T 0][14:52:06]: command exec:nand rom_protect off
[T 0][14:52:07]: command exec:nand scrub 0
[T 0][14:52:18]: command exec:nand info
[T 0][14:52:19]: command exec:defenv
[T 0][14:52:20]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 0][14:52:21]: command exec:setenv recovery_command --usb_burning
[T 0][14:52:22]: command exec:save
[T 0][14:52:24]: load uimage ...
[T 0][14:52:30]: Transfer Complete! total size is 4704256 Bytes
[T 0][14:52:38]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 0][14:52:38]: command exec: crc 0x82000000 4704256 cc9e1542
[T 0][14:52:38]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
[T 0][14:53:33]: command exec once more: load uimage
[T 1][14:54:40]: load spl ...
[T 1][14:54:40]: Transfer Complete! total size is 18712 Bytes
[T 1][14:54:49]: load uboot ...
[T 1][14:54:50]: load uboot ...
[T 1][14:54:51]: load uboot ...
[T 1][14:54:52]: load uboot ...
[T 1][14:54:53]: load uboot ...
[T 1][14:54:54]: load uboot ...
[T 1][14:54:55]: load uboot ...
[T 1][14:54:56]: load uboot ...
[T 1][14:54:58]: load uboot ...
[T 1][14:54:59]: load uboot ...
[T 1][14:55:00]: load uboot ...
[T 1][14:55:01]: load uboot ...
[T 1][14:55:02]: load uboot ...
[T 1][14:55:03]: load uboot ...
[T 1][14:55:04]: load uboot ...
[T 1][14:55:05]: load uboot ...
[T 1][14:55:07]: load uboot ...
[T 1][14:55:08]: load uboot ...
[T 1][14:55:09]: load uboot ...
[T 1][14:55:10]: load uboot ...
[T 1][14:55:11]: load uboot ...
[T 1][14:55:11]: load uboot failed 15 times,maybe because the spl code run err
[T 1][14:55:12]: failed because no connected device ,current step is 1

When it fails there's no other option then unbricking it since it always goes in m6 chip mode.

They're great in screwing things, I have to admit it. The light sensor is another example, it was perfectly working and now in direct noon sunlight doesn't report more than 10 lux

The cute thing is that if I wanna bypass that *shiny software and flash bootloader.img from that rom it finishes in chip m6 mode too.
My install log:

current pc version is: win7
current tool version is: v1.6.2.0128
-----importUpgradeFile-----filenameC:\Ainol-E4-20130201-tima-usbburning.zip
[T 5][22:26:01]: load spl ...
[T 5][22:26:02]: load uboot ...
[T 5][22:26:03]: test command exec: crc 0x8f800000 520348 4e80a205
[T 5][22:26:07]: command exec:set_chgcur 0
[T 5][22:26:08]: command exec:video dev bl_off
[T 5][22:26:09]: command exec:video dev disable
[T 5][22:26:10]: command exec:sf probe 2
[T 5][22:26:11]: command exec:sf erase 0 1000
[T 5][22:26:12]: command exec:nand rom_protect off
[T 5][22:26:13]: command exec:nand scrub 0
[T 5][22:26:23]: command exec:nand info
[T 5][22:26:24]: command exec:defenv
[T 5][22:26:25]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 5][22:26:26]: command exec:setenv recovery_command --usb_burning
[T 5][22:26:27]: command exec:save
[T 5][22:26:28]: load uimage ...
[T 5][22:26:28]: Transfer Complete! total size is 4704256 Bytes
[T 5][22:26:34]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:26:34]: command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:26:34]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
[T 5][22:32:22]: command exec once more: load uimage
[T 5][22:32:23]: load uimage ...
[T 5][22:32:24]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:32:24]: command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:32:24]: command exec once more: load uimage
[T 5][22:32:25]: load uimage ...
[T 5][22:32:26]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:32:26]: command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:32:26]: command exec once more: load uimage
[T 5][22:32:27]: load uimage ...
[T 5][22:32:28]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:32:28]: command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:32:28]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
[T 5][22:32:28]: command exec once more: load uimage
[T 5][22:32:29]: load uimage ...
[T 5][22:32:30]: crc 0x82000000 4704256 cc9e1542 failed
[T 5][22:32:31]: failed ,current step is 17
[T 5][22:32:56]: load spl ...
[T 5][22:32:56]: Transfer Complete! total size is 18712 Bytes
[T 5][22:33:05]: load uboot ...
[T 5][22:33:05]: Transfer Complete! total size is 520348 Bytes
[T 5][22:33:11]: test command exec: crc 0x8f800000 520348 4e80a205
[T 5][22:33:11]: command exec: crc 0x8f800000 520348 4e80a205
[T 5][22:33:11]: sendCommandWithReply: crc 0x8f800000 520348 4e80a205 maxCount:30
[T 5][22:33:12]: begin run 8f800000
[T 5][22:33:16]: finish run 8f800000
[T 5][22:33:18]: command exec:set_chgcur 0
[T 5][22:33:19]: command exec:video dev bl_off
[T 5][22:33:20]: command exec:video dev disable
[T 5][22:33:22]: command exec:sf probe 2
[T 5][22:33:23]: command exec:sf erase 0 1000
[T 5][22:33:24]: command exec:nand rom_protect off
[T 5][22:33:25]: command exec:nand scrub 0
[T 5][22:33:42]: command exec:nand info
[T 5][22:33:43]: command exec:defenv
[T 5][22:33:44]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 5][22:33:45]: command exec:setenv recovery_command --usb_burning
[T 5][22:33:46]: command exec:save
[T 5][22:33:47]: load uimage ...
[T 5][22:33:48]: Transfer Complete! total size is 4704256 Bytes
[T 5][22:33:54]: test command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:33:54]: command exec: crc 0x82000000 4704256 cc9e1542
[T 5][22:33:54]: sendCommandWithReply: crc 0x82000000 4704256 cc9e1542 maxCount:30
[T 5][22:33:55]: command exec:bootm 0x82000000
[T 5][22:33:57]: boot uImage ...
[T 5][22:34:49]: find disk: G:
[T 5][22:34:50]: recoveyCommand: wipe_data prepareCommand:
[T 5][22:34:50]: send command : wipe_data ok!
[T 5][22:35:09]: wipe_data success(wipe_data):eek:k
[T 5][22:35:10]: recoveyCommand: update:update.zip prepareCommand:
[T 5][22:35:50]: copy successed:update.zip
[T 5][22:35:50]: send command : update:update.zip ok!
[T 5][22:38:02]: update:update.zip success(update:update.zip):eek:k
[T 5][22:38:03]: recoveyCommand: shutdown prepareCommand:
[T 5][22:38:03]: send command : shutdown ok!
C:/USB-Burning-tool-v1.6.2.1228/log/02.11.00.06_Ainol-E4-20130201-tima-usbburning_manual.log
success:2 failed:1 failed postion: s17:1

When it fails at 77% I leave the USB plugged in, power off the device, then power on & volume-, then run the flash again.

I select "erase nand", and under settings set "auto burn firmware after enable erase nand".
 
#91 ·
i was riff raffing through ...
if someone isnt successful in using the flash tool / stuck at 86 %

after having installed the world cup driver

1- load burning tool
2- file->import upgrade file. choose the 267 mb zip file. ok. (tab should be connected on one of the ports)((this is our part to press vol- and pwr untill its recognized))
3- select the options nand erase and no usb hub press start.
4- after that finishes deselect earase nand and press start again.((no usb hub is checked)) (tab should be connected on one of the ports)
4- did it for me.

on QM.
 
#92 · (Edited by Moderator)
The thing is that if I try the "double" pass with nand erase before that it ends in m6 mode and in that mode it's bricked.
If i avoid nand erase it gets stucked at 77%.

I guess there may be some slightly different hw revisions (not only the TM-bma/mma and QM-bma/mma) which will behave differently with that crappy thing

edit: anyway for those of you that have it running try to boot this uImage_recovery, it's TWRP 2.4.1 and should be working with this build
 
#95 ·
Yes. Happens sporadically. Have had to hard reset each time. Still playing with settings to see if wireless or daydream or something creating the problem.

Funny thing is that on the one device I have with a dead touch-screen I can move the mouse around & I get the mouse cursor over the black screen. I can also get some vibration when I click on where the back or home button should be, but the screen stays dead. On my other tablets with fully-functioning touchscreens, touching has no effect on screen as you describe.

I have to say I dislike the washed out graphics in this ROM.

And the light sensor isn't working.
 
#99 ·
man I don't know how but it started flashing... i unplugged/replugged it several times when uboot was failing


twrp seems having problems with partitions, even if I have set the correct entry points. Anyway display kinda sucks, max brightness is incredibly dim, I'm not sure I'm going to do a comp zip for this thing
 
#104 · (Edited by Moderator)
I've fixed brightness problem in recovery. It seems that real brightness is set only after the device suspends / resume, so in the init I do this "game"

TWRP 2.4.1.0
 
#106 ·
Cheers.

Any fix to the non-responsive touchscreen after sleep? When you get a moment


Oh, and I've loaded up Netflix (2.1.1), I don't have an account but I'm happy to send a logcat of it running if that helps?
 
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