Develop Bugs

Help. Two Mi Max stuck on Mi logo.

I have a two phones.
Mi Max 3/32 : Global 8.1.6.0. I recieved OTA to 8.2.1.0. Start downloading, on 40%+- phone freeze and reboot. Stuck on MI logo and dont boot. Dont show powered by android. Just mi logo.
Then i flash 8.2.1.0 trough MiFlash, bootloader locked, and... Same situation. Stuck on bootlogo. I Flash china rom, i flash global, flash older version. Come on Xiaomi! What wrong with you?!
Okay. Story #2
Mi max pro 3/64. Global 8.0.3.0. I downloading OTA, press instal, phone reboot and go install update. Ok. After this process, phone boot and... Cycle reboot. Again and again. On launcher, on setup wizards, on mi logo. Everywhere. Hmmm, okay, i open miflash repeat all as in story #1. Not effect. Zero. Cycle reboot. How?!
I dont know.
Both phones not bricks. But and dont work.
Debugging on usb is a necessary? I dont activated bcaz my phones dont booted. Funny, yeah.

Can it connect via adb?
Sent from my MI MAX using Tapatalk

RAMBO29 said:
Can it connect via adb?
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
yes

If it can connect via adb, flash via EDL mode and see.

If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom

IndDoc said:
If it can connect via adb, flash via EDL mode and see.
Click to expand...
Click to collapse
hmm, for this it is necessary unlock boot?

SubwayChamp said:
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
Click to expand...
Click to collapse
okay,
I did so. flash firmware and immediately bootloop. no root.

Dark_Eyes said:
hmm, for this it is necessary unlock boot?
Click to expand...
Click to collapse
Not required if you're going to flash the stable version.

IndDoc said:
Not required if you're going to flash the stable version.
Click to expand...
Click to collapse
sorry my mistake, i try but fastboot devices comand work (see device), adb ... not.
flash via fastboot
FAILED (remote: device is locked. Cannot erase).
need to unlock, yep?

That's not EDL, that's fastboot. See here for a guide how to use EDL mode.

IndDoc said:
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
Click to expand...
Click to collapse
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE

Dark_Eyes said:
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Click to expand...
Click to collapse
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.

IndDoc said:
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
Click to expand...
Click to collapse
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.

Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Sounds like you have a hardware problem. Take it to a service center.

IndDoc said:
Sounds like you have a hardware problem. Take it to a service center.
Click to expand...
Click to collapse
agree, it seems. thank you.

Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you

SubwayChamp said:
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
Click to expand...
Click to collapse
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?

Dark_Eyes said:
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Click to expand...
Click to collapse
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom

SubwayChamp said:
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
Click to expand...
Click to collapse
after i click flash all, window appears 1 sec and all. no effect. what wrong?

Dark_Eyes said:
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Click to expand...
Click to collapse
Recogniced device?, type first fastboot devices to be sure

Question One Plus 9 Pro Unbrick/Bootloop

Hey Guys i have an Big Problem and i dont knwo what to please help
So i wanted to flash lineageos and that worked good but its garbage the camera ist very basic and there are a lot of features which not work
So i decide to get back to Oxygenos und root it
Yeah and know my phone is stuck at something it only shows the one plus logo, sometimes nothing, and somethimes i get into fastboot but that not helping because when i boot or flash boot a recovery nothing happends it shows only the one plus logo!!
So i have an One Plus image but i cant sideload it into fastboot
is there an fastboot image?
i hope so!!
thans for reading i am from germany so my english is not the best

Use the msm tool for unbrick your devices

ChrisFeiveel said:
Use the msm tool for unbrick your devices
Click to expand...
Click to collapse
Hey thanks for anwering i have downloaded it but i really dont know how to use it
but the bigger problem ist that the phone only shows a red flash and a white circle!
so i cant get into fastboot

SeppelLetsPlay said:
Hey thanks for anwering i have downloaded it but i really dont know how to use it
but the bigger problem ist that the phone only shows a red flash and a white circle!
so i cant get into fastboot
Click to expand...
Click to collapse
Search for the link and be sure to read on how to use the tool completely until you understand!
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS​

TheGhost1951 said:
Search for the link and be sure to read on how to use the tool completely until you understand!
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS​
Click to expand...
Click to collapse
Yeah but i dont get in EDL or Fastboot
its only shows the obeplus logo every 3 seconds and reboot
but power + vol +/- are ignored
only +/- is also not working
please help i am despair

