Database Develop

[HOW-TO] Run commands and persist settings after reboot - Updated

Here is an easy way to run commands after each boot.
In the init.rc file, the file /system/bin/clrbootcount.sh always gets run after a successful boot. Since it isn't trivial to change the init.rc file, we will use clrbootcount.sh to run commands after a boot. Since people are having issues with modifying clrbootcount.sh, we will choose a safer method.
clrbootcount.sh will always attempt to call /data/boot_complete_hook.sh, which doesn't exit. We are going to create this file and use that to run commands.
Create a file named boot_complete_hook.sh with the following contents (On Windows, use Notepad++):
Code:
#!/system/bin/sh
##################################################################################
#
# File boot_complete_hook.sh
# Description Run any commands that you want to be run after boot
#
##
setprop persist.service.mount.umsauto 0
echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Save and close.
Now, execute the following commands to put the file on your nook:
Code:
adb push boot_complete_hook.sh /data/boot_complete_hook.sh
adb shell chmod 755 /data/boot_complete_hook.sh
Note:
Before you reboot verify that the file will run properly. Open up a shell via adb shell. Inside that run the following:
Code:
setprop persist.service.mount.umsauto 1
getprop persist.service.mount.umsauto
You should see 1 as the output. Now run:
Code:
sh /system/bin/clrbootcount.sh
You should see an output similar to:
Code:
4+0 records in
4+0 records out
4 bytes transferred in 0.010 secs (400 bytes/sec)
Now run:
Code:
getprop persist.service.mount.umsauto
If 0 is printed out, exit the shell.
If 0 is not printed out, something went wrong and the file will not be run properly on the next boot. If you do reboot in this state 8 times, the boot count won't be reset and you will hit the factory reset. While you are trying to get the script working, you could always manually reset the boot count by executing (from a shell):
Code:
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
Now reboot:
Code:
adb shell reboot
As you are rebooting, run:
Code:
adb shell getprop persist.service.mount.umsauto
It will return 1 since the init.rc file sets it to 1 explicitly. However, once you are fully booted it will return 0.

Didn't work for me.

