Database Info

Nvidia Shield Tablet OEM Unlock

Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon

Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.

Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...

So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.

I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?

Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?

You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery

It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.

Redmi note 7 stuck in a bootloop. Can only access stock recovery, is it fixable?

Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.

Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.

jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?

I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.

oneplus 8t(tmo) hardstuck in fastboot mode

Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help

lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com

ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.

and that is the guide ive been following. however i keep getting partition issues.

lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".

okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.

solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help

lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.

nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.

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

the current image(boot/recovery) have been destroyed

I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?

samjoandco said:
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
Click to expand...
Click to collapse
TWRP will not boot up on OOS 12. Worse, it sometimes switches slots in the process (trying to fall back to the previous slot).
So, if you can get to bootloader, try changing slots and booting system (NOT recovery).
If that doesn't work, MSM is your friend.

BillGoss said:
TWRP will not boot up on OOS 12. Worse, it sometimes switches slots in the process (trying to fall back to the previous slot).
So, if you can get to bootloader, try changing slots and booting system (NOT recovery).
If that doesn't work, MSM is your friend.
Click to expand...
Click to collapse
MSM has been failing for me with sahara communication failed. i have been able to extract boot.img from stock image of 12 beta using dumper and flash it and it is not stuck on bootloader or recovery anymore, i can even adb shell and see directories but its is not completely up. need a way to dirty flash the zip again for whihc i think i need to wait for TWP of OOS 12. or keep trying the MSM

samjoandco said:
MSM has been failing for me with sahara communication failed. i have been able to extract boot.img from stock image of 12 beta using dumper and flash it and it is not stuck on bootloader or recovery anymore, i can even adb shell and see directories but its is not completely up. need a way to dirty flash the zip again for whihc i think i need to wait for TWP of OOS 12. or keep trying the MSM
Click to expand...
Click to collapse
Glad to hear that.
You can't afford to wait for TWRP 12 - it could be a very long wait.
So you can actually boot OOS 12 beta? What do you mean by "it is not completely up"?
You could try to install the apk mentioned in the https://forums.oneplus.com/threads/oxygenos-12-open-beta-1-for-the-oneplus-8t.1548475/ and use it to try to flash the beta zip again.
Also, if you can get into bootloader, you can always try to flash the files you get from payload dumper using the process described in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/ - just make sure you include all the my_* partitions (they are all logical partitions) as well.
Note also the process hidden in the "Spoiler" button which is where the my_* partitions need to be included.

Bill thanks for the udpaye
after restoring the boot.img and wiping out data i was able to get up to new setup screen and accept OP agreement screen and it would then hang.
subsequently
i tried to flash all the imgs as per the instructions you shared above.
almost all of them failed with either of these errors
remote: 'Flashing is not allowed for Critical Partitions'
OR
'fastboot: error: Could not check if partition abl has slot all'
After a few images that i could flash to slot a and b now the phone can only be in bootloader or recovery mode cant go beyond that.

samjoandco said:
Bill thanks for the udpaye
after restoring the boot.img and wiping out data i was able to get up to new setup screen and accept OP agreement screen and it would then hang.
subsequently
i tried to flash all the imgs as per the instructions you shared above.
almost all of them failed with either of these errors
remote: 'Flashing is not allowed for Critical Partitions'
OR
'fastboot: error: Could not check if partition abl has slot all'
After a few images that i could flash to slot a and b now the phone can only be in bootloader or recovery mode cant go beyond that.
Click to expand...
Click to collapse
You only flash boot, recovery, and dtbo in bootloader mode. All the others must be flashed in fastbootd mode.
Given the errors you had I don't think you did that, right?

BillGoss said:
You only flash boot, recovery, and dtbo in bootloader mode. All the others must be flashed in fastbootd mode.
Given the errors you had I don't think you did that, right?
Click to expand...
Click to collapse
Bill Many thanks , you are a genius!
I missed the fastbootd part. After trying again, I was able to quickly flash everything except the LPDDR4X / LPDDR5 memory chip flash because i didnt know which memory was there.
it is now up and running fine.
I owe you a coffee , thanks again
one more thing i noticied after upgrade is that executing the following command to find the memory type does not return anything. its blank , neither 0 nor 1 . i am not sure what is wrong.
adb shell getprop ro.boot.ddr_type
Click to expand...
Click to collapse
i still dont have 5G or mobile data with OO12. i want to flash the OOS12 again but dont see an option
----

samjoandco said:
Bill Many thanks , you are a genius!
I missed the fastbootd part. After trying again, I was able to quickly flash everything except the LPDDR4X / LPDDR5 memory chip flash because i didnt know which memory was there.
it is now up and running fine.
I owe you a coffee , thanks again
Click to expand...
Click to collapse
If you run getprop | grep ddr you'll see the ddr type of your device: 0 is ddr4, 1 is ddr 5.
Remember this so that next time you know which xbl files to flash.

BillGoss said:
If you run getprop | grep ddr you'll see the ddr type of your device: 0 is ddr4, 1 is ddr 5.
Remember this so that next time you know which xbl files to flash.
Click to expand...
Click to collapse
that entry is missing in getprop. there is no entry for ddr is what i am saying.
===edit====
I rolled back to OOS 11 using the APK you shared earlier from oneplus and have everything working back now.
apparently getprop | grep ddr =0 so i have LPDDR4X ( this is a more common chip for OP8T anyway)
all good. it was a good roller coaster ride for a day
Bill Thanks again

I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...

coebisho said:
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
Click to expand...
Click to collapse
I am not sure but I read in a few places that flashing the wrong version will damage the phone.
What did you flash 4 or 5?
Which rom did you extract to imgs?
Was it the the same rom / version that you originally had?
Did you try reaching out to OnePlus support? You can try for repair.

coebisho said:
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
Click to expand...
Click to collapse
You're probably in CrashDump mode but with no error displayed (I've been there also)
You should be able to get back to bootloader by:
- hold down Pwr+Vol Up until the phone buzzes
- immediately hold Pwr+Vol Down (or Pwr+Vol Up+Vol Down) and you should boot into bootloader
You can then flash the correct xbl* image files

samjoandco said:
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
Click to expand...
Click to collapse
same problem ....tried solution mentioned earlier but after first 3 commands same problem is there.... please help... tried erasing cache ...and recovery and tried flashing recovery again...but nothing is working
{Mod edit: Quotation fixed}
i am having the same problem "
the current image(boot/recovery) have been destroyed"
no solution has worked.
erase cache (​Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
same problem presists with other erase commands
booting into recovery says
Sending 'boot.img' (102400 KB) OKAY [ 2.343s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
please help ....... i have no idea what to try ..

magbrave said:
please help ....... i have no idea what to try ..
Click to expand...
Click to collapse
Did you try MSM tool?

Rootk1t said:
Did you try MSM tool?
Click to expand...
Click to collapse
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting

magbrave said:
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
Click to expand...
Click to collapse
same issue here fastboot not not detecting my device after crashing recovery. i even downloaded and installed driver from android studio which worked earlier now its not. it keep shows waiting for device

magbrave said:
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
Click to expand...
Click to collapse
Boot to EDL using hard keys!

i have same issue. corruption of boot img recovery happens when i boot into recovery on latest c20 update on kb2005. does anyone elses phone get destroyed on c20 when booting into recovery?

Which recovery did you use when you tried to boot into recovery when on OOS 12?

BillGoss said:
Which recovery did you use when you tried to boot into recovery when on OOS 12?
Click to expand...
Click to collapse
was on normal recovery that flashes when upgrading to oos12, stock recovery worked on c16 but when on c21 when boot into stock recovery my phone gets boot img destroyed