Database Info

[Q] TWRP problem

I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?

Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader

Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE

aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.

win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster

Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help

Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster

The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways

Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?

I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.

Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster

I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)

Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:

Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android

Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?

My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.

Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B

ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?

Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file

UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping

ADB Won't see ASUS TF300T no matter what

Okay, a little background info:
- This is not my tablet, i'm trying to fix it for a friend
- Not even sure it's a TF300T, is sure looks like from the pictures, it has a blue back.
- I don't have the docking station, just the tablet itself.
- Previously, my friend had someone else try to fix it unsuccessfully, so I don't know whats been done to it.
- There is no data that needs to be recovered. At this point, i'm just trying to get it back so I can flash it with CM.
- The only computer I have at my disposal is running Win7 x64.
Symptoms:
- Boots to Asus screen with nVidia logo at the bottom-right
- Behavior is constantly rebooting to the asus screen until battery is dead
- Hold down VOL- and PWR, goes to Asus bootloader with the following options from left to right: RCK, Android, USB and Wipe Data.
- Recovery Kernel causes it to give me the error "unrecoverable bootloader error (0x00000000000000)"
- Choosing the Android does nothing.
- Wipe Data causes it to give me the error "unrecoverable bootloader error (0x00000000000000)"
- Choosing USB gives you the text "starting fastboot USB download protocol"
Troubleshooting:
- Connecting to computer and choosing USB, the computer will detect the tablet and install "ASUS Android bootloader interface"
- Running the command ADB devices gets me "List of devices attached" with a blank space below it.
- Running the command Fastboot devices gets me "015d25685207f816 fastboot"
- In device manager, I see the tablet under "Samsung Android Phone", and its labeled as "ASUS Android bootloader interface"
- I have tried uninstalling it and installing WCID drivers using Zadig
- I have tried uninstalling everything and using the Google drivers from the SDK
- I have tried uninstalling everything and installing ASUS Sync
- I can run ADB devices and get the ID of my Samsung tablet without a problem
So I'm out of ideas how to get into this tablet so I can flash it with the ASUS blob.
Any ideas, 'cause i'm fresh out of them. Thanks!

Anyone have a clue or can think of something I haven't tried?

snootch said:
Anyone have a clue or can think of something I haven't tried?
Click to expand...
Click to collapse
Did You tried this? Download last stock firmware for Your SKU, unpack it twice and put blob file (the biggest one; if it have different name You should rename it to "blob") into tool folder. Connect tablet in USB mode to Your PC and flash it with any of fastboot option.

snootch said:
Okay, a little background info:
- This is not my tablet, i'm trying to fix it for a friend
- Not even sure it's a TF300T, is sure looks like from the pictures, it has a blue back.
- I don't have the docking station, just the tablet itself.
- Previously, my friend had someone else try to fix it unsuccessfully, so I don't know whats been done to it.
- There is no data that needs to be recovered. At this point, i'm just trying to get it back so I can flash it with CM.
- The only computer I have at my disposal is running Win7 x64.
Symptoms:
- Boots to Asus screen with nVidia logo at the bottom-right
- Behavior is constantly rebooting to the asus screen until battery is dead
- Hold down VOL- and PWR, goes to Asus bootloader with the following options from left to right: RCK, Android, USB and Wipe Data.
- Recovery Kernel causes it to give me the error "unrecoverable bootloader error (0x00000000000000)"
- Choosing the Android does nothing.
- Wipe Data causes it to give me the error "unrecoverable bootloader error (0x00000000000000)"
- Choosing USB gives you the text "starting fastboot USB download protocol"
Troubleshooting:
- Connecting to computer and choosing USB, the computer will detect the tablet and install "ASUS Android bootloader interface"
- Running the command ADB devices gets me "List of devices attached" with a blank space below it.
- Running the command Fastboot devices gets me "015d25685207f816 fastboot"
- In device manager, I see the tablet under "Samsung Android Phone", and its labeled as "ASUS Android bootloader interface"
- I have tried uninstalling it and installing WCID drivers using Zadig
- I have tried uninstalling everything and using the Google drivers from the SDK
- I have tried uninstalling everything and installing ASUS Sync
- I can run ADB devices and get the ID of my Samsung tablet without a problem
So I'm out of ideas how to get into this tablet so I can flash it with the ASUS blob.
Any ideas, 'cause i'm fresh out of them. Thanks!
Click to expand...
Click to collapse
If you have fastboot there is hope ...
PM me if you would like some help with this...
Thx Josh

