Related
Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Very nice Thanks for your hard work and good luck
CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).
Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.
Thanks
Thanks
Where are the screenshots?
please add some screenshots.
deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.
Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.
Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.
Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:
Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.
Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work
Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.
DISCLAIMER:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Hello Guys !
In this thread you will find my custom ROM And Recovery for the Wiko DarkMoon
Please be sure to read (and re-read) this carefully in order to avoid unnecessary questions.
Instructions and Frequently asked questions (FAQ):
For Instructions jump into post #2.
FAQ jump into post #3.
Wiko DarkMoon internal memory re-partition, jump into post #4.
How to Revert to the STOCK Rom / Recovery / Partition Layout, jump into post #4.
Recovery INFO
The salient features of Carliv Touch Recovery include:
Based on CWM 6.0.4.4
Full Touch Support
With features of Cannibal Open Touch
Aroma File Manager Support
Support for both Edify and Amend scripting allows flashing all ROMs
Touch screen button controls
Advanced Backup
Advanced Restore
Delete old backups
Persistent settings
User-defined backup locations
ADB Sideload
Update CTR v2.5 (30/07/2014)
Changelogs:
New Menu Layout
Tar + Gzip Backup Compression : ( "Backup/Restore" -> "Default Backup Format" )
Your Backups will be smaller now, just like on the old native CWM
Removed "wipe all" option from wipe menu ( if you need to wipe system, use "format system" from "mounts/storage")
Rearanged menu order in root menu to restore CWM order
There's now an "nvram backup/restore" menu in "carliv" section
The nvram partition will be backed up in clockworkmod/backup 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 of size 0x500000 (check your scatter) and if you have the nvram defined as /dev/nvram path 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.
some other small changes.
Changelogs
Android 4.2.2 (JB) Based custom ROM:
Changelog Build v1.0 (February 22 2014)
Based on official Android 4.2.2 ROM (WIKO DARKMOON Version 8)
Kernel 3.4.5
Custom Mods:
User customize-able installation based on AROMA installer
Pre-rooted with SuperSU (v1.93)
Debloated
Added BusyBox (v1.22.1 - Stericson)
Added Ad blocker (patched "host" file)
Ziplagned apks (better performance)
init.d support with performance scripts
Network, wifi, power saving, and several other tweeks
Updated APN's from CyanogenMOD repo
Added Performance Control (several CPU/System Mods)
Added in-built Xposed framework and Latest Gravity BOX module v2.9.7 (Several System Mods)
Acess To the Mediatek MTK Eng Mode
Added the following Android 4.4 KitKat Goodies:
Apps (Including Google Launcher - GEL, with Voice Search )
Bootanimation
QuickOffice
And other necessary system files
Kernel:
Insecure
Removed Mediatek debugger (mtk.aee.aed Daemon; etc)
USB Mass Storage as Default (instead of MTP)
GPL Compliance:Kernel 3.4.5
Github Kernel Repo
Downloads:Dev-Host
WIKO_DarkMoon_JB_4.2.2_Stable_v1.0.zip - 386.12 MB
Mod_extended_USRDATA_2.5GB.zip - 7.07 MB
MT65xx_USB_VCOM_drivers.zip - 403.65 KB
Wiko_Recovery_and_FlashTool.zip - 12.54 MB
Credits:
SuperDragonPT
Wiko
Carliv (Awesome CWM based Recovery)
iBotPeaches, brut.all (for apktool)
amarullz (for AROMA Installer)
Chainfire (for SuperSU)
rovo89 (for the AWESOME Xposed Framework), Learn More Here
C3C076 (For the AWESOME Xposed GravityBox module), Learn More Here
bgcngm(For Maintaining the Gbox JB Branch)
h0rn3t and educk (for Performance Control), Learn More Here
XDA:DevDB Information
[RECOVERY] [ROM] Wiko DarkMoon (MT6582) [MULTILANG] , ROM for the Android General
Contributors
superdragonpt
Source Code: https://github.com/dragonpt/Kernel_Wiko_DarkMoon_Custom
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-02-22
Created 2014-02-22
Last Updated 2015-02-14
How to flash custom recovery:
Make Sure your Phone is fully Charged
Make an Full Backup of your files (Photos/Contacts, etc)
Download The MT65xx_USB_VCOM_drivers.zip
Install The Mediatek VCOM Drivers (For Detailed Drivers instalation Instructions, please check this thread)
Download The Wiko Recovery and FlashTool
Extract the .zip and you'll see two folders "Recovery" and "SP_Flash_Tool"
Open "SP_Flash_Tool" > Flash_tool.exe > Scatter-Loading> And select the "MT6582_Android_scatter.txt" from the "Recovery" Folder
Turn OFF your Phone
Press "Download" (don't worry with the pop-up "Download-Warning" Message), press YES
Connect Your Phone to PC (Turned OFF) , The Flash Progress should beginn, when its succesfully Finished A Green Ring will shown.
Congrats The Recovery is installed
How to enter into recovery mode:
With the Phone completely turned off...
Press and hold VOL. UP + VOL DOWN + POWER keys and turn on the phone.
Keep holding the keys, wait until you see on Phone:
Code:
"Recovery Mode: Volume UP"
"Factory Mode: Volume Down"
Then Press on VOL. UP key, and Recovery will load.
Navigation under recovery mode:
As soon as the splash logo disappears, Carliv Touch Recovery menu will appear. Navigation is Full Touch.
You can also use VOLUME keys (navigate up with VOL. UP and navigate down with VOL. DOWN) and POWER key to apply the action.
Scroll Pages under Recovery: To Scroll page down you have to swipe right, and for scroll page up to swipe left. Also swipe left for Go Back.
Aroma File Manager:
This Recovery Supports the Aroma File Manager
Whats this? Check here
Download the Aroma File Manager
Then just copy the aroma .*zip into the "Clockworkmod" folder on the root of your SD Card
Flashing The ROM:
Copy The ROM to The External SDCard
On Recovery:
Wipe Menu> Wipe All Data - PreFlash (Select YES - Wipe All)
Wipe Dalvik Cache (Select YES - Wipe Dalvik Cache)
Install zip > Choose zip SDCard (Select the location of the ROM.zip)
And Follow The On-Screen AROMA Installer Instructions
In the End the Phone will Reboot Itself
The first Boot will take some minutes (it's normal)
F.A.Q
Q: How Can i acess The MTK Eng Mode?
A: GravityBox >Engineering Mode
Q: What Mods can i do on the Eng.Mode?
A: There are alot of things you can do, the two most common are:
Increasing volume Level:
MTK Menu> Hardware Testing> Audio> On the "headset mode" and "LoundSpeaker Mode" set max values to 145 (The max is 160, but i dont advise it, stay safe and use the 145 value)
Speed up the GPS reception :
(Before Going to the MTK Menu)
Open the app "FasterGPS", and give it root permissions
Choose your Continent, your region (at this point, your gps is properly configured with your country *.ntp values)
(Now on MTK Menu ...)
MTK Menu> Location> Location Based Service> On the "AGPS" tab, tick the "Enable A-GPS", and on the "EPO" tab, tick "Enable EPO" and "Auto Download" , this last option will download the EPO files it requires an data connection.
Start the app "GPS Status", in the first Satts Lock, you need to wait a little bit (it can take up to 15m, be sure you are in an Open Area).
When you get an good lock, on Satts, your DONE.
A: I dont see the Development Options, how can i acess it?
Q: Unlocking the Development Options:
Go to "Settings" > "About Phone"
Then tap 7 times on the "Build Number"
Q: Where are the Development Options?
A: Settings> Developer Options
Q: What is the Performance Control?
A: Its an Control Panel, where you can Change / managed the CPU Governors/ IO Shedulers / among several other things.
Q: The Launcher sometimes seems an bit laggy
A: Go to Settings> Developer Options> on "Window animation scale" set it to .5x, and on "Transition animation scale" set it to .5x
Q: I really like your work, how can i thank you?
A: You can press the "THANKS" button, and if you want, you can donate some beers to me
Wiko DarkMoon internal memory re-partition
Mod Extended Userdata v1 ( 2GB ) --> Removed / Use the v2
This Mod will extend userdata partition to 2GB (stock size is 1GB) and the rest of the space will remain for the internal sdcard
NOTE: Make an FULL backup of your Rom under Recovery, and don't forget to also backup your Internal SDCard since it will be full erased
Instructions:
Download the Mod extended USRDATA.zip
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt from the Internal_2GB_Mod Dir
Press Download
After flashing is complete, boot into recovery mode and format /data (under Mounts and Storage Menu)
Optionally, if you want to restore previously saved userdata, go to backup / restore > and restore data (advanced restore feature)
Profit
Mod Extended Userdata v2 (2.5 GB)
This Mod will extend userdata partition to 2.5GB (stock size is 1GB) and the rest of the space will remain for the internal sdcard
NOTE: Make an FULL backup of your Rom under Recovery, and don't forget to also backup your Internal SDCard since it will be full erased
Instructions:
Download the Mod extended USRDATA_2.5GB.zip
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt from the Internal_2.5GB_Mod Dir
Press Download
After flashing is complete, boot into recovery mode and format /data (under Mounts and Storage Menu)
Optionally, if you want to restore previously saved userdata, go to backup / restore > and restore data (advanced restore feature)
Profit
Reverting to the Stock ROM
This will revert back your phone to STOCK (including the stock recovery), in case you need to send your phone to the Service Center
Instructions:
Go to Wiko's website and download the latest Rom Version:
http://fr.wikomobile.com/maj.php?telephone=131
Follow the instructions given ...
Older instructions:
Download the DARKMOON_JB4.2.2._Stock Rom-wiko_rev8.zip
Use the SPFlashTool that i provided with the CWM Recovery .zip
Make sure phone is fully charged
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt
Press Download
After flashing is complete,you'll see an green circle
Profit
Thanks. Can you add some screenshots?
h3lder said:
Thanks. Can you add some screenshots?
Click to expand...
Click to collapse
Was Uploading, check under the ScreenShots TAB
Regards
I doubt:
on step "How to flash custom recovery" - before you can do this you need to have already rooted the device?
can you please add how to root the device? it will be nice to complete better all the info.. but is already great!
congrats and thanks you! as soon as i by my wiko darkmoon i will definitely try it!
sapoide said:
I doubt:
on step "How to flash custom recovery" - before you can do this you need to have already rooted the device?
can you please add how to root the device? it will be nice to complete better all the info.. but is already great!
congrats and thanks you! as soon as i by my wiko darkmoon i will definitely try it!
Click to expand...
Click to collapse
Hi
You can root with framaroot, but i dont think thats necessary.
Just flash The recovery, then The ROM.
Regards
superdragonpt said:
Hi
You can root with framaroot, but i dont think thats necessary.
Just flash The recovery, then The ROM.
Regards
Click to expand...
Click to collapse
Ok understood, thanks
Do this rom will work with my Xolo Q700S?
Sent from my Q700S using xda app-developers app
superdragonpt:
Where can you please downloaded the source code for kernel mt6582? Can you give me a link please?
Or: Your sources kernel what you gave to download are original (unchanged)?
Edit:
OK. I found where you can download the source. Sorry for the spam.
http://forum.xda-developers.com/showthread.php?t=2645756
http://forum.xda-developers.com/showthread.php?t=2650513
Hi
You guys are all crazy with the MTK leaked sources, but do you even have an clue what those sources are?
You cant just compile an source that's customize for other phone , thinking it will work on yours.
There's a lot of work to be done, and you need an huge amount of luck to have your phone drivers available in that source.
This said, I will appreciate that people avoid off-topic and other phones talk in this thread.
This ROM and recovery will only work on wiko darkmoon and Micromax a200 (clone).
If your using this ROM as a base for another MT6582 phone, please be an gentlemen and give proper credits.
Regards
Added Internal USRDATA Mod to the OP
Check post #4
Enjoy
superdragonpt said:
Added Internal USRDATA Mod to the OP
Check post #4
Enjoy
Click to expand...
Click to collapse
Great work, thanks.
Do you know by any chance if there is any option to add languages to this rom? Wiko doesn't include many languages. I can use locale2 from google play, but that only translates some of the functions.
skydancer79 said:
Great work, thanks.
Do you know by any chance if there is any option to add languages to this rom? Wiko doesn't include many languages. I can use locale2 from google play, but that only translates some of the functions.
Click to expand...
Click to collapse
The ROM is multi language.
What language where you looking for?
Regards
superdragonpt said:
The ROM is multi language.
What language where you looking for?
Regards
Click to expand...
Click to collapse
Slovenian...most android phones have it. Moto G had the same "problem"
skydancer79 said:
Slovenian...most android phones have it. Moto G had the same "problem"
Click to expand...
Click to collapse
Hi
Yes i know, when i made a MIUI rom for my old ZTE v970, i had an hard time trying to find the proper strings for your language.
Even on stock roms from big brands, its very rare to find support for that language.
Im trying to merge and revise some strings from various sources, maybe in an future version.
Regards
superdragonpt said:
Hi
Yes i know, when i made a MIUI rom for my old ZTE v970, i had an hard time trying to find the proper strings for your language.
Even on stock roms from big brands, its very rare to find support for that language.
Im trying to merge and revise some strings from various sources, maybe in an future version.
Regards
Click to expand...
Click to collapse
Great, that would be awsome.
As for rarity of my language, I find it quite well supported. Google Nexus has it, all Samsungs have it, so does HTC, Sony... I know Prestigio and Gsmart have it. CM also. It's not a big deal, but nevertheless - I wouldn't mind having it
Great ROM btw, very customizable.
skydancer79 said:
Great, that would be awsome.
As for rarity of my language, I find it quite well supported. Google Nexus has it, all Samsungs have it, so does HTC, Sony... I know Prestigio and Gsmart have it. CM also. It's not a big deal, but nevertheless - I wouldn't mind having it
Great ROM btw, very customizable.
Click to expand...
Click to collapse
Hi
Well good news and bad news
The good:
I managed to Build an UNOFFICIAL Lewa Rom for our device, currently fixing the lastest issues and adding multi-language support.
So since im currently working on this language strings, might as well use that work for this rom also.
Preview pics:
http://i.imgur.com/VAGpQI3.png
Http://imgur.com/1IADxZx
Http://imgur.com/1C56EO6
The bad:
From what i gather until now, only about 100 slovenian strings are compatible (this is less than 5% of overall translation files), will keep looking
Regards
superdragonpt said:
Hi
Well good news and bad news
The good:
I managed to Build an UNOFFICIAL Lewa Rom for our device, currently fixing the lastest issues and adding multi-language support.
So since im currently working on this language strings, might as well use that work for this rom also.
Preview pics:
http://i.imgur.com/VAGpQI3.png
Http://imgur.com/1IADxZx
Http://imgur.com/1C56EO6
The bad:
From what i gather until now, only about 100 slovenian strings are compatible (this is less than 5% of overall translation files), will keep looking
Regards
Click to expand...
Click to collapse
So is this ROM fully functional? I mean no bugs? For English language.. I could test it on my Turbo mini
{
"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"
}
This is a thread for the ZTE T815/Telstra Tempo T815. I hope other users who have this device might get some benefit and enjoyment out of this thread.
BACKUP!
Start here for a guide to extracting a ROM dump from your T815 and processing it to create a backup you can use to restore your phone if anything goes wrong for you
Custom Recovery and Root Method
I have ported PhilZ Touch Recovery V6 (6.59.0 - based on CWM 6.0.5.1) to the T815. Installation method and rooting instructions can be found here
Custom ROMs (list will be updated as new ROMs are posted)
[ROM] [PussyFap V3][KitKat] ZTE T815 - here
[ROM] [Pure LG G3][KitKat] ZTE T815 - here
[ROM] [Cherry ROM Lite v2.1][KitKat 4.4.2] ZTE T815 - here
[ROM][Amgoo OS][KitKat4.4.4] ZTE T815 - here
How install custom recovery and root ZTE T815
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's 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 knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
I have been able to port PhilZ Touch Recovery V6 (6.59.0 - based on CWM 6.0.5.1) to the ZTE T815. To flash this recovery to your device you will need the following:
- USB VCOM Driver - Installation tutorial and download of driver here (Don't worry that it says MTK6577, it works fine with MTK6572 based devices)
- Smart Phone Flash Tool - Download for all versions can be found here - scroll to the bottom of the list to find latest version
- Scatter file and custom recovery image - download here
- PC and USB cable
Method:
1. Follow the tutorial and install the USB VCOM driver.
2. Install SP Flash Tool - once installed, run as administrator.
3. On the "Download" tab page, click the box on the right hand side named "Scatter-loading". Browse to the location where you saved the downloaded "MT6572_Android_scatter.txt" file, select it and click "Open".
4. In the lower section of SP Flash Tool screen, tick the box next to RECOVERY. This is the ONLY box that is to be selected.
5. On the RECOVERY line, go across to the to the blank cell under the "Location" heading and click on it. Now browse to the location where you saved the downloaded "recovery.img", select it and click "Open". The line should now show the location of the file.
6. Turn off your phone and remove the battery.
7. On SP Flash Tool, click the "Download" button at the top of the page and THEN connect your phone to the PC via the USB cable (battery still out).
8. All going well, you should now see the download progress being displayed across the bottom of the screen. Once completed, you will see a big green tick displayed in the middle of the screen. Success! Your phone now has PhilZ Touch Recovery installed.
To access Recovery Mode, from power off hold down the volume up button and power button together for around 6 seconds (press and hold volume up first then press and hold power). You will now see the recovery main menu.
Root: (after you have your custom recovery installed)
1. Download supersu.zip (latest version) here - thanks to @Chainfire
2. Send zip file to your SD card.
3. Boot into recovery and install zip from SD card.
4. Reboot - your device is now rooted.
Important:
Make yourself a backup. (Note: the external SD card is /storage/sdcard1 - if you try to backup to sdcard0, you will run out of memory.)
To bring this PhilZ Touch Recovery to you, thanks and credit must be given to the following:
- Phil3759
- Koush for having created and maintaining cwm
- Cyanogenmod for making all this possible
- Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
- Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
- Chenglu for his unpacking tools and porting i9505: Huge credit
- kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
- sk8erwitskil for his recovery source, a great place to start learning
- shoe63 for his help from the start across many devices
- DooMLoRD for his work and help with Sony
- [NUT] for his ports to Sony
- wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
- dougiebee for his work on fixing time on many Qualcom devices
- ausdim for all the support in developing kernels for i9505
- dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
- Chainfire for his support (stock recovery flash) and all his work for the Android community
- 1966zippy for bringing it to the ZTE T815!
[ROM] [PussyFap V3][KitKat] ZTE T815
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I have had my first success at porting a custom ROM to the T815, so I present to you ***** Fap V3.
Requirements
BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
You must be rooted.
You must have a custom recovery installed
You must have experience flashing but if not, feel free to ask questions before flashing.
Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the PussyFap_v3_T815.zip file and install. Go back to "Wipe and Format Options"and wipe Cache and wipe Dalvik/ART Cache. Go back to main menu and hit "Reboot System Now". Enjoy exploring this custom ROM.
Note: Google Play Store is an older version but it will update to the latest version once you have signed in and have an active internet connection.
Download ***** Fap V3 ROM for ZTE T815 here
Features:
Full Lollipop UI
Lollipop Framework
Tinted Status Bar
Nice settings
Smooth performance
Performance Control
Engineer Mode
Init.d Tweaks
Battery Icon Styles
Dynamic system bars
Progress bar animation
Known Bugs:
- GPS not working Appears it is working, just MT6572 GPS is really crap!
- shows 2 sim slots instead of 1
- I have not used this ROM to make calls so there may be issues that are radio/sim related. Let me know what you find and I will try to fix.
Screenshots:
Full Credits:
Team *****
Thanks for your helpful information
PetaX8 said:
Thanks for your helpful information
Click to expand...
Click to collapse
You're very welcome.
Sent from my GT-I9506 using XDA-Developers mobile app
[ROM] [Pure LG G3][KitKat] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Another ROM for you to enjoy - Pure LG G3
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Pure LG G3_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Pure LG G3 ROM for ZTE T815 here
Features:
- 99% LG G3 UI
- LG G3 boot animation
- Smart Pause
- Palm Motion
Bugs:
- Let me know
Screenshots:
Credits:
- Muhammad Restu
- Team LG Developers
- needrom
- Smart Four Team
Thanks for updating me on this 1966zippy. Its worked perfectly for me
millsb0mb said:
Thanks for updating me on this 1966zippy. Its worked perfectly for me
Click to expand...
Click to collapse
Glad to hear. Hope you enjoy the ROMs.
1966zippy said:
Glad to hear. Hope you enjoy the ROMs.
Click to expand...
Click to collapse
Works significantly better thanks
zte t815 it says recovery mode i updated it from then it is happening
frank bird said:
zte t815 it says recovery mode i updated it from then it is happening
Click to expand...
Click to collapse
If you are in recovery mode with a purple background and a green android in the middle then you are in the recovery mode that we set out to achieve. Just touch "go back" on the screen until you are at the main menu and then select "reboot phone now" and you will boot to your stock OS.
If you are on the black recovery screen (stock recovery), it means that some part of the process did not work and you didn't get the custom recovery flashed correctly. You can navigate through the stock recovery menu by pressing volume down to select the line with the option you want and then confirm your selection with volume up (which I think goes against "normal" thinking and is a trap for making incorrect selections, so be careful, says he who has fallen for this same trap and blitzed his phone!).
You need to get back to the "reboot now" option and then try the process again (be sure you have the USB VCOM drivers installed properly.):good:
[ROM] [Cherry ROM Lite v2.1][KitKat 4.4.2] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here is another ROM for you to explore - Cherry ROM Lite v2.1
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Cherry ROM Lite_v2.1_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Cherry ROM Lite v2.1 for ZTE T815 here
Features:
- Amazing performance
- Audio enhancements
- Cyanogen file manager and browser
- Added GPS settings for better access to satellites
- SuperSU pre-installed
- Excellent RAM management
Bugs:
- Let me know
Screenshots:
Credits:
- Dertio Acos
- Unknown Porting Team
- Computer+Android
- 1966zippy for porting to T815
is there any new roms coming in? what about CyanogenMod? are you guys making a "pure" android ROM for T815? i didn't like the ***** fap rom as it doesn't work well with small screen, lg rom is perfect but slow, is the cherry rom near stock??
PS: great work keep up. if you could maybe remove the dual sim notification as i only have 1 sim slot, also maybe its a good idea to upload de-bloated stock rom for t815
Jesus Chen said:
is there any new roms coming in? what about CyanogenMod? are you guys making a "pure" android ROM for T815? i didn't like the ***** fap rom as it doesn't work well with small screen, lg rom is perfect but slow, is the cherry rom near stock??
PS: great work keep up. if you could maybe remove the dual sim notification as i only have 1 sim slot, also maybe its a good idea to upload de-bloated stock rom for t815
Click to expand...
Click to collapse
Thanks for your feedback. I do have plans to upload more ROMs as I port them and get most of the bugs squashed but, as I am on a massive learning curve regarding porting myself, it is taking a bit of time. I don't reckon I've done too bad so far for only a couple of weeks! I will leave the CyanogenMod ROM for a while, as it looks like it is one of the more complicated ROMs to port, but I will try to get it up here at some stage. I am working with a pure android ROM at the moment so hopefully that works out and I can upload it soon. The Cherry ROM is debloated and has some nice features but the only way to find out is to give it a whirl.
As for the dual sim thing, I am still trying to work out how to modify the ROM to only show the one sim (as I said, still got "L" plates on) and once I work out how to do this I will repost the corrected ROMs. I agree that a debloated stock ROM is a great idea so I will work on that when time permits.:highfive:
thanks
1966zippy said:
Thanks for your feedback. I do have plans to upload more ROMs as I port them and get most of the bugs squashed but, as I am on a massive learning curve regarding porting myself, it is taking a bit of time. I don't reckon I've done too bad so far for only a couple of weeks! I will leave the CyanogenMod ROM for a while, as it looks like it is one of the more complicated ROMs to port, but I will try to get it up here at some stage. I am working with a pure android ROM at the moment so hopefully that works out and I can upload it soon. The Cherry ROM is debloated and has some nice features but the only way to find out is to give it a whirl.
As for the dual sim thing, I am still trying to work out how to modify the ROM to only show the one sim (as I said, still got "L" plates on) and once I work out how to do this I will repost the corrected ROMs. I agree that a debloated stock ROM is a great idea so I will work on that when time permits.:highfive:
Click to expand...
Click to collapse
thanks for the lightning fast reply, ill be looking forward to pure stock android with support for single sim. keep up the good work and you da real MVP. perhaps check out alcatel pixi 3 xda http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624 as the 4 inch version have very similar spec with t815. (i have 4.5 inch with much fast/newer chipset,alias it doesn't have any custom rom) :good::good::good:
Jesus Chen said:
thanks for the lightning fast reply, ill be looking forward to pure stock android with support for single sim. keep up the good work and you da real MVP. perhaps check out alcatel pixi 3 xda http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624 as the 4 inch version have very similar spec with t815. (i have 4.5 inch with much fast/newer chipset,alias it doesn't have any custom rom) :good::good::good:
Click to expand...
Click to collapse
LOL!:laugh: Around 6 month ago I was looking for a cheap phone to mod and my final choice was between the Tempo T815 and Pixi 3(4), the Pixi winning out because it was $5 cheaper. It was the right choice as I found @kirito9's thread which was crammed full of info and ROMs. I learned a few things about working with the Mediatek MT6572 chipset and porting ROM's (thanks again to @kirito9 here, absolute legend) over there, all the while watching a small thread about the Tempo T815 where they had all stopped posting as no one could get root on the T815. I thought I could take the bits that I have worked out and apply them to this little supported device so here we are. I am no expert on all things MT6572 but I am working things out slowly so hang in there and I will put more ROMs and helpful info up here when I can.
[ROM] [Amgoo OS][KitKat 4.4.4] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Amgoo OS_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Amgoo OS for ZTE T815 here
Features:
- Android Lollipop Inspired UI
- Deodexed
- Zipaligned
- Debloated
- Rooted (KingUser)
- Updated GAPPS (Google Chrome(Default Browser), Google App, Google Play Services, Hangouts(Default Messenger), Google Play Music(Default Music Player), Google Now Launcher(Default Launcher), Google Play Store)
- Modded System App (Lollipop Themed)
- Xposed Modules Integrated in Settings.apk
- Amgoo os Boot Logo
Bugs:
- Sound works OK but I can't get it as loud as I would like
- Anything else, let me know
Screenshots: (Apologies for poor screens but this ROM is worth trying for it's UFO live wallpaper alone!)
Credits:
- Nayeem Hossen For Porting This ROM
- Mou For making the boot logo
- 1966zippy for porting to T815
Full ROM Dump Backup & Read Back Method
This guide will show you how to make a full ROM dump of your ZTE T815 (Mediatek MT6572) device. It can be used to make a full backup at anytime but I strongly suggest that you follow this procedure prior to making any modifications to your device. That way you will always have a completely stock unmodified image to return to if things go bad or aren't what you expected. Don't say you haven't been warned!
Things you will need:
- ADB Drivers - here or here
- USB VCOM Driver - Installation tutorial and download of driver here (Don't worry that it says MTK6577, it works fine with MTK6572 based devices)
- MTK Droid Tools - here - scroll to the bottom of the list to find latest version
- Smart Phone Flash Tool - Download for all versions can be found here - scroll to the bottom of the list to find latest version
- Notepad++ - here
- A PC and USB Cable
Preparations:
- Install ADB Drivers system wide and follow tutorial to install USB VCOM Driver
- Install Notepad++
- Create a folder somewhere convenient (e.g. desktop) and give it a name related to phone/mods etc.
- Into this folder, install MTK Droid Tools and SP Flash Tool.
Process:
Make Scatter File
Run MTK Droid Tools as administrator. Once the program has started, connect your phone via the USB cable and you will see that your phone information loads up on the left side of the page. Below this you will see a button that says "Block Map". Press it. You will now see a screen displaying Block Info and at the bottom left a button "Create scatter file". Press this button and save the "MT6572_Android_scatter.txt" file to the folder that you made earlier. Don't close MTK Droid Tools, just minimise it at this stage and unplug your phone.
Read Back ROM From Phone
Run SP Flash Tool as administrator. By default it starts on the Download tab. You will see a button labelled "Scatter-loading" at the top right of the screen. Press this button and direct it to the "MT6572_Android_scatter.txt" that you just saved. Once loaded, change to the "readback" tab along the top and then click "Add". A line is added below and you need to click in the blank area under the heading "File". Browse to the location where you want to save your ROM dump (in that same folder again would be appropriate) make sure you retain the file name of "ROM_0" and press "Save".
There is now a dialogue box that pops up, "Readback block start address". The "Type" must remain as Hex. The "Start address" should also remain as it is - 0x0000000000000000. The "Length" address is determined by the address of the partition we wish to finish our ROM dump at. I would suggest that we use the address of the last partition in the phone. To find out this address we need to examine the scatter file. Open the scatter file with Notepad++ (this will keep the formatting in place). Easy way is to right click on the file and select "Edit with Notepad++" from drop down menu. Scroll to the bottom of the page and find the FAT partition information. The "linear_start_addr:" value here is where to end the ROM dump so carefully copy the address and paste into the "Readback block start address" dialogue in the "Length" field. (e.g. the linear start address of my FAT partition is 0x97140000 so this is the figure I enter into "Length").
Note: If you have already been using your phone before doing this backup method, you may wish to create a ROM dump that excludes your personal info. If so, you might choose not include the CACHE and USERDATA partitions in the backup so you would end the ROM dump at the linear start address of the CACHE partition (in my phone this is 0x36340000, for example).
Once the "Length" value is entered, press OK. Turn your phone off at this stage. Once it is fully powered down, click "Read Back" and then connect your powered off phone to the USB cable and all things going well you should see the progress bar at the bottom go blue and start moving. Once completed successfully you will see a green circle with a tick in it. Done! Disconnect your phone.
Process ROM For Use With SPFT
Turn your phone back on and when ready reconnect to MTK Droid Tools. Change to "root, backup, recovery" tab and press on the button labelled "To process file ROM_ from Flash Tool". Browse to your modding folder location and open "ROM_0". The processing will start and you will be prompted to make a CWM recovery automatically. Answer "No" and then "Cancel" when it asks to choose recovery. You will see the process in action and it will end with the message "Task is complete" at the end of the script. The folder containing this processed backup is located in yourmoddingfolder/Mtk_Droid_Tool_v2.5.3/backups. If you examine the contents of this processed ROM backup you will note that the output folder now also contains a scatter.txt file.
Restore process to follow - edit soon:good:
1966zippy said:
This guide will show you how to make a full ROM dump of your ZTE T815 (Mediatek MT6572) device. It can be used to make a full backup at anytime but I strongly suggest that you follow this procedure prior to making any modifications to your device. That way you will always have a completely stock unmodified image to return to if things go bad or aren't what you expected. Don't say you haven't been warned!
Click to expand...
Click to collapse
Can I borrow this post?
kirito9 said:
Can I borrow this port?
Click to expand...
Click to collapse
Assuming port was supposed to be post, you absolutely can borrow it, mate. [emoji106]
Sent from my GT-I9506 using XDA-Developers mobile app
#-------------------------Disclaimer----------------------------#
I am in no way responsible for dead NAND/EMMC chips, SD cards Lost basebands, nuclear war or anything else for that matter YOU the users are soley responsible for any and all actions you make the build is 100% tested & confirmed working on UBIFS R11 max chinaphone with board variant Q6_M144_GT-018_MB_1.0
#-----------------------Device info----------------------------#
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
Board Variant: HS_Q6_MB_V1.0
Storage Capacity=512Mb (4Gb ext through recovery)
Ram Capacity= 497Mb
Resolution= 480×854
#-----------------CyanogenmodOS--------------------------#
Version = 11
SDK-ver = 4.4.4
SDK-API = 20
B-TYPE = userdebug
Build id = XNG3C
Linux Kernel = 3.4.67
LCD- density = 240
LCD-Dpi = 320
• Deodexed
• IO_scheduler set to CFQ
• Performance adjustments
• Preloaded with Gapps
• Cyanogen account support
• CyanogenMod Logo
• Ram flag optimisations
• Default runtime set to art
• Voice unlock support
• Pre rooted with Cyanogenmod SU 1.34
• addon.d support
• init.d support
• BT NFC support
• addon.d & init.d slinked in cpio in bootimg
• Custom CM bootimg with storage fix.
• Ad and popup blockers
• CM ambient updater
• CM InCallUi
• google voice search
• CM Device management
• CM SetupWiz
• factory test mode [ *#*#0#*#* ]
• CM Live lockscreen
• CM MusicFX
• CM Trebuchet Launcher
• Chrome based browser
• CM Voice +
• Voice command support
• Camera interpolated and tweaked
• camera path changed to added cameraserver in vendor/bin/cameraserver instead of system/bin/mediaserver
• Added Clearmotion props to default & build.prop
• Added Clearmotion config to /etc
• Added Clearmotion support libs
• Added Clearmotion FW to /lib
#---------------------------NOTICE------------------------------#
I do this in my free time DO NOT ask for Eta's,
Includes storage modified CM boot.img which will be flashed with the rom please use the partiton sd card option in advanced options in recovery to make up to a 4096mb /data partition before transferring zip to sd and flashing.
#----------------------------BUGS------------------------------#
• update #003 is having a whinge with storage for downloaded apps from store so they wont install after download will be fixed in build #004,
• NFC is working properly but you must purchase NFC bluetooth module tags to support nfc transfer, i have compiled & added an nfc.ko module to use bluetooth instead of newer modules which use the wifi reciever as the antenna and due to there being no NFC compatibile HW on these extremely poor low end devices i do not wish to see comments about this as a bug.
#-------------------------LINKS------------------------------#
CM CTR recovery.
https://drive.google.com/file/d/1UErBsSe2DLFEtcgwXz-hZR_fQINxpn9H/view?usp=drivesdk
Stock touch recovery to replace original
https://drive.google.com/file/d/14Y-WQHDLfqlEdjmu-PTujNqGkkUpcpLn/view?usp=drivesdk
CyanogenmodOS #001-BETA 20190412
https://drive.google.com/file/d/1Xuf-gSHPHr5CGsZjFu3pgT44FdR5GFx5/view?usp=drivesdk
CyanogenmodOS update #002 20190414
https://drive.google.com/file/d/19Nt1pVo8ruvTCugsgejtMQvJDe2xZIb7/view?usp=drivesdk
CyanogenmodOS update #003 20190504
[ Has play store issue ]
https://drive.google.com/file/d/1D4sCf1oflvSTFJxFzH1WwMJL_1j8H5-G/view?usp=drivesdk
Welcome to CyanogenMod 11
BUILD #002 is up get it from the OP
CHANGELOG
Camera works now with slow motion & fast motion video recording, picture quality is still **** but is tons better than it was on stock rom.
Rebuilt the system layout and merged most /vendor files and folders to /system
Fixed gallery keeps stopping error even though it wasnt
Cleaned up the GUI scaling to produce cleaner icons etc etc changelog is in /etc for anyone that wants to look
Changed the Live lockscreen wallpaper to something much simpler & better looking.
Converted entire system to single sim & removed Gemini where i could & set props to disable what i couldnt find of it, repathed ril to run through mtk-ril.so also added init.volte.rc, volte_imsm.so/volte_stack.files to help ril call clarity as certain parts of the stack are interacting with ril even though its a GSM Radio
Added getenforce & setenforce to /bin and file_contexts to try and get my init.rc props for setenforce to run the kernel permissively for some extra init processes, BUT setenforce for some reason is receiving permission denied cannot symlink so i hope to have this completed & working in build #003
Added /product/build.prop dir to deal with zram for swap & ext4 /data partitiion under logical boot partitions.
Added new android apple crime screen power off logo
Added some misc ringtones, notification tones and ringtones other than the cyanogen tones.
Nice Work Matty1993!!
You have been a busy bee :highfive:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
bigrammy said:
You have been a busy bee :highfive:
Click to expand...
Click to collapse
Haha yeah one of my old projects ive been meaning to get finished for ages, finding out how to attach android to UBIFS on top of UBI was a pain in the ass lol got to experiment with ril on this one as it was dual sim and tried running gemini through it but as it was a source build dual sim compatibility dosent work so had to depract gemini and set single sim still been working on the tuba build tho taking my time with it as sony really like to mix things up, also finishing a lineage OS 14.1 build for Alcatel Pixi 3.5 that was from source also but dualsim works on this one even though this phones a single sim phone haha go figure lol
DJ Robby said:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
Click to expand...
Click to collapse
What model is your R11 max clone phone it must be HS_Q6_MB_V1.0 board revision or it wont boot on your device and i will need to build one for your revision if so as the kernel will be different,
You can find the board variant by taking the backing off the phone and looking at the sim slot see pic attached,
Check this out first or youll brick it 100% i gaurantee it, google how to take a firmware backup using SP flash tool before doing anything SP flash tool can be downloaded from here aswell as the MTK Vcom drivers for flash tool,
https://spflashtool.com
If your board is different i need the BOOTIMG.file from your SP Tool backup so please do this first before anything or i wont be able to build you anything as i need your stock kernel from boot.img to decompile and make changes for my rom aswell as the boot.img is highly modifed with CM source
Hello,
I can't find a number like that, I looked everywhere.
Here is a full backup of the phone: https://drive.google.com/file/d/15P9KutXb0FrxHRTj4qrQ-KW94XA6J2SI/view?usp=sharing
The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
DJ Robby said:
Hello,
I can't find a number like that, I looked everywhere.
I have the boot.img, I will edit this message with the boot.img when I have a chance. The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
Click to expand...
Click to collapse
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Matty1993 said:
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Click to expand...
Click to collapse
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Hey mate,
Sweet ill get onto it and post link here to a new thread ill make for your variant r11 max.
Ive got a new build just about ready also which is build #003 so ill start your variant from #003 which has vast improvements from build #002
# edit
Glad you didnt flash your R10 is eMMC ext4 fs and not ubifs just finished the boot.img off anyhow
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Matty1993 said:
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Click to expand...
Click to collapse
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
DJ Robby said:
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
Click to expand...
Click to collapse
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Matty1993 said:
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Click to expand...
Click to collapse
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
DJ Robby said:
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
Click to expand...
Click to collapse
Rom will be ready soon it takes time to convert things to ext4 from ubifs patience is a must for these things unless you want a brick ? Lol plus ive got another 5 projects on the go so lots to do and not enough time to do it all, just finished lineage 14.1 android 7.1.2 for alactel pixi 4027A using a stock kernel on android 4.4.4
as for TWRP probably not due to the size of your recovery and the size of most twrp is about 3mb to short for your partition youll need to use cwm ive added mount points to the script for your data & system partitions so if it dont flash mount in CWM and then flash if it still dosent use the take a log option in my installer and forward it to me so i can see if it was the mounts or what,
Also i havent set meta-data for permissions ive set perm & perm_recursive which is specifically for CWM so please flash with that,
I make no gaurantee it will boot as i dont have one in front of me to work on & debug but everything should work ok though link will be up in roughly half hour max
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Matty1993 said:
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Click to expand...
Click to collapse
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
DJ Robby said:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
Click to expand...
Click to collapse
Hey mate i took a look at the log,
For some reason it didnt symlink any of the system files or set the perms for them
Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct
In the script
Format was ok
Mounting was ok
Extract system files was ok
I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,
The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,
To restore your backup using SP flash tool open flash tool, select the scatter box,
Navigate to your backuo folder & double click on the scatter_file.txt,
All of your partitions and files will automatically load up for flash,
Change the download mode to download only
Power off phone click start download
Connect phone & wait for flash
I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
Hello, this is a test build for coral users (will work on crosshatch/blueline later).
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
- allow repacking of TWRP from boot.img
- magisk not working currently on repacked image
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
- fix repacking magisk with TWRP
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_twrp_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
Glad to see this!
Finally TWRPified! Thanks for bringing this to us!
bigbiff said:
[RECOVERY] TWRP 3.4.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me
Click to expand...
Click to collapse
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Daisymae said:
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Click to expand...
Click to collapse
Same here ?
I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:
I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001
Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw
If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Surge1223 said:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Click to expand...
Click to collapse
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
bigbiff said:
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
Click to expand...
Click to collapse
Sure, no problem. logs attached
Surge1223 said:
Sure, no problem. logs attached
Click to expand...
Click to collapse
Thanks, did you try test2?
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
Boggling my mind that it works on my coral with out linking issues.
Can you post the results of getprop please?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
bigbiff said:
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
Click to expand...
Click to collapse
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
Click to expand...
Click to collapse
Wait did you want getprop while in recovery or booted?
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Wait did you want getprop while in recovery or booted?
Click to expand...
Click to collapse
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
bigbiff said:
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
Click to expand...
Click to collapse
heres getprop
https://hastebin.com/eluqagolub.md
heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl
Got some $$ coming your way Monday OP.
Thank you for this. It could not have been easy
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
dhacke said:
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
Click to expand...
Click to collapse
No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.