I succesfully rooted my Tab A 9.7 LTE and installed MacroDroid to make it power off when the charger is unplugged.
However, I can't make it turn on when plugging in.
I read about it here and watched this, but I can't get the CMD to work with fasboot command. Looks like my PC does not recognise the tablet when it's in recovery menu, and when I choose "Reboot to bootloader" it just reboots to download mode.
Code:
adb devices
then works, but
Code:
fastboot
in any iteration does not
Related
[Tools, Tips & Tutorials] [kenzo]Entering EDL mode via Test Mode Screen
Who cannot enter EDL mode from standard Android boot and have no abilty to boot an image from FastBoot mode, you could try the following:
Switch the phone off.
Press and hold both Volume keys and Power key.
As Mi logo appears on the screen, release all buttons.
After several seconds, Test Mode Screen should appear (SYSTEM INFO, KEYPAD BACKLIGHT etc.).
Open Device Manager in Windows.
Connect the phone to the Windows computer (no matter which cable end is inserted first).
If ADB drivers are installed, "Android device" branch should appear in Device Manager, containing "Android Composite ADB Interface" and "Xiaomi Composite MDB Interface". Addionally, there should be "Portable devices" branch with "Redmi Note 3" device. If some drivers are not installed, install them.
Execute "adb devices" command to check if ADB connection is established.
If no devices are shown by ADB, wait a minute until "Redmi Note 3" device gets the "!" mark. Repeat "adb devices" command.
If "Redmi Note 3" device is not marked by "!" after a minute and ADB does not list the phone ID, try to disable "Redmi Note 3" in Device Manager.
As the phone ID becomes listed by ADB, execute "adb reboot edl" command.
Click to expand...
Click to collapse
Keep repeating "adb devices" until it reports connected.
Thought this deserves a thread of it's own. If anyone tried to get to EDL via volume buttons, will probably know how difficult it is.
not working
Redmi note 3 , screen on while put to charging, I tried to start mobile , by pressing Volumn + , volume - & Power buttons simultaneously, tried several times but unable to start mi note 3
Hi all you good people, I have a nexus 4 with a bootloop also additional problems are:
1. Im a complete novice and can only do things with simple instructions (sorry!)
2. No debugging mode was enabled
3. I only have a Mac
4. The Mac is not showing the device with the android transfer app and also I've tried a few things in terminal - but again comes up with device not found.
I can get to the Postboot mode by pressing the power/volume buttons so thats okay, on that screen it says: SECURE BOOT - enabled & LOCK STATE -locked
I have tried all the clear cache/restore factory on the recovery screen and taken the battery out for a while but to no avail.
thanks in advance!
You should unlock the bootloader and then flash a stock Google image. Unlocking the bootloader will wipe all data on the phone.
First thing would be to at least get the phone to recognize fastboot commands. Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=1917237
audit13 said:
You should unlock the bootloader and then flash a stock Google image. Unlocking the bootloader will wipe all data on the phone.
First thing would be to at least get the phone to recognize fastboot commands. Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Thankyou that is really helpful how ever when I type in: ./adb devices it dosnt list any devices including my phone, if I try a command such as:
./fastboot oem unlock
it just hangs on: "waiting for device"
The USB cable is good as I tried it with another device - could it be a damaged USB female socket on the device itself?
thanks
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
audit13 said:
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
Click to expand...
Click to collapse
Thanks when you say 'fastboot' mode - how do I get it in that mode?
audit13 said:
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
Click to expand...
Click to collapse
is there a command line I can input for fastboot?
nexus4uk said:
is there a command line I can input for fastboot?
Click to expand...
Click to collapse
Fastboot mode is when you boot into the bootloader where it said secure boot enabled.
Sent from my Nexus 4 using XDA Labs
To enter fastboot mode on the phone, power off the phone, press and hold volume up + volume down + power at the same time.
audit13 said:
To enter fastboot mode on the phone, power off the phone, press and hold volume up + volume down + power at the same time.
Click to expand...
Click to collapse
Thanks tried this - and and nothing came up with the command 'fastboot devices' - thanks anyway
If nothing comes up when executing the command, that tells me the drivers are not installed or the connection between the phone and computer is not good.
HI
How can I install the drivers on a mac? thanks
This may help: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
hi
While working with the device, it reset without prior warning, and since it trying to start and when the Google logo disappears and the animation stage arrives, 3 seconds later it turns himself off.
I entered into the Recovery mode and cleaned Cash - did not help
I thought to take out the battery in case something might be stuck in my memory but I still have not done it because when I dismantled the small panel (on the part of the camera) I accidentally turned on the device and it showed me that it upgrades the apps, which was a good sign for me so I closed the panel and waited for it to finish The 147 applications. At the end he turned himself off
I did not proceed with the matter of dismantling the battery.
I have the default recovery, I did not install recovery applications that expand the possibilities in the recovery mode.
and i don't remember if i turned on the USB debugging.
I decided to transfer the files (pic's, whtsapp) by ADB befor i try the factory reset
but I get sideload instead of recovery
C: \ adb> adb devices
List of devices attached
R ********** sideload (I changed the stereo to asterisks)
and every command I try to run I get
error: closed
Does anyone have an idea of how to copy files or repair the system ?
thanks
You should be able to bring it to fastboot mode by powering it off, then holding Power, Volume up an Volume down until the robot appears.
From there you should see the device with "fastboot devices". You might need to install some drivers at that point.
When in fastboot you should be able to start TWRP with "fastboot boot twrp-3.1.1-0-manta.img". When in TWRP you can see /sdcard in Windows or you can start Advanced > File Manager and copy your data to a USB stick.
thanks bornheim2
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night
so my guess is that my battery is bad.
can i use usb a male to usb a male adapter
or Hittime smart 3 in 1 Micro USB OTG/Sync/Charging cable
( i can't put links )
to connect the device with OTG to the computer for power and for transfer data to the computer ?
thanks
[email protected] said:
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night so my guess is that my battery is bad.
Click to expand...
Click to collapse
You should see the device in Windows when TWRP is running (and the device is charged by the PC). That should be enough to save your files.
i don't see it on windows (computer)
[email protected] said:
i don't see it on windows (computer)
Click to expand...
Click to collapse
That might be a driver problem. Do you see it in Device Manager on Windows? Probably with a yellow triangle?
it's good in the devices manager "Android Bootloader Interface"
but after the TWRP it upload, the devices no longer appears in the device manager
and the screen is still blinking
when i run the "fastboot boot twrp-3.1.1-0-manta.img"
it turn in the device manager to "Android ADB recovery interface" and after 1 sec is disconnect
I want to install the AOSP on the x compact.
I unlocked the bootloader but when I type
Code:
adb devices
no devices is recognized. I installed the fastboot tool too. I booted into fastmode with holding the volume up button when connecting but no device is recognized. I also factory reset the phone without luck to run the
Code:
fastboot
Maybe you need to allow your computer when it's asked on the phone.
evilorb said:
Maybe you need to allow your computer when it's asked on the phone.
Click to expand...
Click to collapse
what you mean when is phone is fast boot there has no display controls
Do it when the phone is ON, just after the USB debugging option is ticked, put your cable and the box for computer authorization will appear on the phone.
Don't know the way to do it when a phone is off.
evilorb said:
Do it when the phone is ON, just after the USB debugging option is ticked, put your cable and the box for computer authorization will appear on the phone.
Don't know the way to do it when a phone is off.
Click to expand...
Click to collapse
I authorized the phone but still not able to run fastboot commands when I go into fastboot mode with the blue led
But now you see your phone in terminal when you type "adb devices" ?
evilorb said:
But now you see your phone in terminal when you type "adb devices" ?
Click to expand...
Click to collapse
in the normal system mode then I can see it but not in the fastboot mode
Adb won't work in fastboot mode. Try "fastboot devices" when in fastboot mode.
When phone is turned off and connected via usb (vol+) to pc then type:
fastboot devices
When phone is turned on and connected via usb to pc (usb debugging on) then type:
adb devices
I want to unlock the bootloader of my phone using the unofficial method. I reboot my phone into fastboot mode using "adb reboot bootloader" and plug my phone to my laptop. Fastboot detects my devices, however, when I try to execute any command, for example "fastboot reboot", the command hangs. There is no output and I can't send a SIGINT signal to it either by pressing Ctrl+C. It should actually reboot my phone instead of hanging. Also, sometimes my phone would just display "Press any key for shutdown" right after I plug it to the laptop (similar to what's happening here). I tried running same commands on my old Zenfone Selfie (Z00T, ZD551KL) on fastboot and they work fine, I could even flash a custom recovery with no issues.
My system parameters:
Processor is Intel Core i5-8250U.
Operating system is Ubuntu 20.04 LTS.
ADB and fastboot versions are 1:8.1.0+r23-5ubuntu2 each.
My phone's firmware is PKQ1.WW_Phone-16.2017.1912.060-20191125
So far I've tried:
Changing the cable I use to connect my phone with my laptop. No results.
Changing the port I connect my device to from USB 3.1 to USB 2.0. No results.
Using a different fastboot version (the one that came with the unofficial bootloader unlock method). Nothing either.
Using a Windows 10 virtual machine, connecting my phone to it and executing fastboot commands there. No results either.
Updating my phone's firmware to 087, also Pie version. No results either.
Updating my phone to the beta version of Q, 438. No results.
Unplugging the phone during the process of command hanging and then plugging it back. Results vary. Sometimes it takes exactly 3.02 seconds and it does nothing, sometimes it would display the aforementioned "Press any key for shutdown" message.
Executing the command on my laptop and then plugging my phone in. Same as the previous point.
Executing "fastboot oem device-info" instead, using a method described in the previous point. It says "FAILED (remote: unknown command)"
Rebooting my phone to fastboot mode with Volume Up + Power and through recovery mode. No results.
Any idea what could be the issue and how do I solve it? Since ASUS stopped supporting our device, I would really like to unlock the bootloader of my phone so I could install custom ROMs.
Thank you for your time.