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.

[Q] Booting to recovery with ADB

Good morning guys,
I potentially have a couple of hundred of these to update with an AOSP ROM. I dont have any problems with the update, all smooth sailing, but I'm trying to script as much as possible to automated the process - Unlock bootloader, get root, push all the files then install the ROM.
For some reason though the command 'adb reboot recovery' doesn't work as expected. It just reboots the phone back to the normal OS.
Has anyone else encountered this? or a work around?
I can issue 'adb reboot-bootloader' and it will reboot into the bootloader correctly where I can issue fastboot commands but not to the recovery (Which is CWM latest as of today, which I think is 6.1.1?)
Thanks in advance!

Code:
adb shell
su
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
reboot / reboot recovery

Adam77Root said:
Code:
adb shell
su
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
reboot / reboot recovery
Click to expand...
Click to collapse
Your a genius.
As a side note this didn't require root access.

Adam77Root said:
Code:
adb shell
su
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
reboot / reboot recovery
Click to expand...
Click to collapse
Maybe you can help me out a little futher. What I'm trying to do is automate the superuser install.
From the look of that, is that writing to one of the recovery commands located under /cache/recovery ? Perhaps the command file?
If it is or not, perhaps you know of a way to write the /cache/recover/command file to run an update ZIP immediately on rebooting into the recovery? My reading seems to be going in circles.
From my reading what I would need to do is:
* Copy the superuser.zip to the sdcard
* write 'boot-recovery' to 'a' file as you mentioned above
* write '--update_package=/sdcard/superuser.zip' to the file /cache/recovery/command
Obviously without root already I cant just write to that file so I thought it might be possible to use 'dd' as above?
Then rebooting into recovery should automatically run the update zip? Or am I mad?

You do need root to write into the command file. 'dd' tool also needs root.

(SOLVED)--Require of sim unlock ...how to carry out instruction

------------------------------------SOLVED---------------------------------------------------------------------
JUST CARRIED OUT THE COMMANDS IN CWM RECOVERY ....THAT SOLVED ALL PROBLEMS
I have htc j one ...japanese htc one
Hboot is 1.52 and android 4.1.2
I have been able to s off, unlock bootloader using revone
I have flash cwm and rooted phone
Now I need to sim unlock the phone with some adb commands given in the below mentioned website :-
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
You can easily auto translate the above page if u open it in google chrome
Can anyone help me with that ?
Thanks in advance
Sent from my GT-N7000 using xda premium

download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps

criszz said:
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
Click to expand...
Click to collapse
Thanks for replying
I will download this file and put in adb folder
I shud do
adb push misc.img
( is this commabd correct or do I need to to put / ar back)
Then
Adb shell
It shows $ at the end
So it type
Su
Now it becomes #
Then I shud type
dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
Am I correct ?
Plz help as I am noob in this ...but am trying to learn
Sent from my GT-N7000 using xda premium

The auto-translated instructions are not good enough, and this is a very risky procedure. Fortunately, with code you usually don't need to read the words to understand it. Fortunately, with my Japanese-speaking colleague's help, I understand everything. Some things to know:
- Don't try this unless you are content to risk your phone, because I can tell he made mistakes in his instructions
- To reiterate, you either need to follow his incorrect instructions or you need to listen to me (why would you do that?)
- Look at the code blocks--all that code is meant to be run on your computer while the phone is connected to USB.
- There is only one complicated step, and this is the one with the incorrect instructions.
What he says:
Open misc.img in a hex editor, represent [00001023] as [11] and save. If you are lazy, use the file I modified already. <link>
There are two problems with this statement. First, "00001023" is not a reasonable position in the file. It means "line 10, column 3" (lines start with zero, columns start with zero). But there are 16 bytes per line, so what he really means is "byte 147". (Each pair of hex characters is a byte. The lowest value is 00, the highest value is ff.)
The second problem is that in his "already modified" file, that byte is "00", not "11". This is what I expected, because it's not reasonable for number="11" to mean "unlocked". More likely, "11" is his carrier and "00" is when the phone is unlocked.
What I advise is getting your carrier to unlock the phone, and if that's not possible, proceed only if you are willing to risk your phone. Follow his instructions, but when you get your misc.img file, download his modified version and compare them. If they differ in only one position, install his file to your phone (as per the instructions). If they are very different but the same size, you can try changing byte 147 to 00 (if the surrounding bytes are also all 00). Save the unmodified .img file, because you might be able to use it to rescue your phone if this fails.
Note: this is risky, with or without language barrier issues. At least 10% chance of bricking your phone.

