Related
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
mbze430 said:
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
Click to expand...
Click to collapse
Here ya go
oh ok lol thank u i found it dugh
silver03wrx said:
im trying to do this i keep getting the message the process cannot access the file because it is being used by another process?. i did adb kill-server then adb start server it started then i typed in adb logcat -d *:E > dump.txt. and i can not find the dang text file on my sd card lol sorry have not used adb much
Click to expand...
Click to collapse
the text file will be located in the directory where you ran the command from and not in the sdcard or in the phone
ok thanks bud here ya go
Attached my dump file.
I may need to google some of the crap that was in it.
Hi, i have ICS for HTC Desire (Bravo), Android 4.0.4 and my problem when i start Terminal Emulator, i type "su" and i get # (superuser permissions) and when i type "adb uninstall package" i get message from terminal "waiting for device" and i dont know what to do
I need to uninstal com.android.vending
Thx for help
t0msk said:
Hi, i have ICS for HTC Desire (Bravo), Android 4.0.4 and my problem when i start Terminal Emulator, i type "su" and i get # (superuser permissions) and when i type "adb uninstall package" i get message from terminal "waiting for device" and i dont know what to do
I need to uninstal com.android.vending
Thx for help
Click to expand...
Click to collapse
This has nothing to do with Terminal Emulator, it's working fine ->
adb stands for android debug bridge, it's meant to be a way to do stuff with your android device from your computer over the "bridge" that is USB. It says "waiting for device" because it needs a USB android device to be connected. As far as I know, even with OTG you can't use adb actually on an android device itself with Terminal Emulator. If all you want to do is uninstall an app, you shouldn't need adb anyway.
Read here.
HTCDreamOn said:
This has nothing to do with Terminal Emulator, it's working fine ->
adb stands for android debug bridge, it's meant to be a way to do stuff with your android device from your computer over the "bridge" that is USB. It says "waiting for device" because it needs a USB android device to be connected. As far as I know, even with OTG you can't use adb actually on an android device itself with Terminal Emulator. If all you want to do is uninstall an app, you shouldn't need adb anyway.
Read here.
Click to expand...
Click to collapse
I tried use adb through cmd in windows but its waiting too (adb through cmd is working only in recovery)
So how can i uninstall system app?
Screenshot is in attachments, i can disable it, but i need to uninstall it, because here is thread: http://forum.xda-developers.com/showthread.php?t=1355660&page=1662
Originally Posted by rfandango View Post
Download: Vending-3.8.15.noupdate.norestrictions.apk - google it - rename to Vending.apk, with root explorer move it to system app and set perm to rw r r...reboot...work like a charm
Unfortunately, this isn't working for me - still no play store, but there's an entry for com.android.vending in Manage Apps with a grey icon (generic app icon with a little SD card in the bottom right corner) and a size of 0.00b. Anyone know what I missed?
Click to expand...
Click to collapse
Edit: Fixed it! Needed to do "adb uninstall com.android.vending" and then reboot. The store is back now.
Click to expand...
Click to collapse
Any idea?
Because i dont have Play Store so i cant do anything
t0msk said:
Any idea?
Because i dont have Play Store so i cant do anything
Click to expand...
Click to collapse
Try run the following in Terminal Emulator:
Code:
pm uninstall com.android.vending
* You must find out the vending apk and delete it first (If the apk exists and is a system app).
codelover said:
Try run the following in Terminal Emulator:
Code:
pm uninstall com.android.vending
* You must find out the vending apk and delete it first (If the apk exists and is a system app).
Click to expand...
Click to collapse
i got "Failure"
I made new screenshot and i found that when i type "adb devices" in Terminal Emulator i get blank page, you can see it in the screenshot
t0msk said:
I made new screenshot and i found that when i type "adb devices" in Terminal Emulator i get blank page, you can see it in the screenshot
Click to expand...
Click to collapse
As mentioned by @HTCDreamOn, adb is for you to run commands from Windows and since you are working with Terminal Emulator you do not need to deal with adb related command.
Also mentioned earlier that you MUST manually delete the apk first before you can uninstall the app if it is a system app.
To do that first find out where the vending apk located. assumed that you have busybox/grep installed, run the following in Terminal Emulator:
pm list packages -f | grep vending
You should get something like this:
package:/system/app/vending.apk=com.android.vending
Click to expand...
Click to collapse
* Actual filename & path may vary depending on device
Now that you know where the apk is, eg: /system, mount the /system rw and delete the vending.apk manually.
Then you can proceed to uninstall using the following command:
pm uninstall com.android.vending
Success :laugh:
Thx!
I dont want to make new thread so my another question is why i cant go to ini.d folder when its exists?
Look at my screenshot
//EDIT: SOLVED
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
cronikman84 said:
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
Click to expand...
Click to collapse
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
cronikman84 said:
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
Click to expand...
Click to collapse
Never mind LMAO...i got it :victory:
cronikman84 said:
Never mind LMAO...i got it :victory:
Click to expand...
Click to collapse
How'd you get it?! I'm stuck here too, thanks!
thanamesjames said:
How'd you get it?! I'm stuck here too, thanks!
Click to expand...
Click to collapse
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
cronikman84 said:
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
Click to expand...
Click to collapse
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
diazamet said:
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
Click to expand...
Click to collapse
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
cronikman84 said:
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
Click to expand...
Click to collapse
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
diazamet said:
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
Click to expand...
Click to collapse
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
cronikman84 said:
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
Click to expand...
Click to collapse
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
diazamet said:
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
Click to expand...
Click to collapse
Sweet!!...glad you got it fixed... I knew that the native SU was crippled the first time i tried it...that's why i tried the OUYA toolbox cause i knew people had success with SU on that toolbox, so i gave it a try and SU was workin...tha's how i knew something was wrong with the native SU...
Hello,
I couldn't find an up to date thread with this, so I decided to create it.
I uploaded the newest adb and fastboot binaries out of the Android SDK for OS X and Linux and wrote a little script, which installs it for you.
You can find the script and the binaries here: https://github.com/simmac/minimal_adb_fastboot
I will try to keep the binaries up to date! You can help me by posting an answer as an heads up, I will do the rest.
How to install:
Download the zip
unzip it
cd to the directory (probably Downloads/minimal_adb_fastboot ) *
Start the shell script with ./install.sh
*You don't longer have to do this. Since v1.1 you can call the script with /path/to/script/./install.sh . (eg Downloads/minimal_adb_fastboot-master/./install.sh )
You can either download the zip directly ( https://github.com/simmac/minimal_adb_fastboot/archive/master.zip ) or clone the repository ( https://github.com/simmac/minimal_adb_fastboot ).
[LEGACY] Installer Package! You can now install the binaries via my installer package, which simply copies the binaries to /usr/bin. Download: https://github.com/simmac/minimal_a...nload/1.1.1/Quick_ADB-Fastboot_Installer.mpkg NOTE: The package isn't supported anymore, please use the script!
NOTE: This is for OS X and Linux!
I hope I help you with this.
Changelog:
15.11.2014: Initial release with adb version 1.0.32
16.11.2014: v1.1 allows you to call the script from everywhere
23.11.2014: v1.1.1: Name changed to "Quick ADB / Fastboot installer" due to name conflict with "Minimal ADB and Fastboot"
[*]10.03.2015: v1.2: Update to Platform-Tools v22 and adjustments to the script.
13.03.2015: v1.2.1 Improved version check
14.03.2015: v2.0: Linux support! (experimental)
31.05.2015: v3.0: Major code cleanup, uninstaller and more
v1.1 release
I just released v1.1 of my script.
Changes: The script can now be called from everywhere, you don't have to navigate to the folder anymore.
Thanks! Working great for me.
Good to hear, @JennyLikesSka !
Excellent. The first link on Google didn't support sideload but this did so thanks so much!
AlecRobertson said:
Excellent. The first link on Google didn't support sideload but this did so thanks so much!
Click to expand...
Click to collapse
You are welcome!
That's exactly why I made this I couldn't find the newest Binaries anywhere, so I downloaded the whole SDK and extracted the bins.
Maybe a mod wants to pin the thread?
v 1.1.1 release notes + installer package
I just released v1.1.1, which changes the name to "Quick ADB/Fastboot installer" due to name conflict with the "Minimal ADB and Fastboot" tool.
Also, I did some cleanups in the code and made an installer package, which simply copies the binaries in /usr/bin.
Download the installer package here: https://drive.google.com/file/d/0B_i0YdEB_NoQVklSNldvRTVpZU0/view
And the normal command line installer here: https://github.com/simmac/minimal_adb_fastboot/archive/1.1.1.zip
I run accross the issue with flashing my N5 with stock 5.0 and adb needing to be updated to 1.0.32
I have downloaded and run command prompts up to where it says - Installation completed successfully! adb version 1.0.32 is now installed.
I then tried to flash again, but still get the error to update my adb?
simmac said:
I just released v1.1.1, which changes the name to "Quick ADB/Fastboot installer" due to name conflict with the "Minimal ADB and Fastboot" tool.
Also, I did some cleanups in the code and made an installer package, which simply copies the binaries in /usr/bin.
Download the installer package here: https://drive.google.com/file/d/0B_i0YdEB_NoQVklSNldvRTVpZU0/view
And the normal command line installer here: https://github.com/simmac/minimal_adb_fastboot/archive/1.1.1.zip
Click to expand...
Click to collapse
The package won't open on my mac. Just get an error message.
@dholm: How do you run adb/fastboot?
With "adb" or "./adb"?
@JennyLikesSka: Which Message?
Did you try open it with rightclick - > Open?
Which OS X version do you run?
simmac said:
@dholm: How do you run adb/fastboot?
With "adb" or "./adb"?
@JennyLikesSka: Which Message?
Did you try open it with rightclick - > Open?
Which OS X version do you run?
Click to expand...
Click to collapse
./adb
dholms said:
./adb
Click to expand...
Click to collapse
I see, that's your error.
With installing adb, you don't have to execute it with ./ before the command name, simply type in the command via "adb" .
Ha I will give that a try, thanks!
dholms said:
Ha I will give that a try, thanks!
Click to expand...
Click to collapse
Do this, please report back, also if it worked.
simmac said:
Do this, please report back, also if it worked.
Click to expand...
Click to collapse
It got passed my previous issue, but it now shows
E: footer is wrong
E: signature verification failed
Install aborted
My steps were
1. Install 5.0 (LRX21O) from here - https://developers.google.com/android/nexus/images
2. Install Android SDK from here - https://developer.android.com/sdk/index.html
3. Rename folders (1 = ota.zip and 2= android)
4. Copy ota.zip to platform-tools folder
5. Run terminal commands (cd /Users/*username*/Desktop/android/sdk/platform-tools -> adb devices -> adb reboot-bootloader -> put into recovery then hold power button and tap volume up -> install from adb -> adb sideload ota.zip
@dholms: Seems like an issue with your update.zip. Are you rooted?
simmac said:
@dholms: Seems like an issue with your update.zip. Are you rooted?
Click to expand...
Click to collapse
Lock state was unlocked to install DP of 5.0 - That was it...
Edit: seems this might be the issue - http://forum.xda-developers.com/google-nexus-5/help/e-footer-wrong-t2938236
dholms said:
Edit: seems this might be the issue - http://forum.xda-developers.com/google-nexus-5/help/e-footer-wrong-t2938236
Click to expand...
Click to collapse
Yeah, seems so, you may have to flash the image.
But my Installer worked, right?
simmac said:
Yeah, seems so, you may have to flash the image.
But my Installer worked, right?
Click to expand...
Click to collapse
Yes it did, thank you very much!
Hello all, I've recently been trying to install the Metasploit Framework in Termux, I have already got a fully working Kali Chroot but would like to remove this to free up some space on my Device (Samsung Galaxy J5 2016, running ViperOS) I've so far managed to get most of the dependency installed as per the instructions on
https://wiki.termux.com/wiki/Metasploit_Framework
But I'm getting stuck on Gems, the error I'm getting is Segmentation Fault (See screenshots attached)
Does anyone have any ideas?
theashleyd123 said:
Hello all, I've recently been trying to install the Metasploit Framework in Termux, I have already got a fully working Kali Chroot but would like to remove this to free up some space on my Device (Samsung Galaxy J5 2016, running ViperOS) I've so far managed to get most of the dependency installed as per the instructions on
https://wiki.termux.com/wiki/Metasploit_Framework
But I'm getting stuck on Gems, the error I'm getting is Segmentation Fault (See screenshots attached)
Does anyone have any ideas?
Click to expand...
Click to collapse
When you bore with troubles,
Use this script for install automatically
https://github.com/iqbalfaf/Metasploit-Termux
Nuttapat007 said:
When you bore with troubles,
Use this script for install automatically
https://github.com/iqbalfaf/Metasploit-Termux
Click to expand...
Click to collapse
Get the same issues, script hangs after install ruby and trying to install Bundles.
theashleyd123 said:
Get the same issues, script hangs after install ruby and trying to install Bundles.
Click to expand...
Click to collapse
Please reinstall termux and try this script personally tested https://github.com/Hax4us/Metasploit_termux
lkdevil said:
Please reinstall termux and try this script personally tested https://github.com/Hax4us/Metasploit_termux
Click to expand...
Click to collapse
Can you please provide instructions on how to run this script?
mod edit - content removed
Try My New script works fine.Before proceeding to install Metasploit framework on your device make sure you clear all the data from your settings (settings>Apps>Termux>clear data)
Open Termux app & follow my Instructions carefully:
termux-setup-storage (Give storage permission)
pkg install git
git clone https://github.com/Mohithchowdary/exploit-toolkit
cd exploit-toolkit
chmod +x exploit-toolkit.sh
./exploit-toolkit.sh
This will start your installation process. Wait for a while until you get prompt symbol $
Type this command to start the Metasploit framework
cd metasploit-framework
./msfconsole
If you are facing any error after trying This script please let me know.
Thank you!
Start Exploiting today[emoji6]
Sent from my Z2 Plus using Tapatalk
./metasploit.sh: line 1: 400:: command not found
Abhikk said:
./metasploit.sh: line 1: 400:: command not found
Click to expand...
Click to collapse
What's app: +919491555177
Sent from my Z2 Plus using Tapatalk
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
WhatsApp me: +919491555177
Sent from my Z2 Plus using Tapatalk
How to install Metasploit-framework on any Android device(Termux) without root?
Problem solved!
This blog helps you to download & install the latest Metasploit-framework on any Android device using Termux.Works on both rooted and Non-rooted devices.Start exploiting today!
Link:- http://termux-world.blogspot.in
Have you gotten solution to it. Cause I got same error here