Database Info

HTC One XL hboot 2.15.0000 can't unbrick

My HTC One XL went on low battery and i plugged it on charge. Power outages meant the phone couldn't charge and when power came back on, I plugged it again on charge for about two hours. I tried booting the phone and the phone couldn't start, but the red light kept blinking even though it was unplugged from the charger. I pressed and held the power button for a while and turned it on again. It came on, but could not boot pass the "HTC quietly brilliant" screen, it kept restarting from that screen after it stays on for some seconds.
Next thing i did was to boot into bootloader. The bootloader was initially "Unlocked" but when the bootloader came up, it showed "LOCKED", which means the bootloader has gone back to locked all by itself. I tried unlocking the bootloader again, but when the unlocking warning screen shows up and i select "YES", it restarts and the "HTC quietly brilliant" screen keeps restarting. I tried factory reset from bootloader but the htc screen comes up and restarts from there.
The next thing i did was to look for an RUU. I couldn't find any, as most of the links were down. So i downloaded "RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radi o_0.19as.32.09.11_2_10.105.32.25L_release_271865_s igned" and I tried flashing from there, but the RUU loader could not load on the phone, could not even restart into the bootloader, as the HTC screen keeps restarting. RUU could not also be loaded from fastboot commands. I tried flashing a new kernel, but the phone doesn't allow the command to push the "boot" image file.
The phone was running on the official T-Mobile 4.2.2 Sense 5 which I updated OTA before unlocking the bootloader, and everything was working just fine, until the phones battery run low and the bootloader went back to locked by itself. Please help, as it seems all options have been exhausted. I have attached a copy of an image of my bootloader. But the details are as follows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 14 2013, 16:02:22:-1
Please help :'(

Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).

redpoint73 said:
Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).
Click to expand...
Click to collapse
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.

Economistaterry said:
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.
Click to expand...
Click to collapse
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.

redpoint73 said:
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.
Click to expand...
Click to collapse
so can the bootloader be repaired? if yes, how?

Economistaterry said:
so can the bootloader be repaired? if yes, how?
Click to expand...
Click to collapse
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.

Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.

redpoint73 said:
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.
Click to expand...
Click to collapse
The red light which shows that the battery is charging never turns green. I have left it on charge over night so many times, but green never shows. Then the red light also stays solid for like 6seconds, goes off for like 2 or 3 seconds and comes back on. It never turns solid like it does when it's fully working, even when I leave it on charge for a long time.

twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
When ever I give the rebootRUU command, the phone restarts, the black HTC screen never shows.

Have you tried
fastboot erase cache
and then try rebootRUU?

twistedddx said:
Have you tried
fastboot erase cache
and then try rebootRUU?
Click to expand...
Click to collapse
Yes please, I just did that a couple of times. It only reboots the HTC white screen, same problem.

From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?

twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
I gave the "fastboot flash recovery recovery.img" command and all i get is "sending 'recovery' (9060 kb) . . ." and nothing happens. The green bar which will show on the bootloader shows, but doesn't load. I have done this a couple of times, same results

twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.

So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"

twistedddx said:
So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"
Click to expand...
Click to collapse
-yes, 5.08 OTA
-yes, can not boot into a ROM
-yes, can not boot into recovery
-yes, INFOcid: T-MOB101
-yes, can clear cache with fastboot
-yes, flash recovery fails
-fastboot oem lock comes "INFODevice is already locked!"
-yes, unlocktoken fails. Got millions of new tokens from htcdev, all can't unlock, but will try again
-yes, RUU fails, will try the version u mentioned
-yes, rebootRUU fails, and i know its case sensitive
Thanks a lot for your support. Am in Ghana, no htc servive center here, no jtag repair center too.

Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?

Economistaterry said:
Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?
Click to expand...
Click to collapse
It could be a hardware issue.. But I doubt a hardware issue would mess up your hboot to the point you cant do anything.
You won't be able to flash anything with a locked bootloader. Keep trying to unlock the bootloader. Use the same unlock token, you do not need to re-request new ones everytime. if/when it fails to unlock, press and hold power until the phone shuts off, let go of power, press and hold volume down to go back into bootloader then try again with the same unlockcode bin file. Repeat until it unlocks. It may take many many tries. Press and hold power to hard power off the phone between tries every time.
When you finally do get it to unlock post here and we will fix your hboot issues.

