Related
Vodafone Smart II aka Alcatel v860
based on stock vodafone it
1. How to make flash.
First unpack "alcatel-onetouch.7z" to ROOT of your MicroSD Card.
"must be in root eXactly like this "f:\alcatel-onetouch\backup\" (where f:\ is your letter of the MicroSD Card)
so for that just unzip, unrar the files "alcatel-onetouch.7z" to your MicroSD Card letter mine is f:\
2. Insert in your Vodafone Smart II aka Alcatel v860 smarthphone and be sure that you have the phones battery charged at 100% before continue.
3. make backup of your stock rom first just in case something is wrong
start up phone with VOLUME UP + POWER as soon as is vibrate just let go of POWER key and don't let go of VOLUME UP till TCT ALCATEL Recovery v1.0.0.0 appears
to navigate use VOLUME UP + VOLUME DOWN
to enter in subdirectory or to enter use HOME (HOUSE)
to go back from subdirectory use GO BACK ARROW
4. To make BACKUP of existing ROM go to
- backup and restore - backup
5. To RESTORE do
- wipe userdata/factory reset (confirm with YES -- delete all user data)
- wipe cache partition (confirm with YES -- Wipe Cache)
- advanced - Wipe Dalvik Cache (confirm with YES -- Wipe Dalvik Cache)
- backup and restore - Restore (select "apps")
Wait to complete restore operation and
- reboot system now
======================================================================
English (United States)
English (United Kingdom)
Italiano
Francais
Espanol
Deutsch
======================================================================
roeddie custom rom edition v0.7
Changelog: 01-08-2012
With Applications version
Requires: microSD memory card inserted in the phone and 370 mb free space on it
0. Totally UNBRANDED from Vodafone Crap
1. ROOT access with Superuser
2. Link2SD for advanced USERS and App2SD to move application from internal memory to microSD card and free space
3. has over 75 mb free space of internal memory
4. has best tweaked settings for CAMERA, recording in h264 with maximum of 1.5 mb/s of 640x480 and with AAC stereo sound enabled with maximum bitRate 128000 and sampleRate 16000
5. Total Commander with ROOT support (the best file manager ever)
6. IMPROVED speed up and performance with new settings
7. BATTERY BOOSTER to balance and maximixe battery without loss in performance
8. Launcher replaced with tweaked more powerfull and less memory eater LauchPro
9. Fixed WiFi, Bluetooth and 3G, no more errors when turning off, on
10. Customization and many others tweaks.....
11. Build in with Apps and Games
SORRY I STILL HAVE 8 POST SO LINKS ARE FOR 10 POSTS
JUST GO TO
roeddie.blogspot.com
and download
infos:
this backup rom is NOT SIM NETWORK UNLOCKED !
--
You are the best jajaja, Thanks to you we can see the first ROM for Vodafone Smart II!!!!!!!!!!!!!!
MEDIAFIRE WAS DELETED 0.2 Version OF THE ROM
Thanks, re uploaded media fire links
Arnau134 said:
You are the best jajaja, Thanks to you we can see the first ROM for Vodafone Smart II!!!!!!!!!!!!!!
MEDIAFIRE WAS DELETED 0.2 Version OF THE ROM
Click to expand...
Click to collapse
RE UPLOADED MEDIAFIRE LINKS to v0.5
In my phone the WIFI no works, I downgraded to 0.1 version, sorry, in 1 reebot works fine, but I returned to official rom
Update error
No update.zip on sdcard.....
Does it also work with a locked phone?
Very nice job! One question, I have a Smart II with a Vodafone simlock. When I install your rom would it also unlock de sim?
Flash player
Flash player is not working,black skrin
Flash player
FLASH PLAYER is working.
Can you please let us have the file or explain how to do the changes for:
4. has best tweaked settings for CAMERA, recording in h264 with minimum of 1 mb/s and maximum of 2.5 mb/s of 640x480 and with AAC stereo sound enabled with maximum bitRate 128000 and sampleRate 16000
6. IMPROVED speed up and performance with new settings
7. BATTERY BOOSTER to balance and maximixe battery without loss in performance
8. Customization,Launcher replaced with tweaked more powerfull and less memory eater LauchPro
I want to try the tweaks on my actual rom to keep original language pack.
Problem....
I dont have option were to restore/backup the phone as you see in the pics... any advice ? Thank you in advance
http://imageshack.us/photo/my-images/845/p1030937p.jpg/
Voda_Smart_2 said:
Can you please let us have the file or explain how to do the changes for:
4. has best tweaked settings for CAMERA, recording in h264 with minimum of 1 mb/s and maximum of 2.5 mb/s of 640x480 and with AAC stereo sound enabled with maximum bitRate 128000 and sampleRate 16000
6. IMPROVED speed up and performance with new settings
7. BATTERY BOOSTER to balance and maximixe battery without loss in performance
8. Customization,Launcher replaced with tweaked more powerfull and less memory eater LauchPro
I want to try the tweaks on my actual rom to keep original language pack.
Click to expand...
Click to collapse
go to roeddie.blogspot.com
it's all there eXplained
phenomenalxp said:
go to roeddie.blogspot.com
it's all there eXplained
Click to expand...
Click to collapse
Wait !
Volume Up + power button = Recovery menu - I got only 4 options: Reboot System
Apply update from sdcard
Wipe userdata
Wipe Cache
.And ... thats all ! Nothing more ... to change the name of the .zip ? from alcate.... to update ?
Recovery with 4 options
spinky360 said:
Wait !
Volume Up + power button = Recovery menu - I got only 4 options: Reboot System
Apply update from sdcard
Wipe userdata
Wipe Cache
.And ... thats all ! Nothing more ... to change the name of the .zip ? from alcate.... to update ?
Click to expand...
Click to collapse
That's because you're from a country that sent recovery system with 4 options (Portugal, spain...).
I could tell you how to get all options but I did that and now I can't select any because my home button (in recovery mode) doesn't function, and since there's that risk I advise you not to mess with that recovery and wait till CWM launches (if they launch) a root mod for Vodafone smart II.
But I'm no expert on this so do as you think it's best.
ah_burn! said:
That's because you're from a country that sent recovery system with 4 options (Portugal, spain...).
I could tell you how to get all options but I did that and now I can't select any because my home button (in recovery mode) doesn't function, and since there's that risk I advise you not to mess with that recovery and wait till CWM launches (if they launch) a root mod for Vodafone smart II.
But I'm no expert on this so do as you think it's best.
Click to expand...
Click to collapse
Mine is from Ireland.... I just bought it ... so ... Im waiting for smb with experience.
DUDE HELP
I DID THIS http://roeddie.blogspot.com/p/vodafone-smart-ii-recovery.html AND NOW TOUCH SENSITIVES BUTTONS ARENT WORKING
PLEASE HELP
qepaxhiu said:
DUDE HELP
I DID THIS http://roeddie.blogspot.com/p/vodafone-smart-ii-recovery.html AND NOW TOUCH SENSITIVES BUTTONS ARENT WORKING
PLEASE HELP
Click to expand...
Click to collapse
Use fastboot to install a stock boot.img / system.img / data.img and let it make the update 2 (wich will fix the touch keys), you have several stock rom available in xda
dude why you rom it ends with .001
and why are 2 roms
when i try to extract the roms winrar it says error
qepaxhiu said:
dude why you rom it ends with .001
and why are 2 roms
when i try to extract the roms winrar it says error
Click to expand...
Click to collapse
First I'm not your dude, second the rom isn't mine as you can guess, but i'll explain, you have to use 7-zip to mount both parts into a file, than install it via fastboot since you don't have touch keys.
You can solve your problem by installing a stock rom available on this site and updating it via firmaware update on defenitions
ah_burn! said:
First I'm not your dude, second the rom isn't mine as you can guess, but i'll explain, you have to use 7-zip to mount both parts into a file, than install it via fastboot since you don't have touch keys.
You can solve your problem by installing a stock rom available on this site and updating it via firmaware update on defenitions
Click to expand...
Click to collapse
i fixed the touch buttons
and i tried to open the download rom with 7zip and still error
Item specifics
Unlock Phones: Yes
Display Color: Color
Brand Name: Star
Design: Bar
CPU: Quad Core
Cellular: GSM,WCDMA
Display Resolution: 1280x720
Touch Screen Type: Capacitive Screen
Screen LCD Type: TFT
SIM Card Quantity: Dual SIM Cards
RAM: 1G
CPU Manufacturer: MTK
Camera: 12MP
ROM: 8G
Operation System: Android 4.2.1
Feature: GPS Navigation,Email,FM Radio,MP3 Playback,Touchscreen,Bluetooth,Wi-Fi,Memory Card Slots,Video Player,Gravity Response,Message
Model Number: S1
Display Size: 5.8 Inch
color: Black and white
Display: 1280*720
CPU: Quad core MTK 6589
OS: Android 4.2
Screen: 5.8 Inch capacitive touch screen
WIFI: Support
GPS: Support
RAM: 1G
ROM: 8G
CWM5 - ClockWorkMod 5
CWM6 - ClockWorkMod 6
TWRP - Team Win Recovery Project 2.4.4.0 (support for saving NVRam)
Stock firmware v2. TWRP. PrePooted. - The standard firmware. Removed Chinese applications, SMS-senders. Contains TWRP and ROOT.
Stock firmware. CWM5. PrePooted. - The standard firmware. Removed Chinese applications, SMS-senders. Contains CWM and ROOT.
Lewa Rom - Lewa Rom from Russia for S1.
Guys, sorry for my english ...
Dear [email protected],
Is the stock ROM missing uboot, cache & user data ?
strangermj said:
Dear [email protected],
Is the stock ROM missing uboot, cache & user data ?
Click to expand...
Click to collapse
They are specifically deleted! Why do you need cache & user data - Chinese applications need? If they are needed - I can put them separately. No problem!
[email protected] said:
They are specifically deleted! Why do you need cache & user data - Chinese applications need? If they are needed - I can put them separately. No problem!
Click to expand...
Click to collapse
Actually I am a beginner and my star s1 was bricked.
I use flash tool to upgrade firmware, it said i need to tick all necessary files. At last i use download it can load your stock ROM to my s1. However, my s1 can boot up with the booting sound but the screen only have back light. When I touch the screen, it have feed back like click sound and virbate..... but nothing can see... only back light is on.
What's your CPU MTK6589 or MTK6577 - they come in two flavors!
[email protected] said:
What's your CPU MTK6589 or MTK6577 - they come in two flavors!
Click to expand...
Click to collapse
mtk6589
strangermj said:
mtk6589
Click to expand...
Click to collapse
I found that uboot is the driver of display, front and back camera. Can you upload S1 uboot ? something like uboot.bin or lk.bin
strangermj said:
I found that uboot is the driver of display, front and back camera. Can you upload S1 uboot ? something like uboot.bin or lk.bin
Click to expand...
Click to collapse
http://yadi.sk/d/SUhKiA244k1rO
[email protected] said:
http://yadi.sk/d/SUhKiA244k1rO
Click to expand...
Click to collapse
:good::good::good:
My Phone can boot up la :fingers-crossed::fingers-crossed::fingers-crossed:
Thank you very much.
few problems:
After boot up, it show invalid IMEI, whatsapp said my device is a tab
use the home key cannot wake up the screen
strangermj said:
After boot up, it show invalid IMEI
Click to expand...
Click to collapse
Repair IMEI by the engineering menu.
1. Click on the button to dial the number and enter * # * # 3646633 # * # * If you do not work (and we did not work) then put IT. and go to the point of prozhke Engineer Mode-> Engineer Mode (MTK)
2. We fall into the engineering menu and choose: "CDS Information", "Radio Information", "Phone1"
3. At the very pinnacle of the field where it says AT + add EGMR = 1,7, "vash_imei1" in itogde get the string AT + EGMR = 1,7, "vash_imei1" button and click "SEND AT COMMAND"
where vash_imei1 - this is your imei for the first SIM card
4. If you want to register for the second imei sim card, then in the same row is typed AT + EGMR = 1,10, "vash_imei2" again and click the button "SEND AT COMMAND"
5. Exit the engineering menu and restart your smartphone.
P.S: You can find the IMEI under the battery ...
strangermj said:
use the home key cannot wake up the screen
Click to expand...
Click to collapse
This is the factory, and later made a patch to fix it ....
finally I flash the ROM again and follow you instruction, it working now, thanks.
Now, I found a problem between bluetooth and 3G. When my Jawbone ICON HD connected, I can hear the sound clearly but my friend said my voice quality is very bad. Moreover, every time when I disconnect the call from my bluetooth, the 3G signal will lost and then need few second to search the network again. Is it the hardware limitation or software problem ?
Software...
I find bluetooth address Unavailable
Hello [email protected] i have same phone STAR S1 - i need a rom firmware you possibile help me ?
Thanks
I have a star G9300 mtk6577 android 4.1.1 y need to root any help me?
Sent from my e1920_v77_zlh_fwvga using xda premium
eminemskc said:
Hello [email protected] i have same phone STAR S1 - i know a mtk 6577 and have android 4.1.1 i need a rom firmware you possibile help me ?
Thanks
Click to expand...
Click to collapse
A little later lay the firmware for you to MTK6577.
how much does it?
The file will be available until 1 June 2013.
http://yadi.sk/d/MDUgH7fw5HLpe
Pls I have issues with downloading from the
server without resume capability, kindly help put
the rom for star s1 mtk6589 in a resume supported server. This will be
highly appreciated. Also is there an upgrade in
version of android available for this product yet?
mt6572, mt6575, mt6577, mt6589, mt6582, mt6592 and all the other variants up to mt6592, except AndroidOne project.
The version 2.7 is the final version for Jellybean kernels (or older). This is the end of the road for it. Won't be more updates. Instead for newer kernels (kitkat, maybe lollipop) you should check my new version.
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
It is a CWM based recovery and is compatible with it. In this version I used Napstar-xda's full touch module as base. The navigation it is posible by touching the menu item. In long display menu (as choose zip from sdcard) for scroll page down Swipe Right and for scroll page up Swipe Left. For Go Back also Swipe Left.
If the Swipe doesn't work (usually if your phone is multitouch but has only 2 points of touch), use bottom virtual navigation keys or volume buttons Down for Scroll down, Up for Scroll up, and the back button for Go Back.
Version 2.7 update (11-dec-2014):
- rebuilt from base (cwm 6.0.3.7) and add improvements on top.
- reintegrated bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- better compressed backups integration - pigz support from cm-11
- new "nvram backup/restore" menu functionality: the nvram partition will be backed up in clockworkmod/backup/.nvram/nvram-xxxxx folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition defined in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- the recovery has now an increased stability, many issues are solved
- the content of the backup folder will contain only what an usual clockworkmod backup contain, and that will make it easy to restore backups made with older versions.
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
- some other changes.
You can flash in recovery the attached AromaFM_installer.zip, and the aromafm.zip will be placed at its place, so you can use aroma fm menu.
For port follow my new guide from here. If you want to use the automated method, that works only for older versions at my friend yuweng's thread.
Currently there are two lunfile paths in the world of mtk devices. This will make your USB Mass storage to work in recovery or not. Search that path in your device to see what you have.
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file" - this can be found in many devices mt6572, mt6589, mt6589T, and other old ones.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file" - this is related to new devices mt6582, mt6592...
Find where is your path and download the image to port from correct section.
There are two sections, corresponding to those two lunfile paths, with 15 images each. These 15 images are corresponding to different resolutions. Choose the one that match exactly your phone resolution. If your phone has the resolution 720x1280, then take an image with "720x1280" in name. There are few landscape versions for tablets with landscape format, so don't confuse "720x1280" with "1280x720".
IMPORTANT:[/B]
These are compiled recoveries for porting purposes only. DON'T take any of them and flash it in your phone as it is. It won't work, they include a dummy kernel. You need to port it to your device as I show in my guide, to make it work.[/COLOR]
CREDITS:
- Napstar-xda - for touch module;
- Philz-cwm6 - for get partition size method;
- xiaolu - for the new fonts;
- C3C0 - for initial mtk tweack hint - Unused now;
- Koush and all CWM team for the recovery;
- bgcngm for unpack/repack utils;
- sk8erwitskil for aromafm menu
RULES for posting your ports!
If you manage to port this to your device, add proper credits in your thread, post or article.
If you want that to be posted in a list with working devices, then post here a link to the thread or the post on xda (only on xda). Why not a free hosting link, like google drive, dev-host, mega-coz or other? Because if in the future you will port a new version, you have to replace it in that thread or post and the link from list remain the same.
ATTENTION:
There is a possibility that the touch feature to not work in all phones. It was tested in many phones, and in some of them it doesn't work. There isn't a switch, a toggle or other method to make it to work, it depends on your phone touchscreen capability from recovery. If this doesn't work in your phone, I'm sorry, it happens, and my advice is to try something else.
Few clarifications:
I provided all necessary infos to help you to port it to your devices.
It is ment to be ported to all MTK devices, but this doesn't mean it will work in all.
In some devices with a cheap screen display (usually those with anly one or two points of touch) there is a big chance to not work, or to work only partial.
If the recovery has the screen flipped, you need to use the non-touch version, and to compile it by yourself from source, or to ask a developer from your device to do it, with BOARD_HAS_FLIPPED_SCREEN true flag in device BoardConfig.
This recovery is compiled in CM-10.1 environment (android 4.2.2) and is proved to be working in devices with kernels up to Android 4.3. For kitkat use my new version.
The main purpose for this recovery was to keep it under 6Mb, to fit in that small recovery partition that was used in these MTK phones.
If your phone's kernel is bigger than 4.3Mb and the recovery size is 6Mb, don't botter to try it. It won't work, because it will exceede those 6Mb.
Carliv Touch Recovery, version 2.7, for phones with custpack partition
This is for phones with an extra custpack partition (Alcatel or TCL).
Carliv Touch Recovery, version 2.7, for phones with "ubifs" file system
This is for phones with "ubifs" file system.
CREDITS:
- Christian Troy - for ubifs initial code;
List of compiled or ported recoveries for various devices.
Lenovo S660 (CN version S026)
THL T100S
THL T11
Elephone P7 mini
Bluboo X1 (mt6582)
Doogee Rainbow DG210
Kuphone 1phone 5s (sanstar72_wet_jb3)
ZTE V967S
iNew V3 for fw versions up to 1.0.7 (different kernel)
iNew V3 for fw versions 1.0.8 and above
ONN M7 tablet
Hisense Mira II HS EG980 / Smartfren Andromax Z
Alcatel OT POP C5 5036X/5036D
Polytron W8470 / Gionee GBW192
BLU Life Play L100
BLU Life Play X L102
Micromax A110
Micromax A110 - v2.5
Alcatel One Touch 5020 and variants
Xolo Q700/Q700i
Xolo A500s
Xolo A600
Micromax A120
LAVA-iris458Q * XOLO-Q600 * CROSS A88
Alcatel One Touch S'Pop 4030/A/E/D/Y/X
Landvo L200G
XOLO 8x-1000/8x-1100
Huawei Y320-U10
Lenovo P780 - [4Gb/CN/2013 version]
Alcatel Pop C2/4032A
Acer Liquid E3 / E380 v1
Acer Liquid E3 / E380 v2
Acer Liquid Z5(Z150)
Acer Liquid Z2 (Z120)
Alcatel One Touch Pop C3 4033A/X/D/E
CTR Recovery Ported to Canvas 2 / A110/ Noir Q10/Cynus T2
Master @carliv
Master,
Once Again a Masterpiece of yours is on XDA & So, Once again this disciple of yours has done this first.....
Here is My Thread for
CTR Recovery & CWM Recovery 6.0.4.0 for Micromax A110.
Thanks a ton for this again & again. Don't know how to thank you for all of your work. but I do remember my words and waiting for that to thank you once.
thanks for your efforts!
edit: ported the 720x1280 ver. for my device and it seems to be working all fine but the log info seems to be blocking the navigation button. I guess that's just it, thanks again!
dnle71 said:
thanks for your efforts!
edit: ported the 720x1280 ver. for my device and it seems to be working all fine but the log info seems to be blocking the navigation button. I guess that's just it, thanks again!
Click to expand...
Click to collapse
No. it shouldn't be that way. This has something to do with some values from default_recovery_ui. I put those values arbitrary because I don't have your phones. It's not really blocking, only visual, but the buttons still work. I guess it looks like in the old AmonRa recovery with touch buttons.
I will take that in consideration for future improvements. For other phones with same resolution, may be different.
It will be really helpfull if you post here your phone res and the maxX and maxY values from settings.ini from cotrecovery folder, if you had that installed before.
carliv said:
No. it shouldn't be that way. This has something to do with some values from default_recovery_ui. I put those values arbitrary because I don't have your phones. It's not really blocking, only visual, but the buttons still work. I guess it looks like in the old AmonRa recovery with touch buttons.
I will take that in consideration for future improvements. For other phones with same resolution, may be different.
It will be really helpfull if you post here your phone res and the maxX and maxY values from settings.ini from cotrecovery folder, if you had that installed before.
Click to expand...
Click to collapse
touch is working even if it was somewhat blocked or something but the touch could extend above even if im not actually touching the nav buttons.
cot settings here.
;
; COT Settings INI
;
[Settings]
Theme = hydro ;
SDTheme = 0;
ORSReboot = 0 ;
ORSWipePrompt = 1 ;
BackupPrompt = 1 ;
SignatureCheckEnabled = 0 ;
BackupFormat = 0 ;
maxX = 742 ;
maxY = 1278 ;
touchY = 1067 ;
Language = en ;
dnle71 said:
touch is working even if it was somewhat blocked or something but the touch could extend above even if im not actually touching the nav buttons.
cot settings here.
;
; COT Settings INI
;
[Settings]
Theme = hydro ;
SDTheme = 0;
ORSReboot = 0 ;
ORSWipePrompt = 1 ;
BackupPrompt = 1 ;
SignatureCheckEnabled = 0 ;
BackupFormat = 0 ;
maxX = 742 ;
maxY = 1278 ;
touchY = 1067 ;
Language = en ;
Click to expand...
Click to collapse
Can you download and port again your resolution 720x1280? I changed some settings and it is updated to 6.0.4.0
Tell me if it works to re-compile all res again.
carliv said:
Can you download and port again your resolution 720x1280? I changed some settings and it is updated to 6.0.4.0
Tell me if it works to re-compile all res again.
Click to expand...
Click to collapse
still the same.. also notice my finger, the nav button detects it.
dnle71 said:
still the same.. also notice my finger, the nav button detects it.
Click to expand...
Click to collapse
The Touch is something similar like the Graph (of Mathematics).
Its based on X,Y positions like - X10 & Y 10 but in this there is no negative numbers.
So notice one thing. When ever you will click above any navigation key you will find it clicks the navigation button coming parallel to it.
Its not completely like TWRP or CWM Touch Version. But yes as we know Master @carliv can port the CWM touch version also for CTR Recovery. Then only we can get everything on touch based.
Awesome brother.. hats off.. expecting a full touch recovery soon from you...
Update
Successfully ported the recovery and its cent percent functional..btested every single options.. touch is working fine.. thanks for your suppport brother.. and I'm uploading the file now.. after that I'll update it here brother..
Sent from my Celkon A97i
I forgot to write. I made it this way, to be full screen touch. You can navigate up, down by swipe up/down in button area. For select you have to touch the screen in select button area. What is bothering me is log overlaping the icon menu. In my phone doesn't...
I will study that and maybe I will find an universal solution.
-----------------------
Ok, I figured out. I have to reduce MAX_ROWS.
I will rebuild every res, and the new one will be on 6.0.4.0 base.
carliv said:
I forgat to write. I made it this way, to be full screen touch. You can navigate up, down by swipe up/down in button area. For select you have to touch the screen in select button area. What is bothering me is log overlaping the icon menu. In my phone doesn't...
I will study that and maybe I will find an universal solution.
Click to expand...
Click to collapse
Brother here is the link.. and thanks for your awesome releases..and bro it didn't take even 2 mins to port it.. thanks for your guides..
http://forum.xda-developers.com/showthread.php?p=45347902
Sent from my Celkon A97i
All done. All updated to version 2.2. All recoveries compiled again with new version.
In attachment are ported recoveries for Canvas4 A210, Cubot A890, Star B6000, Star S9500, Star N9500, Zopo ZP820, UMI X2, Blackview JK809, Alcatel One Touch X'Pop 5035D (with custpack).
If you share one of these recoveries on your site, or other sites and forums, please use the name I gave it Carliv Touch Recovery, not Recovery Touch or CWM Touch (which is Koush's touch recovery name) or anything else. After six months of hard work I deserve that, and wasn't an easy job. Thanks!
carliv said:
All done. The source is adapted to 6.0.4.0 version of CWM. All resolutions recoveries compiled again with new version, and I hope the overlaping issue is gone.
In attachment are ported recoveries for Cubot A890 and Star B6000.
Click to expand...
Click to collapse
thanks! it's fixed now. will patiently wait for the updated features of this recovery
carliv said:
All done. The source is adapted to 6.0.4.0 version of CWM. All resolutions recoveries compiled again with new version, and I hope the overlaping issue is gone.
In attachment are ported recoveries for Cubot A890 and Star B6000.
Click to expand...
Click to collapse
Thanks Again Carliv, This Carliv Touch Recovery v.1 do Work!
I've thanked you!
PS: I put the recovery in my thread, as I did with the COT, and I also Quoted you and this 2nd post, okay?
carliv said:
All done. The source is adapted to 6.0.4.0 version of CWM. All resolutions recoveries compiled again with new version, and I hope the overlaping issue is gone.
In attachment are ported recoveries for Cubot A890 and Star B6000.
Click to expand...
Click to collapse
Bro @carliv I've ported this new recovery and its very good.. but a little problem with it is after finished installing the zip updates it never returend to the main menu.. to go out of recovery I'm removing the battery.. even the volume and power buttons also failed to work.. this problem shows up rarely and rest of the time it was good... and brother I'm moving my tjread for celkon here
http://forum.xda-developers.com/showthread.php?t=2473641
Please update it brother. The old thread is discontinued.. and one again a tons of thanks for you recoveries...
Sent from my Celkon A97i
praderj said:
Bro @carliv I've ported this new recovery and its very good.. but a little problem with it is after finished installing the zip updates it never returend to the main menu.. to go out of recovery I'm removing the battery.. even the volume and power buttons also failed to work.. this problem shows up rarely and rest of the time it was good...
Sent from my Celkon A97i
Click to expand...
Click to collapse
That's because the recovery doesn't exit from zip updater-script. Ask who write that script to do it better, with necessary unmount and clean up entries.
carliv said:
That's because the recovery doesn't exit from zip updater-script. Ask who write that script to do it better, with necessary unmount and clean up entries.
Click to expand...
Click to collapse
Brother I myself wrote it and it has correct format as you said.. it unmounts all the mounted partitions and also cleans up the temp files.. when I tried to flash the same recovery again the process went good.. ssometimes it stuck in the flashing screen and never returns.. it occured twice of my 13 tries....
Sent from my Celkon A97i
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
First of all I would like to share this method as I don't see it anywhere here (yet).
This method is not mine, nor anything is of my discovery
Alactel Flash 2 Specs (please let me know of any variation of this model)
5.0-Inch HD IPS Display (720 x 1280 Pixels, 294 ppi)
Android 5.1 Lollipop OS
MediaTek MT6753 Chipset
1.3GHz Octa Core 64-bit Cortex-A53 CPU
Mali-T720 MP2 GPU
2GB of RAM
13.0 Megapixel Autofocus Main Camera with Two-Tone LED Flash
5.0 Megapixel Front Camera with LED Flash
16GB Internal Storage
Expandable Up to 128GB via MicroSD
Dual SIM (Regular + Regular)
4G LTE, 3G HSPA+, 2G EDGE and GPRS Networks
Wi-Fi and Wi-Fi Hotspot
Bluetooth 4.0
GPS with A-GPS
FM Radio with RDS
USB OTG
MicroUSB 2.0
3.5mm Audio Jack
Magnetometer
Accelerometer
Proximity Sensor
Ambient Light Sensor
3,000mAh Li-ion Battery (Non-removable)
STEPS
Requirements:
- PC
- USB Cable
- Brain
- Little bit of common sense on flashing
Download Links:Mediatek VCOM Drivers:
- Link
SP Flash Tool:
- Link
Flash 2 TWRP & Scatter File:
- Link
ETA-SuperSU-v2.52.zip:
- SuperSU link
Instructions:
1. Download all necessary files.
2. Install MTK Drivers
3. Extract SPFlash tool anywhere on your PC and flash2_twrp.zip
4. Copy the BETA-SuperSU-v2.52.zip to your phone.
5. Open flash_tool.exe, click on the Download Tab
6. Click Scatter-loading and browse for the scatter file(included in the flash2_twrp.zip)
7. Make sure flashing mode is set to "Download Only" and check mark only on the Recovery.
8. Click Download.
9. Turn off your phone, connect your phone to the PC and wait for the flashing to commence.
10. Green Ring image will show once flashing is completed.
11. Important: Disconnect your phone from the computer, press and hold Vol Up + Power.
12. Boot menu will show, select Recovery.
From the custom recovery, before rooting, backup your rom first.
To root:
1. On the TWRP Recovery, click Install.
2. Select BETA-SuperSU-v2.52.zip.
3. Flash it, then you can reboot as it is.
4. Enjoy your rooted AF2.
All files and credits belongs to:
Mr. Long NT of AF2 FB Group
NOTE: members of af2 group states that this method is bugged and you will lose OTA.
Please verify if someone successful in rooting this method. thanks
yabadap said:
NOTE: members of af2 group states that this method is bugged and you will lose OTA.
Click to expand...
Click to collapse
That is why, before rooting, it is said to backup first, besides, there is already a stock rom that is flashable via recovery.
dweller417 said:
Please verify if someone successful in rooting this method. thanks
Click to expand...
Click to collapse
Worked for me, most error they encounter is SPFT not reading their devices, and others (first batch buyers) said that their OTA was gone, but this, I am not fully aware of what do they mean.
It's work, thank you very very much.
kitipon said:
It's work, thank you very very much.
Click to expand...
Click to collapse
You're welcome. Rooting shouldn't be a problem though. Having a flashable stock rom is, might be my case only. In the AF2 FB group a recovery flashable is already done, but a SPFT one isn't, yet.
Facing a bug, can you help? Please
yabadap said:
NOTE: members of af2 group states that this method is bugged and you will lose OTA.
Click to expand...
Click to collapse
Hi, after rooting using this method, I can't install any app, from playstore as well as offline apk installation, playstore shows "error code:-504." Any idea or solution? BTW, I rebooted several times, wiped data and cache of play store and Google service framework and removed then readded my Google ID as suggested by other forums. No result...
Can I get the link for the Facebook group you are talking about
Can I get the link for the Facebook group you are talking about?
ade.sultan said:
Can I get the link for the Facebook group you are talking about?
Click to expand...
Click to collapse
Alcatel Flash 2 PH.
So who has tried this guide? I'm planning to purchase a Flash Plus 2 (Is it the same device?)