Thanks a lot for your advice.
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Currently am stuck ...
Sent from my GT-N7000 using xda premium

sitanshu91 said:
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Click to expand...
Click to collapse
I think it's probably safe to flash the misc.img file he uploaded and linked to, if (and only if) it is exactly the same as yours, except for that one byte. Low chance of bricking the phone.

But currently can you tell me to how to pull the image coz I havr followed his command ...
Adb shell
It strt with $
Su
Now # come
Then somd dd comand
Here it shows operation cannot complete(will update what is exactly error in few min)
Exit
Adb pull misc.img
Here it shows error device not detected
Can you help me to first pull file so I can compare
Sent from my GT-N7000 using xda premium

Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?

fenstre said:
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
Click to expand...
Click to collapse
see this is what i get
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ #
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
requesting your help
thanks

sitanshu91 said:
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
Click to expand...
Click to collapse
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)

fenstre said:
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
Click to expand...
Click to collapse
so you say i should proceed
see again i did the same
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT35Z******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ # exit
exit
1|[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
now how should i proceed ....please help

Guys requesting help before the new year starts
So I can use my phone in new year
Sent from my GT-N7000 using xda premium

sitanshu91 said:
/misc.img: cannot open for write: Read-only file system
Click to expand...
Click to collapse
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?

Kasi!995 said:
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Click to expand...
Click to collapse
yes this is unlocked bootloader ...i have done it thru revone
now i have installed busybox
and i can progress
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT3******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks

sitanshu91 said:
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
Click to expand...
Click to collapse
what Recovery do you have flashed? TWRP?

Its cwm recovery
Sent from my GT-N7000 using xda premium

Run adb pull outside of adb shell.

1st problem :-
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you tell me where is my mistake
What can I do can you type command
2nd problem
similiarly when i try
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb push misc.img /
failed to copy 'misc.img' to '//misc.img': Permission denied
request you to please help me
thanks and regards
Sent from my GT-N7000 using xda premium

what is your status now?

criszz said:
what is your status now?
Click to expand...
Click to collapse
i am very glad that you asked .....happy new year
Now my status is sim unlocked ....but i can use only to make and receive phone calls and sms ...
now here is the problem
i cant use data (2g/3g) on my phone
do u know how to do that
thanks
sitanshu

cant remove TAMPERED HELPPP

hlo...... I used command method to remove tampered and it was gone at first but when I unlocked bootloader using command tampered came again and now it is not going with revine,guru bootloader......helppppp

jaspreet4140 said:
hlo...... I used command method to remove tampered and it was gone at first but when I unlocked bootloader using command tampered came again and now it is not going with revine,guru bootloader......helppppp
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2477792

helpp
hy nykk again.......thx for reply......but I used this method at first only ....now this also not working...
now I got more big trouble...
I m only s-off and bootloader is relocked and have no root so can't flash any recovery......
I I tried unlock_bin token cmd says sending token(0 bytes) successful but bootloader do not show anything........what should I do noww...

jaspreet4140 said:
hy nykk again.......thx for reply......but I used this method at first only ....now this also not working...
now I got more big trouble...
I m only s-off and bootloader is relocked and have no root so can't flash any recovery......
I I tried unlock_bin token cmd says sending token(0 bytes) successful but bootloader do not show anything........what should I do noww...
Click to expand...
Click to collapse
okay, but first, can you please relax!!
after you relax, please post your current "fastboot getvar all" (excluding IMEI and s/n), and if you are S-Off, we'll have you unlocked pretty quickly
but you have to relax!! otherwise you're going to rush things and make a mistake.

re
bootloader 1.54.0000
baseband. 4A.17.3250.14
cpld: none
microp:none
main:2.24.980.3
pvt ship s-off
meid:00000000000000
product:m7_ul
HBOOT-8064
midN0714000
cid:11111111
securityff

jaspreet4140 said:
bootloader 1.54.0000
baseband. 4A.17.3250.14
cpld: none
microp:none
main:2.24.980.3
pvt ship s-off
meid:00000000000000
product:m7_ul
HBOOT-8064
midN0714000
cid:11111111
securityff
Click to expand...
Click to collapse
1- that's not a copy/paste you typed that stuff ... (see screenshot for copy/paste on windows)
2- are you relaxed now?
3- next time, please quote me, or mention me using @nkk71 to get my attention, otherwise I may not read the post
4- are you relaxed now
5- to get unlocked:
Since you are S-Off, use a custom recovery masked in a firwmare package: you can use of these "firmware" packages (m7_u/ul only):
http://www.androidfilehost.com/?w=files&flid=13085
fastboot oem rebootRUU
fastboot flash zip fw_m7ul_TWRP_2.6.3.3_1.26.401.33.zip
fastboot reboot-bootloader
-> enter RECOVERY (should be TWRP or CWM now)
and use @scotty1223's commands in custom recovery http://forum.xda-developers.com/showthread.php?t=2475914 to unlock bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
[SIZE="1"][I][U]Note[/U]
CWM shell prompt usually looks like [B]~#[/B]
TWRP shell prompt usually looks like [B]~ # ←[6n[/B]
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue
[/I][/SIZE]
[I][SIZE="1"]Setting UNLOCKED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/COLOR][/B]
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
^^ if this doesn't work in your particular version, just select reboot to bootloader in TWRP.
ps: your version-main will now say 1.26.401.33 (reflecting the recovery version 2.6.3.3); it didn't actually change, but version-main always show the last thing flashed in ruu mode.
6- careful on what you flash/install etc. you're doing quite a few mistakes... and rushing things.... so please be careful!!
.

