Unable to detect Android device with ADB on Mac but can detect it through Fastboot?

I am unable to view my Android device, an Oppo Find7, with ADB. I can view it with Fastboot. As I use a Mac, I followed this guide to install ADB and Fastboot.

More generally, I am having issues with my phone which is stuck on boot-loop and I can only access Fastboot (no bootloader or recovery working). I’m hopeful I can fix this once I get ADB working again! But if anyone knows if I can get the Oppo unbricking tool for Mac I would be very grateful 🙂 I’ve only found it for Windows, and unfortunately, the official Oppo support forums no longer exist.

Typing

Fastboot getvar all 

gives me

 All:     

Not a good sign I think.

Thank you!

How do I install OS in Andriod phone without using fastboot and TWRP?

I’ve tried to upgrade the rom in MOTO G4 Plus using TWRP version of 3.2.1.0 and during installation process I wiped out the existing android 7.0.1 without backup(understood the cost of backups now). As I faced error while installing android 9.0.1 with error 255 code because of TWRP some upgrade issue couldn’t complete the installation process successfully.

I tried multiple ways to upgrade TWRP which was not successful and even fastboot commands aren’t working now. Whenever I try fastboot + combinational command like devices and etc it goes into an infinite loop with an error code iterator not found. After a good amount of search found about ADB and happily can connect to my device using ADB now. Then started trying with multiple options like adb side load after reading multiple forum answers and posts I did pushed a rom to scared/data/media after reading this forum NEED HELP: Accidentally deleted OS in TWRP/Cant install Rom which was successfully pushed but didn’t do any thing nor I couldn’t understand what to do after pushing it.

Then started search again to install stock rom in any different ways before coming here and stumbled at this question which is similar did read the question and included forum post in it to go start the process when I did download stock rom stock rom download couldn’t find any flashall.sh file to start the process

Now I’m stuck and couldn’t find better place to find a working solution for this situation. Can somebody help me? What can I do while my phone is in this state?

What is CSC Fastboot Mode, and how to get rid of it?

I am trying to access my Zenfone Go’s fastboot in order to unlock its bootloader, but it seems to have been replaced with something called “CSC Fastboot mode”.

In this mode, I just see the ASUS logo, a “CSC Fastboot Mode!” text, and I am unable to enter any input. It looks like this:

https://i.ytimg.com/vi/fGvKbRoB8b0/maxresdefault.jpg

Since I cannot enter any input, most communication with fastboot.exe is impossible. I somehow managed to have fastboot.exe correctly detect the device, but any command that requires confirmation on the phone is impossible (ex: fastboot flashing unlock), fastboot.exe just waits forever. I tried inputting the commands on the phone anyway, in case there was an invisible menu or something, but didn’t work.

What I tried:

  • Turning off my phone, then “Power Button + Volume Up Button” until it restarts. It goes directly to CSC Fastboot Mode.

  • Turning off my phone, then “Power Button + Volume Down Button” until it restarts. It goes into Recovery Mode. Then I select “reboot to bootloader”. It goes to CSC Fastboot Mode.

  • Accessing my phone through adb, and using the “reboot-bootloader” command. It goes to CSC Fastboot Mode.

What is CSC Fastboot mode? What is it caused by? And how to reach a usable fastboot menu?

Model Number: ASUS_X013DB

Android Version: 5.1.1

Build Number: LMY47V.JP_Phone-13.0209.1705.116-20170621044040677_2015122901270020000400001

lenovo a6010 fastboot when trying to flash

I want to root my device(Lenovo a6010),am now trying to install TWRP but fastboot can’t see my device when I try to flash the image, even though “fastboot devices” yields my device. Usb debugging enabled and “adb devices” also yields the expected output when not in bootloader. What should I do? Is there perhaps some kind of driver I haven’t installed?

C:\Users\User\Downloads\TWRP\tools>fastboot devices 1415547b        fastboot C:\Users\User\Downloads\TWRP\tools>fastboot -i 0x17ef flash recovery C:\Users\User\Downloads\TWRP\img\twrp.img < waiting for any device > 