SeppelLetsPlay said:
Yeah but i dont get in EDL or Fastboot
its only shows the obeplus logo every 3 seconds and reboot
but power + vol +/- are ignored
only +/- is also not working
please help i am despair
Click to expand...
Click to collapse
Try power+vol- to get to recovery.... Other than that keep trying different button combinations... What happens when you hold both vol buttons and power button for more than ten seconds? To completely shut phone off hold vol up and power button. Otherwise I have heard some say let the phone battery run down battery until phone shuts off. Then try the buttons again. Only just both vol buttons no power and phone not plugged in. Start the MSM tool it will say waiting on device, then with phone off, hold both vol buttons down wait 10 seconds then connect phone to PC.

So when i press power + "-" nothing happend, no vibration, no screen nothing
when i press +/- and power the phone starts and there stands fastboot but a few seconds läter come the red flash and the phone shuts down(but it is onto an powercord)
when i only press +/- also nothing happend and the phone is not responded in msm

SeppelLetsPlay said:
So when i press power + "-" nothing happend, no vibration, no screen nothing
when i press +/- and power the phone starts and there stands fastboot but a few seconds läter come the red flash and the phone shuts down(but it is onto an powercord)
when i only press +/- also nothing happend and the phone is not responded in msm
Click to expand...
Click to collapse
Do not use +/- and power....do not use the power button just +/- only

TheGhost1951 said:
Do not use +/- and power....do not use the power button just +/- only
Click to expand...
Click to collapse
ok but as i sag wehen i power off the device(with fastboot) the +/- doesent work and its not regnosized
but i have sucsessfully launched twrp with fastboot boot twrp
but when i sideload the zip i get the error that the storage cant be mounted

SeppelLetsPlay said:
ok but as i sag wehen i power off the device(with fastboot) the +/- doesent work and its not regnosized
but i have sucsessfully launched twrp with fastboot boot twrp
but when i sideload the zip i get the error that the storage cant be mounted
Click to expand...
Click to collapse
You don't side load it, make sure the magisk app is located in phone storage, boot to twrp then select install while in twrp......

Ok and for what i need magisk first i must get oxygenos to run
and how can ich get magisk.apk onto the device? on my pc i cant see the phone/storage

SeppelLetsPlay said:
Ok and for what i need magisk first i must get oxygenos to run
and how can ich get magisk.apk onto the device?
Click to expand...
Click to collapse
Sorry that response was for another person!

TheGhost1951 said:
Sorry that response was for another person!
Click to expand...
Click to collapse
oh ok sorry

TheGhost1951 said:
You don't side load it, make sure the magisk app is located in phone storage, boot to twrp then select install while in twrp......
Click to expand...
Click to collapse
Ok, you were able to get to fastboot, now we are getting somewhere....hold on. We will get you up and running....!

You will need phone in fastboot mode connected to PC..,..do you have the ROM you want to flash?

TheGhost1951 said:
You will need phone in fastboot mode connected to PC..,..do you have the ROM you want to flash?
Click to expand...
Click to collapse
yeah i have the stock rom
c.47 europe full ota
OnePlus 9 and 9 Pro Firmware Flash File (Stock ROM)
If you're using a OnePlus 9 and 9 Pro or planning to buy it, then this guide is for you. If you want to install Stock Firmware, here we will share the
www.getdroidtips.com

SeppelLetsPlay said:
yeah i have the stock rom
c.47 europe full ota
OnePlus 9 and 9 Pro Firmware Flash File (Stock ROM)
If you're using a OnePlus 9 and 9 Pro or planning to buy it, then this guide is for you. If you want to install Stock Firmware, here we will share the
www.getdroidtips.com
Click to expand...
Click to collapse
Extract the zip, should see a payload.bin and change it to payload.img. then fastboot flash payload.img that will flash it to the phone... Then fastboot boot, that should reboot into setup screen on phone. If it doesn't, the last step would be to change the active slot and reboot again in fastboot mode...

Finally, from fastboot mode, fastboot twrp img and in twrp tap on reboot and boot to EDL mode with MSM tool "started" and that will start the process... If the above procedure fails! This is the way I recover from a crashed phone!

unknown partition 'payload.img'
error: cannot determine image filename for 'payload.img'
Does not work

