Related
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
Hi guys, xda-developers have a whole lot of newbies at Android, and when they come across ROMs or something, they have terms that they don't understand, so I make a thread for them to understand the terms. Please delete this if there is one already, and please correct me if I'm wrong, also help me add more terms, you guys will get a thanks and a shoutout in the post. Here I use the term "device" for all Android phones and tablets.
General (incl. Linux, Android, etc) terms:
- Odexed: A ROM that all the system apks has an .odex file that contains stuff about the apk. It is used to save some storage in most of stocks.
- Deodexed: A ROM that all the system apks has their own stuff in their own apk, not reliabling on the .odex files to save storage.
- Wiping: Self-explanatory. Every time you flash a ROM you need to wipe away all the stuff of the old things, and bringing the modified stuff back to normal and then you can replace it (if not it will conflict and stucks)
- Xposed: A framework for modding without the hassle of editing any apks. Uses modules to mod. Kinda cool.
- Terminal: The Terminal of Linux. You can say it's like Windows' Command Prompt. You guys can reach the terminal shell within Android with Terminal Emulator (Play Store please, it's free), it still uses Linux's commands, it's also used by Complete Linux Installer to host a VNC server and run Linux distros on it, and you guys can also install BusyBox to extend the Android Terminal shell as the Android Terminal shell is not the same as Linux's, so BusyBox to the help! Unleash your inner geek!
- BusyBox: You guys gotta know this, right? It's a executable contains most Linux/Unix commands, ie. In your Wi-Fi router, there is a very small 3MB flash, and there are Linux/Unix commands in it. They uses BusyBox to narrow down the size as BusyBox is very small in size but contains most Linux/Unix commands. And we also can install single packages, instead of using the whole thing.
- Recovery: A "secret" menu thingy, reached by holding a combination. It's where you can do basic crap like factory resetting your phone, applying update.zip (OTA updates) (stock), in custom recoveries, you can do a lot more stuff.
- Flash: Writing an official Android firmware (kernel, system, baseband, etc. of stock files) to your device. We have ODIN for Samsung, Flashtool for Sony (that's all I know)
- ROM: The Android firmware in your device.
- Radio: The radio firmware, you need it to connect to Internet.
- Kernel: The core of every OS, and here, we're based on Linux. And if your bootloader is unlocked, you can replace it. Simple.
- Soft-brick a.k.a Bootloop: You got stuck in the logo or it keeps looping the boot sequence.
- Bootloader: What Android (and every OS) uses to make the core reads and loads the OS.
- Unlocked/Locked Bootloader: The state of the bootloader. Unlock the bootloader makes the Android kernel replaceable, and make the core reads it as a valid Android kernel. Locked bootloader only reads the stock kernel as valid to boot. Usually unlocking the bootloader voids your warranty.
- Root: The work to gain full control. You guys know Linux, it come with root, but on Android, Google disabled it, so we gotta enable it, and use an app like SuperSU to control and manages it. In the old days, rooting usually needs to unlock the bootloader, so you gonna void the warranty of the phone. But now, we can root with out unlocking the bootloader, which we can keep the warranty!
- Hard-brick: Basically, your device becomes a battery-powered paper holder. (And it CANNOT be saved unless: you buy a new phone or you go and change the mainboard)
Recovery-related terms:
- Stock Recovery: Just too bullcrap, only usable for stock OTA updates (apply update.zip) and factory resetting your devices.
- Custom Recovery: A customized recovery (self-explanatory) and it can do more than the stock recovery, like installing ROMs, flash stuff, etc. Two well-known custom recoveries are ClockworkMod and TeamWin Recovery Project. There are less-known variants of them like PhilZ, ClockworkMod Touch, due to their compatibility to less phones.
- ClockworkMod Recovery (CWM, or CWM Recovery for short): A custom recovery for Android devices. Not just factory resetting your devices, it can also clear cache, do crap in it and install custom ROMs
- TeamWin Recovery Project (TWRP or TWRP Recovery for short): Same as CWM but more user-friendly with touch controls, and also can flash more than one zip at once, and other stuff. But we have CWM Touch to compete with TWRP in the user-friendly-ness!
Sony-related terms:
- TA Partition: Trim Area Partition, where Sony's DRM keys for Sony's patented stuff to run. When you unlock your bootloader, the TA Partition will be erased. You will lose Sony's technologies like Bravia Engine,... if the TA Partition is erased.
HTC-related terms:
- S-ON and S-OFF: Basically, it's a extra protection layer staying under the bootloader. S-OFF means you can fully operates the device, like a simple unlock of the bootloader. But in HTC, to have full control, you have to S-OFF too, and I remember it also voids your warranty.
Samsung-related terms:
- Knox: Samsung's new protection like HTC's S-ON, it will become 0x1 ("Custom" state) if you flash a custom ROM. When it becomes 0x1, your warranty is voided.
- Flash counter: If you flash 1 custom ROM or a ROM with ODIN, it will becomes 1. And as soon as it becomes 1, you will trip Knox, and your warranty is voided. You can reset this with a Gingerbread ROM (official, everything included).
ROM-related terms:
- Stock ROMs: The Android firmware shipped with your phone, full of bloatware (in my opinion) and better be replaced with a custom one.
- Custom ROM: An Android firmware has been changed and modded by developers. Usually based on these three kernels:
+ Stock (Normal Kernel)
+ CyanogenMod (CyanogenMod kernel for modding)
+ AOKP (AOKP kernel I remember)
- AOSP: Android Open Source Project, the source code of Android released by Google Inc. and most major aftermarket ROMs based on it. (also stocks too, no AOSP, no Android)
- CyanogenMod: An aftermarket Android firmware, official releases based on AOSP, very customisable, very smooth and it's better than stock ROMs to use daily because of the smoothness of AOSP.
- AOKP: Android Open Kang Project, also an aftermarket Android firmware, has a lot of features (even more than CM) but the small bit of lag due to the features makes it not very comfortable to use daily.
- ParanoidAndroid: Again, another aftermarket firmware, like AOKP, has a lot of features and other crap. And it has a cool thing: Pie Control. Basically navbar in a pie chart thingy.
*ALL THOSE ROMS ABOVE ALL BASED ON CYANOGENMOD, EXCEPT FOR ITSELF, WHICH BASES ON AOSP*
CyanogenMod (CM for short)-related terms:
- Theme Engine: A theme engine of CM, presents since CM9 (I remember - Trebuchet is CM's own launcher since then so yeah) which applies custom themes, they themes from the icons to the status bar icons. Pretty freaking sick. I use stock in my Acro HD, and CM in my Arc S, and I miss that kind of modding the theme of my phone.
ParanoidAndroid (PA for short)-related terms:
- Pie Control: As explained above, a navbar in a pie chart thingy, which helps a lot I mean. I used PA once, and that is sick. PA ROMs are cool. They have CM's features and some of their stuff. Sick as crap. So cool. Just full awesome.
Debug-related terms:
- ADB: Android Debug Bridge, a debug tool for developers to "hook" themselves up to the device. It can do a basic Android device can do: install, uninstall, take a logcat of the device, etc. Some commands:
+ adb devices: list the devices (under the serial) connected and recognized.
+ adb logcat: take a logcat of your device in realtime, press Ctrl+C to stop.
+ adb install: install Android APKs to your phone, adb uninstall is vice-versa.
+ adb push: copy a file to your device.
+ adb pull: take a file from your device and copy it to your PC.
+ fastboot flash (image): flash a kernel to your device.
+ fastboot boot (image): boot an image (usually for a recovery) without flashing it onto your phone, for backing up a fully stock ROM with stock recovery (mostly).
Okay. It's the end of it for now. Please press thanks if it helped you, and please add me stuff if I missed anything, also correct me if I'm wrong. Thanks! I love Android, and I always will.
NOTE: NO APPLE FANBOYS HERE PLEASE! REMEMBER, I LOVE ANDROID, AND I ALWAYS WILL
NOTE 2: TERMINAL AND BUSYBOX ARE LINUX'S TERMS, NOT ANDROID'S BUT THEY ARE RELATED SO IT'S STILL BEING LISTED HERE AS IT'S STILL PART OF ANDROID ANYWAY
Sent and edited from my Acro HD and my Arc S via XDA Premium 4 app, and my PC through Chrome.
ChiefDoraemon said:
Hi guys, xda-developers have a whole lot of newbies at Android, and when they come across ROMs or something, they have terms that they don't understand, so I make a thread for them to understand the terms. Please delete this if there is one already, and please correct me if I'm wrong, also help me add more terms, you guys will get a thanks and a shoutout in the post. Here I use the term "device" for all Android phones and tablets.
General:
- ROM: The Android firmware in your device.
- Radio: The radio firmware, you need it to connect to Internet.
- Soft-brick a.k.a Bootloop: You got stuck in the logo or it keeps looping the boot sequence.
- Bootloader: What Android (and every OS) uses to make the core reads and loads the OS.
- Unlocked/Locked Bootloader: The state of the bootloader. Unlock the bootloader makes the Android kernel replaceable, and make the core reads it as a valid Android kernel. Locked bootloader only reads the stock kernel as valid to boot. Usually unlocking the bootloader voids your warranty.
- Hard-brick: Basically, your device becomes a battery-powered paper holder.
HTC-specific stuff:
- S-ON and S-OFF: Basically, it's a extra protection layer staying under the bootloader. S-OFF means you can fully operates the device, like a simple unlock of the bootloader. But in HTC, to have full control, you have to S-OFF too, and I remember it also voids your warranty.
Samsung-specific stuff:
- Knox: Samsung's new protection like HTC's S-ON, it will become 0x1 ("Custom" state) if you flash a custom ROM. When it becomes 0x1, your warranty is voided.
- Flash counter: If you flash 1 custom ROM, it will becomes 1. And when it becomes 1, you will trip Knox, and your warranty is voided.
Okay. It's the end of it for now. Please press thanks if it helped you, and please add me stuff if I missed anything, also correct me if I'm wrong. Thanks!
Click to expand...
Click to collapse
I feel like something like this has to exist already. Granted I'm not on the lookout for it because these terms aren't foreign to me. Nevertheless, if something like this doesn't exist, I suppose it would be a good sticky to have somewhere on the forums so that people can have a quick glossary of jargon to access. I mean, yeah, people can just Google it too, but ya know... keeping people on the site is important n stuff.
Android Terminology
Thanks mate, way to go helping the noobies out. Even though I am familiar with these terms, its always a good refresher.:good:
This is still helpful, thanks!
Mithraeum said:
This is still helpful, thanks!
Click to expand...
Click to collapse
DvDev said:
Thanks mate, way to go helping the noobies out. Even though I am familiar with these terms, its always a good refresher.:good:
Click to expand...
Click to collapse
Thanks guys! Add more terms for me! Just helping the noobies folks!
Thanks for sharing this useful info.
Guys, please hit the thanks button instead of spamming the thread with thanks posts.
Great job
would be nice also to explain the
TWRP
Flashing
Recovery
Thanks a lot
alexmforero said:
Great job
would be nice also to explain the
TWRP
Flashing
Recovery
Thanks a lot
Click to expand...
Click to collapse
Sure! Adding it right now.
Recovery BootStrap (TWRP) - Motorola Defy\Bravo
Version: 4.0
Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.
Download: (Windows: MEGA / Google Drive) | (Linux: port by nastys post>>)
Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser.
Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about resize.zip).
Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
Instructions:
1. Download the archive
2. Unpack it somewhere else with a short path, for example D:\andro
3. Connect your phone via USB cable ("debugging on USB" should be included)
4. Run the install_bootstrap.cmd
5. When you see the label "Let's Start? =)", press any key
6. If the superuser ask permission for full access "ADB Shell", allow.
7. After installing the smart phone will automatically restart
!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom
Change log:
V3:
Changed how the script
Fixed installation errors recovery on Android 4.x and later
V4:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and later)
Made for normal (mortals) users , before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".
Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy)
Questions\FAQ:
Error "[ERROR] Verify device!", what to do?
Error "[ERROR] Verify device!", it is may mean the following:
1. You have not enabled USB debugging
2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)
3. You need to confirm the action ADB on your smartphone
4. Or you have some other connection problems
Stock transition to CyanogenMod 11 of Quarx
Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)
1. Install Recovery BootStrap (TWRP) via USB
2. Enter Recovery install resize.zip
3. Restart your smartphone
4. Install CyanogenMod 11 and GApps
Good work, comrade! I flashed CM11 on the Moto Defy - everything works!
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
starbright_ said:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
Click to expand...
Click to collapse
I tried to do something like that, is not yet happened. Perhaps in the future even try
nastys said:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
Click to expand...
Click to collapse
Maybe. If Iunderstand with GNU/Linux scripts
The new version, V4
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Linux port done!
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: MediaFire | MEGA
On Ubuntu just mount the ISO as image (not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
evilinheaven said:
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
Click to expand...
Click to collapse
Format your SD card (to FAT32) or use another one.
Octanium91 said:
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Click to expand...
Click to collapse
nastys said:
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: https://www.mediafire.com/folder/candnhxj8aovj/Defy_Bootstrap_Installer_for_Linux
On Ubuntu just mount the ISO as image (not archive) then click 'Run'. It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included. Tested on 14.10 x86_64.
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code.
Click to expand...
Click to collapse
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
answer
Aceofzeroz said:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
Click to expand...
Click to collapse
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Octanium91 said:
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Click to expand...
Click to collapse
Many thanks for the prompt and well ordered reply! I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.
We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms. So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:thumbup:
Sent from the Ace's MB865 using Tapatalk
Error. More than one device and emulator
what am i doing wrong?
LoeWn said:
Error. More than one device and emulator
what am i doing wrong?
Click to expand...
Click to collapse
Perhaps you have not enabled USB debugging
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
I did enable usb debugging
LoeWn said:
I did enable usb debugging
Click to expand...
Click to collapse
You can send us a screenshot?
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Haldy said:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Click to expand...
Click to collapse
Based on first screenshots, Recovery installed. Now you need to install system.
Than display goes black and thats all - maybe have to wait
marcooleo said:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Click to expand...
Click to collapse
In principle it is possible, but it does not make sense.
Hey , Guys this Thread Is Specially Made for Noobs. With All Info For Android.
So , Let's Directly go to Topic
Firstly What Is Android?
• a robot with a human appearance.
•an open-source operating system used for smartphones and tablet computers which is based on Linux Os.
Source- Google
_____________________________
Version Of Android
Cupcake:
Android 1.5
Donut:
Android 1.6
Eclair:
Android 2.0
Android 2.1
Froyo:*(short for "frozen yogurt") & The Most successor Veraion
Android 2.2
Gingerbread:
Android 2.3
Honeycomb:
Android 3.0
Android 3.1
Android 3.2
Ice Cream Sandwich:
Android 4.0
Jelly Bean:
Android 4.1
Android 4.2
Android 4.3
KitKat:
Android 4.4
Lollipop:
Android 5.0
Android 5.1
Source-android.stackexchange
______________________________
What is Root?
★In Simple Word Rooting Means gives Read-Write[RW] permission on System Dictionary.★
Rooting*is the Android*equivalent of jailbreaking, a means of unlocking the operating system so you can install unapproved (by Google) apps, update the OS, replace the firmware, overclock (or underclock) the processor, customize just about anything, and so on.
Source- Google
______________________________
What is Recovery?
A combination of key presses (or instructions from a*command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install*official OS updates.
Source-Android A to Z
_____________________________
What is Bootloader?
•Every Android phone has a bootloader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
Source-addictivetips.com
____________________________
★Advance Section★
1. Bootloop - Bootloop means your phone doesn't but up right, it's just starting and starting and nothing happens, or it's starting and shutting down and starting again. It just means your phone makes a loop while booting.
2. Brick - Brick means your phone can't boot up and you can only recover it with for example flash the stock rom. But there are different bricks for example soft bricks (for example bootloops) and hard bricks (for example doing and over the air=ota update when bootloader is unlocked). There are some other bricks and examples as well.
There Are Two Types of Bricks
1.Soft Brick - you can still turn your phone on but it doesnt really start (bootloop i think is a kind of soft brick. )
this kind of brick can be fixed through softwares like flashtool.
2. Hard Brick - you can't turn your phone on and it doesnt really start, you don't get any response from it.
Click to expand...
Click to collapse
3. Fastboot - Fastboot mode is used to flash a kernel if the bootloader is unlocked. With fastboot you flash a boot.img for your device, for example a kernel for a specific rom
Source - from( XDA)
_____________________________
What is Nandroid?
the type of permanent storage memory that your device uses, and Android. A*Nandroid*backup is a de-facto (by the hacking community) standard directory structure for backing up a perfect mirror image of your Android device.
Source - Google
_____________________________
What is Kernel ?
is a “deeper” line of code that rests beneath the surface, so to speak. It tells the software how to interact with the hardware.
____________________________
What is Custom Rom?
A*custom ROM replaces your device's Android operating system — normally stored in read-only memory — with a new version of the Android operating system.
Some Famous Custom Roms Are
°Cyanogen Mod
° Pac-Man
etc...
___________________________
What is Flashing?
Flashing is a process in which system's update Any Kind of files like Apps , System file etc...
___________________________
This Things Might Confused Many People But for Development of Android.
You Have To Totally Know This Types Of Things.
Good info for noobs:thumbup:
suresh.anthati said:
Good info for noobs:thumbup:
Click to expand...
Click to collapse
Thanks Dude
Hi,
I'm currently waiting for buy the Xperia XZ. I check some of XDA's thread and with Sony's smartphone I'm still afraid. So I want to know if there is a thread gathering all the detailled step to root, install TWRP, flash latest firmware, install custom ROM etc... ?
Thanks a lot
[Guide] Here is the DHGE guide for rooting SONY devices 2019-04
Changelog at the bottom of this post.
nathan30 said:
if there is a thread gathering all the detailed step to root, install TWRP, flash latest firmware, install custom ROM etc... ?
Click to expand...
Click to collapse
No - but you can find all you need to know here in this forum or in the devices-fora later than Z3+ or SONY-cross-device.
https://forum.xda-developers.com/crossdevice-dev/sony
Good introductory (written for devices before Z3+):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
It is still valid but the 2015 and newer devices are not rootable anymore as described thanks to DM-Verity.
For rooting the current device you have to open the bootloader.
Any claims to the contrary found "on the web" are only tricks to have you install "interesting" software on a Windows PC.
Do you want root?
A classic post to help you decide
No:
wait for the OTA-updates from SONY (over the air - prosaic?)
don't like waiting or want to downgrade: get Flashtool http://www.flashtool.net
it comes with Xperifirm that finds you the latest ROM
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Unfortunately Xperifirm only finds the latest ROM (the only available on SONYs servers) so you better keep your downloads (>2 GBytes each) or find an older ROM in case you need it (xda has a search function). Here you'll find some ROM-versions: https://xpericheck.com
since my Xperia XZ/XZ1 I occasionally have problems with Flashtool that it requires a FSC-script which does not come with it or can not easily be copied from a similar device.
Now I use Newflasher https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426 by @munjeni. This is a command line tool that for me unfortunately only works under Windows (have JDK issues under Debian).
You unpack the ROM (ftf-file) and place the newflasher.exe in the directory where you unpacked to. Then you start the device in flash mode (power on while holding the volume down key) and run the tool from the command line as administrator/root.
If you do not delete userdata.sin you will initiate the equivalent of a factory reset (aka loose all your data and settings!). For an upgrade within the same Andoid version I always delete userdata.sin before newflashing.
Yes:
As stated above, you need to unlock the bootloader to modify the system software on your device. Fortunately SONY gives (for non-carrier-locked) devices the option to unlock the bootloader.
Check if unlocking is allowed: in the service menu (dial *#*#7378423#*#* or *#*#SERVICE#*#* ) check under "Service Info"->"Configuration" the line "Bootloader unlock allowed:"
If you read anything other than "Yes" Stop here!
No: flashing another SONY Rom ("Customized CountryX") does not help you.
Hint: there is an app "SONY service menu" in the app-repository (F-Droid or Google).
OK - you can Now it is your last chance to save your device keys or "backup the trim area partition"
You should do this if you ever want to return to a SONY "blessed" state. e.g claiming service in countries where warranty is not for devices with unlocked bootloader or you want to sell it.
There are some device specific kernels out there whose authors state that they mitigate all DRM issues once the TA is restored. I guess you need these kernels otherwise restoring the TA locks up your device ...
Otherwise do not bother with restoring the TA-partition. Doing so after the next steps will soft brick your device.
Now you have to prepare your PC with some drivers in order to start the backup process:
Go to SONY's developver world http://developer.sonymobile.com
Under "Downloads" you will find the drivers for the XZ or any other device http://developer.sonymobile.com/downloads/drivers/xperia-xz/
These drivers are for Windows, do not bother if you are running a free operating system.
To get fastboot running you might additionally have to find the "fastboot_driver" in the download area. Put the content of the ZIP-file into the directory where you you unzipped the device driver and install it via right-clicking on the file android_winusb.inf.
Install these drivers if you are a Windows user. Under Windows 8 and newer there could be problems with installing "non signed" drivers.
Do a web/xda search to circumvent this security measure of Microsoft or do click on reboot while holding the shift-key and figure it out yourself.
http://www.flashtool.net/win8drivers.php
When you are installing: You also need to install the programs adb and fastboot.
https://forum.xda-developers.com/showthread.php?t=2317790
If you are running a free operating system: search for adb/fastboot or Android SDK in your repository and install these.
Running Linux it helps to insert the udev-rule mentioned in http://www.flashtool.net/lininstall.php otherwise you have to run esp. fastboot with root-privileges (not recommended, although the udev rule saves no punches ...)
On Android on your SONY device you have to be root to save a partition - catch 22 :crying: ...
https://en.wikipedia.org/wiki/Catch-22
Don't fear the ... / catch: For Android Marshmallow ROMs, e.g. up to version 39.0.A.3.30 of the Xperia XZ ROM, exists an exploit of the copy on write function in the Linux kernel that gets you root privileges temporarily.
On newer devices where there is no Marshmallow ROM with a vulnerable kernel available you are out of luck until another exploit is found.
Follow https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Hint: In post #21 is described how to restore the TA (read the last sentence! -> you have to flash a stock ROM after restore).
If it does not work the first time let the tarnished bovine do its stride several times more.
Or: Repeat the process until success.
If you are already on Nougat you must downgrade the system ROM (see above) to use the exploit and backup the TA-partition.
The latest exploit that is available for devices that came out with Oreo uses a different exploit.
Search for this exploit in the specific forum or on "Sony Cross Device". If you are already on Pie you have to download an Oreo ROM for your device.
This is similar to the procedure described above that has the Xperia XZ in mind.
TA-partiton backed up?
Now the non-reversible part:
Under http://developer.sonymobile.com/unlockbootloader/ you request an unlock code.
READ, READ what SONY have written there!
- You will lose some DRM functionality: https://forum.xda-developers.com/z3-compact/general/loss-drm-keys-t2890936
- Your device will factory reset. You have a backup?
You can get the IMEI-number from the original package of your phone (if you have good eye sight and nobody swapped the boxes) or pull a tab from the side of the phone (you do not want to do that) or print a screen shot of the relevant page of your service menu or head into settings->about device->status->IMEI-Info.
You follow SONY's instructions to unlock the bootloader and hold your breath as after a long reboot everything on your device is wiped. On the newer devices you get an ugly warning "the device can't be trusted anymore".
NEVER EVER enable the MyXperia software from now on!
On some devices this in combination with an unlocked bootloader will hard brick your device.
Here was a link to fxpblog where they destroyed two devices.
Hey, you have been warned. With the TA-backup you always can return to the chicken den.
Become a "developer"
- Tap seven times on the build number of your device. (settings->device info)
- then enable "OEM unlocking" (new for the 2016 and later devices like XZ) and "USB-debugging"
You have read the SONY advice?
Next decision: Root stock ROM or go Custom Rom?
I am VERY happy with LineageOS on a Tablet Z and other devices in my household. I liked the Resurrection Remix ROM on my SAMSUNG phone.
Your mileage may vary: Testing a ROM and reversing will cost you with a proper backup minimum 4-5 hours.
If you choose a custom ROM:
- read the thread to get a hunch if you really want to install it (get over the off topic noob questions and annoying full quotes)
- Follow the instructions of the first page of the ROM-thread to install it. If you can not do this: stop or be prepared for searching and learning.
From February 2017 until May 2017 I had eXistenZ N on my Xperia XZ and like the UI tuning modifications. This "ROM" does not come pre-rooted it is a patch for the stock ROM (match the versions exactly!) that enhances the settings/look.
On SONY devices I recommend rooting stock ROMs.
Shortcut: Pie users can proceed to step 7 here
Having a custom kernel might still be advantageous for you.
You need a custom (or modified stock) kernel (aka boot image) with DM-Verity and SONY-RIC OFF.
This kernel has to be in sync with your ROM. Flashing an unsuitable kernel (e.g. MM-kernel on N-Roms) will result in a boot loop aka "soft brick".
You even can bake one yourself (no easy task) if you find/adapt the sources for your device. -> first stop SONY developer world
This is might be easy! THANKS to the efforts of @AndroPlus, @janjan and others.
You have to look into the device specific fora to find a proper kernel for your ROM-version.
They have also included many patches to improve battery life, mitigate some (e.g. camera) issues from the loss of the device keys ...
Download the kernel and recovery for your device and ROM-version and follow the kernel makers' instructions.
On devices where there is no custom kernel, you can try patching the stock kernel to switch off RIC and DM-verity. In reality behind the scenes it is a bit more than just patching (=modifying) the kernel. You also get some updated init-scripts and as a end result a new boot.img
Very useful is [PoC][Work in progress] Trim Area Proof Of Concept developed by @munjeni
These scripts not only prepare a stock kernel for rooting but also put your TA backup from above to such a use that you regain the DRM-features lost by opening the bootloader! So you do not need a custom kernel with partial DRM-fixes!
For Oreo it is more complicated (it might be easier to search for a suitable boot.img aka kernel and I have not tested it on Pie but see next step):
@serajr enhanced a script specifically for Xperia X Performance, XZ and XZs
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Under Linux I had to set the executable attributes on the shell scripts and binaries (chmod +x).
You get the required kernel.elf via the tools menu in Flashtool. Dump "kernel.sin".
I started applying the scripts to the Stock ROM in May 2017 since eXistenZ ROM lagged a bit behind in security patches and Android version:
- flashed stock ROM via Flashtool or Newflasher
- prepared a patched boot image with PoC and my kernel...sin and TA.img and answered all questions with "yes" (hit return each time)
Code:
./ta_poc kernel.sin TA.img ramdisk
I am on Debian as operating system.
On Windows you just run the provided batch files and follow the instructions here and in the thread for the scripts.
- flashed the resulting boot image with fastboot flash boot boot.img and test it works. Service menu/Security: keys provided YEAH
- flash recovery and from there root with SuperSU and flash Titanium Backup
- restored my apps with their data via Titanium Backup
==============
Some hints:
==============
Most of these commands emit useful info on the command line - read it, post their error messages if you are stuck.
Version numbers of the software used speeds diagnosis of problems. Often a good advice: "Use latest version."
adb reboot bootloader or switching OFF the device and then pressing the "volume up" button while plugging the USB cable gets you into fastboot mode. You see a black screen and the blue LED light.
I normally do not flash the kernel-ZIP-file via recovery but unpack it and flash this: fastboot flash boot boot.img
To get into recovery mode:
Switch OFF your device. Press the "power" button shortly to switch ON and hold "volume down" button more than 5 seconds (or when you see the yellow LED light on some devices).
Or: adb reboot recovery
If you can not get into recovery (e.g. AndroPlus has no kernel for your latest SONY ROM):
fastboot boot TWRP_latest_version.img
I use an SD card (content there survives factory resets) and there a directory "for_recovery" well stocked with the zip-files I intend to flash. In TWRP you can tell the file manager on what storage (internal, SD-card, USB ...) it will find the flashable ZIP-files. The default is "internal".
Pressing the Power button and "volume up" for about five seconds gives you a hard reset.
Good if you are totally struck - just flash a SONY ROM for your device with Flashtool and all the wipe boxes checked or use Newflasher (overwrites most partitions including your data).
If you like to read about the haarrrdddd way:
https://forum.xda-developers.com/z4-tablet/help/enybody-root-t3154926
The first rooting of a DM-Verity secured device in 2015. Thanks to SONY for releasing source code and binaries.
Rooting - aaahh, finally
Flash the latest Magisk (up to late 2017 I used SuperSU which still works) from recovery.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://www.chainfire.eu/ Find the latest SuperSU from there. You will not find it there any more since Chainfire has sold the rights to the utility. I endorse Magisk since that is open sourced on GitHub.
No: flashing a custom kernel and recovery does not root your device.
For Android Pie users: On my Xperia XZ1 I can skip step 6 completely!
Just install/upgrade to the latest Pie ROM and flash Magisk and install the Magisk app.
Bonus: Debloat the device
https://forum.xda-developers.com/search/forum/2522?query=debloat
Nowadays I use a debloat script written by @serajr for my devices https://forum.xda-developers.com/xperia-xz2/development/oreo-debloat-script-v1-0-t3798979,.
I edit (comment out) the debloat_list.sh in order to keep "com.google.android.apps.maps" and "com.sonymobile.email" which I both use.
mine (you screened my script?):
flash the attached ZIP-file
View attachment xtrm_debloat.flashable_ew_2016-12.zip
found in https://forum.xda-developers.com/xperia-z5/general/discussion-bloat-sony-xperia-z5-t3518860 probably original work by @ganeshbiyer
=============================================================
With opened bootloader you will not get OTA updates any more!
You have to check with the Xperifirm program if there are newer ROMs for your device.
I have not had any problems with installing e.g. a Swiss ROM over a Central Europe. There could be some worries when switching continents.
Download the desired ROM via Xperifirm and follow the instructions of Flashtool to flash the device (over USB update = OUU :laugh.
Accept the use of the FSC script.
Repeat the steps 5 to 6(7) for any other/newer SONY ROMs you flash followed by step 4 (if necessary).
If a wipe is needed I prefer the full wipe in TWRP compared to checking the boxes in Flashtool.
Or use Newflasher without flashing userdata.sin (just delete the file) in case of an upgrade.
=============================================================
CHANGES to this Guide
2019-04-23 updated for Pie, endorsed Newflasher, added link to serjars debloat script, link ckecks
2018-02-28 clarified getting kernel.elf for self patching, some typos, link ckecks
2018-01-31 link for better suited ta_poc added, toned down AndroPlus endorsement, added Magisk
2017-06-25 added link to xpericheck (find older ROMs), added hint for restoring TA for those TLDR-guys
2017-06-02 added procedure for patching stock kernel as alternative to custom kernels
2017-02-05 added recommendation for eXistenZ N ROM
2017-01-25 new URL for SuperSU, typos
2017-01-18 corrected the advice for booting into TWRP
2017-01-17 added info on fastboot driver for Windows users
DHGE said:
No - but you can find anything here or in the devices-fora later than Z3+ or SONY-cross-device.
https://forum.xda-developers.com/crossdevice-dev/sony
Good introductory (written for devices before Z3+):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
It is still valid but the 2015 and newer devices are not rootable anymore (as described) thanks to DM-Verity.
For rooting the current device you have to open the bootloader.
Any claims to the contrary found "on the web" are only tricks to have you install "interesting" software on a Windows PC.
Do you want root?
No:
wait for the OTA-updates from SONY
don't like waiting or want to downgrade: get flashtool http://www.flashtool.net
it comes with Xperifirm (at least for my linux machines) that finds you the latest ROM
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Unfortunately it does not find many older ROMs anymore so you better keep your downloads (>2 GBytes each) or find an older ROM in case you need it (xda has a search function).
Yes:
As stated above, you need to unlock the bootloader to modify the system software on your device. Fortunately SONY gives (for non-carrier-locked) devices the option to unlock the bootloader.
Check if unlocking is allowed: in the service menu (dial *#*#7378423#*#* or *#*#SERVICE#*#* ) check under "Service Info"->"Configuration" the line "Bootloader unlock allowed:"
If you read anything other than "Yes" Stop here!
No: flashing another SONY Rom ("Customized CountryX") does not help you.
Hint: there is an app "SONY service menu" in the app-repository (F-Droid or Google).
OK - you can Now it is your last chance to save your device keys or "backup the trim area partition"
You should do this if you ever want to return to a SONY "blessed" state. e.g claiming service in countries where warranty is not for devices with unlocked bootloader or you want to sell it.
Otherwise do not bother with restoring the TA-partition. Doing so after the next steps will soft brick your device.
Go to SONY's developver world http://developer.sonymobile.com
Under drivers you find the drivers for the XZ under "Downloads" http://developer.sonymobile.com/downloads/drivers/xperia-xz/
These drivers are for Windows (which version?), do not bother if you are running a free operating system.
Install these drivers if you are a Windows user. Under Windows 8+ there could be problems with installing "non signed" drivers. Do a web/xda search to circumvent this security measure of Microsoft. http://www.flashtool.net/win8drivers.php
When you are installing: You also need to install the programs adb and fastboot.
https://forum.xda-developers.com/showthread.php?t=2317790
If you are running a free operating system: search for adb/fastboot or Android SDK in your repository and install these.
Running Linux it helps to insert the udev-rule mentioned in http://www.flashtool.net/lininstall.php otherwise you have to run esp. fastboot with root-privileges (not recommended, although the udev rule saves no punches ...)
You have to be root to save a partition - catch 22 :crying: ...
For Android Marshmallow ROMs, precisely up to version 39.0.A.3.30, exists an exploit of the copy on write function in the Linux kernel that gets you root privileges temporarily.
Follow https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
If you are already on Nougat you must downgrade the system ROM (see above) to use the exploit and backup the TA-partition.
TA-partiton backed up?
Now the non-reversible part:
Under http://developer.sonymobile.com/unlockbootloader/ you request an unlock code.
READ, READ what SONY have written there!
- You will lose some DRM functionality: https://forum.xda-developers.com/z3-compact/general/loss-drm-keys-t2890936
- Your device will factory reset. You have a backup?
You can get the IMEI-number from the original package of your phone (if you have good eye sight and nobody swapped the boxes) or pull a tab from the side of the phone (you do not want to do that) or print a screen shot of the relevant page of your service menu or head into settings->about device->status->IMEI-Info.
You follow SONY's instructions to unlock the bootloader and hold your breath as after a long reboot everything on your device is wiped. On the newer devices you get an ugly warning "the device can't be trusted anymore".
Hey, you have been warned. With the TA-backup you always can return to the chicken den.
Become a "developer"
- Tap seven times on the build number of your device. (settings->device info)
- then enable "OEM unlocking" (new for the 2016 devices like XZ) and "USB-debugging"
You have read the SONY advice?
Next decision: Root stock ROM or go Custom Rom?
Well - my opinion - for the newer SONY devices I have not found a recommendable custom ROM yet. I am VERY happy with a generic CyanogenMod on a tablet Z in my household. Do not ask me about the sad story of CyanogenMod as of late 2016...
Your mileage may vary: testing a ROM and reversing will cost you with a proper backup minimum 4-5 hours.
If you choose a custom ROM:
- read the thread to get a hunch if you really want to install it (get over the off topic newbie questions)
- Follow the instructions of the first page of the ROM-thread to install it. If you can not do this stop or be prepared for searching and learning.
On SONY devices I recommend rooting stock ROMs.
You need a custom kernel (aka boot image) with DM-Verity and SONY-RIC OFF.
This kernel has to be in sync with your ROM. Flashing an unsuitable kernel (e.g. MM-kernel on N-Roms) will result in a boot loop aka "soft brck".
You even can bake one yourself (no easy task) if you find/adapt the sources for your device. -> first stop SONY developer world
This is easy! THANKS to @AndroPlus
AndroPlus has also included many patches to improve battery life, mitigate some (e.g. camera) issues from the loss of the device keys ...
https://forum.xda-developers.com/xperia-xz/development/kernel-andropluskernel-v01-t3475240
AndroPlus has kernels for other devices too. Look into the specific device forum for a custom kernel,
Download the kernel and recovery for your device and ROM-version and follow AndroPlus' instructions.
Some hints: (most of these commands emit useful info on the command line - read it, post it if you are stuck)
adb reboot bootloader or switching OFF the device and then pressing the "volume up" button while plugging the USB cable (hooked to your PC! we need DC power for all this) gets you into fastboot mode. You see a black screen and the blue LED light.
I normally unpack the kernel-ZIP-file and flash this: fastboot flash boot boot.img
You get into recovery mode on booting by pressing the "volume up" button when you see the yellow LED light.
If you can not get into recovery (e.g. AndroPlus has no kernel for your latest SONY ROM):
fastboot boot TWRP_latest_version
I use an SD card (content there survives factory resets) and there a directory "for_recovery" well stocked with the zip-files I intend to flash.
Pressing the Power button and "volume up" for about five seconds gives you a hard reset.
If you like to read about the hard way:
https://forum.xda-developers.com/z4-tablet/help/enybody-root-t3154926
The first rooting of a DM-Verity secured device in 2015. Thanks to SONY for releasing source code and binaries.
Rooting - aaahh, finally
Flash the latest SuperSU from recovery.
https://download.chainfire.eu/1019/SuperSU
No: flashing AndroPlus or TWRP does not root your device. You'll have to flash Chainfire's ZIP-file!
Bonus: Debloat the device
https://forum.xda-developers.com/search/forum/2522?query=debloat
mine (you screened my script?):
flash the attached ZIP-file
View attachment 4000189
With opened bootloader you will not get OTA (over the air - prosaic?) updates any more!
You have to check with Xperifirm if there are newer ROMs for your device.
I have not had any problems with installing e.g. a Swiss ROM over a Central Europe. There could be some worries when switching continents.
Download the desired ROM via Xperifirm and follow the instructions of flashtool to flash the device. Accept the use of the FSC script.
Repeat the steps 5 to 6(7) for SONY ROMs followed by step 4 (if necessary).
If a wipe is needed I prefer the full wipe in TWRP compared to checking the boxes in FlashTool.
Click to expand...
Click to collapse
Woaw, thanks a lot for your awesome answer !
I receive my phone today, I'll follow your instructions
@DHGE your guide is well put, and I've not had any problems so far (I used a slightly different version of the Xperia ROM since the version you specified didn't show up, but it worked just fine, is sitting on Android 6.0, and I have the TA backed up).
I've obtained the unlock code from Sony's developer site, but I've still yet to get their email with the instructions on where to shove the code. Its been about two or three hours now, and it was sent to a Gmail address (which has received other mail since). I tried generating a new code to make sure the email was right (it was), and it spat out the same unlock code, so I'm guessing its just based off of the IMEI.
Question is: what does one do with the unlock code? I can't imagine the instructions would be different for each person and am not sure how long it may take Sony to email the Gmail account...
k2trf said:
What does one do with the unlock code?
Click to expand...
Click to collapse
Follow the steps on SONY's website where you obtained the unlock code.
Look at the big link at the right bottom after all the warnings...
Somehow I missed that completely, and just latched onto it saying to wait for the instructions via email. Honestly, I don't even know why they think it necessary. Anyone playing with unlock codes damn sure better be familiar with ADB and fastboot already, or be learning as they go. >_>
Hi,
there something I can do to roll back if I didn't backed up my TA partition?
thanks
bigkekko said:
Hi,
there something I can do to roll back if I didn't backed up my TA partition?
thanks
Click to expand...
Click to collapse
Roll back to recover TA? Unfortunately not.