re
ya I m relaxed......thx for concern....
but I can't download ur files using pc.....how to download them I enabled javascript also using mozilla

tnxx
ok done...thxxx nkk71 again greate helpp.........

ree
nkk71 now everything is back to normal except a small thing....TAMPERED is not going I used scotty command ,revone tool and guru bootloader ...none is helpful......others are working good I.e I m able to relock ,unlock,lock bootloader but not tampered.........it worked at first time but when I unlocked it came again n now its not going.....
can u get ur magic sword on this one

jaspreet4140 said:
nkk71 now everything is back to normal except a small thing....TAMPERED is not going I used scotty command ,revone tool and guru bootloader ...none is helpful......others are working good I.e I m able to relock ,unlock,lock bootloader but not tampered.........it worked at first time but when I unlocked it came again n now its not going.....
can u get ur magic sword on this one
Click to expand...
Click to collapse
you need to use @nkk71 (ie @ then nkk71, no spaces) not just nkk71 for me to get notified
and scotty's command should work just fine, maybe you're mistyping them or not in su mode? reboot to custom recovery, then
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
[SIZE="1"][I][U]Note[/U]
CWM shell prompt usually looks like [B]~#[/B]
TWRP shell prompt usually looks like [B]~ # ←[6n[/B]
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue
[/I][/SIZE]
[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
^^ if this doesn't work in your particular version, just select reboot to bootloader in TWRP.
copy/paste (no screenshot, a real copy/paste please) your command prompt output (all of it) if it still fails.
PS: oh and is it going, but coming back or just not going away?
.

rom
can anyone suggest me a latest non sense based ROM for htc one which has some cool features like multi tasking ,double tap or slide up unlock.......

sorry for late replying @nkk71 .my exams were going on..........and tampered was gone for first time only and now it: s not going and I m using scotty cmd with su mode in usb debugging...

jaspreet4140 said:
sorry for late replying @nkk71 .my exams were going on..........and tampered was gone for first time only and now it: s not going and I m using scotty cmd with su mode in usb debugging...
Click to expand...
Click to collapse
try the commands while booted into custom recovery (and there's no need to 'su' in custom recovery as it already should give you a root shell:
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
[SIZE="1"][I][U]Note[/U]
CWM shell prompt usually looks like [B]~#[/B]
TWRP shell prompt usually looks like [B]~ # ←[6n[/B]
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue
[/I][/SIZE]
[I][SIZE="1"]Resetting TAMPERED[/SIZE][/I]
~ # [B][COLOR="Blue"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988[/COLOR][/B]
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes (1B) copied, 0.009370 seconds, 106B/s
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
^^ if this doesn't work in your particular version, just select reboot to bootloader in TWRP.
remember to copy/paste that command, even something as small as an extra/missing <space>, can make it not work.
if it still doesn't work, you'll have to do as @scotty1223 mentioned in his thread (under the section "if this does not work for you"): http://forum.xda-developers.com/showthread.php?t=2477792
don't just say it doesn't work, you need to provide him with:
1) a copy/paste of "fastboot getvar all"
2) a copy/paste of your command prompt output
3) your mmcblk0p7
though I don't think I've ever seen a post that said this doesn't work (unless the command is mistyped)
.

