Database Info

No OS, TWRP fails to flash .ZIPs

Hey guys,
I'm having some trouble with flashing a new ROM and now I've soft-bricked my device.
I was trying to flash from CROMi to CM11 so I wiped data, cache, dalvik using TWRP. But when i tried to flash CM11 M9, i would get the "failed" error. I tried flashing other ROMs but same result - "FAILED".
So I thought maybe it was the recovery. I downloaded a CWM recovery (in .zip) and tried to flash it. FAILED!
I tried to restore my device using the "Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery" method from this post. Since it is basically flashing the stock ROM, naturally it fails.
Now I'm out of ideas. How can I save my tablet?
Thanks for your help guys!
PS: I'm trying to install CMW via fastboot. When I press power + vol down, I get to the screen with "RCK, Android, Data Wipe"; I dont see the USB icon. How do i boot into fastboot?

You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....

berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure

berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks!

oh.herro said:
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks![/QUOTE]
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse

r3dal3rt said:
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
Click to expand...
Click to collapse
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh

lj50036 said:
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
Click to expand...
Click to collapse
Exactly.
I also would like to know how you performed the wipe you mentioned. The tablet booting only and straight to recovery would indicate that you used 'Wipe Data' from the bootloader???
Also, do not use ROM Manager. It does not work well with the Transformers and can cause a lot of problems.
I have a feeling another user is going to benefit from your excellent unbrick guide, Josh...
Aren't you glad you wrote it?? [emoji12]

lj50036 said:
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.

oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
No boot to recovery ?
No bootloader ?
No nvflash blob backups ?
If that is the case then you are not looking good ...
There is no way out of this one ...
We need fastboot or recovery one or the other ..
Sorry for the bad news ....
Thx Josh

oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
I agree with lj - not looking good. [emoji17]
Do you have adb access when it boots to the Asus splash screen?

[Q] TWRP flash says successful... but stock recovery is still there?

Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?

fastboot reboot-bootloader ; just after recovery flash.

Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.

Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon

I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!

theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon

[Q&A] [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]

Q&A for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Does TWRP 2.8 (latest version 2.8.7.0) okay to start out with? Meaning, if we are at the latest version of stock (ASUS build JOP40D.US_epad-10.6.1.27-5-20130902; Android 4.2.1) and we are going to flash a custom rom for the first time, the latest versions of TWRP won't brick our devices?
It could be that I'm just confused because there were lots of older versions that reference individual Android builds (JB vs ICS). And people would say "if you have X version of Android, use Y version of TWRP or you're gonna brick it".

Can't enter twrp but everything ok
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12

I got sent here, so I'll try again.
I'm a little confused now, because I can't understand what is happening to my tablet. Let me explain step by step what I did, maybe one of you can figure out what is wrong.
I was running CM11 M12 with TWRP 2.8.1.0 and wanted to try the new Android 5.1. I decided to go with the latest Omnirom and found out I needed at least TWRP 2.8.5.0.
So first step would be to update TWRP. When I got at the TWRP website I read that there was something new in TWRP 2.8.4.0, so I decided to first go from .1 to .4 and then go to the latest .7. An upgrade to .4 went fine through Fastboot. Then I thought I could try the new in GUI recovery flasher, but I didn't understand it properly so I chose to go safe and flash the .7 through Fastboot.
I guess that's where I went wrong. The tablet went to recovery just fine, but in TWRP it couldn't access anything anymore. "Unable to mount" on everything. Internal storage was 0. It didn't boot to the ROM anymore.
So after some tinkering, not really sure what I did anymore, I got my access to the FS again. I had the CM11 M12 ROM still in the MicroSD, so I ran the "install ROM procedure" for that one and it booted again.
Only now I don't seem to have a recovery anymore. I can get into Fastboot, but when I send the "fastboot -i 0x0b05 flash staging twrp.blob" the tablet hangs itself. Holding power revives it and it boots to CM11M12 again. I tried to flash different TWRP versions (.4 .5 .6 and .7) but no sigar.
Does anyone have an idea how to get my recovery back?
Edit0: I tried to install the TWRP manager from the store and get a recovery from there, but the app doesn't work. It hangs when I try to tap on the "Recovery version to install" option.
Edit1: I followed the link in the post above and solved it. Next thing I did was flashing the .6 TWRP recovery and it stuck. Time to wrestle with some new roms! Thanks!
Edit2: Back to square one. The TWRP can't see anything in my internal storage. Is my storage memory going dry? "Unable to mount ###" shows up for every partition.
Edit3: And now it can see in my internal memory again... Hardware failure?

2.8.7.0 on tf300t reboot/shutdown does not work
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again

tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
for me it's the same..
thanks in advance
edy

aoesp3 said:
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?

anjeu67 said:
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
Click to expand...
Click to collapse
Nope. I am using lastest TWRP(2.8.7.0) now.

Hello
Can someone help me please?
For the moment i have TWRP 2.8.0.1 and i want to update it to 2.8.7.0.
First of all, i tried to update it with twrp manager.
So i open twrp manger
The install recovery screen opens and i choose for "Install Recovery".
Then i'm redirected to jmz software and then i got next screen:
Forbidden - you don't have permission to access /tf300t/ on this server.
What i'm i doing wrong?

tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
Same here... what gives?

Same here also.

ecb116 said:
Same here... what gives?
Click to expand...
Click to collapse
Same problem here,, no answers?

HELP! No SIM card detected after update

Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me

Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.

Same problem here with the 123015 update. Reverting to old roms did not work.

just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again

reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk

Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'

deleted

just back to 29/12 nightly, flash correct recovery and again flash 30/12

I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.

twrp-2.8.6.0

NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk

fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem

Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!

I get this issue as well.

IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.

bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk

Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...

¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk

Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?

well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk

Fastboot Bootloop

I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.

Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.img​Learned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.

Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.img​Learned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....

mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq

OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help

Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.