redpoint73 said:
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.
Click to expand...
Click to collapse
twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?

Economistaterry said:
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?
Click to expand...
Click to collapse
absolutely nothing will flash with a locked bootloader. Nothing nothing nothing.

[Q] OTA Update 2.2 has bricked my brand new ST?

So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?

Nastybutler said:
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Click to expand...
Click to collapse
you need to unlock the bootloader

Daniele12 said:
you need to unlock the bootloader
Click to expand...
Click to collapse
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.

VijayBais said:
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
Click to expand...
Click to collapse
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)

Keithn said:
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Click to expand...
Click to collapse
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.

VijayBais said:
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
Click to expand...
Click to collapse
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?

Keithn said:
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Click to expand...
Click to collapse
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s

I know this won't help VijayBais, but after a while I guess the stock kernel and everything settled in and it stopped random restarting and when I did restart, after installing apps and whatnot, it booted right back up. Now that I'm on 5.1, I haven't had any issues with it freezing up, or random restarts. Crisis averted.

VijayBais said:
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
Click to expand...
Click to collapse
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?

Keithn said:
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Click to expand...
Click to collapse
No, I haven't done any factory reset till now.
Even the recovery option doesn't proceed to further options on bootloader page.

You can't get into the recovery menu? When you chose it and get the dead android do you quickly tap the power+volume up combo?

Bootloop on Motorola Moto G4 Play (Verizon) XT1609

I would like to recover the ROM on this Android this device it keeps bootlooping I tryed to Root the Device and I did a factory reset on it after I did a root... I thought everything was going find and it started to keep reloading the logo (Moto)...
I basically tried everything to recover the ROM on it using the following programs...
ADB Setup
MFastBoot (Error Message with Bootloader)
it seems to be locked device I can't seem to unlock the device... I seen someone that you don't have to have it unlock it to install TWRP or something....
Am all new to this stuff and I just got my phone I did not want anything happen to this phone for important use I would like to get this phone back up and running again...
Thanks

