Android Tablets Forum banner
1 - 17 of 17 Posts

·
Registered
Joined
·
25 Posts
I used : Notebook (with USB 2.0 port) and Win7 Home Basic 64 bit.
My Flame : QM and installed Feiyu ROM 0103.

I flashed and followed @Frontier and Lokumrom steps ...

1. Download Ainol-E4-20130131-qimei-usbburning.zip dan USB-Burning-tool-v1.6.2.1228
2. Extract USB-Burning-tool-v1.6.2.1228 into your PC/NoteBook
3. Turn Power Off Flame and plug it into PC/Notebook using USB (better using USB 2.0 port)
4. Push Volume - and Power wait until Windows detect New Hardware
5. Then select the driver manualy and browse into folder USB-Burning-tool-v1.6.2.1228 and select folder AmlogicusbBurningdriver
6. When it's done.. by default your USB connection will be named "WorldCup Device"
7. Still Power Off Flame Flame Screens still OFF/blank , run ImageBurnTool.exe
8. Flame will be detected in one of eight ports and the status is "Connect"
9. I was select Erase Nand and push Start button, offcourse all data in nand (internal storage) destroyed
.. wait until it's done (green blink)
10. After that... I selected menu File>Import Upgrade File and browse Ainol-E4-20130131-qimei-usbburning.zip. And I didn't select any button...
11. Push Start button...then blue color progress is running... wait until it's done 100% with green blink.
12. Unplug the Flame, and Turn Power ON... taste the Jelly Bean...


Regards
 

·
Registered
Joined
·
25 Posts
I turn my Flame primary for Multi Media Player.
So far this AML ROM 0131 (JB 4.2.1) :
- I don't hear sonic boom when the first time play the movie (like Feiyu ROM 0103)
- I quess MTP is unstable (or maybe the ports or the USB cable) when I tried copying VOB file
- Wifi seems slowly (using Connectify, copying movie more than 500MB)
- Auto Rotation fixed
- Mosquito buzz fixed
- Phablet UI

Still rainy in Jakarta and trafic jam on the way back home, so I stuck in office, can't test HDMI yet...

Regards

EDIT :
@ Eriol
- First Loading...ROM fully "internationalized" but I (always do )change the language : EN-USA
- I'm using mostly for Multimedia Player, it's good enough for me right now...
- I don't use Goggle Play
- I think it Rooted
 

·
Registered
Joined
·
25 Posts
Hi dd_yulius

Please, may I ask you a question?

In the step 7. you wrote "Still Power Off Flame, run XXXXXXXX". I'm confused because, previously, in the step 3. you turned-off the tablet and in the step 4. you turned-on again the tablet by pressing "VOL -" and "Power" simultaneously.
So te question is: When the tablet is powered-off? I'm confused

Thank you very much in advance for your attention to this request.

Best Regards

Fernando
Hi Fernando...

I'm sorry...

My mistake... in the step 7. The screen remain black (from step 3 until it reboot )... so I Wrote "Still Power Off Flame"... actually it's still ON and the Flame identified as "WorldCup Device" by Windows...

Thank's for correcting me...


Regards

Yulius
 

·
Registered
Joined
·
25 Posts
android.process.acore pop up error ,i put Contacts.apk into /system/app floder and chmod rw-r--r-- can fixed.sorry for my bad eng.

PS:anyone can fix google play because many many app nothing can found
View attachment 12274
Thank's highotquest... after copy, set rw-r--r-- and reboott... it's work for my skype...

Regards

Yulius
 

·
Registered
Joined
·
25 Posts
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
 

·
Registered
Joined
·
25 Posts
Does that mean you can't flash with the SD or with the USB too? I mean can you flash the official 4.2.1 again with the USB?
@DVB : Yes, I can not flash with internal Recovery... because Vol - and Power doesn't work, I guess it search partition or file "uImage_recovery". IMHO

Before I flashed this ROM, I ever put TWRP "uImage_recovery" into external SDCard, if I pushed those buttons, it run TWRP. But If I used Quick Reboot.apk options "Recovery", it run Feiyu "uImage_recovery".
Yes I can flash official 4.2.1 (again) with PC/Notebook and USB cable plug in