Well,
It should be working, but i think it's getting stuck. I'm running the following command:
c:\platform-tools>fastboot -i 0x0B05 flash system c:\platform-tools\blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800931 KB)...
OKAY [108.776s]
writing 'system'...
And it sits there... I've let it go all night, and is was still there in the morning. Don't know what commands to run now.

snootch said:
Well,
It should be working, but i think it's getting stuck. I'm running the following command:
c:\platform-tools>fastboot -i 0x0B05 flash system c:\platform-tools\blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800931 KB)...
OKAY [108.776s]
writing 'system'...
And it sits there... I've let it go all night, and is was still there in the morning. Don't know what commands to run now.
Click to expand...
Click to collapse
It may be usb port issue. Try another one.

Graiden05 said:
It may be usb port issue. Try another one.
Click to expand...
Click to collapse
Done that twice, no change.

snootch said:
Done that twice, no change.
Click to expand...
Click to collapse
Try then wipe it manualy:
Code:
fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 flash system c:\platform-tools\blob
Or alternatively flash it through staging:
Code:
fastboot -i 0x0B05 flash staging c:\platform-tools\blob

Great, now it won't even boot. I'm pressing the hard reset pin hole while holding down. the vol-. Power+Vol- won't do anything either. Of the last 50 times I tried, I got the Asus screen with red text at the top-left saying something about corrupt bootloader error 0x00000005. The poer button does not have a light on it either.

p5110 Unknown USB Device (Device Descriptor Request Failed)

Hello.
So today i've decided to update firmware on my p5110.
It was already rooted and with cyan 10. I've installed TWRP 3.0.0.0 via CWM recovery and booted in TWRP. And then i chose Format data and it completely wiped out all of my files. I knew that, but i was thinking that i'll be able to flash ADB Sideload without a problem.
After that i've tried to boot into ADB Sideload, and nothing happened. My PC is not recognizing p5110. Sometimes it's showing notification "Unknown USB Device (Device Descriptor Request Failed)" in Device Manager, but most of the time it's not connected.
So, basically, now i have a tablet with working recovery, without any files on it and with no OS. I can't flash original firmware via Odin, and i can't flash it through ADB sideload, cause it's not recognized.
I reinstalled Samsung USB Drivers on my pc, installed ADB drivers and Android SDK, my other Samsung devices have no problems with USB connection, and the cable is fine.
Also, I have Windows 8.1 64 bit.
Is there any solution? Please, help.

I have exactly this same issue - running windows 10.
Following the CM installation instructions here:
https://wiki.cyanogenmod.org/w/Install_CM_for_espressowifi
Windows itself complains that the "device you connected to this computer malfunctioned and can not be recognised" and Zadig itself sees it as
"Unknown USB Device (Device desciptor request failed).
Any thoughts on this?
Cheers

cy80rg said:
I have exactly this same issue - running windows 10.
Following the CM installation instructions here:
https://wiki.cyanogenmod.org/w/Install_CM_for_espressowifi
Windows itself complains that the "device you connected to this computer malfunctioned and can not be recognised" and Zadig itself sees it as
"Unknown USB Device (Device desciptor request failed).
Any thoughts on this?
Cheers
Click to expand...
Click to collapse
install or re-install latest samsung driver from here
http://developer.samsung.com/technical-doc/view.do?v=T000000117