Moto G4 Play XT1609 Bootloop after rooting
travisbrown9201 said:
I would like to recover the ROM on this Android this device it keeps bootlooping I tryed to Root the Device and I did a factory reset on it after I did a root... I thought everything was going find and it started to keep reloading the logo (Moto)...
I basically tried everything to recover the ROM on it using the following programs...
ADB Setup
MFastBoot (Error Message with Bootloader)
it seems to be locked device I can't seem to unlock the device... I seen someone that you don't have to have it unlock it to install TWRP or something....
Am all new to this stuff and I just got my phone I did not want anything happen to this phone for important use I would like to get this phone back up and running again...
Thanks
Click to expand...
Click to collapse
Am in the same boat. My Verizon Moto G4 Play XT1609 Bootloops after rooting and restarting. I have tried all else including repairing via Verizon Upgrade Assistant tool with no success (Ugrade Assistant tool detected my phone, flashed latest firmware and cleared user data only for the phone to resume bootloop :crying.
I had to try Upgrade Assistant tool since this model does not qualified for bootloader unlocking ("fastboot getvar all" returned cid: 0x0002)
I trust that all hope is not lost, having confidence someone would turn up something somehow :laugh:
So, any help would be appreciated.

Re-run autoinitroot and then follow the instructions to unroot, thats all!

conquesoextra said:
Re-run autoinitroot and then follow the instructions to unroot, thats all!
Click to expand...
Click to collapse
Thanks too much! you just saved my Motorola!

bullracing said:
Thanks too much! you just saved my Motorola!
Click to expand...
Click to collapse
Hi,
I asked a related question in https://forum.xda-developers.com/g4-play/help on 4/9 and have yet to receive any responses. I didn't see this question before. It looks like a very similar situation to mine.
My XT1609 also is bootlooping and the bootloader also is locked, so I assume that this is why I'm getting "Preflash validation failed" errors when I try to download stock images to it. I found harpia_vzw_oem_vzw_user_7.1.1_NPI26.48-38_48_release-keys-cid2_vzw.tar.gz through this site and have been attempting to use Linux/fastboot to download images from the tar. I am able to download and reflash one of the images, logo.img, but I get the prevalidation errors for everything else I've tried.
I'm not familiar with mfastboot or autoinitroot. Can someone tell me where I can get these and how to use them? Should I just need to use autoinitroot to fix the bootlooping or does this somehow allow me to flash images to the phone?
Thanks!

thalwegz said:
Hi,
I asked a related question in https://forum.xda-developers.com/g4-play/help on 4/9 and have yet to receive any responses. I didn't see this question before. It looks like a very similar situation to mine.
My XT1609 also is bootlooping and the bootloader also is locked, so I assume that this is why I'm getting "Preflash validation failed" errors when I try to download stock images to it. I found harpia_vzw_oem_vzw_user_7.1.1_NPI26.48-38_48_release-keys-cid2_vzw.tar.gz through this site and have been attempting to use Linux/fastboot to download images from the tar. I am able to download and reflash one of the images, logo.img, but I get the prevalidation errors for everything else I've tried.
I'm not familiar with mfastboot or autoinitroot. Can someone tell me where I can get these and how to use them? Should I just need to use autoinitroot to fix the bootlooping or does this somehow allow me to flash images to the phone?
Thanks!
Click to expand...
Click to collapse
Hi, again
I was able to download the autoinitroot package from http://downloads.codefi.re/autoprime/Motorola/autoinitroot/XT1609 and extract and run the Linux version of the script. Here's what happened:
2102d sudo ./auto#initroot.linux.sh
#initroot and cve-2016-10277 by https://twitter.com/roeehay
magisk by https://twitter.com/topjohnwu
auto#initroot by https://twitter.com/@utoprime
.
..
...
....to uninstall auto#initroot, press <any> key within 3 seconds
...
..
.
-start auto#initroot
-send fastboot oem config fsg-id a initrd=0x91000000,2064196
...
FAILED (remote failure)
finished. total time: 0.017s
-send fastboot flash initroot xt1609_harpia_vzw_mpis24.241-2.35-1-17.initroot
target max-download-size: 256MB
sending 'initroot' (19531 KB)...
OKAY [ 24.421s]
writing 'initroot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 24.431s
-send fastboot continue
resuming boot...
OKAY [ 0.097s]
finished. total time: 0.097s
-finish moto boot
I have Android 7.1.1 installed on my phone, the stock Verizon OTA version. Could there be an incompatibility between this initroot image and the other software on the phone?
Thanks

Pixel 2 = brick? FASTBOOT + ADB not helping. How do I clear files so can get repair?

I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.

Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.

Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.

Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk

Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.

I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk

It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse

You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk

Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse

domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.

Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse

domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.

What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.

Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse

Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse

Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse

And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock

In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it

Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.

Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.

Question [Question] Unroot + Relock Bootloader?

Hi,
I have an ROG Phone 5 that I unlocked and rooted using https://forum.xda-developers.com/t/asus-rog-phone-5-unlock-bootloader-and-root-guide.4261151/
I've realized I'm in a little bit over my head and I want to go completely back to a fresh start as if I'd just gotten the phone etc. I uninstalled Magisk but I don't know how to go about restoring the phone back to factory and relocking the bootloader. I know that re-locking the bootloader means I can't unlock it again and I'm okay with that, I just want to start fresh.
Let me know if you need any extra information.
Thanks!

Flash a stock boot image or install Magisk and use the restore include in that before deleting it again. After that, there is a fastboot command to lock the bootloader. I can't remember it off the top of my head, but the fastboot commands thread should help.

Isn't ASUS a special command?
It depends on your local
Only the Chinese version and the WW version have RAW files to be reinstalled.
Depending on your local, you can't restore it unless you create a raw file yourself.
It is presumed that local is different because the command does not pass.

twistedumbrella said:
Flash a stock boot image or install Magisk and use the restore include in that before deleting it again. After that, there is a fastboot command to lock the bootloader. I can't remember it off the top of my head, but the fastboot commands thread should help.
Click to expand...
Click to collapse
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?

Just in case you didn't know: once you lock the bootloader you cannot unlock it anymore. If there is no advantage (and I don't know any real good advantage, especially when you want to sell it) you should not do that.

EliseBelle said:
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Click to expand...
Click to collapse
If none of those work, then I have no idea.
Anubarak16 said:
Just in case you didn't know: once you lock the bootloader you cannot unlock it anymore. If there is no advantage (and I don't know any real good advantage, especially when you want to sell it) you should not do that.
Click to expand...
Click to collapse
EliseBelle said:
I know that re-locking the bootloader means I can't unlock it again and I'm okay with that, I just want to start fresh.
Click to expand...
Click to collapse

