I can only boot an twrp img using windows machines. I only have one just for this reason. Can anybody give me insight on how to get it working on my linux machines. ADB and Fastboot are installed on the linux machines and adb works. The phone is recognized in adb and fastboot but when I try to boot a twrp image in fastboot it puts the phone in fastboot mode but the pc hangs at "waiting for any device". I can access all the info on the phone and can write files to the system storage. Just can't get fastboot to work.
Related
I'm trying to install baconbits on my G2 and I have a mac. I cannot seem to get the recovery image to work through fastboot. Help?
I can access the phone through the terminal but once I command it to reboot to the bootloader I can't get it to find the img file
There's a fastboot binary available for download from this page: http://developer.htc.com/adp.html
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
pak256 said:
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
Click to expand...
Click to collapse
You can flash files from recovery if they are on the SD card. You can either adb push while in recovery, or mount USB storage and tranfer the file. Or just transfer it via USB while the phone is on (big, green android screen)
I'm not sure how to install baconbits, but I think you need fastboot to flash the .img file. Recovery flashes .zip files and fastboot flashes .img files. You can put fastboot-mac in the same folder as adb... then fastboot flash recovery your_recovery.img. You really don't need adb (for this) since you can boot into fastboot on the phone by restarting while holding down the trackpad button.
These might be the droids you are looking for...
Code:
adb (read the instructions)
adb devices (you'll see your phone if it's plugged in, turned on, and in the proper mode)
adb reboot bootloader (white screen with androids on skateboards)
fastboot-mac (more reading...)
fastboot-mac devices (your phone again)
fastboot flash recovery your_recovery.img
fastboot reboot-bootloader
For some reason, I had a little trouble flashing my recovery- sometimes it would hang and wouldn't flash, sometimes it would only fastboot boot. So if you run into trouble, there might be other problems.
While you are at it, you might as well save yourself the trouble and either add the adb and flashboot folders into your path, or put the binaries somewhere in your path. I also renamed fastboot-mac to fastboot for simplicity.
Going to try that when I get out of class but I think you helped me realize what I was doing wrong. Thanks and will let you know if it works
Sent from my T-Mobile G2 using XDA App
Okay I could get the fastboot prompts to work but when I try to flash the recovery it tells me "g2recovery.img" could not be loaded
okay, used clockwork and got it to work. yay!
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
I have some important files that I forgot to backup and was suddenly hit by the BLOD.
Is it possible to retrieve files from my device that is stuck on bootloop?
Details:
Device is rooted
I have the ability to run fastboot commands
TWRP not installed
Android version: 7.1.1
I tried to install TWRP using fastboot command and boot into recovery but all it did was restarted the device and continued with the bootloop.
I am able to run fastboot commands and see my device using "fastboot devices".
However when I try running "adb" commands, I get the error "no device/emulators found". Is this normal?
TIA
As long as I know, you can't use ADB commands in bootloader.
To use ADB, you should enter Android os, or at least recovery.
So it's normal that adb doesn't recognize your device in bootloader.
I wanted to install a custom rom for my moto g4 and I just have problems with installing twrp. I downloaded twrp img and adb tools, then connected my phone to the pc in debug mode. In the adb console, the phone is displayed, but when I put the phone in the fastboot mode, it is not recognized.
that's cos there's separate program (e.g. fastboot) for interfacing with bootloader (c.f. Android Debug Bridge for interacting with recovery or Android).
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it
Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode
FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.
When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.