I'm trying to root a pixel (sailfish). I'm able to find the device in adb, but when I go into bootloader, the device isn't there. I'm mostly trying things on my Mac, which I used to successfully root a Nexus 7, but I also had the same issue on a Raspberry Pi. What's more is that I have a Verizon Pixel, which is detected in bootloader (but I can't root it since it's Verizon), and the problematic Pixel in bootloader isn't even registering as a connected USB device when I use the command, "system_profiler SPUSBDataType". Anyone have any advice?
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I’ve tried that. It doesn’t show anything.
I have spent months trying to figure out how to get TWRP flashed on my Pixel Phones (I have 2 of them). I have searched & read many links on this forum and can't find any firm details/directions on how to get TWRP on a pixel. From https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ it appears I should of installed TWRP on the factory image first, but I went to Lineage a couple years ago on Android 9 & this was not an option back then.
Both phones have the two latest version of Lineage OS, Both Devices are UNLOCKED, Both have Developer Options Enabled, and on my Windows PC I have the latest version of SDK tools & drivers installed.
Plugging into the PC is done with a a tested/good USB cable plugged into a USB 2 Port. Here is what I am seeing with LinageOS running:
adb devices shows List of Devices Attached
FA77LO302202 device
After executing - adb reboot bootloader
adb devices -> shows an empty list, hence doing a -> fastboot devices shows no devices.
Going to Recovery Mode in Bootloader list of devices shows:
FA76F0303478 unauthorized
In Recovery Mode -> Advanced -> Enable ADB list of devices shows:
FA76F0303478 recovery
I can Apply Update in Recovery Mode via Sideload, but that does not help me get TWRP flashed.
With no devices showing in the main bootloader via adb I can't get the phone into autoboot mode. Per the link at android.gadgethacks.com in order to put the Factory Image back on the phone, https://developers.google.com/android/images, I need to get the phone into autoboot mode.
Anyone have any ideas????
Come-on guys & gals. I'm sure someone can help me at XDA get my devices to fastboot.
Related
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
My K7 is T-Mobile LG-K330, Android 5.1.1, kernel 3.10.49, Build LMY47V, vers K33010j
I have searched and tried many root guides. All end the same way. This isn't new for me as I have rooted and installed mod roms on several phones and a tablet.
The main problem seems to the phone will not show as connected to the root tools. I have triple checked the developer mode ena and usb debugging ena and tried OEM unlock both ways.
I have the latest (as of today from XDA, minadb and kingroot (PC)). Both are installed on my Win10Pro comp.
The phone USB drivers must be in place as I can plug in the usb and the K7 comes up in the This PC list and I have access to the folders. I must be missing something.
adb devices -l
daemon starts but no devices are listed
fastboot devices
none listed
kingroot
all is well up to the point where it tries to "connect" it just fiddles in circles
I waited 15 min and Xed out.
This may be related: I cannot boot to the recovery screen. No matter how I hold the power and up volume I always get the T-Mobile screen and android.
Has anyone seen this or have any suggestions?
Happy Trails
I had similar problems with my K7.
I had to download a different minimal ADB / Fastboot tool from http://forum.frandroid.com/topic/246460-root-and-recovery/ .
Once the bootloader was rebooted the phone had on-screen instructions.
Use this https://forum.xda-developers.com/lg-k7/how-to/t-mobile-lg-k7-thread-t3481844 and the site above for instruction.
Put your recovery twrp-image-3.img and the SuperSU.zip on a micro sd and insert it in your phone before you start.
Also put the twrp-image-3.img in the ADB program folder on your computer.
Once the bootloader is unlocked, instead of typing: fastboot flash recovery twrp-image-3.img .
Type: fastboot boot recovery twrp-image-3.img or fastboot boot twrp-image-3.img (I don't remember) (only one will work).
Then once in twrp install the recovery ( twrp-image-3.img ) and then the SuperSU.zip from the SD card.
Also make sure you check the box and allow your computer permission to connect to your phone when you first connect them, after you enable usb debugging on you phone.
Good Luck.
I have this phone and now it wont boot. Im thinking there is no OS to boot. It tries and says DM varity disabled at top of screen then says software cant be checked for corruption /bootloader unlocked. When in bootloader there is no recovery to boot into as well when plugged into desktop . ADB devices command is not seeing it. So my question is where do I start to install recovery and make PC (adb/fastboot) recognize device. If I could get adb to identify device shouldn't I be able to fastboot boot (twrp-disc.img) then flash twrp.zip then reboot bootloader and flash factory ROM and kernel or custom? Hate if I sound like a noob im learning all I can. Any help is greatly appreciated!
ADB, Fastboot & Recovery are 3 completely things independent from each other:
ADB program deals with Android OS ( folders / files / settings )
Fastboot program deals with device's bootloader
Recovery is a special bootable partition on device, which contains a recovery application installed in it
If
Code:
adb devices
doesn't show you a connected "device" then either USB debugging isnt enabled or Android OS isn't accessable at all or Android's USB service isn't set to "adb"
If
Code:
fastboot devices
doesn't show you device's mode as "fastboot" then device's bootloader isn't accessable at all.
Back to your "issue", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader & disabled "dm-verity" will boot with those warning, so nothing to worry about, and , at the moment it's not possibile to remove those warnings.
When Fastboot is working, then you should be able to boot device into a Custom Recovery, of course only if that is at 100% suitable to the device.
Hi all,
Just bought yesterday this phone and after doing typical actions like android config (oem, debugging, etc.), installed adb and fastboot. PC recognized command adb devices and shows the phone but when I reboot to fastboot mode, it stucks and the device manager shows unknown android.
Have read all the tips here, forums, youtube, etc. but no way. Tried in 2 different computer with same results. Installed last android studio with sdk manager, same error. Installed oneplus drivers and also the same.
Even I have tried a different cable but no success at all.
This is so frustrating situation, ever more considering that I'm not newbie at this (years ago always changed rom every month and smartphone every 2 months).
Any advice? Format pc? Install other windows in other partition?
Or selling the phone and buying another brand
spamerobaldomero said:
Hi all,
Just bought yesterday this phone and after doing typical actions like android config (oem, debugging, etc.), installed adb and fastboot. PC recognized command adb devices and shows the phone but when I reboot to fastboot mode, it stucks and the device manager shows unknown android.
Have read all the tips here, forums, youtube, etc. but no way. Tried in 2 different computer with same results. Installed last android studio with sdk manager, same error. Installed oneplus drivers and also the same.
Even I have tried a different cable but no success at all.
This is so frustrating situation, ever more considering that I'm not newbie at this (years ago always changed rom every month and smartphone every 2 months).
Any advice? Format pc? Install other windows in other partition?
Or selling the phone and buying another brand
Click to expand...
Click to collapse
Did you select always allow from this computer after enabling debugging and plugging your phone into computer when phone was booted and running(not in recovery or fastboot. Also adb does not work in the bootloader only fastboot commands. Secondly search for the insecure modded stock recovery if you want to do adb access commands in recovery. There is also a fastboot d mode on our phones which look like recovery but you can flash all partions via full fastboot to get to fastboot d your phone has to be on then you type adb reboot fastboot
toolhas4degrees said:
Did you select always allow from this computer after enabling debugging and plugging your phone into computer when phone was booted and running(not in recovery or fastboot. Also adb does not work in the bootloader only fastboot commands. Secondly search for the insecure modded stock recovery if you want to do adb access commands in recovery. There is also a fastboot d mode on our phones which look like recovery but you can flash all partions via full fastboot to get to fastboot d your phone has to be on then you type adb reboot fastboot
Click to expand...
Click to collapse
finally solved!! thanks mate
spamerobaldomero said:
finally solved!! thanks mate
Click to expand...
Click to collapse
No prob
Hi!
I'm still on my way ro root my Samsung Tab SM-T725, after upgrading to Android 11. Before Android 9 was on the device, succesfully rooted via Magisk. Updating and keeping the root status didn't work properly, the flashing process in Odin failed. Therfefore I had to flash the latest stock recovery, successfully. So now I have Android 11 on my device but no root. The bootloader is open and USB debugging enabled.
I tried the method described here. But the flashing in Odin failed again. So now I try to follow the instructions on the Magisk website. If I get everything right a processed recovery.img has to be flashed via ADB/Fastboot. That's new to me and I have questions.
- Is fastboot and download/recovery mode the same? Booting to the recovery and following "reboot to bootloader" leads to the turquois "Downloading" window. The same occurs when prompting "ADB reboot fastboot" e. g. Again the mentioned Downloading window shows up, nothing (special) with fastboot. Is that correct?
- Will therefore all fastboot commands not work? And only ADB is possible on my tablet? Is that common for Samsung devices?
- Can the flashing of the patched recovery.img (for Magisk) be done with ADB as well? Instructions always mention fastboot.
- My device doesn't show up in ADB when being in recovery mode. In normal mode it is listed when entering "ADB devices". Trying again in recovery mode the list stays empty - and all other commands have no effect. Current Samsung and Google USB drivers are installed. How could that be solved? Without ADB (perhaps fastbood) running in download mode I shouldn't be able to flash (and root the device) as planned.
I hope I described everything properly. I'm not that Android expert - but successfully managed to root a couple of devices over the years.
Samsung devices dont know of Fastboot mode. But you can run them in either Recovery or Odin / Download mode or Normal mode.
Running Samsung devices in Download mode you can flash ROM or update system in the Android device. When the Samsung device has entered Download mode, the device will boot from external sources. You can also make the stock ROM replaced in Download mode.
ADB mode is the Normal mode.
In Recovery mode ADB - with some exceptions - isn't working
Because your device is a Samsung one the Google USB drivers are senseless. Remove them to avoid conflicts.
Thanks for the quick and helpful response!
That makes clear why the tablet didn't show up in ADB. And that all rooting efforts for Samsung devices via that way should be obsolete. Strange enough that Magisk doesn't mention this on their instruction site.
So I'll have to try on with flashing a patched AP via Odin - and hope for a solution for my fail-problem.