Database Develop

[Q] TWRP flash via Fastboot failing

I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so.
Code:
fastboot flash recovery twrps.img
sending 'recovery' (4822 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5.
Need help to flash the TWRP and begin using JB roms.

YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.

giveen said:
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
Click to expand...
Click to collapse
Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.

I bricked my OnePlus 7 Pro (was stuck and fastboot) and how I fixed it

Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.

Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk

vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done

All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.

I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!

Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!

Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.

vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!

vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.

i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd

nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/

vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power

I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?

I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:

moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk

Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?

Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?

Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk

Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...

I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse

Recover Pixel 4 XL? Device unlocked but "no valid slot to boot"?

Hi, I am a noob to rooting Android devices, and due to country restrictions on Motion Sense I decided to give it a go. I followed the guide using Magisk and Platform Tools (on Mac).
I got to the point of entering "./ fastboot flash boot magisk_partched.img"
Code:
192:platform-tools usernameredacted$ ./fastboot flash boot magisk_patched.img
Sending 'boot_a' (32092 KB) OKAY [ 0.310s]
Writing 'boot_a' OKAY [ 0.196s]
Finished. Total time: 0.796s
192:platform-tools usernameredacted$
192:platform-tools usernameredacted$ ./fastboot flash boot magisk_patched.img
< waiting for any device >
Sending 'boot_a' (32092 KB) ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (Undefined error: 0))
fastboot: error: Command failed
Something was successful, but I can see there's an error e00002eb there. Now the Pixel 4 XL doesn't boot. It shoes the screen attached, stating "Device state: unlocked" and "Enter reason: no valid slot to boot".
I can also get it into a bootloop, which will show the bootloader and then the Google logo, but then loops.
Any ideas on what I should do next?
My assumption is, if I could replace the "magisk_patched.img" with the original "boot.img", then I could Recover the device back to normal. If I can do that, I will possibly try again to root, but that's less of a priority as I simply want to avoid a bricked device for the time being. FYI, I found it strange that my 'magisk_patched.img' is 32mb whilst the original 'boot.img' is 67mb, but I have no idea if this is normal or not.
Any help or links to Recovery guides very welcome. I can't seem to find a guide yet! Thanks in advance for anything, as it's currently a brick

foaf said:
Hi, I am a noob to rooting Android devices, and due to country restrictions on Motion Sense I decided to give it a go. I followed the guide using Magisk and Platform Tools (on Mac).
I got to the point of entering "./ fastboot flash boot magisk_partched.img"
Something was successful, but I can see there's an error e00002eb there. Now the Pixel 4 XL doesn't boot. It shoes the screen attached, stating "Device state: unlocked" and "Enter reason: no valid slot to boot".
I can also get it into a bootloop, which will show the bootloader and then the Google logo, but then loops.
Any ideas on what I should do next?
My assumption is, if I could replace the "magisk_patched.img" with the original "boot.img", then I could Recover the device back to normal. If I can do that, I will possibly try again to root, but that's less of a priority as I simply want to avoid a bricked device for the time being. FYI, I found it strange that my 'magisk_patched.img' is 32mb whilst the original 'boot.img' is 67mb, but I have no idea if this is normal or not.
Any help or links to Recovery guides very welcome. I can't seem to find a guide yet! Thanks in advance for anything, as it's currently a brick
Click to expand...
Click to collapse
Try a different cable. And the Magisk patched image is always smaller due to compression.

custom recovery flash successful, but not working

Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.

to-bu said:
Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.
Click to expand...
Click to collapse
Obviously, you did something wrong.
Try renaming the recovery that you downloaded to "recovery" with no quotation marks
Place the file in the platform tools directory
For example: C:\Android\platform-tools\
Then use these commands.
fastboot flash recovery recovery.img
fastboot boot recovery.img
The commands above will flash the recovery.image to the recovery partition, then reboot then phone to recovery, you will then need to flash root.
If that doesn't work just use the Tool all in One

It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitly something is wrong

to-bu said:
It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitely something is wrong
Click to expand...
Click to collapse
Are you sure that you have developer options setup? ADB debugging is enabled?
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
The latest Orange Fox is here: https://files.orangefox.tech/OrangeFox-Beta/dipper/OrangeFox-R10.1_002-Beta-dipper.zip
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
If that is not an option:
A lot of people have trouble flashing TWRP, so dont get discouraged. After flashing recovery you must immediately boot to recovery and flash root then choose reboot to recovery. You may see check boxes asking to install TWRP manager, choose yes and reboot to TWRP.
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
If your phone doesn't reboot in TWRP it may be overwritten by the ROM's recovery.
Unplug Your phone then Manually boot it into recovery
PS: Welcome to XDA, good manners when someone takes their time helping is to give thanks by clicking the thanks button. Don't say thanks click the button. See the signature. good luck.

