Hi guys,
I've got a question...
But first, STORY:
I have a tablet with stock Android 4.2.2 rooted and a Moto G (not rooted). I had connected my Moto G (4.4.2) to the tablet over an USB Dongle with USB debuging enabled and my tab found my Moto G. So I started the terminal Emulator with SU permisions on my tab and typed:
su
Adb devices
My tab listed my device as "device" and i had control of my Moto G.
Now I updated my Moto G to 4.4.4 and when I connect my device now to my tab, my Moto G is listed as "offline". Thats Bad.
I tried:
- toggle USB debugging
- reset adb Permissions
- reboot Tab and Moto G
- used up -to-date ADB binary of the Android SDK for Linux (failed: magic 7f45)
I think I need to update my build-in ADB binary of my tab to get succesfully connected.
Can anyone send me a Built-in ADB binary from an Android 4.4 device, please? I think it can be found in /system/bin .
Thanks to all!
PS: Sorry for my Bad english.
Related
Hi ppl,
I was wondering if it's somewhat possible to have fastboot installed as an apk on my tablet (Android) in order to flash things on a smartphone plugged in that tablet.
Scenario is: wife wants my notebook; I want her tablet. If I could use adb and fastboot from the Android tablet, I could really do everything with it and the swap may happen
Thanks
Fabio
No way at all, I guess?
Android already has fastboot built in but you will need a OTG cable and a search in the manual to find out how to access.
On my tablet (Aishuo) it is menu and power up .
Do the swap man you wont regret it ( he says )
Keith
There is a binary called "flash_image" which you can run from terminal emulator, which can (as the name suggests) flash images in a similar fashion to fastboot. Google it
found it
Not sure if you already figured out yourself, but this thread is about fastboot and adb via otg
http://dl.xda-developers.com/attach...dd88a/1/5/4/2/6/7/1/ADB_FastbootInstaller.zip
Hi All
I got myself a Mediapad 10 FHD two weeks ago, 1.2MHz 1GB Ram, 8GB Rom, Wifi.
It looks like I cannot get root nor custom recovery installed on the device. I have tried all I could find so far, without any luck.
What I have tried so far is:
Hi Suite Setup v1.7.00.1006
Hi Suite Setup v1.8.10.1506
custom USB driver from Team Android
standard Linux ADB driver (which work on my Nexus 4)
Windows XP in a virtual box running the driver above
standalone Windows XP computer running this drivers
toolboxes for ADB / root
Genotools v2.0
Root with Restore by Bin4ry22
auto recovery installer for huawei mediapad
root with repair
Genotools seems to work for some people, no luck here.
When I follow the steps for root manually from a Linux console I can move all the needed files onto the device but cannot change permissions or dont have access to the desired folders.
The weird thing is that that I cant access the device when in recovery at all, while access with ADB debugging is ok.
adb reboot bootloader boots the device into recovery
afterwards fastboot devices doesnt show anything
fastboot flash recovery cwm.img just waits for the device forever
Anybody have an idea what else I can try?
Recoveries in that installer are ONLY for 7" mediapad (hws7300)
Hello all,
I flashed my Moto g to CM11, but now I want to go back to the stock version-1.8-1.4_CFC US_retail_XT1032_KXB20.9
I put the phone in usb debugging mode, but when I run the adb devices does not recognize the phone:
Code:
C:\Users\USER\Downloads\ElementalXDesigns-MotoX-Tools>adb devices
List of devices attached
note: I have returned the original recovery
Hi All !
I have a Samsung Galaxy Note 10.1 GSM 3G tablet [N8000 model]. Right now it comes with stock Samsung Android 4.1 and stock Android recovery.
I have a trouble installing ClockWorkMod and root it.
What I did ?
1. Installed Samsung USB drivers + ADB + fastboot + Odin.
2. Enabled USB debug
3. adb devices
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4107764d436ccf47 device
4. fastboot devices
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>fastboot devices
[empty]
5. fastboot flash recovery [imagefile]
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>fastboot flash recovery E:\S
martphones\Android\GalaxyNote_10.1\recovery-clockwork-6.0.4.6-n8000.img
< waiting for device >
...
Basically adb "sees" my device, but fastboot does not see it.
I tried this procedure when Android is booted ans also when it is in "download" mode.
Host is: Windows 7 x64, Intel Core i7 4770. I have installed
Another problem: Odin 3.0.9 sees my device, and it does not accept *.img files from CWM, but requires .tar instead. Why so ?
Any ideas ?
Please help.
-Technologov
I have a HTC Google Nexus 9 tablet. I recently received the update to Android 6.0.1 via the normal push notification. The update got stuck on ‘optimizing your apps 1 of 74’. It normally moves up in the numbers within minutes but it remained on ‘1 of 74’ for an entire night. So, the next morning I switched off by holding the power button.
The system still booted but soon enough I received error messages like ‘there is an internal error, contact the manufacturer’ and during the boot it says that my system was corrupted.
I decided on a factory reset. It went through with it. But when setting up the cleaned system, there is another problem: I can pick my language and connect to my WIFi without problem. But then it goes to a screen where it says ‘checking connection. This may take a while.’ It gets stuck there for several hours - so it is clearly faulty as I don’t think ‘a while’ means 12 hours and more. I also don’t think that the factory reset solved the problem anyway as I still receive error messages, hinting at a corrupted system, during and after the boot.
So, I decided to try to flash a system image.
I got the Minimal Android Debugging Bridge ADB and Fastboot on Windows 7 and Ubuntu,
Then I followed the Google developers instructions and downloaded Volantis MOB30D from there.
I also got Android drivers for Windows, but I’m not entirely certain if they are right.
When I connect the Nexus 9 to the Windows computer, I now see in Device manager: ASUS Android Devices -> Android ADB Interface
It’s not an ASUS tablet though and I can’t see the Nexus 9 in ‘Computer’ (it used to show up there as ‘Portable Media player’
Is it possible that I got the wronger drivers and if so, how would I install the correct ones?
Then I start the Nexus 9 and hold power and volume up down to get to the bootloader.
It says ‘Fastboot USB’
I also says ‘device state - locked’ . I can’t get to the system settings to do the OEM unlock as I’m stuck on ‘checking connection’ when I boot normally.
Then I opened ‘Minimal ADB and Fastboot’ on Windows and tried the following commands:
Fastboot flashing unlock
… and it says:
FAILED (remote not allowed)
Then …
Fastboot oem unlock
… and it says:
(bootloader) ability is 0
(bootloader) permission denied for this command
Then I tried the same on Ubuntu. The device doesn’t show in the left hand side panel. When I try the above commands it just says
waiting for device
So, I guess Ubuntu doesn’t even recognize the Nexus 9
I then opened ‘Additional Drivers’ but it just says searching for available drivers and then no proprietary drivers are in use on this system
Any advice for Nexus 9 drivers on Ubuntu?
I also tried from the bootloader: Hboot → Recovery → Apply update from ADB
In Ubuntu I went to the directory where the ZIp file of the system image is located
Then I typed in the terminal:
adb sideload image-volantis-mob30d.zip
And it says …
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
1. You don't have correct drivers for Nexus 9. The Nexus Root Toolkit has a driver instillation guide.
2. You can not sideload factory images.
Try sideloading the failed ota available here
Code:
April 2016 Nexus OTA Updates - Security Level 2016-04-02
Nexus 9 (LTE) [URL="https://android.googleapis.com/packages/ota/google_flounderlte_volantisg/9ae7d85d6433d055a9e4f3049ac86eb0e562bbf1.signed-signed-volantisg-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
Nexus 9 (Wi-Fi) [URL="https://android.googleapis.com/packages/ota/google_flounder_volantis/6a2119f2077022c1ba852f2c613b8ce942c33836.signed-signed-volantis-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
If that doesn't work try sideloading Android N OTA
aeglyss said:
Any advice for Nexus 9 drivers on Ubuntu?
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
Click to expand...
Click to collapse
I don't know specifically about Ubuntu, but I've done several updates to usb-connected android devices using Debian linux, and I've never needed to add a device-specific driver.
Some additional ideas on the permissions:
(1) Did you enable "USB Debugging" in Settings->Developer Options?
(2) From your Linux machine, did you try to run adb as the root user or use sudo? I have to do this for both adb and fastboot. (Example command line: '$sudo adb devices', without the quotes.)
(3) Finally on the Linux side, did you try to connect first via adb? And, if so, did you look on your Nexus for an "Enable..." approval notification?
Good luck!
cheers,
john
Thanks everyone. I managed to fix it
aeglyss said:
Thanks everyone. I managed to fix it
Click to expand...
Click to collapse
Hi, I am at a similar point, my Google Nexus 9 failed doing the update, I then tried to factory re-set it and now it is trying to check connections...
I have downloaded the bootloader and my Windws 10 pc can see the tablet via explorer. I believe I have also switched the tablet to Fastboot but bootloader doesn't sem to be able to make the connection.
I was wondering if you are able to provide me with instruction as to how to rescue this tablet. I am not an expert, so I would appreciate any instructions to be as simple as possible.
Thank you for your help,
Mike