Database Info

something up with my shell scripts.

I seem to be frequently flashing or messing up my G1 so I decided to write some shell scripts to help out but they seem to only half work if at all. Actually I'm not sure what they did because they displayed no output.
This script is supposed to backup the default init.rc and mountd.conf files then replace the existing ones with the modified ones.
Though it does not work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
busybox cp -a /system/etc/mountd.conf /sdcard/recovery/mountd.conf.bak
busybox cp -a /system/init.rc /sdcard/recovery/init.rc.bak
busybox cp -a /sdcard/recovery/mountd.conf /system/etc/mountd.conf
busybox cp -a /sdcard/recovery/init.rc /system/init.rc
then this is the next set to move the apks and the program caches which doesn't work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
busybox cp -a /data/app /system/sd
rm -r /data/app
ln -s /system/sd/app /data/app
busybox cp -a /data/app-private /system/sd/app-private
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -R /data/data/com.android.browser/cache/webviewCache
ln -s /sdcard/cache/webviewCache /data/data/com.android.browser/cache/webviewCache
rm -R /data/data/com.android.vending/cache
ln -s /sdcard/cache/marketCache /data/data/com.android.vending/cache
rm -R /data/data/com.google.android.street/cache
ln -s /sdcard/cache/streetCache /data/data/com.google.android.street/cache
reboot
Plus both run and output no errors either. Who knows what problems I'll run into because I have no idea what they actually did.
Anyone see anything wrong here?

Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
I have a menu that does that and I have got some experience as why it works one day and not the other.

Rafase282 said:
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
Click to expand...
Click to collapse
I took the reboot out after the mountd.conf and init.rc did not appear to copy due to the lack of /dev/mmcblk0p2 hoping to see some sort of output why it did not run. Unfortunately it runs and backs up the files but does not replace them with the modded ones.
Rafase282 said:
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
Click to expand...
Click to collapse
Not copying the apps is a good idea, modified the script to not do so.
Rafase282 said:
I have a menu that does that and I have got some experience as why it works one day and not the other.
Click to expand...
Click to collapse
Does Android require that you do a chmod on all shell scripts first?
On Debian I usually just use sudo sh ./ and it runs the script w/o changing anything on the file permissions so I figured Android would be similar if I just ran them as root. Still I see a lot of people requiring a chmod 777 on any guide referring to running shell scripts.
I will try that and report back with my findings. Thanks for replying.

Does Android require that you do a chmod on all shell scripts first? I just have to type m oon anywhere in the androud shell and my scripts run, for that i put it on /system/bin and do a chmod 4755 to the file. it is still needed to type su before you run the script.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
cp /sdcard/media/Data/mountd.conf /system/etc/mountd.conf
cp /sdcard/media/Data/init.rc /system/init.rc
Thats my code for copying the modified files to the right place. So maybe you should try that.
Oh for androoid you dont unless you put it on /system/bin then you will have to use sude and sometiems it still wont run due to lack or permisions so is better to do a chmod 4755

Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.

joshtheitguy said:
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
Click to expand...
Click to collapse
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once

LucidREM said:
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
Click to expand...
Click to collapse
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.

joshtheitguy said:
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
Click to expand...
Click to collapse
yes .. but you can't create the sym links when they already exist .. running the update.zip only wipes the /system .. not /data .. if the links were there before the update.zip they will be there after

i didnt need a thread for this....sorrry!!!!!!!!!

I've tried the method below and it doesn't seem to work........it doesn't give me errors......but it doesn't delete the files that I don't want anymore.
I did try searching the forums but didn't see any posts regarding this....but seeing how new the 1.5 firmware it is...I didn't think there would be a post on it anyway and didn't think the command prompt or the location of these files would change
Any help is appreciated
-Type su
mount -o rw,remount -t yaffs2 /dev/block/
mtdblock3 /system
rm -r /system/media/audio/ringtones
rm -r /system/media/audio/notifications