SeppelLetsPlay said:
unknown partition 'payload.img'
error: cannot determine image filename for 'payload.img'
Does not work
Click to expand...
Click to collapse
Read my last post above...to use the MSM tool

Question BootLoop not letting me access fastboot

Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit.
Vol down + power buttons does not work. Neither does volum up + power. But when I press vol up+vol down+power my PC emits sound of connected device. I think that it is a problem of A/B partition, but I need to get to fastboot to fix it.
Any solution? I have already tried battery running out.

marcos_rgn said:
... my PC emits sound of connected device.
Click to expand...
Click to collapse
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.

.

Renate said:
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
Click to expand...
Click to collapse
This is with usblog.exe.
I have checked and adb devices and fastboot devices are empty even while device is connected (in that 3 seconds window). I have runned some commands with "wait-for-device" and they didnt work.

So you have the MediaTek ROM bootloader there.
I've played with some of the MediaTek stuff (and even started to write a native Windows MTK client), but I'm no expert.
There are two modes, 0e8d/0003 (ROM) and 0e8d/2000 (preloader).
You might look here: https://github.com/bkerler/mtkclient
Try holding the VolUp while rebooting to try to get 2000.

I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.

you can flash with this spflash tool to take back your phone.
SP Flash Tool v5.2044 Edited By Kurdish Gsm Team (Free Downlowd)
SP Flash Tool v5.2044 Modefiad Version With Auth Bypass Button
www.firmware4mobile.com
here is the video tutorial

Renate said:
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
Click to expand...
Click to collapse
I have stopped boot loop by flashing boot.img and vbmeta.img with MTK client, thank you!
Generally speaking, if I want to return to default ROM, what files should I flash? What are the "software pieces" that Magisk touches and modify?

marcos_rgn said:
What are the "software pieces" that Magisk touches and modify?
Click to expand...
Click to collapse
Normally, Magisk only needs to have the boot image replaced.
The instructions tell you to optionally make the vbmeta inactive, but Magisk ignores all that verification anyway.

Question Did I hard brick my phone? (SOLVED)

First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img

In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?

mbj731 said:
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Click to expand...
Click to collapse
Also, you need T-Mobile msm

oddlyspaced said:
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
Click to expand...
Click to collapse
I've tried that. Still no luck. Getting either "IMEI is incorrect" or "device doesnt match image" errors. Kind of odd getting different errors each time.
jamescable said:
Also, you need T-Mobile msm
Click to expand...
Click to collapse
I've tried them all just hoping one will work. Tmo-EU, Tmo, EU, Global etc etc

Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.

Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
I use USB C to USB C 3.2 with no issues

Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)

BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?

mbj731 said:
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
Click to expand...
Click to collapse
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.

Shooter7889 said:
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Click to expand...
Click to collapse
Yes, I had been running on A13 for a few days. Got the itch to root but as I said, I couldnt unlock bootloader (kept saying to flash token) so I decided to start the whole process over, unlock the bootloader and try to manually flash A13 instead of doing a local upgrade. (hadnt hit OTA for me yet)
During the process, theres a point where you have to boot in to fastbootD to flash critical partitions that wont flash in regular fastboot.... using the commands "fastboot reboot fastboot" wouldnt get me to fastbootD as I read it's supposed to. I think during all that and scrolling through the bootloader menu, I hit "recovery mode" which was apparently wiped because I just went straight to a black screen and thats where it's been ever since. I did all the button combos etc thinking it would just go back to bootloader but to no avail.
I wish there was a way to do manual commands in EDL or something. Maybe bootloader is there just that it's not responding to the hardware keys?

Oh. When u tried to unlock BL did u try "fastboot oem unlock? Yeh usually, eben if I mess up with msm or flashing imgs, it will kind of get stuck in edl, and I have to hold all three hardware buttons for some time b4 it will finally respond

Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck

First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.

kjslabber said:
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
Click to expand...
Click to collapse
I taped all the buttons down and I'll watch it for a while and see if it boots up. I have tried holding them for a very good while with no luck already though

Shooter7889 said:
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
Click to expand...
Click to collapse
I've tried the IND MSM gives me an "unsuspected target TMO" error or something like that. So at least some tools are seeing it as TMo... Tmo tools say the device doesnt match! I'll have to find another computer or 2 to try.. I was supposed to ship off my oneplus 7t tomorrow for trade in on this 9 pro but now I'm using the 7t again as it's my only working device. this has been a headache. lol
thanks for the feedback. I'm trying everything I can think of and researching too

Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol

mbj731 said:
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
Click to expand...
Click to collapse
Every one of us that's been at this long enough has gone thru this or a similar experience. It's a lot more headache but you also learn a lot more for the next time or to help others. Congrats on getting it up

mbj731 said:
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
Click to expand...
Click to collapse
You can use python3 to decrypt the .ops file, edit the first line parameters in the settings.ini, then python3 to encrypt the folder that was decrypted. Slow process but gives extra options.....

Question Bricked OnePlus 9 Pro

Hi guys,
A have flashed a couple of old phones, and then a friend asked me to flash a high-end phone. He is anti-Google, and wanted something that would give him privacy.
He purchased a new OnePlus 9 Pro, and asked me to install Lineage 20.
I managed to get the bootloader unlocked, using Adb and Fastboot commands.
I then tried to install TWRP. Got it working but for some reason I couldn't see the ROM I loaded. Couldn't see any of the normal directories and tried repairing the drive. Tried for a while, and then looked at Magisk.
Got that installed and then needed a boot.img to complete the patch. Found one where someone posted about the problem and gave a link to their boot.img file. This corrupted things.
Now the phone is in a Fastboot loop. I can't connect to my laptop, and the phone won't even charge when connected. Saw a couple of "Qualcomm dump", "die" messages.
I'm a noob and was following instructions as closely as I could. This is a friends new phone and would really appreciate any and all assistance you generous souls could offer!

Can you list:
Hardware model of phone ( on box )
Which rom was previously installed.
Someone should be able to assist from there.

Start here....
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com

Or here,
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com

As long as you can get to Fastboot you definitely can revive your phone. Always read, read, read and then read some more before diving into doing any flashing on an Android device!

AndyC76 said:
Can you list:
Hardware model of phone ( on box )
Which rom was previously installed.
Someone should be able to assist from there.
Click to expand...
Click to collapse
Hi.
Model No is LE2123 and Build No is Oxygen OS 11.2.9.9.LE15BA.

AndyC76 said:
Can you list:
Hardware model of phone ( on box )
Which rom was previously installed.
Someone should be able to assist from there.
Click to expand...
Click to collapse
Hi.
Model No is LE2123 and Build No is Oxygen OS 11.2.9.9.LE15BA.

TheGhost1951 said:
Start here....
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Ghost,
I have downloaded the specific MSM Tool, but cannot connect to the phone. The phone loops in Fastboot, and nothing else.
Any ideas?

Hi guys,
I have detailed my situation at the beginning of this thread. I have subsequently downloaded the specific MSM Download Tool, but as the phone is in a Fastboot loop, I cannot get my laptop to connect top the phone. Any ideas Please?

Try holding vol + and power button to shutdown the phone completely. Then hold down vol + and vol- and power buttons and see if it will boot to bootloader (fastboot) and stay..

Here are some steps I recommend to try if your device isn't being detected by your WINDOWS based PC
1. Disable Driver signature enforcement on windows 10 / 11 - google this if you don' know how to do
2. Install Oneplus Pro 9 drivers from official website of oneplus <------Make sure u do step 1 before you install them.
3. Have the latest adb platform tools and try again.
4. IF after trying the first 3 steps and still doesn't work, put your phone into EDL mode and use MSM tool. This requires the qualcomm drivers installed on your PC.

Use unbrick Firmware (MSM)

There's a trick to get the unbrick tool to recognize the device in FB mode. I think it's called EDL mode. I was in similar situation when I soft bricked my TMO variant OP9Pro.
@immortalwon posted the proper instructions. Those are the steps I had to do to unbrick my phone.

NewNoob911 said:
Hi guys,
I have detailed my situation at the beginning of this thread. I have subsequently downloaded the specific MSM Download Tool, but as the phone is in a Fastboot loop, I cannot get my laptop to connect top the phone. Any ideas Please?
Click to expand...
Click to collapse
Did you solved ?

In fastboot mode, temporary boot TWRP, fastboot boot name_of_twrp.img, then start MSM Tool on laptop make sure to click start in MSM tool. Then with phone connect to PC, in TWRP, tap on reboot then tap EDL.....there you go.

Reason you bricked, is you were on wrong firmware. Need A13 for Lineage 20. After MSM update to A13 before trying to flash.