Dear
When i rooting the htc tattoo following problem are appear ;-
adb server is out of date. Killing....
Daemon is started sucessfully
i solve this problem but another problem appear:-
when i go to this line: adb push su /data/local/bin/ and hit enter line appear:
adb push su /data/local/bin/
adb not found
pls solve my problem
Pls solve my problem
Thanks
Related
So i am modding my own widgetlocker for the first time and would like to push it back into my device.
See screenshot first.
and i am using clockworkmod recovery 2.5.0.1.
Problem, as you can see, i think i've successfully push it right? but when i reboot why i still cant see the app?
and for adb shell, when i entered that, yes it passed, then when i entered "su" , it says not found. why is it?
i tried installing but got the error as you see in screens.
adb remount, failed? why?
You are using adb wrong!
For pushing you have to use this template:
"adb push *file* *directory*"
e.g.: (without quotes)
"adb push com.teslacoilsw.widgetlocker-1.apk system/app/"
not:
"adb push com.teslacoilsw.widgetlocker-1.apk /system/app/com.teslacoilsw.widgetlocker-1.apk"
Also make sure, that your SDK is installed correctly, because you used "adb install" correctly, but it gives you an error.
I hope it can help you, had got the same issues..
Hi mate, thanks for the reply. I got it working just before you posted.
this is what i did.
1) adb remount (i did it first and it succeeded! yay!)
2) adb push (still using the same template as i did)
but still very much thanks for replying. will keep your info in mind!
yay my first adb!
cool that you figured it out!
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
- the app does not give you a root option - it only guides you what to do
- have you followed all steps ?
adb shell chmod 777 /data/local/tmp
adb install BurritoRoot3.apk
<go open the app now>
adb shell /data/local/tmp/BurritoRoot3.bin --root
adb shell /data/local/tmp/BurritoRoot3.bin --install
maybe you have to do the adb commands with ./ in front (eg ./adb whatever)
t4nn3d1n said:
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
Click to expand...
Click to collapse
You have to make sure that you do this command:
adb shell chmod 777 /data/local/tmp
Otherwise it will not make a "BurritoRoot3.bin" file, which means no root.
Install the BurritoRoot3.apk on your kindle, and go into the app.
After that is finished, input:
adb shell /data/local/tmp/BurritoRoot3.bin --root
Then:
adb shell /data/local/tmp/BurritoRoot3.bin --install
I found http://forum.xda-developers.com/showthread.php?t=1410223 which has that chmod command in it. Naturally I found that thread 10 minutes after I posted and was so dumbstruck with myself that I didn't post a reply to my own post.
The device is rooted now and I installed the Alpha Release of MIUI 4.0.? and naturally a few things don't work. Trying again with MIUI's 2.3 stable release (don't know the version number off the top of my head)
Thanks for the quick reply and looking out
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!
Hey guys!
I'm tearing out my hair over this. My NP has bootloader unlocked and is rooted.
I've been sitting a few hours just to install CM-12.1 on my NP... but it won't work!
I can see that my NP is connected when I type:
Code:
adb devices
I push using this command:
Code:
adb push cm-12.1-20150830-NIGHTLY-fugu.zip /sdcard/cm-12.1-20150830-NIGHTLY-fugu.zip
I also tried:
Code:
adb push cm-12.1-20150830-NIGHTLY-fugu.zip /sdcard/
It succeeds in pushing the file, because I can see it when I type:
Code:
adb shell ls /sdcard/
But when I choose install from internal storage in Cyanogen Recovery, the file does not show up! I've tried it over and over again for hours.
Am I doing something wrong?
Fixed it myself.
Thanks for the help everyone!!!
Hi, "adb shell reboot disemmcwp" doesnt work for me on 2017G 7.1.1 (B05).
Some weeks ago i used a different command that worked. But i cant remember this command and cant find it anymore via google.
Does anyone know which command it is?!
thanks.
It depends on where you're doing this at. Are you using CMD or terminal on the phone?
nolimit78 said:
Are you using CMD or terminal on the phone?
Click to expand...
Click to collapse
cmd as admin and also with terminal (root).
Spillunke said:
cmd as admin and also with terminal (root).
Click to expand...
Click to collapse
I just used 'adb reboot disemmcwp' and it worked.
This command doesnt work for me.
No effect with CMD or terminal. There is an other similar command that works.
EDIT: im not sure, but is it maybe a problem of magisk? I use Magisk, not SuperSu. Would it work with SuperSu?
PUSH
Spillunke said:
PUSH
Click to expand...
Click to collapse
Did you try it? What was the error? Its very bad practise to just say "it did not work".
After booting up, i cant deinstall system apps for example.
Now i switched to an other stock rom and now i can deinstall systemapps, but there are still problems: cant delete files in system/ but this seems to be an magisk based issue.
Spillunke said:
After booting up, i cant deinstall system apps for example.
Now i switched to an other stock rom and now i can deinstall systemapps, but there are still problems: cant delete files in system/ but this seems to be an magisk based issue.
Click to expand...
Click to collapse
try mount -o rw,remount,rw /system (as root)
if that doesnt work, try this in terminal in twrp.
Zobat said:
try mount -o rw,remount,rw /system (as root)
if that doesnt work, try this in terminal in twrp.
Click to expand...
Click to collapse
All in one line or are this 3 single commands?
hi guys.
this simple process is so hard for me but somehow i managed to reboot disemmcwp
i learned that my ZTE HSUSB driver not properly installed (check through you device manager).
after properly installed it, i manage to pair with my laptop
before
C:\adb>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
after
C:\adb>adb shell
[email protected]:/ $
so just type
C:\adb>adb shell
[email protected]:/ $ reboot disemmcwp
colmanjr said:
hi guys.
this simple process is so hard for me but somehow i managed to reboot disemmcwp
i learned that my ZTE HSUSB driver not properly installed (check through you device manager).
after properly installed it, i manage to pair with my laptop
before
C:\adb>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
after
C:\adb>adb shell
[email protected]:/ $
so just type
C:\adb>adb shell
[email protected]:/ $ reboot disemmcwp
Click to expand...
Click to collapse
msm8974? you sure you have an axon7?