I did this yesterday, and removed all the stock ringtones and replaced with htc defaults.
I did this from ADB shell, I suppose you can do it from the terminal, matter of fact I'm sure you can.
The trick is to use busybox.
#commands below
busybox rm -rf /system/media/audio/ringtones # remove ringtones
busybox rm -rf /system/media/audio/notifications # removes notifications
# this removed all my ringtones and folders
After that I just used "adb push c:\ringtones /system/media/audio/ringtones"
That simply took whatever .ogg / .mp3 ringtones and put them back on the system memory of my G1.
Using JF 1.5, didn't need to go into recovery or anything.

[HOWTO]Wipe EXT + DATA with ease!

I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
if you wish to save your userinit.sh
Code:
mount /system/
mount /data/
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*
rm- rf /data/*
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.

This is awesome thanx. It will be useful.
Question:
I understand wiping the apps of the ext but why would you want to wipe the data when you can just do an alt+w? Wouldn't an alt+w also wipe the data?

Mine shows /system/sd/ empty, but when I boot up into the OS all the apps are still there.

Thanks Denkai, one thing missing...
First
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Denkai said:
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/;
mount /data/;`
rm -rf /data/* ;
rm -rf /system/sd/* ;
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse

I usually would do mount /system/sd/ then rm -rf /system/sd/*

Denkai said:
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/;
mount /data/;`
rm -rf /data/* ;
rm -rf /system/sd/* ;
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
You forgot 'mount /system/sd' step. Also, instead of 'rm -rf /system/sd/*', you may wanna say 'rm -rf /system/sd/app*;rm -rf /system/sd/dalv*;'. You don't want to delete people's custom /system/sd/userinit.sh.

this should be included in the cyanogen+JF recovery, so we can just do it there before installing new roms.

devsk said:
You forgot 'mount /system/sd' step. Also, instead of 'rm -rf /system/sd/*', you may wanna say 'rm -rf /system/sd/app*;rm -rf /system/sd/dalv*;'. You don't want to delete people's custom /system/sd/userinit.sh.
Click to expand...
Click to collapse
you don't need to mount system/sd it gets mounted when you mount system. and the idea by 'rm -rf /system/sd/*' instead of what you are saying is so that it does wipe EVERYTHING. hense the context. if they don't want to remove thier userinit.sh, they need to keep a copy.

Denkai said:
you don't need to mount system/sd it gets mounted when you mount system. and the idea by 'rm -rf /system/sd/*' instead of what you are saying is so that it does wipe EVERYTHING. hense the context. if they don't want to remove thier userinit.sh, they need to keep a copy.
Click to expand...
Click to collapse
Mount command is not recursive. Somebody cribbed about their '/system/sd' being empty, it was because of this.

no it wasn't. I've tested it. the apps folder is there with all the .apks. test it out yourself. they probably didn't know what they were doing.

it says device or resource busy.. :S
what to do?
UPDATE: this works..
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
but honestly i dont know the difference between all these commands...

When I wipe it involves formatting the partition, not just deleting the data off it. i.e. `mke2fs -j /dev/block/mmcblk0p2`

so if i do this:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
will my FAT32 partition remain intact?
my end goal is to wipe/nuke everything on my EXT3 and then reflash a ROM all from 1.4 recovery.

elingreen said:
so if i do this:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
will my FAT32 partition remain intact?
my end goal is to wipe/nuke everything on my EXT3 and then reflash a ROM all from 1.4 recovery.
Click to expand...
Click to collapse
Your FAT32 should not be touched using this.

dumfuq said:
When I wipe it involves formatting the partition, not just deleting the data off it. i.e. `mke2fs -j /dev/block/mmcblk0p2`
Click to expand...
Click to collapse
awesome, tried it and works... i have 4 apps installed.. so nuking is my best option!!!
thanks man!

Denkai said:
however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
I believe this 'could' work
the files are in RAM, so not all needed. Possibly deleting them all and then an immediate reboot would work

or delete and then r/o really fast.

I5800XWJPI Deodex (Flash trough CWM)

Hi.
There is (i think) an easy way to deodex (for ADB users).
First step, download this file who contain they flashable .zip for CWM : Link
Push this zip into your sdcard.
Then, connect you phone with USB, open your cmd.exe and put this commands :
Code:
adb shell
su (only if you dont got the "#" sign)
mount -o remount,rw /dev/block/stl9 /system
rm -r /system/app/*.apk
rm -r /system/app/*.odex
rm -r /system/framework/*.jar
rm -r /system/framework/*.odex
reboot recovery
Put those line ONE by ONE for sure to not missing a step (Dont care about Force close on the phone )
After your phone is reboot on CWM, choose "install zip from sdcard", and choose "XWJPI_deodex_signed.zip", wait few moment, then reboot
Enjoy
Thanks to Rudolf for show us the way to deodex

[TWEAK] [ROOT] mDNIe screen sharpness tweak

If in file "sys/class/mdnie/scenario" in first byte replace 0 to 1 or 2 or 3 or 4 screen sharpness is increasing (1 more sharp.........4 less sharp.).

my taste
I have tryed 2 and 3. My taste is 3 perfect

is this safe

zeyadhan said:
is this safe
Click to expand...
Click to collapse
Absolutely. I like 3.

alexhc18 said:
Absolutely. I like 3.
Click to expand...
Click to collapse
yeah 3 is nice.But it resets to zero every time I change wallpaper.
any way to make it permanent .

alexhc18 said:
If in file "sys/class/mdnie/scenario" in first byte replace 0 to 1 or 2 or 3 or 4 screen sharpness is increasing (1 more sharp.........4 less sharp.).
Click to expand...
Click to collapse
For some reason, I can never get this to work. When I try to make the changes by navigating to sys/class/mdnie, there's another folder/shortcut that takes me to another minor folder. In there, I see the scenario file and quite a few others. It even has text and no single digit (like my note 2 did) further more, any changes I make to the scenario file never stick. Maybe the T-Mobile US version is different?

When I reboot will the value reset itself? And do I need reboot after changing the value? I'm confused hmm.
RE: OK I figured out the thing that I asked. (I had no time to try those when I asked.)
1) No need to reboot after editing.
2) After reboot you have to re-do it.
Sent from my SM-N900 using XDA Premium HD app

3 looks bad ass. Use root explorer. Its what I used and changed the value easily.

so 0 value is the most sharpness ?
right ?
Sent from my SM-N900 using XDA Premium 4 mobile app

Is there anyway to make it permanent? Rather than redoing anytime when power off or reset. .w

garykcliu said:
Is there anyway to make it permanent? Rather than redoing anytime when power off or reset. .w
Click to expand...
Click to collapse
Make init.d support on mobile and create file "00mdnie" in folder "etc/init.d" with this inside:
#!/system/bin/sh
echo 3 > /sys/class/mdnie/mdnie/scenario
busybox mount -o remount,rw -t auto /system;
busybox chmod -R 777 /system/etc/init.d;
busybox mount -o remount,ro -t auto /system;
Or type in "terminal emulator" : echo 3 > /sys/class/mdnie/mdnie/scenario
Apps camera and gallery resets this to default 0

alexhc18 said:
Make init.d support on mobile and create file "00mdnie" in folder "etc/init.d" with this inside:
#!/system/bin/sh
echo 3 > /sys/class/mdnie/mdnie/scenario
busybox mount -o remount,rw -t auto /system;
busybox chmod -R 777 /system/etc/init.d;
busybox mount -o remount,ro -t auto /system;
Or type in "terminal emulator" : echo 3 > /sys/class/mdnie/mdnie/scenario
Apps camera and gallery resets this to default 0
Click to expand...
Click to collapse
I just followed your guide but still cannot make it work as well.
Perhaps it is too technical for me but anyway thanks so much for your assistance.
By the way, is it possible to make a flashable zip so that we can flash on CWM?
Thank you

garykcliu said:
I just followed your guide but still cannot make it work as well.
Perhaps it is too technical for me but anyway thanks so much for your assistance.
By the way, is it possible to make a flashable zip so that we can flash on CWM?
Thank you
Click to expand...
Click to collapse
First you need busybox. Install this by Stericson: https://play.google.com/store/apps/details?id=stericson.busybox
reboot after installing. Open busybox, use "normal install" method to "system/bin", don't use "smart install".
Then CWM install this:
View attachment zip_init.zip by Ryuinferno

alexhc18 said:
Make init.d support on mobile and create file "00mdnie" in folder "etc/init.d" with this inside:
#!/system/bin/sh
echo 3 > /sys/class/mdnie/mdnie/scenario
busybox mount -o remount,rw -t auto /system;
busybox chmod -R 777 /system/etc/init.d;
busybox mount -o remount,ro -t auto /system;
Or type in "terminal emulator" : echo 3 > /sys/class/mdnie/mdnie/scenario
Apps camera and gallery resets this to default 0
Click to expand...
Click to collapse
#!/system/bin/sh
#Replace the number down here with what you want
VAL=`3`
#init.d commands (optional)
busybox mount -o remount,rw -t auto /system;
busybox chmod -R 777 /system/etc/init.d;
busybox mount -o remount,ro -t auto /system;
#auto check commands
while [ 1 ]
do
VAL1=`cat /sys/class/mdnie/mdnie/scenario`
if [ "$VAL1" != "$VAL" ]
then
echo "$VAL" > /sys/class/mdnie/mdnie/scenario
fi
sleep 1
done

iba21 said:
#!/system/bin/sh
#Replace the number down here with what you want
VAL=`3`
#init.d commands (optional)
busybox mount -o remount,rw -t auto /system;
busybox chmod -R 777 /system/etc/init.d;
busybox mount -o remount,ro -t auto /system;
#auto check commands
while [ 1 ]
do
VAL1=`cat /sys/class/mdnie/mdnie/scenario`
if [ "$VAL1" != "$VAL" ]
then
echo "$VAL" > /sys/class/mdnie/mdnie/scenario
fi
sleep 1
done
Click to expand...
Click to collapse
Unfortunately no matter how hard I tried, I still cannot get it worked.
I have no other alternative but to give up.
Anyway thanks so much for your advice.

You need a rom witch has the init.d script.. or busybox and create the init.d folder + putting the correct permissions
And sure.. you have to create a script witch contains that code

iba21 said:
You need a rom witch has the init.d script.. or busybox and create the init.d folder + putting the correct permissions
And sure.. you have to create a script witch contains that code
Click to expand...
Click to collapse
This is what I have done...I have enabled the init.d support and then go into the etc/init.d folder to create a file '00mdnie' without extension which contains the codes:
------
#!/system/bin/sh
echo 3 > /sys/class/mdnie/mdnie/scenario
busybox mount -o remount,rw -t auto /system;
busybox chmod -R 777 /system/etc/init.d;
busybox mount -o remount,ro -t auto /system;
------
However every time when I shut down or reboot the N900 and then it will automatically reset to 0 and could you please advise when went wrong with the procedures that I am doing.
Thank you so much.

You have to put what i wrote.. all codes

tried that in CM11 4.4.2, manual setting scenario works but its uncomfortable to change it everytime it resets. pasting your code into init.d makes no difference... any ideas? i love sharpness tweaks but don't want to change kernel now so....

Script init.d
00mdnie
Code:
#!/system/bin/sh
# By @criskelo - CriskeloRoms
# Mod By @alexhc18
chmod 777 /sys/class/mdnie/mdnie/scenario
echo 1 > /sys/class/mdnie/mdnie/scenario
chmod 555 /sys/class/mdnie/mdnie/scenario
This prevents the gallery or camera changes the value to 0
:good:
Edit:
chmod 555 /sys/class/mdnie/mdnie/scenario
Read only and execution
Do not write
Edit:
ATTACHED FILES
All in one
Only install by CWM
ADD in your rom
screen sharpness 1
Support-Init.d