Database Users

Need help with ADB on a mac

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!

[Q] Can't boot. Stuck on Google logo

Hi,
I really need some help on this one. I wiped everything using TWRP recovery in preparation of installing a custom ROM.
I then realised I forgot to transfer the custom rom to my phone! When I went to reboot the system it says "No OS installed! Are you sure you want to reboot?"
No it's stuck on the google logo.
Is there a way to see if any Rom is still installed on on my phone or if it deleted my stock rom also?
I tried to push the rom through adb but it says error read only.
Also USB debugging is not enabled but I can't boot to enable it.
Please help.
Thanks

Go into fastboot and ensure your fastboot devices command shows your s/n. If so then grab the stock image from xda and flash it.
fastboot flash bootloader BOOTLOADERNAME.img
fastboot reboot-bootloader
fastboot flash radio RADIONAME.img
fastboot reboot-bootloader
fastboot -w update IMAGENAME.zip
Alternatively, using ADB.
from command prompt: adb remount
adb push <FILE PATH> /sdcard/0/
Boot into recovery (I use CWM) and then install it.

Thanks for the quick reply.
I managed to solve it by using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2010312
It's all in fastboot so I had no problems
Problem solved.

[Q] ADB sideload & fastboot not working

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?

Stuck loading twrp

Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks

This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
redirts1978 said:
Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks
Click to expand...
Click to collapse

HELP!!!! cant get my phone to be recogniced by adb, I have the same problem,
if its on TWRP boot screen or RECOVERY (blue downloading.... screen) its the same!!!
please help
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse

i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME

Kackwuerstchen said:
i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME
Click to expand...
Click to collapse
I don't know what are you doing wrong but when I was stuck in this situation, I flashed stock firmware from sammobile and it fixed the problem.
Make sure you downloaded correct firmware.

Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse

dankovac1999 said:
Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
Click to expand...
Click to collapse
Same problem and question here

OnePlus 8 TMO Magisk boot image IN2017_11_C.43

It took a bit of work to root OnePlus 8 T-Mobile version on the latest Android 12 update. I am a long time lurker and simply I wished someone else had posted the boot image to save me time. Can be simply flashed using fastboot commands.
Please check to make sure you are on the latest update from T-Mobile and that software version is: IN2017_11_C.43 Android 12 Security update November 5, 2022.
Installation instructions:
*You must have your phone unlocked for any carrier otherwise OEM unlocking will be unable to set.*
#1 go to settings, about device. TAP software version five times to enable developer options under system settings. Go to developer options and tick the following options:
a OEM Unlocking
b Enable USB debugging
#2 Download the OnePlus 8 Windows drivers and ADB fastboot drivers if your using a PC or Termux from F-Droid if using another rooted phone.
PC instructions:
Go to the directory you installed ADB and Fastboot. Open the command prompt by either right click on an empty space in that folder and finding command prompt or going to the directory tree and typing cmd and hit enter. Inside the Windows command prompt the root directory should be the same folder as your ADB and fastboot executables. Move the attached boot image to the same folder as your ADB and fastboot executables and rename it boot.img. Attach your phone to your PC and run the following commands:
adb devices
This command is so you can check to see if your PC is correctly configured and it should send you a notification on your phone to allow debugging from your PC, make sure you will allow it always.
adb reboot fastboot
This command will reboot your phone into fastboot mode. Do not select any you on your phone and only type in the following commands on your PC.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This command will flash the magisk modified boot image which will grant you root access to your phone.
fastboot reboot
This command will reboot your phone. Congrats, your now rooted on the latest Android 12 update for your T-Mobile Oneplus 8!

what attached boot img?

zeromonarch said:
what attached boot img?
Click to expand...
Click to collapse
I must've somehow missed it too. I cant find any boot image to download

If only there were the elusive boot image...
It could have saved my ass from the current double-slotted brick I sit upon!

Does anyone have the boot image for the latest T-Mobile update?
IN2017_11_C.45
in fact this isn't even the latest as there is a new update waiting for me with the new security release or security update but I haven't updated yet also does this wipe data?