Hi,
tsongming said:
Are you sure that you have developer options setup? ADB debugging is enabled?
Click to expand...
Click to collapse
Yes, I am. This is not the first time i switched to lineage /cyanogen mod. I already customized a Nexus 4 (mako), Motorola Moto G (falcon), Samsung Galaxy S4 (jfltexx), Samsung Galaxy Tab S2 (gts210vewifi)
and LG V20 (h990ds). So I'm not new to this.
tsongming said:
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
Click to expand...
Click to collapse
I see this in this subsection and i marked it already, since you suggest it i will try it as soon the flashing is working.
tsongming said:
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
Click to expand...
Click to collapse
Sorry, Germany
tsongming said:
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
Click to expand...
Click to collapse
I don't see the point why the image must have a name with only characters, but i renamed the image to twrp.img and tried:
In Android with developer options enabled (and pc allowed):
Code:
adb reboot fastboot
Now i'm in fastboot and using my zsh on linux, im on my home directory located the twrp.img:
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.279s]
Writing 'recovery' OKAY [ 0.118s]
Finished. Total time: 1.402s
Now the command to upload and boot to the same image:
Code:
~ fastboot boot twrp.img
Sending 'boot.img' (42044 KB) OKAY [ 1.236s]
Booting OKAY [ 0.067s]
Finished. Total time: 1.341s
On device: bank screen (about 5 sec) > mi logo with unlocked symbol/text (about 3 sec) > mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.
Second try manual:
Code:
adb reboot fastboot
Flashing...
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.248s]
Writing 'recovery' OKAY [ 0.107s]
Finished. Total time: 1.360s
Unplug the phone, pressing now together VOLUME-UP and POWER until device going black and mi logo showing and devices vibrates. => mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.

Similar issue
I have the exact same issue. Did you manage to find a solution?

dojabato said:
I have the exact same issue. Did you manage to find a solution?
Click to expand...
Click to collapse
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.

I found the solution
to-bu said:
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.
Click to expand...
Click to collapse
Hello,
I was in the same case like you, to resolve this issue you must install this TWRP : TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN
Sorry I'm new and can't post links...
I installed with the TOOL ALL IN ON => Erase all data => recovery flasher (check only automatic TWRP...) => POWER+Volume down => POWER+Volume up very quickly => Enjoy it !

[HELP] Google Pixel 5 bricked (LineageOS for microG 18.1)?

Hi All,
After several years (since 2006) of playing with flashing and rooting the hardware, the day has finally come (I still hope not ...) - I broke my smartphone.
Don't ask me why it happened - I think I was rocking in the clouds by turning off USB debugging while I was still getting my stuff back from backups... Maybe I clicked this option by accident. But one by one:
1. I have downgraded the LineageOS for microG 18.1 ROM to the April 11 version (the newer one had huge connectivity problems :[).
2. Everything worked fine again, unfortunately I have restored too many files (some system files) using my root backup and after rebooting I have bootloop.
The above would not be a problem, but:
* USB debugging is disabled (I don't know if there is a hack method on Pixel 5 to enable it from PC (I'm using Linux)). Flashing recovery seems unavailable (Writing 'recovery' FAILED (remote: 'No such file or directory')), the same with adb sideload commands.
* adb shell is unavailable (I tried to send a ROM image file to the device) due to lack of any trusted device on Pixel 5.
(db: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.)
adb kill-server/start-server and deleting my Linux adbkey doesn't work of course.
I can only add that I have root access and an unlocked bootloader, but I don't know if I can do anything on this basis.
Is there any magician on the forum who has an idea for my brick with bootlooping screen?

Maybe this can work for you? >> Deuces Flashing Script
It should work with any google factory image as stated in the post, don't download the wrong factory image tho.
Goodluck.

XDHx86 said:
Maybe this can work for you? >> Deuces Flashing Script
It should work with any google factory image as stated in the post, don't download the wrong factory image tho.
Goodluck.
Click to expand...
Click to collapse
Thank you very much! I have only recently been with Pixel and did not know about the existence of this script.
Interestingly, on my first try on Pixel 5 the script crashed, it requires fastbootd instead of the fastboot standard:
system
Sending 'system_b' (23660 KB) OKAY [ 0.700s]
Writing 'system_b' FAILED (remote: 'Partition should be flashed in fastbootd')
as a result, the system did not rise.
Quickly switched to recovery and then fastbootd on the second attempt was successful.

Michu_z said:
Thank you very much! I have only recently been with Pixel and did not know about the existence of this script.
Interestingly, on my first try on Pixel 5 the script crashed, it requires fastbootd instead of the fastboot standard:
system
Sending 'system_b' (23660 KB) OKAY [ 0.700s]
Writing 'system_b' FAILED (remote: 'Partition should be flashed in fastbootd')
as a result, the system did not rise.
Quickly switched to recovery and then fastbootd on the second attempt was successful.
Click to expand...
Click to collapse
No need for a magician then I guess, haha.
Glad it worked out mate, don't brick your phone again. I think pixel phones are one of the hardest to fix.