Database Users

[GUIDE] Porting Guide - How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs

Use wisely!!
If you plan to use it, please share anything that might be missing or any step taken to resolve bootloops, FC's, etc.
:good: Thanks and Credits to: :good:
Peteragent5- Original Thread:
http://forum.xda-developers.com/showthread.php?t=1598713
GalaxyUser for his great contribution on this tutorial!
[Disclaimer]
I'm not responsible for any problems this may cause on your phone.
And I will repeat this.
I'm not responsible for any problems this may cause on your phone.
!!!YOU DO THIS UNDER YOUR OWN RISK!!!
-----------------!!!!IMPORTANT!!!!-----------------
This tutorial is not meant to port the following Touchwizz, Sense, Motoblur or from different vendors
If your Device is not from the same manufacturer, unpack the kernel and edit the BOOTCLASSPATH in init.rc to match the BASE kernel and then repack Kernel
You can try, but it's under you own risk.
-----------------!!!!IMPORTANT!!!!-----------------
IMPORTANT:
1. You must know if your Device is Armv7, Armv6, or Armv5. YOUR BASE AND PORTED MUST BE THE SAME CPU!!
''''''Nexus S is ARMv7''''''
Example: SGS I9000 can be used as PORT.​List of Devices CPU:
http://forum.xda-developers.com/showthread.php?t=1596800
2. If your BASE has problems, then your ported ROM is going to have the same problems.
3. Make sure both PORTED and BASE are on the same Android Version. As for what I know, you cannot Port ROM on GB using Base on ICS and viceversa.
So let's get started geeks and trolls:
[PROCEDURE]
Step 1. ROM Download
Download ROM you want to 'PORT' and download ROM you want to use as 'BASE'.​
Step 2. Unzip
Unzip both PORT and BASE on separate folders (Just to keep it clean).​
Step 3. [OPTIONAL] Backup important files
Make a backup of the following files from both PORT and Base (This is just in case you have the original one)(modify the name with something unique to the ROM - add it at the end maybe):
/system/lib/libandroid_runtime.so
/META-INF/com/google/android/updater-script
/system/build.prop​
Step 4. Backup and copy important Apps
From BASE, backup the following from /system/app:
stk.apk
vpnservices.apk
camera.apk
bluetooth.apk
VpnDialogs.apk
nfc.apk
tag.apk
Add these apps into PORTED /system/app folder.​
Step 5. Inside Ported
Remove kernel:
boot.img | zImage | kernel.sin | etc...
Remove folders on PORTED /system:
cameradata
tts
usr
vendor
modules
/etc/wifi
Now you get 2 options:
Delete bin & xbin & lib folder, but keep libandroid_runtime.so inside /system/lib
Keep bin & xbin & lib folder
Explanation:
If PORTED has no tweaks or addons to those folders.
If PORTED has tweaks and addons.
Remove every folder inside /system/etc except:
init.d
permissions
license
Remove the following inside META-INF:
CERT.RSA
CERT.SF
MANIFEST.MF
Remove: META-INF/com/google/android/update-binary​
Step 6. Inside Base
Move kernel to PORTED:
boot.img | zImage | kernel.sin | etc...
Delete libandroid_runtime.so inside /system/lib
Move the following inside /system to PORTED:
(If prompted, select YES to copy and Replace all)
cameradata
bin
lib
tts
usr
vendor
firmware
modules
wifi
xbin
(If prompted, select YES to copy and Replace all)
Move everything inside /system/etc
To: PORTED's /system/etc
(If prompted, select YES to copy and Replace all)
Move: META-INF/com/google/android/update-binary
To: PORTED's META-INF/com/google/android/
For ICS & Newer:
Move the following inside /system/media to PORTED's media:
LMprec_508.emd
PFFprec_600.emd​
Step 7. Build.prop edition
Open /system/build.prop from both PORTED and BASE with Notepad++ (or any other text editor you like)
Edit PORTED build.prop to match BASES's build.prop.
!!!IMPORTANT!!! - Make sure the following fields on the PORTED matches your BASE fields:
ro.build.description=
ro.build.fingerprint=
ROM WILL NOT boot without this.
Most of the options that would need to be modified are from the 'build properties' section.
Copy & Replace the following:
ro.modversion
ro.cm.version
ro.config.ringtone
ro.config.notification_sound
ro.config.alarm_alert
ro.config.sms_received_sound
ro.config.sms_delivered_sound
persist.sys.themeId
persist.sys.themePackageName
and anything similar to that, to: BASE's build.prop
For MIUI:
Add & Make sure the following values are like this:
ro.build.id=MIUI
ro.build.display.id=MIUI x.x.x
ro.build.version.incremental=x.x.x
ro.config.ringtone=MI.ogg​
For Lewa OS:
Add & Make sure the following values are like this:
ro.build.display.id=LeWa_ROM_DeviceNickname_xx.xx.xx
ro.lewa.version=LeWa_ROM_DeviceNickname_xx.xx.xx
ro.lewa.device=DeviceNickname
ro.lewa.swapper.part_path=PORTED's_Value
ro.lewa.swapper.flash_swappiness=PORTED's_Value
ro.lewa.swapper.sd_swappiness=PORTED's_Value
ro.error.receiver.system.apps=com.lewa.fc
ro.error.receiver.default=com.lewa.fc​
Make sure the following is for your Device:
rild.libpath=
rild.libargs=
Inside BASE:
Highlight from: ro.build.tags=
to: # ADDITIONAL_BUILD_PROPERTIES
Copy & Replace that highlighted part to: PORTED's build.prop's highlighted part
Copy everything from: # ADDITIONAL_BUILD_PROPERTIES
To: the end of the file
Paste it to PORTED's build.prop
Save PORTED build.prop.
For XPERIA devices:
The whole build.prop is untidy and filled with tweaks and addons.
To edit an XPERIA build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do​
For HTC devices (Sense):
The whole build.prop is filled with tweaks, addons and extra libs values.
To edit an HTC build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do​
Step 8. META-INF updater-script edition
Inside BASE:
Move the following, to PORTED:
(If prompted, select YES to copy and Replace all)
META-INF/com/google/android/update-binary
META-INF/com/android/metadata
META-INF/com/android/otacert
Open /META-INF/com/google/android/updater-script from both PORT and BASE.
8.a. Modify PORTED updater-script
8.b. Replace 'assert' line in PORTED with the one on BASE.
'assert' will verify 'build.prop' values to make sure you are flashing a ROM meant for your device.
Make sure any 'assert' check matches your BASE build.prop field.
If this check fails, you will most likely get CWM error status 7 (if I'm not mistaken)
8.c. Replace 'format' and 'mount' lines in PORTED with the ones on BASE. Should be like this:
format("ext4", "EMMC", "/dev/block/platform/s3c-sdhci.0/by-name/system", "0");
mount("ext4", "EMMC", "/dev/block/platform/s3c-sdhci.0/by-name/system", "/system");
This is a HIGHLY important step, so don't miss this step.
8.d. If 'retouch_binaries' exists on BASE, copy line into PORTED file where SYMLINKS ends. Replace if necessary.
8.e. DO NOT CHANGE ANY SYMLINK on PORTED.
8.f. Change/Edit/Add 'set_perm' from BASE to PORTED (Take note of the added set_perms & set_perm_recursives that PORTED added. Then replace all set_perm and set_perm_recursive from BASE to PORTED. Put back in the noted set_perms & set_perm_recursive you wrote down, to PORTED's updater-script(If the updater-script in PORTED is modded to have tweaks & addons do the set_perms procedure above)).
8.g. Modify any 'ui_print' as you wish.
8.h. The installation of the kernel (Something like: assert(package_extract_file("boot.img",)
8.i. Save PORTED updater-script.
8.j. Now use BASE's entire META-INF Folder. Copy it to PORTED (Do not replace the updater-script we just modified).
ALWAYS use COMMON SENSE to edit build.prop and updater-script to avoid bricks!
For MIUI v4:
Add the following values to PORTED:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");​
Step 9. Porting from a different Manufacturer
If you are porting from a different manufacturer like, HTC or Sony, you have to check the kernel from them.
Unpack the kernel from PORTED
Unpack your Device's kernel
Open PORTED's init.rc
Replace the BOOTCLASSPATH from PORTED's init.rc to BASE's init.rc
Compare the two files, and addon to your Kernel's init.rc
Packup/Repack your Kernel​
Step 10. Clean your workspace
Double check the ROM if it has any leftover files or folders you need to modify or edit.
And delete any file or folder if it has nothing to do with your Device.​
Step 11. Assure Boot Image
Make sure you replace the Kernel with one compiled for your Device.
This needs to be on '/' and named boot.img​
Step 12. Add what you want
If you like to add special apps, or update the existing ones like Superuser and it's Binaries, Busybox, and more, you can do it now!
Maybe add Beats Audio, XLoud, MegaBeatsBass?? Your Choice!! Goooo crazy!​
Step 13. Zip your ROM and tranfer to SDCARD
PORTED is your final ROM.
Now zip your ROM Workspace (You can compress the zip).
You can also sign your ROM but it's not necessary.
But if your recovery only reads signed zips, then sign your ROM.​
Step 14. Don't worry, be HAPPY!!
If you encounter any problems during flash, boot, or processes FC'ing:
ADB Logcat and DDMS are your FRIENDS....and maybe Google.​
Happy Porting!!!

How to Debug / ADB & DDMS
ADB:
1. Connect device via USB.
2. Make sure Debugging is ON.
3. Open CMD Prompt and Type:
adb logcat -v long​
DDMS:
1. Connect device via USB.
2. Make sure Debugging is ON.
3. Open CMD Prompt and Type:
ddms
DDMS window will open.
4. Select your device on the top left panel.
5. You can see all messages now being logged. For any problems, where it says 'verbose' choose 'Error' on the dropdown box You can also use 'warn'.​
NOTE: I am still swallowing all of this information myself. Please do NOT expect me to have all answers. In fact, I will probably have a few (maybe one or two ).
Hopefully we can get input from more knowledgeable people when it comes to Logcats and DDMS errors.

Other Guides / General Info / Common Errors
JB Port Thread:
http://forum.xda-developers.com/showthread.php?t=1739561
Swamp Goblin Nexus S Porting Thread:
http://forum.xda-developers.com/showthread.php?t=1603363
MIUIv4 Guide:
http://forum.xda-developers.com/showthread.php?t=1499411 - Thanks to proxuser!!
Logcat Help:
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise/
http://www.xda-developers.com/xda-t...an-ports-and-helping-devs-with-logcat-xda-tv/
Screen resolution does matter. LCD density in the build.prop needs to match your Device's LCD density.
For the best Port result, your Ported and Base should be the same MDPI, HDPI, or LDPI
ldpi - Resources for low-density (ldpi) screens - 120dpi
mdpi - Resources for medium-density (mdpi) screens - 160dpi - This is the baseline density
hdpi - Resources for high-density (hdpi) screens - 240dpi
xhdpi - Resources for extra high-density (xhdpi) screens - 320dpi
Build.Prop Info:
http://forum.xda-developers.com/showthread.php?t=1639104 - Thanks to H M Judge
http://forum.xda-developers.com/showthread.php?t=1151608 - Thanks to Master&Slave
Want to learn how to theme???
http://forum.xda-developers.com/showthread.php?t=916814 - Thanks to theimpaler747
Common Errors:
1. When flashing ROM it says Installation aborted status (6)
Status 6 ussually means some syntax error in updater-script, check it, maybe you missed a ; or " somewhere.
2. When flashing ROM it says Installation aborted status (7)
Check 'assert' on updater-script and make sure it matches build.prop fields.
3. On Logcat:
E/JNIHelp ( 166): Native registration unable to find class 'android/debug/JNITest', aborting
F/libc ( 166): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
Usually means a Framework.jar issue.....don't ask me what to do lol
4. FIX Tethering (CM7)
Decompile framework-res.apk, edit theses to files:
--[arrays.xml]
Quote:
Change the correspondant lines with this:
<string-array name="config_tether_usb_regexs">
<item>usb0</item>
</string-array>
<string-array name="config_tether_wifi_regexs">
<item>wl0.1</item>
</string-array>
<array name="config_tether_dhcp_range" />
<string-array name="config_tether_upstream_regexs">
<item>rmnet\\d</item>
<item>eth\\d</item>
</string-array>
--[bools.xml]
Quote:
<bool name="config_tether_dun_required">false</bool​Recompile framework-res.apk

i am porting rom from galaxy S(hdpi) to galaxy ace plus(mdpi).... do i need to re-size system apps and frameworks or something else.... what if i change lcd density will it work... and also which should i port first cm7 or miui... i get sucked or phone restarts again and again in my miui port....
or else can you suggest me any galaxy phone which is arm7 and have mdpi display..... i cannot find it...
Oogway13 said:
MIUIv4 Guide:
http://forum.xda-developers.com/showthread.php?t=1499411 - Thanks to proxuser!!
Logcat Help:
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise/
http://www.xda-developers.com/xda-t...an-ports-and-helping-devs-with-logcat-xda-tv/
Screen resolution does matter. LCD density in the build.prop needs to match your Device's LCD density.
For the best Port result, your Ported and Base should be the same MDPI, HDPI, or LDPI
Common Errors:
When flashing ROM it says Installation aborted status (6)
Status 6 ussually means some syntax error in updater-script, check it, maybe you missed a ; or " somewhere.
When flashing ROM it says Installation aborted status (7)
Check 'assert' on updater-script and make sure it matches build.prop fields.
On Logcat:
E/JNIHelp ( 166): Native registration unable to find class 'android/debug/JNITest', aborting
F/libc ( 166): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
Usually means a Framework.jar issue.....don't ask me what to do lol
Click to expand...
Click to collapse

For what I know, you cannot port from different densities. But, there is a build.prop option:
ro.sf.lcd_density=
You can try setting this value to the one you want.
For the CM7, MIUI question, I would start with CM7 since MIUI ports require some other dependencies.
This thread can provide you insight of all ARM devices:
http://forum.xda-developers.com/showthread.php?t=1596800

My build.prop dont have this line...should i add it... sry fir the noob question...
I saw all devices in armv7 none have hvgi....
Sent from my GT-S7500 using xda premium

Yes, you can add it (make sure you backup the original one).
But, be aware that, for optimal conditions, both devices must be HDPI/MDPI or else you must resize everything.
As a side note:
ldpi Resources for low-density (ldpi) screens (~120dpi).
mdpi Resources for medium-density (mdpi) screens (~160dpi). (This is the baseline density.)
hdpi Resources for high-density (hdpi) screens (~240dpi).
xhdpi Resources for extra high-density (xhdpi) screens (~320dpi).

The only part of this guide I'm having part with is the build.prop. Should I be making the build.prop in ported match EXACTLY with the build.prop in my base? Such as deleting lines in ported that aren't in base, changing properties after the ='s in ported that are different from base, and adding lines that aren't in ported but in base? I know it says use common sense when editing the build.prop, and my common sense is telling me to just change properties that relate to the device. Such as model, brand, name, device, board, product, characteristics to nosdcard(nexus s has none), adding ro.cm.device=crespo after characteristics, board platform...Am I right in thinking that or just horribly wrong? Help me please. Lol.

Well, all product info own to Nexus S have to be changed (build properties section).
Now, some other options within this file may be tweaks added by the DEV on the PORTED ROM. I cannot speak for all setting on this file, but you can check the links for build.prop on the 2nd post.
Here's where common sense come into play. If you see any setting that may not apply to Nexus S, remove it!
Do you have both build.props? What error do you receive on CWM when flashing? Is your 'Assert' on META/INF calling the right information on build.prop?
Are you debugging via Logcat or DDMS?

I have both build.props.
In CWM, upon flashing, I get the following output:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
This is my assert lines. (Is the position of the assert supposed to be before or after all the symlinks and set_perms?):
assert(getprop("ro.product.device") == "crespo" ||
getprop("ro.build.product") == "crespo");
And for some reason, I can't get my phone to connect to adb. Would updating my bootloader version have anything to do with this? Possibly the rom? I have drivers installed and windows recognizes my device, just not adb.

So lets say you wanted to port a GSM nexus S ROM to the 4G. What is the main folder/whatever that would allow the 4G unit to get service after the port?

DefinitiveX said:
I have both build.props.
In CWM, upon flashing, I get the following output:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
This is my assert lines. (Is the position of the assert supposed to be before or after all the symlinks and set_perms?):
assert(getprop("ro.product.device") == "crespo" ||
getprop("ro.build.product") == "crespo");
And for some reason, I can't get my phone to connect to adb. Would updating my bootloader version have anything to do with this? Possibly the rom? I have drivers installed and windows recognizes my device, just not adb.
Click to expand...
Click to collapse
Assert should be the first lines on your updater-script. What the 'assert' does is make sure you don't flash a ROM which is not meant for your device. So, this basically checks a few stuff on the build.prop.
In your case, it checks the following fields on the build.prop: ro.product.device= & ro.build.product=
Make sure those fields are 'crespo' (without quotes).
For the ADB issue, if 'adb devices' doesn't returns anything, then you might need to update your drivers.

NYYFan325 said:
So lets say you wanted to port a GSM nexus S ROM to the 4G. What is the main folder/whatever that would allow the 4G unit to get service after the port?
Click to expand...
Click to collapse
To be honest, I don't know, but all of these files are left untouched on your base. Notice that on the port process, we modify apps/framework/fonts/media and other files, and leave most of the base with the original files.

Oogway13 said:
To be honest, I don't know, but all of these files are left untouched on your base. Notice that on the port process, we modify apps/framework/fonts/media and other files, and leave most of the base with the original files.
Click to expand...
Click to collapse
Yeah I found it last night after some digging lol

NYYFan325 said:
Yeah I found it last night after some digging lol
Click to expand...
Click to collapse
Were you able to port the GSM ROM?

Oogway13 said:
Were you able to port the GSM ROM?
Click to expand...
Click to collapse
Yeah, I got it booting with service and wifi and all that good stuff. I think I left some stuff out though I was having some very minor issues. Pretty sure I missed some libs. Not bad for my first time though

Oogway13 said:
Assert should be the first lines on your updater-script. What the 'assert' does is make sure you don't flash a ROM which is not meant for your device. So, this basically checks a few stuff on the build.prop.
In your case, it checks the following fields on the build.prop: ro.product.device= & ro.build.product=
Make sure those fields are 'crespo' (without quotes).
For the ADB issue, if 'adb devices' doesn't returns anything, then you might need to update your drivers.
Click to expand...
Click to collapse
I downloaded samsung drivers and ran the intall program, tried to update drivers manually with googles usb drivers but couldn't find my device listed in the device manager, even though windows recognizes the device.

DefinitiveX said:
I downloaded samsung drivers and ran the intall program, tried to update drivers manually with googles usb drivers but couldn't find my device listed in the device manager, even though windows recognizes the device.
Click to expand...
Click to collapse
Which guide are you using for this?
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Just in case, you have USB Debugging ON right?

NYYFan325 said:
Yeah, I got it booting with service and wifi and all that good stuff. I think I left some stuff out though I was having some very minor issues. Pretty sure I missed some libs. Not bad for my first time though
Click to expand...
Click to collapse
Niiiice!! If you have any suggestions for the guide, just let me know :silly::good:

Oogway13 said:
Which guide are you using for this?
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Just in case, you have USB Debugging ON right?
Click to expand...
Click to collapse
Wasn't using a guide, actually, unless the usb drivers were in a guide. I just searched on google for the drivers, went to the page, and downloaded them. I will check out that guide though. And yes, I always have USB Debugging enabled on my device.
And just so I'm sure...You said that the assert goes before everything in the updater-script, so, before or after the ui_prints? I currently have it positioned before.

[TWEAKS/SCRIPTS/DOWNLOADS]~ BEST TWEAKS EVER ~ ((26-Oct))

Some great stuff from Amazing devs
-Androguide.fr Pimp My Rom {the best tweak :good:} ((October 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1908269[/url]
- AC!D AUDIO ENGINE Developers ((amazing sound experince))
Code:
[url]http://chautemseric.wix.com/acidaudiotechnology#!devices-support/cdfs[/url]
-croniccorey CronMod-A2SD/D2EXT/INT2EXT {best A2SD tweaks} ((updated 09/19))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909374[/url]
- CarlDeanCatabay Increase RAM using Swap File and Swap Partition and SD card partitioning ((great one try it))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1659231[/url]
-hyperbolic The Complete Guide For Maximum Battery Life {great battery life}
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909996[/url]
-PIT Tech GameBooster ★ root {great games experience }
Code:
[url]https://play.google.com/store/apps/details?id=com.burakgon.gamebooster[/url]
-OOM groupings and priorities tweaks - SuperCharger ((add it with loopy))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=991276[/url]
-Loopy Smoothness tweak ((add it with SuperCharger))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1137554[/url]
[url]http://forum.xda-developers.com/showthread.php?t=1205744[/url]
-droidphile Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs ((15th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1369817[/url]
-jader13254 MooDeD Holo Camera
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1742758[/url]
-Rizal Lovins Camera Mod v.4.0 Cybershot Experience
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1918744[/url]
-Arcatarc NotificationLedFix for 4.1.B.0.587 ((17th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1840114[/url]
Other tweaks or guidelines
-Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
You can use AdFree application for this or changing manually your hosts file.
Code:
[url]http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts[/url]
-Use UOT kitchen for basic theming on your device.
Code:
[url]http://uot.dakra.lt/[/url]
-Disable sync feature in sqlite
(author: ownhere - needs a source for your device so you can compile the /system/lib/libsqlite.so)
Code:
[url]http://forum.xda-developers.com/showthread.php?t=903507[/url]
-Use CyanogenMOD's APN list file - one of the most complete located in
Code:
/system/etc/apns-conf.xml
-Do not use task killers.

for GOD sake ... don't use them all... SELECT/MODIFY according to your ROM and what you want.
WARNING
Note: if you don't know what you are doing please don't try. read first and make sure you understand what you are doing and make a backup before doing any mods. i am not responsible for messing up your device but the ARC community and i may assist.
TO WHO CARE TO KNOW
What is build.prop:
- The build.prop file is your android handset’s ‘ID card’.
- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.
- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.
- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.
- The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don't know what you are doing, you can actually decrease the performance of your device. Over time I will investigate more build.prop properties to determine which ones can actually enhance your Android experience and which ones only create a placebo effect
XperienceD said:
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also sift through what works and what doesn't.
Click to expand...
Click to collapse
WAIT
REQUIREMENT BEFORE YOU START :-
- Make a NANDROID BACKUP
- If you have any V6 Supercharger tweaks installed, un-supercharge before doing these tweaks. Once finished, you may re-supercharge and
- Root (Superuser/Busybox/Terminal Emulator/ES File Explorer),
- kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/)This requires edits in build.prop and the use of terminal emulator
- If your build.prop has an additional build properties section the line of code needs to go in there
(If lines starting with dalvik.vm.checkjni=false or windowsmgr.max_events_per_sec=300 exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
How to
Replace OR tweaks Build.prop :-
1. Download Es File Explorer ((OR ANY APP LIKE IT))
2.CLick menu, settings, check Root Explorer and Mount File System
3.Copy the Build.prop file into the sd card and copy with file manager
4.Click Favorites tab, Click Phone icon /
5.Navigate to system/
6.Rename build.prop to build.bak
7.Paste build.prop you copied earlier Reboot! Done! :good:
Build.prop tweaks((UPDATED 26-Oct))
Add these at the end of your build.prop
Code:
IN THE ATTACHMENT
~ Free Up More RAM, Make Apps Load Faster ~
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
Code:
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
{
"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"
}
2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite
.
(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
Code:
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
After this, run these two commands in adb shell or terminal emulator
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**
How to UNDO this tweak
Type the following in adb shell or terminal emulator
((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))
Code:
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.
Init.d tweaks ((UPDATED 26-Oct))
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
Note:
1- If you have init.d problem or if not have init.d folder try add this line at hw_config.sh
2- some (needs zipalign bin) #!/system/xbin/bash,so it needs the bash file in the /system/xbin folder in order to work
Code:
I COLLECT A LOT OF THEM
IT TOOK ME ALLOT OF TIME AND EFFORT
I PUT THEM IN TEXT
IN THE ATTACHMENT
DELETED WHICH IS DUPLICATED
& MODIFIED SOME
I COULDN'T WRITE THEM ALL HERE
CAUSE ITS SO BIG TO WRITE IT HERE
THEY JUST ALLOW AMOUNT OF LINE FOR ME
SO I PUT THEM ALL IN TEXT DOCUMENT IN THE ATTACHMENT
EVERY DEVS NAME NEAR HIS SCRIPTS
ANYONE COULD DO THEM IN FLASH ABLE ZIP IT WILL BE GREAT
GOOD LUCK TO ALL
THE RAR IS JUST THE TWEAK NOT FLASH ABLE ONE
sysctl tweaks ((UPDATED 26-Oct))
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
-To activate sysctl tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
-sysctl.conf
Code:
IN THE ATTACHMENT

Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
I COLLECT MOST OF THEM AND WE WILL POINT WHAT IS FAKE AND WHAT IS NOT
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal​

Thanks for the info man
But just some advice, I found that some of the tweak mentioned above is somewhat experimental
I forgot which ones, but after doing some research on google, they are indeed not yet fully tested (the effect is still unnoticeable)
And it will be great if you make the thread (2nd post to be more specific) to be more tidy
There are same tweaks mentioned more than one time, it might not good for people to copy and paste the tweaks directly from your thread
Cheers

fakhreza said:
Thanks for the info man
But just some advice, I found that some of the tweak mentioned above is somewhat experimental
I forgot which ones, but after doing some research on google, they are indeed not yet fully tested (the effect is still unnoticeable)
And it will be great if you make the thread (2nd post to be more specific) to be more tidy
There are same tweaks mentioned more than one time, it might not good for people to copy and paste the tweaks directly from your thread
Cheers
Click to expand...
Click to collapse
MAN
First thanx to tell me about my mistake of putting the same tweaks twice
Second i tidy it more now every tweak title will start with #
Third experimental yes some r but u will see improvment
thanx again

dr said:
Third experimental yes some r but u will see improvment
thanx again
Click to expand...
Click to collapse
And some just don't work - http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/

XperienceD said:
And some just don't work - http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Click to expand...
Click to collapse
sorry for that :angel:
am just trying to help
i just updated for other new stuff and cool tweaks
best wishes

i add huge update and new tweaks and arrange it in better way

dr said:
i add huge update and new tweaks and arrange it in better way
Click to expand...
Click to collapse
thanx great collection

dr said:
am just trying to help
Click to expand...
Click to collapse
So am I.

If these things really improve experience, why Sony didn't add theme to their devices in official roms ?
They are professional developers after all ?

XperienceD said:
So am I.
Click to expand...
Click to collapse
thanx :good:
n4ki said:
If these things really improve experience, why Sony didn't add theme to their devices in official roms ?
They are professional developers after all ?
Click to expand...
Click to collapse
why sony didn't fix led bug and they did it here
why sony roms vs good modified stock roms suck
so simple
welcome to android world

dr said:
thanx :good:
Click to expand...
Click to collapse
I found that link whilst searching for mods and used to use some myself, but when you take in to account...
The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don’t know what you are doing, you can actually decrease the performance of your device.
Click to expand...
Click to collapse
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also shift through what works and what doesn't.

yes as i already said in an other thread, it would be helpful known which of these improove our Arc/Arc S and which one deprove some roms, for example the JS 6.1 which im using

XperienceD said:
I found that link whilst searching for mods and used to use some myself, but when you take in to account...
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also shift through what works and what doesn't.
Click to expand...
Click to collapse
noooooooooooooooooooooooooooooooooooooooooooo
noooooooooooooooooooooooooooooooooooooooo
noooooooooooooooooooooooooooooooooo
i didnt take it in to account really its my first time to make thread and i thought u attak me while those not mine
in other way u can say it in deffrent way so i will understand what u want me to understand i will add ur link to the collection
am sorrrrrrrrrrrrrrrrry really soooooooooooo much if i efended u
and thats right lets start to see what is working and what is not
by the way i add and correct some
and trying to do what i can do for helping whom i can
again thanx and soooooooooory if i did something bad
danybhai said:
thanks
Click to expand...
Click to collapse
at ur service alll the time welcome
deniel said:
yes as i already said in an other thread, it would be helpful known which of these improove our Arc/Arc S and which one deprove some roms, for example the JS 6.1 which im using
Click to expand...
Click to collapse
for me i dont use any rom i just root the stock one and play with it for me the last build one works with me
although i went through the web and see some and puts the best value for the best berformance and whats work with me maybe didnt work with u so try and tell us it will be great help

dr said:
again thanx and soooooooooory if i did something bad
Click to expand...
Click to collapse
No offence taken, obviously just a mis understanding.

Thankx for ur hardwork

xperienced said:
no offence taken, obviously just a mis understanding.
Click to expand...
Click to collapse
glad to hear that
cimi244 said:
thankx for ur hardwork
Click to expand...
Click to collapse
all the time welcome
glad to help

why
i get bootloop
alllllllllllllllllllllllllllllllllllllllllllllll
the time when i update the Build.prop tweaks
in JELLY SANDWICH 6.1
and i noticed also the same thing
some Build.prop tweaks repeated twice but with deffrint value in defferint tweak pak
but the rom work like charm :laugh: any idea

dr said:
Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))​
- first one by XperienceD thanx
Click to expand...
Click to collapse
The battery tweaks that you posted in the second post - what does they improve? Huh?

[WORKAROUND] Bootloops due leaking handles with Xposed in Lollipop

Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.

Excellent work friend @ondrejvaroscak. Congrats! Awesome

Was waiting a long time for this! Thanks man! working perfectly.

Working perfectly on D6603, thanks

I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button

Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?

Thanks Bro , Very Nice !!
Perfect Work !!

Z1, C6903
Thank you for this great solution, works on Z1.

NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app

norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..

Working on fully setup 5.02 on Z2 thanks.

ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa

hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).

Ok fine... for verify all you said:
{
"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"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?

hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app

Great thanks

ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa

In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !

Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line

hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?

[KK][4.4.4] Debloating script for xperia phones running KK

***LOOKING FOR A ALL-IN-ONE SOLUTION? THAT'S AVAILABLE FOR Z3C USERS ONLY, IF INTERESTED GO HERE***
I guys, similarly to what I did for LP, and considering that even in the LP time some people asked me about debloating KK (and I'm using it right now and actually seems i like it more than LP too) I share with you my debloating script for those interested in a higly DEBLOATED KK installation, very slimmed down, battery friendly, faster, with less RAM comsuption etc
Heavily debloated actually means almost 900 mb of system stuff moved to a backup folder (that you can even delete or move to sdcards to get 900mb extra free space in /system) so applying my script you agree to debloat A LOT as I did but take care that you will have a much lighter system and still you will be able to restore very easily anything you want anytime moving stuff back from the backup folder to /system (detailed instructions for that below in this thread).
NOTES
1. as all the stuff object of my debloating script is going to be placed in /system when flashing the pre-rooted FW, it is strongly suggested to apply my script immediately after flashing the pre-rooted KK FW and before rebooting, this way all that stuff will be moved away, and it is like it was never installed (at first boot no optimizations for those apps, means faster first boot etc)
2. using different FW as base you may have some more bloat/apks, not present in my FW, that will remain installed. In this case, if you think there is some bloat left that could be removed, please send me a list of all your system apps remained after debloating, so i can check them (you can easily do that via terminal with 'ls /system/app > /sdcard/sysapps.txt' and 'ls /system/priv-app > /sdcard/privapps.txt' and send me the resultant text files)
Click to expand...
Click to collapse
Procedure for all xperia phones running KK:
Requirements:
- working recovery
- be on KK 4.4.4 already
Installation:
1. full nandroid backup to eventually go back to previous any time
2. wipe data, cache and dalvik ***
3. flash my Debloating Script for KK
4. that's all! reboot/enjoy
*** NOTES
1. you can skip wiping data, so you'll keep all your personal data! But please mind that not wiping data during the installation procedure the debloat will not be 100% effective: in fact, if you don't wipe data, all the sony apps installed in /data/app won't be removed by the script! (to remove them, you'll have to uninstall them manually from settings > apps > downloaded)
2. not full wiping, you may also get some FC due to missing overlays at boot: in this case, just enter in TWRP, mount system, go to advanced > file manager and move back the whole "overlay" folder from /system/__Backup/various/vendor_overlay to /system/vendor and reboot
Click to expand...
Click to collapse
RESULT
As said at the top, you'll get a very slimmed down KK FW, battery friendly, very fast, with less RAM comsuption etc
Of course, everything is working great here, I mean all the features I need/use!
In particular, with latest version of my script you are going to delete more than 170 packages in total (unfortunately not also all the libs like it happen in LP because of how are placed apps in system in KK) plus all applications automatically installed by Sony :good:
DISCLAIMER
If you apply my script again please take care I did a pretty massive debloat as I don't use a lot of stuff (social apps, small apps, many of the sony "addons"/special settings etc!!) and this is a working config for me, but for others some functionalities will be probably missing, so mind what you do before apply them! (but again you can restore anything anytime, if interested just continue the reading)
Click to expand...
Click to collapse
###########################################################################################################
REMOVED STUFF
As said at the beginning, with my script, stuff is not going to be deleted anymore, but moved in /system/__Backup folder. This way you can restore things without the need to download them from my GDrive.
At the following link you will find the full list of all stuff I moved away in my customized FW (and what you are going to move away if you flash my debloating script):
https://docs.google.com/spreadsheets/d/1Gof3mcFSWxP4cONuoLXPQkGE6Xnfn9tsg899rLN3ALY/edit#gid=0
PS. the file is with read-only access for everyone, if you have any changes to suggest, please reply in the thread or send me a PM with the changes you propose
Sorry, the link was not public, now you should be able to correctly see the list!
HOW TO RESTORE SOMETHING
PS. of course I also removed from my FW all the stuff that can be easily downloaded from the Play Store (Gmail, etc)
In the hidden field below you will find the restoring instructions you need to follow to restore any package you may want back:
According to what you want to restore, you have to follow two different procedures:
- all the APKs that are inside /system/__Backup/various/etc_custom_apps and /system/__Backup/various/etc_prod_apps are regular APKs that are going to be installed in /data, so you can just run them and then select "install" like a normal APK, easy. You will then see them in Settings > applications > downloaded
- instead, all the things in /system/__Backup/system_app and /system/__Backup/system_priv-app folders can't be normally installed, but must be restored in the correct /system folders with correct permissions. To do this, see the step-by-step instructions below (in the following example, I am going to restore Chrome app in /system/app and Velvet (Google Search) in /system/priv-app, but of course you can restore how many things as you want at the same time)
Code:
- with a root file manager like ES, go to /system/__Backup/system_app and MOVE both "Chrome.apk" and "Chrome.odex" files to /system/app
- with a root file manager like ES, go to /system/__Backup/system_priv-app and MOVE both "Velvet.apk" and "Velvet.odex" files to /system/priv-app
- reboot
- done
PS. don't copy but MOVE things back, or permissions will get messed up and you are likely to end up in a bootloop!
Many THANKS @ondrejvaroscak and @Puffin617 for some very good advices, @mj084 for some packages descriptions :good:

I
moly82 said:
***LOOKING FOR A ALL-IN-ONE SOLUTION? THAT'S AVAILABLE FOR Z3C USERS ONLY, IF INTERESTED GO HERE***
I guys, similarly to what I did for LP, and considering that even in the LP time some people asked me about debloating KK (and I'm using it right now and actually seems i like it more than LP too) I share with you my debloating script for those interested in a higly DEBLOATED KK installation, very slimmed down, battery friendly, faster, with less RAM comsuption etc
Heavily debloated actually means almost 900 mb of system stuff moved to a backup folder (that you can even delete or move to sdcards to get 900mb extra free space in /system) so applying my script you agree to debloat A LOT as I did but take care that you will have a much lighter system and still you will be able to restore very easily anything you want anytime moving stuff back from the backup folder to /system (detailed instructions for that below in this thread).
Procedure for all xperia phones running KK:
Requirements:
- working recovery
- be on KK 4.4.4 already
Installation:
1. full nandroid backup to eventually go back to previous any time
2. wipe data, cache and dalvik ***
3. flash my Debloating Script for KK
4. that's all! reboot/enjoy
RESULT
As said at the top, you'll get a very slimmed down KK FW, battery friendly, very fast, with less RAM comsuption etc
Of course, everything is working great here, I mean all the features I need/use!
In particular, with latest version of my script you are going to delete more than 170 packages in total (unfortunately not also all the libs like it happen in LP because of how are placed apps in system in KK) plus all applications automatically installed by Sony :good:
DISCLAIMER
###########################################################################################################
REMOVED STUFF
As said at the beginning, with my script, stuff is not going to be deleted anymore, but moved in /system/__Backup folder. This way you can restore things without the need to download them from my GDrive.
At the following link you will find the full list of all stuff I moved away in my customized FW (and what you are going to move away if you flash my debloating script):
Coming...
In the meantime here is a raw list of what I removed:
/etc/customization/applications > all
/etc/product/applications > all
/etc/product/content > all
/vendor/app > all
/vendor/overlay > all
/system/app
AnonymousData.apk
AnonymousData.odex
AntHalService.apk
AntHalService.odex
BasicDreams.apk
BasicDreams.odex
Books.apk
Books.odex
BrowserProviderProxy.apk
BrowserProviderProxy.odex
CallWidgetFrameworkPermission.apk
CallWidgetFrameworkPermission.odex
Chrome.apk
Chrome.odex
ClockWidgets.apk
ClockWidgets.odex
CrashMonitorSystem.apk
CrashMonitorSystem.odex
DeviceConfigTool.apk
DeviceConfigTool.odex
Drive.apk
Drive.odex
DrmDialogs.apk
DrmDialogs.odex
DrmUI.apk
DrmUI.odex
DualShockManager.apk
DualShockManager.odex
EnchantedForest.apk
EnchantedForest.odex
ExternalKeyboardJP.apk
ExternalKeyboardJP.odex
FaceLock.apk
FaceLock.odex
Galaxy4.apk
Galaxy4.odex
GenieWidget.apk
GenieWidget.odex
Gmail2.apk
Gmail2.odex
GoogleLyricsPlugin.apk
GoogleLyricsPlugin.odex
HTMLViewer.apk
HTMLViewer.odex
Hangouts.apk
Hangouts.odex
HoloSpiralWallpaper.apk
HoloSpiralWallpaper.odex
IddAgent.apk
IddAgent.odex
Iengine.apk
Iengine.odex
ImageEnhancer.apk
ImageEnhancer.odex
IntelligenceBacklight.apk
IntelligenceBacklight.odex
IntelligenceSettings.apk
IntelligenceSettings.odex
IntelligentRotation.apk
IntelligentRotation.odex
LiveWallpapers.apk
LiveWallpapers.odex
LocationBasedWifi.apk
LocationBasedWifi.odex
Magazines.apk
Magazines.odex
MagicSmokeWallpapers.apk
MagicSmokeWallpapers.odex
Maps.apk
Maps.odex
Music2.apk
Music2.odex
NoiseField.apk
NoiseField.odex
OmaDownload.apk
OmaDownload.odex
OmaV1AgentDownloadServices.apk
OmaV1AgentDownloadServices.odex
PartnerBookmarksProvider.apk
PartnerBookmarksProvider.odex
PhaseBeam.apk
PhaseBeam.odex
PhotoSlideshow.apk
PhotoSlideshow.odex
PhotoTable.apk
PhotoTable.odex
PhotoWidget.apk
PhotoWidget.odex
PlusOne.apk
PlusOne.odex
PrintSpooler.apk
PrintSpooler.odex
RemoteControlService.apk
RemoteControlService.odex
RemoteFileAccess.apk
RemoteFileAccess.odex
RemoteStorageService.apk
RemoteStorageService.odex
SelfPortrait-Aries.apk
SelfPortrait-Aries.odex
SemcAutoPowerOff.apk
SemcAutoPowerOff.odex
SemcCrashMonitor.apk
SemcCrashMonitor.odex
SemcMetadataCleanup.apk
SemcMetadataCleanup.odex
SemcSimDetection.apk
SemcSimDetection.odex
SemcTvLauncher.apk
SemcTvLauncher.odex
SemcWarrantyTime.apk
SemcWarrantyTime.odex
SimContacts.apk
SimContacts.odex
SmallApp-Calculator.apk
SmallApp-Calculator.odex
SmallApp-Timer.apk
SmallApp-Timer.odex
SmallAppManagerService.apk
SmallAppManagerService.odex
SmallAppWidget.apk
SmallAppWidget.odex
SmallAppsFramework.apk
SmallAppsFramework.odex
SmallAppsLauncher.apk
SmallAppsLauncher.odex
SomcCameraWidget.apk
SomcCameraWidget.odex
SomcDlna.apk
SomcDlna.odex
SomcLifeLog.apk
SomcLifeLog.odex
SomcMovieCreatorRmm.apk
SomcMovieCreatorRmm.odex
SomcPOBox.apk
SomcPOBox.odex
SomcSketch.apk
SomcSketch.odex
SonyEntrance.apk
SonyEntrance.odex
SonySelect-ed.apk
SonySelect-ed.odex
StartupFlagV2.apk
StartupFlagV2.odex
Stk.apk
Stk.odex
Street.apk
Street.odex
SyncHub.apk
SyncHub.odex
Tasks.apk
Tasks.odex
Theme001.apk
Theme001.odex
Theme002.apk
Theme002.odex
Theme003.apk
Theme003.odex
Theme004.apk
Theme004.odex
Theme005.apk
Theme005.odex
Theme006.apk
Theme006.odex
TopContactsWidget.apk
TopContactsWidget.odex
TouchBlock.apk
TouchBlock.odex
TouchFilterPackageSwitchService.apk
TouchFilterPackageSwitchService.odex
UnsupportedHeadsetNotifier.apk
UnsupportedHeadsetNotifier.odex
UserDataLogging.apk
UserDataLogging.odex
VMwareReady.apk
VMwareReady.odex
Videos.apk
Videos.odex
VisualizationWallpapers.apk
VisualizationWallpapers.odex
WeatherWidget.apk
WeatherWidget.odex
WikipediaPlugin.apk
WikipediaPlugin.odex
WirelessControllerManagerService.apk
WirelessControllerManagerService.odex
WorldClockWidget.apk
WorldClockWidget.odex
YouTube.apk
YouTube.odex
YouTubeKaraokePlugin.apk
YouTubeKaraokePlugin.odex
YouTubePlugin.apk
YouTubePlugin.odex
com.sonyericsson.xhs.apk
com.sonyericsson.xhs.odex
com.sonymobile.xperialounge.services.apk
com.sonymobile.xperialounge.services.odex
cover-widget.apk
cover-widget.odex
device-monitor.apk
device-monitor.odex
gmail-reader-service.apk
gmail-reader-service.odex
ims.apk
ims.odex
phone-usage.apk
phone-usage.odex
sneiaccountmanager.apk
sneiaccountmanager.odex
talkback.apk
talkback.odex
textinput-chn.apk
textinput-chn.odex
white-balance.apk
white-balance.odex
/sytem/priv-app
BackupRestoreConfirmation.apk
BackupRestoreConfirmation.odex
CoverApp.apk
CoverApp.odex
DefaultCapabilities.apk
DefaultCapabilities.odex
EnterpriseService.apk
EnterpriseService.odex
Exchange2.apk
Exchange2.odex
FBCalendarSync.apk
FBCalendarSync.odex
FBMusicLike.apk
FBMusicLike.odex
GoogleBackupTransport.apk
GoogleBackupTransport.odex
GoogleFeedback.apk
GoogleFeedback.odex
GoogleKeep.apk
GoogleKeep.odex
InputDevices.apk
InputDevices.odex
IntelligentGesture.apk
IntelligentGesture.odex
MyXperia.apk
MyXperia.odex
OMAClientProvisioning.apk
OMAClientProvisioning.odex
OnlineRemoteCamera.apk
OnlineRemoteCamera.odex
PicoTts.apk
PicoTts.odex
SEMCFacebookProxy.apk
SEMCFacebookProxy.odex
SOMCTwitterAccount.apk
SOMCTwitterAccount.odex
SemcEmail.apk
SemcEmail.odex
SemcMusic.apk
SemcMusic.odex
SemcStorageChecker.apk
SemcStorageChecker.odex
SemcTvOut.apk
SemcTvOut.odex
SemcVideo.apk
SemcVideo.odex
ShareApplication.apk
ShareApplication.odex
SharedStorageBackup.apk
SharedStorageBackup.odex
Shell.apk
Shell.odex
SimlockUnlockApp.apk
SimlockUnlockApp.odex
SimpleHome.apk
SimpleHome.odex
SmartcardService.apk
SmartcardService.odex
SnpVUStore.apk
SnpVUStore.odex
SocialEngineCore.apk
SocialEngineCore.odex
SocialEngineFacebookPlugin.apk
SocialEngineFacebookPlugin.odex
SocialEngineFacebookShareFrwkPlugin.apk
SocialEngineFacebookShareFrwkPlugin.odex
SocialEnginePicasaPlugin.apk
SocialEnginePicasaPlugin.odex
SocialEngineTwitterShareFrwkPlugin.apk
SocialEngineTwitterShareFrwkPlugin.odex
SomcHotspot2Settings.apk
SomcHotspot2Settings.odex
SomcMirrorLinkManualSwitch.apk
SomcMirrorLinkManualSwitch.odex
SomcMirrorLinkServer.apk
SomcMirrorLinkServer.odex
SomcMirrorLinkSystem.apk
SomcMirrorLinkSystem.odex
SomcPhotoAnalyzer.apk
SomcPhotoAnalyzer.odex
SomcPlayAnywhere.apk
SomcPlayAnywhere.odex
SomcPodcast.apk
SomcPodcast.odex
SomcSeamlessTethering.apk
SomcSeamlessTethering.odex
SomcWifiDisplay.apk
SomcWifiDisplay.odex
SoundPhotoCamera.apk
SoundPhotoCamera.odex
Tag.apk
Tag.odex
TimeShiftCamera.apk
TimeShiftCamera.odex
UpdateCenter.apk
UpdateCenter.odex
Velvet.apk
Velvet.odex
VpnDialogs.apk
VpnDialogs.odex
ar-effect.apk
ar-effect.odex
bgdefocus.apk
bgdefocus.odex
com.bambuser.sociallive.apk
com.bambuser.sociallive.odex
enhancedusbux.apk
enhancedusbux.odex
filecommander.apk
filecommander.odex
helpapp.apk
helpapp.odex
infoeye.apk
infoeye.odex
livewaremanager.apk
livewaremanager.odex
retaildemo.apk
retaildemo.odex
usb-mtp-backup-transport.apk
usb-mtp-backup-transport.odex
usb-mtp-factoryreset-wrapper.apk
usb-mtp-factoryreset-wrapper.odex
usb-mtp-marlin-wrapper.apk
usb-mtp-marlin-wrapper.odex
usb-mtp-update-wrapper.apk
usb-mtp-update-wrapper.odex
usb-mtp-vendor-extension-service.apk
usb-mtp-vendor-extension-service.odex
HOW TO RESTORE SOMETHING
PS. of course I also removed from my FW all the stuff that can be easily downloaded from the Play Store (Gmail, etc)
In the hidden field below you will find the restoring instructions you need to follow to restore any package you may want back:
According to what you want to restore, you have to follow two different procedures:
- all the APKs that are inside /system/__Backup/various/etc_custom_apps and /system/__Backup/various/etc_prod_apps are regular APKs that are going to be installed in /data, so you can just run them and then select "install" like a normal APK, easy. You will then see them in Settings > applications > downloaded
- instead, all the things in /system/__Backup/system_app and /system/__Backup/system_priv-app folders can't be normally installed, but must be restored in the correct /system folders with correct permissions. To do this, see the step-by-step instructions below (in the following example, I am going to restore Chrome app in /system/app and Velvet (Google Search) in /system/priv-app, but of course you can restore how many things as you want at the same time)
Code:
- with a root file manager like ES, go to /system/__Backup/system_app and MOVE both "Chrome.apk" and "Chrome.odex" files to /system/app
- with a root file manager like ES, go to /system/__Backup/system_priv-app and MOVE both "Velvet.apk" and "Velvet.odex" files to /system/priv-app
- reboot
- done
PS. don't copy but MOVE things back, or permissions will get messed up and you are likely to end up in a bootloop!
Many THANKS @ondrejvaroscak and @Puffin617 for some very good advices, @mj084 for some packages descriptions :good:
Click to expand...
Click to collapse
And what if I am on lollipop? How do I get this package installed? Do you have an all-in-one with the firmware together?

So if I would remove all this, and need to do a factory reset. Will it still be possible or would it crash totally?
Skickat från min C6903 via Tapatalk

alwaysbelieve1 said:
I
And what if I am on lollipop? How do I get this package installed? Do you have an all-in-one with the firmware together?
Click to expand...
Click to collapse
mate look beginning of OP, red part, there is a link to a semi-all-in-one solution there, very similar to the one i made for LP
not completely all-in-one for now as you will need to flash multiple files for now, but it's very easy, and btw next week I'll upload a real all-in-one KK solution too (need fast connection to upload it )
btw if you follow all instructions in the linked thread, you'll already end up with a working debloated and modded install very similar to the one i made for LP, but this time KK based
Kfdjrk said:
So if I would remove all this, and need to do a factory reset. Will it still be possible or would it crash totally?
Skickat från min C6903 via Tapatalk
Click to expand...
Click to collapse
not sure to understand correctly your question.. you mean what will happen if you flash the debloating script now, and later you will need to do a factory reset?
if so, it won't be a problem at all, as my script affect mostly system partition, while factory resetting you are likely to touch only data and cache partitions.. so after factory resetting you'll still have system partition untouched and still debloated, unless you'll wipe system too and reflash another full FW

moly82 said:
mate look beginning of OP, red part, there is a link to a semi-all-in-one solution there, very similar to the one i made for LP
not completely all-in-one for now as you will need to flash multiple files for now, but it's very easy, and btw next week I'll upload a real all-in-one KK solution too (need fast connection to upload it )
btw if you follow all instructions in the linked thread, you'll already end up with a working debloated and modded install very similar to the one i made for LP, but this time KK based
not sure to understand correctly your question.. you mean what will happen if you flash the debloating script now, and later you will need to do a factory reset?
if so, it won't be a problem at all, as my script affect mostly system partition, while factory resetting you are likely to touch only data and cache partitions.. so after factory resetting you'll still have system partition untouched and still debloated, unless you'll wipe system too and reflash another full FW
Click to expand...
Click to collapse
I'll probably wait till next week unless I get really bored and decide to pull the plug. Is it going to be quite noticeable of a difference compared to lollipop? Mainly I'm looking for battery life.

alwaysbelieve1 said:
I'll probably wait till next week unless I get really bored and decide to pull the plug. Is it going to be quite noticeable of a difference compared to lollipop? Mainly I'm looking for battery life.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62680704
my battery stats

@moly82 can u please tell me how to reenabke NFC?I tryied to send something with undroid beam without luck!
forget it dude all OK!

dead link
The Dropbox link is dead

dunno why links are dead..stuff is still there in my DB! here it is btw

FcukBloat said:
dunno why links are dead..stuff is still there in my DB! here it is btw
Click to expand...
Click to collapse
this also removes the drm based optimizations...

yes those fake things...

DirtyCow based Universal Debloater [Root not required]

This tool uses Dirty COW (CVE-2016-5195) vulnerability in the Linux kernel to escalate privilege and disable/enable system packages.
It should work on all Android versions which exposed to this vulnerability.
To use this Universal Debloater is very easy.
Start Universal Debloater by double click on { Debloater.bat } file and follow the informations on the screen - it's easy. All menu letters are case Insensitive and you can type how you want [B or b, etc.], and the numbers... are just numbers
Usage:
- DISABLE PACKAGES
This option makes disable script from the selected list of packages and run it for disable packages on device.
Note: Packages list should consist of the names of packages, each on a separate line and must be placed in "/package lists" directory.
You can get packages list by selecting the appropriate option in the menu.
Note: Do not forget to uncomment package names which you want to disnable, by deleting "#" symbol before name in the beginning of the line (do not touch the second).
- ENABLE PACKAGES
This option makes enable script from the selected list of packages and run it for enable packages on device.
Note: Packages list should consist of the names of packages, each on a separate line and must be placed in "/package lists/disabled/" directory.
You can get disabled packages list by selecting the appropriate option in the menu.
Note: Do not forget to uncomment package names which you want to enable, by deleting "#" symbol before name in the beginning of the line (do not touch the second).
- READ PACKAGES
This option makes packages list by reading from device and comparing with database.
If you select to "get all packages list", you will get list of all system packages from your device. You can find it in "/package lists" directory.
If you select to "get disabled packages list", you will get list of only disabled system packages from your device. You can find it in "/package lists/disabled/" directory.
In the list you can see description of known packages and location of apk files associated with unknown packages to make a decision about enabling/disabling this package. Before using this list to enable/disable packages do not forget to uncomment package names which you want to enable/disable, by deleting "#" symbol before name in the beginning of the line (do not touch the second).
Download:
Universal_Debloater_by_D1kiy_v1.0b
Credits:
* man'[email protected] for advice;
* [email protected] for some help with script;
* [email protected] for his Image Kitchen from which I took design;
* [email protected] for his Debloat Script which gave me idea;
* Tony Monroe for cowsay program;
* Dennis Bareis for the CTEXT DOS coloring tool;
* Phil Oester for his discovery CVE-2016-5195;
Click to expand...
Click to collapse
Please respect my work and if you use it don't forget to hit the THANKS button in my thread. And if you take it and share it on other sites, or integrate it in other tools, give proper credits for my work.
XDA:DevDB Information
Universal Debloater, Tool/Utility for all devices (see above for details)
Contributors
D1kiy
Version Information
Status: Beta
Current Beta Version: 1.0b
Beta Release Date: 2017-01-21
Created 2017-01-21
Last Updated 2017-01-21

Reserved

This only disables the packages right? Can it uninstall them? If not, it's cool, just wondering, because there is quite a few of them on my phone that need to be eliminated. Great work either way!

hydroman202 said:
This only disables the packages right? Can it uninstall them? If not, it's cool, just wondering, because there is quite a few of them on my phone that need to be eliminated. Great work either way!
Click to expand...
Click to collapse
Yes, this tool only disables packages. Unfortunately you can not uninstall them without normal root.

D1kiy said:
Yes, this tool only disables packages. Unfortunately you can not uninstall them without normal root.
Click to expand...
Click to collapse
How do i enter root shell?
---------- Post added at 06:08 PM ---------- Previous post was at 05:58 PM ----------
I figured it out, but all I get is setresgid/setresid failed.

hydroman202 said:
How do i enter root shell?
---------- Post added at 06:08 PM ---------- Previous post was at 05:58 PM ----------
I figured it out, but all I get is setresgid/setresid failed.
Click to expand...
Click to collapse
On which android version? And after what you get this error?

D1kiy said:
On which android version? And after what you get this error?
Click to expand...
Click to collapse
It is marshmallow 6.0.1. It happens when attempting to elevate to root. I will upload a screen shot here in a minute.

Here is a screenshot:

Also, if it helps, I have only the setsid in the system bin directory.

hydroman202 said:
It is marshmallow 6.0.1. It happens when attempting to elevate to root. I will upload a screen shot here in a minute.
Click to expand...
Click to collapse
/system/bin/run-as does not have the setuid bit set on your device.
I will look for possibility to fix this.

D1kiy said:
/system/bin/run-as does not have the setuid bit set on your device.
I will look for possibility to fix this.
Click to expand...
Click to collapse
Thank you

Hello. I have tried this on Note 4 N910C
and I get error: Package 'con' is unknown
I have attached screens with the log and my android version as well.
Thank you for the tool anyway!

Run as error
it says Run as: Package exec is unknown