• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root how safe is this for esteem


all it does is add a init.d script which after looking through his build.prop i would guess it doesnt do a whole lot more than anything we already have. his other script included in the zip just rewrites a new build prop adding these (the underlined part):

| sed '/ro.kernel.android.checkjni/d' \
| sed '/ro.HOME_APP_ADJ/d' \
| sed '/debug.sf.hw/d' \
| sed '/wifi.supplicant_scan_interval/d' \
| sed '/pm.sleep_mode/d' \
| sed '/ro.ril.disable.power.collapse/d' \
| sed '/video.accelerate.hw/d' \
| sed '/debug.performance.tuning/d' \
| sed '/dalvik.vm.verify-bytecode/d' \
| sed '/dalvik.vm.execution-mode/d' \
| sed '/persist.sys.use_dithering/d' \
| sed '/persist.sys.purgeable_assets/d' \
| sed '/dalvik.vm.dexopt-flags/d' \
| sed '/windowsmgr.max_events_per_sec/d' \
| sed '/net.tcp.buffersize.default/d' \
| sed '/net.tcp.buffersize.wifi/d' \
| sed '/net.tcp.buffersize.umts/d' \
| sed '/net.tcp.buffersize.gprs/d' \
| sed '/net.tcp.buffersize.edge/d' \
| sed '/net.tcp.buffersize.hspa/d' \
| sed '/net.tcp.buffersize.lte/d' \

...with the values he put here:

echo "ro.kernel.android.checkjni=0" >> /system/bp.temp
echo "ro.HOME_APP_ADJ=1" >> /system/bp.temp
echo "debug.sf.hw=1" >> /system/bp.temp
echo "wifi.supplicant_scan_interval=180" >> /system/bp.temp
echo "pm.sleep_mode=1" >> /system/bp.temp
echo "ro.ril.disable.power.collapse=0" >> /system/bp.temp
echo "video.accelerate.hw=1" >> /system/bp.temp
echo "debug.performance.tuning=1" >> /system/bp.temp
echo "dalvik.vm.verify-bytecode=false" >> /system/bp.temp
echo "dalvik.vm.execution-mode=int:jit" >> /system/bp.temp
echo "persist.sys.use_dithering=0" >> /system/bp.temp
echo "persist.sys.purgeable_assets=1" >> /system/bp.temp
echo "dalvik.vm.dexopt-flags=m=y" >> /system/bp.temp
echo "windowsmgr.max_events_per_sec=300" >> /system/bp.temp
echo "net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288" >> /system/bp.temp
echo "net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152" >> /system/bp.temp
echo "net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288" >> /system/bp.temp
echo "net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288" >> /system/bp.temp
echo "net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144" >> /system/bp.temp
echo "net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144" >> /system/bp.temp
echo "net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152"

these were copy and pasted from his script. These are extremely common and well known build props and are found in probably every single rom we have here. As for actually running the script to add the init.d and build.prop? I wouldnt. It was made for the HTC Rezound and HTC usually has a different setup not to mention thats its all to easy with rom toolbox lite (free) to add these manually and at the very least semi safely.

To sum up is this safe for our phone? Probably, but not recommended, by me anyways. Also its very likely that its all already on your phone, if you have flashed any custom rom. :)

Hope this helps to quell your curiosity for a bit! :D

*EDIT: At least this is the case for the v4 I didnt look at the other ones but Im sure its all similar.
 
Any script that was WORTH keeping is OR isn't in #2. L has been there and done that. Want more info on specific scripts, I would ask him. ;)
 
Back
Top Bottom