Hackwerk's Acer Liquid E3 (E380) / ALE3 Topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Made by Hackwerk: Feel totally free to press the Thanks button if you like my work. Took a lot of my time!
Post simple/stupid/IDoNotUnderstand questions in the Q&A subthread (button under thread title) please!
-- THIS TOPIC IS NO LONGER FREQUENTLY UPDATED --
Specifications / Features / Hardware
Full specs (and E3/E380 vs E2/V370) at GSMArena
Model / Name: E380 / Acer Liquid E3 (Duo / Single / Duo PLUS) or "ALE3"
SKU/EAN/UPC: HM.HDZEE.004.412EF4E96413 (Duo, black) / 4713147308262 / 887899533860
(HM.HE2EE.002 = Duo, titanium gold / HM.HE0EE.001 = Single, black / HM.HE1EE.001 = Single, titanium gold / HM.HE3EG.001 = Duo PLUS, black)
CPU/GPU: Mediatek MT6589 1.2GHz Quad-core Cortex-A7 / PowerVR SGX544
ROM/RAM: 4GB (or 16GB in PLUS) / 1GB (or 2GB in PLUS)
Screen: 4.7" IPS LCD, 720 x 1280, 16M (part 6M.HDZH7.001)
Camera back/front: 13MP, 4160 x 3120 (flash, autofocus) / 2MP (flash)
Battery: Model BAT-A10 (1ICP4/58/71), Cell PGF355870HT (Samsung)("Fixed", Li-Polymer, 2000mAh, 3.8V)
Other: MicroSD (to 32GB), Dual (Duo) or Single SIM, a-GPS, DTS Sound (Optional NFC (in PLUS?))
Dimensions: 138x69x9 mm (5.35x2.68x 0.35 inch), 135 g (4.73 oz)
Firmware / Software
Firmware: Android 4.4.2 KitKat (original Android 4.2.2 (Jelly Bean))
Kernel: 3.4.67 [email protected] #1 (20140925)(custom kernels made by cyclon1978!)(cyclon1978 custom kernel with inverted Y-ax for replacement screens)
Build: Acer_AV0K0_E380_1.018.00_EMEA_GEN1 (KOT49H)
Radio/band: MOLY.WR8.W1248.MD.WG.MP.V44.P10 (20140909)(APN 2.094)
Recovery: CWM 6.0.5.0 for E380 by vache -hold Volume Up while powering on-
Acer update history / Changelog
French version of the changelogs by Shreps can be found here at the Acer Club (.fr).
WARNING: When updating root will be removed & recovery/bootlogo/bootanimation will be reset to stock! You can easily restore root by our flash method and restore Link2SD apps etc!
Update 2014-04-11
Build: > Acer_AV052_E380_1.012.00_EMEA_GEN1
APN: > 2.062
Apps: Not checked
Fixes: Unknown
Update 2014-06-06
Kernel: 3.4.5 st3@st3-server #1 (20140530)
Build: > Acer_AV052_E380_1.016.00_EMEA_GEN1
Radio: > MOLY.WR8.W1248.MD.WG.MP.V5.P51 (20140424)
APN: > 2.076
Apps: Google Maps, Acer Customer Experience, ALU, Quick mode, Snapnote, Nidus, Live screen, Swype, Touch Panel FW, Google GMS R6 etc?
Fixes: (thanks to Shreps)
Camera focus a little better. (Totally fixed & fast in latest KitKat update (RC18))
GPS a little better. (Totally fixed & very fast and accurate in latest KitKat update (RC18))
Improve power consumption.
Camera shutter sound – set off as default.
Disable vibrator when taking picture.
Long press menu key to launch setting menu.
Disable hall sensor if flip UI is disabled.
Improve Acer RAPID function.
Improve Float APP performance.
Animation scale change to 0.5x
Battery warning message incorrect (user is asked to remove the battery).
Bluetooth connection dropping issue with BMW series 1 carkit.
Beta/RC 10 (635439223707245731) (thanks to vache)
Android: 4.4.2 KitKat (RC10)
Kernel: 3.4.67 [email protected] 20140813 st3.1407926371
Build: Acer_AV0K0_E380_1.010.00_EMEA_GEN1 (KOT49H)
Radio: MOLY.WR8.W1248.MD.WG.MP.V44.P8 (20140811)
APN: 2.089
Beta/RC 14 (635451389186094510) (thanks to vache)
Android: 4.4.2 KitKat (RC14)
Kernel: 3.4.67 [email protected] 20140828 st3.1409221923
Build: Acer_AV0K0_E380_1.014.00_EMEA_GEN1 (KOT49H)
Radio: MOLY.WR8.W1248.MD.WG.MP.V44.P8 (20140811)
APN: 2.0.93
RC 17 (635464579241492804) (thanks to Shreps)
Android: 4.4.2 KitKat (RC17)
Kernel: 3.4.67 [email protected] 20140915 st3.1410756057
Build: Acer_AV0K0_E380_1.017.00_EMEA_GEN1 (KOT49H)
Radio: MOLY.WR8.W1248.MD.WG.MP.V44.P10 (20140909)
APN: 2.0.93
Update 2014-10-07: Acer KitKat Update (RC18)(635475739172038202)(OLD LINK)
Android: 4.4.2 KitKat (RC18)
Kernel: 3.4.67 [email protected] #1 20140925
Build: Acer_AV0K0_E380_1.018.00_EMEA_GEN1 (KOT49H)
Radio: MOLY.WR8.W1248.MD.WG.MP.V44.P10 (20140909)
APN: 2.0.94
Fixes:
GPS is fixed and now very fast and very accurate!
Camera (focus) is fixed and now fast and sharp!
Google Play Store icons (black background when transparant) is fixed.
?
Update 2015-01-28: Final Acer KitKat Update (RC19)(635580282980063641)
Android: 4.4.2 KitKat (Final)(RC19)
Kernel: ?
Build: Acer_AV0K0_E380_1.004.00_EMEA_GEN1s_A44K_A (KOT49H)
Radio: ?
APN: ?
Fixes:
?
Official
The following are official Acer pages/links, but content IS different on all other languages/regions (so try others)!
Support pages (drivers/manuals/source): NL, Global/US.
USB Driver v1.0 AV052 (2014-03-27) (does NOT work with tools (flashing and dumping etc), as you need PDAnet or VCOM drivers for that (see ROM Dump section))
Kernel Sources v20150126 (4.4.2)
Kernel Sources v20150126 (4.2.2)
Manual (ENG)(Duo) (for other manuals follow 1st link)
Acer Club (FR) Forums (semi-official)
ROM Dump / Partitions / Scatter
When stuck / frozen on boot (bootloop) you can always reset by holding Volume Up & Power for over 12 sec!
Carlivs Tutorial is another good, clear and complete overview of all this!
You CAN NOT dump/read your phone with the official Acer drivers (no virtual COM port)!
I now succesfully used PDANet (See Tools / Drivers), but a lot of people seem to use the VCOM drivers (MT6589 VCOM, MTK Preloader etc.
The only tool (see Tools section) working after a lot of trying (!) for me was (old) SP Flash Tool 3.1344, and sometimes the newest 3.1408, both icw MTK Droid 2.5.3!
Read these 5 great (similar) ROM dump / flash tutorials (or read this tutorial about Android partitions):
Tutorial 1
Tutorial 2
Tutorial 3
Tutorial 4
Tutorial 5
-- SEE POST ATTACHMENT FOR CURRENT SCATTER FILE --
In this table you find the partition name (all EMMC) (as found in the scatter file attached to this post, probably made by MTK Droid Root & Tools (see Tools section)), then the start adress and then the length, all in hex.
(This could also be done by connecting to phone (with USB Debug on) and using ADB: "adb shell cat /proc/dumchar_info")
PRELOADER
0x0 0xc00000
MBR
0xc00000 0x80000
EBR1
0xc80000 0x80000
__NODL_PMT
0xd00000 0x400000
__NODL_PRO_INFO
0x1100000 0x300000
__NODL_NVRAM
0x1400000 0x500000
__NODL_PROTECT_F (EXT4 mount as /protect_f)
0x1900000 0x400000 (or 0xA00000?!)
__NODL_PROTECT_S (EXT4 mount as /protect_s)
0x2300000 0xA00000
__NODL_SECCFG
0x2d00000 0x20000
UBOOT
0x2d20000 0x60000
BOOTIMG
0x2d80000 0x600000
RECOVERY
0x3380000 0x600000
SEC_RO
0x3980000 0x600000
__NODL_MISC
0x3f80000 0x80000
LOGO
0x4000000 0x300000
__NODL_EXPDB
0x4300000 0xA00000
ANDROID (EXT4 mount as /system)
0x4d00000 0x3E800000
CACHE (EXT4 mount as /cache)
0x43500000 0x7E00000
USRDATA (EXT4 mount as /data)(can not read it in SP Flash Tool, because "length does not allign"?!)
0x4b300000 0xB4CF00A8
__NODL_BMTPOOL (can not read it in SP Flash Tool, because "length does not allign"?!)
0xffff00a8 0x1500000
ROM Installing / Updating
Basic instructions to update your phone (if not automatically Over The Air (OTA)) with a ROM ZIP using a recovery:
If you have the SP Flash Tool (see Tools), make a backup with that too
Install CWM (or any other custom recovery like Carliv's CTR or TWRP if available for E380)(see Root by Flash)
Download and unzip the ROM update (see Acer Update History and watch new posts)
Copy the FixPack-B.zip to SD card
(Re)Boot into recovery
Make a full backup in recovery (to SD)
Flash the FixPack-B.zip from recovery
Reboot & enjoy the new ROM / updated Android!
Root by flash (preferred method)
WARNING: USE AT YOUR OWN RISK, THIS CAN BE DIFFICULT OR EVEN DANGEROUS!!!
When stuck / frozen on boot (bootloop) you can always reset by holding Volume Up & Power for over 12 sec!
Carlivs Tutorial is another good, clear and complete overview of all this!
Steps 0-4 are to be found explained more thouroughly and with images, in the tutorials in the ROM Dump section. Read them. Read them well!
All tools can be found in the Tools section.
Also, a short (better?) version by Shreps can be found here (or check this ChinaPhoneArena one).
0) Install drivers (see Tools) with a good USB virtual COM port emulation! Most simple is to install PDANet maybe, but lot of people seem to use so called VCOM drivers / MT6589 VCOM / MTK Preloader etc. Other option is the MTK USB All Developer drivers. Make sure connection is OK, and MTK Droid works (when phone is on)!
1) Create scatter file or use the one attached to this post.
2) Read back (stock) recovery (or all) partitions with (old) SP Flash Tool 3.1344 using scatter from 1, or download my stock recovery img here.
3) Download CWM 6.0.5.0 by vache or Carliv Touch Recovery CTR (2.7 for JB, 3.0 for KK) (thanks to vache/Shreps for CWM, thanks to Carliv for CTR!)(or make your own by MTK Droid altering stock recovery image);
4) "Download" (to phone) the custom recovery with (old) SP Flash Tool 3.1344 using scatter from 1, or use mine.
5a) Copy SuperSU zip to SD card, and boot your phone into CWM/Carliv recovery (hold volume up and turn phone on), and then Install zip from SD > install SuperSU.
5b) Te keep your custom CWM: Install SuperSU immediately after boot, and use File / Root Explorer to delete file ".. recovery .." in System folder before booting again!
6) YOU ARE ROOTED!
7) Install BusyBox (see Tools section)
WARNING: USE AT YOUR OWN RISK, THIS CAN BE DIFFICULT OR EVEN DANGEROUS!!!
Root by app
WARNING: ALL METHODS AT YOUR OWN RISK (NOT TROJAN OR MAL-/SPYWARE CHECKED)!!!
You can always first check the Lifehacker Always Actual Root Guide.
Working (confirmed):
Kingo Root APK / 1.5.1.2996 PC
May be working / Not tested:
KingRoot 5.1.0 APK / 3.5.0.1157 PC (MAY BE UNSAFE)
iRoot 3.3.6 APK / 1.8.8 PC by XINYI Network / Mgyun (formerly VRoot)(WORKING BEFORE UPDATE TO KITKAT!)
Root Genius 2.2.84 APK / 3.1.7 PC by Shuame
Baidu Root / MROOT
Voodoo OTA Rootkeeper 2.0.3 (protects root on rooted phones)(WORKING BEFORE UPDATE TO KITKAT!) (Or use SuperSU Pro (paid)!)
NOT (yet) working (anymore)(confirmed):
Please message me your own test results and additions!!!
WARNING: ALL METHODS AT YOUR OWN RISK (NOT TROJAN OR MAL-/SPYWARE CHECKED)!!!
Developing / Custom ROM's
MyROM (4.0.037)(just search thread for newer!) by our friend cyclon1978 (Best rated custom ROM yet!)
CyanogenMod 10.1 for E3 (ported from UMI X2)!
MIUI v6 for E380 by Kenji Zefaneo Hanson, now at version 4.12.28!
MIUI v5 for ALE3 by Artha Bedul, now at version 4.8.29!
EMUI by Artha Bedul, now at version 3.0 R2!
Lollitop version 2 by Awand Mbengi (4.4.2 so only cosmetic 5.01!)
LEWA for E380 by Artha Bedul;
Androium 4.2.0 for E3 by Matx;
4PDA (Russian) thread with customs like MIUI4 and Sony Xperia C (AT YOUR OWN RISK);
FrAndroid (French) thread with customs (cosmetic/themed) (AT YOUR OWN RISK);
Your custom ROM for the E3 here soon?
Kernel sources in the Official section!!!
Tools / Drivers / Fixes / Hacks
Kernel sources can be found in the Official section!!!
Drivers
Google 'Naked' Drivers (see next subsection or Google them)
MTK USB All developer drivers (0.9.2 / 9.2.1)(WATCH OUT FOR VIRUSSES/TROJANS!)
PDANet (4.19)
Google for VCOM drivers / MT6589 VCOM / MTK Preloader etc. (All the same old v 1.1123.0)
Official Acer drivers (see link in first part of post)(probably wont always work, so deinstall or do not use those!)
Google Tools (ADB, Fastboot & Google Naked Drivers
Minimal ADB & Fastboot (1.4.2)(ADB, Fastboot)
15 Seconds ADB Installer (1.4.3)(ADB, Fastboot & Drivers)
Official Google Android SDK (r25.2.3)(Choose "Command line tools only")(ADB, Fastboot & Drivers etc. etc.)(Tutorial here)
Tools
MTK2000 is a great MediaTek-hack site with frequent updates of SP/MTK Flash Tool and MUCH more for MTK!
----- MediaTek Tools -----
SP Flash Tool / Smart Phone Flash Tool (v(5.)1708)(MT65xx)(now also Linux!)(First try 3.1344 or older!)
MTK Flash Tool (v5.1624.00)(MT62xx)
MTK Droid Root & Tools (2.5.3)(create scatter (datamap) file, flash etc.)
MTK Rom Studio (1.1.77.301)(by Linerty)(please use Google)
Multiple MTK (Engineer) Apps / Tools on Google Play
----- Universal Tools -----
Google Apps (Open GApps) packages
Xposed Framework (2.7 for KK)(higher/newest versions for newer custom Android ROMs)
SuperSU (2.79)(Download the ZIP and install ZIP from from sdcard in CWM to root)
BusyBox (49)
Titanium Backup (8.0.0)(backup/restore, and remove or move apps, also system apps)
FDroid App Market (non Google approved Apps, like AdAway add blocker!)(COULD BE DANGEROUS)
Fixes
No current fixes, as all big problems seem fixed in KitKat (RC19)(see Updates section)...
PS. cyclon1978 custom kernel with inverted Y-ax for replacement screens in first part of this post!
Hacks
A MEGA load of hacks/mods available in Xposed Framework, so install it and look for Xposed Modules doing what you want!
Change IMEI of Phone 1 or Phone 2 easily with lots of MTK apps from Google Play store! WARNING: MAY BE VERY ILLEGAL IN YOUR COUNTRY! (Is NOT in mine, NL)
To boot into recovery/fastboot mode, hold Volume Up while powering device on.
To boot into Factory (Test) mode, hold Volume Down while powering device on.
To make Acer's drivers also recovery/fastboot compatible, add this line to your "android_winusb.inf" files in the maps in submap "drivers" (and then install/update drivers in Windows Device Manager): %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
Repartition and extend space to SD with Meteos App here or here (root required)(more partition info here)(not tested yet)
Use external SD for apps with the famous INT2EXT script or check all options like App2SD, Mount2SD, Data2SD etc
PS. cyclon1978 custom kernel with inverted Y-ax for replacement screens in first part of this post!
More?
-- THIS TOPIC IS NO LONGER FREQUENTLY UPDATED --
Made by Hackwerk: Feel totally free to press the Thanks button if you like my work. Took a lot of my time!
Post simple/stupid/IDoNotUnderstand questions in the Q&A subthread (button under thread title) please!
Special thanks for testing and assisting me go to (random order):
Carliv (Touch Recovery), tiliarou, d3nnisd, Dakloos88, Shreps, vache, cyclon1978
I've managed to make a backup using MTK droid and root tool. hackwerk, it seems you are getting ahead of me now can you post your recovery if it's working ? thanks !
Is it safe to install and activate Xposed framework on the E3 ?
I got a notification today about a 8.23 Mb update ! But there is no changelog anywhere and I don't want to install it yet...
Anyone got it ?
tiliarou said:
I've managed to make a backup using MTK droid and root tool. hackwerk, it seems you are getting ahead of me now can you post your recovery if it's working ? thanks !
Is it safe to install and activate Xposed framework on the E3 ?
I got a notification today about a 8.23 Mb update ! But there is no changelog anywhere and I don't want to install it yet...
Anyone got it ?
Click to expand...
Click to collapse
Yes I already have a datamap / scatter file (from MTK Droid) and used it succesfully to dump / backup all blocks to images (recovery.img boot.img android.img etc) on my non-rooted phone! (however USERDATA block fails in SP Flash Tool, and I do not know the end address of the ROM thus cannot dump the last block (__NODL_BMTPOOL))
Made a CWM custom recovery with the Official CWM Builder online, but the new output recovery was larger than my stock input one!?
Big problem for now, as I cannot fit it in the current recovery space?!
Xposed I do not know? However I strongly advise everyone NOT to install / run programs or apps or packages etc which are not on XDA or are closed source! There's a LOT of virussing / spying / trojanning going on in this world.
The official Acer update is only (as far as I found out);
1) Update of the build from Acer_AV052_E380_1.007.00_EMEA_GEN1 > Acer_AV052_E380_1.012.00_EMEA_GEN1
2) Update of the APN version from APN 2.053 > APN 2.062
I colored the 2 changes green in my FP.
So just do it, its fine I guess, and we will get Android 4.4 Kit Kat soon anyways...
Ok, and do you think that with root I would be able to retrieve this last block ?
I can confirm that even after reboot the root is there ! I used Voodoo OTA rootkeeper to make the OTA update, just to be safe and it managed after 2 restores to put back root. I don't know if it was needed.
I don't see any change with this update, just a traduction error corrected in the settings menu (flip cover wake up)...
Would be nice to have a changelog from Acer just to know !
I can also confirm that Xposed Framework is perfectly working on this phone.
tiliarou said:
Ok, and do you think that with root I would be able to retrieve this last block ?
I can confirm that even after reboot the root is there ! I used Voodoo OTA rootkeeper to make the OTA update, just to be safe and it managed after 2 restores to put back root. I don't know if it was needed.
I don't see any change with this update, just a traduction error corrected in the settings menu (flip cover wake up)...
Would be nice to have a changelog from Acer just to know !
I can also confirm that Xposed Framework is perfectly working on this phone.
Click to expand...
Click to collapse
Size of the last 2 partitions is now known and added but the reason it cannot be read by SP Flash Tool is that the sizes are not a multiple of 512 or so!?
Yeah baby! Great news!
I managed to install the ClockworkMod Recovery (rua1 autoCWM 5.5.0.4) made by the MTK Droid Root & Tool, and Downloading it to my phone in the older SP Flash Tool 3.1344!
After that of course installed SuperSU and we are ROOT, by a simpel/safe/clean method!
Links and stuff are in the first post.
Problems/ToDo now:
1) This CWM is removed after a normal (re)boot and replaced by the stock one (Android system recovery 3e). How!? And how to stop this?!
2) Newer CWM (6.0.4.7) like the one the online CWM Builder makes for me (altering my stock image) seems to big for the partition
3) Custom ROM making (CyanogenMod!!!), but let's wait for 4.4 Kit Kat and the sources of that, which will be available in the next months.
Data to Ext SD
We need to extend space to our external SD card, as the internal phone memory is not huge.
However I really really cannot see all differences with pro's and con's anymore between all options, so please help me!
What should we do, with this rooted stock Acer ROM (Android 4.2.2)(with EXT4 partitions and CWM recovery)?
1) Use one of the famous scripts INT2EXT, Data2EXT/D2EXT, Mount2SD/M2SD, Apps2SD/A2SD etc. etc.
1b) For INT2EXT we need Init.d support, so whats the best way to add that? An App like Init.d Toggler or Universal Init.d or so? (4.4 support would be nice!)
2) Just use simple symlinks with Link2SD/L2SD or Apps like FolderMount etc
3) Repartition and make data partition on SD, using Meteos etc
4) Use one of the many Apps to move Apps, like Titanium Backup etc.
What CAN, and SHOULD we try/use? Please advise me?
Have you already seen this behaviour of a custom recovery reverting back to stock after reboot ?
I've always used link2sd with my previous phone, so far I put my apps on sd using the android built-in option on my E3, because I haven't reached the internal storage limit yet...
Are we only 2 having this phone ?^^
tiliarou said:
Have you already seen this behaviour of a custom recovery reverting back to stock after reboot ?
I've always used link2sd with my previous phone, so far I put my apps on sd using the android built-in option on my E3, because I haven't reached the internal storage limit yet...
Are we only 2 having this phone ?^^
Click to expand...
Click to collapse
From what I can see now, you should install SuperSU immediately the first time in CWM, and THEN reboot. SuperSU asks for permission for Acer system update and you should deny that. CWM will then stay. However, you could also update (to 4.4 later) and then flash the CWM again of course.
Yeah the phone is JUST released, so we are the first. Probably some more people will join in the next months!
hackwerk said:
Hackwerk's Acer Liquid E3 (E380) / ALE3 Topic
Specifications / Features / Hardware
Full specs (and E3/E380 vs E2/V370) at GSMArena
Model / Name: E380 / Acer Liquid E3 (Duo) or "ALE3"
SKU/EAN/UPC: HM.HDZEE.004.412EF4E96413 (Duo, Black) / 4713147308262 / 887899533860
(HM.HE2EE.002 = Duo in Silver / HM.HE0EE.001 = Single in black / HM.HE1EE.001 = Single in silver)
CPU/GPU: Mediatek MT6589 1.2GHz Quad-core Cortex-A7 / PowerVR SGX544
ROM/RAM: 4GB (or 16GB) / 1GB (or 2GB)
Screen: 4.7" IPS LCD, 720 x 1280, 16M
Camera back/front: 13MP, 4160 x 3120 (flash, autofocus) / 2MP (flash)
Other: Li-Po 2000mAh battery (fixed), MicroSD (to 32GB), Dual (Duo) or Single SIM, a-GPS, DTS Sound, Optional NFC
Dimensions: 138x69x9 mm (5.35x2.68x 0.35 inch), 135 g (4.73 oz)
Firmware / Software
Firmware: Android 4.2.2 (Jelly Bean)(4.4 Kit Kat available 2014 Q2)
Kernel: 3.4.5 [email protected] #1 (20140227)
Build: Acer_AV052_E380_1.012.00_EMEA_GEN1
Radio/band: MOLY.WR8.W1248.MD.WG.MP.V5.P47 (20140226)(APN 2.062)
Recovery: rua1 autoCWM 5.5.0.4 for E380 (custom by MTK Droid, see Tools section)(stock: Android system recovery 3e)(hold Volume Up while powering on)
ROM Dump / Partitions / Scatter
You CAN NOT dump/read your phone with the official Acer drivers (no virtual COM port)!
I now succesfully used PDANet (drivers), but a lot of people seem to use the VCOM drivers (MT6589 VCOM, MTK Preloader etc.: All the same old v 1.1123.0).
The only tool (see Tools section) working after a lot of trying (!) for me was (old) SP Flash Tool 3.1344, and sometimes the newest 3.1408, both icw MTK Droid 2.5.3!
Read these 5 great (similar) ROM dump / flash tutorials:
Tutorial 1
Tutorial 2
Tutorial 3
Tutorial 4
Tutorial 5
In this table you find the partition name (as found in my created scatter file made by MTK Droid Root & Tools (see Tools section)), then the start adress and then the length, all in hex.
PRELOADER
0x0 0xc00000
MBR
0xc00000 0x80000
EBR1
0xc80000 0x80000
__NODL_PMT
0xd00000 0x400000
__NODL_PRO_INFO
0x1100000 0x300000
__NODL_NVRAM
0x1400000 0x500000
__NODL_PROTECT_F (EXT4 mount as /protect_f)
0x1900000 0x400000
__NODL_PROTECT_S (EXT4 mount as /protect_s)
0x2300000 0xA00000
__NODL_SECCFG
0x2d00000 0x20000
UBOOT
0x2d20000 0x60000
BOOTIMG
0x2d80000 0x600000
RECOVERY
0x3380000 0x600000
SEC_RO
0x3980000 0x600000
__NODL_MISC
0x3f80000 0x80000
LOGO
0x4000000 0x300000
__NODL_EXPDB
0x4300000 0xA00000
ANDROID (EXT4 mount as /system)
0x4d00000 0x3E800000
CACHE (EXT4 mount as /cache)
0x43500000 0x7E00000
USRDATA (EXT4 mount as /data)(can not read it in SP Flash Tool, because "length does not allign"?!)
0x4b300000 0xB4CF00A8
__NODL_BMTPOOL (can not read it in SP Flash Tool, because "length does not allign"?!)
0xffff00a8 0x1500000
Official
The following are official Acer pages/links, but content IS different on all other languages/regions (so try others)!
Product page (UK)
Support page (UK)(drivers/source/manuals)
USB Driver v1.0 AV052 (do NOT work with tools (flashing and dumping etc), as you need PDAnet or VCOM drivers for that (see ROM Dump section))
Kernel Sources v20140307 (4.2.2)
Manual (ENG)(Duo)
Rooting (CWM > SuperSU)
WARNING: USE AT YOUR OWN RISK, THIS CAN BE DIFFICULT OR EVEN DANGEROUS!!!
Steps 0-4 are to be found explained more thouroughly and with images, in the tutorials in the ROM Dump section. Read them. Read them well!
All tools can be found in the Tools section.
0) Install drivers with a good USB virtual COM port emulation. Most simple is to install PDANet (4.15), but lot of people seem to use the VCOM drivers / MT6589 VCOM / MTK Preloader etc. (All the same old v 1.1123.0). Make sure connection is OK, and MTK Droid works (when phone is on)!
1) Create scatter file or use mine.
2) Read back (stock) recovery (or all) partitions with (old) SP Flash Tool 3.1344 using scatter from 1, or download my stock recovery img here.
3) Let MTK Droid alter the recovery image and make a custom CWM one of it.
4) Download (to phone) the custom CWM recovery with (old) SP Flash Tool 3.1344 using scatter from 1, or use mine.
5) Copy SuperSU zip to SD card, and boot your phone into CWM recovery (hold volume up and turn phone on), and then Install zip from SD > install SuperSU. Do it the first time in CWM, because a reboot without root REVERTS recovery to stock (safety by Acer?!)!
6) YOU ARE ROOTED!
7) Install BusyBox (see Tools section)
WARNING: USE AT YOUR OWN RISK, THIS CAN BE DIFFICULT OR EVEN DANGEROUS!!!
Root Tools (Simple / OneClick)
WARNING: ALL METHODS AT YOUR OWN RISK (NOT TROJAN OR MAL-/SPYWARE CHECKED)!!!
Working (confirmed):
Kingo (1.2.1 used)(at your own risk, closed source and controversial)
Voodoo OTA Rootkeeper (keep root after updates, for rooted phones)
May be working / Not tested:
CF Auto Root
Bin4ry v33
OneClickRoot
Universal Rooter 1.1
SRS Root
VRoot
ERoot
Not (yet) working/modded (confirmed):
Framaroot (E2/V370 etc etc)(1.9.1 tested)
MotoChopper = MT6589_rooter = MT6589_rooting_pkg by Dan Rosenberg (@djrbliss)(universal MT6589)(1.1 tested)
SuperOneClick
E350 Liquid Gallant method
Please message me your own test results and additions!!!
WARNING: ALL METHODS AT YOUR OWN RISK (NOT TROJAN OR MAL-/SPYWARE CHECKED)!!!
Developing / Custom ROM's
None yet, but we hope for a CyanogenMod and ClockworkMod Recovery, although this MediaTek support is not expected :crying:
But due to the fact that the E2 and E3 are almost the same (a part from the screen and cams), we hope for mods/ports of for instance:
E2 SC0RPION ROM
E2 JellyXperia ROM
E2 MIUI 5 ROM
Your custom ROM for the E3 here soon?
Kernel sources in the Official section!!!
Tools / Fixes / Hacks
Kernel sources can be found in the Official section!!!
Tools
MTK2000 is a great MediaTek-hack site with frequent updates of SP/MTK Flash Tool and more!
SP Flash Tool / Smart Phone Flash Tool (v3.1408.00)(super tool for MT65xx phones!)(new code/layout from 3.1352 up, and for recovery flash you MUST use older 3.1344 etc!!!)
MTK Flash Tool (v5.1320)(super tool for MT62xx phones!)
MTK Droid Root & Tools (2.5.3)(great tool, to create scatter (datamap) file (Succeeded! See ROM Dump section) etc.)
MTK Rom Studio (1.1.77.266)(by Linerty)
Multiple MTK (Engineer) Apps / Tools on Google Play, like Mobileuncle MTK Tools (2.9.9)
Xposed (2.5.1) Framework (modify ROM without flashing)
Titanium Backup (6.1.5.4)(backup/restore, and remove or move apps, also system apps)
SuperSU (1.94)(install via CWM to root phones etc)
BusyBox (11 / 1.22.1)
Fixes
Bad GPS fix with MobileUncle MTK Tools (or MT GPS EPO Fix)
Camerafix (by ventus00): Drag Camera app to homescreen into "App info" which brings you to "Gallery" app info. Press Force stop > Clear data. What fixed the cam was pressing "Clear defaults" under "Launch by default".
Hacks
To boot into recovery/fastboot mode, hold Volume Up while powering device on.
To make Acer's drivers also recovery/fastboot compatible, add this line to your "android_winusb.inf" files in the maps in submap "drivers" (and then install/update drivers in Windows Device Manager): %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
Repartition and extend space to SD with Meteos App here or here (root required)(more partition info here)(not tested yet)
Use external SD for apps with the famous INT2EXT script or check all options like App2SD, Mount2SD, Data2SD etc
More?
To Do / Problems
Which script/app to use for data > ext SD? See post #6 etc!
Which method to use to get init.d support?
Custom recovery ClockworkMod RUNNING (5.5.0.4 with MTK Droid) but the CWM custom one from CWM Builder online) seems to large :/
Besides the CWM, build and test custom TWRP Recovery, and Carliv Touch Recovery.
No custom ROM like CyanogenMod yet :/
Made by Hackwerk, and feel totally free to press the Thanks button if you like my work. It took a lot of my spare time!
(special thanks to tiliarou for testing, and d3nnisd for the first/old thread)
Click to expand...
Click to collapse
Porting custom roms from Acer Liquid E2 to Acer Liquid E3 it's very simple.
All you need to do is to take boot.img (kernel) from your stock rom and then if you want I can help you to port kernel to your e3
marcogiannetta said:
Porting custom roms from Acer Liquid E2 to Acer Liquid E3 it's very simple.
All you need to do is to take boot.img (kernel) from your stock rom and then if you want I can help you to port kernel to your e3
Click to expand...
Click to collapse
Welcome Marco and thanks!
Our ALE3 stock boot.img and the kernel source (both still 4.2.2) are already available and I really welcome you to help us.
Although we are also very much waiting for the 4.4 Kit Kat release which is almost there (Q2)!
Ps. Is it (still) hard/impossible to get a CyanogenMod (which I LOVE and am very used to) clone running on our ALE3 (because of MediaTek MT6589?)?
Unlock
Can you tell me if any of the above will unlock my new E380 ? Or do I need to wait for a custom ROM to be ported ?
Many thanks.
hackwerk said:
Welcome Marco and thanks!
Our ALE3 stock boot.img and the kernel source (both still 4.2.2) are already available and I really welcome you to help us.
Although we are also very much waiting for the 4.4 Kit Kat release which is almost there (Q2)!
Ps. Is it (still) hard/impossible to get a CyanogenMod (which I LOVE and am very used to) clone running on our ALE3 (because of MediaTek MT6589?)?
Click to expand...
Click to collapse
I own a Acer Liquid E2 and I ported CM11 from Wiko Stairway (MT6589) to my phone thanks to some patches and libs. At the moment developers have to fix camera,bluetooth, hw acceleration and some little bugs.
I can port this roms but I haven't got a Acer Liquid E3 so I can't test them.
EDIT: I'm gonna port these kernels, but I can't upload those roms because of my bad connection
So all you had to do is to download the roms, replace my kernel in the rom and replace libs with stock libs (they are located in system/lib/modules )
Jellyxperia kernel:
https://mega.co.nz/#!8ZVHzTwJ!kQO_A9AJdLx2Mz3u1ctZ5-IhuEUZvFJOb-SxG9LuyJA
MIUI kernel
https://mega.co.nz/#!gJtQVSCQ!5IdxGHxOobBfGblp8Dd7AUM03prNScxaIudSXT5879E
Try and tell me if I succeed
As long as key features of our (ALE3) phone are not supported in custom ROMs, like camera, I will not (try to) flash/test or modify them.
I am not a developer, and I really demand basic features like making a picture
And again, maybe we should start fukkin around when 4.4 (and sources of 4.4?) are released!
hackwerk said:
As long as key features of our (ALE3) phone are not supported in custom ROMs, like camera, I will not (try to) flash/test or modify them.
I am not a developer, and I really demand basic features like making a picture
And again, maybe we should start fukkin around when 4.4 (and sources of 4.4?) are released!
Click to expand...
Click to collapse
You didn't understand me, those bugs (like camera) are only in CM11.
MIUI, Scorpions and Jellyxperia work fine
pwwuk said:
Can you tell me if any of the above will unlock my new E380 ? Or do I need to wait for a custom ROM to be ported ?
Many thanks.
Click to expand...
Click to collapse
What exactly do you mean by unlock? Rooting? Pattern/PIN lock? SIM / network lock?
Rooting:
See the first post (FP) / topic start (TS) if rooting is what you want and try the simple but obscure Kingo method or flash CWM and install SuperSU etc (complicated but trusted / universal method).
SIM / Network lock:
If rooted, you can install all apps (signed and unsigned) and do everything in your phone you want to, so install a SIM unlock app (OWN RISK), or use a complicated but more trusted file edit method (OWN RISK). A good app option seems to be the famous MobileUncle MTK Tools (see Tools section in FP), as it has a Permanent Unlock option for both SIMs in the Engineer Mode (MTK)!
PIN / Pattern:
A million methods via ADB, or (CWM) recovery etc, like these, but just Google man!
marcogiannetta said:
You didn't understand me, those bugs (like camera) are only in CM11.
MIUI, Scorpions and Jellyxperia work fine
Click to expand...
Click to collapse
So you have CM11 running, but with these problems (because of the MT6589), on your ALE2?
And you did (or also) run customs SC0RPION, JellyXperia and MIUI (only/all three?) and without big problems (so I can probably use those on daily basis)?
Which one do you like best? SC0RPION seems most updated, newest and best fitting (ALE2 based), MIUI seems older and simpler, and Jelly is based on an other phone?!
I do not understand how I would be able to port them to our ALE3. Can you explain it more elaborate please?
hackwerk said:
What exactly do you mean by unlock? Rooting? Pattern/PIN lock? SIM / network lock?
Rooting:
See the first post (FP) / topic start (TS) if rooting is what you want and try the simple but obscure Kingo method or flash CWM and install SuperSU etc (complicated but trusted / universal method).
SIM / Network lock:
If rooted, you can install all apps (signed and unsigned) and do everything in your phone you want to, so install a SIM unlock app (OWN RISK), or use a complicated but more trusted file edit method (OWN RISK). A good app option seems to be the famous MobileUncle MTK Tools (see Tools section in FP), as it has a Permanent Unlock option for both SIMs in the Engineer Mode (MTK)!
PIN / Pattern:
A million methods via ADB, or (CWM) recovery etc, like these, but just Google man!
Click to expand...
Click to collapse
Many thanks,
Yes I meant network unlock (use a phone on an alternate network to that to which it is locked)
Three (UK) have kindly agreed to unlock without charge .. So I just need to root as I need to port some sideloaded apps accross from an old HD.
All the best
Peter
hackwerk said:
So you have CM11 running, but with these problems (because of the MT6589), on your ALE2?
And you did (or also) run customs SC0RPION, JellyXperia and MIUI (only/all three?) and without big problems (so I can probably use those on daily basis)?
Which one do you like best? SC0RPION seems most updated, newest and best fitting (ALE2 based), MIUI seems older and simpler, and Jelly is based on an other phone?!
I do not understand how I would be able to port them to our ALE3. Can you explain it more elaborate please?
Click to expand...
Click to collapse
CM11 is still buggy on mt6589, not only on my phone.
I tried those roms and they are bugfree except jellyxperia which is not multilanguage, in fact only english and chinese.
Honestly I prefer Sc0rpion rom because of its performance/battery life.
About porting roms, you should follow these steps:
1 - Download rom you want to port
2 - On your stock rom, go to system/lib/modules and copy all the libs inside this folder on your sd card
3 - Open custom rom zip and replace custom libs (in the same folder) with your libs
4 - Now replace boot.img of the rom with the ported boot.img which I gave you (i.e. ALE3Jellyxperia)
5 - Make a backup of your stock rom, Wipe data/factory reset and flash the zip in CWM
Yesterday I forgot Sc0rpion kernel, so you can download it here:
https://mega.co.nz/#!1Fl1FKbC!-tTMxyfDJl3_GrmvnCdYywXkutZv3trvxl4XyyA_r6k
Please tell me if you have any problem
marcogiannetta said:
CM11 is still buggy on mt6589, not only on my phone.
I tried those roms and they are bugfree except jellyxperia which is not multilanguage, in fact only english and chinese.
Honestly I prefer Sc0rpion rom because of its performance/battery life.
About porting roms, you should follow these steps:
1 - Download rom you want to port
2 - On your stock rom, go to system/lib/modules and copy all the libs inside this folder on your sd card
3 - Open custom rom zip and replace custom libs (in the same folder) with your libs
4 - Now replace boot.img of the rom with the ported boot.img which I gave you (i.e. ALE3Jellyxperia)
5 - Make a backup of your stock rom, Wipe data/factory reset and flash the zip in CWM
Yesterday I forgot Sc0rpion kernel, so you can download it here:
https://mega.co.nz/#!1Fl1FKbC!-tTMxyfDJl3_GrmvnCdYywXkutZv3trvxl4XyyA_r6k
Please tell me if you have any problem
Click to expand...
Click to collapse
Thanks a lot but after my whole journey (see FP) I just finished configging my phone and am very happy at the moment.
I will try it later, but maybe 4.4 (will be released for us, inc kernel source) will be my next step, and I hope CM11 4.4 customly made from/for this!
How did you make these boot.img images for our ALE3 (from ALE2) btw?
hackwerk said:
Thanks a lot but after my whole journey (see FP) I just finished configging my phone and am very happy at the moment.
I will try it later, but maybe 4.4 (will be released for us, inc kernel source) will be my next step, and I hope CM11 4.4 customly made from/for this!
How did you make these boot.img images for our ALE3 (from ALE2) btw?
Click to expand...
Click to collapse
I unpacked ALE2 and ALE3 kernel. Then I packed a kernel with the ramdisk of the ALE2 and the zImage of the ALE3. That's all
Hello XDA, longtime reader, first time poster.
I tried flashing a custom ROM the other day, but something went wrong, and I now have a device that bootloops (unlocked screen, SONY logo, followed by a "the software update failed" message). I think the cause of all of this came from a few missing drivers that Flashtool/Windows 7 didn't install properly. I'm not sure if this matters, but this happened after trying to update to the latest stock nougat firmware (downloaded via Xperifirm) from a custom 6.0.1 ROM.
I went through as many solution threads as possible, but I'm still having trouble. The last thing I did just before this post was create an ftf via Flashtool, added "41.fsc" script when asked, prepared flash with full wipe/no exclusions, connected phone to USB via Flash Mode, selected F83XX when prompted for device, and this was the log I received...
29/021/2017 00:21:58 - INFO - Device connected in flash mode
29/021/2017 00:21:59 - INFO - Opening device for R/W
29/022/2017 00:22:00 - INFO - Reading device information
29/022/2017 00:22:00 - INFO - Phone ready for flashmode operations.
29/022/2017 00:22:00 - INFO - Opening TA partition 2
29/022/2017 00:22:00 - INFO - Start Flashing
29/022/2017 00:22:00 - INFO - No loader in the bundle. Searching for one
29/022/2017 00:22:44 - INFO - No matching loader found
29/022/2017 00:22:44 - WARN - No loader found or set manually. Skipping loader
29/022/2017 00:22:44 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Bootloader status : ROOTED
29/022/2017 00:22:44 - INFO - Max packet size set to 4M
29/022/2017 00:22:44 - INFO - USB buffer size set to 512K
29/022/2017 00:22:54 - INFO - Parsing boot delivery
29/022/2017 00:22:54 - INFO - Found a template session. Using it : C:\Users\[name]\.flashTool\firmwares\prepared\41.fsc
29/022/2017 00:22:54 - INFO - Set loader configuration : [00 01 00 00 00 0C]
29/022/2017 00:22:54 - INFO - Flashing finished.
29/022/2017 00:22:54 - INFO - Please unplug and start your phone
29/022/2017 00:22:54 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Extra information...
PC
- Windows 7 64-bit
- Flashtool 0.9.23.2 installed
- As far as I know, every driver I need has been downloaded and installed (Sony's website, Flashtool-drivers.exe)
(↑ "Sony sa0115 ADB Interface Driver" under Device Manager reads "This device cannot start. (Code 10)", if that makes any difference)
- Xperia Companion doesn't detect my phone, so I can't use their "software repair" option
Phone
- F8332
- Bootloader unlocked
- *Backup TA missing*
- Device rooted
- TWRP 3.1.1-0 installed
- Android 6.0.1 (firmware unknown)
Files
- Latest Nougat firmware (F8332_Customized FR_1305-9679_41.2.A.7.76_R1D) -- folder only (ftf can be created anytime, just need to know what to keep/exclude. I've been seeing different answers regarding when to add "41.fsc" to ftf (before/after flashing, or adding at all), and excluding .sin files before flashing, so if anyone has a definite answer to these, I'd really appreciate it.)
Otherwise, if none of that matters and the problem lies somewhere else, I'm all ears.
Thank you in advance.
@simpleflips
wow - your post should stand out as a prototype for HOW TO ASK FOR HELP!
I had the same problem recently when trying to flash my F8331 under Windows 10. Did not try Linux on the same machine since there are some issues with Mono here.
My drivers where not giving me any clues (PC-Manager, logging under Windows?).
So I dug out my spare laptop (Win 7 bitness?): installed the XZ-driver and it worked there after a full wipe in TWRP (I had encrypted the device and TWRP did not take the key properly).
You can try the drivers I link in my Guide.
Under both Windows installations I had no problems with adb and fastboot.
So I can only guess that my "solution" was the full wipe or some unkwon differences in driver magic between the notebooks used.
@DHGE
Apologies for the delay, thank you for the words and response. I should've noted that before my OP and bootloop, I tried to flash the custom Nougat ROM via TWRP, but got an error. (Zip file is corrupt! Error installing zip file '/sdcard1/[rom].zip') (Tested after transferring the file via AirDroid, don't remember if I even downloaded directly from my phone.) Now if I run a full wipe through TWRP and re-flash the original 6.0.1 ROM that's in my microSD, it *does* install, but bootloop still exists. I tried wiping/flashing the custom ROM via fastboot out of curiosity, and received the following:
wipe (entered bootloader mode from my Downloads folder, where the ROM is found)
C:\Users\[name]\Downloads>fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (status read failed (Too many open files in system))
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command failed (Invalid argument))
erasing 'userdata'...
FAILED (command write failed (No such device or address))
finished. total time: 0.020s
(Afterward, I get a message saying fastboot.exe has stopped working. Not on Minimal ADB, though.)
flash
C:\Users\[name]\Downloads>fastboot update [rom].zip
'archive does not contain 'android-info.txt' ,
error: update package '[rom].zip' has no android-info.txt
Do these errors relate with each other? Was my file just not downloaded properly?
Regarding the drivers, I downloaded the official Xperia XZ ADB interface driver (Sony sa0115) from SONY's website, and installed via Device Manager, but get the Code 10 Error mentioned in OP. According to some user posts, the solution was changing their phone's USB configuration to MIDI, afterward Windows would properly detect and install the Sony sa0115 driver. (I reckon that's not possible on a soft bricked device, is it...?) No devices are found after entering adb devices in command prompt, so I'm going to presume installing/flashing anything via ADB is out of the question. Right now, Device Manager shows 2 devices-- One of them being the actual XZ when connected in fastboot mode (labeled "Android Phone"), the other being the Sony sa0115 driver I downloaded/installed. The trick now is mounting the two together.
At this point, fastboot/TWRP seem to be the only way out of this. The custom ROM notes that no kernel flashing is necessary, but your guide includes a link to the AndroPlus kernels (for stock, and other roms, I take it). Unfortunately, until I figure out how to properly flash the firmware via Flashtool, AndroPlus will have to wait. (Unless there's a way to find out what firmware my phone is using right now.) The next option is to directly send the custom 7.1.1 ROM from my PC to the microSD card, but I can't find my SD card adapter right now, so I'll update later this week.
simpleflips said:
@DHGE
At this point, fastboot/TWRP seem to be the only way out of this
Click to expand...
Click to collapse
Unfortunately this is not a way out. And what you wrote above sounds rather weird for me...
The only way out is to flash a SONY ROM properly. THE tool for this is flashtool.
There are some mentions of SONY's recovery tool(s?) but last time I tried one I could not get it to work. Flashtool to my rescue.
Maybe you can take your phone to a qualified repair shop and they flash you a SONY ROM.