Okay so I have been trying to push/install/anything to an .apk file.
all I get is the error:
'adb' is not recognized as an internal or external command,
operable program or batch file.
which I have rooted my phone and pushed files before.
I have also noticed the .apk files do not appear as their usual file images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Run the commands from your android sdk/platform tools folder
Or any folder that has adb/fastboot .exe
bigdaddy619 said:
Run the commands from your android sdk/platform tools folder
Or any folder that has adb/fastboot .exe
Click to expand...
Click to collapse
I have attempted, the error still shows up.
What seems to have fixed my adb issue (at least for flashing not sure about pushing/installing yet)
was that I uninstalled my version and reinstalled the tools.
I will attempt pushing and installing tomorrow or in a few hours.
Has that error ever happened to you just randomly?
I ALWAYS run the commands from my sdk files holding the adb.exe
Only time I got those errors was when I was using the wrong folder to run them.
bigdaddy619 said:
Only time I got those errors was when I was using the wrong folder to run them.
Click to expand...
Click to collapse
Fair enough.
I did make sure I did it in the right folder I even tried in another folder with a adb.exe and fastboot.exe
The same result until I uninstalled and reinstalled
Related
First, I wasn't quite sure where I should put this, so if theres a better forum for it, please move it.
I feel like a real idiot right now, but nonetheless I'm having issues getting Eclipse 3.5.2 and the Android SDK to work (on Mac OS X).
I got as far as installing the ADT plugin and then once I got to "showing" Eclipse where the Android SDK was located I failed miserably. Every time I navigate to the folder and hit open and then apply nothing happens, it just stays at the "default" no SDK(s) screen. Bit hard to explain, so I took a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So if anyone knows how to get that to work, it would be really appreciated. Maybe I screwed up something really obvious, that would be just my luck.
Umm, have you downloaded all the developer tools in the SDK? Launch the android binary in the /tools/ folder and look for available packages and install them all, or the ones you'll be using at least.
GrdLock said:
Umm, have you downloaded all the developer tools in the SDK? Launch the android binary in the /tools/ folder and look for available packages and install them all, or the ones you'll be using at least.
Click to expand...
Click to collapse
Wasn't sure if that would work, I'll give it a try and let you know.
Hooray that worked.
Thanks a ton GrdLock.
Intro:
Today I present you with GetDump, a Windows batch file that is the simplest way to get a system dump from your phone. All its takes is 2 clicks. I might add Linux and Mac OS 10 support in the future, but if anybody wants to do it for me that would be great. The ADB files are included in the zip so you don't need to install them. I hope I posted this is the right place....
Requirements:
Your device drivers (The drivers from the manufacture)
Windows
Should have ADB installed
How to use:
Unzip the GetDump.zip file then once its unzipped double click on the GetDump.bat file. After that follow the onscreen instructions. Once its done a window will pop up with your system dump inside of it.
Download:
http://www.mediafire.com/download/sa7jy5s2frtzve1/GetDump.zip
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits:
Andy Huynh - For teaching me MS-DOS
My cat Chibbs - For testing
Hey cool, gonna DL for my Windows! Someone already beat ya to it in Linux tho
http://forum.xda-developers.com/showthread.php?p=62845957
Gratefully sent from my Rooted JollyRoger_B13
bcrichster said:
Hey cool, gonna DL for my Windows! Someone already beat ya to it in Linux tho
http://forum.xda-developers.com/showthread.php?p=62845957
Gratefully sent from my Rooted JollyRoger_B13
Click to expand...
Click to collapse
Tell Me how you like it. SuperRs does more then just a system dump, but I might make one that just does a system dump.
Hi
I have two old LGG2Minis. One with LineageOS and the other with stock Android 5.0.2. I thought that I would throw something else on the other one too.
I wanted to open bootloader by copying the aboot.bin file (as the is the easiest way to do this in this device). So I copied it into the internal memory, I entered the command in the Terminal Emulator and got the info 'no such file or directory'. OK, I could have have made a mistake in a command. I carefully typed again and the result was the same. I tried to get into the /sdcard directory with cd command and the message still 'no such file ..'
I went to ES Explorer and what I'm seeing in /mnt is that I do not have a /sdcard directory there, just something with that name with an icon looking like a file icon. I checked in the Total Commander and I have the /sdcard FOLDER in /mnt, I can get inside, add folders and what not. I thought that since with TC it is ok maybe this is an app permission problem so I installed Termux - the result as in the Terminal Emulator.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't have any other issues with internal memory. Phone works fine. I can save photos in internal memory (external SD card too). I don't get messages from apps or errors other than those I'm writing about. Finally I copied aboot.bin from another directory, twrp.img as well. In the File Manager in TWRP I have emmc with what's in the /sdcard directory.
I think that storage/emulated/legacy should be a hint for me, but I don't have the knowledge to use this hint. So my questions are - what happened? How to change that?
Google has made it easy to use ADB in Windows these days, but the ADB commands can only be used in a directory. This a Powershell script for Windows that will download the latest ADB from the Official repositories and install it System-wide or User-Wide, this script will also install latest Google drivers also from from the Official repositories. This script will help to install ADB and the drivers in an easy way. Most ADB installers come in exe format where you cannot see exactly what they do exactly. So I decided to write the whole thing as a Windows Poweshell script.
On my github page you can download the script and you can also find an explanation how to use the script. The big difference to others is that ADB & Fastboot drivers are updated in real time when this tool is used. For the drivers i have to update a link I'll do my best when a new driver comes out to update the link as soon as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
System-wide: ADB and Fastboot are installed to HOMEDRIVE\ADB directory, and added system-wide path.
HOMEDRIVE=C:\ so in case of the system-wide install option ADB will copy over to C:\ADB
Current user only: ADB and Fastboot are installed to UserProfile\ADB directory, and added path for current user. UserProfile=%SystemDrive%\Users{username} so in case of the Userwide-wide install option ADB will copy over to C:\Users\username\ADB
CMD or Powershell can use ADB and Fastboot from any directory.
If you are using this tool and you having problems leave a comment and I will try to help you
ķANKAN
Hi, so i got a simple tablet, Multilaser M7S Lite, and i want to root it, my main goal is to be able to edit System folder, i want to change the boot animation, mainly.
So , since there is no TWRP recovery for this brand, i decided that the only way, was with magisk patching boot.img. So i found my deivce firmware - https://www.stockrom.net/2021/04/multilaser-m7s-lite-so06-v7-20200509-8-1oreo.htmland download the .img file. So to extract the boot.img, i need to change it to .zip file and open. But when opening it it says the following:
And using 7-zip, it only extract this files :
What can i do?
The firmware-package file you linked to is a .RAR-formatted archive.
When you unpack this .RAR-file then you can see a ML***USER.img is housed therein what is tablet's Stock ROM.
To unpack this .IMG-file you may use sim2img provided here:
[DEV][Tools] simg2img for Windows
Hello, although I'm working in Linux (VM too) I rewrote the SIMG2IMG so far for Windows (PE32, x86) Usage: simg2img.exe -i -o Optional: -d for debugging messages, listing all chunks of the image...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Running sim2img, it says bad magic.
It's the full firmware but is it an allwinner or a rockchip or... These tabs can be like whatever. Check that first then google how to extract etc.
I found this: https://forum.xda-developers.com/t/...images-unpacker-packer.1753473/#post-28329544
SOO i manage to unpack it!!
Which file i use in magisk to patch?? boot.fex?
yep.