Nexus 5 stuck on OS loading animation, pressing Volume-/Power only shows fastboot for a second, adb shows nothing

This is the normal LineageOS loading screen, which I had until yesterday:

enter image description here

Problem: Since yesterday, only one circle is going from right to left, forever. In other words, it never reaches the 3 circles (even after 8 hours overnight), and my Nexus 5 has become useless.

After reading Nexus 5 stuck on "flying color dots lollipop" screen after Hard Factory Reset I tried pressing Power/Volume- at the same time for 30 seconds. Result: It makes the fastboot screen appear for less than a second (during that split second I can move the cursor with Volume+/-), then the screen turns black, then fastboot for a split second again, then this boot-loop:

  1. white Google+unlocked lock on black background, for a few second
  2. black screen
  3. Vibration
  4. Back to step 1

Pressing the same Volume-/Power during the earlier “white Google+unlocked lock on black background” screen results also results in the same boot-loop.

During all of these phases (animation, fastboot, boot-loop), running adb logcat from my connected computer only shows waiting for device.

I am performing all of this with the charger plugged in. I even changed the battery to make sure it was not a power problem. To check I managed to quickly push “Power off” in fastboot and it shows the battery level: 100%.

The computer/port/cable I am using are the ones that I have been using everyday for years to transfer files and debug apps over USB. I also tried a wall charger and new cable too to make sure, same result.

After plugging the phone into a Windows conmputer (instead of my usual Linux), fastboot miraculously stayed on, and I was able to get the following information:

Partitions

~ # cat /proc/partitions major minor  #blocks  name   179        0   30535680 mmcblk0  179        1      65536 mmcblk0p1  179        2       1024 mmcblk0p2  179        3        512 mmcblk0p3  179        4        512 mmcblk0p4  179        5        512 mmcblk0p5  179        6        512 mmcblk0p6  179        7       2048 mmcblk0p7  179        8       1024 mmcblk0p8  179        9        512 mmcblk0p9  179       10        512 mmcblk0p10  179       11        512 mmcblk0p11  179       12       3072 mmcblk0p12  179       13       3072 mmcblk0p13  179       14        512 mmcblk0p14  179       15      16384 mmcblk0p15  179       16      16384 mmcblk0p16  179       17       3072 mmcblk0p17  179       18      22528 mmcblk0p18  179       19      22528 mmcblk0p19  179       20      22528 mmcblk0p20  179       21       3072 mmcblk0p21  179       22        512 mmcblk0p22  179       23        512 mmcblk0p23  179       24        512 mmcblk0p24  179       25    1048576 mmcblk0p25  179       26      30720 mmcblk0p26  179       27     716800 mmcblk0p27  179       28   28551146 mmcblk0p28  179       29          5 mmcblk0p29  179       32       4096 mmcblk0rpmb 

Mount

~ # mount rootfs on / type rootfs (rw,seclabel) tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755) devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,seclabel,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) tmpfs on /tmp type tmpfs (rw,seclabel,relatime) /dev/block/mmcblk0p25 on /system type ext4 (ro,seclabel,relatime,data=ordered) 

Block names

~ # ls -l /dev/block/platform/msm_sdcc.1/by-name lrwxrwxrwx    1 root     root            21 Jan  1 01:00 DDR -> /dev/block/mmcblk0p24 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 aboot -> /dev/block/mmcblk0p6 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 abootb -> /dev/block/mmcblk0p11 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 boot -> /dev/block/mmcblk0p19 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 cache -> /dev/block/mmcblk0p27 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 crypto -> /dev/block/mmcblk0p26 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 fsc -> /dev/block/mmcblk0p22 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 fsg -> /dev/block/mmcblk0p21 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 grow -> /dev/block/mmcblk0p29 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 imgdata -> /dev/block/mmcblk0p17 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 laf -> /dev/block/mmcblk0p18 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 metadata -> /dev/block/mmcblk0p14 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 misc -> /dev/block/mmcblk0p15 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 modem -> /dev/block/mmcblk0p1 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 modemst1 -> /dev/block/mmcblk0p12 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 modemst2 -> /dev/block/mmcblk0p13 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 pad -> /dev/block/mmcblk0p7 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 persist -> /dev/block/mmcblk0p16 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 recovery -> /dev/block/mmcblk0p20 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 rpm -> /dev/block/mmcblk0p3 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 rpmb -> /dev/block/mmcblk0p10 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 sbl1 -> /dev/block/mmcblk0p2 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 sbl1b -> /dev/block/mmcblk0p8 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 sdi -> /dev/block/mmcblk0p5 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 ssd -> /dev/block/mmcblk0p23 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 system -> /dev/block/mmcblk0p25 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 tz -> /dev/block/mmcblk0p4 lrwxrwxrwx    1 root     root            20 Jan  1 01:00 tzb -> /dev/block/mmcblk0p9 lrwxrwxrwx    1 root     root            21 Jan  1 01:00 userdata -> /dev/block/mmcblk0p28 

Filesystem

~ # blkid /dev/block/mmcblk0p28 /dev/block/mmcblk0p28: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" 

Wiping cache

~ # twrp wipe cache Formatting cache using make_ext4fs... Failed to mount '/cache' (Invalid argument) Done processing script file  ~ # mke2fs -t ext4 /dev/block/mmcblk0p27 mke2fs 1.42.9 (28-Dec-2013) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 44832 inodes, 179200 blocks 8960 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=184549376 6 block groups 32768 blocks per group, 32768 fragments per group 7472 inodes per group Superblock backups stored on blocks:         32768, 98304, 163840  Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done  ~ # twrp reboot command is: 'reboot' and there is no value Failed to mount '/data' (Invalid argument) Failed to mount '/data' (Invalid argument) E:a Done processing script file 

Doing that cache wipe did not solve the problem, unfortunately.

Question: How to at least get the content of my Nexus 5’s /sdcard saved to a computer? Or maybe even fix the Nexus if possible?

Fastboot failed with (data transfer failure (No error))

Sorry for newbie question,

I’m running fastboot on windows and sometimes fastboot returns this error

FAILED (data transfer failure (No error)) 

and when it get this error it continue to send this error until I reboot the PC and re-run it again.

C:\>fastboot.exe -s tcp:192.168.1.73 flash system_i C:\system.img target reported max download size of 268435456 bytes erasing 'system_i'... OKAY [ 60.543s] sending sparse 'system_i' 1/2 (262140 KB)... FAILED (data transfer failure (No error)) finished. total time: 86.195s  C:\> 

Note: it usually happen on large files, but when it happen, it also fails on all other files including small ones until I reboot the PC.

I have not encounter this problem on Linux, it seems it’s specific to Windows version, probably fastboot itself or windows setup. (different fastboot version tried).

I search and did not find any complain for this kind of error!

Note: fastboot downloaded from internet. https://developer.android.com

Lg Aristo 2 Fastboot flash recovery – FAILED (remote: ‘unknown command’)

I’ve recently been trying to flash twrp on my Lg Aristo 2, when I ran the code to OEM Unlock a device it came out with the same “FAILED (remote: ‘unknown command’)”. I started my phone back up and it came to a set up screen, I set up my phone and it said it was OEM Unlocked. When I try to flash a custom recovery, or run any command with fastboot at the beginning i get “FAILED (remote: ‘unknown command’)” and it doesn’t work. Can someone please help?

LG K20V Stuck in Fastboot Mode

My LG K20V is currently stuck in fastboot mode. I’ve run the ADB/Fastboot tool, via the Windows 10 command line prompt.

The Fastboot Devices command recognizes the device. The Fastboot Reboot command says it has run successfully. However, the phone does not reboot.

Any help with figuring this out will be appreciated!