[Q] ADB inside Android? - Android Q&A, Help & Troubleshooting

I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needing a PC).
So..... Would it be possible?

This would fare better in the Android Q&A forum. I'll flag it to the forum mod and ask them to move it

Done, and Thank You Sir.

adb
pokepal101 said:
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needinig a PC).
So..... Would it be possible?
Click to expand...
Click to collapse
I want to start by saying I'm no expert, but to the best of my knowledge, this is how it works.
adb runs native on android, the android property is ro.secure=1 this is found in the default.prop file. ADB is run in user privilege mode with this property setting. Not all of the adb shell commands will work with the device in this mode. With ro.secure=0 property setting, adb will run with root user privileges and all adb shell commands will function. There is an adb comand that when issued will return the value of the setting, but off the top of my head I could not tell you it. The file default.prop is part of the boot.img and will load every time the device is booted, so to edit the file the boot.img would have to be unpacked, edited, repacked, and pushed to the device boot partition.
I don't know why you would want to connect two smartphones using adb and don't know if it is even possible. It is probably best to run the binary with a script on the device where you want it installed. Good Luck with your project.

Sorry, I don't think I quite understand....
fdaconta said:
Not all of the adb shell commands will work with the device in this mode
Click to expand...
Click to collapse
I'm sorry if I'm not making myself clear, but I'm talking about running the ADB client/server on an android phone (normally done on a development computer), not the ADB daemon.
fdaconta said:
It is probably best to run the binary with a script on the device where you want it installed
Click to expand...
Click to collapse
That's also not possible, as the script involves running some complicated ADB-ish things like "adb restore" and running while device #2 is turned off - hence the need for device #1.

Related

Problams and solution while rooting

It might seem a bit stupid, but maybe others will encounter one of this issues and it will help them. your more than welcome at add to this.
P: computer wont recognize device in debug mode. instead it recognizes "android 1.0" or something else.
S: download HTC sync. it contains the proper drivers.
P: while activating the *.bat file you get the erroe "adb out of date...killing". the script will run all the way, but root access wont be given.
s: you need to close all adb processes from task manager, and the htcsync process as well (on PC)! also, you need to reflash the img file, and try rooting again.
HTC SYNC
after 10 attempts at ROOT, I found this tread. It is CRITICAL that you stop the HTCSync process on you PC or root will not work!
HTC Sync on the tab or on the pc? I killed it on the tab through the running applications. To kill adb processes just close the command window on the pc.
you need to kill it on the PC.
Ok so noob question of the day!
Where are you supposed to input the commands (such as adb reboot bootloader) to start the kernel flash process? I tried in cmd as well as terminal emulator on the tablet with no luck, what am I missing here?
NJFM said:
Ok so noob question of the day!
Where are you supposed to input the commands (such as adb reboot bootloader) to start the kernel flash process? I tried in cmd as well as terminal emulator on the tablet with no luck, what am I missing here?
Click to expand...
Click to collapse
you should have ADB in your c:\android folder, or wherever your sdk is installed.
Do a search for adb with your pc to find out where you installed it.
then using the command prompt under start> programs> accessories> command prompt, go to the corrected directory that ADB is in.
to go to C:\android, for example, type " cd c:\android "
Then you would execute the adb commands, (example: adb reboot bootloader)
Go to youtube and search for a 'how to use ADB' tutorial.
I'm having difficulty hotbooting the insecure kernel.
I've uninstalled HTC Sync on my PC, and I've downloaded the insecure kernel to my SD card's root directory.
I have no problem rebooting the bootloader via adb, and my device is detected. However, when I try to hotboot the kernel, I routinely get a "cannot load" response. I'm typing in "fastboot boot [filename].img."
Suggestions?
Many thanks.
the insecure kernel shouldn't go to the SD card. only the wifi module should.
the *.img file should go to the adb\tools directory,
(maybe you can put it anywhere else and just write the full path while flashing, i'm not sure. i just copy this files to the tools directory and flash them from there. easiest way)
the flash command flashes the file from the directory on the computer to the device.
Thanks very much!
I'm sitting here laughing to myself because I'd tried changing the path in the command to a couple of places I'd placed the insecure kernel in my PC; the c: root directory and a directory I'd created to house downloaded Jetstream files. Obviously, neither worked.
Placing it in the adb\tools directory makes complete sense.
By the way, your mention of the "wifi module" sent me back to DooMLoRD's kernel thread. I see that you flashed the kernel and related wifi module on 1/4. Like others who posted, are you pleased with the kernel?
Thanks, again!
The kernel seems very nice and almost no one complaind.
Sent from my GT-I9000 using XDA App

[GUIDE] ADB - Usage, Tips, Tricks and More!

*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.

[Q] adb command

I am having a hard time un-rooting my phone back to stock to return to at&t. I have followed this instruction:
http://forum.xda-developers.com/showthread.php?t=1634087
But when I get to this part I am totally lost.
" Issue the following adb command. I SUGGEST YOU COPY AND PASTE IT, IF YOU TYPE IT WRONG YOU WILL HARD BRICK YOUR PHONE.
command: " adb shell dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 "
I am not sure I installed ADB correctly following this instruction:
http://jaxov.com/2010/10/set-up-adb-on-windows-7-vista-xp-for-android-phones/
and this:
http://developer.android.com/sdk/installing/bundle.html
I can't afford to brick my phone and if I get caught by my wife.... OOOOO the horror.
Here's what I have,
1. the adb bundle in a folder here -C:\Android Development\
2. android Development contains - a. eclipse folder, b. sdk folder, c. a workspace folder for eclipse projects I added
3. I have the drivers for my phone installed (I think - Kies works)
4. I have the Recovery image on my sd card. (my external card won't mount)
5. Debugging enabled
6. SDK manager has been run and updated
I think I need to do some thing with the environment variables but I'm not sure what.
the instructions said:
"Navigate to My Computer (Icon)->Properties (Link)->Advanced System Settings (Link)->Advanced (Tab)->Environment Variables (Button)->System variables (Section)->Path (Variable)-> Edit (Button)-> Variable value. Enter the following value as shown in the screenshot.
C:\android-sdk-windows\tools "but my path is not the same. I didn't want to mess up my computer so I created a new variable named android path and added C:\Android Development\sdk\tools.
when I open the cmd line, the instructions here ( http://jaxov.com/2010/10/set-up-adb-on-windows-7-vista-xp-for-android-phones/ ) show the folder as C:\android-sdk-windows>adb devices and I have C;\Useres|Momma Bear (Yes it's her computer)
What do I do Next? Pleas help a noob Google let me down for hours.
Thanks to all who look and help. and +10 to all the devs and who ever gives me a working solution.
Just use dos commands to change to the directory with adb.exe , then run adb, then type " devices" and it should report your phone as android device. If not, PC did not correctly install driver. If yes, copy paste command.
But honestly, just return to stock, then delete superuser app. How will they check?

Kindle HDX 7''. Pushing system update files - Android ADB Interface - Bootloop -

Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK,I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2

Help extracting data from Android Device

Hi, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.

Categories

Resources