Database Users

[Q] .sh script help

Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?

do you have an output you can show us?
Sent from my SCH-I500 using XDA App

This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.

Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....

Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.

wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.

Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..

dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.

I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.

This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500

imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.

sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App

jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.

sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App

[Q] Dualtouch installation problem

downloaded the gesture x8gesture-v004.zip and installed it,
downloaded update-floyo15-2011-03-26-rel-signed.zip and installed it,
checked all the relevant files (hw_config.sh- it had the necessary code in that file and the x8gesture.ko was in /system/lib/modules)
but it still didnt work. Am i missing something? i have baseband XXX015 and im using floyo. help?

dmcb123 said:
downloaded the gesture x8gesture-v004.zip and installed it,
downloaded update-floyo15-2011-03-26-rel-signed.zip and installed it,
checked all the relevant files (hw_config.sh- it had the necessary code in that file and the x8gesture.ko was in /system/lib/modules)
but it still didnt work. Am i missing something? i have baseband XXX015 and im using floyo. help?
Click to expand...
Click to collapse
Just read instructions again.. begin at the top.. maybe you missed something in the process.. ex. typo error.. because system work on me..
http://forum.xda-developers.com/showthread.php?t=1004740

I just re-read through the instructions and I have done it all correctly. I backed up a friends floyo (he has dualtouch) and restored it onto my phone and it still doesn't work
Sent from my X8 using XDA App

This happened to me too, using minicm rc1, Elelinux v3 and Nexus-x8 v2 also no luck to get it.
Minicm RC1 - using update-minicm2-2011-04-13-signed.zip (9.44 KB) after update,
no dualtouch, loose OC.
check with hw_config.sh, the code is at the bottom.
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
Install again 3 custom rom - minicm rc1, Elelinux v3 and Nexus-x8 v2
with factory reset
Manual Installation for the dualtouch and oc
I had added the code at the beginning
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
insmod /system/lib/modules/x8oc.ko # x8 overclock
As a result, Im only get the OC.
Edit: I had baseband 015, and i did adb shell command check also
adb shell
dmesg | grep X8Gesture
It returned a same output in the command prompt.
I had try with Multitouch Visualiser 2, always showing 1 touch

Add insmod line to the top of /system/bin/chargemon. I did that and it's working.

hi blagus, you mean add
insmod /system/lib/modules/x8gesture.ko at top of the line /system/bin/chargemon,
and how about the insmod /system/lib/modules/x8gesture.ko at the hw_config.sh,
leave it there or delete the command line?

lookingpost said:
hi blagus, you mean add
insmod /system/lib/modules/x8gesture.ko at top of the line /system/bin/chargemon,
and how about the insmod /system/lib/modules/x8gesture.ko at the hw_config.sh,
leave it there or delete the command line?
Click to expand...
Click to collapse
Remove insmod from hw_config and put it as the second line in chargemon.
In my case, chargemon looks like this:
Code:
#!/system/recovery/sh
insmod .../x8gesture.ko
insmod .../x8oc.ko
[...and so on...]
I think this is better method that hw_config because chargemon is the first thing executing on boot.

Hi blagus, my chargemon is start like this
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event 1 > /dev/keycheck&
sleep 3
Kill -9 $!
.... and so on ...
So i need to add like this ...
#!/system/bin/busybox sh
insmod /system/lib/modules/x8gesture.ko
insmod /system/lib/modules/x8oc.ko
/system/bin/charger
cat /dev/input/event 1 > /dev/keycheck&
sleep 3
Kill -9 $!
Edit: after test with Mr. Blagus method..the result still the same
OC worked but multitouch failed (I think is my hardware problem)

This didn't work for me either
Sent from my X8 using XDA App

I doubt that it's HW problem... I suggest you to flash baseband 015 again to make sure you have latest kernel.

blagus said:
I doubt that it's HW problem... I suggest you to flash baseband 015 again to make sure you have latest kernel.
Click to expand...
Click to collapse
this didnt work either :\ beginning to think it may well be a hw problem but i really dont understand how that could possibly be

No, it shouldn't be HW problem. When did you buy your phone?

