So I want access the TWRP through fastboot command( since volume up + power botton wont work) but it's not reconizing the device.
I have USB debug on and I don't know if i have OEM unlock mode on because I can't find it in the developer tab.
I only want to root the device so I can install the google cam.
Any suggestions ?
Tiigs said:
So I want access the TWRP through fastboot command( since volume up + power botton wont work) but it's not reconizing the device.
I have USB debug on and I don't know if i have OEM unlock mode on because I can't find it in the developer tab.
I only want to root the device so I can install the google cam.
Any suggestions ?
Click to expand...
Click to collapse
RR should also have advanced reboot in developer options. You can than simply reboot into recovery.
Noter2017 said:
RR should also have advanced reboot in developer options. You can than simply reboot into recovery.
Click to expand...
Click to collapse
Thanks for the reply.
The problem is that I have no way of reaching TWRP , If I do the Power+ volume up I will go to the MI-recovery 3.0.
What I do is, I restart the phone and only hold down the volume up button after the screen goes black. That always gets me into TWRP. But I usually use the advanced power menu because that's way easier.
Fixed the fastboot not get recognized on my computer.
I had to disable driver signature verification. Then I installed the proper TWRP version. Now the Volume up + power goes strait to the TWRP.
I am just posting here someone might find useful.
ty all for the help.
Tiigs said:
Fixed the fastboot not get recognized on my computer.
I had to disable driver signature verification. Then I installed the proper TWRP version. Now the Volume up + power goes strait to the TWRP.
I am just posting here someone might find useful.
ty all for the help.
Click to expand...
Click to collapse
Did you forget to boot into your recovery.img after flashing TWRP via fastboot? "fastboot boot recovery.img". A lot of guides stupidly leave that out.
sk8223 said:
Did you forget to boot into your recovery.img after flashing TWRP via fastboot? "fastboot boot recovery.img". A lot of guides stupidly leave that out.
Click to expand...
Click to collapse
No my problem was that I could not even call fastboot through console because my computer wont recognize the device. If i called "fastboot devices" on the console it would not show any answer. Disabling driver signature verification made my computer recognize the smartphone usb , so all the fastboot commands worked as intended again .
You have driver problems, donwload the latest adb or install a virtual machine with Ubuntu or Debian, after that install android-tools-adb and android-tools-fastboot. Then connect your phone to the virtual machine and access adb from there.
Related
Good Afternoon Everyone !
I'm new to the XDA , but not a Newbie in the delevoping section.
Because of a hardware problem when i changed the display of my phone
my volume keys aren't working anymore.
Today I flashed the Beanstalk ROM from the user TH3Bill, but unusally it won't start.
So i got the problem right now that it wont boot and I'm stuck with the Motorola Logo,
because I can' get into recovery. Is there any option to get into recovery without the volume
buttons or fastboot ?
PS : sry for the bad english
If you can access adb you can type "adb reboot recovery"
jorno88 said:
If you can access adb you can type "adb reboot recovery"
Click to expand...
Click to collapse
tried it, but it just says that now device was found , but the device is listet in the device manager as adb device interface.
that seems correct, only way to go into recovery without volume is adb or fastboot or ofcourse rebooting into recovery...(as far is i know)
do you know how to use adb?
can you see your device listed when you type adb devices?
jorno88 said:
that seems correct, only way to go into recovery without volume is adb or fastboot or ofcourse rebooting into recovery...(as far is i know)
do you know how to use adb?
can you see your device listed when you type adb devices?
Click to expand...
Click to collapse
Not really, my firstime , but i used fastboot before . but for fastboot you have to go into the fastboot mode, and without wokring volume keys that isnt possible.
No when i type in adb devices, there is no device listed at all , just the line " List of all ADB devices"
First you have to activate android debugging in settings for adb to show ur device.
Secondly, even if u boot into recovery, u cannot use recovery without volume buttons unless you flash a touch recovery, for which I think u need to boot into fastboot which again needs volume buttons...
any other solution anyone?
Sent from my cm_tenderloin using xda app-developers app
sa.guly10 said:
First you have to activate android debugging in settings for adb to show ur device.
Secondly, even if u boot into recovery, u cannot use recovery without volume buttons unless you flash a touch recovery, for which I think u need to boot into fastboot which again needs volume buttons...
any other solution anyone?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I cant activate anything, i flashed a new Rom and then I got into a Boot Loop, and yes i have a touch recovery
Edit: I found some threads using adb in a Boot loop, is it possible that i have the wrong drivers ? i used two different mehtods but i can't update the adb interface driver
look
Method 1 :hxxp://atrix4ghacks.com/atrix-4g-hacks/how-to-install-atrix-4g-drivers/ this is where i got stuck
I also found a second with a package to extract which was accesable from the cmd, adb started but the phone wasn't rechable
Edit Edit: It worked with the officila motorola drivers, and the normal adb-tools , thx for your support
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.
Hello i wanted to ask about this since i dont see any other thread related to my issue, im trying to install magisk root and im at the stage of accessing fastboot/bootloader, when i go to recovery mode and select "reboot to bootloader" it just restarts the phone, i have tried adb commands didnt work either, same result, just restarts. The "unlock oem" option under developer options is enabled, i could flash another firmware of the same phone with SPD upgrade tool and its still not letting me get into bootloader, (to do this i must press down vol down and connect the usb while the program is on, and it is detected, otherwise it just restarts adb and fastboot tools will not detect it as download mode) any idea or suggestions on how I could root the phone, been thinking about twrp but not sure it would let me install that, looked into many pages about rooting this device and none show anything related maybe its not possible, i saw there are phones with blocked bootloader. the phone is android 9
Have you tried to
- flash the boot.img from the stockfirmware;
- install a recovery (twrp, orangefox, etc.) and rebooted to fastboot from recovery?
wenyendev said:
Have you tried to
- flash the boot.img from the stockfirmware;
- install a recovery (twrp, orangefox, etc.) and rebooted to fastboot from recovery?
Click to expand...
Click to collapse
TWRP and orangefox dont support my phone, there may be something unnoficial for twrp as i search and im not sure i can flash the phone with a specific boot file since to flash i use a single .pac file that contains the rom ill look into this
For now im not able to flash the phone with custom boot.img or recovery.img maybe i need to pack specific files i dont know about i give up for today
Sorry to hear that...
Have you tried the following command?
Apache config:
adb reboot bootloader
wenyendev said:
Sorry to hear that...
Have you tried the following command?
Apache config:
adb reboot bootloader
Click to expand...
Click to collapse
yes both that and adb reboot fastboot just restart the phone
Have you tried the method in the following page?
Hold volume up & power buttons. Otherwise, try volume down & power buttons.
How to get into fastboot and How to exit fastboot ZTE Blade A5 PRO? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
wenyendev said:
Have you tried the method in the following page?
Hold volume up & power buttons. Otherwise, try volume down & power buttons.
How to get into fastboot and How to exit fastboot ZTE Blade A5 PRO? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
This is not my phone model, its zte blade a5 plus 2020, vol up and power restarts the phone normally