Database Info

Koushik (Koush) Recovery Builder tool for all!

Koushik Dutta, creator of ROM Manager, ClockworkMod Recovery today posted on Google+ his new automated Recovery Builder.
All you need is a stock recovery image and press build to port ClockworkMod Recovery to virtually any device.
Builder Link: http://builder.clockworkmod.com/
google+ Link: https://plus.google.com/u/0/103583939320326217147/posts

Ooooooh
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Check the links... pretty interesting though.

I wonder if we can fix the "new recovery" with this. I'm too lazy to try it..
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

someone do it

BaconStep said:
someone do it
Click to expand...
Click to collapse
yeah some one do it! please...

Normal cwm works fine on sgs3 !!!
Thx!!!
EDIT: ops wrong thread, but very nice tool

Where would I be able to find a recovery image?

Pull it from a stock recovery tarball.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

unsupported page size = 16384
I have a rooted PROSCAN plt7035-pl tablet that i've extracted a recovery.img from and uploaded to the recovery builder. The build failed with unsupported page size = 16384. Is there something I can do to fix the pagesize and make it complete the build?
recovery builder console output(shortened):
----- Making recovery filesystem ------
----- Making recovery filesystem ------
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/etc
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/tmp
Copying baseline ramdisk...
Copying baseline ramdisk...
cp -R /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/root /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery
rm /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/init*.rc
Modifying ramdisk contents...
Modifying ramdisk contents...
cp -f bootable/recovery/etc/init.rc /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/init.rc
cp -f /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/obj/EXECUTABLES/recovery_intermediates/recovery /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/sbin/
rm -f /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/init.*.rc
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/system/bin
cp -rf bootable/recovery/res /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/
cp -f device/unknown/rk29sdk/recovery.fstab /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/etc/recovery.fstab
cp /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/obj/PACKAGING/ota_keys_intermediates/keys /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/res/keys
cat /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/root/default.prop /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/system/build.prop \
> /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/default.prop
> /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/default.prop
Modifying default.prop
Modifying default.prop
sed -i 's/ro.build.date.utc=.*/ro.build.date.utc=0/g' /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/default.prop
----- Made recovery filesystem --------/Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root
----- Made recovery filesystem --------/Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root
----- Making uncompressed recovery ramdisk ------
----- Making uncompressed recovery ramdisk ------
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/mkbootfs /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/mkbootfs /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio
----- Making recovery ramdisk ------
----- Making recovery ramdisk ------
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/minigzip < /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.img
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/minigzip < /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.img
----- Making recovery image ------
----- Making recovery image ------
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/mkbootimg --kernel /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/kernel --ramdisk /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.img --base 0x60400000 --pagesize 16384 --output /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery.img
error: unsupported page size 16384
make: *** [/Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery.img] Error 255
build error!
Build failed.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE
Help us localize this page
Page generated: Dec 29, 2012 7:06:51 PMREST APIJenkins ver. 1.489
Click to expand...
Click to collapse

T.L.Hingan said:
I have a rooted PROSCAN plt7035-pl tablet that i've extracted a recovery.img from and uploaded to the recovery builder. The build failed with unsupported page size = 16384. Is there something I can do to fix the pagesize and make it complete the build?
recovery builder console output(shortened):
Click to expand...
Click to collapse
Glad you could extract the recovery image because I failed when I tried it with the PLT-7035B.:crying:

does look interesting, and I see the potential, but not for our device. Especially when u can just Odin twrp.

mindmajick said:
I wonder if we can fix the "new recovery" with this. I'm too lazy to try it..
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Click to expand...
Click to collapse
what new recovery are you talking about? > the leak?
and whats the problem with the new recovery? >

vincom said:
what new recovery are you talking about? > the leak?
and whats the problem with the new recovery? >
Click to expand...
Click to collapse
You quoted an 8 month old post
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
You quoted an 8 month old post
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
lol, seen the date for last few posts, didnt notice majics post date

stupid xda app..stupid page 2...

vincom said:
lol, seen the date for last few posts, didnt notice majics post date
Click to expand...
Click to collapse
icenight89 said:
stupid xda app..stupid page 2...
Click to expand...
Click to collapse
Hahaha, pwned
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

