I created a separate thread for KITKAT 4.4.2. OFFICIAL version have been realeased for Alcatel One Touch / TCL S950 Idol X starting from BUILD 1008. This ROM is official for TCL S950 mobile IDOL X but working perfectly with Alcatel One Touch Idol X because they are the same hardware (only different brand).
{
"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"
}
I am following this Chinese Thread and this russian forum 4PDA for reference.
I am not taking credits for this work. Im just sharing these to those who can't download from the chinese forums / russian forum.
DOWNLOAD AND INSTALLATION
Well, I assume this is not the first time you will flash your phone.
If not... I will make a tutorial or provide links on how to flash using SP Flash Tool / Flashtool Mod.
Anyway lets start!
First you have to download the KITKAT ROM to be installed to your device. Extract it and put it a convenient location like on your desktop. Download the Philz Touch Custom Recovery and extract it to desktop. Now we are ready to [email protected]!
Run Flashtoolmod / SP Flash Tool
1. Load SCATTER FILE from the folder where you extracted the ROM.
2. Manually select CUSTPACK.img
3. Click the RECOVERY and select the location where you extracted the custom recovery.img file.
4. Make sure that PRE-LOADER and MOBILE INFO are not chosen (UNCHECKED)!
5. Click DOWNLOAD.
6. Turn OFF your phone (wait for the device until it vibrate) then connect your device via USB.
7. Wait for the Green Circle. Flashing is done! Turn ON your phone.
IMPORTANT!
After successful flashing, ROOT you device by flashing SUPERSU via Recovery.
Download SuperSU 2.01
*****DO NOT EXTRACT and put it inside the phone storage*****
*****reboot into RECOVERY*****
*****go to ADVANCE FUNCTIONS*****
Code:
Sdcard target: /data/media/0 [B]SHOULD GET[/B] /data/media
*****restart to take effect. (GO BACK > POWER OPTIONS > REBOOT RECOVERY)*****
*****go to INSTALL ZIP > CHOOSE FROM SD CARD and chose the supersu.zip file*****
*****after flashing is done WIPE CACHE and DALVIC CACHE*****
BUILD VERSIONS:
1009S950_KK442_150123
- Optimized calls time standby screen lights up
- After power restoration power display shows the power is inconsistent with the start charging before the percentage
- Fixed in the camera screen, press the power button to light up the screen lock screen and then press the return key does not return to idle screen directly
- And more added to the firmware WhatsApp
1008 S950_KK442_010415
Optimized weather pattern clarity
flashlight brightness optimization problem too dark
wallpaper optimization problem is slow to load
optimization switch machine animation for TCL dynamic effects
1007 S950_KK442_121914
Optimization Night and low light conditions, reducing the ISO values camera flash mode automatically improve photo realism
Repair equalizer button in the music player comes with software problems missing
Radio does not work to fix the problem properly
1006 S950_KK442_121214
Save the picture prompt repair the wrong question
to repair the memory capacity to import contacts from SD card or phone to your Gmail account will be force close issue
repair call runs in the background, entering the video player click the play button again, the video can be playback problems
1005 S950_KK442_112814
After repairing the opening and closing flight mode execution, SIM cards can not be registered to network problems
Repair few phone prompts low battery shutdown shutdown, a night without charge and then boot, power display allowed the problem
to repair after few phone long standby, power-down and fast Problem
fixes phone signal to identify the different state does not comply with Andrews KitKat style
shooting photos after the repair is no problem marking the best photo
restoration SMS notification option in the setup menu is not in the same issue of individual columns of
a particular repair set contact ringtone unsuccessful problem
repaired minority received phone messages event time is not accurate
to optimize the accuracy of the G-sensor to work
off the charging animation shows the percentage increase in the mark
1004 S950_KK442_111414
※ repair the lock screen missed calls, call recording time Sort confusion
※ repair set specific ringtone to a contact, the preview does not sound problems ringtones
※ repair MMS is limited to 300KB maximum
※ when repairing a new contact or group, the screen flashes problems
※ part iron should recommend that this new Google service S950 software version, which is built into ROM package google all relevant apk. This version is for iron users want to experience the full version of the system, not like friends can continue Lite experience.
1003 S950_KK442_1031
optimized view pictures in the gallery or photo display black box problem
optimization in power saving mode Tips user can not adjust the screen brightness
to optimize the phone battery from the charging rate of 99% to 100% of the [repair] repair restart the phone switch Animation anomalies close power saving mode after the repair, the phone all set to return to the previous repair to enter a short message interface occasionally stops unexpectedly problem [New] Super Hero N3 additional notes gadget can be freely written record of daily life and improve the experience of large-screen phone
1002 S950_KK442_101714
Bluetooth headsets optimized quality
optimized interface under horizontal screen display and operating experience
on the phone keypad to optimize the user experience vibration feedback
Click to return to the recording screen repair button issues arise unexpectedly stopped
repairing the problem is not synchronized data roaming
repair long press an invalid key issues be set up
to repair the problem automatically dim the screen brightness does not turn on after a power saving mode
clock repair problems in the fields displayed in English
1001 S950_KK442_092614
Hang up the phone after the repair menu does not automatically hide problems
Recovery from backstage back recorder interface, recording interface confusion
Repair input method selection box and calls the interface layer order problem
Repair Clear recent apps, quit recording application problem but the recording icon is still displayed
After the repair call back, call icon and lock screen still shows missed calls Tips
Click on an image to enlarge Repair, picture appears beating problem
After repairing burst mode using slide view unresponsive problem
Repair view pictures and turn the screen, the status bar disappears problem
Repair Music delete screen appears black box problem
Some repair teleconference interface content display is not clear question
Repair time translation app for
Repair entering FM problem does not automatically play again
Tip no vibration problem repair calls
UI interface display optimization settings
Optimized write email recipient address pop-up box size
Known issue, set the interface to add google account will flash back, subsequent versions will repair
XDA:DevDB Information
Kitkat 4.4.2 for Alcatel OT 6040D / TCL S950 Idol X, ROM for the Android General
Contributors
bryanjay420, BZzzz3, All the people fro 4PDA forum
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Kitkat 4.4.2
Version Information
Status: Stable
Current Stable Version: 01009
Stable Release Date: 2015-01-23
Created 2014-10-25
Last Updated 2015-08-20
Custom ROMS for KITKAT
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.
*/
AOSP IDOL X 4.4.2
Original Thread from 4PDA
CHANGELOG:
v.1
- Naked android
- Xposed gravity box and work (when you install the unlock button on the volume sometimes decreases the brightness)
- The core of the port dimkin
- Installation of an ordinary memory layout
- To work as root, you need rekaveri a whale cat (the one in the header)
- I once fell off Route (problem was solved by installing a super su from under rekaveri)
- Threads are applied using xtheme
- Patch to disable the lower touch button works
- All perky and shustrenko))
v1.1
- Phone with Russian language
- The camera now works
- Improved scrolling
- Added application control
- Gallery and the camera from Lenovo
- A bit blind to file
- Improved multi-tasking
INSTALLATION:
The firmware is present with Aroma Installer, all installation through it.
Put the ROM.zip file on your PHONE STORAGE
Reboot to RECOVERY
In Recovery go to WIPE AND FORMAT OPTIONS
Click CLEAN TO INSTALL NEW ROM
After finished wipe chose INSTALL ZIP then CHOOSE ZIP FROM SDCARD and choose the ROM.zip
Follow the instruction on Aroma Installer (the language is in Russian, just click next)
DOWNLOAD:
AOSP IDOL X Ver. 1.1 190115
AOSP IDOL X Ver. 1 150115
Click to expand...
Click to collapse
PORT FIRMWARE FROM LG G3
Original Thread from 4PDA
CHANGELOG:
Like anything special. Its graphics and only.
Advanced Menu reboot corrected chart, indicators of network traffic, batteries (huge selection), edits, finishing touch, etc.
INSTALLATION:
Put the ROM.zip and the DATA400SYSTEM826_2 Patch on your PHONE STORAGE
Reboot to RECOVERY
In Recovery go to WIPE AND FORMAT OPTIONS
Wipe FORMAT DATA, CLEAR CACHE and CLEAR DALVIC CACHE
Then...
*****IMPORTANT*****
Install this DATA400SYSTEM826_2 Patch
After flashing the patch now we can proceed in flashing the rom
INSTALL ZIP then CHOOSE ZIP FROM SDCARD and choose the ROM.zip
DOWNLOAD:
LG_G3_TCL_Idol_X
Click to expand...
Click to collapse
ROM dimkin_76 L reliz-ANDROID 4.4.3
Original Thread from 4PDA
CHANGELOG:
All I will not describe a lot of things
Very powerful system optimization
Propisanie capacity of your battery and strong optimization is made in English is called .........: D, shorter notification battery at 4% and is not strong battery discharge at 14%
Full screen photo
100% quality photos with the photo on the appointment of contact, cut all under your screen resolution
A set of messages by voice, without connecting to Internet
Extended reboot
Translated and expanded inzhenerki
Shorter now and not all spomnyu: D
Selection of the core and not only all cm. Configured
Powersave
Frequency is always equal to the minimum. Sometimes included in order to save the battery when the battery is low or off screen.
Performance
Frequency is always equal to the maximum. Used for the tests, obtain stable values in the benchmarks, or during charging and connecting to a computer. This is a faster mode than fixing a minimum equal to the maximum frequency (in ondemand for example), because there is no frequent requests to change it.
Userspace
For manual setting of frequencies that are not supported by the kernel. Not recommended and almost nobody uses.
Ondemand
Is present in most of the nuclei by default. At specified intervals (sampling_rate: ~ 10-20 milliseconds) checks the CPU usage and when it reaches a certain threshold (up_threshold ~ 80%) increases the frequency to the maximum until the CPU is not reduced.
Does not contain profiles for turning off the screen, so it is often set to powersave.
Hotplug
Based on Ondemand. Its distinctive ability - on multicore devices can disable kernel at low loads.
INSTALLATION:
Put the ROM.zip and the DATA400SYSTEM826_2 Patch on your PHONE STORAGE
Reboot to RECOVERY
In Recovery go to WIPE AND FORMAT OPTIONS
Wipe FORMAT DATA, CLEAR CACHE and CLEAR DALVIC CACHE
Then...
*****IMPORTANT*****
Install this DATA400SYSTEM826_2 Patch
After flashing the patch now we can proceed in flashing the rom
INSTALL ZIP then CHOOSE ZIP FROM SDCARD and choose the ROM.zip
DOWNLOAD:
ROM_dimkin_76_TCL_S950_reliz
Click to expand...
Click to collapse
Port firmware IOCEAN X8 on ART
Original Thread from 4PDA
CHANGELOG:
Firmware immediately translated into job ART'e, so that the download will last longer.
INSTALLATION:
Put the ROM.zip and the DATA400SYSTEM826_2 Patch on your PHONE STORAGE
Reboot to RECOVERY
In Recovery go to WIPE AND FORMAT OPTIONS
Wipe FORMAT DATA, CLEAR CACHE and CLEAR DALVIC CACHE
Then...
*****IMPORTANT*****
Install this DATA400SYSTEM826_2 Patch
After flashing the patch now we can proceed in flashing the rom
INSTALL ZIP then CHOOSE ZIP FROM SDCARD and choose the ROM.zip
DOWNLOAD:
TCL_IOCEAN_X8_ART
Click to expand...
Click to collapse
XPERIA Z3 OS 4.4.2
Original Thread from 4PDA
CHANGELOG:
Port with Lenovo, only corrected power_profile.xml in the frame. Normal operation of the memory on odnosimah not guarantee for 2 simah should be all set.
INSTALLATION:
Put the ROM.zip and the DATA400SYSTEM826_2 Patch on your PHONE STORAGE
Reboot to RECOVERY
In Recovery go to WIPE AND FORMAT OPTIONS
Wipe FORMAT DATA, CLEAR CACHE and CLEAR DALVIC CACHE
Then...
*****IMPORTANT*****
Install this DATA400SYSTEM826_2 Patch
After flashing the patch now we can proceed in flashing the rom
INSTALL ZIP then CHOOSE ZIP FROM SDCARD and choose the ROM.zip
DOWNLOAD:
Idol_X_XPERIA_Z3_OS442
Click to expand...
Click to collapse
To be updated...
Altenative Download and Add-Ons
1. Detect your device as ALCATEL
Look for this items in build.prop and change.
Code:
ro.product.model=ALCATEL ONE TOUCH 6040D
ro.product.name=ALCATEL_ONE_TOUCH_6040D
ro.product.board=ALCATEL_ONE_TOUCH_6040D
ro.product.display.model=ALCATEL ONE TOUCH 6040D
2. Change notification drawer background
Code:
decompile SystemUI-res.apk custpack/JRD_custres/app replace the file on res/drawable-xxhdpi/notification_panel_bg.png
3. Install Xperia Z3 Keyboard with lots of language supported
Code:
flash via recovery, wipe dalvic/cache
4. Change the default click sound
Download Xperia.ogg
Download Lewa.ogg
Code:
rename the file to tap.ogg and replace tap.ogg in system/media/audio/ui
5. Philz Touch Recovery 6.57.9 for Kitkat 4.4.2
Code:
flash using Mobile Uncle Tools or SP Flash Tool
go to the Advanced Functions on Sdcard target: / data / media / 0 / (should get / data / media /)
-Restart (Go back-Power Options-Reboot Recovery)
6. Identifier pro_info. Identify your device as Alcatel to TCL and vice versa for upgrading via Mobile Upgrade and TCL Updater
Download FlashToolMod
Code:
flash using Flash Tool Mod
7. Add Home Icon is Setting
Code:
disassemble Settings-res.apk in custpack/JRD_custres/app
go to \res\drawable-xxhdpi\ and replace ic_settings_home.png
8. Network Icons on the left
Code:
decompile systemui-res.apk go to res\layout and replace the files
9. Modding Battery Icon
i. Extract systemui-res.apk. go to res\drawable\stat_sys_battery.xml
ii. Under these lines
Code:
<?xml version="1.0" encoding="utf-8"?>
<level-list
xmlns:android="http://schemas.android.com/apk/res/android">
iii. Replace the texts with these
Code:
<item android:drawable="@drawable/stat_sys_battery_0" android:maxLevel="0" />
<item android:drawable="@drawable/stat_sys_battery_1" android:maxLevel="1" />
<item android:drawable="@drawable/stat_sys_battery_2" android:maxLevel="2" />
<item android:drawable="@drawable/stat_sys_battery_3" android:maxLevel="3" />
<item android:drawable="@drawable/stat_sys_battery_4" android:maxLevel="4" />
<item android:drawable="@drawable/stat_sys_battery_5" android:maxLevel="5" />
<item android:drawable="@drawable/stat_sys_battery_6" android:maxLevel="6" />
<item android:drawable="@drawable/stat_sys_battery_7" android:maxLevel="7" />
<item android:drawable="@drawable/stat_sys_battery_8" android:maxLevel="8" />
<item android:drawable="@drawable/stat_sys_battery_9" android:maxLevel="9" />
<item android:drawable="@drawable/stat_sys_battery_10" android:maxLevel="10" />
<item android:drawable="@drawable/stat_sys_battery_11" android:maxLevel="11" />
<item android:drawable="@drawable/stat_sys_battery_12" android:maxLevel="12" />
<item android:drawable="@drawable/stat_sys_battery_13" android:maxLevel="13" />
<item android:drawable="@drawable/stat_sys_battery_14" android:maxLevel="14" />
<item android:drawable="@drawable/stat_sys_battery_15" android:maxLevel="15" />
<item android:drawable="@drawable/stat_sys_battery_16" android:maxLevel="16" />
<item android:drawable="@drawable/stat_sys_battery_17" android:maxLevel="17" />
<item android:drawable="@drawable/stat_sys_battery_18" android:maxLevel="18" />
<item android:drawable="@drawable/stat_sys_battery_19" android:maxLevel="19" />
<item android:drawable="@drawable/stat_sys_battery_20" android:maxLevel="20" />
<item android:drawable="@drawable/stat_sys_battery_21" android:maxLevel="21" />
<item android:drawable="@drawable/stat_sys_battery_22" android:maxLevel="22" />
<item android:drawable="@drawable/stat_sys_battery_23" android:maxLevel="23" />
<item android:drawable="@drawable/stat_sys_battery_24" android:maxLevel="24" />
<item android:drawable="@drawable/stat_sys_battery_25" android:maxLevel="25" />
<item android:drawable="@drawable/stat_sys_battery_26" android:maxLevel="26" />
<item android:drawable="@drawable/stat_sys_battery_27" android:maxLevel="27" />
<item android:drawable="@drawable/stat_sys_battery_28" android:maxLevel="28" />
<item android:drawable="@drawable/stat_sys_battery_29" android:maxLevel="29" />
<item android:drawable="@drawable/stat_sys_battery_30" android:maxLevel="30" />
<item android:drawable="@drawable/stat_sys_battery_31" android:maxLevel="31" />
<item android:drawable="@drawable/stat_sys_battery_32" android:maxLevel="32" />
<item android:drawable="@drawable/stat_sys_battery_33" android:maxLevel="33" />
<item android:drawable="@drawable/stat_sys_battery_34" android:maxLevel="34" />
<item android:drawable="@drawable/stat_sys_battery_35" android:maxLevel="35" />
<item android:drawable="@drawable/stat_sys_battery_36" android:maxLevel="36" />
<item android:drawable="@drawable/stat_sys_battery_37" android:maxLevel="37" />
<item android:drawable="@drawable/stat_sys_battery_38" android:maxLevel="38" />
<item android:drawable="@drawable/stat_sys_battery_39" android:maxLevel="39" />
<item android:drawable="@drawable/stat_sys_battery_40" android:maxLevel="40" />
<item android:drawable="@drawable/stat_sys_battery_41" android:maxLevel="41" />
<item android:drawable="@drawable/stat_sys_battery_42" android:maxLevel="42" />
<item android:drawable="@drawable/stat_sys_battery_43" android:maxLevel="43" />
<item android:drawable="@drawable/stat_sys_battery_44" android:maxLevel="44" />
<item android:drawable="@drawable/stat_sys_battery_45" android:maxLevel="45" />
<item android:drawable="@drawable/stat_sys_battery_46" android:maxLevel="46" />
<item android:drawable="@drawable/stat_sys_battery_47" android:maxLevel="47" />
<item android:drawable="@drawable/stat_sys_battery_48" android:maxLevel="48" />
<item android:drawable="@drawable/stat_sys_battery_49" android:maxLevel="49" />
<item android:drawable="@drawable/stat_sys_battery_50" android:maxLevel="50" />
<item android:drawable="@drawable/stat_sys_battery_51" android:maxLevel="51" />
<item android:drawable="@drawable/stat_sys_battery_52" android:maxLevel="52" />
<item android:drawable="@drawable/stat_sys_battery_53" android:maxLevel="53" />
<item android:drawable="@drawable/stat_sys_battery_54" android:maxLevel="54" />
<item android:drawable="@drawable/stat_sys_battery_55" android:maxLevel="55" />
<item android:drawable="@drawable/stat_sys_battery_56" android:maxLevel="56" />
<item android:drawable="@drawable/stat_sys_battery_57" android:maxLevel="57" />
<item android:drawable="@drawable/stat_sys_battery_58" android:maxLevel="58" />
<item android:drawable="@drawable/stat_sys_battery_59" android:maxLevel="59" />
<item android:drawable="@drawable/stat_sys_battery_60" android:maxLevel="60" />
<item android:drawable="@drawable/stat_sys_battery_61" android:maxLevel="61" />
<item android:drawable="@drawable/stat_sys_battery_62" android:maxLevel="62" />
<item android:drawable="@drawable/stat_sys_battery_63" android:maxLevel="63" />
<item android:drawable="@drawable/stat_sys_battery_64" android:maxLevel="64" />
<item android:drawable="@drawable/stat_sys_battery_65" android:maxLevel="65" />
<item android:drawable="@drawable/stat_sys_battery_66" android:maxLevel="66" />
<item android:drawable="@drawable/stat_sys_battery_67" android:maxLevel="67" />
<item android:drawable="@drawable/stat_sys_battery_68" android:maxLevel="68" />
<item android:drawable="@drawable/stat_sys_battery_69" android:maxLevel="69" />
<item android:drawable="@drawable/stat_sys_battery_70" android:maxLevel="70" />
<item android:drawable="@drawable/stat_sys_battery_71" android:maxLevel="71" />
<item android:drawable="@drawable/stat_sys_battery_72" android:maxLevel="72" />
<item android:drawable="@drawable/stat_sys_battery_73" android:maxLevel="73" />
<item android:drawable="@drawable/stat_sys_battery_74" android:maxLevel="74" />
<item android:drawable="@drawable/stat_sys_battery_75" android:maxLevel="75" />
<item android:drawable="@drawable/stat_sys_battery_76" android:maxLevel="76" />
<item android:drawable="@drawable/stat_sys_battery_77" android:maxLevel="77" />
<item android:drawable="@drawable/stat_sys_battery_78" android:maxLevel="78" />
<item android:drawable="@drawable/stat_sys_battery_79" android:maxLevel="79" />
<item android:drawable="@drawable/stat_sys_battery_80" android:maxLevel="80" />
<item android:drawable="@drawable/stat_sys_battery_81" android:maxLevel="81" />
<item android:drawable="@drawable/stat_sys_battery_82" android:maxLevel="82" />
<item android:drawable="@drawable/stat_sys_battery_83" android:maxLevel="83" />
<item android:drawable="@drawable/stat_sys_battery_84" android:maxLevel="84" />
<item android:drawable="@drawable/stat_sys_battery_85" android:maxLevel="85" />
<item android:drawable="@drawable/stat_sys_battery_86" android:maxLevel="86" />
<item android:drawable="@drawable/stat_sys_battery_87" android:maxLevel="87" />
<item android:drawable="@drawable/stat_sys_battery_88" android:maxLevel="88" />
<item android:drawable="@drawable/stat_sys_battery_89" android:maxLevel="89" />
<item android:drawable="@drawable/stat_sys_battery_90" android:maxLevel="90" />
<item android:drawable="@drawable/stat_sys_battery_91" android:maxLevel="91" />
<item android:drawable="@drawable/stat_sys_battery_92" android:maxLevel="92" />
<item android:drawable="@drawable/stat_sys_battery_93" android:maxLevel="93" />
<item android:drawable="@drawable/stat_sys_battery_94" android:maxLevel="94" />
<item android:drawable="@drawable/stat_sys_battery_95" android:maxLevel="95" />
<item android:drawable="@drawable/stat_sys_battery_96" android:maxLevel="96" />
<item android:drawable="@drawable/stat_sys_battery_97" android:maxLevel="97" />
<item android:drawable="@drawable/stat_sys_battery_98" android:maxLevel="98" />
<item android:drawable="@drawable/stat_sys_battery_99" android:maxLevel="99" />
<item android:drawable="@drawable/stat_sys_battery_100" android:maxLevel="100" />
iv. Extract systemui-res.apk. go to res\drawable\stat_sys_battery_charge.xml
v. Under these lines
Code:
<?xml version="1.0" encoding="utf-8"?>
<level-list
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:maxLevel="0">
<animation-list android:oneshot="false"
xmlns:android="http://schemas.android.com/apk/res/android">
vi. Replace the texts with these.
vii. Download the file and copy the xml codes and replace the stock.
viii. Go to res\drawable-xxhdpi and replace the files you can find in this site. Pick one and replace the stocks.
Known Issues
how to escape from bootloops
the solution (credit to the one who share this) :good:
Plug the phone to your charger
press the power button, the screen will turn off and the notification led will light
as soon as the led turns on, unplug the charger (one has to be very quick)
wait a bit to be certain that the phone stays off
plug the charger again and wait some seconds that the screen turns on, as soon has the screen is on, unplug the charger.
Now you should be out of boot loop
start the phone in recovery mode (power + vol+) wipe data/factory reset or if you have backup then restore backup
or if you dont have any custom recovery you can update via mobile upgrade / tcl updater (i do this a lot but will take a lot of time, you can watch movie while taking time to finish installing rom)
or you can flash your device with new rom using sp flash tool.
Sometimes you have to do it lot of times on a trial and error basis
tested it lot of times :good:
Click to expand...
Click to collapse
nvram warning err=0x10 solution
sportistasd said:
i tried but there is still error,
anyway wifi working ok but in the list there is nvram warning err=0x10 is listed as an open wifi network
i searched throu forum and i found a vople of solution to fix that error i try few but nothing there are few more method so i hope i will find solution for that error on earlier version of betas i havent exipirenced that bug only on this from 14.11.
IF ANYONE EXIPIRIENCED THIS PROBLEM HERE IS SOLUTION:
Step # 1 : Switch on WiFi adapter on your phone.
Step # 2 : Go to 'About Phone' from Settings and note your phone's Wi-Fi MAC Address mentioned there. It should lok like xx:xx:xx:xx:xx:xx (xx = value of Mac Add.)
Step # 3 : Switch off WiFi adapter on your phone
Step # 5 : Launch 'Total Commander' application on your phone and navigate to File system root/data/nvram/APCFG/APRDEB and copy one file named 'WIFI' from there to the SD Card of your phone
Step # 6 : Copy this file i.e. WIFI from your SD card to Desktop on your laptop/desktop
Step # 7 : Launch 'HxD-Hexeditor' on your laptop/desktop and click on OPEN or Ctrl+O and select WIFI file (copied as per Step # 6) from desktop
Step # 8 : Refer to the first raw in the opened file and go to column no. 04
Step # 9 : Insert value of your actual MAC Address (as per Step # 2) in column 04 to 09 (Ensure that none of the value is ZERO) and SAVE this change
Step # 10 : Close Hexeditor and copy changed WIFI file from your desktop to the SD card of your phone. Delete older WIFI file from SD Card before copying this file.
Step # 11 : Once the file is copied to SD card, launch Total Commander application and move this file from SD card root to File system root/data/nvram/APCFG/APRDEB
Step # 12 : Reboot your phone
Click to expand...
Click to collapse
Reserve
for future use
thanks for your great post.
I dl all the files and open SP-Flash, change also the recovery .img.
But the SEC-Row box is empty. Whisout sec-row flash is not possible. Which file I should select from the 4.4 package?
Thanks
gregor4711 said:
thanks for your great post.
I dl all the files and open SP-Flash, change also the recovery .img.
But the SEC-Row box is empty. Whisout sec-row flash is not possible. Which file I should select from the 4.4 package?
Thanks
Click to expand...
Click to collapse
i flashed this rom without sec_rom. just select manually the custpack and the recovery. by the way, rename the custom recovery to recovery.img
how cool is that.
many Thanks work very well!
what is the different between dalwic and ART lib?
will all old apps run also with ART mode?
do we have an other boot animation? Alcatel sucs
many Thanks again.
sorry...off topics...but can u teach me how to disable capacitive button on 6040D...thanks
gregor4711 said:
how cool is that.
what is the different between dalwic and ART lib?
will all old apps run also with ART mode?
Click to expand...
Click to collapse
Nope, there are apps in the market that don't like the ART lib, but you can test it and with problems try an alternative app with the same function.
The most populair apps like whatsapp/facebook and so on are running fine with ART.
gregor4711 said:
do we have an other boot animation? Alcatel sucs
Click to expand...
Click to collapse
You can flash another one with the SP Flash tool.
Did anyone try xposed with this Kitkat beta? Does it work?
mmsandi said:
Did anyone try xposed with this Kitkat beta? Does it work?
Click to expand...
Click to collapse
i think you can try to install latest xposed but if you install gravity box and some other modules it will cause bootloop. you cant use xposed v2.3.1 in this because the framework will not work. need the latest version for kitkat
kitkat 4.4.2 build 1002
https://cloud.mail.ru/public/89ce0a4...4.4.2_1017.zip
bryanjay420 said:
https://cloud.mail.ru/public/89ce0a4...4.4.2_1017.zip
Click to expand...
Click to collapse
The working link: https://cloud.mail.ru/public/89ce0a4a9100/S950_KK4.4.2_1017.zip
laav said:
The working link: https://cloud.mail.ru/public/89ce0a4a9100/S950_KK4.4.2_1017.zip
Click to expand...
Click to collapse
ohh the link i post is where i downloaded it. but anyways it was already saved in my 4shared account
I'm using kitkat without root. When i download and try to flash recovery only in sp tools, but after click "download" wait for 10 mins also no any response. Any idea?
wweeping said:
I'm using kitkat without root. When i download and try to flash recovery only in sp tools, but after click "download" wait for 10 mins also no any response. Any idea?
Click to expand...
Click to collapse
is it working before?
Ok already, it need to wait almost 40mins.
hai....in this new rom...should i remove some .txt file just like kk4.4.2_0926.zip.....or i just simply flash it without some modify..thank
skoolished said:
hai....in this new rom...should i remove some .txt file just like kk4.4.2_0926.zip.....or i just simply flash it without some modify..thank
Click to expand...
Click to collapse
The 1017 doesn't have an .txt extension inside. Push the scatter inside Flash Tools and fill in the blank marks. Use te recovery placed in this topic instead of the official one!
Related
I would like to know how to uninstall xposed before I install it on my android lollipop phone in-case there is something you have to do before installing.
Also how come on a forum about xposed there is nothing about how to uninstall the thing????!
Anyway... thank you!
<br />
You can remove Xposed framework by this way:<br />
<br />
1. Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:<br />
2. Go into /system/bin/ and delete app_process32 and app_process32_xposed<br />
3. Rename app_process32_original to app_process32<br />
4. Delete dex2oat and rename dex2oat.orig to dex2oat<br />
5. Repeat the above step for oatdump and patchoat<br />
6. Go up a directory and then into the lib directory<br />
7. Delete libart.so and rename libart.so.orig to libart.so<br />
8. Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so<br />
9. Delete libxposed_art.so<br />
10. Go up a directory and delete xposed.prop<br />
11. Go into framework directory and delete XposedBridge.jar<br />
12. Reboot your device.<br/>
Or dirty flash your rom again.
Sent from my bacon!!!!!
TWRP for Z5 Compact E5823
Credits first
Most of the ideas and some of the code are kang'd from @dl12345 and his TWRP v2.8.7.0 for Sony Z3+
The first release of this recovery was based on Zombie b1 by @Tommy-Geenexus
Known problems
Colors are a bit distorted - but I think it looks good (fixed)
Not working with encrypted phone (unconfirmed)
How to build
Not for beginners
Please contribute to my repositories by creating pull requests if you manage to fix any bugs
First, sync omnirom sources:
Code:
repo init -u git://github.com/omnirom/android.git -b android-5.1
repo sync
Waaaaaiiiiiit.
Create a local manifest:
Code:
mkdir .repo/local_manifests/
nano .repo/local_manifests/twrp.xml
Manifest contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="sony" fetch="git://github.com/sonyxperiadev/" />
<remote name="jackfagner" fetch="git://github.com/jackfagner/" />
<project path="device/sony/kitakami" name="twrp-device-sony-kitakami" groups="device" remote="jackfagner" revision="TWRP" />
<project path="device/sony/suzuran" name="twrp-device-sony-suzuran" groups="device" remote="jackfagner" revision="TWRP" />
<project path="kernel/sony/kitakami" name="twrp-kernel-sony-kitkami" groups="device" remote="jackfagner" revision="TWRP" />
<project path="vendor/sony/system/dtbtool" name="twrp_vendor_sony_system_dtbtool" groups="device" remote="jackfagner" revision="TRWP-28.0.A.8.251" />
<project path="vendor/sony/system/mkivybootimg" name="twrp_vendor_sony_system_mkivybootimg" groups="device" remote="jackfagner" revision="TRWP-28.0.A.8.251" />
<project path="vendor/sony/system/thermanager" name="thermanager" groups="device" remote="sony" revision="master" />
<project path="vendor/sony/system/macaddrsetup" name="macaddrsetup" groups="device" remote="sony" revision="master" />
<project path="vendor/sony/system/timekeep" name="timekeep" groups="device" remote="sony" revision="master" />
</manifest>
Sync again.
Code:
repo sync
Download Sony binaries and unzip inside repo dir:
Code:
unzip SW_binaries_for_Xperia_AOSP_L_MR1_v12.zip
Setup your environment variables (ARCH and CROSS_COMPILE), then build as usual:
Code:
source build/envsetup.sh && lunch
make -j 4 recoveryimage
Binary download
Current (kernel and recovery):
TWRP for Z5C, based on kernel 32.0.A.6.152 (v2) (10.11.15)
GDrive mirror for all you MEGA haters
Old versions:
TWRP for Z5C, based on kernel 32.0.A.6.152 (v1) (07.11.15)
TWRP for Z5C, based on kernel 32.0.A.5.32 (29.10.15)
TWRP for Z5C, first release (28.10.15) - recovery only
Instructions
Boot using:
Code:
fastboot boot recovery.img
Or, better yet, flash to your phone (will replace your kernel):
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
When you see an amber LED, press volume buttons a few times to boot to TWRP.
Instructions to kernel developers (I'm looking at you @Tommy-Geenexus)
Like most Sony phones, the Z5/Z5C cannot boot from the recovery (FOTAKernel) partition.
This is "solved" by letting the kernel boot image chain load the recovery ramdisk.
I was looking around for a nice script to do this, but - no offence - they were all pretty bad.
So I wrote a less bad one:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
nilezon said:
Dear XDA, I present to you:
fully (...or possibly not) working TWRP for Z5 Compact E5823.
More info soon. Until then:
Download:
TWRP for Z5C
Boot using:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Im also trying to get that work ... How did you solved the sensor.te error?
Sent from my mint using XDA Free mobile app
Nice work, boots fine, most things seem fine.
However colors are inverted, i suppose it needs some pixel format tuning there.
Else, great work!
Edit: @nilezon
Add
Code:
TW_BRIGHTNESS_PATH := /sys/class/leds/wled/brightness
TW_MAX_BRIGHTNESS := 3511
to fix brightness slider.
Tommy-Geenexus said:
Add
Code:
TW_BRIGHTNESS_PATH := /sys/class/leds/wled/brightness
TW_MAX_BRIGHTNESS := 3511
to fix brightness slider.
Click to expand...
Click to collapse
Thank you! Will do.
I just want to get a nicer build environment up. This first build required a lot of hacking.
I'm hoping to publish a manifest file for easy building, including regular Z5.
nilezon said:
Thank you! Will do.
I just want to get a nicer build environment up. This first build required a lot of hacking.
I'm hoping to publish a manifest file for easy building, including regular Z5.
Click to expand...
Click to collapse
That would be good would like to see the source ^^
And while you are testing around with pixelformat may have a look here:
https://gerrit.omnirom.org/#/c/14475/
I know this is not a mtk device but maybe thats the pixelformat?
Sent from my mint using XDA Free mobile app
@nilezon a mirror for your file here: link
mega sin't available in every country, so..
I've got to jump in with this. Thanks for your effort! This beauty works like a charm. I just made the first back up with this twrp and the outcome looks great. Overall size of back up file suprized me but otherwise it's all good and I kinda like this color layout more than the usual blue. Great job!
Ok, maybe I jumped thru the roof little too early. Is this meant to be launched with fastboot or is this integrated recovery after flashing it?? I couldn't get straight to twrp recovery without fastboot.
Anyway this is a great opening and one step closer to real thing ?
Thanks alot!
Mmmiku said:
Ok, maybe I jumped thru the roof little too early. Is this meant to be launched with fastboot or is this integrated recovery after flashing it?? I couldn't get straight to twrp recovery without fastboot.
Anyway this is a great opening and one step closer to real thing
Thanks alot!
Click to expand...
Click to collapse
I'm working on a kernel that can boot to recovery using key-combo.
nilezon said:
I'm working on a kernel that can boot to recovery using key-combo.
Click to expand...
Click to collapse
This is tricky as you must use the sony copyleft sources...look at my github. You can deconstruct my Z3+ recovery image for the ramdisk for a dual recovery-boot solution. I'm guessing that you could probably apply my Z3+ config almost unchanged for the Z5. I used CM 12.1 to build for the Z3+....
dl12345 said:
This is tricky as you must use the sony copyleft sources...look at my github. You can deconstruct my Z3+ recovery image for the ramdisk for a dual recovery-boot solution. I'm guessing that you could probably apply my Z3+ config almost unchanged for the Z5. I used CM 12.1 to build for the Z3+....
Click to expand...
Click to collapse
I've done this. Unpacked your Z3+ boot img and repacked it with my TWRP ramdisk and kernel cpio, and of course my copyleft kernel.
However, something seem wrong with the boot script, since it is always booting to the ramdisk-recovery.cpio.
I'm not fully satisfied with the ramdisk.cpio/ramdisk-recovery.cpio solution. I'm going to try writing an init.sh script that allows booting from FOTA without using any cpio's at all: regular ramdisk already in /, and recovery ramdisk is fetched from FOTA and overwriting / if recovery is requested.
New version!
Now you can flash recovery and boot it without using fastboot every time.
Edit:
New firmware (32.0.A.6.152) just released by Sony.
I will update the recovery and kernel when the source code is released.
nilezon said:
New version!
Now you can flash recovery and boot it without using fastboot every time.
Edit:
New firmware (32.0.A.6.152) just released by Sony.
I will update the recovery and kernel when the source code is released.
Click to expand...
Click to collapse
You, sir, are much appreciated! \m/
nilezon said:
New version!
Now you can flash recovery and boot it without using fastboot every time.
Edit:
New firmware (32.0.A.6.152) just released by Sony.
I will update the recovery and kernel when the source code is released.
Click to expand...
Click to collapse
For this we must have Z5C with bootloader unblocked ?
Hispa
hispanico957 said:
For this we must have Z5C with bootloader unblocked ?
Hispa
Click to expand...
Click to collapse
Yes.
nilezon said:
New version!
Now you can flash recovery and boot it without using fastboot every time.
Edit:
New firmware (32.0.A.6.152) just released by Sony.
I will update the recovery and kernel when the source code is released.
Click to expand...
Click to collapse
The Sources are already up, but they're unbuildable.
I had to fix like 40 compiler issues and am now left with the linker stuff.
They must be incomplete.
nilezon said:
I've done this. Unpacked your Z3+ boot img and repacked it with my TWRP ramdisk and kernel cpio, and of course my copyleft kernel.
However, something seem wrong with the boot script, since it is always booting to the ramdisk-recovery.cpio.
I'm not fully satisfied with the ramdisk.cpio/ramdisk-recovery.cpio solution. I'm going to try writing an init.sh script that allows booting from FOTA without using any cpio's at all: regular ramdisk already in /, and recovery ramdisk is fetched from FOTA and overwriting / if recovery is requested.
Click to expand...
Click to collapse
I tried this. It's difficult to get a robust solution. You're better off having a clean ramdisk and unpacking the boot ramdisk from a cpio archive.
The recovery ramdisk in cpio format is just a backup in case no image exists in the FOTA kernel partition - if one does then it's used instead.
dl12345 said:
I tried this. It's difficult to get a robust solution. You're better off having a clean ramdisk and unpacking the boot ramdisk from a cpio archive.
The recovery ramdisk in cpio format is just a backup in case no image exists in the FOTA kernel partition - if one does then it's used instead.
Click to expand...
Click to collapse
Ok. I understand your reasons, but I'm looking to create a solution that is as easy as possible for a 3rd party kernel developer to integrate. I think it works well right now:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
There is of course room for improvement. I will try to improve the script with a full cleanup of the ramdisk (excluding my /bootrec folder) before extracting the recovery cpio, but that is more of an aesthetic thing.
Another thing:
Do you have any idea why the colors get distorted? Did you have that problem on the Z3+/Z4?
Looks like kernel and twrp works great after updating with latest release 32.0.A.6.152. Reminder: after updating with FlashTool install boot.img and recovery.img thru fastboot and you have the whole set (root, twrp and zombie kernel) kicking Thanks again with your great job!
Tommy-Geenexus said:
The Sources are already up, but they're unbuildable.
I had to fix like 40 compiler issues and am now left with the linker stuff.
They must be incomplete.
Click to expand...
Click to collapse
Where? I can only find 32.0.A.6.115, not 32.0.A.6.152 ?
I have the Fire 2015 on FireOS 5.1.1
Rooted and has google play services.
In order to gain write access to the external SD with TitaniumBackup I modified the platform.xml as follows:
Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Upon reboot, I have no access to the microSD card using ES File Explorer. The internal partition sdcard is also not accessible and shows no files or folders. I can only view the system partition.
Additionally, I cannot access the internet, although I can connect to my wifi network.
When I try to write to the internal sd "0" partition, I see "open failed: EACCES (Permission denied)"
I tried removing the changes in the platform.xml file but I could not save them, even with root explorer turned on in ES File Explorer.
I installed fx explorer and its root module using adb. I was then able to edit the xml file, taking out my change, making it original. I rebooted the device and the issues still persist. I figured this would happen because I have read other users' report issues even when replacing the modified platform.xml with the original.
(I cannot access root with it using "adb root" as it returns "adbd cannot run as root in production builds")
I tried a factory reset. The issues still persist.
At this point I might have to wait until there is a method for custom recoveries on 5.1.1 in order format /system and flash a custom rom. I was fine with being on fireOS with root...I just wanted to use TitaniumBackup with the extSDcard. I should have picked a different method!
Any ideas?
Start over. Reinstall FireOS 5.1.1 > root > block OTA > add google play.
See the thread on restoring stock FireOS.
No luck
blueberry.sky said:
Start over. Reinstall FireOS 5.1.1 > root > block OTA > add google play.
See the thread on restoring stock FireOS.
Click to expand...
Click to collapse
Thanks for the reply, bluberry.sky
So I successfully sideloaded my firmware version. It didn't work.
It restored all the stock fireos apps and everything, keeping a couple non amazon apps I had pushed to it earlier. Wifi settings were saved too. Issues with wifi and extSDcard remain.
I thought for sure your suggestion would work...
You can wipe with FlashFire
FlashFire worked for me. Since I saw it was possible to flash SlimLP with 5.1.1 I went ahead with that, rather than just wiping and restoring with a manual sideload.
1. I adb installed FlashFire
2. Used OTG-USB to copy the rom and gapps to root directory of device
3. Used FlashFire to wipe and install SlimLP
Man, it is so much snappier than FireOS.
Thanks for the replies.
Hello, I've been searching for roughly 3 hours finding solution to uninstall pre-installed xposed framework on my ROM (Using Aurora 5.3 ROM on N900 Galaxy Note 3) but ending up having boot loop after tried this method :
<br />
You can remove Xposed framework by this way:<br />
<br />
1. Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:<br />
2. Go into /system/bin/ and delete app_process32 and app_process32_xposed<br />
3. Rename app_process32_original to app_process32<br />
4. Delete dex2oat and rename dex2oat.orig to dex2oat<br />
5. Repeat the above step for oatdump and patchoat<br />
6. Go up a directory and then into the lib directory<br />
7. Delete libart.so and rename libart.so.orig to libart.so<br />
8. Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so<br />
9. Delete libxposed_art.so<br />
10. Go up a directory and delete xposed.prop<br />
11. Go into framework directory and delete XposedBridge.jar<br />
12. Reboot your device.<br/>
Click to expand...
Click to collapse
and same result after tried flashing uninstaller zip both xposed-uninstaller-20150831-arm.zip or xposed-uninstaller-20160211.zip
Could anyone help me please? Thanks
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for CyanogenMod is available in the CyanogenMod GitHub repo.
And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Official CyanogenMod 14.1 Release post : https://wiki.cyanogenmod.org/w/Mint_Info
CyanogenMod 14.x for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3461744
Xperia TX (Hayabusa) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3461745
Xperia V (Tsubasa) : http://forum.xda-developers.com/xperia-t-v/v-development/rom-t3461746
Downloads Links
CyanogenMod 14.1 (Unlocked Bootloader) :
Xperia T (Mint) : https://mega.nz/#F!ugsE0JgS!IKLQAJhTWYWLZDIHydQrCQ
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.0 : http://forum.xda-developers.com/xperia-t-v/t-development/recovery-twrp-3-0-0-touch-recovery-t3319588
Useful alternatives to CM Updater (with Deltas) : CM Downloader on Play Store
About CyanogenMod : ChangeLog available on http://www.cmxlog.com/14.1/mint/
About CyanogenMod 14 Device Side : See my GitHub trees linked below
Unification of the user partitions into UserData
Read more about the UserData unification : https://wiki.cyanogenmod.org/w/Mint_Info
Migrate to the one big partition for CM-14.x :
- (Optional) Backup all your data, applications, internal storage, ...
- (Optional) If wished, do a full Nandroid backup from Recovery
- Flash the latest ROM zip of your device to start the unification
- Read and follow the instructions from the zip if anything goes wrong
- (Optional) Restore your Nandroid backup if you want to
- Flash the same ROM zip for CyanogenMod
Reverse the migration for older ROMs :
- (Optional) Backup all your data, applications, internal storage, ...
- Reboot to recovery and do a Factory reset (data will be lost)
- Flash restore_sdcard-YYYYMMDD-blue.zip
- Read and follow the instructions from the zip if anything goes wrong
- Flash the ROM you want now and restore your data
Flashing and updating
CyanogenMod clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the CyanogenMod ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
CyanogenMod update / upgrade :
- (Information) Don't wipe anything unless you want to
- (BETA / UNOFFICIAL) Nothing to wipe when switching
- Flash the latest CyanogenMod ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
CyanogenMod day-to-day updates :
- (Information) Don't wipe anything unless you want to
- (Information) Being Nightlies, try to have a safe backup once a month
- Update to latest Nightly using CM Updater or CM Downloader (link above)
- Reboot
About the builds
Device tree : https://github.com/AdrianDC/android_device_sony_mint/commits/cm-14.1
Common tree : https://github.com/AdrianDC/android_device_sony_blue-common/commits/cm-14.1
Kernel sources : https://github.com/AdrianDC/android_kernel_sony_msm8x60/commits/cm-14.1
Vendor blobs : https://github.com/AdrianDC/proprietary_vendor_sony/commits/cm-14.1
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Q&A - FAQ
CM-14.x Mint Regular Questions and Answers : Q&A Thread
About CM-14.x : https://en.wikipedia.org/wiki/CyanogenMod
The CyanogenMod team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
CyanogenMod available for Mint also thanks to :
- The CyanogenMod Team
- Everyone involved in working and testing
XDA:DevDB Information
CyanogenMod 14.1, ROM for the Sony Xperia T
Contributors
Adrian DC
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Created 2016-09-14
Last Updated 2017-03-20
Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- Dual Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok, only Ext4 support missing from ROM
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently based on Huashan kernel
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok (RTC real hardware clock, in TWRP recovery too)
- Powered-off alarm : Ok
- Offline Charging : Ok
- Encryption : Status unknown
- UserData Unification : Ok
- SEPolicies : Fully enforced
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open CyanogenRecovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
Reserved
Current local manifest of the ROM build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/CyanogenMod/android -->
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" />
<project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" />
<project name="CyanogenMod/android_packages_apps_FMRadio" path="packages/apps/FMRadio" remote="github" />
<project name="AdrianDC/android_device_sony_blue-common" path="device/sony/blue-common" remote="github" />
<project name="AdrianDC/android_device_sony_mint" path="device/sony/mint" remote="github" />
<project name="AdrianDC/android_kernel_sony_msm8x60" path="kernel/sony/msm8x60" remote="github" />
<project name="AdrianDC/proprietary_vendor_sony" path="vendor/sony" remote="github" />
</manifest>
Thank you very much, great work as always
ps. Some screenshots
@Adrian DC you're awesome! Thanks man, you really are a genius!
From your cm13 ROM with unified partition - only factory deset and flash this ROM and gapps? Btw gr8 work!
Bary said:
From your cm13 ROM with unified partition - only factory deset and flash this ROM and gapps? Btw gr8 work!
Click to expand...
Click to collapse
Yes, you need clean install (factory reset) and then just flash rom & gapps
THX. As I see in first post: photo working, video not (front, back or both)? GPS unknown mean not tested yet?
checking for md5 file..
skipping md5 check: no md5 file found
target: sony/LT30p: 4.3/9.2.a.1.205/Mvv_tg: user/release-keys
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/System
Patching system image unconditionally..
E:unknown command [log]
E:unknown command [log]
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/System
script succeeded: result was [1.000000]
updating partition details..
...done
I got this problem and the rom wont boot up.. any advices?
UPDATE: Nevermind it booted succesfully now.
OMG the CM recovery is so annoying, if I'm going to flash the TWRP again using fastboot it makes me stuck in the twrp until I install again the CM14.. need to figure out this somehow
Flash twrp from your device using the dd command. You can find a how to in the thread as well as on the official twrp website
LukaPochi said:
UPDATE: Nevermind it booted succesfully now.
OMG the CM recovery is so annoying, if I'm going to flash the TWRP again using fastboot it makes me stuck in the twrp until I install again the CM14.. need to figure out this somehow
Click to expand...
Click to collapse
Flash TWRP fota zip, or manually flash the recovery to fota partition. Instructions in twrp thread ...
Thanks @Adrian DC ! The ROM is fast and snappy.
dzadzev said:
Flash TWRP fota zip, or manually flash the recovery to fota partition. Instructions in twrp thread ...
Click to expand...
Click to collapse
Thanks
Have you tried to install supersu yet? Flashing it in the twrp recovery dosen't seems to do anything SuperSU-v2.78-201609011115
LukaPochi said:
Thanks
Have you tried to install supersu yet? Flashing it in the twrp recovery dosen't seems to do anything SuperSU-v2.78-201609011115
Click to expand...
Click to collapse
Don't use SuperSU, read more about it here ...
Just enable the integrated CM root access in developer options
So, its necessary to do a clean installation and if I do this i lost my files from my internal storage due to the unification?
Good Work!!!
don't work recording camera to me (I had try Google camera too). Anyone had try install root in this room?
Just hardbricked my phone by trying to resize internal partition on my own (should've read CM 14 Q&A :crying. Just a heads up.
Its nice, but there are some bugs, i love dual screen
I found a bug, the GPS (stand alone, without the internet access) dosen't track the position at all.
arniks8 said:
Just hardbricked my phone by trying to resize internal partition on my own (should've read CM 14 Q&A :crying. Just a heads up.
Click to expand...
Click to collapse
So you can't restore it anymore? omg
great work! thank you
despite of this does not work manual selection of operator.