Develop Bugs

HELP. HOX is dead

Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?

How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?

I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?

the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/

It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.

BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.

I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?

BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.

IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.

IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.

BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/

IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.

What I dont get is why you didn't just root/unlock bootloader via htcdev.com

RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.

IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.

BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.

I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.

BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.

IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.

BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.

[Q] Fastboot Error

When I'm trying to boot the recovery image in fastboot it gives me error:
C:\sdk\platform-tools>fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img
cannot load '/path/to/OuyaCWMrecovery6.0.3.2.img': No error
Fastboot devices sees my device
I have 3 copies of OuyaCWMrecovery6.0.3.2.img around just incase it needed a special place;
1 in the tools with adb and flashboot, 1 in the root of the c drive, and 1 on the desktop.
So can anyone help?

deathknight842 said:
When I'm trying to boot the recovery image in fastboot it gives me error:
C:\sdk\platform-tools>fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img
cannot load '/path/to/OuyaCWMrecovery6.0.3.2.img': No error
Fastboot devices sees my device
I have 3 copies of OuyaCWMrecovery6.0.3.2.img around just incase it needed a special place;
1 in the tools with adb and flashboot, 1 in the root of the c drive, and 1 on the desktop.
So can anyone help?
Click to expand...
Click to collapse
if adb fastboot does list your device, and you have a ouya cwm recovery in your adb/fastboot folder (make sure it's not a bad download)
and run fastboot boot OuyaCWMrecovery6.0.3.2.img
no need for path since it's in the same folder.

GizmoTheGreen said:
if adb fastboot does list your device, and you have a ouya cwm recovery in your adb/fastboot folder (make sure it's not a bad download)
and run fastboot boot OuyaCWMrecovery6.0.3.2.img
no need for path since it's in the same folder.
Click to expand...
Click to collapse
Thanks. that did it.

I did the same but i got an purple screen and I can not read the text because if aligned to the left :S

[Q] kindle fire hd 8.9 fastboot device not found

Hello every one
I was running stock tooted 8.4.3 with TWRP 2.4.3.0 when I decided to upgrade the TWRP to latest version (2.6.3.1) and install CM on my kindle fire hd 8.9. After copping Cm zip file and TWRP file on the sdcard, I reboot to recovery and installed the TWRP. Everything was going on plan, and my kindle reboot into the newest TWRP with no problem. I wipe cash, factory data, and went to install the CM when i notice that TWRP wiped my sdcard. Now the problem is that the stock rom does not work anymore,and my kindle stock in the blue kindle screen, and for some reason I can reboot my kindle to fastboot but when i type adb devices it can not find my kindle and i can not use adb push <filename> /sdcard/ to push cm file to the sdcard to installed it. In new TWRP storage mount is broken so I can not go throw that rout either. my adb driver are installed correctly. and I tried to push cm file on windows 8.1 and windows 7 but it didn't work. Please help me if you can. Thank-You
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\CB>cd \
C:\>cd adb
C:\adb>cd sdk
C:\adb\sdk>cd platform-tools
C:\adb\sdk\platform-tools>fastboot -i 0x1949 getvar product
< waiting for device >
product: Jem-PVT-P###-##
finished. total time: 0.001s
C:\adb\sdk\platform-tools>adb devices
List of devices attached
C:\adb\sdk\platform-tools>adb push cm.zip /sdcard/
error: device not found
C:\adb\sdk\platform-tools>

go into recovery and use the adb command there.
Sent from my SM-N900V using Tapatalk

[Q] Nexus 7 2013 Problems...

A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!

I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Any other suggestions..?

Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...

PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?

that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?

PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7

Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..

tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later

PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7

i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow

LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?

There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7

How to install twrp without being able to boot into system?

I hate doing this since I've been a long time user and usually am able to figure stuff out on my own, but I'm hoping there is an easy fix. I dirty flashed the new aokp update over an older aokp version for the pixel xl and i forgot to flash the twrp image after. Now the system ui crashes upon boot (no surprise there) and I can only get into bootloader and the stock phone recovery. How do I get twrp back?

localceleb said:
I hate doing this since I've been a long time user and usually am able to figure stuff out on my own, but I'm hoping there is an easy fix. I dirty flashed the new update over an older aokp version for the pixel xl and i forgot to flash the twrp image after. Now the system ui crashes upon boot (no surprise there) and I can only get into bootloader and the stock phone recovery. How do I get twrp back?
Click to expand...
Click to collapse
You fastboot boot twrp then flash it in twrp. The same way you got it the first time.

pcriz said:
You fastboot boot twrp then flash it in twrp. The same way you got it the first time.
Click to expand...
Click to collapse
I used the toolkit last time, but I cant adb to recognize the phone in its current state

localceleb said:
I used the toolkit last time, but I cant adb to recognize the phone in its current state
Click to expand...
Click to collapse
This why I wouldn't use a toolkit, you're just kind of handicapping yourself..
You don't need adb to fastboot. either you are using adb (in the booted OS or in recovery) or you are using fastboot (in the bootloader).
You should take a gander at a few of the guides in the Guides section on how to install recovery.
TWRP Thread:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
How to Guide for Beginners (look for the portion on installing twrp):
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Good luck.

localceleb said:
I used the toolkit last time, but I cant adb to recognize the phone in its current state
Click to expand...
Click to collapse
If you are in bootloader mode when you type adb commands it will fail. You use Fastboot commands at that point.
ADB commands are for when tbe phone is booted normally.

TonikJDK said:
If you are in bootloader mode when you type adb commands it will fail. You use Fastboot commands at that point.
ADB commands are for when tbe phone is booted normally.
Click to expand...
Click to collapse
Can you mount the system and use adb commands through the stock recovery? I can't seem to get any fastboot or adb commands to work at all. Even when the system is booted up. The system ui crashes, but shouldn't adb commands still work at that point?

localceleb said:
Can you mount the system and use adb commands through the stock recovery? I can't seem to get any fastboot or adb commands to work at all. Even when the system is booted up. The system ui crashes, but shouldn't adb commands still work at that point?
Click to expand...
Click to collapse
Who knows what else crashed if the ui crashed. Power down, count to ten. Then power and vol down. Once in recovery, connect it to the computer. Not before.
Fastboot devices
If it shows flash the factory image. Modify the bat file and remove the -w to save your data.
If it doesn't connect try other usb ports. Mine won't connect to my front panel, only the rear.
And try another cable.

TonikJDK said:
Who knows what else crashed if the ui crashed. Power down, count to ten. Then power and vol down. Once in recovery, connect it to the computer. Not before.
Fastboot devices
If it shows flash the factory image. Modify the bat file and remove the -w to save your data.
If it doesn't connect try other usb ports. Mine won't connect to my front panel, only the rear.
And try another cable.
Click to expand...
Click to collapse
Well, in theory if I can get fastboot to work I would want to flash the twrp recovery image and then restore a backup, right?

localceleb said:
Well, in theory if I can get fastboot to work I would want to flash the twrp recovery image and then restore a backup, right?
Click to expand...
Click to collapse
I am not a fan of TWRP backups on the Pixels. Seen a few bricks, especially on R2.

So i have attempted to fastboot flash a twrp img and its failing.
C:\Android\TWRP>fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (26588 KB)...
OKAY [ 0.917s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.020s
Am I safe to try a factory image or am I doing something wrong trying to flash the recovery image. ADB commands don't seem to work at this point for some reason.
Thanks for any help!

localceleb said:
So i have attempted to fastboot flash a twrp img and its failing.
C:\Android\TWRP>fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (26588 KB)...
OKAY [ 0.917s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.020s
Am I safe to try a factory image or am I doing something wrong trying to flash the recovery image. ADB commands don't seem to work at this point for some reason.
Thanks for any help!
Click to expand...
Click to collapse
You are doing it wrong. You copy the TWRP zip to the phone.
Then
Fastboot BOOT twrp twrp-3.0.2-0-RC1-fastboot-marlin.img
That boots you to twrp. Then you install the twrp zip while in twrp.
You can not install twrp any other way.

TonikJDK said:
You are doing it wrong. You copy the TWRP zip to the phone.
Then
Fastboot BOOT twrp twrp-3.0.2-0-RC1-fastboot-marlin.img
That boots you to twrp. Then you install the twrp zip while in twrp.
You can not install twrp any other way.
Click to expand...
Click to collapse
I need to add that I cant boot into the system as the system ui crashes so I have no way to transfer files to the phone at this place.

localceleb said:
I need to add that I cant boot into the system as the system ui crashes so I have no way to transfer files to the phone at this place.
Click to expand...
Click to collapse
Fastboot boot to twrp as I described. TWRP has ADB in it, so then from your computer you can ADB push the twrp zip and install it.
But I still advise you to flash the factory image after removing the -w from the flashall bat file.

TonikJDK said:
Fastboot boot to twrp as I described. TWRP has ADB in it, so then from your computer you can ADB push the twrp zip and install it.
But I still advise you to flash the factory image after removing the -w from the flashall bat file.
Click to expand...
Click to collapse
He shouldn't bother removing the -w. A fresh image is what he is in need of. Wipe the phone and start over. Easy.