ya..didnt work for me either, Im from malaysia, i also dont understand why will become like this..Now, only OC worked for me but i satisfied what i had now, actually the multitouch not very important for me, just curious to know what happened

About the phone last christmas
Sent from my X8 using XDA App

*I bought the phone last christmas
Sent from my X8 using XDA App

cool ill try it

dmcb123 said:
*I bought the phone last christmas
Sent from my X8 using XDA App
Click to expand...
Click to collapse
Me too, so it CAN'T be HW problem due to new revision... it's somewhere else.
First, chmod x8gesture to 777 (chmod 777 /path-to/x8gesture.ko)
If that fails...
Reflash stock FW (you can get it in my Mediafire folder), root, install xRecovery, then flash custom ROM, copy modules to /system/lib/modules and put insmod lines to chargemon.

blagus said:
Me too, so it CAN'T be HW problem due to new revision... it's somewhere else.
First, chmod x8gesture to 777 (chmod 777 /path-to/x8gesture.ko)
If that fails...
Reflash stock FW (you can get it in my Mediafire folder), root, install xRecovery, then flash custom ROM, copy modules to /system/lib/modules and put insmod lines to chargemon.
Click to expand...
Click to collapse
I had tried before using Root Explorer, tick all at the permission on x8gesture.ko, but dont know this step will be same as your method..will try later on. (Now im using minicm rc2,best rom atm only compass not work)
Edit: after chmod 777 - x8gesture.ko (rwxrwxrwx)
As a result - multitouch didint work, i lost root again (this is 2nd time, first time install floyo theme), now restore back RC2

Dont really want to go back to stock fw, ill wait a while for an update and then see about going back. Thanks anyway really appreciatedappreciated
Sent from my X8 using XDA App

To Blagus,
Reflash stock FW (From your Mediafire folder) and the Build 2.1.1.A.0.6 provided by mohakrastogi, is it the same method?

[OUTDATED GUIDE]Make Custom Rom Easier Than Cycling