Gosh, for whatever reason I totally overlooked that
Let's pretend it never happened

Anubarak16 said:
Gosh, for whatever reason I totally overlooked that
Let's pretend it never happened
Click to expand...
Click to collapse
I agree, though. The nag screen and manual updates are a small price for being able to restore from home. Someone may even come up with a way to fix OTA eventually.

EliseBelle said:
I flashed the stock rom but I can't figure out how to lock the bootloader again. I've tried;
fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot oem asus-lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
Any ideas?
Click to expand...
Click to collapse
How did you enter Fastboot mode? Volume up + Power or through the stock recovery menu?

I have the same problem. If I enter Fastboot from TWRP, the "default implementation" error happens.
If I enter FastBoot mode by Volume Up+Power, the Tool does not recognize my device, so the command waits for a device...
Is it caused by configuration of the Tool? Or drivers? Please halp!

Hectorim said:
I have the same problem. If I enter Fastboot from TWRP, the "default implementation" error happens.
If I enter FastBoot mode by Volume Up+Power, the Tool does not recognize my device, so the command waits for a device...
Is it caused by configuration of the Tool? Or drivers? Please halp!
Click to expand...
Click to collapse
There is no TWRP for this device, so that is probably part of it.
It also sounds like you don't have drivers and / or fastboot installed properly.

So lemme get this straight...
When I boot into FastBoot, either by VolumeUp or by Tool-all-in-one, the phone SHOULD be picked up by the tool/PC? I mean when the phone is on the screen with "Fastboot Mode" in red lettering.
If it's a driver fault, how can I wipe them off my PC to try to start anew? Is there a step-by-step guide for dummies?

Hectorim said:
So lemme get this straight...
When I boot into FastBoot, either by VolumeUp or by Tool-all-in-one, the phone SHOULD be picked up by the tool/PC? I mean when the phone is on the screen with "Fastboot Mode" in red lettering.
If it's a driver fault, how can I wipe them off my PC to try to start anew? Is there a step-by-step guide for dummies?
Click to expand...
Click to collapse
I'm sure you could google fastboot and find 50.

Turns out my device isn't visible because Windows doesn't recognize it properly - it sees it as "Android" with an exclamation mark.
I have installed fastboot and adb drivers, Asus ROG specific USB drivers manually (as legacy), so I have no idea why it isn't recognized.

Hectorim said:
Turns out my device isn't visible because Windows doesn't recognize it properly - it sees it as "Android" with an exclamation mark.
I have installed fastboot and adb drivers, Asus ROG specific USB drivers manually (as legacy), so I have no idea why it isn't recognized.
Click to expand...
Click to collapse
For me the solution is to connect the device to the pc, boot into fastboot, then do the manual steps to install the adb drivers. If I install the drivers manually without the device already in fastboot, it will not recognize the device properly.
Good luck!

For what reason u want to re-roll from rooted phone?

aldomuwsa said:
For what reason u want to re-roll from rooted phone?
Click to expand...
Click to collapse
Because you didn't get an SSR.
Jokes aside, it's only really for warranty repair or in hopes it will enable OTA. You really shouldn't do it just for fun, though.

twistedumbrella said:
Because you didn't get an SSR.
Jokes aside, it's only really for warranty repair or in hopes it will enable OTA. You really shouldn't do it just for fun, though.
Click to expand...
Click to collapse
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions

aldomuwsa said:
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
Click to expand...
Click to collapse
If its what u get, surely im gonna root my phone right now

aldomuwsa said:
What kind u get from rooted phone by the way? Special hacking tools? Mod SSR Generate, or what?
Sorry for my newbie questions
Click to expand...
Click to collapse
For the typical user, root is unnecessary for day to day life.
The biggest reasons people used to root were for ad blocking, sound enhancement, mobile hotspot functionality, and to modify the build.prop with values for another device (to bypass restrictions).
Of the previously mentioned uses, modifying the build.prop still requires root. Sound enhancement is a bit obsolete and mobile hotspot functionality or ad blocking can be achieved without root.
Unlike years ago, rooting is less of a "do not update or you miss the chance" process if you aren't using a Samsung. You don't have to jump into it if you don't have a reason and can always do it later if you find one.