So I have looked at post about installing adk.. I've manually set it up, I've used a repository to setup, I've did the 'idiot proof SoupKit'..... no matter what I try the same thing happens.
I can run 'adb devices' and get a list of the android devices connected via USB. I see them just fine. My udev setup works, the adb commands works.. I have done this by manually installing from Google the latest adk, installing binaries. I can always get adb to see the devices.
When I run 'fastboot devices', it just returns without listing devices at all. Any other fastboot commands simply say < waiting on device > and nothing happens.
Why would adb work and fastboot not?
I have tried this HTC Incredible 1, HTC Incredible 2, and ASUS TF300T tablet...
Any help/advice would be appreciated.
John
A little knowledge goes a long way
Sorry to answer my own question in the forum, but I did not find an answer which I understood... Now I understand what I should have been doing. For the next folk like me:
adb - can communicate with your android device while it is running and has USB debug mode enabled. For ICS this USB debug option was under the developer settings. You can tell adb is communicating properly by running the command 'adb devices' and seeing your device show up in the output list.
fastboot - can communicate with your android device when it has been booted into 'fastboot' mode, not while booted normally form a system image. Running the command 'fastboot devices' when your USB is connected to a device booted into 'fastboot mode' will show a device if it is communicating properly.
From my browsing of many other messages, I did not see clearly articulated the need to BOOT into fastboot mode on the device. Maybe I'm just simple minded.
On my TF300T tablet, I got into fastboot mode by powering it off, and then starting it while holding down the down volume button and the power button at the same time. This brought me to a screen which I could use the volume down button to toggle between three modes, 1) erase data partition 2) fastboot mode (found it!) or 3) normal boot. I used the down volume key to move the selection to fastboot and then the up volume key to select fastboot. It then launched into 'fastboot' mode, awaiting fastboot commands.
Once my device was booted to 'fastboot mode', the latest fastboot executable from google worked. The downloaed exectuable from SoupKit and the downloaded version I found for Windows did not. From my experience, download the latest ADK from Google and use the platform-tools version of fastboot.
I certainly hope this detail helps the next poor soul who googles and read things they don't fulling understand.
P.S. This all start when my ASUS device would not update with the OTA update and after several days of really useless interaction with their support, I decided to take matters into my own hands. You have to love Android which lets you learn and grow without the specific task master of a bad support division.
environment:
PC is linux(ubuntu) 3.7 kernel
PC SDK is up to date 'platform-tools' 16.0.2
PC /etc/udev/rules.d/51-android.rules has SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
PC : 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] from 'lsusb'
Galaxy tab 2 : P3113 - android 4.1.1 stock ROM bootloader still locked
ADB devices shows the tab 2 when it is on USB connection w/ 'debugging' enabled
Details:
ADB OK for push pull files to mounted version of /mnt/sdcard.
Boots to recovery OK using 'adb reboot recovery'
But, fastboot does not seem to recognize the device. So, not possible to unlock the bootloader and sideloading using stock recovery fails on 'signature' error. Without fastboot , i can push CWM.recover.img to the sdcard mount, but i dont know how to flash it without 'fastboot'. If fastboot worked instead of throwing the 'waiting for device' error, then i could also 'fastboot boot CWM.recovery.img'. But that does not work because fastboot does not see device.
So, not able to put 4.2.2 on the device. Not able to eliminate all the software cruft from samsung that i dont like.
I would like to slim down the software stack to a native 4.2.2 with Google Apps and without all the other stuff and then consider using it as a development device. However in this current state, i dont think that i would bother.
rowntreerob said:
environment:
PC is linux(ubuntu) 3.7 kernel
PC SDK is up to date 'platform-tools' 16.0.2
PC /etc/udev/rules.d/51-android.rules has SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
PC : 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] from 'lsusb'
Galaxy tab 2 : P3113 - android 4.1.1 stock ROM bootloader still locked
ADB devices shows the tab 2 when it is on USB connection w/ 'debugging' enabled
Details:
ADB OK for push pull files to mounted version of /mnt/sdcard.
Boots to recovery OK using 'adb reboot recovery'
But, fastboot does not seem to recognize the device. So, not possible to unlock the bootloader and sideloading using stock recovery fails on 'signature' error. Without fastboot , i can push CWM.recover.img to the sdcard mount, but i dont know how to flash it without 'fastboot'. If fastboot worked instead of throwing the 'waiting for device' error, then i could also 'fastboot boot CWM.recovery.img'. But that does not work because fastboot does not see device.
So, not able to put 4.2.2 on the device. Not able to eliminate all the software cruft from samsung that i dont like.
I would like to slim down the software stack to a native 4.2.2 with Google Apps and without all the other stuff and then consider using it as a development device. However in this current state, i dont think that i would bother.
Click to expand...
Click to collapse
beg your pardon, are you following a certain guide? i don't use linux myself but have seen a few folk refer to a program called heimdall (forgive me if that's already waht you're using) if not, take a look here - http://forum.xda-developers.com/showthread.php?t=1861838
squ89r97 said:
beg your pardon, are you following a certain guide? i don't use linux myself but have seen a few folk refer to a program called heimdall (forgive me if that's already waht you're using) if not, take a look here - http://forum.xda-developers.com/showthread.php?t=1861838
Click to expand...
Click to collapse
Great suggestion! thanks .. with device in download mode, heimdall detected device OK...
rowntreerob said:
Great suggestion! thanks .. with device in download mode, heimdall detected device OK...
Click to expand...
Click to collapse
all good, don't forget the Thanks button
by the way, 4.2.2 roms are not stable (in my opinnion) enough for daily use! if you can stick with a 4.1.2. AOKP Milestone 1 works like a dream!
I have Asus Fonepad 7 dual sim (Build ver. 5.5.1).
I want to root my device.
Code:
adb devices
recognizes my device properly.
Debugging mode is on.
Even device enters in fastboot mode by executing
Code:
adb reboot-bootloader
in terminal (I am using Ubuntu 14.04).
I have set up android rules in /etc/udev/rules.d/99-android.rules .
I've found out my vendor id and product id using
Code:
lsusb
(when the device is in fastboot mode). I've made corresponding entry in android rules file. But even that didn't help
I've tried
Code:
sudo fastboot devices
also. Every time I get nothing but a blank line.
Somebody please help!!
2ndGenCore_i5 said:
I have Asus Fonepad 7 dual sim (Build ver. 5.5.1).
I want to root my device.
Code:
adb devices
recognizes my device properly.
Debugging mode is on.
Even device enters in fastboot mode by executing
Code:
adb reboot-bootloader
in terminal (I am using Ubuntu 14.04).
I have set up android rules in /etc/udev/rules.d/99-android.rules .
I've found out my vendor id and product id using
Code:
lsusb
(when the device is in fastboot mode). I've made corresponding entry in android rules file. But even that didn't help
I've tried
Code:
sudo fastboot devices
also. Every time I get nothing but a blank line.
Somebody please help!!
Click to expand...
Click to collapse
This link solved my problem . It is a correct version of fastboot which works just fine for my device.
Sorry for my bad english from ahead of time.
I got a Asus Tf300T that last year Dec 2015 I had installed using TWRP recovery and updated the firmware to 5.0. All was smooth from Dec to 2 Days Ago.
When I turned on the machine it was stuck on the Asus Logo. So I turned off the machine and turned it back on and same thing. Did the vol - + power button. Got into the recovery mode with the 3 icon (recovery,usb,wipe). I click on the recovery got up toward the Team Logo then it got stuck. I turned of the machine tried it again same thing. When I connected the device to the PC it told me APX . I again whent into the 3 icons and selected the usb icon the tablet froze , I though might be due to the driver, I did a search online how to browse for the driver and installed the driver (Andriod ADB Interface)
But I'm unable to see it as fastboot. Now when I disconnected the device. I turned on the device again , now this time it shows the Asus logo with a blue bard bellow it then it loads all the way then black screen. I have no clue what else to do if someone can help me with this would I be very grateful
locohunter said:
I installed the driver (Andriod ADB Interface)
Click to expand...
Click to collapse
If you are able to access your tablet via ADB, please try following on your own risk:
-start adb devices with the command "shell" .After that ~ # appears.
-Then copy into the opened line: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
-Enter and copy into the opened line: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
-Enter.
The device should boot normally! It was successful several times.
Good luck!
ebonit said:
If you are able to access your tablet via ADB, please try following on your own risk:
-start adb devices with the command "shell" .After that ~ # appears.
-Then copy into the opened line: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
-Enter and copy into the opened line: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
-Enter.
The device should boot normally! It was successful several times.
Good luck!
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
>adb devices shell
Usage: adb devices [-l]
I have no clue what else to do if someone has the time to even remote connect to help me.
that 3 icons screen should allow fastboot access (no need to select anything on it, just leave 3 icons on screen) - try if it will be discovered.
if yes - go here: http://forum.xda-developers.com/showthread.php?t=2399698
Sent from my TF300T using XDA-Developers mobile app
I don't get to go to the 3 icons anymore I only get a blue bar bellow the ASUS logo then when it fully loads the bar the screen stays black.
I did a clean install of win 7 pro 64 bit. When I hooked up the device I get APX driver missing.
Should I download the SDK to install the driver ? Or? How? If someone can walk me tru it.
locohunter said:
I did a clean install of win 7 pro 64 bit. When I hooked up the device I get APX driver missing.
Should I download the SDK to install the driver ? Or? How? If someone can walk me tru it.
Click to expand...
Click to collapse
First of all, the USB Driver for your TF3300T in general you will find in the Asus "PC-Suite" getting on the Asus driver site.
Furthermore you need mandatory "Minimal ADB and Fastboot" in order to access your device for different installations via flash from here: http://forum.xda-developers.com/showthread.php?t=2317790.
Further questions?
I Installed the PC suite with Asus sync and all Minimal ADB.
When I hook up the device it still tells me APX is missing driver.
locohunter said:
I Installed the PC suite with Asus sync and all Minimal ADB.
When I hook up the device it still tells me APX is missing driver.
Click to expand...
Click to collapse
Please download the USB driver for TF300T here: https://androidmtk.com/download-asus-usb-drivers.
After that please look at this: http://www.androidheat.com/adb-fastboot-install-drivers-setup/
ebonit said:
Please download the USB driver for TF300T here: https://androidmtk.com/download-asus-usb-drivers.
After that please look at this: http://www.androidheat.com/adb-fastboot-install-drivers-setup/
Click to expand...
Click to collapse
Downloaded the usb driver.
PC still shows APX when connecting, did a browse for driver on the location of the extracted folder.
It doesn't find anything in the folder.
locohunter said:
Downloaded the usb driver.
PC still shows APX when connecting, did a browse for driver on the location of the extracted folder.
It doesn't find anything in the folder.
Click to expand...
Click to collapse
Nobody knows what happened to your device in the past. APX mode is a special low-level diagnostic and device-programming mode for NVIDIA Tegra–based devices sometimes called nvflash mode. You don't need it for that case.
To exit APX mode, press and hold the power button for about six seconds. The device should immediately boot into its normal mode.
If you have access via ADB, I would like to advise to reset your tablet on the last Asus stock rom. How to? you will find in that forum.
Read this whole guide before starting.
This is for the 6th gen Fire HD8 (giza).
Current version: amonet-giza-v1.3.zip
NOTE: This process does not require you to open your device, but should something go horribly wrong, be prepared to do so.
NOTE: This process will modify the partition-table (GPT) of your device.
NOTE: Your device will be reset to factory defaults (including internal storage) during this process.
What you need:
A Linux installation or live-system
A micro-USB cable
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
1. Extract the attached zip-file "amonet-giza-v1.2.zip" and open a terminal in that directory.
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
2. Enable ADB in Developer Settings.
3. Start the script:
Code:
sudo ./step-1.sh
Your device will now reboot into recovery and perform a factory reset.
NOTE: If your PL/TZ/LK versions are too new, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you don't need to run step-2.sh below:
Make sure ModemManager is disabled or uninstalled:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
After you have confirmed the bricking by typing "YES", you will need disconnect the device and run
Code:
sudo ./bootrom-step-minimal.sh
Then plug the device back in.
It will then boot into "hacked fastboot" mode.
Then run
Code:
sudo ./fastboot-step.sh
NOTE: When you are back at initial setup, you can skip registration by selecting a WiFi-Network, then pressing "Cancel" and then "Not Now"
NOTE: Make sure you re-enable ADB after Factory Reset.
4. Start the script:
Code:
sudo ./step-2.sh
The exploit will now be flashed and your device will reboot into TWRP.
You can now install Magisk from there.
Going back to stock
Extract the attached zip-file "amonet-giza-v1.2.zip" and open a terminal in that directory.
You can go back to stock without restoring the original partition-table, so you can go back to unlocked without wiping data.
Just use hacked fastboot to
Code:
sudo fastboot flash recovery bin/recovery.img
If you want to go back completely (including restoring your GPT):
Code:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery. Use adb sideload to install stock image from there.
Important information
In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)
Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
Very special thanks to @xyz` for making all this possible and releasing the original amonet exploit for karnak.
Special thanks also to @k4y0z for making all this possible and porting the exploit to 64 bit devices.
Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
Special thanks also to @lovaduck for all the testing.
Unbricking
If Recovery OR FireOS are still accessible there are other means of recovery, don't continue.
If your device shows one of the following symptoms:
It doesn't show any life (screen stays dark)
You see the white amazon logo, but cannot access Recovery or FireOS.
If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
Make sure the device is powered off, by holding the power-button for 20+ seconds
Start bootrom-step.sh
Plug in USB
In all other cases you will have to open the device and partially take it apart.
1. Extract the attached zip-file "amonet-giza-v1.2.zip" and open a terminal in that directory.
2. Start the script:
Code:
sudo ./bootrom-step.sh
It should now say Waiting for bootrom.
If you're lucky and have an old preloader (Up to FireOS 5.3.2.0), you can just hold the left volume button while plugging the device in.
If you're on a newer preloader, there are two options:
Open the device and short the marked pin (CLK) in the attached photo to ground while plugging in.
Downgrade to 5.3.1.0 firmware (google drive mirror) via adb sideload in Amazon recovery, then proceed to use the left volume button to enter boot-rom.
NOTE: Using option two may brick your device until you have successfully finished the process.
4. When the script asks you to remove the short, remove the short and press enter.
5. Wait for the script to finish.
If it fails at some point, stop it and restart the process from step 2.
6. Your device should now reboot into unlocked fastboot state.
7. Run
Code:
sudo ./fastboot-step.sh
The device should reboot to TWRP. Format data and use TWRP to flash a custom ROM, Magisk or SuperSU.
Checking USB connection
In lsusb the boot-rom shows up as:
Code:
Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.
dmesg lists the correct device as:
Code:
[ 6383.962057] usb 2-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.0
Source Code:
https://github.com/R0rt1z2/amonet-giza
https://github.com/R0rt1z2/android_device_amazon_giza
https://github.com/chaosmaster/android_bootable_recovery
Reserved #1
Great job by Roger, everything worked very much at first attempt while I tested. Now I have revived an old tablet that was not in use anymore!
I would advise everybody trying this process to keep in mind that things can always go wrong, but you have nothing to lose anyways. Hack at your own risk.
So good luck with the mod, and again, kudos to @Rortiz2
I get the following when running step 1:
This is only for the "giza" - Amazon Fire HD 8 (2016) - , your device is a "full_giza"
Click to expand...
Click to collapse
Is there much of a difference between the two and if not should I just edit the check in step-1.sh & step-2.sh?
cultofrobots said:
I get the following when running step 1:
Is there much of a difference between the two and if not should I just edit the check in step-1.sh & step-2.sh?
Click to expand...
Click to collapse
Oh well, my fault, let me fix that.
EDIT: Fixed the product check, use the v1.1 package.
Wrong thread.... deleted.
Rortiz2 said:
Oh well, my fault, let me fix that.
EDIT: Fixed the product check, use the v1.1 package.
Click to expand...
Click to collapse
That worked. Thanks.
thankssssss my frind , but i want root for fire hd8 5gen veeeeeerynessry sory bad englash
also i can buy it form you pleassss
789mod said:
thankssssss my frind , but i want root for fire hd8 5gen veeeeeerynessry sory bad englash
also i can buy it form you pleassss
Click to expand...
Click to collapse
Unfortunately, the Amazon Fire HD8 2015 (thebes) uses MT8135 which is pretty different to MT8163. Since I don't own the device, I can't really help you with that.
Rortiz2 said:
Unfortunately, the Amazon Fire HD8 2015 (thebes) uses MT8135 which is pretty different to MT8163. Since I don't own the device, I can't really help you with that.
Click to expand...
Click to collapse
have you any way to root these ) fire HD 10 5gen ?
I need it to my wrok
my work it unlockbootloader
Hi. I have a problem on Step 2
adb: error: cannot stat 'bin/boot0short.img': No such file or directory
Click to expand...
Click to collapse
I checked bin directory and really didn't found boot0short.img. Maybe it should be generated by the script. I checked code and didn't found any other mentions about this file...
What I doing wrong?
sancho_sumy said:
Hi. I have a problem on Step 2
I checked bin directory and really didn't found boot0short.img. Maybe it should be generated by the script. I checked code and didn't found any other mentions about this file...
What I doing wrong?
Click to expand...
Click to collapse
I've updated the main post with the v1.2 version, can you try with that one, please?
(https://forum.xda-developers.com/attachments/amonet-giza-v1-2-zip.5405917/)
Rortiz2 said:
I've updated the main post with the v1.2 version, can you try with that one, please?
(https://forum.xda-developers.com/attachments/amonet-giza-v1-2-zip.5405917/)
Click to expand...
Click to collapse
Now I have a brick...
Dark screen after "Rebooting into TWRP"
Dark screen, device didn't responce on power button...
sancho_sumy said:
Now I have a brick...
Dark screen after "Rebooting into TWRP"
Dark screen, device didn't responce on power button...
Click to expand...
Click to collapse
Bricked after running the 1.2 version? That makes no sense, unless your RPMB was updated. What's the output of "lsusb" when you plug in the tablet to the computer"?
Rortiz2 said:
Bricked after running the 1.2 version? That makes no sense, unless your RPMB was updated. What's the output of "lsusb" when you plug in the tablet to the computer"?
Click to expand...
Click to collapse
Yes. I run Step 2 from 1.2 version.
After "Rebooting into TWRP" screen off and didn't on anymore.
It's not listed in lsusb:
[email protected]:~/Downloads/amonet-giza-v1.2$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:2113 Acer, Inc Integrated Camera
Bus 001 Device 005: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
After plug in to USB dmesg:
usb 1-3: USB disconnect, device number 7
Click to expand...
Click to collapse
Is there any chances to fix it? :-(
sancho_sumy said:
Yes. I run Step 2 from 1.2 version.
After "Rebooting into TWRP" screen off and didn't on anymore.
It's not listed in lsusb:
After plug in to USB dmesg:
Is there any chances to fix it? :-(
Click to expand...
Click to collapse
don't worry
first short your devices after this
2. sudo ./boot-fastboot.sh
the screen still black
after that
unplug your USB write sudo ./ fastboot-step.sh and plug it
and wait 1sec
will successfully..
thank
789mod said:
don't worry
first short your devices after this
2. sudo ./boot-fastboot.sh
the screen still black
after that
unplug your USB write sudo ./ fastboot-step.sh and plug it
and wait 1sec
will successfully..
thank
Click to expand...
Click to collapse
do you have any detailed instruction how to short it?
sancho_sumy said:
do you have any detailed instruction how to short it?
Click to expand...
Click to collapse
before short ,
try this commands
sudo ./boot-fastboot.sh
and wait 3sec
and
sudo ./fastboot-step.sh