Things you need:
Base firmware (i'm use Gingerbread S5830SERKPH 2.3.4)
Windows (I'm use windows 7 X64 service pack 1)
Linux (Ubuntu recommended)
And the last thing is, You need enough experience in android world
step-step :
Flash your phone with your desired base firmware.
Make required modifications at your phone.
After that, do hard reset to your phone.
Next back up system.rfs .
put system.rfs with boot.img, data.rfs, recovery.img from PDA base firmware in one folder.
After that, repack your custom rom.
what should we do to modify it :
Remove useless widgets
Add more apps
Change theme
How to back up System.rfs :
Download at market "terminal emulator"
next run this code:
Code:
su
dd if=/dev/stl12 of=/sdcard/system.rfs
How to hard reset your phone :
Move by root explorer your modification apps to system/app then change permission like this :
Code:
User:Read, Write
group:Read
Others:Read
Next change the owner to "root" by root explorer
At least boot into recovery mode "HOME+POWER" and choose "wipe data/factory reset" be sure your contact data already backup
How to repack your custom rom :
PDA by running this code via terminal at linux:
Code:
tar -H ustar -c boot.img recovery.img data.rfs system.rfs >> ROMNAME.tar
md5sum -t ROMNAME.tar >> ROMNAME.tar
mv ROMNAME.tar ROMNAME.tar.md5
change ROMNAME to your desired, of course, ROM name.
If you want to build One-Package ROM, just use 1st and 2nd command and don't forget to include all files on all *.tar.md5 (such as modem, csc, apboot) like this :
Code:
tar -H ustar -c *.* >> ROMNAME.tar
md5sum -t ROMNAME.tar >> ROMNAME.tar
How to change your rom name :
At root explorer you see at folder system "build.prop"
Open it in text editor edit "ro.build.display.id=GINGERBREAD.XXKPH" with your rom name
Another Handy Modification Guide:
How to edit system.rfs on your Pc :
importan : if you want to edit system.rfs at windows, DON'T use Magic Iso, why? because i was use it, then my system.rfs corrupt.
you must have linux (ubuntu recommended)
run it from terminal :
Code:
sudo mount -o loop system.rfs /some_dir
make required modification
then Unmount it
How to Unpacking & repacking the image :
Note: below I give you the details for unpacking and repacking manually, but I have attached two perl scripts that do most of this for you
If you are good with a hex editor, you can open up any of these images and strip off the first 2k of data. Then, look for a bunch of zeroes followed by the hex 1F 8B (which is the magic number of a gzip file). Copy everything from the first line of the file, through the zeroes, and stopping at the 1F 8B. That is the kernel. Everything from the 1F 8B through the end is the ramdisk. You could save each of these files separately. In order to see the contents of the ramdisk, you need to un-gzip it and then un-cpio it. You could use a command like this (ideally after creating a new directory and cd'ing into it):
Code:
gunzip -c ../your-ramdisk-file | cpio -i
That will place all of the files from the ramdisk in your working directory. You can now edit them.
In order to re-create the ramdisk, you need to re-cpio them and re-gzip those files, with a command like the following (remember, cpio will include everything in the current working directory, so you probably want to remove any other cruft you might have in there):
Code:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
The final step is to combine the kernel and your new ramdisk into the full image, using the mkbootimg program (which you should download and compile from the git repository):
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel your-kernel-file --ramdisk newramdisk.cpio.gz -o mynewimage.img
Now, there's a lot of hassle in pulling apart files in hex editors and remembering all of these commands, so I wrote unpack and repack perl scripts for you (attached). Hooray.
How to Manually deodex your phone :
What you'll need:
xUltimate v2.2
Unzip xUltimate v2.2, and launch "Main.exe"
If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
Run option 1. After option 1 is done, run option 2.
Now these well take a while. Run option 3.
IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
Now run option 4, and wait.
Exit xUltimate, and put the phone in USB mass storage.
Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
Put the phone in PC mode
Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Your phone should now be deodexed!
You may notice an increase in speed, and you now have the ability to edit certain files with greater effects.
How to change bootanimation :
using a Root explorer goto the /system/media directory.
Copy bootanimation.zip to your SD Card.
Connect your droid to your computer with usb and mount the SD Card
Copy bootanimation.zip to your computer.
extract bootanimation.zip to a folder
Inside you will find 2 folders with all the individual PNG files in them.
With photoshop or paint modify the png files to add your custom graphics, OR make/download your own pictures. (Make sure they are match with your phone device)
Highlight the two folders and the desc file.
Right click the highlighted files.
Select add files to archive.
Select Zip check box
In the compression method drop down box select Store. (this is key if you dont do this it wont play the animation)
save the archive as bootanimation.zip
copy the new bootanimation.zip to your SD Card
Select the bootanimation.zip file from your SD Card and move it... system>media>paste
________________
i'm just 12 years old if i can do it, why you can't

Advantages of this way is :
More efficient
Reduce your internet usage (dont need kitchen, apk manager, etc)
Easy to modification (You can see the direct result)
Reduce your time (only 2 hours i can do this way)
More soon

You steal my IDEAS Univos! No, just kidding, there are incorrect guide on "how to hard reset" lol. Anyway, try to build a ROM before creating this guide, my friend.

Wow Kids!
are doing development now a days

fla.sh said:
You steal my IDEAS Univos! No, just kidding, there are incorrect guide on "how to hard reset" lol. Anyway, try to build a ROM before creating this guide, my friend.
Click to expand...
Click to collapse
im not steal it.
Where is incorrect guide i'm try to fix it?
Sent from my GT-S5830 using XDA App

GadgetCheck said:
Wow Kids!
are doing development now a days
Click to expand...
Click to collapse
Thanks
Sent from my GT-S5830 using XDA App

This guide tested by me, and i have get result from this.
Sent from my GT-S5830 using XDA App

If you have question just ask me!
Sent from my GT-S5830 using XDA App

I think this guide is the same with fla.sh's guide.

devilsking said:
I think this guide is the same with fla.sh's guide.
Click to expand...
Click to collapse
Different, Fla.sh make guide for cooking his rom.
in this thread i tell you how to make your own custom rom.
with Phone device Samsung Galaxy Ace.

Univos said:
Different, Fla.sh make guide for cooking his rom.
in this thread i tell you how to make your own custom rom.
with Phone device Samsung Galaxy Ace.
Click to expand...
Click to collapse
ya ya. I see tks for your guide

devilsking said:
ya ya. I see tks for your guide
Click to expand...
Click to collapse
Please press thanks button, if i helped you
Sent from my GT-S5830 using XDA App

Univos said:
This guide tested by me, and i have get result from this.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk

EmoBoiix3 said:
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
Click to expand...
Click to collapse
Just kept reading, ask people, don't feel has a lot of knowledge, kept countinue to learn
Sent from my GT-S5830 using XDA App

EmoBoiix3 said:
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
Click to expand...
Click to collapse
Maybe this holiday i will developt a simple custom rom.
Sent from my GT-S5830 using XDA App

Univos said:
Maybe this holiday i will developt a simple custom rom.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I am thinking about a kid with two or more different XDA ID.

ketut.kumajaya said:
I am thinking about a kid with two or more different XDA ID.
Click to expand...
Click to collapse
No, the real name Fla.sh is "Aver..." my real name is "iz..." we are student of junior high school at surabaya. I'm "Aver..." friend.
Sent from my GT-S5830 using XDA App

Univos said:
No, the real name Fla.sh is "Aver..." my real name is "iz..." we are student of junior high school at surabaya. I'm "Aver..." friend.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I'm swear.
Sent from my GT-S5830 using XDA App

ketut.kumajaya said:
I am thinking about a kid with two or more different XDA ID.
Click to expand...
Click to collapse
ROFLAMO

Jukirdolly said:
ROFLAMO
Click to expand...
Click to collapse
??????
Sent from my GT-S5830 using XDA App

[GUIDE][ALL DEVICES + ALL ROMS] How To Add Init.d Support To Rom/Kernel

What is init.d ?
Init.d is a feature which allows you to run brunch of scripts at boot . Thats really useful while you want to set values which reset at boot or run/do any thing at every boot or install tweaks , engines and....
There are some ways to add this feature to you rom but always best way is to add init.d support directly by your kernel . I want to help you to do this
Requirements
1- Ability to unpack boot.img & ramdisk
2- Some basic linux shell knowloedge
3- Having Busybox located in /system/bin/busybox at your rom
Step 1: Making kernel ready
1- Unpack kernel then ramdisk
2- Open Init.rc with a text editor
3- Add this codes at the end , before the paragraph which there is "stop bootanim" command in it :
Code:
service sysinit /system/bin/sysinit
oneshot
4- Save , Exit and repack ramdisk and boot.img
Step 2 : Making Rom Ready !
1- Open /system/bin/sysinit
2- Add this codes :
Code:
#!/system/bin/sh
export PATH=${PATH}:/system/bin:/system/xbin
chmod 777 /system/etc/init.d/*
logwrapper busybox run-parts /system/etc/init.d/
3- Set permissions of sysinit to 777 or 755 ( rwxrwxr-x | rwxrwxrwx )
4- Make a directory at system/etc and name it init.d
Now you have init.d support !

Reserved for future changes !

Pls tell me about this '' init'' on my supersu dialog box...
It's my first time to see this and I don't know what is this for?
Is this harmful? Or very important not to loose it...
Educate me... I really don't know what is is for...
... What? why? how?
Thanks much!
Sent from my GT-I9300 using XDA Premium HD app

'' Init '' or '' init.d''
Pls differentiate....
What is this for?
Sent from my GT-I9300 using XDA Premium HD app

leio rusher said:
'' Init '' or '' init.d''
Pls differentiate....
What is this for?
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
leio rusher said:
Pls tell me about this '' init'' on my supersu dialog box...
It's my first time to see this and I don't know what is this for?
Is this harmful? Or very important not to loose it...
Educate me... I really don't know what is is for...
... What? why? how?
Thanks much!
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Read in the op what is init.d section...
Inviato dal mio GT-I9070 con Tapatalk 2

WP=OFF, Does It Work Though

JakeDHS07 said:
Ok guys. I am gonna throw you all a bone here. Cause I'm nice like that. I haven't been able to figure out the bootloader but I have gained write protection off already.
Heres the process I used
go to play store and download an app called BusyBox Install (No Root) and install it and install BusyBox
If you don't already go and download Android Terminal Emulator from the play store
Now after you install emulator open and enter su
Accept the superuser prompt
now go back to the busybox app and copy the link it gives you and enter in emulator by pasting and hit enter
exit out of emulator
reopen emulator and ensure su is enabled by looking for the $
enter the following command busybox mount -o rw,remount system
Wait a minute or so
Reboot and profit!
Click to expand...
Click to collapse
Found this going through the turbo section, does anyone want to try this?

[email protected]:/ $ su
[email protected]:/ # busybox mount -o rw,remount system
tmp-mksh: busybox: can't execute: Permission denied
126|[email protected]:/ #

JH1108 said:
Found this going through the turbo section, does anyone want to try this?
Click to expand...
Click to collapse
It's not going to be anything as already stated. If it was that easy, it would've been done already.

Disable system write protection
Did anyone try to use this kernel extension to disable Write Protection?

carbonat87 said:
Did anyone try to use this kernel extension to disable Write Protection?
Click to expand...
Click to collapse
I doubt it that's for HTC one
Sent from my XT1080 using XDA Free mobile app

kalel420 said:
I doubt it that's for HTC one
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
And what? A didn't ask what for is that extension.

carbonat87 said:
And what? A didn't ask what for is that extension.
Click to expand...
Click to collapse
No you asked if anyone had tried it and I said I doubt it it's for HTC one kernel, but feel free to try that should give you a very nice brick I would think.
Sent from my XT1080 using XDA Free mobile app

kalel420 said:
No you asked if anyone had tried it and I said I doubt it it's for HTC one kernel, but feel free to try that should give you a very nice brick I would think.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Seems you don't know anything about bricks. In the worst way it will give a soft brick which is easy to repair. If you can't help with this, what are you doing here?
I'm asking this question because it can be done only on unlocked bootloader.

carbonat87 said:
I'm asking this question because it can be done only on unlocked bootloader.
Click to expand...
Click to collapse
What makes You think it is only for unlocked bootloader? Anyway if You had unlocked bootloader you would not need to turn WP off.
Do we actually have any knowledge on how the write-protection is done in our phones? Is it the same way as in htc? Do we have the kernel code for this to look at? I did see that motorola released some code because of the gpl license, but is it there?

So I did try this and no luck.
I took the latest sources from here:
https://github.com/flar2/wp_mod
I took the motorola kernel sources from here:
https://github.com/MotorolaMobilityLLC/kernel-msm
I compiled the module and copied it to the phone, but insmod did not work:
insmod init_module failed (operation not permitted)
I did run su in the console before trying the insmod. I have no idea why I can't insert the module into kernel, maybe it would have to be copied into /lib/modules/ and insmoded at boot, but that would require to burn the module into the system and flash it, but i have no time for that currently.

pizmak said:
So I did try this and no luck.
I took the latest sources from here:
https://github.com/flar2/wp_mod
I took the motorola kernel sources from here:
https://github.com/MotorolaMobilityLLC/kernel-msm
I compiled the module and copied it to the phone, but insmod did not work:
insmod init_module failed (operation not permitted)
I did run su in the console before trying the insmod. I have no idea why I can't insert the module into kernel, maybe it would have to be copied into /lib/modules/ and insmoded at boot, but that would require to burn the module into the system and flash it, but i have no time for that currently.
Click to expand...
Click to collapse
Ok, thanks for great work. I'll try to find someone who would be able to bake into system your compiled module and give us dump.

carbonat87 said:
Ok, thanks for great work. I'll try to find someone who would be able to bake into system your compiled module and give us dump.
Click to expand...
Click to collapse
Just be careful with this, because if the module gets insmoded correctly, but does not work with our kernel and cause a reboot it will leave you with a brick and you would have to flash the filesystem once again without this module burnt in.