Database Develop

[Q] unable to root my tattoo whit one click

when i try i got this messege in the log, it looks lige the program is unable to access my system folder on the device.
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
329 KB/s (5392 bytes in 0.016s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock3
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Out of memory[/COLOR]
OK
Pushing superuser.apk...
failed to copy 'superuser.apk' to '/system/app/superuser.apk': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
THREAD CLOSED
ask ur question in the Q & A Thread or the 1 click thread

kongen1280 said:
when i try i got this messege in the log, it looks lige the program is unable to access my system folder on the device.
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
329 KB/s (5392 bytes in 0.016s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock3
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Out of memory[/COLOR]
OK
Pushing superuser.apk...
failed to copy 'superuser.apk' to '/system/app/superuser.apk': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
Click to expand...
Click to collapse
Try rooting with the unrevoked setting

howabout try use the "1-click" instead of fiddeling with ADB?
http://forum.xda-developers.com/showthread.php?t=761507

V8 rooted but no CWM

I was on v8 non-rooted.
I followed the instructions here to the letter:
http://forum.xda-developers.com/showthread.php?t=1566729&page=4
didn't have any issues at all, no errors.
I'm confirmed on V8 and do have root but can't access CWM. Attempting to run the new AIO again gives the following:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: Read-only file system
7781 KB/s (5345280 bytes in 0.670s)
Unable to chmod /system/xbin/busybox: Read-only file system
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
Any ideas how to get to CWM?

Looks like you need to root again after your upgrade. Run MT's Root&RecoveryAIO.bat again and select the "Root ZV8" option.
[EDIT]
My bad. That's what you are trying to do! I've been up all night and am tired. Did you get any errors when you ran the "Prepare for Update" option before you upgraded? That option actually pushes the superuser files back to your phone and the "Root ZV8" option just goes back and set's the permissions. You can try manually running these commands with adb first.
Files\adb push Files\zergrush /data/local/tmp/zergrush
Files\adb shell "chmod 755 /data/local/tmp/zergrush"

[Q] Can't S-off !!!

I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me

What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium

jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
sharkman3d said:
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^ What he said!!!!!!!! ^^^^^^^^^^^^^^^^
More information please.

Sorry I'm on 2.01.0001

What error did you get?

jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?

I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)

InsertDumbNick said:
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
Click to expand...
Click to collapse
Yes, it was the first i tried...

Is the RUU you have the correct one for your region? The fact you are choosing not to make a goldcard could be having an effect.

Type this command into cmd while your phone is in fastboot mode 'fastboot oem lock'. I did that before I run the process.
Sent from my HTC Incredible S using xda premium

jules290496 said:
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
Click to expand...
Click to collapse
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.

tpbklake said:
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
Click to expand...
Click to collapse
No, i don't see any # and i tried whith and without goldcard

jules290496 said:
No, i don't see any # and i tried whith and without goldcard
Click to expand...
Click to collapse
Yeah, the whole key to the script is getting temp root access so that the mainver can be modified to 2.00.0000.
If that doesn't work, the whole goldcard and RUU thing will not work.
The best thing you could try is to open a command window and try manually typing the commands in and post the command window to help isolate the issue.

I think i will give up, thanks anyway

jules290496 said:
I think i will give up, thanks anyway
Click to expand...
Click to collapse
You have a custom recovery installed?

No, i don't now how to do it without revolutionary...

jules290496 said:
No, i don't now how to do it without revolutionary...
Click to expand...
Click to collapse
So the phone is completely stock, just unlocked bootloader?

Yes it's completely stock

jules290496 said:
Yes it's completely stock
Click to expand...
Click to collapse
Try locking the bootloader and doing a factory reset. Boot into recovery once, turn fastboot off and USB debugging on and run the newest version (3.2) of the script again.

Ok, i will try

(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

Andyroid Su Problems

I am trying to root Andy 47.0.1096, but am having some problems. I tried using the andyroot, but obviously doesn't work because it's not for Nougat.
I managed to find this guide and manually flash root, but it will not run the daemon when I start andyroid.
I have to manually run command, in CMD, to get daemon to work so the supersu can grant access to xposed.
Code:
adb shell /system/bin/su --daemon&
How can I make it so the daemon is running on it's own and me not having to run the command every time I want to use Andy?