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?
Related
Apologies if this has been repeated but I have spent the last 30mins looking through this site and can not find a similar problem.
I am currently going through the process of overclocking my Nexus one.
I am running Cyanogen and have flashed the image file needed.
I am now trying to push the bcm4329.ko file to the system modules folder.
I have updated my USB drivers sand the phone appears to have liked that.
However when I try to perform an ADB remount command it takes a while thinking about it, tells me that "daemon is not running" and is "starting it now"
ADB server didnt ACK
* failed to start daemon *
error: can not connect to daemon.
Any suggestions as to how I can resolve this issue please?
adb kill-server
adb start-server
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...
Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App
Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.
Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.
Quick noob question everyone, if I have an unlocked bootloader and custom recovery, am I rooted? Because busybox and superuser still aren't giving me command prompts. I'm on stock ics
Sent from my HTC PH39100 using XDA
Long story short no your not rooted but you did the hard part already just follow this guide you'll be rooted in under 2 minutes http://forum.xda-developers.com/showthread.php?t=1498003
THANKS!
Sent from my HTC PH39100 using XDA
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Adb isn't set up properly or may need to ne run as administrator
Sent from my HTC PH39100 using xda premium
MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
If you could get back to stick gb, Google zergrush root. Its a tempt root for users who still have their boot loader locked. But in your case, it should be locked.
Sent from my HTC PH39100 using XDA
jigajay said:
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
Click to expand...
Click to collapse
All In One automatically reboots into recovery, runs the batch then responds with "device not found" after each command.
I did try what you said. I booted into bootloader, then ran the perm root from AIO, but got the same "device not found" result.
---------- Post added at 05:46 PM ---------- Previous post was at 05:10 PM ----------
After much reading, booting and rebooting, I managed to get this response from All In One:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
* server not running *
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
349 KB/s (22364 bytes in 0.062s)
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
4800 KB/s (843503 bytes in 0.171s)
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
However, no still no root. I've kept up to date with the AIO forum. Read the "under construction SuperGuide cover to cover. I have done exactly what many others have, except no joy for me. It appears I may have the only AT&T Vivid in the world that will not root.
http://forum.xda-developers.com/showthread.php?t=1529669
Flash that in boot loader. If it says update presses yes then you're back to gingerbread.
Sent from my HTC PH39100 using XDA
http://forum.xda-developers.com/showthread.php?t=1341162
Use that to root your phone. Follow instructions carefully.
Sent from my HTC PH39100 using XDA
Hi, I'm a newbie to android rooting and have spent the whole day trying to root my Kindle Fire HD v7.2.3.
I've used the bin4ry RunMe.bat and RootQemu.bat. I have no problems with the Qemu part but as for the RunMe.bat part I get permission problems (see picture below)
http://www.freeimagehosting.net/ikz64
The device gets rooted but the super user is no where to be seen. Therefore I can access root files but I can't write as it is read only.
I've already tried this: http://forum.xda-developers.com/showthread.php?t=2086210 (fixing a bug)
I've also tried the basics of rebooting after rooting, run as admin, locate through cmd but nothing has worked for me so far.
Anyone know what the problem is?
I was having a similar permission denied error when rooting 7.2.3. Try this and see if it helps. These commands are pulled from the Qemu script.
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
Wait for the device to reboot then run these.
Code:
adb shell rm /data/local.prop
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
reboot
Now wait for the device to reboot then check if the Qemu root hack worked correctly by connecting to your device with adb shell. You should see a root prompt.
Code:
$ adb shell
[email protected]:/ #
If you see a root prompt then re-run the RunMe.bat script and it should complete without error. The reason for your permission denied error is the script is not running as root.
I tried this frist: http://forum.xda-developers.com/lg-l90/general/guide-root-l90-varients-updates-t2928364
but the command adb reboot --bnr_recovery just only reboot the device not to recovery and nothing happens
so I tried this http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
but after all the things, in the last command adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
just nothing happens, no root installed
also tried the one click http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
seems every things work but noone root gain
look the log, seems jump some things:
Code:
Phone found at COM3!
Rooting phone...
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
##
Done!
what should I do?
the driver is from these threads, 4.1.1.0
rom 5.0.2 V20c-SCA-XXX