Related
I installed JDK and the Android SDK on this Windows XP 32bit system.
Copied the busybox, rage, root, su and Superuser.apk files into the platform-tools folder.
Connect the MT4G to the computer via USB.
The MT4G mounts as "G:\" on this Windows XP system.
Made sure USB debugging is enabled.
In the Command Prompt window:
C:\android-sdk\platform-tools> adb push su /sdcard/su
error: device not found
What did I do wrong?
Did you run "HTCDrivers.exe"? It's found on your SD card.
You should check out this this thread. It has an excellent write-up on setting up ADB as well as a much smaller installation file that makes the entire SDK unnecessary.
Can you access the contents of the SD card in windows explorer? If so you need to right click the G: and "eject". Now try it.
No, I did not install the "HTCDrivers.exe"
When I connected the MT4G to the XP system initially, it did not prompt me to do so.
Still I was able to view the G drive with Windows Explorer.
Anyway, I did install the "HTCDrivers.exe" and that took care of the "error: device not found" message. Don't see that anymore.
But now ...
...\platform-tools> adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
employee said:
But now ...
...\platform-tools> adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Click to expand...
Click to collapse
I don't recognize that command. "su" is used to initiate root access in ADB shell, but you don't 'push' su to the phone to get that root access. What exactly are you trying to do?
TeeJay3800 said:
I don't recognize that command. "su" is used to initiate root access in ADB shell, but you don't 'push' su to the phone to get that root access. What exactly are you trying to do?
Click to expand...
Click to collapse
I am trying to follow these instructions:
http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
I have already installed the Android SDK.
So ...
failed to copy 'su' to '/sdcard/su': Permission denied
... means I am stuck at step 6 under "Gaining Temporary Root Access".
Well, apparently after you connect the USB cable to XP and phone - you must select "Charging" on phone.
Once I did that it did not display the "failed to copy 'su' to '/sdcard/su': Permission denied" anymore and I am able to complete those adb commands.
employee said:
Well, apparently after you connect the USB cable to XP and phone - you must select "Charging" on phone.
Once I did that it did not display the "failed to copy 'su' to '/sdcard/su': Permission denied" anymore and I am able to complete those adb commands.
Click to expand...
Click to collapse
Glad you figured it out.
employee said:
Well, apparently after you connect the USB cable to XP and phone - you must select "Charging" on phone.
Once I did that it did not display the "failed to copy 'su' to '/sdcard/su': Permission denied" anymore and I am able to complete those adb commands.
Click to expand...
Click to collapse
LOL I was having the same problem. Switch to charging it worked like a charm. thanks mate
I just don't know if I still want CM 7.01 RC1 now. I kinda like the sense time and weather widget
Hi,
I tried for hours but cannot get OpenVPN to run or install.
I have the Blayo 0.8.4 Rom installed and know that
ifconfig is in
/system/xbin/ifconfig
and tun.ko is located in
/system/lib/modules/tun.ko
When i run the OpenVPN installer from the market it asks me where to put the files and asks for Superuser permission - but when the app wants to do the copying the phone hangs and does a reboot.
The OpenVPN Library File i used is from here (Sorry its German):
http://www.android-hilfe.de/anleitungen-fuer-motorola-milestone/28392-how-openvpn-auf-dem-milestone.html#post321528
So can anybody help me to get OpenVPN running?
I sadly cannot use the preinstalled VPN methods, because my University Wlan only supports Cisco-VPN or OpenVPN Method.
I thought it might be the problem that OpenVPN installer cannot write to the system Partition -- so i opend a local Terminal in ConnectBot and typed
aufs --enable
But there i get the Message:
Enabling Read-Write /system overlay
/data/local/dosysoverlay: Permission denied
Please reboot your phone for changes to take effect
But after a reboot the OpenVPN installer still doesn't work...
I hope someone has a idea or solution to my problem!
Thanks a lot!
Try enabling system overlay via Terminal Emulator or ADB.
Sent from my HTC Legend using XDA Premium App
You need to su to gain root privileges before executing aufs. Or use adb shell which already has root privileges.
Sent from my HTC Legend
Thanks a lot BlaYo!
I opened a local Session in ConnectBot
then i typed
su (I had to allow SuperUser Access!)
aufs --enable
And it worked!
Its me again -- the installation of OpenVPN works, but i cannot open a connection.
When i try to open the the Connection it asks for username and password,
But then it says:
cannot load ca cert /sdcard/openvpn/RRZE-ca.crt path (null)
I searched with google and found that maybe it is a permission problem, but
su
chmod 555 RRZE-ca.crt
still didn't help
chmod 777 RRZE-ca.crt
also didn't help...
i also edited the config File to
...
ca //sdcard/openvpn/RRZE-ca.crt
...
or:
ca /sdcard/openvpn/RRZE-ca.crt
or ca RRZE-ca.crt
it's alsways the same :-(
The Config files for my university's OpenVPN is here:
RRZE-ca.crt
RRZE-full-tunnel.ovpn
I appreciate every help or idea you might help!
Rename it to ca.crt and edit config file accordingly.
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
crimsontide said:
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
Click to expand...
Click to collapse
If you used BurritoRoot and you were able to successfully install the Market, then you likely have root.
Easiest and simplest way to 100% know is connect your KF to your PC. Run the following:
Code:
adb shell
su
If it says "su: Permission Denied" you don't have root (or at least it is not currently enabled). If it just gives you a prompt run:
Code:
id
If it comes back and says "uid=0(root) gid=0(root)" then you are good.
Make sure you use the superuser posted in the burritoroot post. There was one posted originally that was no good with the kindle fire but they updated to a working one.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
http://www.mediafire.com/?jj8sx4ojvq9i198
litotamez said:
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
I tried that app and it reports, "Sorry, you don't have root access."
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac devices
List of devices attached
7766000600000001 device
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell
$ su
su: permission denied
$
Looks like I have some more work to do, and I am not sure where to start.
I have installed on the KF:
BurritoRoot: Kindel Fire Edition 1.0.0
version 1.0.0
SuperUser version 3.0.6
Click to expand...
Click to collapse
Ok I went back and re-ran everything. Had to uninstall SuperUser in the middle, but things seem to be working better now!!!
HTML:
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac root
adbd is already running as root
Traveler:KindleFireRootMacLinux crimsontide$ adb push su /system/xbin/su
-bash: adb: command not found
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac push su /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chown 0.0 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chmod 06755 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
4426 KB/s (785801 bytes in 0.173s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
2858 KB/s (785801 bytes in 0.268s)
pkg: /data/local/tmp/Superuser.apk
Success
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac reboot
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
adb shell mount is not allowed
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
renamedresfile said:
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
adb shell mount is not allowed
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
Click to expand...
Click to collapse
You should be able to mount the system r/w with the proper command, hopefully someone will be here soon to give you the commands.
do you have fff & twrp available ?
if yes boot to twrp - there you have full adb availabe and you can copy your backup framework-res to the kf
same thing happened to me,but I made it worse and the computer wouldn't even detect the KF.I had to return it.
Sorry): I know how it feels
renamedresfile said:
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
adb shell mount is not allowed
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
Click to expand...
Click to collapse
Try using 'adb remount' then try to rename it again.
if you get the 'Read-only file system' error again:
adb reboot
adb remount
try again
Sent from my Kindle Fire using xda premium
Hi all!
I've run into the problem in the title and solved it, so I thought I'll share my experiences.
1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:
Samsung Accessory service:
https://play.google.com/store/apps/details?id=com.samsung.accessory
Galaxy Watch plugin:
https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin
Galaxy Wearable:
https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager
The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)
2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one
To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.
To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:
/system/build.prop
/system/vendor/build.prop
/system/vendor/odm/etc/build.prop
You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.
You can now "download" and "upload" build.props. Between adb pull and adb push, you need to edit the downloaded build.prop like I wrote above.
Code:
adb pull /system/build.prop
adb push build.prop /system
adb pull /system/vendor/build.prop
adb push build.prop /system/vendor
adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc
EDIT: on lineageos 18 you need to edit two more files:
Code:
adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop
adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop
Restart into system after this.
The 3(5) build.prop edit will do the work and Galaxy Wearables will start and you can connect your watch.
Important info again after every OTA or manual LineageOS update, you need to edit build.props to continue using your watch (watch won't connect after OS update at all, without build.prop edits)
liquidraver said:
Hi all!
I've run into the problem in the title and solved it, so I thought I'll share my experiences.
1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:
Samsung Accessory service:
https://play.google.com/store/apps/details?id=com.samsung.accessory
Galaxy Watch plugin:
https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin
Galaxy Wearable:
https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager
The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)
2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one
To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.
To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:
/system/build.prop
/system/vendor/build.prop
/system/vendor/odm/etc/build.prop
You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.
You can now "download" and "upload" build.props. Between adb pull and adb push, you need to edit the downloaded build.prop like I wrote above.
Code:
adb pull /system/build.prop
adb push build.prop /system
adb pull /system/vendor/build.prop
adb push build.prop /system/vendor
adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc
EDIT: on lineageos 18 you need to edit two more files:
Code:
adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop
adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop
Restart into system after this.
The 3(5) build.prop edit will do the work and Galaxy Wearables will start and you can connect your watch.
Important info again after every OTA or manual LineageOS update, you need to edit build.props to continue using your watch (watch won't connect after OS update at all, without build.prop edits)
Click to expand...
Click to collapse
Fantastic. I just installed LineageOS 18.1 on my Tab A6 and I Galaxy Wearable app didn't want to work but thanks to your post I managed to get it fixed. Great work. Thanks
Thx, works perfectly on a Galaxy S5 (klte) with LineageOS/eOS based on Android 11 with Magisk-Root.
liquidraver said:
Hi all!
I've run into the problem in the title and solved it, so I thought I'll share my experiences.
1, First of all, you need 3 apps to successfully connect and use a galaxy watch and here comes the first problem:
Samsung Accessory service:
https://play.google.com/store/apps/details?id=com.samsung.accessory
Galaxy Watch plugin:
https://play.google.com/store/apps/details?id=com.samsung.android.geargplugin
Galaxy Wearable:
https://play.google.com/store/apps/details?id=com.samsung.android.app.watchmanager
The last one is installable on a lineageos with google apps, but the first two is not. You can hunt down the apk-s yourselves, but you need to install them by hand (I'll uploaded the latest ones on my androidfilehost, but not sure about linking them here, so... if you can find them...)
2, The second problem comes after you installed everything... Galaxy Wearable won't start because you modified your operating system. It's right, you modified... installed a brand new one
To solve your second problem, you need to edit the build.prop in the device's /system folder (/system/build.prop) - and important --> on android 10 (LineageOS 17.1) you need to edit in two more folders.
To summarize, edit build.prop and replace every "samsung" text with anything else (I use HTC or some other name) in the following places:
/system/build.prop
/system/vendor/build.prop
/system/vendor/odm/etc/build.prop
You can connect your phone with TWRP recovery booted, go into Mount section and tick System to mount system partition.
Sie können jetzt build.props "herunterladen" und "hochladen". Zwischen adb pull und adb push müssen Sie die heruntergeladene build.prop bearbeiten, wie ich oben geschrieben habe.
Code:
adb pull /system/build.prop
adb push build.prop /system
adb pull /system/vendor/build.prop
adb push build.prop /system/vendor
adb pull /system/vendor/odm/etc/build.prop
adb push build.prop /system/vendor/odm/etc
BEARBEITEN: Auf Lineageos 18 müssen Sie zwei weitere Dateien bearbeiten:
Code:
adb pull /system/product/build.prop
adb push build.prop /system/product/build.prop
adb pull /system/system_ext/build.prop
adb push build.prop /system/system_ext/build.prop
Starten Sie danach das System neu.
Die Bearbeitung von 3(5) build.prop erledigt die Arbeit und Galaxy Wearables wird gestartet und Sie können Ihre Uhr anschließen.
Nochmals wichtige Informationen: Nach jedem OTA- oder manuellen LineageOS-Update müssen Sie build.props bearbeiten, um Ihre Uhr weiterhin verwenden zu können (die Uhr stellt nach dem Betriebssystem-Update überhaupt keine Verbindung her, ohne build.prop-Bearbeitungen)
Click to expand...
Click to collapse
gilt das auch für 19.1
Bernd1712 said:
gilt das auch für 19.1
Click to expand...
Click to collapse
this also applies to
Hi, everytime when i wanted to push the changed build.prop file to system/vendor/odm/etc adb says :
adb: error: stat failed when trying to push to /system/vendor/odm/etc: Not a directory
But the build.props from the other directories work. Can someone help me? And sorry for my english...
Thanks
Edit: I'm using an S5 klte with official Lineage 18.1