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

Root init.d enabled stock ZV5 boot image here

jhofseth

jhofseth

Member
The attached init.d enabling stock ZV5 boot image file is NOT zipped; re-name to boot.img (removing .zip in filename) and flash with Flashify (or whatever you prefer).

The attached init.d test file IS zipped and must be extracted (see below).
----
Your phone must be rooted.
Your phone must be on ZV5 update.
Your phone must have busybox installed (to /system/xbin/).
The init.d works on rooted stock ZV5 rom.
Make a backup with TWRP first of at least the 'boot'.
You must create /etc/init.d folder (see below).

This boot image gives you init.d support the proper way (ramdisk init.rc file edited).

*Do NOT flash the init.d test zip*, extract 00test and place into /etc/init.d (same folder as /system/etc/init.d). Create /etc/init.d first if you have not already. I use ESFile Explorer from Playstore, just enable root explorer in settings. Change permissions of init.d and all scripts to 755. owner: R-W-X, group: R-X, other: R-X in ES File Explorer properties (with root explorer enabled). 'Test.log' will appear in /data/ folder after reboot if successful.

Good luck! :)
 

Attachments

Last edited:
After flashing the above init.d enabling boot image with Flashify, you can use scripts like the following provides:

I found the attached performance/battery tweak CWM/TWRP flashable file here: http://www.theandroidhow.com/2014/06/performance-and-battery-tweak-all-android.html
The directions are in the link but the file is attached and flashed in recovery--only after init.d has already been enabled.

I haven't used it as I use pimp my rom from the playstore, but I don't have to use universal init.d anymore--the init.d boot image provides a superior init.d method.
 

Attachments

Hmm,tried this. Didn't work. Not sure why not. I followed directions. I'll try something else. Thanks anyway.
 
I tried that tweak package before. Damn near burnt up my phone, and consumed battery like water. Use caution anyone who tries this.
 
bg4m3r said:
I tried that tweak package before. Damn near burnt up my phone, and consumed battery like water. Use caution anyone who tries this.
Click to expand...
Yeah, haven't tried the performance/battery tweak, 'cause I use Pimp My Rom (now without universal init.d enabled 'cause boot image init.rc init.d is better) but if I did I'd cherry-pick. For example, I'd extract scripts I wanted from tweaks init.d file and and hand paste via ESFile Explorer with root explorer enabled into /etc/init.d (changing permissions with ESFile Explorer root explorer enabled to RWX RX RX; i.e., 755). Of course, you could do the opposite and CWM/TWRP flash the performance/battery tweak and then go into your init.d folder and hand-delete the scripts you didn't want. Regardless, I recommend running the following to see output.
in Android Terminal Emulator:

su
busybox run-parts /etc/init.d

After running the above command, you can see in terminal what works or doesn't and edit or delete scripts, accordingly. Good luck! :)
 
Last edited:
xry75 said:
Hmm,tried this. Didn't work. Not sure why not. I followed directions. I'll try something else. Thanks anyway.
Click to expand...
xry75, if rooted, stock, on ZV5 update, busybox installed to /system/xbin/, it could be a permissions-related issue. I use ESFile Explorer with root explorer enabled to change permissions and I never have issues of changes not sticking. :)
 
Last edited:
jhofseth said:
xry75, if rooted, stock, on ZV5 update, busybox installed to /system/xbin/, it could be a permissions-related issue. I use ESFile Explorer with root explorer enabled to change permissions and I never have issues of changes not sticking. :)
Click to expand...
Never mind, I used a different technique that used the terminal emulated. I now have init.d support. Thanks though.
 
jhofseth said:
To all, I recommend this Playstore Busybox: Busybox X
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
It's supposed to be the most complete Busybox and the free version is not limited!
(Just make sure to uninstall your old Busybox before installing Busybox X.)
Click to expand...
What does it have that others don't, and why do I need those things?
Seriously asking, I mean, i know what busybox is and why it's needed, but why do I need more busybox?
 
bg4m3r said:
What does it have that others don't, and why do I need those things?
Seriously asking, I mean, i know what busybox is and why it's needed, but why do I need more busybox?
Click to expand...

Its sort of like a set of commands that other apps can use but its a condensed version meant to run on mobile instead of a desktop so not all commands are always included so I assume that that one supposedly has the most of these commands.
 
cmdrdan said:
Its sort of like a set of commands that other apps can use but its a condensed version meant to run on mobile instead of a desktop so not all commands are always included so I assume that that one supposedly has the most of these commands.
Click to expand...
Yeah, I understand that, but why do I need the additional commands?
 
Not exactly getting the answer I'm looking for, but OK. However, I looked to see what version of busybox that app installed with the one I've been using since it doesn't show... My app shows a newer version.
 

Attachments

  • 1425264394541.jpg
    1425264394541.jpg
    74.6 KB · Views: 150
jhofseth said:
After flashing the above init.d enabling boot image with Flashify, you can use scripts like the following provides:

I found the attached performance/battery tweak CWM/TWRP flashable file here: http://www.theandroidhow.com/2014/06/performance-and-battery-tweak-all-android.html
The directions are in the link but the file is attached and flashed in recovery--only after init.d has already been enabled.

I haven't used it as I use pimp my rom from the playstore, but I don't have to use universal init.d anymore--the init.d boot image provides a superior init.d method.
Click to expand...
I flashed this and the remote wouldn't work, I don't recommend this one.
 
hmmm, could be permissions related. system tuner (or fix permissions app) fix permissions for quickremote app might help. not sure, though.
 
bg4m3r said:
Not exactly getting the answer I'm looking for, but OK. However, I looked to see what version of busybox that app installed with the one I've been using since it doesn't show... My app shows a newer version.
Click to expand...
hi bg4m3r, there are 43 additional applets in Busybox X versus Stericson Busybox. I've attached a PDF side-by-side comparison, so you can see what's what, if desired. I used to use Stericson Busybox before I found Busybox X, and I definitely prefer the ease-of-use of Busybox X installer! :)
 

Attachments

Thanks, that's more what I wanted to know, but are those extra commands really needed for much of anything?

Is it possible that the version of busybox you are using is why the init.d script didn't work?
 
What he's asking is, are we actually ever really going to need those additional commands busybox x has, whatever they may be? Most devs just use busybox, how will busybox x really benefit us?
 
bg4m3r said:
Thanks, that's more what I wanted to know, but are those extra commands really needed for much of anything?

Is it possible that the version of busybox you are using is why the init.d script didn't work?
Click to expand...
You mean the init.d script you linked me in the OC thread? Dunno. I'm not sure why that script kept unrooting my phone. Busybox X is the same as Stericson Busybox with 43 extra commands. Both default to installing to /system/xbin. I guess it just boils down to installer preference and/or if you like any of the extra commands in Busybox X. More commands make it closer to Linux, I guess--since Busybox is a substitute for Linux core-utils. :)
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom