Develop Bugs

[DISCONTINUED][GUIDE] [TOOL] Fix Broken Fastboot / Droidboot

Playing around with custom roms is very excited for our zenfone. Many of them have very glamour and shiny feature, performance, xposed etc.
But sometimes will make our zenfone brick, lost droidboot and bootloop if we not follow the procedure correctly.
I make a flashable droidboot to fix broken droidboot.
Important :
This flashable droidboot can execute only if you have a working twrp recovery.
Download
Procedure to flash :
1. Put this flashable droidboot on MicroSD
2. Boot twrp recovery
3. Choose Install
4. Pick Flashable Droidboot.zip
5. Swipe to install
Now boot your phone to droidboot to check if it fix.
Tested work on ZENFONE A500CG TOOF 3.24.40.87
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
Playing around with custom roms is very excited for our zenfone.
Many of them have very glamour and shiny feature, performance,
xposed etc.
But sometimes will make our zenfone brick, lost droidboot and bootloop if we
not follow the procedure correctly.
Now I make a flashable droidboot to fix broken droidboot.
Important :
This flashable droidboot can execute only if you have a working twrp recovery.
Download :
https://drive.google.com/file/d/0B0AFmAAcGS5xcE1rM1h5Mmo0VGc/view?usp=drivesdk
Procedure to flash :
1. Put this flashable droidboot on MicroSD
2. Boot twrp recovery
3. Choose Install
4. Pick Flashable Droidboot.zip
5. Swipe to install
6. Phone will reboot itself
Now boot your phone to droidboot to check if it fix.
Tested work on ZENFONE A500CG TOOF 3.24.40.87
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Nice but I have no idea what's the diff between fastboot and droidboot
Sent from my ASUS_T00F using Tapatalk

febry_valdy said:
Nice but I have no idea what's the diff between fastboot and droidboot
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
No diff, in kk they call fasboot but in lollipop they call droidboot
Sent from my ASUS_T00F using XDA-Developers mobile app

Is this unlocked?

farhankn said:
Is this unlocked?
Click to expand...
Click to collapse
Didnt understand what are you talking about

farhankn said:
Is this unlocked?
Click to expand...
Click to collapse
It said that u have to install it from twrp recovery, I think when U install a custom recovery you have to unlock bootloader first, so the answer is yes
Sent from my ASUS_T00F using Tapatalk

yep, i didnt read that..
sorry
---------- Post added at 05:42 PM ---------- Previous post was at 05:32 PM ----------
yep, i didnt read that..
sorry

is it working on custom rom?
Sir I'm using big rom 12.6 & whenever I tried to boot into droidboot (bootloader) its showing usb logo & boot into sytem. Will this fix the problem?

rockytheguru said:
Sir I'm using big rom 12.6 & whenever I tried to boot into droidboot (bootloader) its showing usb logo & boot into sytem. Will this fix the problem?
Click to expand...
Click to collapse
If you have a working twrp, this should work
Sent from my ASUS_T00F using XDA-Developers mobile app

bro i have twrp 2.8.7.2 Pinaslang zenfone recovery.
and i have wipe all system, cache, etc everything.
my phone doesnt have os now
when i got to install Rom its give me error E:error executing binary in zip '/external_sd/#$#%#$%.zip
note: that my usb is not working, ADB is not working, it doest show in my computer or other computer.
solution please 

imsandeshjagtap said:
bro i have twrp 2.8.7.2 Pinaslang zenfone recovery.
and i have wipe all system, cache, etc everything.
my phone doesnt have os now
when i got to install Rom its give me error E:error executing binary in zip '/external_sd/#$#%#$%.zip
note: that my usb is not working, ADB is not working, it doest show in my computer or other computer.
solution please 
Click to expand...
Click to collapse
Im not clear what you gonna do. Installing system through twrp 2872?
Sent from my ASUS_T00F using XDA-Developers mobile app

i want to install a rom, by twrp.
paktepu said:
Im not clear what you gonna do. Installing system through twrp 2872?
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
i want to install a rom, by twrp.
my usb adb is not workings, when i connects usb cable to pc it just gets charge phone.

imsandeshjagtap said:
i want to install a rom, by twrp.
my usb adb is not workings, when i connects usb cable to pc it just gets charge phone.
Click to expand...
Click to collapse
I suggest you to change to twrp 3.0. it can install stock.zip through twrp
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
I suggest you to change to twrp 3.0. it can install stock.zip through twrp
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
its give me error E:error executing binary in zip '/external_sd/#$#%#$%.zip

can give me xcess for download this flashable droidboot

Authorized needed
Authorized Needed for access Your Gdrive
i wanna try it thanks

Anyone !! having mirror of this

paktepu said:
I suggest you to change to twrp 3.0. it can install stock.zip through twrp
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
no download link available :/

link download?

paktepu said:
Playing around with custom roms is very excited for our zenfone. Many of them have very glamour and shiny feature, performance, xposed etc.
But sometimes will make our zenfone brick, lost droidboot and bootloop if we not follow the procedure correctly.
I make a flashable droidboot to fix broken droidboot.
Important :
This flashable droidboot can execute only if you have a working twrp recovery.
Download
Procedure to flash :
1. Put this flashable droidboot on MicroSD
2. Boot twrp recovery
3. Choose Install
4. Pick Flashable Droidboot.zip
5. Swipe to install
Now boot your phone to droidboot to check if it fix.
Tested work on ZENFONE A500CG TOOF 3.24.40.87
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
send link download plss

Zenfone 2 CM13 (i need help please)

So, I tried to install CM13 on my zenfone 2 using a tethered custom recovery and now when I apply the update and restart, I am redirected to the bootloader menu. (cm13 and gapps install but when i restart i go back to reboot i go to bootloader)
If possible help me make it stay on cm13 or marshmallow
i have zenfone 2 1080p

I'm not 100 percent sure, but I believe you need installed TWRP. Tethered wont do. I could be wrong tho.
Sent from my ASUS_Z00A using Tapatalk

When i try to install it via adb (flashing twrp.img) it either does not see my device or it says it is unauthorized

Is your bootloader unlocked?

I have the same problem, I followed a guide I found here on xda to unlock the bootloader of the ze550ml mm beta, problem is that, after using that guide and supposedly unlocking the bootloader, using the twrp i found in that guide i tried to flash the latest cm13 build for my device but it always goes to fastboot, also the only recovery that works is the twrp I found in that guide. Please help me fix this.

Dan_Jacques said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
By unlocked do you mean if I can get into the bootloader or into the stock recovery. I cannot get into the stock recovery but I can get in the bootloader

hudasameer450 said:
By unlocked do you mean if I can get into the bootloader or into the stock recovery. I cannot get into the stock recovery but I can get in the bootloader
Click to expand...
Click to collapse
When I get home I will post a video of what happens

nvm i just realized i dont have a phone

hudasameer450 said:
nvm i just realized i dont have a phone
Click to expand...
Click to collapse
What the heck?
Sent from my ASUS_Z00A using Tapatalk

hudasameer450 said:
When i try to install it via adb (flashing twrp.img) it either does not see my device or it says it is unauthorized
Click to expand...
Click to collapse
Do you have the advantage drivers and fastboot installed on your pc? Did you go into developer mode in your phone and turn on USB debugging? Lastly, did you authorize the pc to debug your phone? (the authorization screen that pops up the first time you send an add command to your phone)... It sounds like one of these issues are your problem
Sent from my ASUS_Z00AD using XDA-Developers mobile app

jflow36 said:
Do you have the advantage drivers and fastboot installed on your pc? Did you go into developer mode in your phone and turn on USB debugging? Lastly, did you authorize the pc to debug your phone? (the authorization screen that pops up the first time you send an add command to your phone)... It sounds like one of these issues are your problem
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
what are advantage drivers and yes to everything else

OtterX Adb not working

I've noticed for a couple days now the adb wont work on my kindle. I have the latest bootloader (v.2.05) i have tried the other otterx bootloader with no luck. :crying:. I've tried many twrps and mtp and adb still wont work. Im not sure what is happening and I've done everything @sd_shadow has either told me to do or was put in his posts all my partitions are correct everything is fine just adb wont work only fastboot will. If anyone else is haveing this issue please chime in also if you have a solution please, please put it out there. I've been searching these threads for days now with nothing turning up.

technerd13 said:
I've noticed for a couple days now the adb wont work on my kindle. I have the latest bootloader (v.2.05) i have tried the other otterx bootloader with no luck. :crying:. I've tried many twrps and mtp and adb still wont work. Im not sure what is happening and I've done everything @sd_shadow has either told me to do or was put in his posts all my partitions are correct everything is fine just adb wont work only fastboot will. If anyone else is haveing this issue please chime in also if you have a solution please, please put it out there. I've been searching these threads for days now with nothing turning up.
Click to expand...
Click to collapse
windows 10?

sd_shadow said:
windows 10?
Click to expand...
Click to collapse
yes

technerd13 said:
yes
Click to expand...
Click to collapse
Kindle doesn't show at all in device manager?

kind of
it shows when in fastboot when i go to recovery it disappears entirely

technerd13 said:
it shows when in fastboot when i go to recovery it disappears entirely
Click to expand...
Click to collapse
change partitions back to amazon, flash a fff bootloader and otter/blaze twrp
see [How-To] Revert from OtterX Project back to Stock Amazon Partitions
then see if adb works in twrp again

what twrp? nvm

sd_shadow said:
change partitions back to amazon, flash a fff bootloader and otter/blaze twrp
see [How-To] Revert from OtterX Project back to Stock Amazon Partitions
then see if adb works in twrp again
Click to expand...
Click to collapse
nope not working still

technerd13 said:
nope not working still
Click to expand...
Click to collapse
which versions did you use?
filenames?
Sent from my XT1254 using XDA Labs

sd_shadow said:
which versions did you use?
filenames?
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
fff v1.4a and twrp 2.2.2.1 blaze or openrecovery-twrp-2.2.2.1-blaze.img and fff-u-boot_v1.5.bin

technerd13 said:
fff v1.4a and twrp 2.2.2.1 blaze or openrecovery-twrp-2.2.2.1-blaze.img and fff-u-boot_v1.5.bin
Click to expand...
Click to collapse
did you ever use a Otter/blaze twrp, before converting to OtterX?
or did was the first find you did was flash OtterX twrp and bootloader in fastboot?

I did previously use fff and blaze twrp
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app

Than I learned about otterx and did that them deleted everything. I did have a previous XDA account by the name of kindlekiller13 if you want to see that I lost the account do to not remembering the password
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app

@kindlekiller13
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app

technerd13 said:
@kindlekiller13
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't see any mention of using an otter/blaze twrp to do anything.
Looks like you jumped straight to otterx, which is fine, but problem may have nothing to do with otterx
---------- Post added at 04:50 AM ---------- Previous post was at 04:20 AM ----------
using the emmc corruption fix may have broken something that is not fixable
Hashcode should have added some warnings about using that...
Sent from my KFFOWI using XDA Labs

Well I had it wrong after I used emmc corruption is when I realized adb wasn't working it turned out fastboot worked fine also I was able to flash 2 Roms but in each one the WiFi was broken so I saw the fix and deleted all. Now I'm stuck with adb not working at all
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app

I was able to get adb to work after several shut downs and restarts. I think it may be my computer. I did some searching and apperantly people had the same problem with adb not working but fast boot was they switched computers and all was fine
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app

sd_shadow said:
I don't see any mention of using an otter/blaze twrp to do anything.
Looks like you jumped straight to otterx, which is fine, but problem may have nothing to do with otterx
---------- Post added at 04:50 AM ---------- Previous post was at 04:20 AM ----------
using the emmc corruption fix may have broken something that is not fixable
Hashcode should have added some warnings about using that...
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
so i did the emmc corruption fix just now and flashed twrp 2.7.1.0 im going to reinstall the kfu drivers and if it still dont work than R.I.P kindle fire number 2

technerd13 said:
so i did the emmc corruption fix just now and flashed twrp 2.7.1.0 im going to reinstall the kfu drivers and if it still dont work than R.I.P kindle fire number 2
Click to expand...
Click to collapse
turns out the micro usb port is now official broken cant even charge oh welll R.I.P
Edit: Ive literally had this thing since its release lol i dont care enough about it to do anything else to it

Rollback from O to N

I unenrolled from the Android beta program yesterday but they still haven't sent an OTA to rollback to N. Can I use wugz to manually do it?
Sent from my Pixel XL using XDA-Developers Legacy app

ucpro said:
I unenrolled from the Android beta program yesterday but they still haven't sent an OTA to rollback to N. Can I use wugz to manually do it?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Have you tried just flashing the latest N factory image or are you trying to retain data and such?

I'd wipe data just to be safe
Sent from my Pixel XL using XDA-Developers Legacy app

Jammol said:
Have you tried just flashing the latest N factory image or are you trying to retain data and such?
Click to expand...
Click to collapse
On Verizon you cannot flash the latest public image. The bootloader is too old coming from Android O

fresnored said:
On Verizon you cannot flash the latest public image. The bootloader is too old coming from Android O
Click to expand...
Click to collapse
What?

I have an unlocked pixel. I just wanna make sure nothing will mess up if I try to flash an image through wugz
Sent from my Pixel XL using XDA-Developers Legacy app

ucpro said:
I have an unlocked pixel. I just wanna make sure nothing will mess up if I try to flash an image through wugz
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I guess wugz is a toolkit right? I'm not sure why you'd need to use anything other than the bootloader menu to flash a factory image. Extract the image you want, in bl menu (on the computer) just type flash-all if you're on Windows, walk away when it starts and come back in 10 minutes. Done.

bobby janow said:
I guess wugz is a toolkit right? I'm not sure why you'd need to use anything other than the bootloader menu to flash a factory image. Extract the image you want, in bl menu (on the computer) just type flash-all if you're on Windows, walk away when it starts and come back in 10 minutes. Done.
Click to expand...
Click to collapse
That's what I was thinking. And the fact that a full wipe is desired makes it even easier.

Yes wugz is a root toolkit but it also let's you restore your phone with whatever version of Android you want, and also downloads the image for you. I haven't tried doing it through the bootloader
Sent from my Pixel XL using XDA-Developers Legacy app

ucpro said:
Yes wugz is a root toolkit but it also let's you restore your phone with whatever version of Android you want, and also downloads the image for you. I haven't tried doing it through the bootloader
Click to expand...
Click to collapse
Are you familiar with flashing Google factory images? If not, @CZ Eddie has a nice tutorial in the guides sub-forum.

I do that through ADB right?
Sent from my Pixel XL using XDA-Developers Legacy app

ucpro said:
I do that through ADB right?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, you do it while in the bootloader menu from the computer. You just need to make sure your device is recognized in bootloader mode on the computer with the command fastboot devices. It should show up. Then flash to your hearts content. Just download and extract the correct image to the correct folder on the computer.

Ok I'll give it a shot
Sent from my Pixel XL using XDA-Developers Legacy app

i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through revovery?

ucpro said:
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through revovery?
Click to expand...
Click to collapse
No I think you should properly learn how to use fastboot and adb before continuing any further.
What fastboot version are you currently using.
What output do you get when you type fastboot devices with your device in the bl menu. Let's figure out you're fastboot issues first and then worry about flashing the image(which will be the easy part).

toknitup420 said:
No I think you should properly learn how to use fastboot and adb before continuing any further.
What fastboot version are you currently using.
What output do you get when you type fastboot devices with your device in the bl menu. Let's figure out you're fastboot issues first and then worry about flashing the image(which will be the easy part).
Click to expand...
Click to collapse
Wise words. Not replying to the OP so hopefully he reads down a bit. It looks like his drivers are not working, i.e. the fastboot ones since he can adb. If he's on Windows then device manager should show an exclamation mark or unknown device. There is a fastboot installation, let me take a look see if I can find it. Ok here ya go. https://www.androidusbdrivers.com/google-pixel-usb-drivers/ I actually didn't need to do that exact procedure but I've been fastbooting for some time.
To the OP. You need to get 'fastboot devices' command to show your device when connected via usb to your computer and in bootloader mode. Once it sees the device the rest is child's play.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
ucpro said:
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through recovery?
Click to expand...
Click to collapse
See above.

bobby janow said:
Wise words. Not replying to the OP so hopefully he reads down a bit. It looks like his drivers are not working, i.e. the fastboot ones since he can adb. If he's on Windows then device manager should show an exclamation mark or unknown device. There is a fastboot installation, let me take a look see if I can find it. Ok here ya go. https://www.androidusbdrivers.com/google-pixel-usb-drivers/ I actually didn't need to do that exact procedure but I've been fastbooting for some time.
To the OP. You need to get 'fastboot devices' command to show your device when connected via usb to your computer and in bootloader mode. Once it sees the device the rest is child's play.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
See above.
Click to expand...
Click to collapse
I can get the phone to show on the computer in adb when the phone is booted up, but it won't show while in fastboot. I use the same command 'adb devices' when the phone is booted up and also in fastboot. I looked through my device manager and there's no exclamation points anywhere on both computers that I've tried

ucpro said:
I can get the phone to show on the computer in adb when the phone is booted up, but it won't show while in fastboot. I use the same command 'adb devices' when the phone is booted up and also in fastboot. I looked through my device manager and there's no exclamation points anywhere on both computers that I've tried
Click to expand...
Click to collapse
You need to type "fastboot devices" when in the bootloader.

Ok I'll give it a shot later tonight

No touch on OS after failed root

Hi everyone.
I'm desperate for help here. I've not even had this phone 12 hours and it's unusable. I feel sick to stomach.
I tried to root my phone via TWRP.img boot and Majisk.
Followed the process, booted into TWRP.img.
Flashed TWRP and Majisk(I assume on the same partition, my idiot mistake there) and it went into bootloop.
No problem, reflash back to factory image and now touch screen doesn't work on the OS.
To test, I reboot back into TWRP.img and touch works there.
I'm begging you wonderful people here.
Please help.
Edit: Additional information, it always boots into recovery mode before booting OS

ryanhavana said:
Hi everyone.
I'm desperate for help here. I've not even had this phone 12 hours and it's unusable. I feel sick to stomach.
I tried to root my phone via TWRP.img boot and Majisk.
Followed the process, booted into TWRP.img.
Flashed TWRP and Majisk(I assume on the same partition, my idiot mistake there) and it went into bootloop.
No problem, reflash back to factory image and now touch screen doesn't work on the OS.
To test, I reboot back into TWRP.img and touch works there.
I'm begging you wonderful people here.
Please help.
Click to expand...
Click to collapse
Try flashing the stock firmware keeping the -w and then boot the twrp.img, switch slots, reboot to bootloader and flash stock again.

Misterxtc said:
Try flashing the stock firmware keeping the -w and then boot the twrp.img, switch slots, reboot to bootloader and flash stock again.
Click to expand...
Click to collapse
Hi,
Thank you.
I'll try this immediately

Misterxtc said:
Try flashing the stock firmware keeping the -w and then boot the twrp.img, switch slots, reboot to bootloader and flash stock again.
Click to expand...
Click to collapse
This didn't work.
:crying:

Boot into twrp then run the magisk uninstaller. Then flash the factory image.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Boot into twrp then run the magisk uninstaller. Then flash the factory image.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Stupid question,
I can't seem to get access to the phone's storage on my PC since I can't get into the OS.
I assume there's another way to access the storage?
Thank you!

ryanhavana said:
Stupid question,
I can't seem to get access to the phone's storage on my PC since I can't get into the OS.
I assume there's another way to access the storage?
Thank you!
Click to expand...
Click to collapse
Do you have the stock recovery on your device now? If so boot into it and use adb to push the file to your device.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Do you have the stock recovery on your device now? If so boot into it and use adb to push the file to your device.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thank you,
I'm not sure I'm doing it correctly.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/
adb: error: failed to get feature set: no devices/emulators found

ryanhavana said:
Thank you,
I'm not sure I'm doing it correctly.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/
adb: error: failed to get feature set: no devices/emulators found
Click to expand...
Click to collapse
Push it to /storage/emulated/0/Download
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Push it to /storage/emulated/0/Download
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I feel like a right fool here. I'm really sorry.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/emulated/0/Download
adb: error: failed to get feature set: no devices/emulators found

ryanhavana said:
I feel like a right fool here. I'm really sorry.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/emulated/0/Download
adb: error: failed to get feature set: no devices/emulators found
Click to expand...
Click to collapse
What do you get when you type adb devices. Does that return the serial number. Also, do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app

ryanhavana said:
Hi everyone.
I'm desperate for help here. I've not even had this phone 12 hours and it's unusable. I feel sick to stomach.
I tried to root my phone via TWRP.img boot and Majisk.
Followed the process, booted into TWRP.img.
Flashed TWRP and Majisk(I assume on the same partition, my idiot mistake there) and it went into bootloop.
No problem, reflash back to factory image and now touch screen doesn't work on the OS.
To test, I reboot back into TWRP.img and touch works there.
I'm begging you wonderful people here.
Please help.
Edit: Additional information, it always boots into recovery mode before booting OS
Click to expand...
Click to collapse
What process did you follow?
Did you purchase it from Google or Verizon?
Do you have the latest SDK Platform-tools r28.0.1?

jd1639 said:
What do you get when you type adb devices. Does that return the serial number. Also, do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have the latest SDK platform tools.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb devices
List of devices attached
It's just blank

Homeboy76 said:
What process did you follow?
Did you purchase it from Google or Verizon?
Do you have the latest SDK Platform-tools r28.0.1?
Click to expand...
Click to collapse
Yes, the latest.
I followed this - https://www.youtube.com/watch?v=BgV1xxkcBk8
I purchased via contract from EE(UK). I very much doubt they will replace the handset.
I'm starting to panic

ryanhavana said:
I have the latest SDK platform tools.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb devices
List of devices attached
It's just blank
Click to expand...
Click to collapse
That may not be good. When you boot into the stock do you select the adb sideload, I don't remember exactly what it says. You need to do that too run the adb commands.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What do you get when you type adb devices. Does that return the serial number. Also, do you have the latest sdk platform tools?
Click to expand...
Click to collapse
@jd1639@ryanhavana
Sorry, I'm dropping out, you are more than qualified to assist him
One question what did he get when he typed fastboot devices?

jd1639 said:
That may not be good. When you boot into the stock do you select the adb sideload, I don't remember exactly what it says. You need to do that too run the adb commands.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have no idea. I don't think I have touched anything that mentions adb sideload

Duplicate

Ok, you're booting into the bootloader and then going to recovery? Then you get the dead andriod? Then you press and hold power then press and release vol up to get into the recovery? Then you should see a selection for "Apply update from adb". You need to get there to run adb commands.
Sent from my [device_name] using XDA-Developers Legacy app

Homeboy76 said:
@jd1639@ryanhavana
Sorry, I'm dropping out, you are more than qualified to assist him
One question what did he get when he typed fastboot devices?
Click to expand...
Click to collapse
Fastboot devices returns my serial number