JoshMiers said:
Here is an easy way to run commands after each boot.
In the init.rc file, the file /system/bin/clrbootcount.sh will always gets run after a successful boot. Since it isn't trivial to change the init.rc file, we will use clrbootcount.sh to run commands after a boot.
Do:
Code:
adb pull /system/bin/clrbootcount.sh .
Open the file (on Windows, don't use Notepad) and you should see:
Code:
#!/system/bin/sh
##################################################################################
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
Add the following to the end of the file:
Code:
#run other commands
setprop persist.service.mount.umsauto 0
Save and close.
Now, execute the following commands to put the file back on your nook:
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push clrbootcount.sh /system/bin/clrbootcount.sh
adb shell chmod 755 /system/bin/clrbootcount.sh
adb shell mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell reboot
As you are rebooting, run:
Code:
adb shell getprop persist.service.mount.umsauto
It will return 1 since the init.rc file sets it to 1 explicitly. However, once you are fully booted it will return 0.
Click to expand...
Click to collapse
Wouldn't this screw up the 8X "back to stock firmware" sequence since that depends on having the boot counter increment up to 8?

docfreed said:
Wouldn't this screw up the 8X "back to stock firmware" sequence since that depends on having the boot counter increment up to 8?
Click to expand...
Click to collapse
The script file is already there and already being called after each successful boot. The 8x boot counter logic happens with 8 failed boots. Regardless, the instructions just show you how to append a custom command to be run after the stock commands run, no other booting logic is affected.
>DARKMAN< said:
Didn't work for me.
Click to expand...
Click to collapse
What didn't work? Run the following and paste your output:
Code:
adb shell cat /system/bin/clrbootcount.sh
Code:
adb shell ls -l /system/bin/clrbootcount.sh

Awesome, thanks for the tip! Been wondering how to put in my own stuff into the init, I'd love to modify the path but I suspect this won't be the way, but regardless it's good info.
BTW, I have found that disabling this USM property seems to disable the SD card automounting but the Nook itself might still automount... But that's for another thread I suppose

Worked perfectly
This is exactly what I was looking for.
Thanks
Sent from my LogicPD Zoom2

There seems to be a little confusion over at the refresh rate thread http://forum.xda-developers.com/showthread.php?t=901294.
To be explicit, if you want to disable auto-mounting as well as change the refresh rate, you would edit clrbootcount.sh to have the following contents:
Code:
#!/system/bin/sh
##################################################################################
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
#run other commands
setprop persist.service.mount.umsauto 0
echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
If you don't want to disable auto-mounting, just remove the line with
Code:
setprop persist.service.mount.umsauto 0

I ran what was posted and it still returns 1.
Sent from my HAXSUNG Moment

JoshMiers said:
What didn't work? Run the following and paste your output:
Code:
adb shell cat /system/bin/clrbootcount.sh
Code:
adb shell ls -l /system/bin/clrbootcount.sh
Click to expand...
Click to collapse
Screen shot attached (1.0.1 Auto-Nooter 2.12.25).

# cat /system/bin/clrbootcount.sh
cat /system/bin/clrbootcount.sh
#!/system/bin/sh
################################################################################
##
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
#
# ls -l /system/bin/clrbootcount.sh
ls -l /system/bin/clrbootcount.sh
-rwxr-xr-x root root 338 2011-01-06 19:50 clrbootcount.sh
#

edit double post oops

I lost my backup of clrbootcount.sh
and now it won't reset the boot count.
any help would be greatly appreciated.

adb shell getprop persist.service.mount.umsauto
Click to expand...
Click to collapse
always returns 1 during and after complete reboot. The echo command for screen does not persist. Have followed your instructions super letter by letter multiple times and leading up to the reboot everything is exactly as you say.
Right now, I am most concerned that whatever I have done will not reset the boot count since it stays at 1 and does not go to 0. I've already lost my entire setup twice and had to start from scratch trying to make this work. At least I know how to reset to 0 with the line command script but how do I ensure i don't need to worry about it?
I think this process may be a bust.

I am on 1.0.0 and have been using this since I posted it and both the refresh rate and automount values are sticking between reboots.

>DARKMAN< said:
# cat /system/bin/clrbootcount.sh
cat /system/bin/clrbootcount.sh
#!/system/bin/sh
################################################################################
##
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
#
# ls -l /system/bin/clrbootcount.sh
ls -l /system/bin/clrbootcount.sh
-rwxr-xr-x root root 338 2011-01-06 19:50 clrbootcount.sh
#
Click to expand...
Click to collapse
I am assuming you are using the new method, which would mean you need to post your /data/boot_complete_hook.sh

>DARKMAN< said:
I lost my backup of clrbootcount.sh
and now it won't reset the boot count.
any help would be greatly appreciated.
Click to expand...
Click to collapse
The clrbootcount.sh file that you posted is the default file. I will post it again:
Code:
#!/system/bin/sh
##################################################################################
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
Also, the original post explains how to manually reset the boot count. Here it is:
If 0 is not printed out, something went wrong and the file will not be run properly on the next boot. If you do reboot in this state 8 times, the boot count won't be reset and you will hit the factory reset. While you are trying to get the script working, you could always manually reset the boot count by executing (from a shell):
Code:
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4

jleecong said:
Screen shot attached (1.0.1 Auto-Nooter 2.12.25).
Click to expand...
Click to collapse
It appears you are running Windows, so I am hoping that you did not use Notepad to edit this file.
Since you are running 1.0.1, post your /init.rc file.

Thought I may have been doing something wrong since I used notepad but downloaded Notepad++ and created the new .sh file. Still no go. Screen still flickers and USB still automounts. Maybe 1.0.1 just is not commpatible with this process. Only difference I can see.
The getprop persist.service.mount.umsauto also indicates 1 after full boot and not 0. Pretty sure this will wipe everything out after 8 boots, going to wipe it all out now and proactively prevent it.

[HOWTO] Root Nexus One 2.2.1 FRG83D without OEM unlock

This guide is for people who want root but want to keep their stock rom, not breaking the warranty, unlocking bootloader etc.
A proud ubuntu user, I am writing this in a new thread purely because the manual rageagainstthecage method and SuperOneClick method did not not work for me, see link to my conclusion below if you care
http://forum.xda-developers.com/showpost.php?p=11305312&postcount=2526
What did work however was via adb shell using psneuter and its fairly simple if you follow the following commands.
This guide assumes you know how to get access to the shell via adb, if you dont then search elsewhere for a useful guide
OK lets get to business!
1. Download the attached nexus_one_softroot.tar from the bottom of this post and extract contents to the same folder as adb
2. Open up your terminal, cd to the same folder as adb and the extracted files
3. Enter the following commands:
Code:
sudo ./adb push psneuter /data/local/tmp/psneuter
sudo ./adb push busybox /data/local/tmp/busybox
sudo ./adb push su /data/local/tmp/su
sudo ./adb shell chmod 755 /data/local/tmp/psneuter
sudo ./adb shell chmod 755 /data/local/tmp/busybox
sudo ./adb shell chmod 755 /data/local/tmp/su
sudo ./adb shell
After this you should see only a $ which tells us that we at the android command line with user privileges only, lets continue
Code:
$ cd /data/local/tmp
$ ls
busybox
su
psneuter
$ ./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
You will now be kicked out of android shell, lets go back in
Code:
sudo ./adb shell
After this you should see only a # which tells us that we root baby! If you want to double check issue this command
Code:
# id
uid=0(root) gid=0(root)
Lets continue on. From this point we will install busybox and su which will make root permanent
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /data/local/tmp
# ./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
# busybox cp su /system/bin
# chmod 4755 /system/bin/su
# exit
For some reason I sometimes have to enter exit twice to leave the android shell. Again, re-access the android shell
Code:
sudo ./adb shell
Now in the android shell we can finish up
Code:
# su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
# exit
Lastly we must install Superuser, and I did this from the android market so I knew its the latest version, its simple to get, less command input etc.
Now you have root! I hope this was simple enough to follow, I have not really written a guide before but from lots of searching I just could not find a solution for my Nexus One 2.2.1 FRG83D, especially any guide that uses psneuter.
Anyway, glad to contribute
EDIT - also, being new to starting threads, this may not quite be in the right section of the forum, sorry if thats the case mods

Added link to the thread from Wiki.

upgraded to gingerbread 2.3.3. after copying and setting permissions, got this:
PHP:
$ cd /data/local/tmp
$ ls -l
-rwxr-xr-x shell shell 26248 2010-07-22 10:20 su
-rwxr-xr-x shell shell 1062992 2010-10-16 22:29 busybox
-rwxr-xr-x shell shell 585731 2011-01-08 18:02 psneuter
su
busybox
psneuter
$ ./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
second time threw me out of shell. again adb shell gives this:
PHP:
$ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)