Now I would try to downgrade, I curious about missing internal Recovery...

Regards,

Edit :

@dvb :
I'm sorry, my fault, I can not Flash official 4.2.1. again with USB, when I pushed Vol - and Power buttons, only green robot appeared and Windows didn't find any new hardware...
But the good news is, wait until green robot disappear about 5 minute, then uimage_recovery in ext sdcard will executed...
 

·
Registered
Joined
·
25 Posts
Hi, have you tested the wifi in sleep mode with option "Always on"?
thank you
@alfonzorossi :

Connecting wifi at my office...
First time, Sleep about 2 hours, when awake wifi tried to reconnect
but battery level decrease about 1-2 %

Then I tried sleep less than 2 minute, when awake wifi tried to reconnect


The same result when I connected to Connectify, but I must restart Connectify first


But when I set Flame as Portable Wifi Hotspot and sleep about 5 minutes... hotspot still on


BTW, I let battery level reach 0% then notification power off appeared just a second then Flame turn OFF


Regards,
 

·
Registered
Joined
·
25 Posts
So if you put the uImage_recovery from the ROM you want to flash on the external SD card, can you go into recovery then? If so just flash a stock or feiyu ROM and it will rewrite the nand uImage_recovery also.

Novo 7 Flame running CM10.1 2013-02-02 qm 1.3.2
@Billcnz :
No, I can not go into nand recovey, neither ext sdcard. Because I don't know where I put uimage_recovery.

@highotguest :
Thank's for advice... I'll report later...

EDIT:
"GOD Loves Patience People" (Orang Sabar Disayang Tuhan)

Last time I wasn't patience for waiting proces Vol - and Power so I wrote : "those buttons doesn't work"

Couple minutes ago, I did it again with more patience... TG... it works...
wait until green robot disappeare about 5 minutes then uimage_recovery in my external SDCard executed.

I tried FEIYU and TWRP uimage_recovery, they works...

So I don't have to downgrade into old official ROM ...


Guys... Do you have any idea where I can copy uimage_recovery into nand ?

Regards,
 

·
Registered
Joined
·
25 Posts
Dear all,

My Flame-QM
WIN 7 Home Basic
USB 2.0 port

Upgrade to Official ROM 20130201 from FEIYU 20130110 (4.1.1)

