Database Info

Phone stuck on boot animation, won't sideload

I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.

pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?

All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.

rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1

pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.

zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")

You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus

rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back

rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."

pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?

rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1

pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed

pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.

Flashfire can't see my zip

I am trying to use Flashfire v0.53 to update my Google-sourced, rooted Pixel from 7.1.0 (build NDE63X) to 7.1.1 (build NMF26V). I've downloaded sailfish-ota-nmf26v-1988a458.zip to my phone and can see it with a root file browser but when I direct Flashfire to the same directory it lists no files. Any thoughts? If I'm going about updating my phone the wrong way, I'm happy to be pointed in the right direction. Thanks.

FlashFire is not working on this phone last I heard. Flash it with TWRP.

TonikJDK said:
FlashFire is not working on this phone last I heard. Flash it with TWRP.
Click to expand...
Click to collapse
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.

ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around

aholeinthewor1d said:
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187 seems promising. I can adapt to use sailfish vs. marlin. But I'm not sure how to know which image is for Verizon.

ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.

fritzgerald said:
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
Click to expand...
Click to collapse
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?

ChrisNelsonPE said:
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
Click to expand...
Click to collapse
That's correct. If you downloaded the OTA with System Updates then I'm not sure where it gets stored. If you downloaded it from Google then it would be in your downloads folder.

You can try the guide I wrote here to sideload the full ota zip from google.

adb sideload failure
spiller37 said:
You can try the guide I wrote here to sideload the full ota zip from google.
Click to expand...
Click to collapse
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.

ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Sounds like the driver isn't recognized. Does ADB devices list your device?

ChrisNelsonPE said:
...
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.

ChrisNelsonPE said:
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
Click to expand...
Click to collapse
Alpha 2 is the wrong TWRP. You want RC1.

ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?

spiller37 said:
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
Click to expand...
Click to collapse
Yes.

TonikJDK said:
Alpha 2 is the wrong TWRP. You want RC1.
Click to expand...
Click to collapse
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?

ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
I get into TWRP on my phone an do
Code:
PS C:\adb> fastboot .\twrp-3.0.2-0-RC1-fastboot-sailfish.img
< waiting for device >
on my computer and it waits forever.

ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
Power it down, hold power button and volume down to get it into fastboot.
Fastboot flash TWRPfilename.img
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.

TonikJDK said:
...
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
Click to expand...
Click to collapse
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?

ChrisNelsonPE said:
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
Click to expand...
Click to collapse
Unzip it into your fastboot directory. Then edit and run flashall.

twrp recovery issue

following the xz2 twrp recovery thread ive found myself stuck in front of a laptop for ten hours now and i got as far as step 2 after unlocking the bootloader and gaining access to twrp menu. What I do not understand is that I have the twrp.img pushed from pc but when attempting to install recovery ramdisk there is no twrp.img pulled nor any other files, just empty folders. Have i fluffed something up or have i just come into an unrootable xz2?

jre1986 said:
following the xz2 twrp recovery thread ive found myself stuck in front of a laptop for ten hours now and i got as far as step 2 after unlocking the bootloader and gaining access to twrp menu. What I do not understand is that I have the twrp.img pushed from pc but when attempting to install recovery ramdisk there is no twrp.img pulled nor any other files, just empty folders. Have i fluffed something up or have i just come into an unrootable xz2?
Click to expand...
Click to collapse
phone in recovery connected to computer should show up on devices list. Use the computer to copy the twrp img to the phone...

levone1 said:
phone in recovery connected to computer should show up on devices list. Use the computer to copy the twrp img to the phone...
Click to expand...
Click to collapse
ok, how do i do that sorry

jre1986 said:
ok, how do i do that sorry
Click to expand...
Click to collapse
He did mean the file transfer Dialogue not workong in your Windows 8.1 Machine

"The system has been destroyed" Poco X3 NFC

So I was just messing around with my phone and somehow "destroyed" it. Is it possible to somehow flash it?

xiaomi.eu_multi_POCOX3NFC_V12.0.8.0.QJGMIXM_v12-10

MilanTom said:
So I was just messing around with my phone and somehow "destroyed" it. Is it possible to somehow flash it?
Click to expand...
Click to collapse
Don't worry dude. You can still take your phone to fastboot mode. Download a FASTBOOT rom (*.gz or *.tgz) from mifirm.net then flash it via mi-flash (download from mi-globe). Follow the instructions on mifirm.net

adadwa
ndminhdev said:
Download a FASTBOOT rom (*.gz or *.tgz) from mifirm.net
Click to expand...
Click to collapse
Ok I understand that and I've downloaded the ROM but there is this sentence "1. If Fastboot firmware. The ext. must be tgz. If not. Rename it from .gz to .tgz. Extract it by WinRAR" and also these sentences "ZIP. ZIP ROM using Update function in System or TWRP EU. EU ROM flash using TWRP".
I am just completely lost

To be simple : your flash went wrong probably with a bad rom download or a bad flash method.
If I were you I'd reread the post on installing Xiaomi.eu rom and redownload the whole.
Install OrangeFox recovery with the corresponding thread in the forum and ask if you're still lost
By the way, how did you flash that ROM?

Howell said:
By the way, how did you flash that ROM?
Click to expand...
Click to collapse
Well I started on this site https://magiskmanager.com/#How_to_I...Version_220_on_Android_Custom_Recovery_Option and downloaded the stuff that the site said was needed

And which recovery are you using ?

You should be able to reflash stock and recover your phone using the MiFlash tool.
Download fastboot ROM here, and MiFlash tool here.

And also the problem is, that my phone (Poco X3 NFC) isn't being shown in the MiFlash software. I can access the fastboot screen on my phone and yet it still won't show up

