[Q]Why does fastboot fail to detect my device? - General Questions and Answers

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.

Related

Fastboot does not find device [Zync Z930 tablet]

Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
root
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
Click to expand...
Click to collapse
Hey can you please guide me how did you root this device? I am having the same and I need to root it. Thanks.
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
... [CUT FOR SPACE] ...
Thanks a lot,
badday
Click to expand...
Click to collapse
I have the exact problem badday has, but with the Ainol Novo7 Paladin. Any help will be appreciated in my corner as well!
Unable to root Zync z930
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If anyone of you manages to crack it please let me know, thanks!
---------- Post added at 08:27 PM ---------- Previous post was at 08:22 PM ----------
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If you managed to crack it please let me know, thanks!
To clarify things: I did not root my device so far.
Some additional information I found out:
Try to reboot in adb via "reboot-bootloader" results in normal startup. Furthermore, booting to fastboot mode (with vol-up-button down) with Micro-SD-Card inserted makes the device not to appear any more in lsusb.
Anyway, that made me having even less clues than more :crying:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
abdulmomin said:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
Click to expand...
Click to collapse
Anyone found any method to root z930?
I'm not sure for linux but I think you will have to download drivers ,,,,,,,I had to do this for my computer (running win 7) to read my phone in fast boot
I downloaded an app called driver tools and that fixed it ....hope this helps
Ps : It maybe that your running 64 bit Os
@abdulmomin, jaydeepkhalpada: Rooting thread can be found here: http://forum.xda-developers.com/showthread.php?t=2028740
@fredworxz: Yes, I use a 64bit OS. However, for GNU/Linux drivers should not be needed as adb runs out of the box (please correct me if I am wrong).
Resolved! - See my post! http://forum.xda-developers.com/showthread.php?t=2045173
I've not only installed JB in Z930 but also successfully ADB'd it to root it
Here:
http://forum.xda-developers.com/showthread.php?t=2045173
Actually I cannot install the driver which might be some problem as I use 64bit OS and have no 32bit available. Anyhow, according to the name scheme, there should also be a 64bit version included.
Apart from that I have also problems with this Chinese software, does it need adb drivers to be installed? Actually when I boot in this mode with vol-up-button, there appears absolutely nothing in the device manager.
Would be great if you could help me out as I need this tablet for some sort of NGO project.
Greetings from Delhi,
badday
This is not fastboot mode
as your trying to unlock fastboot ,but this is not fastboot mode
this is for flashing firmware through G+massprotection tool..
There is no fastboot mode in Z930..
but you can goto recovery menu by pressing
1st press & release Power button then press and hold vol+ button

Cant use fastboot / bricked bootloader?

Hi
My problem is that I can access fastboot on my phone (computer) I have tried in windows and as inserted in Linux. My phone is bricked, OS (CM-10) is not running and just dark screen in recovery mode. As you can see, i can access adb device and adb reboot to recovery, but not to fastboot that I will need to flash my phone (ZTE NUBIA Z5)
Help is very much appreciated THANKS!!!
[email protected] ~ $ adb devices
List of devices attached
NX40X recovery
[email protected] ~ $ fastboot devices
[email protected] ~ $ adb devices
List of devices attached
NX40X device
Basmand
Driver Missing!
USB Drivers Are Missing That's Why :fingers-crossed: DO Your Best!
Google For Drivers :victory:

[how to] lock/unlock your bootloader without htcdev(s-off required)

READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
(yes this is m7. i dont have an E8. if someone wants to provide correct screenshots,ill add them)
other useful threads:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change mid without an eng bootloader: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148
sorry for the delay,guys. hope you find it useful
This way doesn't wipe out all the data, right?
buggerman said:
This way doesn't wipe out all the data, right?
Click to expand...
Click to collapse
Correct. It will not wipe any data
Sent from my HTC One max
Good job.
Any way to do S-OFF to S-ON ??
greg
gregferns said:
Good job.
Any way to do S-OFF to S-ON ??
greg
Click to expand...
Click to collapse
Sunshine again..
windows 8 and above
am using windows 10 but it seems the required tool does not support the operating system
any other option for me?
cant get # prompt
hi, when i enter the Su command it says su not found and the prompt still remains $ instead of #. Is it something am not getting right or something. Thanks

[Help needed] Acer Iconia B1-750 + ubuntu = no fastboot

Hi, all.
I went through the forums here and googled, but I can't find one working solution.
I have the tablet in subject (Acer Iconia B1-750).
I'd like to root it using guide I found on this forum and with modification for Ubuntu from here.
I can see my device in adb no problem.
When I run lsusb, I see device
Code:
Bus 003 Device 030: ID 0502:367b Acer, Inc.
So far so good.
When I do
Code:
adb reboot-bootloader
the device restarts to something called DROIDBOOT PROVISION OS.
When I type
Code:
lsusb
I can still see the device as
Code:
Bus 003 Device 031: ID 0502:3680 Acer, Inc.
So far so good.
However, when I do
Code:
sudo fastboot devices
I see no device connected.
I tried the -i 0x0502 switch for fastboot, did not help.
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
I tried to modify the ~/.android/adb_usb.ini, no help.
I also ensured I have correct permissions for plugdev on the device using udev rules and I do.
Does anyone have any advice how to force fastboot binary to "see" the device?
@sancho_sk Which Ubuntu version are you using?
Sent From my SM-G928F via Tapa
As I wrote:
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
Nobody? Seriously nobody works with Ubuntu?

Waiting for Device Error

i want to root https://www.xda-developers.com/root/
when i try
Code:
fastboot flash boot /path/to/magisk_patched.img
im stuck at
< waiting for device >
when i try
adb devies
it show my device
but when i boot to fastboot in my phone
i try
fastboot devices
didn't show fastboot devices
i use
15 seconds ADB Installer​https://www.droidthunder.com/adb-drivers/#Method_1_Using_15_seconds_ADB_Installer
what should i do ??
if youre on windows, have you installed the driver provided by your manufacturer? Or did you run command prompt as administrator?
if youre on linux, did you execute adb/fastboot with root permissions?
Also make sure you use the official plaform tools: https://developer.android.com/studio/releases/platform-tools
MLPIR said:
if youre on windows, have you installed the driver provided by your manufacturer? Or did you run command prompt as administrator?
if youre on linux, did you execute adb/fastboot with root permissions?
Also make sure you use the official plaform tools: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
im on windows i have already install mtp driver also run cmd as admin in the platform-tools folder still not show the devices.
chatofking said:
im on windows i have already install mtp driver also run cmd as admin in the platform-tools folder still not show the devices.
Click to expand...
Click to collapse
Is your usb properly plugged in and working? (Both on the computer and phone)
yes as you can see
it work on adb devices but not fastboot devices.
Code:
D:\platform-tools>adb devices
List of devices attached
WGWWINQGT8NBJVB6 device
Code:
D:\platform-tools>fastboot devices
what should i do ??
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
xXx yYy said:
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
Click to expand...
Click to collapse
did you mean
Code:
adb reboot bootloader
xXx yYy said:
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
Click to expand...
Click to collapse
thank it worked now
it show fastboot mode instead fastboot in my phone
D:\platform-tools>fastboot devices
WGWWINQGT8NBJVB6 fastboot
can i ask one more question i got this message
when i
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
what should i do ??

Categories

Resources