skyless_kingdom said:
Hello.
So today i've decided to update firmware on my p5110.
It was already rooted and with cyan 10. I've installed TWRP 3.0.0.0 via CWM recovery and booted in TWRP. And then i chose Format data and it completely wiped out all of my files. I knew that, but i was thinking that i'll be able to flash ADB Sideload without a problem.
After that i've tried to boot into ADB Sideload, and nothing happened. My PC is not recognizing p5110. Sometimes it's showing notification "Unknown USB Device (Device Descriptor Request Failed)" in Device Manager, but most of the time it's not connected.
So, basically, now i have a tablet with working recovery, without any files on it and with no OS. I can't flash original firmware via Odin, and i can't flash it through ADB sideload, cause it's not recognized.
I reinstalled Samsung USB Drivers on my pc, installed ADB drivers and Android SDK, my other Samsung devices have no problems with USB connection, and the cable is fine.
Also, I have Windows 8.1 64 bit.
Is there any solution? Please, help.
Click to expand...
Click to collapse
I found my old Samsung P5110 that i hard bricked a long time ago and i am having the same issue. It boots into download mode just fine, but i am getting the same error with the driver. Tried reinstalling the drivers but nothing seems to work.

Please help! Pixel 2 stuck in bootloader

Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.

try another usb port and/or another cable.

Velunavian said:
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
Click to expand...
Click to collapse
I have had this happen before except it did not prevent adb/fastboot from working. I just had to switch slots with the fastboot cmd ( fastboot --set-active=b or a ) depending on which slot you are currently on. Then flash the factory img. Are you sure you have the correct drivers installed for adb/fastboot? Have you tried a different usb port / different pc / different cord?
Sent from my [device_name] using XDA-Developers Legacy app

Thank you for your reaction!
I'm sure I have the right drivers, but I will trie more ports, cables and another pc and keep you updated!

First update
So I couldn't get my pc to recognise my phone.
I then used a MacBook so I could use the official USB-C cable. I downloaded the android SDK platform-tools and the factory image. I placed the files from the factory image into the platform-tools folder. Then I used the command './adb devices' and it showed my device! But when I tried the next command, it said "no devices found". Now, when I do the same thing, no device will show up, even in the beginning.

Velunavian said:
So I couldn't get my pc to recognise my phone.
I then used a MacBook so I could use the official USB-C cable. I downloaded the android SDK platform-tools and the factory image. I placed the files from the factory image into the platform-tools folder. Then I used the command './adb devices' and it showed my device! But when I tried the next command, it said "no devices found". Now, when I do the same thing, no device will show up, even in the beginning.
Click to expand...
Click to collapse
adb does not work in fastboot mode. use ./fastboot