1. Flame is OFF
2. Plug USB cable
3. Open Control Panel > Device Manager
4. Push VOL - & POWER
5. Wait until libusb-win32 device show... (Device Manager)
6. Run ImageBurnTools.exe (I don't run as administrator)
7. File > Import Config File : Config_progress.xml
8. Check Erased NAND & no hub support
9. Click Start
10. When Finish, click Stop
11. Uncheck Erased NAND & no hub support
12. Push Home & Power
13. Wait until libusb-win32 device show... (Device Manager)
14. Import upgrade file : Official ROM.zip
15. When Finish, click Stop
16. UnPlug USB
17. Turn Flame On

Then I did several downgrade, here the result :

uimage_recovery (I used that attached by each ROM and copied to root ext sdcard)

(Don't Plug USB)
0. Turn Flame OFF
1. Vol - & Power
2. Wipe all
3. Apply Update from EXT / sdcard > Custom ROM.zip
4. Wipe all
5. Reboot Flame

EDIT:
The last time, after reboot back to flash menu (Android system recovery <3e>) then I did :
6. Only Apply Update from EXT / sdcard > Custom ROM.zip
7. Reboot Flame

Downgrade to FEIYU 20121030 (4.0.4) - OK but Ext Storage Unmounted

Downgrade to FEIYU 20130103 (4.1.1) - OK

Downgrade to FEIYU 20130110 (4.1.1) - OK

Downgrade to FEIYU 20130130 (4.1.2) - OK but Failed when Reboot

Downgrade to Official 20121012 - Failed while proces

CM 10.1 20130112 - (used TWRP 2.3.3.0) Failed wipe all , except wipe cache, there's no emmc mounted.

Pls, correct me if I'm wrong...

Regards,

EDIT:
I did downgrade again from Official to Feiyu 20130110 (4.1.1), and then flashed to PA 2.99 (pa_elf2-2.99-30GEN2013-143120.zip)... TG... Succesed...
 

·
Registered
Joined
·
25 Posts
Now I'm back to Official ROM 20130201 From PA 2.99 , here the log :

current pc version is: win7
current tool version is: v1.6.2.0128
-----importConfigFiles-----filenameD:\00 ROM\Official\Ainol-E4-20130131-qimei-usbburning\wwww\config_progress.xml
needHub false, for develop,only allow one device
[T 1][21:37:29]: load spl ...
[T 1][21:37:29]: Transfer Complete! total size is 18712 Bytes
[T 1][21:37:38]: load uboot ...
[T 1][21:37:38]: Transfer Complete! total size is 520348 Bytes
[T 1][21:37:44]: test command exec: crc 0x8f800000 520348 4e80a205
[T 1][21:37:44]: command exec: crc 0x8f800000 520348 4e80a205
[T 1][21:37:44]: sendCommandWithReply: crc 0x8f800000 520348 4e80a205 maxCount:30
[T 1][21:37:46]: begin run 8f800000
[T 1][21:37:49]: finish run 8f800000
[T 1][21:37:51]: rematchPortInfo
[T 1][21:37:51]: erase nand, you are in erase mode: nand rom_protect off;nand scrub 0;poweroff
[T 1][21:37:51]: sendCommandWithReply: nand rom_protect off;nand scrub 0;poweroff maxCount:0
[T 1][21:37:52]: rematchPortInfo
[T 1][21:38:06]: rematchPortInfo
[T 1][21:38:07]: rematchPortInfo
[T 1][21:38:08]: rematchPortInfo
[T 1][21:38:09]: rematchPortInfo
needHub true, for product
-----importUpgradeFile-----filenameD:\00 ROM\Official\Ainol-E4-20130131-qimei-usbburning.zip
[T 1][21:39:09]: load spl ...
[T 1][21:39:09]: Transfer Complete! total size is 18712 Bytes
[T 1][21:39:18]: load uboot ...
[T 1][21:39:19]: Transfer Complete! total size is 520348 Bytes
[T 1][21:39:25]: test command exec: crc 0x8f800000 520348 4e80a205
[T 1][21:39:25]: command exec: crc 0x8f800000 520348 4e80a205
[T 1][21:39:25]: sendCommandWithReply: crc 0x8f800000 520348 4e80a205 maxCount:30
[T 1][21:39:26]: begin run 8f800000
[T 1][21:39:29]: finish run 8f800000
[T 1][21:39:32]: command exec:set_chgcur 0
[T 1][21:39:33]: command exec:video dev bl_off
[T 1][21:39:34]: command exec:video dev disable
[T 1][21:39:35]: command exec:sf probe 2
[T 1][21:39:36]: command exec:sf erase 0 1000
[T 1][21:39:37]: command exec:nand rom_protect off
[T 1][21:39:38]: command exec:nand scrub 0
[T 1][21:39:53]: command exec:nand info
[T 1][21:39:54]: command exec:defenv
[T 1][21:39:55]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 1][21:39:57]: command exec:setenv recovery_command --usb_burning
[T 1][21:39:58]: command exec:save
[T 1][21:39:59]: load uimage ...
[T 1][21:39:59]: Transfer Complete! total size is 4704256 Bytes
[T 1][21:40:05]: test command exec: crc 0x82000000 4704256 c875f76e
[T 1][21:40:05]: command exec: crc 0x82000000 4704256 c875f76e
[T 1][21:40:05]: sendCommandWithReply: crc 0x82000000 4704256 c875f76e maxCount:30
[T 1][21:40:07]: command exec:bootm 0x82000000
[T 1][21:40:09]: boot uImage ...
[T 1][21:40:56]: find disk: I:
[T 1][21:40:57]: recoveyCommand: wipe_data prepareCommand:
[T 1][21:40:57]: send command : wipe_data ok!
[T 1][21:41:16]: wipe_data success(wipe_data):eek:k
[T 1][21:41:17]: recoveyCommand: update:update.zip prepareCommand:
[T 1][21:41:58]: copy successed:update.zip
[T 1][21:41:58]: send command : update:update.zip ok!
[T 1][21:44:13]: update:update.zip success(update:update.zip):eek:k
[T 1][21:44:14]: recoveyCommand: shutdown prepareCommand:
[T 1][21:44:14]: send command : shutdown ok!
F:/USB-Burning-tool-v1.6.2.1228/log/02.11.21.44_Ainol-E4-20130131-qimei-usbburning_manual.log
success:1 failed:0 failed postion:

FYI. I tried not to Erase NAND, straighted to Flash ROM... then I stuck in 77% ...

Regards,
 

·
Registered
Joined
·
25 Posts
How you getting into recovery because mine always stuck at android logo?

Sent from my Novo7 Fire using Tapatalk HD
I quess, you had the same situation like I did the first time, be patience... less than 5 minutes... it would enter into Android System Recovery).
And I hope you had inserted uimage_recovery into root ext sdcard... (in my case, FEIYU ROM 0103 or 0110)
After several tested (upgrade and downgrade)... it's olny just couple seconds to show Android System Recovery...
If you still in the same situation, pls try my steps... and pls share...