mfkr said:
upgraded to gingerbread 2.3.3. after copying and setting permissions, got this:
Code:
$ ./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
Click to expand...
Click to collapse
I believe this is due to a change in the kernel as it is upgraded into gingerbread, the input/output controls have changed, leaving psneuter out of date with the current kernel.
However if an exploit is found with the kernel used in 2.3.3, you can use it in place of psneuter with the above method.

[UTIL] SkitzBackup

The attached ZIP includes scripts for Windows and Linux to backup your Galaxy Tab.
Linux users will need to install 7zip
Code:
sudo apt-get install p7zip
May also work on OSX but you're on your own with 7zip
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Windows
Code:
skitzbackup.cmd
Linux / OSX
Code:
chmod a+x <folder where you extracted it>/skitzbackup/skitzbackup.sh
cd <folder where you extracted it>/skitzbackup
./skitzbackup.sh
The script will pull the following partitions and pack them in a 7zip archive for safe keeping:
efs
recovery
boot
system
radio
cache
misc
Before you ask, I have no idea what the 'misc' partition is. Haven't had time to explore that yet
I have NOT tested flashing these back as yet, except for boot and recovery so you use this entirely at your own risk.
DOWNLOAD HERE
View attachment skitzbackup.zip
Enjoy!

Code:
alias del=rm
mkdir skitzbackup
cd skitzbackup
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/sdcard/cache.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/sdcard/misc.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/radio.img bs=4096"
adb pull /sdcard/efs.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/cache.img
adb pull /sdcard/misc.img
adb pull /sdcard/radio.img
adb shell rm /sdcard/efs.img
adb shell rm /sdcard/recovery.img
adb shell rm /sdcard/boot.img
adb shell rm /sdcard/system.img
adb shell rm /sdcard/cache.img
adb shell rm /sdcard/misc.img
adb shell rm /sdcard/radio.img
7z a skitzbackup.7z *.img
del *.img

Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition

working perfectly!You're great

djmasque said:
Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition
Click to expand...
Click to collapse
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.

bcmobile said:
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.
Click to expand...
Click to collapse
Okay, good work nonetheless

Looks a lot like rotobackup, hehe.

Chainfire said:
Looks a lot like rotobackup, hehe.
Click to expand...
Click to collapse
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App

bcmobile said:
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App
Click to expand...
Click to collapse
Whats needed now is a kind of automated restore

bcmobile said:
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Click to expand...
Click to collapse
Sorry for the noob question but how do i do this true windows?

Will this work for me?
Hi bcmobile,
This looks excellent.
I'm currently running a P7100 (10.1v) with ISI-Galaxy 1.2.5v (HC3.2) but my baseband/modem is still P7100BUKE2.
I would like to get the GSM working (for sending USSD commands) but I would need to flash my modem, and I would like to backup the modem before I flash it with the P7500 modem.bin, if something goes wrong, I can always go back to the old one.
In your script, is radio.img the modem.bin?
Also is the "/dev/block/" always the same on all the different versions of the tablet? (in other words if I have a 10.1v will this backup my modem).
Thanks so much. You help is much appreciated.

seraphimserapis said:
Whats needed now is a kind of automated restore
Click to expand...
Click to collapse
/!\ IN THEORY /!\ you'd just have to copy the .img files back to the tab and switch the command line arguments for dd. (e.g. dd if=/path/to/file.img of=/path/to/directory)

soo i know this is kind of old but does this work for any device? if so what am i doing wrong? its stuck on deamon started successfully...

[GUIDE] ADB to Pull Images of L90

Thanks to @evoname for showing me how to do this! [emoji4]
This is if you are interested in pulling the system images for whatever reason. I'm not responsible if you brick your device. Use at your own risk!
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/abootb.img
dd if=/dev/block/mmcblk0p16 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/laf.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/system.img
exit
exit
adb pull /sdcard/aboot.img
adb pull /sdcard/abootb.img
adb pull /sdcard/boot.img
adb pull /sdcard/laf.img
adb pull /sdcard/recovery.img
adb pull /sdcard/system.img
exit
Sent from my LG-D415 using Tapatalk

[DEV] Partition backups LG G2

Here's the codes to backup your partitions on the LG G2. Probably work an any variant. I need this for future references as now it will be stored online forever!!!
Need ADB installed.
adb shell
adb su
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/tz.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
----
dd if=/dev/block/platform/msm_sdcc.1/by-name/dbi of=/sdcard/dbi.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/sdcard/sbl1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img