Related
https://android.clients.google.com/updates/signed-kila-ota-114235-prereq.TC4-RC19.zip
Not sure when this is from. I was tooling around trying to find a way to flash myself off of the RC29 test build that I stupidly put on. Stumbled across this. Tried to flash it over my RC29-Test, and it failed with the following error:
Code:
E:Failure at line 1:
assert file_contains(SYSTEM:build.prop", "test-keys"0 == "true" || file_contains
("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/trout:1.0/
TC4-RC19/109652:user/ota-rel-keys,release-keys") == "true"
Installation aborted.
My build contains the following line:
Code:
ota-rel-keys,for-testing,release-keys
Let me know what y'all think.
I think its something good to add to my collection Thx
Darkrift said:
I think its something good to add to my collection Thx
Click to expand...
Click to collapse
I think it will be good for doing file diffs when we get to that point.
Thanks, It is good to have this...
Has anyone thought of trying to apply these updates to the RC1 from the emulator?
yeah, some guy named neoobs thought of it, not sure if he tried it yet though
Darkrift said:
yeah, some guy named neoobs thought of it, not sure if he tried it yet though
Click to expand...
Click to collapse
If I knew how to apply them I would have tried... but how do you hold the home button and the power button on the emulator? LOL
can you mis-match specific files?
I wonder if you can mis-match specific files in the updates.
I.e I wonder if you copied an RC19 file and built a custom version - but also copied the signatures into the appropriate files - since the file is still signed and it would still verify, I think it would still work to grab old versions and mix in with new versions.
The usefullness of making a frankenbuild is probably "not much" - but perhaps if there is a vulnerable file in one version it could be injected into a later version.
RyeBrye said:
I wonder if you can mis-match specific files in the updates.
I.e I wonder if you copied an RC19 file and built a custom version - but also copied the signatures into the appropriate files - since the file is still signed and it would still verify, I think it would still work to grab old versions and mix in with new versions.
The usefullness of making a frankenbuild is probably "not much" - but perhaps if there is a vulnerable file in one version it could be injected into a later version.
Click to expand...
Click to collapse
That won't work because there are 2 files with signatures... one of which is signed in the other. So if you change the signature file it will not validate. Pretty smart if you ask me.
neoobs said:
That won't work because there are 2 files with signatures... one of which is signed in the other. So if you change the signature file it will not validate. Pretty smart if you ask me.
Click to expand...
Click to collapse
I don't see where the one signs the other - the only META-INF file that is signed is the update-script that I can see in either file.
I do see in the code where it EXPLICITLY does NOT verify the .SF files however:
Code:
for (i = 0; i < mzZipEntryCount(pArchive); ++i) {
const ZipEntry *entry = mzGetZipEntryAt(pArchive, i);
UnterminatedString fn = mzGetZipEntryFileName(entry);
int len = mzGetZipEntryUncompLen(entry);
// Don't validate: directories, the manifest, *.RSA, and *.SF.
if (entry == mfEntry) {
LOGV("Skipping manifest %.*s\n", fn.len, fn.str);
} else if (fn.len > 0 && fn.str[fn.len-1] == '/' && len == 0) {
LOGV("Skipping directory %.*s\n", fn.len, fn.str);
} else if (!strncasecmp(fn.str, "META-INF/", 9) && (
!strncasecmp(fn.str + fn.len - 4, ".RSA", 4) ||
!strncasecmp(fn.str + fn.len - 3, ".SF", 3))) {
LOGV("Skipping signature %.*s\n", fn.len, fn.str);
} else {
unverified[i] = true;
totalBytes += len;
}
}
So I think it is entirely possible to swap in other files that are signed with the same key from an older version. If they change keys, I don't think it will work.
Another thought...
It doesn't make sense to me that the public key would be distributed along with the update - it looks like the phone is using the public key to verify the signed hashes - which is fine - they can see that the hashes were signed by the private-key pair of that RSA file...
But the .RSA is explicitly not verified, and I don't see in the verify.c file where it checks against any kind of keystore on the device...
I wonder if it is just checking that the files are signed, but not necessarily who they are signed by? Meaning - it's making sure the update hasn't been corrupted or tampered with - but not who made the update in the first place?
RyeBrye said:
I don't see where the one signs the other - the only META-INF file that is signed is the update-script that I can see in either file.
I do see in the code where it EXPLICITLY does NOT verify the .SF files however:
Code:
for (i = 0; i < mzZipEntryCount(pArchive); ++i) {
const ZipEntry *entry = mzGetZipEntryAt(pArchive, i);
UnterminatedString fn = mzGetZipEntryFileName(entry);
int len = mzGetZipEntryUncompLen(entry);
// Don't validate: directories, the manifest, *.RSA, and *.SF.
if (entry == mfEntry) {
LOGV("Skipping manifest %.*s\n", fn.len, fn.str);
} else if (fn.len > 0 && fn.str[fn.len-1] == '/' && len == 0) {
LOGV("Skipping directory %.*s\n", fn.len, fn.str);
} else if (!strncasecmp(fn.str, "META-INF/", 9) && (
!strncasecmp(fn.str + fn.len - 4, ".RSA", 4) ||
!strncasecmp(fn.str + fn.len - 3, ".SF", 3))) {
LOGV("Skipping signature %.*s\n", fn.len, fn.str);
} else {
unverified[i] = true;
totalBytes += len;
}
}
So I think it is entirely possible to swap in other files that are signed with the same key from an older version. If they change keys, I don't think it will work.
Click to expand...
Click to collapse
in one of the SF's (Signature Files HAHA never caught that till now) It has the SHA1-digest of the other. I believe it is Cert.sf, at the top it signs manifest.sf
This is why you can not alter the SF's at all because they both have all the files signed with one of them signing the other. Making it impossible to get around. And with SHA1 it just makes it hard to even think about it. Might as well do as others have said and find exploits.
RyeBrye said:
It doesn't make sense to me that the public key would be distributed along with the update - it looks like the phone is using the public key to verify the signed hashes - which is fine - they can see that the hashes were signed by the private-key pair of that RSA file...
But the .RSA is explicitly not verified, and I don't see in the verify.c file where it checks against any kind of keystore on the device...
I wonder if it is just checking that the files are signed, but not necessarily who they are signed by? Meaning - it's making sure the update hasn't been corrupted or tampered with - but not who made the update in the first place?
Click to expand...
Click to collapse
I like that idea... anyone know how to sign the files with your own rsa?
RyeBrye said:
It doesn't make sense to me that the public key would be distributed along with the update - it looks like the phone is using the public key to verify the signed hashes - which is fine - they can see that the hashes were signed by the private-key pair of that RSA file...
But the .RSA is explicitly not verified, and I don't see in the verify.c file where it checks against any kind of keystore on the device...
I wonder if it is just checking that the files are signed, but not necessarily who they are signed by? Meaning - it's making sure the update hasn't been corrupted or tampered with - but not who made the update in the first place?
Click to expand...
Click to collapse
Aperantly not many people know about private-public key cryptography.
Please, if you have the time, wiki private-public key cryptography or download the podcast from TWiT (This Week in Tech) Security now on that subject (episode ~15 or so, it was early on).
A simple explination:
Two keys are generated at random (or user input through an algorithm). A private key and a public key. The private key is used to encrypt files an ONLY the public key can decrypt it. IT IS NOT REVERSABLE.
The public key can be "publicly known", hence the name. It actually has to either be with the files or on the device that needs to unencrypt said files.
Now here's the awsome part a brute force attack on SHA1 would take millions of years to crack ON ONE KEY. (Much more detail to that)
Another added mesure of security is hash checking. Run a file through an algorythm and you get an unique ID for that file. You change as much as ONE BIT on that file and the output of the algorythm is COMPLETLY different.
Not imposible to crack, imposible to stay alive long enough to see it done.
Thats the Thing with PKey and Private Key and it Impossible to crack unless the Boot loader is not checking for Signing Authority.
Please Understand Signing a File and Encrypting the File is Different thing we have G1 Update.zip as Normal Zip file but The moment we change any byte in Zip Store the Checking gets failed. if G1 Boot loader is really not checking Singer and only rely on Signed Object whosmever may have signed then we got the Solution but i dont either HTC or Google is that foolish to do that.
We must have to look at G1 Source code for Details.
I think what cmonex and Olipro does is better. Get Source code of Boot loader Recompile it with disabled Signing Funda. Load the Boot Loader into Memory and that Jump to that Location. here Root access to Device is Necesory once we are Succefull to run Patched Bootloader from Memory Flashing Customised Image may not be a Problem
snoslicer8 said:
https://android.clients.google.com/updates/signed-kila-ota-114235-prereq.TC4-RC19.zip
Not sure when this is from. I was tooling around trying to find a way to flash myself off of the RC29 test build that I stupidly put on. Stumbled across this. Tried to flash it over my RC29-Test, and it failed with the following error:
Code:
E:Failure at line 1:
assert file_contains(SYSTEM:build.prop", "test-keys"0 == "true" || file_contains
("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/trout:1.0/
TC4-RC19/109652:user/ota-rel-keys,release-keys") == "true"
Installation aborted.
My build contains the following line:
Code:
ota-rel-keys,for-testing,release-keys
Let me know what y'all think.
Click to expand...
Click to collapse
can anyone post this file somewhere i can get it? it's not there anymore. My PC no longer see's my device, i'm wondering if flashing back to RC19 will work.
canOpoop said:
can anyone post this file somewhere i can get it? it's not there anymore. My PC no longer see's my device, i'm wondering if flashing back to RC19 will work.
Click to expand...
Click to collapse
First, you can't flash the RC19 if you have RC29.
Second, what do you mean your PC doesn't see your device? If your talking about the SD card through the phone, at the top of your phone when you have connected, you will have a notification at the top of your phone.
Either drag the notification bar or press menu on your home screen and click on Notifications. Select the USB selectionan it will prompt you, select "Mount"
quedijo said:
First, you can't flash the RC19 if you have RC29.
Second, what do you mean your PC doesn't see your device? If your talking about the SD card through the phone, at the top of your phone when you have connected, you will have a notification at the top of your phone.
Either drag the notification bar or press menu on your home screen and click on Notifications. Select the USB selectionan it will prompt you, select "Mount"
Click to expand...
Click to collapse
First: check this out. http://www.blogsdna.com/1256/how-to-quickly-update-t1-mobile-g1-phone-firmware-manually-rc29.htm
i'm thinking if i get the file (RC19) i can flashback.
Second: It had worked before (before the OTA update). I have tried 3 different PC's 2 different USB cables, REFlash of RC29, and a hard reset (to Factory). i do not ever get a notification to mount in Notification bar. Windows throws out the error "One of the USB Devices attached to this computer has malfuctioned, and windows does not recognize it." And yes i have tried different USB ports.
i'm open to any more ideas...
canOpoop said:
First: check this out. http://www.blogsdna.com/1256/how-to-quickly-update-t1-mobile-g1-phone-firmware-manually-rc29.htm
i'm thinking if i get the file (RC19) i can flashback.
Second: It had worked before (before the OTA update). I have tried 3 different PC's 2 different USB cables, REFlash of RC29, and a hard reset (to Factory). i do not ever get a notification to mount in Notification bar. Windows throws out the error "One of the USB Devices attached to this computer has malfuctioned, and windows does not recognize it." And yes i have tried different USB ports.
i'm open to any more ideas...
Click to expand...
Click to collapse
Use anycut and create a shortcut to the activity "SD Card" and see what it says when you open it.
neoobs said:
Use anycut and create a shortcut to the activity "SD Card" and see what it says when you open it.
Click to expand...
Click to collapse
Tmobile is replacing device. I should get a new on Tuesday the 11th. they are out of stock.
Hi,
I just upgraded my Hero to Elelinux's Gingerbread ROM ... had to reinstall swipe, lost previous dictionary, what now ... (most communication is in a Dutch local dialect so official dictionaries aren't much help)
so wrote this little script on my phone in SL4A/python.
What it does is simple :
load all sent & received sms messages in a textfield (separated by spaces)
then all you have to do manually is :
--> select all
--> swipe button
--> wait five minutes for confirmation message
--> every word you ever texted or received is in the dictionary
(just copy this code into a new 'filename.py' in the script folder of SL4A and run it)
Code:
import android
droid = android.Android()
text = ''
messages = droid.smsGetMessages(False,'inbox')
for message in messages.result :
text += message['body'] + ' '
messages = droid.smsGetMessages(False,'sent')
for message in messages.result :
text += message['body'] + ' '
droid.dialogCreateInput('Value', 'Please enter value:', text)
droid.dialogShow()
I know , the string handling is horribly noob but couldn't be bothered with learning python first, so if anyone with more patience can write a better variant that excludes numbers etc , plz do !
or ... if 'there is an app for that' ... let me know
NOTE: THIS GUIDE WILL WORK ANY ANDROID DEVICE BUT HAS FEW EXTRA PRE-SUGGESTED LINKS FOR GALAXY ACE PLUS USERS.
Click to expand...
Click to collapse
Special Thanks to -
dsixda for his awesome kitchen. Please Hit Thanks button for him.
inspired by isidromxz's thread.
Please kindly remind me if i have forgotten to write any name in thanks section, i have collected all things from many many sources and with modification.
Click to expand...
Click to collapse
Who is this tutorial for?
Absolute Beginners.
People with little or no programming skills.
people who really want to learn how to make custom rom's
people who want to learn android and don't know where to start.
Click to expand...
Click to collapse
Tools Required : (Update them manually and report me dead links please)
Java JDK FROM HERE OR JAVA.SUN.COM - FOR INSTALLING CYWIGN
(WARNING: Do not install Cygwin before the JDK!!
Click to expand...
Click to collapse
Cywign Direct Download- Linux Terminal For Windows
Android Kitchen (ROM Development Tool)- For Cooking custom ROM and many more things, Please update this Kitchen to latest version when available.
Official Link to dxda's Kitchen - Official Thread and Github source. Please refer FAQ on official thread for Kitchen related problems.
Click to expand...
Click to collapse
Demo META-INF Folder Download- For Making Flashable zip files and comparing updater script.
Custom Booting.zip - for custom boot animation
notepad++ - for editing files like build.prop, updaterscript
MOST IMPORTANT TOOL YOUR BRAIN... AND ALSO LOTS OF TIME... [DOWNLOAD LINK NOT AVAILABLE...lol]
Click to expand...
Click to collapse
Step one: Installing the JAVA JDK, Cygwin and Setting up the Kitchen.
*Before you do anything install the java jdk*
Try this Dsixda Kitchen Install Picture Tutor(recommended)
OR
watch this video tutorial by gitagaire for how to setup cygwin and kitchen(recommended)
Click to expand...
Click to collapse
INSTRUCTIONS
Download and extract the cygwin_packages.zip
Run the set up(make sure there is no previous cygwin installation)
NOTE: INSTALL CYGWIN IN ROOT DISK LIKE C:\
Follow the kitchen read me txt!!!
local package directory *must* be the path to the cygwin_packages folder that you just extracted
{
"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"
}
Click to expand...
Click to collapse
when it shows all the package names, go to the top and select "all default" until it changes to "all install" (you must click on the arrows)
Click to expand...
Click to collapse
Download the kitchen from above. Then, extract the kitchen's .zip file to a folder under your home account. Rename the dsixda-android-kitchen-*** folder to just "kitchen". In Cygwin, this folder would depend on what was set for your Cygwin install directory, e.g. C:\cygwin\home\John\kitchen
NOTE!! If your user folder contains spaces (e.g. C:\cygwin\home\John Smith\kitchen), then the kitchen will not function properly. Instead, copy it under C:\cygwin\home\kitchen.
Now your ready to run the kitchen type:
those who have their kitchen like this C:\cygwin\home\John\kitchen use these commands given below.
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
those who have their kitchen like this C:\cygwin\home\kitchen use these commands given below.
cd ../kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you did things right you should see this:
congratulations!!
Click to expand...
Click to collapse
Step Two: Setting up a working folder
THERE ARE TOW METHODS FOR THIS.
1. WHEN YOU HAVE BASE ROM AVAILABLE.
2. WHEN YOU DON'T HAVE BASE ROM.
FIRST METHOD -
First our folder structure should look like this:
Code:
cygwin folder/home/your user name/kitchen
Inside the kitchen it should look like this:
Now we need a rom to work on, for GALAXY ACE PLUS[s7500] users i will recommend this rom by blackburner but you can use any rom.
Just Place the original rom zip in the original_update folder inside the kitchen.
run the cygwin.exe again type:
Code:
cd kitchen(enter)
./menu(enter)
now enter option 1, enter again. You should see your rom listed, choose and enter
you will be asked about changing the working folders name, at this point it makes no difference so just continue.
congratulations you have a working folder!!!
SECOND METHOD - this method is by neroyoung
FIRST MAKE A WORKING FOLDER IN CYGWIN FOLDER
IT SHOULD LOOK LIKE THIS
cygwin folder/home/your user name/kitchen/WORKING_(your rom name)
Click to expand...
Click to collapse
NOTE: FOR THIS MEETHOD WE NEED 3 FILES AND FOLDERS TO BE PLACED IN WORKING FOLDER.
1. META-INF FOLDER - GET THIS FROM DOWNLOAD FILES LIST IN FIRST POST
2. SYSTEM FOLDER - TUTORIAL BELOW
3. BOOT.IMG - TUTORIAL BELOW
2. getting system folder
(NOTE - YOU MUST BE ROOTED FOR THIS MEDHOD)
This is universal method and can be done easily using terminal emulator.
For this simply download Terminal Emulator from Android Market.
we need freshly flashed device here. OTHERWISE YOU WILL HAVE LOT OF JUNK FILES.
Open it and type:
su
tar -c system/* >> sdcard/system.tar
Click to expand...
Click to collapse
This will copy all your /system folder to your SDcard with name System.tar
This will take some time to finish so be patient.
After it's done you should have a tar file in your /sdcard named system.tar
You can extract it using Winrar or 7zip software. But yes this will have huge size , as it has other useless folders so you will have to delete them. After extracting this system.tar file you will get following folders (Similar one)
/etc
/fonts
/framework
/lib
/lost-found
/media
/sd
/semc
/usr
/xbin
build.prop
And some other files and folders like ""autorooted,kernel files" etc
Click to expand...
Click to collapse
Now simply delete the folders marked in red color and its done.Don't worry if you don't have folders with red colors above,we don't need them.
And the final files that we will have in our system folders will be
/app
/bin
/etc
/fonts
/framework
/lib
/media
/semc
/usr
/xbin
build.prop
Click to expand...
Click to collapse
If it dont have semc folder no need to worry.
NOTE: YOU CAN ALSO GET THIS SYSTEM FOLDER BY USING ANY ROOT BROWSER. JUST FIND THIS FOLDER AND COPY/EXTRACT TO SDCARD
NOW COPY THIS system FOLDER TO WORKING FOLDER
3. getting boot.img
Here we have 2 options
1. stock boot.img from stock rom - simple kernel which we get in brand new mobile.
2. custom boot.img from custom kernel - kernel which are modified for overclock or other features
1. getting stock boot.img from stock rom.
extract your stock rom with winrar or 7zip. you will see boot.img there. copy it to working folder
2. getting custom boot.img from custom kernel.
download any custom kernel which is only for your device. [galaxy ace plus [s7500] users get from here or here]
extract it with winrar or 7zip and copy boot.img to working folder
NOTE: many of new devices have kernel.bin and other files instead of boot.img so skip this part if your device don't have it...
Click to expand...
Click to collapse
Step Three :change/modify/update rom
YOU CAN MODIFY YOUR ROM IN TWO STEPS:
MODIFY USING ANDROID KITCHEN - for basic modification.
MODIFY MANUALLY. - for advanced modification.
1. MODIFYING USING ANDROID KITCHEN
watch this amazing tutorial by neroyoung on how to editing rom with kitchen
NOTE: DON'T FORGET TO DEODEX YOUR ROM
Click to expand...
Click to collapse
2. MODIFYING MANUALLY.
FOR ALL ANDROID PHONES (ESPECIALLY FOR GINGERBREAD ROMS) USE THIS GUIDE FOR COOL MODS. like center clock,CRT animation, ics and jelly bean style mods etc... ANOTHER GUIDE BY ME
Adding/removing applications
1. Go to the working folder where you extracted your rom, inside you will find:
OR
2. Then go to "system/app" inside this folder you will find all the rom applications(apks) you may also find some in the data folder if your rom has this folder.
3. Copy, replace, and change any app(apk) be carefull if you dont know what the apk is do not delete!!
LIST OF APPS YOU CAN DELETE - HERE OR HERE
If you can not find some apps in this guide then try opening all those app in your phone and see app name and icon or move those apps from system/app to sdcard and see what is not working...
Adding new boot animation
android kitchen doesn't works for this in Samsung phones. So we need a different method.
1) Download and extract the bootanimation and samsungani file from Custom Booting.zip attached in first post.
2) Put them in the /system/bin folder and replace the existing files there
3) Now download any boot animation, and rename the bootanimation to “sanim.zip”.
4) Now, navigate to /system/media and replace the “ODEanim” with “sanim.zip”
You are done with the bootanimation change
customizing the theme
1. replace stock launcher with launchers like nova launcher
2. theming using uot kitchen (fonts, status bar, batery and other icons etc
watch this amazing toutorial by jdlogan151
Click to expand...
Click to collapse
Edit the gps script for your country/location
1. In the workingfolder/system/etc/ you will find a file named gps.conf, you can
edit this file with notepad++ or even word.
2. using the right gps script in this file can speed up gps lock, you can
find some from angeldeath, download extract and replace the gps.conf.
Adding ringtones :
Take your ringtone file...it should be in .ogg format..If not then convert it to .ogg..
Locate to the folder system>media>audio>ringtones>
Copy and paste your .ogg files here in ringtones folder..
You can also change notifications, alarm and UI tones like this..
Changing the Fonts :
Take your desired font.ttf file and rename it as DroidSans.ttf..
Locate to the folder system>fonts>
Now, replace the file DroidSans.ttf with your desired DoridSans.ttf...
To change the lock screen clock font...replace the Clocktopia.ttf with your desired one..(rename first)..
build.prop tweaks!!
check this or this or this post for build.prop
NOTE: EDIT BUILD.PROP WITH NOTEPAD++. SIMPLE NOTEPAD WILL CORRUPT THE FILE.
adding mods and scripts...
download mods and scripts from links below and copy past all files in same folder as your rom... like for init.d scripts add them to system/etc/init.d/here and all permissions in updater script to your updater script...(dont forget to give them credit for it...)
links:-
[TweakZV6] Init.d best tweaks[Flashable] Increase your performance by [email protected]
Collection build.prop; init.d; etc. by optik19918
init.d Tweaks collection by dsexton702
[SCRIPTS][TWEAKS][CWM]SlaidyBoost-V2.3 by slaid480
[CWM][SCRIPTS][TWEAKS] Adrenaline™ Engine by ImbaWind
V6 SuperCharger by zeppelinrox
[SCRIPTS]CronMod-A2SD/D2EXT/INT2EXT by croniccorey
Xloud and Bravia engine by aiman112
AwesomeBEATS™ v.3 by ...Awesome...
(MOD)Beats Audio(2.3+up) by RockoDev
Tuned MegaBassBeat by kurotsugi
Maximum MultiTasking Mods + V6 SuperCharger BY zeppelinrox
[AROMA] Beats Mode - Enhanced Beats sound V7.5 by MemAllocatoR
Interactive Phone Modification [GUIDE]
ICS Style 'Settings.apk' - Make it yourself by balamu96m
StatusBar Tweaks by Master&Slave™
Change lockrings on any rom by daveyannihilation
change ICS lockscreen animation to Honeycomb style by evilisto
S Voice for any devices [ICS] by PlaYOuT
Implement Swipe to Remove Notification by hansip87
Remove SMS log from Call log by wilfredcool007
Activate the rotation of the lockscreen by GalaxyUser
How to use AROMA INSTALLER in any ROM/MOD by pankaj88
All in one tweaks build.prop,init.d,Wifi,Xloud,Bravia,A-Gps,A/V Sync,Modules by XtremePeople
Add 6 lockscreens Mod + Lockscreen Gestures by pratyush.creed
How to add customizable 14 statusbar toggle buttons for samsung ROM by lidroid
Create a custom notification dropdown by jeffsanace
these are few i love, find more yourself...
MORE WILL BE ADDED SOON...
MORE ADVANCE MODIFICATION (not advised for beginners)
editing .apk files
THERE ARE TWO BEST TOOLS FOR EDITING .APK FILES
1. APKTOOLS
This video by neroyoung teaches you how to setup APKTOOL folder as well as teaches you how to edit .apk files.
2. APK Manager
this video by adgoosuc teaches you How to unpack,repack and sign an APK File with APK Manager
Click to expand...
Click to collapse
[*]Editing .JAR Files
In this video by neroyoung you will get information on how to edit .jar files like services.jar using APKTOOL.
Click to expand...
Click to collapse
[*]THEMEING .apk FILE
HERE IS A AWESOME TUTORIAL BY Andrewtst FOR THEMEING ANY .apk FILE.
for porting themes:
1. download and extract theme you want to port.
2. open both apk(base and port) in 7zip/winrar
3. drag and replace png files with same name
this works with only png files not with xml and others
FOR THEMING YOUR ROM YOU CAN EDIT framework-res.apk AND GET MANY COOL THINGS
LIKE you can change smiles, default wallpaper, default lockscreen wallpaper, add 14 toggle mod and many cool things...
for that use Framework Flasher or apktools or any other tool and do changes manually.
CHECK THIS GUIDE BY dully79 TO KNOW WHICH FILES YOU CAN MODIFY AND HOW.
HERE ARE FEW MORE COOL GUIDES -
ICS Style 'Settings.apk' BY balamu96m
Implement Swipe to Remove Notification BY hansip87
add customizable 14 statusbar toggle buttons for samsung ROM BY lidroid
FOR MORE SEARCH MORE...
Click to expand...
Click to collapse
CHANGING HARD KEY FUNCTION (REMAPPING BUTTON)
1. open /system/usr/keylayout/[phone model]-keypad.kl with notepad++
(Some phone may have different names, but it will always end with "keypad.kl)
it will look like this --
Code:
# Copyright (c) 2011, Code Aurora Forum.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# [url]http://www.apache.org/licenses/LICENSE-2.0[/url]
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
#
key 2 1
key 3 2
key 4 3
key 5 4
key 6 5
key 7 6
key 8 7
key 9 8
key 10 9
key 11 0
key 158 BACK WAKE_DROPPED
key 230 HOME WAKE
key 60 SOFT_RIGHT WAKE
key 62 ENDCALL WAKE_DROPPED
key 229 MENU WAKE_DROPPED
key 59 MENU WAKE_DROPPED
key 139 MENU WAKE_DROPPED
key 228 POUND
key 227 STAR
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
key 102 ENDCALL WAKE_DROPPED
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 212 SLASH
key 213 DEL WAKE_DROPPED
key 355 DEL WAKE_DROPPED
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 14 DEL
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
key 51 COMMA
key 52 PERIOD
key 28 ENTER
key 56 ALT_LEFT
key 42 SHIFT_LEFT
key 215 AT
key 57 SPACE
key 53 SLASH
key 127 SYM
key 100 ALT_RIGHT
key 399 GRAVE
HERE YOU WILL FIND 3 ROWS...
1. As you can see, there are different attributes assigned to each key. like this
Code:
key 102 HOME
key 139 MENU
key 158 BACK
key 115 VOLUME_UP
key 114 VOLUME_DOWN
2. Specific application/action launchers:
Code:
HOME #Launches "Home"
MENU #Launches "Menu"
BACK #Takes you back to the last activity
SEARCH #Launches "Universal Search"
CALL #Launches the "Phone" activity and corresponding .apk or initiates a call
ENDCALL #Ends a call
CAMERA #Launches "Camera" activity and corresponding .apk
FOCUS #Initiates Auto-Focus while using the Camera
VOLUME_UP #Self explanatory
VOLUME_DOWN #Self explanatory
3. And attributes saying if it should wake the phone at button push to complete the action, or if it should just complete the action without waking the screen.
Code:
WAKE #Completes the action without waking the screen
WAKE_DROPPED #Wakes the phone to complete the action
Click to expand...
Click to collapse
2. NOW WE WILL EDIT SECOND AND/OR THIRD ROW
Erase the center row value for any key to completely disable it. To reassign the key, replace the center row value with another one from the same row. Change the right row value to either "WAKE" or blank to enable the wake function. Do not modify the left row.
NOTE: don't edit left row i.e. first row which contains specific key identity number.
FOR EXAMPLE I DO THESE CHANGES
DEFAULT VALUES ---
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
CHANGED VALUES ---
Code:
key 115 CAMERA WAKE
key 114 FOCUS WAKE
NOW VOLUME UP KEY WILL WORK AS CAMERA KEY AND VOLUME DOWN KEY WILL WORK AS FOCUS KEY....
NOTE: all words should be in BOLD letters i.e. capital letters...
Click to expand...
Click to collapse
MORE COMING SOON
FOR ADVANCE ROM DEVELOPMENT GUIDES (like porting rom) SEE THIS COLLECTION BY F3niX
Step Four: repackage the rom
AFTER YOU HAVE DONE ALL CHANGE/MODIFICATION YOU WANTED OPEN CYGWIN AGAIN AND TYPE
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
now convert update script to updater script(in option 23)
now lets edit updater script(optional)
Thanks to user langthang for a great updater-script guide.
Download it HERE
Click to expand...
Click to collapse
the updater-script basically tells CWM what steps to take during the installation(flashing rom).
If you don't have any experience please don't edit anything other than what is in this simple tutorial.
TO EDIT UPDATER SCRIPT -
1.Go to META-INF/com/google/android
2.Open the updater-scrip file with Notepad++
3.Any text that would appear during the CWM install should be in this format :
Code:
ui_print("Put your text in HERE");
Add your text start at top and save,
then replace with new updater-scrip
IF YOU GET ANY ERROR YOU CAN COMPARE YOUR UPDATER SCRIPT WITH MINE (attached in 1st post)
NOTE: DO NOT COPY WHOLE UPDATER SCRIPT JUST EDIT PART WHERE YOU GET ANY ERROR...
most common errors will be in mount, remount part in starting and end and boot.img installing part... so replace only those lines....
AND AT LAST
[*]Now that you have made some changes it's time to pack the rom and test!!
Run the cygwin and type
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
enter option 99 - "biuld rom from working folder"
Choose your build option and few more enters
I recommend that you go with all default options until you get more experience with the kitchen.
When rom is packed and signed it will ask to change rom zip name (type name of your rom)
When its all done you will find a folder inside "cygwin/home/yousername/kitchen" called output_zip
Inside the folder is your new rom ready to be flashed and tested!!!
IF YOU WANT THAN YOU CAN MAKE CWM FLASH ABLE ZIP'S MANUALLY USE THIS TOOL BY I.AM.H3RO
congratulations you have build your own rom
TROUBLESHOOTING (by hell_lock)
If you are facing java related problem with cygwin than refer to this post. and Google search
If you get problems in installing a rom then compare your updater-script in META-INF folder with one attached in first post.
If you have a rom without kernel then remove these lines:
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p8"),
delete("/tmp/boot.img"));
NOTE: mmcblk0p8 can be different with different devices... this works fine with galaxy ace plus...
If there is a package error then extract the files of the rom and repack them using any compression software.
If rom installed correctly but stuck onto logo screen?? Then remove try removing kernel and flashing rom again.
If rom installed correctly but got onto bootloop then there could be many possibilities which could lead to this. If you want accurate cause of it then do a logcat.
If there are some apk's which are not working then check if you correctly modded them.
For status errors like status error 0, status error 6, status error 7 see this guide by Tha TechnoCrat and for rest go here and type your error.
NOTE: Most of the problems occur because of updater-script problems so before trying any of the troubleshooting try the first tip.
IF YOU HAVE ANY QUESTIONS OR PROBLEMS FEEL FREE TO POST HERE OR PERSONAL MESSAGE ME.
omg all my thanks goes for you today
●๋•ηι¢є ιηƒσ●๋•
how about using dsixda, toolchain etc in linux? would u please add some tutor for that...even i guess it has the same way... i mean in ubuntu what version of dsixda that work well and what lib is needed for that? cos i have made my own kernel on my last device galaxr fit(gt-s5670) that use armv6 procie..maybe it need diferent type n bersion of tools?
thanks in advance
Sent from my GT-S7500 using xda app-developers app
Sorry i dont use lunix so i know nothing about it..... there are more threads related to this... they can help you....
Sent from my GT-S7500 using xda premium
Can i use this for micromax funbook tablet?
Yes it will work on any device... good luck
Sent from my GT-S7500 using xda premium
Had a quick read through, seems fairly easy to get started, so thanks for that!
What I want to achieve is to be able to take an existing ROM, and customise it for my organisation. I want to be able to remove the initial set up that you get when you flash a new ROM, e.g. name, Google account etc. Do you know how I would achieve this, or the files I would need to edit?
I also want to remove some APKs and preload some APKs, I think I know how to do this its just a case of replacing them in the system folder?
Also I want to preload some Wifi settings on so set it to know our SSID and PSK, is this something which is possible?
Thanks for your help!
fro5tie said:
Had a quick read through, seems fairly easy to get started, so thanks for that!
What I want to achieve is to be able to take an existing ROM, and customise it for my organisation. I want to be able to remove the initial set up that you get when you flash a new ROM, e.g. name, Google account etc. Do you know how I would achieve this, or the files I would need to edit?
I also want to remove some APKs and preload some APKs, I think I know how to do this its just a case of replacing them in the system folder?
Also I want to preload some Wifi settings on so set it to know our SSID and PSK, is this something which is possible?
Thanks for your help!
Click to expand...
Click to collapse
1st for rom you will use as base, get permission of its developers before doing it...
2nd the setup wizard you are talking about(i guess where we have to touch android) is by app in system/app named SetupWizard.apk but i think you should not delete it. it also controls few other things.
3rd replace/delete app you know about...(system/app)
4th i don't know much about preloaded settings... all i know is you will need to edit smali files of apk....
Hi
I've been playing around with this, I've extracted the ROM to a working folder and made a few changes, e.g adding and removing APKs. Then I've repackaged the ROM, but when I copy the .zip onto my SD card and try flashing it, I get an error:
Install /sdcard
Finding update package
Opening update package
Verifying Update package
E:signature verification failed
Installation aborted
I can't install CWM on this device so its just using the Android System Recovery 3e
Is there something else I have to do to get it flashable?
hiii
okay.. so first get cwm recovery as you say you dont have cwm... then while making a zip with android kitchen make sure when it ziplangs all apks then it signs your rom zip... make sure you press enter or press y and then enter...
while flashing rom with cwm you get this error again then in 'ïnstall zip from sdcard' select 'toggle signature verification' then try again if still no luck rply back....
and it seams like you used this guide and you found it helpful i guess and you dint even pressed a thanks button... i don't know why you guys enjoy all stuff and don't even press thanks button.. i am not asking you for money... it wont cost you anything...
fro5tie said:
Hi
I've been playing around with this, I've extracted the ROM to a working folder and made a few changes, e.g adding and removing APKs. Then I've repackaged the ROM, but when I copy the .zip onto my SD card and try flashing it, I get an error:
Install /sdcard
Finding update package
Opening update package
Verifying Update package
E:signature verification failed
Installation aborted
I can't install CWM on this device so its just using the Android System Recovery 3e
Is there something else I have to do to get it flashable?
Click to expand...
Click to collapse
Hi
Thanks for this, I've got it sorted now.
I can't install CWM as its not compatible with my device, but it was just that the zip needed signing for my device. I found info on another forum to sign it properly, and its flashing fine now.
Thanks for your help.
fro5tie said:
Hi
Thanks for this, I've got it sorted now.
I can't install CWM as its not compatible with my device, but it was just that the zip needed signing for my device. I found info on another forum to sign it properly, and its flashing fine now.
Thanks for your help.
Click to expand...
Click to collapse
Wich device you have?
use this to make your own cwm recovery.... http://builder.clockworkmod.com/
fro5tie said:
Hi
Thanks for this, I've got it sorted now.
I can't install CWM as its not compatible with my device, but it was just that the zip needed signing for my device. I found info on another forum to sign it properly, and its flashing fine now.
Thanks for your help.
Click to expand...
Click to collapse
androsamace said:
Wich device you have?
Click to expand...
Click to collapse
Its an Ainol Novo 7 Elf 2 (chinese tablet)
lokeshsaini94 said:
use this to make your own cwm recovery.... http://builder.clockworkmod.com/
Click to expand...
Click to collapse
I'll take a look.
HTC One X
- no ROM support, but de-odexing only! (Here is the guide to de-odex)
So i wanted to start building a ROM the easy way, guess I have to find the manual method..
i dont know what are you talking about... here is link for htc one x roms
http://onexroot.com/category/one-x-roms/
xSilv85 said:
HTC One X
- no ROM support, but de-odexing only! (Here is the guide to de-odex)
So i wanted to start building a ROM the easy way, guess I have to find the manual method..
Click to expand...
Click to collapse
Oh i mean the kitchen.. not suited for htc one x is stated in the op.
Sent from my HTC One X using Tapatalk 2
Title^^
?
I have only power which is the stock option but is there a way to add more? like reboot and recovery
AppEx213 said:
Title^^
?
I have only power which is the stock option but is there a way to add more? like reboot and recovery
Click to expand...
Click to collapse
You have to root your phone for that. Check if Xposed support included for Android 5, if yes you can do that with Xposed
rajneeshk said:
You have to root your phone for that. Check if Xposed support included for Android 5, if yes you can do that with Xposed
Click to expand...
Click to collapse
Xposed does not run on Android 5 (ART runtime), xposed only runs on DALVIK
For the reboot options I'm fine with Simple Reboot by Francisco Franco - https://play.google.com/store/apps/details?id=simple.reboot.com&hl=de
Cheers
hr_kaleu said:
Xposed does not run on Android 5 (ART runtime), xposed only runs on DALVIK
For the reboot options I'm fine with Simple Reboot by Francisco Franco - https://play.google.com/store/apps/details?id=simple.reboot.com&hl=de
Cheers
Click to expand...
Click to collapse
Simple reboot is fine, but its still an app. I wanted something that is on the power menu.
Is there nothing you can do to the framework apk or system ui?
rajneeshk said:
You have to root your phone for that. Check if Xposed support included for Android 5, if yes you can do that with Xposed
Click to expand...
Click to collapse
Everyone and their mother knows that Xposed is incompatible with Lollipop.
AppEx213 said:
Simple reboot is fine, but its still an app. I wanted something that is on the power menu.
Is there nothing you can do to the framework apk or system ui?
Click to expand...
Click to collapse
You can flash a custom ROM with that option i.e. Cataclysm.
AppEx213 said:
Title^^
?
I have only power which is the stock option but is there a way to add more? like reboot and recovery
Click to expand...
Click to collapse
Not on the stock framework (if you are rooted) atm as Xposed doesn`t support ART yet and maybe never will.
Pure AOSP and stock do not have the functionality to add more reboot options.
Without modifying anything else, the only thing you can add is a shortcut to settings, airplane mode, and the silent/vibrate/sound-thing.
frameworks_base/core/res/res/values/config.xml
Code:
<!-- Defines the default set of global actions. Actions may still be disabled or hidden based
on the current state of the device.
Each item must be one of the following strings:
"power" = Power off
"settings" = An action to launch settings
"airplane" = Airplane mode toggle
"bugreport" = Take bug report, if available
"silent" = silent mode
"users" = list of users
-->
<string-array translatable="false" name="config_globalActionsList">
<item>power</item>
<item>bugreport</item>
<item>users</item>
</string-array>
Lethargy said:
Pure AOSP and stock do not have the functionality to add more reboot options.
Without modifying anything else, the only thing you can add is a shortcut to settings, airplane mode, and the silent/vibrate/sound-thing.
frameworks_base/core/res/res/values/config.xml
Code:
<!-- Defines the default set of global actions. Actions may still be disabled or hidden based
on the current state of the device.
Each item must be one of the following strings:
"power" = Power off
"settings" = An action to launch settings
"airplane" = Airplane mode toggle
"bugreport" = Take bug report, if available
"silent" = silent mode
"users" = list of users
-->
<string-array translatable="false" name="config_globalActionsList">
<item>power</item>
<item>bugreport</item>
<item>users</item>
</string-array>
Click to expand...
Click to collapse
So I decompile framework-res.apk go to values and edit config.xml, search for silent and change false to true?
AppEx213 said:
So I decompile framework-res.apk go to values and edit config.xml, search for silent and change false to true?
Click to expand...
Click to collapse
This part is commented out (isn't included when built/compiled, used in source to usually provide info) and won't appear when you decompile it:
Code:
<!-- Defines the default set of global actions. Actions may still be disabled or hidden based
on the current state of the device.
Each item must be one of the following strings:
"power" = Power off
"settings" = An action to launch settings
"airplane" = Airplane mode toggle
"bugreport" = Take bug report, if available
"silent" = silent mode
"users" = list of users
-->
It tells you the possible options you can use in the power menu array
See this part, which is the actual array:
Code:
<string-array translatable="false" name="config_globalActionsList">
<item>power</item>
<item>bugreport</item>
<item>users</item>
</string-array>
Bug report is shown only if you enable it in Settings > Developer Options and User selector is only shown if you have multiple users.
"silent" isn't in the array (config_globalActionsList), but its a possible option as stated by the comment in source code, so you can add:
Code:
<item>silent</item>
into the array where you want it to be, and it'll show up in the power menu. You can also add settings and airplane mode as stated by the comment.
Adding additional possible entries (like reboot) requires modifying other source code, which you'll have to compile AOSP to do anyways which defeats the purpose of specifically modifying stock, except maybe in a case like Cataclysm ROM by atl4ntis. Or edit smali.
That icon on the right with the white circular arrow saves all that, if you put it in the dock is a very good substitute. Plus it's a wide choice...
I know it's not baking something into the OS but those after a quick, useful workaround it's a winner
How exactly would I get this working? Do I need to compile just one .apk or a complete ROM? I feel like I cannot install Lollipop without silent mode working...
rien-ne-va-plus said:
How exactly would I get this working? Do I need to compile just one .apk or a complete ROM? I feel like I cannot install Lollipop without silent mode working...
Click to expand...
Click to collapse
Flash Lollipop then take out framework-res.apk, decompile it on your PC and add it into the array. Recompile and push back onto device.
Lethargy said:
Flash Lollipop then take out framework-res.apk, decompile it on your PC and add it into the array. Recompile and push back onto device.
Click to expand...
Click to collapse
I cannot confirm this to be working. I installed a custom Lollipop ROM which had the silent mode in the framework-res.apk activated but when pressing the button in the shutdown menu it would simply switch to the "important" mode, thus letting more through than desired. Doesn't seem to be the old silent mode. I pulled the file, too, and checked the array configuration...
rien-ne-va-plus said:
I cannot confirm this to be working. I installed a custom Lollipop ROM which had the silent mode in the framework-res.apk activated but when pressing the button in the shutdown menu it would simply switch to the "important" mode, thus letting more through than desired. Doesn't seem to be the old silent mode. I pulled the file, too, and checked the array configuration...
Click to expand...
Click to collapse
Here is allready thread by garynych: http://forum.xda-developers.com/goo.../mod-3-power-menu-stock-5-0-1-deodex-t2997128 with restart option in power menu for deodex rom and extended power menu without restart for odex rom. The second one has the same issue as in your description.
Regards, Zagor
So I understand you don't have a silent mode either using those files, correct? Thanks for the link
BirchBarlow said:
Everyone and their mother knows that Xposed is incompatible with Lollipop.
You can flash a custom ROM with that option i.e. Cataclysm.
Click to expand...
Click to collapse
except my mum knows the workaround for xposed for lollipop.
not fond at Sony stock lollpop
Elluel said:
Pure AOSP and stock do not have the functionality to add more reboot options.
Without modifying anything else, the only thing you can add is a shortcut to settings, airplane mode, and the silent/vibrate/sound-thing.
frameworks_base/core/res/res/values/config.xml
Code:
<!-- Defines the default set of global actions. Actions may still be disabled or hidden based
on the current state of the device.
Each item must be one of the following strings:
"power" = Power off
"settings" = An action to launch settings
"airplane" = Airplane mode toggle
"bugreport" = Take bug report, if available
"silent" = silent mode
"users" = list of users
-->
<string-array translatable="false" name="config_globalActionsList">
<item>power</item>
<item>bugreport</item>
<item>users</item>
</string-array>
Click to expand...
Click to collapse
i cant find config.xml in Sony lollipop stock 270 framework
any solution???
AppEx213 said:
is there a way to add more? like reboot and recovery
Click to expand...
Click to collapse
Do the same as I did - instal the app Link2SD. It's very usefull app and I have the option of restarting from there in more options - reboot, quick reboot, reboot to recovery.
Elluel said:
Pure AOSP and stock do not have the functionality to add more reboot options.
Without modifying anything else, the only thing you can add is a shortcut to settings, airplane mode, and the silent/vibrate/sound-thing.
frameworks_base/core/res/res/values/config.xml
Code:
<!-- Defines the default set of global actions. Actions may still be disabled or hidden based
on the current state of the device.
Each item must be one of the following strings:
"power" = Power off
"settings" = An action to launch settings
"airplane" = Airplane mode toggle
"bugreport" = Take bug report, if available
"silent" = silent mode
"users" = list of users
-->
<string-array translatable="false" name="config_globalActionsList">
<item>power</item>
<item>bugreport</item>
<item>users</item>
</string-array>
Click to expand...
Click to collapse
sir can you point me to a site or link for aosp 7.1.1 nougat? or can you teach us here? thank you
ian97 said:
sir can you point me to a site or link for aosp 7.1.1 nougat? or can you teach us here? thank you
Click to expand...
Click to collapse
You just revived a 3-year-old thread, congrats.
Disclaimer:
I am not responsible for bricked devices or you getting fired because the alarm app failed. Please do some research before making any system modification. You are choosing to make these changes at your own risk and if you point the finger at me for messing up your device, I will laugh at you.
I noticed that most users wanted to have the Pixel Experience for this device and one main reason why we don't was because of those hardware keys which is not in line with Google's stock android.
Thanks to @Tulsadiver for providing the zip which works fine with a/b partition, giving me less work to do.
Below, you'll find how to:
- Enable On-Screen Navigation Bar
- Disable Hardware Capacitive Keys
- Disable Hardware Capacitive Key Lights
- Install Pixel Navigation Bar with animation
Your device needs to be rooted and with TWRP installed
A file manager app with root access
There is no other way to achieve this without having root access
1. To enable on-screen navigation bar:
Navigate to this path: root/system/
Edit the file: build.prop
Insert below code anywhere or at the bottom then save changes.
qemu.hw.mainkeys=0
2. To disable hw keys:
Navigate to this path: root/system/usr/keylayout/
Edit the file: ft5435_ts.kl
At the bottom you'll find below:
key 139 MENU VIRTUAL
key 172 HOME VIRTUAL
key 158 BACK VIRTUAL
To disable those, just put # before the word "key" then save changes.
3. To disable hw key lights:
Navigate to this path: sys/devices/soc/leds-qpnp-10/leds/button-backlight/
Edit the values of below from 10 to 0 then save changes
brightness
max_brightness
Reboot your device for the changes to take effect.
To enable Pixel Navigation Bar with animation, just download the file: [PORT]PixelNavBar-tissot.zip and flash it via TWRP.
(Note: the ozop.zip file is to revert back the changes)
When I try to open the brightness and max_brightness with MiXplorer I get a "failed" message. I am rooted using CFAutoroot.
tosmopolitan said:
When I try to open the brightness and max_brightness with MiXplorer I get a "failed" message. I am rooted using CFAutoroot.
Click to expand...
Click to collapse
Use x-plore app from Play Store.
MarkerBeanXDA said:
Use x-plore app from Play Store.
Click to expand...
Click to collapse
Thanks, worked perfectly!!
MarkerBeanXDA said:
I noticed that most users wanted to enable the on-screen navigation bar and disable the hardware keys including its light to get a better stock android experience.
Below you'll find the steps on how to do just that:
First of all, you need to be rooted and and install a file manager app with root access
There is no other way to achieve this without having root access.
1. To enable on-screen navigation bar:
Navigate to this path: root/system/
Edit the file: build.prop
Insert below code anywhere or at the bottom then save changes.
qemu.hw.mainkeys=0
2. To disable hw keys:
Navigate to this path: root/system/usr/keylayout/
Edit the file: ft5435_ts.kl
At the bottom you'll find below:
key 139 MENU VIRTUAL
key 172 HOME VIRTUAL
key 158 BACK VIRTUAL
To disable those, just put # before the word "key" then save changes.
3. To disable hw key lights:
Navigate to this path: sys/devices/soc/leds-qpnp-10/leds/button-backlight/
Edit the values of below from 10 to 0 then save changes
brightness
max_brightness
Reboot your device for the changes to take effect.
Click to expand...
Click to collapse
Nice
But when we reboot, Lights are enabled.
We have to bring down max brightness to 0 once again.
Is there any permanent method to disable backlight?
Wow thanks. Can you also guide on how to enable night light?
Vasu Netha said:
Nice
But when we reboot, Lights are enabled.
We have to bring down max brightness to 0 once again.
Is there any permanent method to disable backlight?
Click to expand...
Click to collapse
Are you rooted with CF-Auto-Root?
MarkerBeanXDA said:
Are you rooted with CF-Auto-Root?
Click to expand...
Click to collapse
Yes
Vasu Netha said:
Nice
But when we reboot, Lights are enabled.
We have to bring down max brightness to 0 once again.
Is there any permanent method to disable backlight?
Click to expand...
Click to collapse
same problem, how to permanently off the button light?
NavBar not giving animation
i recently try this method to add nav button. then i installed xposed and pixel nav button module. but, the animation not running well. on my other device the home button's ring rotating while charging. but on mi a1 its not animating
How to swap back and recent key?
Please find out a way to disable hw key lights permanently..
Ripon Raihan said:
Please find out a way to disable hw key lights permanently..
Click to expand...
Click to collapse
Looking into it.
Aman301582 said:
How to swap back and recent key?
Click to expand...
Click to collapse
Try swapping their values.
key 139 BACK VIRTUAL
key 172 HOME VIRTUAL
key 158 MENU VIRTUAL
MarkerBeanXDA said:
Try swapping their values.
key 139 BACK VIRTUAL
key 172 HOME VIRTUAL
key 158 MENU VIRTUAL
Click to expand...
Click to collapse
Swap is working!
Ripon Raihan said:
same problem, how to permanently off the button light?
Click to expand...
Click to collapse
Pretty sure you change the permission to read only so the system can't edit it. Could be wrong. Do it at your own risk.
envy63 said:
i recently try this method to add nav button. then i installed xposed and pixel nav button module. but, the animation not running well. on my other device the home button's ring rotating while charging. but on mi a1 its not animating
Click to expand...
Click to collapse
Try to flash the zip provided in this thread instead
Can you create a magisk version?
+1 for a Magisk version
another +1 for a magisk version