Adb drivers are installed ?

Howell said:
Adb drivers are installed ?
Click to expand...
Click to collapse
Yessir

Howell said:
And which recovery are you using ?
Click to expand...
Click to collapse
I don't know If I even have one, because when I hold Volume + and Power button, nothing happens

MilanTom said:
I don't know If I even have one, because when I hold Volume + and Power button, nothing happens
Click to expand...
Click to collapse
But I am pretty sure I tried to install TWRP Recovery

Mate that's just caused by something going wrong. The only times I get that message is the times I have tried to flash a GSI.
I don't know if you can with this unit?
I've fixed that about 5 times with miflash or miflashpro.
Do you have miflash?
It forces a reformat of Miui recovery rom an then you can start again. Just pay close attention to the bottom right hand corner an make sure it is off default. Default is 'relock bootloader'.
MilanTom said:
So I was just messing around with my phone and somehow "destroyed" it. Is it possible to somehow flash it?
Click to expand...
Click to collapse

If drivers are installed an
Howell said:
Adb drivers are installed ?
Click to expand...
Click to collapse
everything is up an running you should be able to get it into fastboot mode (picture of little rabbit fixing his android) an use miflash to reformat an force a flash of miui recovery rom.
I had that happen once with me an it turned out it was my type c cable. Pulled it out an plugged in a wala. PC could connect with my Poco

Bryceicle1971 said:
I had that happen once with me an it turned out it was my type c cable. Pulled it out an plugged in a wala. PC could connect with my Poco
Click to expand...
Click to collapse
The problem is that my computer can't find my phone. Nothing happens when I plug in the USB-C Cable. It doesn't work on the Fastboot screen nor does it work on "the System has been destroyed" screen. I am pretty sure I downloaded the neeeden drivers. And also, the phone was being found/recognized in the working state.

You need to extract then extract again. You double extract with a fastboot image. Then in miflash you find where you extracted that image to. Then hit refresh in miflash an your device should show in miflash. Miflash can be a tricky beast till you have practiced using it a few times

Hi. If you haven't fixed it yet you can try this: Download stock ROM from here (make sure it's the right one for your device!), choose Recovery ROM download link. Put it in your ADB folder. Do the same with recovery. Download this version of recovery as well. Enter fastboot mode on your device and connect it to your PC. Make sure it's detected. If not, try a different USB port on your computer. Open ADB using Open CMD.bat file in ADB folder.
Type in:
fastboot flash recovery OrangeFox-R11.0_6_Alpha-Unofficial-surya.img (hit Enter)
Type in:
fastboot reboot recovery
You should now be able to access your device internal storage from your PC. Copy the downloaded ROM file and OrangeFox-R11-Unofficial-Beta-surya-10-01.zip to your phone (put them in "Download" folder so they're easy to find).
Using Orange Fox recovery file manager find OrangeFox-R11-Unofficial-Beta-surya-10-01.zip and flash it then REBOOT TO RECOVERY.
Using Orange Fox recovery file manager find your ROM file and flash it. Do not reboot! Hit BACK and choose WIPE in Orange Fox menu (Trashcan icon, second from the right) and switch to Format Data at the top. Read the instructions and follow them by typing YES. Reboot to system. You should now have a working device with a clean stock ROM and a custom recovery installed and keep messing around with it

MocnePifko said:
Put it in your ADB folder.
Click to expand...
Click to collapse
Just two more question.
Where does one get the ADB folder? I may have downloaded a few but I don't know if those were good/correct for my device.
And what can I do when the device is not being detected by my computer? Like should I download and install some new drivers?

But can you reach the fastboot splash in your phone?

Question OnePlus 9 LE2110 256GB No OS No Recovery

As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.

DoktorNo said:
As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.
Click to expand...
Click to collapse
Try:
fastboot flashing unlock
then
fastboot flashing unlock_critical

Thank you for the reply.
The device is already unlocked, but I did as you suggested and tried both commands.
For both attempts I got the following message:
FAILED <remote : ' Device already : unlocked!'>
Fastboot: error: Command failed.

@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.

mx597turbo said:
@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.
Click to expand...
Click to collapse
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.

Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota

XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
I haven't tried it. I'll give it a go when I'm home this evening and post my results.

DoktorNo said:
I haven't tried it. I'll give it a go when I'm home this evening and post my results.
Click to expand...
Click to collapse
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.

mx597turbo said:
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.
Click to expand...
Click to collapse
Great question and worth asking. I used twrp 3.5.1_lemonade-Nebrassy.
3.5.1-lemonadep-Nebrassy
Since there's no OS, there is no interface with the touchscreen, so I can't interact with it in that way. I can sideload twrp but then it's just an image on the screen.

There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.

DoktorNo said:
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.
Click to expand...
Click to collapse
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.

mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
This works , mouse and keyboard

XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.

XxBigBuckxX said:
There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.
Click to expand...
Click to collapse
Got the new twrp. Still no touch screen.

mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
I will have to buy an adapter.

Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.

DoktorNo said:
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.
Click to expand...
Click to collapse
Last thing you will need is the driver, here is the signed Microsoft version.
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
I Find it easier to have push start on msm tool at this point
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them. and it should connect and flash.

XxBigBuckxX said:
Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.
Click to expand...
Click to collapse
Downloading now. I'll try this and report back. Thanks.

DoktorNo said:
Downloading now. I'll try this and report back. Thanks.
Click to expand...
Click to collapse
Okay and you might have to try it power cycle it a few times trying to get into edl mode especially if you do not already have working drivers. But windows update will pull working drivers as well if your not sure how to use a .cab file. There are guides everywhere even video if if you need. I've tested some weird things on the 7t pro McLaren and 9 pro and msm tool has always brought them back.

hj