how to use output files of koushik recovery builder
Hello!
Tried using Koushik Recovery Builder but how to use the output files?
I got the following files:
android_device_samsung_espressowifi.zip
inputrecovery.img
recovery.img
manifest.xml
Thanks in advance!

its says
Syncing...
Build was aborted
Aborted by Koushik Dutta
Archiving artifacts
Finished: ABORTED
why was it aborted? im using a a111.

[TOOL] DEXO – universal odex tool | HOW-TO move lib to /system/lib without reflash

DISCLAIMER: I am not the author of this tool!
All credits goes to tommytomatoe and you can press thanks in this thread because there is no dedicated thread for DEXO @xda (at least I found none)​
theking_13 said:
thiagomme said:
Why does it give better battery life? Thank you.
Click to expand...
Click to collapse
Because it splits the .apk (app package) into two parts, the .apk and a .odex file. Usually, for the phone to use an app, it has to decompile the .apk and get the parts it needs to run the app. With the odex files, which stands for "Optimized Dex" the startup time is much faster since the phone doesn't have to perform any optimizing at startup/runtime, and because of that, it also uses less CPU power, and thus makes it faster, smoother, and battery life is increased.
Click to expand...
Click to collapse
OK. So what is this tool?
This tool doesn’t deal with partially odexed ROMs. This tool is for odexing a ROM that is completely DEODEX.
The benefits? Faster boot, smaller imprint on /data/ partition, overall faster feeling
The myths? I can’t theme ODEX! WRONG! You can theme odex just fine! Just use baksmali and smali.
Click to expand...
Click to collapse
Requirements:Of the author:
adb
Linux, Mac OS X, Windows
Android device with busybox
Four minutes of your day
Added by me:
You have finally settled on a ROM that you want to use for some time without an intention to modify it further
You will need about 100 MB free space on system (my free space decreased from 160 MB to 96 MB after the completion of the process) To free some you can delete some apps from /system/app or move them to /data/app with a root file explorer (do not forget to set the correct permissions afterwards) or even better: to move your /system/lib folder to the lib partition without reflashing the ROM (see below for details)
Tested on Fallout 5.0 and Virtuous Infinity 1.35 with my Tweaked3 8.6 kernel. If you are using this it is at your own will and risk
NOT WORKING on CoolDroid and Sabsa Prime 6.5, probably because they have mixed framework from different Sense versions! Do not do on other similar ROMs only on ones with an original (even modded) framework!
Procedure:Go here and read carefully. It is basically some adb commands.
Out of respect to the author I will not mirror his link nor the instructions​----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------How to free about 120 MB space on /system by moving the lib folder to its dedicated partition without reflashing the ROM
This is only for ICS Sense ROMs. AOSP ROMs have enough free space to run the script without issues. I am not sure about the GB Sense ROMs, but if I remember correct they have enough free space on /system too. (if I am wrong please PM me to add GB Sense boot.img)
Requirements:
Bootloader with /system/lib support: 2.xx or 7.xx
150 MB free space on your SDcard
adb drivers installed (link in my signature)
4EXT Recovery (or any other recovery that has a menu entry for mounting /system/lib partition)
good attention while copy/paste the commands from here. One typo will lead to a bootloop
Download Tweaked3: XI_lib_bootimg.zip
md5sum: 1bc1d645b8212cdb2e4e949c6b7b3312
Download Patched: 3089_lib_bootimg.zip
md5sum: f1ae0228eb4057b4e4c4934a1e8a0515​The zips contain boot images of my Tweaked3 and Patched kernels with /system/lib support (I am not advertising them but this are the files I have ready, you can use a Stock kernel as well). There are 4 of them:
Sense4_lib_boot.img - for ALL Sense 4 ROMs (except VIrtuous Infinity)
Sense36_exp_lib_boot.img - for custom Sense 3.6 ROMs with experimental WiFi driver (Experimental kernel)
Sense36_lib_boot.img - for custom Sense 3.6 ROMs with stock WiFi driver (Stable kernel)
Virtuous_lib_boot.img - the name speaks for itself
Extract the archive in the folder where your fastboot executable is. This is not a flashable zip!​orDownload 2: b2b_lib_bootimg.zip
md5sum: 4bb4d44506eae5f247b69f9c5663e3a8​The zip contains boot images of my B2B kernel with /system/lib support (I am not advertising it but this are the files I have ready, you can use a Stock kernel as well). There are 2 of them:
Sense4_lib_boot.img - for ALL Sense 4 ROMs (except VIrtuous Infinity)
Sense36_lib_boot.img - for custom Sense 3.6 ROMs
Extract the archive in the folder where your fastboot executable is. This is not a flashable zip!​NOTE: your ROM has to be on the same version of the kernel before the procedure, otherwise your WiFi will stop working. Or you will need to download the zip from the kernel thread and copy the modules to /system/lib/modules manually giving them right permissions (644 or -rw-r--r--)​Procedure:# Connect the device to PC, open Command Prompt (cmd) and browse to the folder where are your adb and fastboot executables are (example: cd C:\android-tools)
# Reboot to Recovery (4EXT recommended)
Code:
adb reboot recovery
# Make a Nandroid backup
# Mount manually /system and /sdcard from the "mounts | storage" menu of the Recovery
# Copy the content of /system/lib to the SDcard
Code:
adb shell
mkdir /sdcard/system
cp -r /system/lib /sdcard/system
# Clean /system/lib
Code:
rm -r /system/lib
# Recreate empty /system/lib and set permissions
Code:
mkdir /system/lib
chmod 755 /system/lib
# Unmount manually /system from the "mounts | storage" menu of the Recovery
# Mount manually /system_lib from the "mounts | storage" menu of the Recovery
# Copy the lib contents to /system/lib
Code:
cp -r /sdcard/system/lib/* /system_lib
# Set permissions to /system/lib
Code:
cd /system_lib
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
[I]# Creating symlinks [COLOR=Red]Only for Virtuous Infinity![/COLOR][/I]
ln -s libhtc_ril.so librilswitch.so
cd hw
ln -s copybit.msm8660.so copybit.msm7x30.so
ln -s gralloc.msm8660.so gralloc.msm7x30.so
ln -s lights.msm8660.so lights.msm7x30.so
# Remove the SDcard /system/lib folder
Code:
rm -r /sdcard/system
exit
# Unmount manually /system_lib and /sdcard from the "mounts | storage" menu of the Recovery
# Reboot to bootloader
Code:
adb reboot bootloader
# Flash the boot.img and reboot
Code:
fastboot erase boot
fastboot flash boot XXX_lib_boot.img
fastboot reboot
Now you can use the tool above without concerns about free space
Enjoy!

amidabuddha, thanks for sharing. Have you tried this?

old.splatterhand said:
amidabuddha, thanks for sharing. Have you tried this?
Click to expand...
Click to collapse
Yes of course. Read the Requirements part
Sent from my HTC Desire S

Ok, i need help, cause i don't do this things often:
Fifth step, run it!
Click to expand...
Click to collapse
What and how?

old.splatterhand said:
Ok, i need help, cause i don't do this things often:
What and how?
Click to expand...
Click to collapse
Read further in the instructions, Theres a complete usage example with all the commands
Sent from my Desire S using xda app-developers app

Gonna try it today on CM10.
Tapatalked from Desire S running Andromadus

teadrinker said:
Read further in the instructions, Theres a complete usage example with all the commands
Click to expand...
Click to collapse
Sorry, my fault! I thought this come after the 5 steps.

if a rom is zipaligned, doesn't this mean that there's no need being odexed - kind of same thing? (same performance, battery life...)
i've read that, but i'm no expert...

toxic-hero said:
if a rom is zipaligned, doesn't this mean that there's no need being odexed - kind of same thing? (same performance, battery life...)
Click to expand...
Click to collapse
Zipaligning is about better RAM utilization. Odexing is about reducing the Dalvik VM which in theory should reduce CPU use and make the system run smoothly. You can watch the video, it is made by one of the Elite Recognized Developers of XDA so this guy probably knows what he is talking about. Moreover ALL Stock ROMs are odexed and I am sure that the companies developers are not just too lame to use it for nothing

tried the above...pasted something wrong and now phone stuck on htc screen and can't get into recovery

mackhenri said:
tried the above...pasted something wrong and now phone stuck on htc screen and can't get into recovery
Click to expand...
Click to collapse
Have you provided enough free space on your system partition? Try with a factory reset.
And once again:
If you are using this it is at your own will and risk
Click to expand...
Click to collapse

i think it was due to less space but still will try it once again after making space

Was a hard task to get enough space free.
Let's see how it works now.

old.splatterhand said:
Was a hard task to get enough space free.
Let's see how it works now.
Click to expand...
Click to collapse
Yes this may be an issue with the bigger ROMs. The easiest way is to move some app that you use rarely to /data/apps
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Sent from my HTC Desire S

amidabuddha said:
Yes this may be an issue with the bigger ROMs. The easiest way is to move some app that you use rarely to /data/apps
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Sent from my HTC Desire S
Click to expand...
Click to collapse
Get it on buddy.....I am ready to try whatever u make as you seem to give life to my phone once again and all the devs here and I am become a flashaholic...
Sent from my HTC Desire S using xda premium

amidabuddha said:
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Click to expand...
Click to collapse
This would b great, I did it once for Fallout with one of your kernel ramdisks, but it was not so trivial and a pain in the a** doing this all by hand. Though it worked perfectly, I don't remember every step I did, and mayb I didn't do it the elegant way, as I'm not very experienced.
As far as I remember the complicated part was unpacking kernel+ramdisk, modifing ramdisk, repacking everything and signing it. But this has to be done only once (by one idividual) for every kernel (+ramdisk). The rest ist more or less flashing and copying from /system to /system/lib partition (can be done in recovery easily). The latter mayb realised with one single script installer for every kernel (and rom) I guess. But here I also lack the experince with script installers, elsewise I would have shared the info.
I did it on Windows with bootimg-tools via Cygwin (unpacking, repacking), with SignApk on cmd (signing), in recovery (flashing, copying). For flashing I guess fastboot is more elegant (reflashed whole rom with mod boot.img). For the rest I didn't found something more convinient, but maybe soemone can enlighten me.

HOW-TO move your /system/lib folder to the dedicated partition added to the first post. Tested and verified working. Just copy the commands carefully
Enjoy!

Thx, the new guide worked like a charm for me on Fallout v5.0.0 with your kernel v8.5. I think it is more or less what I did, when it worked for me before. Also the odexing stuff worked well. What I am just wondering about, as this is odexing Rosie, will this affect the Fallout Tweaks for Rosie? And I tended to use Titanium Backup to merge updated system apps (like Facebook) into rom (essentially moving to system I guess), are there any drawbacks doing it with odexed apps?

kwisatz79 said:
Thx, the new guide worked like a charm for me on Fallout v5.0.0 with your kernel v8.5. I think it is more or less what I did, when it worked for me before. Also the odexing stuff worked well. What I am just wondering about, as this is odexing Rosie, will this affect the Fallout Tweaks for Rosie? And I tended to use Titanium Backup to merge updated system apps (like Facebook) into rom (essentially moving to system I guess), are there any drawbacks doing it with odexed apps?
Click to expand...
Click to collapse
All apps will work the same way after odexing. I can confirm all Rosie tweaks in Fallout working.
As per the Titanium stuff I have no idea try it and let us know
Sent from my HTC Desire S

when I am trying to copy /sdcard/system/lib to /system_lib it is showing not enough space....
Also in 4extrecovery - two system_lib are showing...
Any ideas?
BTW I am on Fallout 5.0...

[MOD] [SCRIPT] Superwipe Script & Kernel Cleaner Script

{
"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"
}
MOD NOTE: Be advised the superwipe script WILL wipe your internal storage. It's designed that way to wipe all the useless clutter that accumulates. If you don't know what you are doing, then don't flash it.
I have decided to post the wipe scripts here for those KernelHolics & Flashaholics that are flashing kernels and ROMs constantly. I've made small modifications to these scripts FULL credit to the originator of them Credits below.
These are compatible with CWM, TWRP.
Since there have been numerous kernels recently being posted and people wondering what to wipe or what not to wiped here is the Kernel Cleaner.
1. Place the file in the root of your /sdcard
2. Flash Kernel Cleaner
3. Flash/Fastboot Kernel
4. Reboot.
Download: http://d-h.st/BWy
This second script I'm sure everyone is familiar with SUPERWIPE script.
Tired of wiping after every ROM or not knowing what to wipe to flash a ROM and have a clean install? Just flash this script & flash ROM easy right?
1. Place Wipe-Script in root of /sdcard
2. Flash Wipe-Script
3. Flash ROM
4. Reboot.
5. This will wipe external storage. (Wiping without storage coming soon)
Download: http://d-h.st/MFS
Debug​
If it doesn't flash please tell me what recovery your using.
ONLY works for the NEXUS 7 NOT NEXUS 7 3G will be available for other devices as well.
Credit goes to the following people.​
Mike1986
AmazingLarry31
Jivy26
I-777
Myself
IF YOU USE/DOWNLOAD THIS SCRIPT PLEASE PRESS THE THANKS BUTTON​

Re: [mod][script] superwipe script & kernel cleaner script
Reserved for other Awesome Scripts to make your life easier.

So this replaces the ramdisk to the original one? No need to flash the stock kernel before changing from a modified ramdisk kernel to another?
Thank you, we surely need more stuff like that to make our lifes easier =)

Re: [MOD][SCRIPT] Superwipe Script & Kernel Cleaner Script
Grakel said:
So this replaces the ramdisk to the original one? No need to flash the stock kernel before changing from a modified ramdisk kernel to another?
Thank you, we surely need more stuff like that to make our lifes easier =)
Click to expand...
Click to collapse
The Kernel Cleaner will remove the kernel, modules, ramdisk, init.d. To nothing! You will have to flash a new kernel to install the modules and ramdisk again.
Sent from my HTC One S using Tapatalk 2

Re: [MOD][SCRIPT] Superwipe Script & Kernel Cleaner Script
Great scripts for Franco kernel users wanting to migrate to a different kernel :thumbup:
Sent from my Nexus 7 using xda app-developers app

Re: [MOD][SCRIPT] Superwipe Script & Kernel Cleaner Script
FitAmp said:
Great scripts for Franco kernel users wanting to migrate to a different kernel :thumbup:
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, something u get more bugs flashing a kernel over another kernel or ROM this solves that problem. Its like getting a clean kernel install

good we have one of these, really gives you a fresh start!

So I guess it's my fault for not backing up on my computer but you should probably mention that this wipes EVERYTHING! I assumed when you said, flash script, flash rom, you didnt mean connect to PC, ADB push rom, flash, reboot, re set up everything....

Re: [MOD][SCRIPT] Superwipe Script & Kernel Cleaner Script
Gil Smash said:
So I guess it's my fault for not backing up on my computer but you should probably mention that this wipes EVERYTHING! I assumed when you said, flash script, flash rom, you didnt mean connect to PC, ADB push rom, flash, reboot, re set up everything....
Click to expand...
Click to collapse
It wipes internal storage? Yikes :s
Sent from my Nexus 7 using xda app-developers app

FitAmp said:
It wipes internal storage? Yikes :s
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yup.... I wish I had backed up to my computer before hand. At least I have a backup from a month or so ago....

Thanks for this, much needed, will be using the kernel cleaning script a lot. I'm gonna wait till the super wipe doesn't wipe the internal storage, I'm using multiboot atm and don't wanna lose my ROMs or feel like backing them up.
Thanks again!

...Awesome... said:
The Kernel Cleaner will remove the kernel, modules, ramdisk, init.d. To nothing! You will have to flash a new kernel to install the modules and ramdisk again.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
good work man!i only suggest you to insert this things in the kernel script(like i already did times ago in mine i use always)
tricksterMOD app saved data\settings
franco app saved data\settings
faux app saved data\settings
thanks to take the time to modify and post these!
EDIT an example for the galaxy nexus that i use,like you can see it erase also kernel control app data.hope it helps!
Code:
#!/sbin/sh
# clean Popcorn stuff
rm -f /system/etc/sysctl.conf
rm -rf /data/cron
# clean LeanKernelTweaks stuff
rm -f /system/xbin/installbb
rm -f /system/xbin/leantweaks
rm -rf /data/leantweaks
# clean Trinity stuff
rm -f /system/bin/fix_permissions
# clean init.d scripts
INITD_DIR=/system/etc/init.d
# GLaDOS
rm -f $INITD_DIR/90logger
rm -f $INITD_DIR/99nexusinit
rm -f $INITD_DIR/placeholder
# Trinity
rm -f $INITD_DIR/95dimmers
rm -f $INITD_DIR/98tweak
rm -f $INITD_DIR/99complete
# SG
rm -f $INITD_DIR/98_startup_script
rm -f $INITD_DIR/99_startup_complete
# Air
rm -f $INITD_DIR/89airtweaks
rm -f $INITD_DIR/98airtweak
rm -f $INITD_DIR/98airtweaks
rm -f $INITD_DIR/99airtweaks
# franco
rm -f $INITD_DIR/13overclock
rm -f $INITD_DIR/00turtle
# Popcorn
rm -f $INITD_DIR/99sonic
# Lean
rm -f $INITD_DIR/99leantweaks
# Jame Bond
rm -f $INITD_DIR/007tweaks
# miscellany
rm -f $INITD_DIR/99nstools
# lean kernel
rm -f $INITD_DIR/99lk-gpu
# Zen
rm -f $INITD_DIR/99ZenKernel
# clean kernel setting app shared_prefs
rm -rf /data/data/mobi.cyann.nstools/shared_prefs
rm -rf /data/data/aperture.ezekeel.gladoscontrol/shared_prefs
rm -rf /data/data/com.derkernel.tkt/shared_prefs
rm -rf /data/data/com.franco.kernel/shared_prefs
rm -rf /data/data/com.liquid.control/shared_prefs
# remove dalvik cache
rm -rf /data/dalvik-cache
rm -rf /cache/dalvik-cache

Re: [MOD][SCRIPT] Superwipe Script & Kernel Cleaner Script
Will do thanks for taking the time and showing me. I will edit it in the next version.
Sent from my HTC One S using Tapatalk 2

np man,i cited only that 3 apps because they were what come in mind in that moment,don't know if n7 users use something else (kernel control app coded by kernel dev or coded with n7 in mind)

mlaws90 said:
Thanks for this, much needed, will be using the kernel cleaning script a lot. I'm gonna wait till the super wipe doesn't wipe the internal storage, I'm using multiboot atm and don't wanna lose my ROMs or feel like backing them up.
Thanks again!
Click to expand...
Click to collapse
Is it possible for you to add this script into your Rom Aroma installation? would be nice as some of us try many different kernels!

Just a question though: will the kernel cleaner script erase all data on my N7?

no!not worry about that.
little tips.also if you don't know anything related,next time have a look inside the zip,in the updater-script
i report HERE if you want to have a look

sert00 said:
no!not worry about that.
little tips.also if you don't know anything related,next time have a look inside the zip,in the updater-script
i report HERE if you want to have a look
Click to expand...
Click to collapse
So I just want to clarify, the kernel cleaner script doesnt delete anything but just everything to do with the kernel that is installed right? It doesnt erase all the data that I have on my tab?

Re: [MOD][SCRIPT] Superwipe Script & Kernel Cleaner Script
Hi, the links are down and I really need both of these scripts. Do you have another link possibly. I would be most appreciative. Thanks in advance.
Sent from my Nexus 7 using xda premium

Android.Ninja said:
Hi, the links are down and I really need both of these scripts. Do you have another link possibly. I would be most appreciative. Thanks in advance.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
links are NOT down... dev-host got server problems ... F5 is your best friend now

[Q] Problem after pushing the deodexed apps and framework

Hello everybody, I am trying to deodex my stock ICS v28 rom.
I deodexed the app and framework folder successfully with the use of dsixda kitchen, signed all apks and copied it to "/sdcard/_ExternalSD/deodexed" folder.
Note: at the time of deodexing I also selected the api level to 15
Now I am pushing to the device using this code:
Code:
adb shell
su
stop
mount -o remount,rw /dev/block/mmcblk0p7 /system
rm /system/framework/*.odex
rm /system/app/*.odex
busybox cp /sdcard/_ExternalSD/deodexed/app/* /system/app/
busybox cp /sdcard/_ExternalSD/deodexed/framework/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/mmcblk0p7 /system
sync
reboot
after the phone boots I get a security error
Remember, I dont get any error while executing any code in adb and after pushing I checked through adb that those deodexed apps have been pushed successfully to app and framework folder.
Can anybody tell me what I am doing wrong, any help apreciated.
NOTE: The help I need is in deodexing and pushing it to the device, I have already restored my /system partition but I am experimenting with this stuff.
Also, I already have wkpark bootloader 1.25 installed

You need kernel with support for deodexed roms.
Sent from my LG-P920 using xda premium

krija said:
You need kernel with support for deodexed roms.
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
Thanks very much, I flashed the kernel of OptimusRS's new rom and it booted (obviously deodexed). I never knew that the stock kernel doesn't support deodexed apps.
Thanks again.
Edit: Can u suggest me any other good kernel that supports deodexed rom? and do u know the method to make the stock kernel support deodexed rom?

You´re welcome
regarding the method, I only know about this:
http://forum.xda-developers.com/showpost.php?p=40595337&postcount=580
I have tried many kernels, but for now I´m on stock kernel from V28 rom with iodak´s OC modules. I think you have nothing to lose if you try them all apart from PH85.

Impossible to get the init.d support in ramdisk

Hello guys!
I am not new in the Android and Nexus world but at this time I need some help.
I am used to root any Nexus phone in this way:
1. Put su, daemonsu, busybox on /system/xbin/ path;
2. Create the init.d folder in /system/etc/ path;
3. Add a script file to start the superuser daemon at the boot;
4. Edit the kernel ramdisk adding the sysinit script to add the init.d support at the boot;
5. Edit the updated-script for the right permissions to the new init.d folder (and its content) and to the su binary file.
I never had problems with Galaxy Nexus and LG Nexus 4 but today I am having troubles with the Nexus 5.
Is this a common issue?
I hope to get answers,
regards,
kalo86

kalo86 said:
Hello guys!
I am not new in the Android and Nexus world but at this time I need some help.
I am used to root any Nexus phone in this way:
1. Put su, daemonsu, busybox on /system/xbin/ path;
2. Create the init.d folder in /system/etc/ path;
3. Add a script file to start the superuser daemon at the boot;
4. Edit the kernel ramdisk adding the sysinit script to add the init.d support at the boot;
5. Edit the updated-script for the right permissions to the new init.d folder (and its content) and to the su binary file.
I never had problems with Galaxy Nexus and LG Nexus 4 but today I am having troubles with the Nexus 5.
Is this a common issue?
I hope to get answers,
regards,
kalo86
Click to expand...
Click to collapse
fastboot oem unlock
flash custom recovery
flash SuperSU in recovery

Of course I have unlocked the bootloder but the init.d script does not work.
Neither a test script works...
This is the test script that I am using to verify if the init.d support is working. The file 00test is placed in /system/etc/init.d/.
Code:
#!/system/bin/sh
#Init.d Test
busybox mount -o remount,rw -t auto /system
if [ -e /system/Test.log ]; then
rm /system/Test.log
fi
echo "kalo86 @ XDA 2014" > /system/Test.log
echo "Init.d is working !!!" >> /system/Test.log

kalo86 said:
Of course I have unlocked the bootloder but the init.d script does not work.
Neither a test script works...
This is the test script that I am using to verify if the init.d support is working. The file 00test is placed in /system/etc/init.d/.
Code:
#!/system/bin/sh
#Init.d Test
busybox mount -o remount,rw -t auto /system
if [ -e /system/Test.log ]; then
rm /system/Test.log
fi
echo "kalo86 @ XDA 2014" > /system/Test.log
echo "Init.d is working !!!" >> /system/Test.log
Click to expand...
Click to collapse
You're making it way too difficult. Just flash supersu in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app

You could install an application such as Universal init.d from the playstore. It works for me on both my Nexus 5 and 10. Initially works without issue.
Sent from my Nexus 10 using XDA Premium HD app

jd1639 said:
You're making it way too difficult. Just flash supersu in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Why difficult? This is the same identical mechanism that Chainfire uses to root your phone but I like to share a rooted-ROM ready to use.
The init.d folder is not supported at the moment. This is the truth.
And I don't want a workaround since the init.d support is very useful also for other stuff which is not only root access.