Regards,
 

·
Registered
Joined
·
25 Posts
I always clear NAND before flashing and I keep no hub support turned on. Clearing and flashing always fails at the beginning (0%) while device is detected in port 1, then it is detected in port 3 and: clearing NAND just does fine, but flashing ROM always fail at 86% (can't detect device). I've noticed at around
% WorldCupDevice is disappearing from my device list, is it normal?
Mine QM (with notebook Win 7 Home Basic), always detected in Port 2 and I used USB 2.0 port. I'm affraid, that's hardware failure... perhaps the cable or USB Port. IMHO.

I just flash again from CM10.1 (4.2.2) to Official 0131...
This is the First Time I Don't Erase Nand...
I've noticed 86% would be made NAND partition and copied update.zip...
Yes libusb-win32 devices > WorldCup Device dissapeared and changed to be new drive in Computer list ( mine I: )
Less than 3 minutes then it goes to 90%...
Again less than 5 minutes to 100% ....
Succesed...

Here my log :
current pc version is: win7
current tool version is: v1.6.2.0128
-----importConfigFiles-----filename
-----importUpgradeFile-----filenameD:\00 ROM\Official\Ainol-E4-20130131-qimei-usbburning.zip
[T 1][16:53:48]: load spl ...
[T 1][16:53:49]: load uboot ...
[T 1][16:53:50]: test command exec: crc 0x8f800000 520348 4e80a205
[T 1][16:53:53]: command exec:set_chgcur 0
[T 1][16:53:54]: command exec:video dev bl_off
[T 1][16:53:56]: command exec:video dev disable
[T 1][16:53:57]: command exec:sf probe 2
[T 1][16:53:58]: command exec:sf erase 0 1000
[T 1][16:53:59]: command exec:nand rom_protect off
[T 1][16:54:00]: command exec:nand scrub 0
[T 1][16:54:16]: command exec:nand info
[T 1][16:54:17]: command exec:defenv
[T 1][16:54:18]: command exec:setenv bootargs ${bootargs} a9_clk_max=600000000
[T 1][16:54:19]: command exec:setenv recovery_command --usb_burning
[T 1][16:54:20]: command exec:save
[T 1][16:54:21]: load uimage ...
[T 1][16:54:22]: Transfer Complete! total size is 4704256 Bytes
[T 1][16:54:28]: test command exec: crc 0x82000000 4704256 c875f76e
[T 1][16:54:28]: command exec: crc 0x82000000 4704256 c875f76e
[T 1][16:54:28]: sendCommandWithReply: crc 0x82000000 4704256 c875f76e maxCount:30
[T 1][16:54:29]: command exec:bootm 0x82000000
[T 1][16:54:31]: boot uImage ...
[T 1][16:55:05]: find disk: I:
[T 1][16:55:06]: recoveyCommand: wipe_data prepareCommand:
[T 1][16:55:06]: send command : wipe_data ok!
[T 1][16:55:26]: wipe_data success(wipe_data):eek:k
[T 1][16:55:27]: recoveyCommand: update:update.zip prepareCommand:
[T 1][16:56:09]: copy successed:update.zip
[T 1][16:56:09]: send command : update:update.zip ok!
[T 1][16:58:17]: update:update.zip success(update:update.zip):eek:k
[T 1][16:58:18]: recoveyCommand: shutdown prepareCommand:
[T 1][16:58:18]: send command : shutdown ok!
F:/USB-Burning-tool-v1.6.2.1228/log/02.18.17.02_Ainol-E4-20130131-qimei-usbburning_manual.log
success:1 failed:0 failed postion:
 

·
Registered
Joined
·
25 Posts
I'd like some advice from someone more skilled.
My Ainol Fire is (hard?) bricked after a failed attempt to install official AML 0201 firmware. Black screen, PC don't recognize, UnbrickTool not working(from SD card).
I found this thread http://www.slatedroid.com/topic/42212-unbrick-amlogic-based-tablets/page__view__findpost__p__477238 especially post #11 and #12 and this http://tinyurl.com/bbc77ya tutorial for Amlogic based devices.
My question is: worth trying?
If the black screen getting warm, it means fire still on. Make sure it's off then plug USB cable into PC / Notebook USB 2.0 port.
Have you tried push Vol + and Power ? or Home and Power ?
 

·
Registered
Joined
·
25 Posts
I successfull instal 4.2.1, my biggest mistake. My flame becomes more and more unstable.
Finally yesterday no charging, no boot, no recovery mode, display looked death. I reinstalled the 4.2.1 with Amlogicburntool again (Ainol-E4-20130201-tima-usbburning.zip) and it works again but till when. I was not able to reinstall 4.1.2 from feiyu back, when i installed from recovery mode the tablet do not boot, nothing happends, i have to reinstall again anad again 4.2.1

Pleassse, i want back to feiju 4.1.2. Does anybody know how. recovery menu do not helps, also not for official/unofficial other previous roms. I also tried with amlogicburntool but not working

Could anybody downgrade 4.2.1 to 4.1.2, please help
Mine QM

After reinstalled the 4.2.1 with Amlogicburntool (Ainol-E4-20130201-tima-usbburning.zip) then Flash to Feiyu 0103 (2013)...:
- Copy uimage_recovery file to External SD-Card
- Power Off Fire / Flame
- Vol - and Power...
- wipe everything then flash Feiyu 0103 (2013) TM/QM
- wipe again then reboot...
- if not work (stuck in Android Logos) , just repeat once
- Power Off Fire / Flame
- Vol - and Power...
- wipe everything then flash Feiyu 0103 (2013)
- wipe again then reboot...
- And It Works for me everytime...

Last Week I did those steps and flashed from Official 0201 (2012) QM to Official 0830 (2012) QM and it worked...

After doing those steps, you can move to other ROM (Feiyu, PA or CM 10) ... Now I'm using CM 10.1 20130227....

Regards
 

·
Registered
Joined
·
25 Posts
you are the best, thanks, what do you suggest, Feiyu, PA or CM 10
Prise to God. You're wellcome.

It's hard to say... there's no perfect ROM...

I like Feiyu ROM 0103 (only)
- no more poping sound and mosquito buzz
- good as multimedia player (using stok movie player and MX Player)
- no issue for 5MP Camera
- I can use Skype 2.8
- as I remember, battery could reach 0 % and fully charge 100 %
- wifi unstable when fire sleep (IMHO, no matter what the wifi option)
- bugs in auto rotation (solved by using other launcher, mine Apex)

I love CT with CM (10 and 10.1) and AOPK (10, I never try 10.1)

Now I'm using 10.1 (20130227) and wait until Happy Easter...

- no more poping sound and mosquito buzz
- good as multimedia player (using MX Player)
- wifi more stable
- I can use Skype 3
- battery could reach 0 % and fully charge 100 %
- unstable camera (IMHO, kernel problem, cause Official ROM 0201 must limited the size option)

Pls correct me if I'm wrong...


Regards,
 
1 - 17 of 17 Posts
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