HTC Butterfly S 9060 easy unlock bootloader(no need of htcDev)

hey gus i have unlocked my 9060 by this method and its pretty easy(Thanks to its creators).........and the best part is that u dont have lose any data from ur phone .................(ur device must be S-off)
this method is imported from my old phone desire 601 ..........credit:
@scotty1223 thanks
u just have to do this .......
first go to this site and do as he say...... and install the adb to ur pc.........credit goes to @Snoop05
and then just open this (adb.zip) and download it ......
extract it to short path like:--- C:\.
now open the command prompt where u have extracted (press the left shift in that extracted folder and right click and click open command prompt) or locate to the folder
Now u just have to unlock ......
type adb shell (in the command prompt)
type su
type or paste echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
****i advice copy and past****
type exit
type exit
type adb reboot bootloader (for checking its position *****unlocked***** )
type fastboot reboot ( to back in os)

hey @rajat ,can u give me the stock systemUI.apk 4.2.2 9060 ,,,,,it's urgent....thanks in advance

thanks for the new method. can i try this with my htc one m7?

goodman_east said:
thanks for the new method. can i try this with my htc one m7?
Click to expand...
Click to collapse
u can but u have to change this line only the main code.........................
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
cause m7 memory partition is different from zara
else is same .............and btw what m7 u have is it china 802t.............

Good
goodman_east said:
thanks for the new method. can i try this with my htc one m7?
Click to expand...
Click to collapse
Great job

rajat836 said:
hey gus i have unlocked my 9060 by this method and its pretty easy(Thanks to its creators).........and the best part is that u dont have lose any data from ur phone .................(ur device must be S-off)
this method is imported from my old phone desire 601 ..........credit:
@scotty1223 thanks
u just have to do this .......
first go to this site and do as he say...... and install the adb to ur pc.........credit goes to @Snoop05
and then just open this (adb.zip) and download it ......
extract it to short path like:--- C:\.
now open the command prompt where u have extracted (press the left shift in that extracted folder and right click and click open command prompt) or locate to the folder
Now u just have to unlock ......
type adb shell (in the command prompt)
type su
type or paste echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
****i advice copy and past****
type exit
type exit
type adb reboot bootloader (for checking its position *****unlocked***** )
type fastboot reboot ( to back in os)
Click to expand...
Click to collapse
What is the use unlock ?
How I can make the S - OFF?
Thanks for the input.