If there's a USB 3.0 port in the Windows PC, using a USB 3.0 cable even in a supposedly USB 2.0 port can cause problems. (I've been there, to the point that tech support actually shopped me a replacement because they were sure it was a hardware problem with the phone.)
What I used to fix it, to make sure that whatever it is about USB 3.0 that's causing the problem isn't also showing up in a USB 2.0 port in the same computer, was using a Type A to microUSB cable (that's a type 2 cable - there's no question) and a microUSB-to-Type-C adapter.
Then I ran Deuces Recovery, and the phone worked (after about 5 minutes of watching that thin grey line moving on the initial white screen). Evidently the constant "flash/reboot/flash/reboot" cycle fixes something that Google overlooked. (You may find that the phone got messed up enough that you have to format user data to get it working. My first attempt - without formatting user data - didn't work. Formatting it did.)

Thank you for your replie
Rukbat said:
If there's a USB 3.0 port in the Windows PC, using a USB 3.0 cable even in a supposedly USB 2.0 port can cause problems. (I've been there, to the point that tech support actually shopped me a replacement because they were sure it was a hardware problem with the phone.)
What I used to fix it, to make sure that whatever it is about USB 3.0 that's causing the problem isn't also showing up in a USB 2.0 port in the same computer, was using a Type A to microUSB cable (that's a type 2 cable - there's no question) and a microUSB-to-Type-C adapter.
Then I ran Deuces Recovery, and the phone worked (after about 5 minutes of watching that thin grey line moving on the initial white screen). Evidently the constant "flash/reboot/flash/reboot" cycle fixes something that Google overlooked. (You may find that the phone got messed up enough that you have to format user data to get it working. My first attempt - without formatting user data - didn't work. Formatting it did.)
Click to expand...
Click to collapse
Yes, I had the same idea! I will trie it a few more times with my macbook and if it doesn't work I will buy the adapter.
I used an usb 3.0 A to C adapter and a usb 3.0 A to A cable to connect my Pixel to a usb 3.0 port on my pc. I think this should work, but somehow it didn't.

Thank you so much!
munchy_cool said:
adb does not work in fastboot mode. use ./fastboot
Click to expand...
Click to collapse
It worked! I got my device back to normal.

Velunavian said:
It worked! I got my device back to normal.
Click to expand...
Click to collapse
Enjoy.

cmlusco said:
I have had this happen before except it did not prevent adb/fastboot from working. I just had to switch slots with the fastboot cmd ( fastboot --set-active=b or a ) depending on which slot you are currently on. Then flash the factory img. Are you sure you have the correct drivers installed for adb/fastboot? Have you tried a different usb port / different pc / different cord?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Velunavian said:
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,i have same Pixel2 in this Load Error. PC doesn't recognize your device,You just put in annother usb until PC recognize the device,because it needs times to recognize the device.
but,my devices can't fastboot boot twrp.img
it say :
downloading'boot.img'...
OKAY[1.269s]
booting...
FAILED(remote:FAILED to load/authenticate boot image:Load Error)
when i flash factory ROM ,it say:
''archive does not contain 'boot.sig' ^^^^^^^^^
Erase successful,but notautomatically formatting.
Can't determine partition type.
FAILED[command write failed[no error]]
HOw to unbick this devices?
---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------
cmlusco said:
I have had this happen before except it did not prevent adb/fastboot from working. I just had to switch slots with the fastboot cmd ( fastboot --set-active=b or a ) depending on which slot you are currently on. Then flash the factory img. Are you sure you have the correct drivers installed for adb/fastboot? Have you tried a different usb port / different pc / different cord?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Velunavian said:
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,i have same Pixel2 in this Load Error. PC doesn't recognize your device,You just put in annother usb until PC recognize the device,because it needs times to recognize the device.
but,my devices can't fastboot boot twrp.img
it say :
downloading'boot.img'...
OKAY[1.269s]
booting...
FAILED(remote:FAILED to load/authenticate boot image:Load Error)
when i flash factory ROM ,it say:
''archive does not contain 'boot.sig' ^^^^^^^^^
Erase successful,but notautomatically formatting.
Can't determine partition type.
FAILED[command write failed[no error]]
How to unbick this devices?

Install TWRP without USB

I have a Mi 9T Global 6/128GB running stock MIUI 12.0.7 Global with bootloader already unlocked. However the USB port has gone bad and only works for charging.
Is there a way for me to install TWRP without a USB connection?
Everything I've done and observed:
USB debugging enabled
USB tethering option greyed out - no USB connection detected
Default USB action set to MTP does not help
It charges but no prompt for USB mode when connected
Phone does not show up on PC
No new device detected in device manager
No problematic device detected in device manager in any mode
No device detected through ADB in any mode
No device detected through fastboot in fastboot mode
No device detected in miflash tool regardles of phone in system or fastboot
No device detected in miunlock tool regardless of phone in system or fastboot
No detected USB device on which I can attempt a driver update
USB drivers verified updated
Tried on my desktop and laptop, with multiple cables and ports
OTG with another Android device does not work
I was using RR Android Q when I realized this issue. At that time I was using TWRP and even in recovery with everything mounted and MTP enabled, the phone was still not detected on PC. I flashed the latest stable MIUI zip hoping it would be fixed bit no bueno.
I want to get TWRP back to install a custom rom because I refuse to use MIUI.
Any help will be greatly appreciated.

Because this phone doesnt have card slot my guess is you can't re-install TWRP.

Is your phone rooted? if it isn't then try rooting it with kingroot (I know it's bad, but you don't exaclty have any other option)
After rooting then follow this thread.
Briefly:
After rooting the device, install flashify.
Flash TWRP through flashify.
Do a factory reset to remove kingroot.
Download and flash your desired ROM.
I don't know if this method works and I recommend searching into it first before trying it.
If it actually works, don't forget to backup everything before flashing. Also once you flash there is no going back since Xiaomi devices has rollback protection.