Used to be on galaxy nexus, I remember there's a script .zip which can be used to clean the existing kernel to prepare for a new kernel so ensure there wont be any conflict or incompatibilities there. Does anyone have something like it for Nexus 5? Can anyone sic? TIA!
anyone knows anything?
The only time that you need kernel cleaners are if the kernel creator modified the system binaries.
To my knowledge all custom kernels present are modifying only the boot.IMG so there is no need for a cleaner.
Usually of a Dev make a kernel that needs a cleaner. They will provide one for you.
Sent from my Nexus 4 using xda app-developers app
Yup, as above you only need a cleaner if a modified ramdisk was used.
4 months later... it would be useful now
Primokorn said:
4 months later... it would be useful now
Click to expand...
Click to collapse
They flash init.d scripts with different names and modify unknown system files, I can't see how this could be achieved without knowing what was modified Best way is to reflash ROM first
rootSU said:
They flash init.d scripts with different names and modify unknown system files, I can't see how this could be achieved without knowing what was modified Best way is to reflash ROM first
Click to expand...
Click to collapse
Yes but I hoped that each kernel developer who modifies the ramdisk provides the zip cleaner.
Dirty flashing the rom is a solution but sometimes it requires to put some stuff back like new system apps, custom dpi, xposed framework...
Primokorn said:
Yes but I hoped that each kernel developer who modifies the ramdisk provides the zip cleaner.
Dirty flashing the rom is a solution but something it requires to put some stuff back like new system apps, custom dpi, xposed framework...
Click to expand...
Click to collapse
It would be a case of asking each kernel developer to do this. I doubt they're reading this thread.
I have a single zip that I flash after my rom that does all my mods.. Deletes audio files, changes LCD Density in build prop, replaces boot animation etc. I haven't looked at adding Xposed in detail yet but it would be handy....
You could look into that
Related
I remember reading somewhere that when you flash a new kernel, some of the old tweaks are left on your phone and slow it down.
I'm trying to switch from trinity to Franco but I'm not sure if trinity left anything behind.
Is this true? Or am I imagining things.. -_-
Sent from my Nexus S using XDA App
baolongn said:
I remember reading somewhere that when you flash a new kernel, some of the old tweaks are left on your phone and slow it down.
I'm trying to switch from trinity to Franco but I'm not sure if trinity left anything behind.
Is this true? Or am I imagining things.. -_-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
The only thing that could get left would be some kernel modules placed under system....this has no effect on your system.
Sent from my Nexus S using xda premium
What is 99 tweak, 99 complete, and 95 dimmer in my init folder?
Sent from my Nexus S using XDA App
baolongn said:
What is 99 tweak, 99 complete, and 95 dimmer in my init folder?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
init scripts someone bundled with whatever update.zip you flashed. They are numbered to determine the order of execution by the init script in boot.
I have a question,
Say i am using a rom with a custom kernel, Not the one that came with the ROM, If i reflash the rom (without wiping data), Then i get Rom's default stock kernel, But will that remove the files and scripts that came with the custom kernel. Or do i need to do a fresh install to remove all the files of that kernel.
Also 95dimmers, 99 tweak and 99 complete come with the trinity kernels. It's advisable to remove them because they might cause issues when you install another kernel.
saranyan said:
I have a question,
Say i am using a rom with a custom kernel, Not the one that came with the ROM, If i reflash the rom (without wiping data), Then i get Rom's default stock kernel, But will that remove the files and scripts that came with the custom kernel. Or do i need to do a fresh install to remove all the files of that kernel.
Also 95dimmers, 99 tweak and 99 complete come with the trinity kernels. It's advisable to remove them because they might cause issues when you install another kernel.
Click to expand...
Click to collapse
It won't remove what is in /system/modules or /system/etc/init.d unless explicitly told to do so in the updater-script (I don't recall if it still supports delete off of the top of my head). The init scripts you should probably toast.
As your new kernel will write any modules it uses (wifi at a minimum) the modules are a non issue, but unused modules could be removed as well if desired.
Dont delete 99Complete. Rom wont boot then
snandlal said:
Dont delete 99Complete. Rom wont boot then
Click to expand...
Click to collapse
A full stock rom on a custom kernel shouldn't have any issues (going back to a stock kernel / ramdisk / boot image) as init.d scripts aren't used. A custom rom though is a different story.
Depends on the ROM package. Most (in fact all) of the ROMs I have tried, flash a native Kernel to avoid any initial boot-up/setup issues.
Just delete everything in init.d then reflash your desired kernel zip. It will replace anything that is supposed to be there. You should check your ROM zip for anything and copy that too.
Sent from my obnoxious finger using Swype
@zephiK , I installed the VomerTweaks on top of Mahdi rom and Franco kernel from your signature. I flashed it via TWRP , but dont know if its installed or is successfull etc. Can you let me know what exactly this tweak does and any way of finding if its active / installed ? Is there a option which appears in settings ? Thanks !
You didn't have to make a new thread for this.
To verify that the settings indeed have loaded, you need to use a kernel tweaker app (e.g. FKU, Trickster)... if you see that the maximum (fixed) CPU frequency is 1.2GHz then its loaded. A lot of the questions you asked are answered https://192.227.135.147/get/vomertweaks.txt (ignore the warning)
# What is it?
VomerTweaks is a tried and tested set of custom settings and power modes for your device!
The aim is to enable your device to have insane battery life without losing performance (all of us love da juice!)
We develop and test multiple configurations (for different "user types") & share them with the community.
Click to expand...
Click to collapse
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
shapethelola said:
Sorry but it's not showing that min. Cpu frequency on my device in fku but the file was installed correctly via twrp and I just checked it is in the correct location. Any other parameters I could check if it's working correctly somehow?
Click to expand...
Click to collapse
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
zephiK said:
Errr whoops, I messed that up. I meant to say Maximium CPU frequency.
Click to expand...
Click to collapse
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
You need to reinstall Franco if it's supported yet that's all
dayanandgp said:
LOL. I too was about to post the same question Thanks !! by the way , do i need to flash it everytime OTA arrives ?
Click to expand...
Click to collapse
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
You need to reinstall Franco if it's supported yet that's all
Click to expand...
Click to collapse
No, flashing a newer/older version of Franco does not touch this script at all.
zephiK said:
If you're on a custom ROM, it is not needed since a backup script is included.
If you're on CM11S, then you will need to reflash it on a OTA (Or even remove the script before being able to accept the OTA) since addon.d is not supported in CM11S.
No, flashing a newer/older version of Franco does not touch this script at all.
Click to expand...
Click to collapse
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
shapethelola said:
Okay, youre the boss. I just thought installing an ota update from cm11s will overwrite francos kernel and without francos kernel this vomer tweak wont work. What I basically was saying was you need to have a kernel of franco running after you updated your cm11s again.
Click to expand...
Click to collapse
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
zephiK said:
As I said before, CM11S does not support addon.d scripts so therefore it cannot back up the script. Even if the script was allowed to be backed up, the OTA will most likely not work due to changes being made to /system/ unless using a modified upgrade script to the OTA package.
If the user flashed the script without Franco Kernel, then it will simply just not be able to change certain parts since the path is invalid. And I think its pretty obvious that the user needs Franco Kernel for the script to work. The whole point of the script was to be revolved around Franco Kernel and not any other kernel, its not there to discriminate other kernels but kernel developers have their own paths to certain parameters. Its not uniform throughout the phone.
Click to expand...
Click to collapse
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Check this post for download links:
http://forum.xda-developers.com/showthread.php?p=55150676
Sent from the One
dayanandgp said:
@zephiK i cant find the link to Vomertweaks anymore in your signature. Is somthing wrong ? Did you delete it ?
I wanted to find out how to disable/delete for future , as it is surviving mahdi OTA's
Click to expand...
Click to collapse
I removed it since the links were just all over the place. Refer to nikzDHD's link above ^^.
To uninstall, just flash vt_uninstaller.zip
@zephiK sorry to ask this here, but is it possible for someone to build chroma rom for oneplus one? would be great right?
Hey guys, I was just wondering if someone could help me out with a problem.
I put ROMs on my phone at least once every month or so. The question I have is.
If I wanted to make sure I was cleaning up old kernel settings what would be the best steps to take.
Sometimes I just want to change kernel and not ROM. For example, I am on aicp ROM and would like to change
Kernel but I changed settings with kernel tweaker and I don't really know
How to make sure I got rid of settings before flashing next kernel.. Thanks in advance..
Hi edshawn911
There's a boot partition which actually contains the kernel You can wipe it with TWRP as far as I know
Furthermore I'd use the file manager (also available in TWRP) to take a look at your sdcard (internal storage). You might find some config files which were generated by your kernel tweaking app.
Just reflash/dirty flash your ROM then flash your new kernel. Clear data on any kernel apps if you use one. Nothing else.
when you flash a new kernel, itll clear out the old kernel settings automatically. but some kernels still leave behind stuff. most kernels are just kernels, while some add system files as well. you can check places like /etc/init.d and delete whatever is there if a kernel left some files.
experience7 said:
Hi edshawn911
There's a boot partition which actually contains the kernel You can wipe it with TWRP as far as I know
Furthermore I'd use the file manager (also available in TWRP) to take a look at your sdcard (internal storage). You might find some config files which were generated by your kernel tweaking app.
Click to expand...
Click to collapse
Thanks for response..
I usually backup the ROM I'm on with the included/stock kernel before flashing another kernel. When I want to switch, I simply restore the backup beforehand. My current backup has the barebones AOSP kernel.
So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.
Hi folks.
I'm new here.
It's my first post so please forgive me if there's something wrong.
Basically I want to know is, what type of knowledge do i need (programming language and other things) to work on root of android like build.prop and making custom roms and working on the custom recovery etc.
What do I need to learn to understand those things and work on them.
Thanks.
Kaksrocks said:
Hi folks.
I'm new here.
It's my first post so please forgive me if there's something wrong.
Basically I want to know is, what type of knowledge do i need (programming language and other things) to work on root of android like build.prop and making custom roms and working on the custom recovery etc.
What do I need to learn to understand those things and work on them.
Thanks.
Click to expand...
Click to collapse
Your question is not specific and I not sure exactly what information you requesting. For instance,
1 "root of android" ? Are you trying to root you're phone?
2. "build.prop"? Adding or modifying that can be done with an android app provided your device is already rooted. Ising ADB and fastboot may also be a possible.
3. " making custom roms" ? Does that mean installing or actually building a custom rom? Actually building a custom rom that is best left for advanced level developers. If, you mean installing a custun rom then generally speaking that is usually done in custom recovery by flashing a .zip file. Its very specific for each phone and carrier.
4. "working on custom recovery"? Depends on which custom recovery you have installed and what options are available. A YouTube search can provide some general information.
I am assuming you are interested in rooting you phone and unfair with all is necessary in order to do so. I suggest, searching for your specific model and carrier hear on XDA. For instence, I have a note 4, I search, "XDA Sprint Note 4".
Mr. JAVI said:
Your question is not specific and I not sure exactly what information you requesting. For instance,
1 "root of android" ? Are you trying to root you're phone?
2. "build.prop"? Adding or modifying that can be done with an android app provided your device is already rooted. Ising ADB and fastboot may also be a possible.
3. " making custom roms" ? Does that mean installing or actually building a custom rom? Actually building a custom rom that is best left for advanced level developers. If, you mean installing a custun rom then generally speaking that is usually done in custom recovery by flashing a .zip file. Its very specific for each phone and carrier.
4. "working on custom recovery"? Depends on which custom recovery you have installed and what options are available. A YouTube search can provide some general information.
I am assuming you are interested in rooting you phone and unfair with all is necessary in order to do so. I suggest, searching for your specific model and carrier hear on XDA. For instence, I have a note 4, I search, "XDA Sprint Note 4".
Click to expand...
Click to collapse
Well. First of all thanks for the reply.
I do have the knowledge on how to root the device and i have my device rooted.
I know how can i modify the build.prop file.
But i want to know how the tweaks are actually made to put them in build.prop file to get it into work. How that tweak is made.
How to know what actually should i edit and etc.
And for custom roms. I do actually want to know about how to actually make a custom rom. Even though if its a high level thing. I still want to know. So that i can start learning and get in that field.
I want to know how custom recovery is made. For ex how twrp was made. And i want to learn its functionality.
Thanks again for the reply.
Kaksrocks said:
Well. First of all thanks for the reply.
I do have the knowledge on how to root the device and i have my device rooted.
I know how can i modify the build.prop file.
But i want to know how the tweaks are actually made to put them in build.prop file to get it into work. How that tweak is made.
How to know what actually should i edit and etc.
And for custom roms. I do actually want to know about how to actually make a custom rom. Even though if its a high level thing. I still want to know. So that i can start learning and get in that field.
I want to know how custom recovery is made. For ex how twrp was made. And i want to learn its functionality.
Thanks again for the reply.
Click to expand...
Click to collapse
I
You welcome and I also Thank you for responding.
In regards to modification of build.props, I advise beginning with custom recovery and making a full back- up (all partitions). I have soft bricked my phone more that once by modifying build.pros and simply did a full wipe and restored my backup and up and running. Kernel Aduitor is an app that provides a Build prop Editor but there are stand alone app that are also available.
If your custom recovery is TWRP then Tipatch is an app that is worth looking into. Its available here on XDA or can be downloaded via Google Play Store.
Odex Roms vs Deodex Roms and what that means. I suggest Deodex if your plan on modifying and/or porting.
Also good to know the differences between kerels permissive vs enforcing.
Apps= ApkTool X, Apk Editor v1.3,(this is a lower version that offers a rebuild function while the updated version available from Google Play dose not) Md5 , and ZArchiver.
As far as how to make custom roms? Thats above my skill level. However, If you download a custom rom make a copy and rename it, then use a root file manager to extract it or ZArciver app and look threw the files of the rom. May help prove helpful in learning basic structure.
Keep in mind I am not a developer. Modified, porting, flashing, treaking I do often. For instance, Im tunning and od Note 4 on marshmallow 6.0.1 and have official Google Play Dark Theme.
If you have any questions
https://forum.xda-developers.com/android/themes/official-google-play-store-dark-theme-t3977061
Mr. JAVI said:
I
You welcome and I also Thank you for responding.
In regards to modification of build.props, I advise beginning with custom recovery and making a full back- up (all partitions). I have soft bricked my phone more that once by modifying build.pros and simply did a full wipe and restored my backup and up and running. Kernel Aduitor is an app that provides a Build prop Editor but there are stand alone app that are also available.
If your custom recovery is TWRP then Tipatch is an app that is worth looking into. Its available here on XDA or can be downloaded via Google Play Store.
Odex Roms vs Deodex Roms and what that means. I suggest Deodex if your plan on modifying and/or porting.
Also good to know the differences between kerels permissive vs enforcing.
Apps= ApkTool X, Apk Editor v1.3,(this is a lower version that offers a rebuild function while the updated version available from Google Play dose not) Md5 , and ZArchiver.
As far as how to make custom roms? Thats above my skill level. However, If you download a custom rom make a copy and rename it, then use a root file manager to extract it or ZArciver app and look threw the files of the rom. May help prove helpful in learning basic structure.
Keep in mind I am not a developer. Modified, porting, flashing, treaking I do often. For instance, Im tunning and od Note 4 on marshmallow 6.0.1 and have official Google Play Dark Theme.
If you have any questions
Click to expand...
Click to collapse
Great. Thanks for the information you provided.
You were pretty helpful.
So again thanks.