[UPDATE - SOLVED - It was the USB cable. Tried another cable in another USB port on my PC, everything came up roses!]
Hi Everyone, I"ve been following XDA since I got my A700 in late 2012 and have finally decided to attempt rooting and flashing. I wanted to try something based on CM11, like the Omni, PacMan or base Cyanogen ROMs located here. I appreciate your patience with my noobness, I haven't programmed anything since my VB6/VBA days and that was a good decade ago!
First I tried the methods located here:
http://forum.xda-developers.com/showthread.php?t=1984566
Note that I have owned the tab for almost two years and have not modified it in any way. I did a full reset and wipe through Android in preparation for this.
I did get as far as unlocking the bootloader. However, when I attempted to install the recovery at this command:
fastboot flash recovery recovery.img
the tablet reboots and the text in the upper left blinks:
Bootloader vJB-XXXX(Unlock Mode): Starting Fastboot USB download protocol
And stops there. In my cmd window it mentions that it is flashing my recovery.img and the file size, but stops there. I am able to power off and reboot, at which point the cmd window says that it has failed to send the .img with this message:
FAILED (data transfer failure (Too many links))
finished. total time: XXXX s
Update: Another attempt gets be the following message:
FAILED (data transfer failure (Unknown error))
Do you have to root it first? I have since tried the Vorbeth Easyroot from here:
http://forum.xda-developers.com/showthread.php?t=1953917
And it still hangs at the same USB Download Protocol message above, also unable to send the boot.img to the tab.
I will try wiping and rebooting the tab again next. I have downloaded the Adnroid SDK and installed the Eclipse add-on as instructed.
Update: I've wiped again (though it still seems to stay in Unlock Mode) and tried the Root again, same results.
Any thoughts? Thanks in advance from an old-timer!
Mark
Impromark said:
Hi Everyone, I"ve been following XDA since I got my A700 in late 2012 and have finally decided to attempt rooting and flashing. I wanted to try something based on CM11, like the Omni, PacMan or base Cyanogen ROMs located here. I appreciate your patience with my noobness, I haven't programmed anything since my VB6/VBA days and that was a good decade ago!
First I tried the methods located here:
http://forum.xda-developers.com/showthread.php?t=1984566
Note that I have owned the tab for almost two years and have not modified it in any way. I did a full reset and wipe through Android in preparation for this.
I did get as far as unlocking the bootloader. However, when I attempted to install the recovery at this command:
fastboot flash recovery recovery.img
the tablet reboots and the text in the upper left blinks:
Bootloader vJB-XXXX(Unlock Mode): Starting Fastboot USB download protocol
And stops there. In my cmd window it mentions that it is flashing my recovery.img and the file size, but stops there. I am able to power off and reboot, at which point the cmd window says that it has failed to send the .img with this message:
FAILED (data transfer failure (Too many links))
finished. total time: XXXX s
Update: Another attempt gets be the following message:
FAILED (data transfer failure (Unknown error))
Do you have to root it first? I have since tried the Vorbeth Easyroot from here:
http://forum.xda-developers.com/showthread.php?t=1953917
And it still hangs at the same USB Download Protocol message above, also unable to send the boot.img to the tab.
I will try wiping and rebooting the tab again next. I have downloaded the Adnroid SDK and installed the Eclipse add-on as instructed.
Update: I've wiped again (though it still seems to stay in Unlock Mode) and tried the Root again, same results.
Any thoughts? Thanks in advance from an old-timer!
Mark
Click to expand...
Click to collapse
It should be a pretty straightforward process. Let's make sure you're doing it in order.
1) Turn on USB Debugging in your tabs Settings/development options
2) Plug in the tab to the PC
3) In the folder where you have the custom recovery.img, open a CMD window
4) Type adb devices and hit ENTER (should see a device listed, not offline)
5) Type adb reboot bootloader and hit ENTER (should reboot to the bootloader)
6) Type fastboot flash recovery recovery.img and hit ENTER (should go to download mode and transfer file)
Some things you might try;
Fresh boot your PC
Use a different USB port on the PC
Use a different USB cable
Use a win 7 pc, win 8 is ok, but win 8.1 can be a bit wonky
Now, some info for you. If you plan on installing a KitKat (4.4.x) rom, you will need to use a newer adb.exe file after installation. The older one won't work anymore. You can usually find the small package in some of the newer device forums that use Android 4.4.x. That's what I did. Generally you can find the small packages that contain adb.exe, fastboot.exe and the 4 or 5 .dll files. I think I snagged mine from a Samsung forum. But this is only after you get the 4.4.x ROM installed.
Also, make sure your recovery matches your Android version ROM you are using. If ICS, use an ICS recovery. If JB, use a JB based recovery, if Kit Kat 4.4.x, use the newest recovery. I believe the newest TWRP works well with KitKat ROMs.
You do not need to install the Android SDK. For what you are doing, you only need the small package. My and Vorbeths "Easy Root" threads have the necessary files for JB based roms, and also contain a compatible JB based recovery. But vorbeths download links are probably bad if I recall.
As for rooting, it's always best to root it first. This can be done with a modified boot.img and superuser, but I don't think it's necessary.
Hope this helps.
That's fantastic MD, thanks for this! I'll try it over the next couple days (it's Canadian Thanksgiving, don'cha know) and report back. At the end of it, I hope to post some step-by-steps for newbies such as myself to go straight to a KK ROM, which is my ultimate goal.
Mark
Update - the problem was the USB cable. I had no idea that this could be a factor, as I had been using the same cable to transfer files to the tab all this time and it accepted my commands to unlock the bootloader just fine. Once I swapped out the .99 eBay cable for the nice thick one that came with my LG G-Pad 8.3 (which should be telling, really), everything was fine and I was able to root, flash CWM and then a ROM without issues.
Note that in my case I didn't need to update the ADB.exe file, the one I had downloaded was from 6/14/2014 and while I'm not at all sure where it comes into play, I had no problems flashing and using a Kitkat ROM.
Currently on the PacMan ROM, and it's like having a new tablet to play with, albeit with half the RAM I'm used to on my other tablet, and the ever-so-annoying touch response problems that came with the A700. Will be trying the Omni, CM11 nightly and others in due course.
Thanks again MD for the assist!
Mark
Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hi there,
I'm tearing my hair out here. I have an HTC sensation which I inherited off my girlfriend. I tried to update it OTA and it says something like "variant system version htc" etc. I thought oh maybe somehow the bootloader has been tampered with. I previously had a rooted HTC desire for a couple years. I thought oh I'll just root this as well. I've tried on two occassions over 6+ hours to unlock this sensation via HTC Dev and it just doesn't work. I download sdk and put fastboot and adb in a folder. Connect the phone with USB and go into terminal and type cd and drag the folder in to make sure location is right. Then type ./fastboot oem get_identifier_token and it has either said "permission denied" or most commonly "waiting for device". So after shedding tears of rage, I gave up on that route. I thought instead ok lets see if I can go via OTA. So I called HTC and they rain my IMEI and apparently this phone is French (I'm in Australia) and thats why the OTA updates aren't working. He recommended I call the French HTC support and see what they can do. Funny thing is, I don't speak French.
Before I throw this phone off the highest place I can, is there any way I can get this OTA French update online off someone or a download website?
Model number: HTC sensation z710e
Thanks in advance for any helpful comments. I've done lots of reading and seem to be going in circles. From what I've read there doesn't appear to be a one click root app for the Sensation as existed for my HTC desire.
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
you can easily unlock the device !!!
i think you are missing few points here
1. uncheck fastboot in settings -> power/battery
2. also enable "usb debugging" in settings ->developer options
3.then once you connect the phone from bootloader to the pc
( to go to bootloader ..power off phone ..remove battery , reinsert it ..then hold power + volume down buttons together until you get the bootloader screen a few seconds ))
4. if the connection is proper and you have proper drivers installed the phone says "FASTBOOT USB"
if the phone is saying :HBOOT" press power button once then it should say "FASTBOOT USB"
if the phone is just saying "FASTBOOT" that means connection is not proper or drivers are not installed
for proper connection : you can only use usb 2.0 ports ..usb 3.0 port and usb hubs dont work properly ..also if using pc connect to back usb ports
for proper drivers: you need to have HTC sync installed ..or if you have windows 7/8 32 bit install these drivers ..if you have windows 7/8 64 bit install these drivers (NOTE: if you plan to use these drivers .uninstall every HTC related software from control panel then reboot and install these ..and dont install HTC sync any more)
5. to check proper connection
type this command from your adb/fastboot folder
fastboot devices (it should list your device )
6. then continue with the rest of process
success
Thanks for your reply.
I have good news and bad news.
The good news is I have S-OFF and rooted my phone.
The bad news is that both JB roms I have tried I am unable to get passed choosing my language after the phone has started. I select any language (say english US) and it just freezes and then after 10 seconds restarts. This is with the CM 10.1 and AOSP 4.2.2 roms from development section. When installing these roms I make a nand backup, then wiped data and cache as well as dalvik cache. Then install the rom and JBapps. Any ideas on what to try to fix this? For now I have reverted to my backup.
Onto how I unlocked and rooted.
I was consistently getting an error in terminal when typing ./fastboot oem get_identifier_token
It would say .... ERROR
After a lot of googling I discovered that I was most likely getting that error because my HBOOT was too old for the HTCDEV method.
So I tried the revolutionary method which worked perfectly. Than installed clockwork recovery, gained root (did a dance for joy) and now here I am very close to JB goodness just need to figure out why it keeps on rebooting.
Any help is appreciated. :laugh:
lui8906 said:
Thanks for your reply.
I have good news and bad news.
The good news is I have S-OFF and rooted my phone.
The bad news is that both JB roms I have tried I am unable to get passed choosing my language after the phone has started. I select any language (say english US) and it just freezes and then after 10 seconds restarts. This is with the CM 10.1 and AOSP 4.2.2 roms from development section. When installing these roms I make a nand backup, then wiped data and cache as well as dalvik cache. Then install the rom and JBapps. Any ideas on what to try to fix this? For now I have reverted to my backup.
Onto how I unlocked and rooted.
I was consistently getting an error in terminal when typing ./fastboot oem get_identifier_token
It would say .... ERROR
After a lot of googling I discovered that I was most likely getting that error because my HBOOT was too old for the HTCDEV method.
So I tried the revolutionary method which worked perfectly. Than installed clockwork recovery, gained root (did a dance for joy) and now here I am very close to JB goodness just need to figure out why it keeps on rebooting.
Any help is appreciated. :laugh:
Click to expand...
Click to collapse
You've done soff via revolutionary means you've got 1.17 firmware.. For ics and jellybeans you need 3.32/3.33 firmware.. Grab the latest firmware from kohr-ah firmware thread in sensation development section and flash it.. Then flash any ics/jb rom
Sent from my HTC Sensation using xda premium
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk
ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.
LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >
Bro...
Can you explain further,
1. I am here;
2. I am rooted, TWRP
3. Want to try ADB side load.
4. ALL necessary drivers loaded to PC (Perfect Environment)
5. USB debugging
6. Want to know where to keep flashable ROM exactly
7. Want to know what to type in command prompt and when
Note: I am doing this because I want a fresh, FRESH installation because I think my wifi got corrupted, it is not working often, not even turning on, i have tried:
1. Factory reset
2. leaving stock for CM 12 lollipop (not a complete wipe)
3. downgrade to stock kitkat using lg flash tool
Yet to try:
1. A complete wipe and adb side load for installing a fresh ROM
2. Downgrade to JB
Please advise ASAP...
Note 2: Today I dismantled the device completely (A to Z) all screws and connection.. even the battery because I the device used to restart when l lay down it on its back untouched... it got fixed by this re connection of all possible cables inside.. still i see a chance of hardware issue behind this wifi head ache but i want to try all the possibilities before i take it to any shop ...
thanks for reading...
Hi
Thanks for writing to us at XDA Assist. There are many guides on how to use adb sideload on XDA, here's just one:
[GUIDE] CWM/TWRP ADB Sideload
No response in two days, thread closed.
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.