Database Info

Sprint GM1925 Stock ROM

I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.

aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock

Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.

aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.

Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!

Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.

My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.

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.

Cannot get oem unlock token oneplus 8 tmobile (in2017)

So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.

Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml

if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk

PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind

d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp

d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface

DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!

SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?

nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.

FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!

nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.

Need Help Installing Dynamic System Update

Ive tried installing the DSU by phone through developer options and when i restart the phone it just says DSU ready restart phone. Ive tried the adb way and got it to download and restarted my phone now there was no notification at all but the DSU was still not installed. Can anyone explain to me what im doing wrong.

ThatNiggaDurk666 said:
Ive tried installing the DSU by phone through developer options and when i restart the phone it just says DSU ready restart phone. Ive tried the adb way and got it to download and restarted my phone now there was no notification at all but the DSU was still not installed. Can anyone explain to me what im doing wrong.
Click to expand...
Click to collapse
I figured this out today...
Unlock your bootloader and use stock boot image(no magisk)
official aosp gsi(from dsu loader ui) and phh based gsis(with commands from official dsu page) work best.
Also check settings_dynamic_system option to true under feature flags within developer settings(on userdebug ROM) or do the setprop command found on androids official dsu page.
another note about the commands from official dsu page, the provided du command in android system may not support the -b flag, i ended up using "wc -c" to get byte size of system_raw.img in place of "du -b".
make sure your not using any sparse system images, convert those with simg2img, I also rename the gsi from lineage-19-x-x.img to system_raw.img then gzip -c system_raw.img >system_raw.gz make sure the system file name matches what is in the adb install commands, and the image name getting gzipped.
it is possible to run the commands from dsu page within rooted android device(i use adb root since magisk patched boot image only boots the host sustem with new userdata_gsi image)

mrbox23 said:
I figured this out today...
Unlock your bootloader and use stock boot image(no magisk)
official aosp gsi(from dsu loader ui) and phh based gsis(with commands from official dsu page) work best.
Also check settings_dynamic_system option to true under feature flags within developer settings(on userdebug ROM) or do the setprop command found on androids official dsu page.
another note about the commands from official dsu page, the provided du command in android system may not support the -b flag, i ended up using "wc -c" to get byte size of system_raw.img in place of "du -b".
make sure your not using any sparse system images, convert those with simg2img, I also rename the gsi from lineage-19-x-x.img to system_raw.img then gzip -c system_raw.img >system_raw.gz make sure the system file name matches what is in the adb install commands, and the image name getting gzipped.
it is possible to run the commands from dsu page within rooted android device(i use adb root since magisk patched boot image only boots the host sustem with nei just got the 1+ nord n200 5g ive tried everything including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
Click to expand...
Click to collapse
i just got the 1+ nord n200 5g ive tried the dsu loader and it brick my device ive tried everything i could including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point

ThatNiggaDurk666 said:
i just got the 1+ nord n200 5g ive tried the dsu loader and it brick my device ive tried everything i could including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
Click to expand...
Click to collapse
theres no screen for edl mode. launch msm tool, click start, connect phone, as soon as it finds device, it starts. make sure you have qualcom drivers

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