This is something I realized when the init.d hack by naven was posted, it plain didn't work for me, and after some investigation i discovered that not all busybox versions had the run-parts applet.
It has come to my attention to that many users may not have the proper hack installed, at least the ones using my scripts, I had them check in /data for the zipaplign log and it was in fact not there.
I got it working by modding navens hack. Credit goes to him for his discovery.
Here is a link to the flashable zip. If you are using my scripts, check in /data for the zipalign log, if you don't have one, just flash this zip, reboot, and check again.
http://www.sendspace.com/file/9g6ngz
Thanks!
Edit (8/31/2011): Just so there is no confusion, this is not my new Speedy script, this is just a re-hack for init.d originally discovered by naven. This will just help those of you having problems with his hack. Obviously you need to be rooted and have recovery bootstrap.
Just flashed your zip. Log file in /data
Welcome back! Thanks for your work on the X2.
Sent from my DROID X2 using xda premium
Grapejelly!!
Sent from my DROID X2 using xda premium
Worked perfectly
Sent from my DROID X2 using XDA App
Is this a new version of your script then?
Do we have to flash this the same way with recovery (aka renaming it to update.zip) like i had to go with the manual gb update?
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
SuBDivisions said:
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
Click to expand...
Click to collapse
There is an option under advanced I think, in recovery, to enable/disable that.....
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You need to use the modified boot -strap recovery available on this forum. D/L it & install it like any other app. When you open it, just read & follow the directions on the screen & you will get to the custom recovery where all good things flash from.
Sent from my DROID X2 using xda premium
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You should be flashing this thru the Bootstrap Recovery, not the default Android Recovery.
Sent from my DROID X2 using Tapatalk
Ahh HA.. See i know i was missing something.. Thanks have been given.
Zip-align logs were not showing in /data/ for me, so I flashed this, and now they do.
I'm assuming that means the rest of the scripts weren't working either?
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
BusyBox with run-parts binary, installed in /system/xbin - If you don't have BusyBox, you can download it from the market here.
Click to expand...
Click to collapse
hapyman said:
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
Click to expand...
Click to collapse
You should be okay on 1.19.0 now, but busybox should always always be installed in xbin.
So which init is better or the working one?
gkitab said:
So which init is better or the working one?
Click to expand...
Click to collapse
Some people find that the re-hack (this thread) works (and the original does not), others find that the original hack works just fine. A way to test is to install my Speedy Gonzales scripts, reboot the phone, and then check in /data for a zipalign log. If not, then flash this re-hack.
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing. I also noticed when I flashed speedy navens old oo got left behind. So I deleted al scripts in init folder and reflashed yours and all yours are now correct.
With his init and your script. Yours scripts are in there but no zipalign in data.
Should I start over by deleting unit folder flash your unit then speedy would that be the safe bet?
Thanks for staying.
gkitab said:
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing.
Thanks for staying.
Click to expand...
Click to collapse
They are two separate things entirely. I posted the re-hack for those having troubles getting scripts to run with naven's original hack. The re-hack posted in this thread doesn't contain any init.d scripts, it's purely the hack. Like I said above, a good way to test his hack is to install my scripts (which it looks like you have), and then use a file manager like Root Explorer and navigate to /data, there should be a zipalign log, if there isn't then his hack isn't working.
Edit: Well, the biggest question is if the init hack you have installed is even working. I'm assuming you have naven's... try the above, let me know if the log is there or not.
I edited my post can you please check it and let me know what you think.
I do have his with your script.
I think I should I should delete init completely and start fresh with yours and your scripts. That sounds like safest bet. Or does naven init need to be there first then yours on top then your scripts. Thanks.
Related
Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid
While attempting to modify my wpa_supplicant in /system/app (not by any process listed here) I somehow managed to completely destroy my /system partition. Not a single file was left alive. My nook did not particularly like this, and now will not boot. I had installed cwm recovery through indirect's app, and cwm won't flash either of Barnes and noble's update zips for some reason. My question is, does anybody have a cwm compatible zip that will restore my /system, or can anyone point me to information on how to make one? Cwm's scripting language seems to be poorly documented, if documented at all. Thank you in advanced for any help! I worked on this for several days before posting.
Sent from my MB860 using xda premium
Have you tried with adb? If not then you haven't try it all.
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM mount /system, take the \system folder of the acclaim_update.zip(unzip it) and put it in C:\ntroot ( where adb should be) , cut \system\bin folder and put it outside so it will look like this C:\ntroot\bin, open CMD as administrator and run
>cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push bin /system/bin ( it will push all the files inside bin folder to /system/bin and override them)
Repeat the process with the other folders.
Wish you luck!
PS: if you have CWM backup you could even unpack system.img is easy but you need linux ubuntu is fine so you use your own modified tweaked and working system.
~ Veronica
Sent from XDA premium using my Nook Tablet
Thank you, I didn't know adb could push entire folders! I would still like to learn how to make flashable zips, though. Should I just read the source code or something? I really cannot find any documentation.
Sent from my MB860 using xda premium
Zapcorns said:
Thank you, I didn't know adb could push entire folders! I would still like to learn how to make flashable zips, though. Should I just read the source code or something? I really cannot find any documentation.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Pm celticwebsolutions user he just learned how to make flashable zips so he must have the documentation, I will look into it this week. Let me low if you managed to fix your nook.
~Veronica
Sent from XDA premium using my Nook Tablet
http://forum.xda-developers.com/showthread.php?t=1187313
http://www.freeyourandroid.com/guide/introdution_to_edify
http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/
A cwm flashable zip must have a META-INF directory and whatever you're loading with a structure like below:
/META-INF
-/com
--/google
---/android
----/update-binary (file)
----/updater-script (file)
/system (or whatever you're loading)
'updater-script' uses the edify script language to mount, copy, set permissions, etc. Make sure this is in unix formatted text and not dos/win. Some CWM versions dislike dos/win formatted text. May as well make sure it's unix to avoid any issues.
You can just pull 'update-binary' from any flashable zip for the NT.
Once the zip is created you need to sign it, but CWM can be set to ignore that.
Just look at other cwm installable zips for examples.
http://downloads.androidsu.com/superuser/
http://forum.xda-developers.com/showthread.php?t=1458452
Igthorn said:
http://forum.xda-developers.com/showthread.php?t=1187313
http://www.freeyourandroid.com/guide/introdution_to_edify
http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/
A cwm flashable zip must have a META-INF directory and whatever you're loading with a structure like below:
/META-INF
-/com
--/google
---/android
----/update-binary (file)
----/updater-script (file)
/system (or whatever you're loading)
'updater-script' uses the edify script language to mount, copy, set permissions, etc. Make sure this is in unix formatted text and not dos/win. Some CWM versions dislike dos/win formatted text. May as well make sure it's unix to avoid any issues.
You can just pull 'update-binary' from any flashable zip for the NT.
Once the zip is created you need to sign it, but CWM can be set to ignore that.
Just look at other cwm installable zips for examples.
http://downloads.androidsu.com/superuser/
http://forum.xda-developers.com/showthread.php?t=1458452
Click to expand...
Click to collapse
lol now i realized i've always played with the tools for make this but i have never used them to create update.zip's or flashable zips just to extract .img files and sign them lmao, i have made a tutorial about this in other forum toowhich will be posting here too, for now i leave the tools i used like unyaffs, etc which are needed and will make your life easier.
IMG_tools.zip
And this is the tutorial, just some more reference
~ Veronica
Good news, I just managed to make it fail to boot at a different point. That's not much, but its progress. Does anyone have any ideas? I did successfully restore /system (I think) so I don't know why I'd won't boot.
Sent from my MB860 using xda premium
Zapcorns said:
Good news, I just managed to make it fail to boot at a different point. That's not much, but its progress. Does anyone have any ideas? I did successfully restore /system (I think) so I don't know why I'd won't boot.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
unmount system, wipe cache, advanced> wipe dalvik cache, fix permissions in CWM try that and give more details of its status.
~ Veronica
Zapcorns said:
While attempting to modify my wpa_supplicant in /system/app (not by any process listed here) I somehow managed to completely destroy my /system partition. Not a single file was left alive. My nook did not particularly like this, and now will not boot. I had installed cwm recovery through indirect's app, and cwm won't flash either of Barnes and noble's update zips for some reason. My question is, does anybody have a cwm compatible zip that will restore my /system, or can anyone point me to information on how to make one? Cwm's scripting language seems to be poorly documented, if documented at all. Thank you in advanced for any help! I worked on this for several days before posting.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
find any CW flashable zip, get the 1.4 acclaim zip, copy all content from acclaim zip, EXCEPT META folder, to the CW zip, and put the CW zip, overwrite if it asked, you just produced on SD and flash it win recovery. You will need to re-root.
So, I managed to do the same thing...not to ask for help or anything but can someone provide a link to a CW zip that can get me back to square one?
I was finally able to fix it! Using Cobrato's flashable zip in the developer forum, i was able to flash a working system. It even included many of the apps i had been using before not available on the market. Thank you for all youre help.
Sent from my BNTV250 using xda premium
Zapcorns said:
I was finally able to fix it! Using Cobrato's flashable zip in the developer forum, i was able to flash a working system. It even included many of the apps i had been using before not available on the market. Thank you for all youre help.
Sent from my BNTV250 using xda premium
Click to expand...
Click to collapse
Great News!
Please update your OP title.
And link to the file that fixed it. I'm sure one of us other n00bs will do the same.
Sent from my PG06100 using xda premium
Heric1 was in the same situation but i gave him a link that i found in development with 1.4.0 stock ROM with indirect and cfoesch root methods and it worked ill post this links in My FAQ. Development should have the thread that was created to index all the ROMS updated and stickied
http://forum.xda-developers.com/showpost.php?p=21748940&postcount=57
~ Veronica
Sent from XDA premium using my Nook Tablet
Is busyBox built into CWM recovery kernals? is this common practice?
if so, and "I believe it is" How can I update my busyBox Version?
The experience Im having is on stock 2.3.4 when I check with root checker pro .apk it shows BusyBox Version 1.19.2cm71 installed in /sbin/ So I try to update to BusyBox version 1.19.4stericson via his BusyBox installer .apk Then check with Root checker Pro .apk and all is well Untill I reboot My phone Imediatly after reboot Root cheker shows the old Busy Box version again.
So I geuse what Im asking for is verification basicly.
Is there not a tool to incorporate CWM into existing stock recovery like the one used for the OG transformer Tab?
By the way to all comers who would like to bash my noobness Bring it!
I say this because I can learn more from the bashing than from no response/answer at all.
That being said Thanks to the Devs that do chime in with direct, and helpful responses. Its much appreciated by me as this is my main source of refferance for android learning. My post count is so low because I read !
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Pirateghost said:
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
Click to expand...
Click to collapse
Thanks for your response, but I Know what busybox is and where its supposed to be but if you have CWM recovery do me a favor and check your "/sbin" folder on "root of phone" not in the "/system" folder there you will see "busybox" in "/sbin". Also there is an app called "root checker" by Joey something or other if you run this app and swipe to the left you'll see the screen verify busybox click it and it will tell you where its installed and what version is installed.
I originaly thought same as your reply and its true as long as you install busybox While using stock recovery. Meaning if I install busybox to "/system/xbin" with CWM recovery installed my newer busybox version won't stick. (Only good until reboot)
I've completely reverted to stock 2.3.4 GB and checked the /sbin folder before and after installing codeworkx 5.0.2.3 CWM revovery and These were my findings.
However on the skyRocket I do not seem to have this problem I believe this is why.
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
While Great for My "I727" that doesnt help me on my "I777"
rdannar said:
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks but not at all what I was talking about.
Phatboyj420 said:
Thanks but not at all what I was talking about.
Click to expand...
Click to collapse
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
rdannar said:
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks again but your still off please re-read O.P.
Ive done all that you suggest. in doing so I,ve learned that when I manualy delete busybox from "/sbin" it gets re-written upon reboot.
The only Rom with CWM recocery That I've found this not to be true in is "task650's" latest ICS release UCPLC5, It does initialy install busybox but not to
"/sbin" and it does'nt get re-written on every reboot. Thus allowing the users busybox update to stick. Thanks for that Task.
I experience the same troubles with GB SpeedMod Kernel v2.21 which includes CWM 5.0.2.3, so I searched around and found this thread.
Running StockROM (GB 2.3.6) the updates of BusyBox (have it in /system/xbin) work perfectly, no second version anywhere (/system/bin or /sbin).
Flashing SpeedMod Kernel with CWM delivers a second copy of BusyBox into /sbin, where busybox itself is a symlink to recovery in the same directory. Bad enough that an update to the latest BusyBox version seems to be fine but doesn't stick after reboot (as mentioned by Phatboyj420, for clarification: the update in /system/xbin sticks but the update or deletion of BusyBox in /sbin is reverted as part of kernel during reboot), so e.g. Ghost Commander shows some errors (owner and file permissions) which are related to this mixed version status and disappear after updating BusyBox (till the next reboot).
To confirm that CWM delivers BusyBox to /sbin I looked into the source of SpeedMod v2.21 (find it here!). Just unpack it and have a look into /initramfs/out/sbin.
Does anyone use Supercharger v6 on AOKP? I tried using it, but I got an awk error, so I installed the modified busybox from their site, but it doesn't persist after reboot (reverts back to 20-cm9).
I guess my question is does anyone know if I can get these two to play nicely?
For people having this issue, please refer to zepplinrox's Supercharger v6 thread where you can find a script that will reinstall busybox 1.19.4 on boot.
Did you completelyremove all busybox information from your phone before installing the new version?
If so, try doing a cache and dalvik wrote in between (can't hurt) for kicks. If you get out working but can't get the minfrees to stick, run 99SuperCharger.sh as root and at boot.
Lemme know.
Clay
Sent from my SGH-I777 using XDA
use script manager, and have it set to run at startup
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
use script manager, and have it set to run at startup
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
just the 99SuperCharger.sh file, not the entire script.
Oh, and for sure use sm, haven't used terminal emulator but sm is easy to navigate and get used to.
Clay
Sent from my SGH-I777 using XDA
Last I checked, completely removing busybox is dangerous business. I can't seem to do it anyways . But I removed about as much as I can using the BusyBox app, but it still reverts back to 1.20.0-cm9 after a reboot.
Then I tried manually deleting /system/bin and /sbin, but as expected that caused very bad things to happen .-.
lol, nvm, deleting /system/bin and /sbin just f-ed up my su binary. After replacing that, BusyBox (app) is still reporting that I have 1.20.0-cm9 installed.
When you open busy box what does it tell you at the top? 1.20 or whatever?
Do you then have the option to choose what version you wish to install? If so, what happens if you choose 1.19.4?
I originally chose version 1 of the version 1.20's then reverted back to 1.19.4. I'm SuperCharged fine. I'm running a different Rom and Kernel, but that seems to working for me
Clay
Sent from my SGH-I777 using XDA
It tells me 1.20.0-cm9 installed if I use the free version. If I use the paid version, I get "multiple busybox installed" (possibly from TB?)
I'll give 1.19.4 a shot.
1.19.4 still reverts back to 1.20.0-cm9 on reboot.
use the boot reinstaller version from the supercharger OP.
It reinstalls wraithdu's v1.19.4 busybox build on every boot for situations like yours.
zeppelinrox said:
use the boot reinstaller version from the supercharger OP.
It reinstalls wraithdu's v1.19.4 busybox build on every boot for situations like yours.
Click to expand...
Click to collapse
Lol, I was just reallllyyy hoping to find a way around that lol.
I created that tool because there is no way around that - except for fight fire with fire
lol, thanks zeppelinrox. Should I set that up with sm? Or somehow put that in init.d? Does SS99Supercharger work then?
Yeah just run it like you do all my other scripts...
After rebooting, check to see which busybox build is active
Problem is that it always defaults to 1.20.0-cm9, lol. Whatever, I've just put your busybox installer script in init.d and having it run right before SS99Supercharger, and all seems to work well. Thanks a lot for you help and the awesome script
heh... well that's what the boot reinstaller script does - it converts the normal installer script to a proper init.d script (renames it to 96busybox and removes sleep commands and other stuff)
Oh my bad, you had a script for that? o.0 I assumed you meant "just copy it into init.d xD"
Looking now...lol
ya... it's called boot reinstaller or something like that... lol
wp_mod: Module to disable system write protection
This is a kernel module that disables write protection on the system partition while running the stock kernel.
HTC changed the MMC_MUST_PREVENT_WP_VIOLATION code to make it much harder to crack. I had to redo the module completely, so this is experimental. In the past, it was a simple matter of changing a variable, now we have to replace a function in the kernel so it returns something different, causing the kernel to skip over the write protection code.
I would caution against loading the module after attempting to make changes to the system partition. It could end up corrupting the filesystem. If the module is loaded at boot, there should be no worries.
This module will probably need to be updated to load with future kernels when they are released.
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Download:
wp_mod for GPE Marshmallow 6.0 can be found here:
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Sense 4.4.4 (thanks @migascalp):
http://www.mediafire.com/download/4vyqslnc4crsnto/wp_mod_3.28.401.6.zip
Sense 4.4.3 (2.22 base):
wp_mod.ko
Sense 4.4.2:
wp_mod.ko
GPE 4.4.4 (thanks to @italyforever):
wp_mod.ko
GPE 4.4.2:
wp_mod.ko
Installation:
Wait for it to be implemented in your favourite ROM
* or *
Copy the module to your device, and type
Code:
su
insmod /location-where-you-copied-it/wp_mod.ko
Changes:
April 2, 2014 - wp_mod 4.1
-only return non-existing partition number if called by generic_make_request_checks
-remove exit from module (we don't want to be able to unload it)
-clean up code
March 31, 2014 - wp_mod 4.0
-new method for HTC One m8
Source:
https://github.com/flar2/wp_mod
Module was compiled against m8 Google Play Edition source. Some symbol CRC checks had to be hexedited in the compiled module to match the stock kernel. Thanks to Michael Coppola for example of function hooking on arm: http://poppopret.org/2013/01/07/suterusu-rootkit-inline-kernel-function-hooking-on-x86-and-arm/#arm
Nice Job!!!! this is awesome
AWESOME! Thank you! Will test and see
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Confirmed working here. I was able to delete stuff with titanium backup and it stuck after reboot. Thanks so much!
Sent from my M8 via XDA Premium app
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
You guys are awesome.
Awesome work....Can now scratch my theming itch
Sent from my unknown using Tapatalk
gjlowe said:
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Click to expand...
Click to collapse
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
graffixnyc said:
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
Click to expand...
Click to collapse
Can you share your zip please
Sent from my HTC One_M8 using Tapatalk
gjlowe said:
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
Click to expand...
Click to collapse
You need to run it each time you boot, until it is correctly working as init.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Electronic Punk said:
You need to run it each time you boot, until it is correctly working as init.
Click to expand...
Click to collapse
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
gjlowe said:
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
Click to expand...
Click to collapse
Yup, I have already added it to my copy of ARHD 3.x and it is working great, so look for a release as soon as Mikes connection allows!
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
-4ndr01d- said:
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
Click to expand...
Click to collapse
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
flar2 said:
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
Click to expand...
Click to collapse
jcase has got us root access ...its only writable to /system/xbin and has to run on every boot. the app used is called WeakSauce
but i was thinking. once my phone boots up, i wait til i have root access, then download the file, place it in the correct directory, download terminal emulator and run the commands. then /system becomes writable until next reboot?
@flar2 nice job as always man!! :good:
awesome awesome awesome
looking forward to elementalx on the m8!
For users who have init.d support in their ROM. Flash this and your good to go
https://mega.co.nz/#!XINyDIrB!QcdP3sZJjgKAivkEa7iN8Jusx0e78T1rpA5PT7VGAxQ
Sent from my Note 3