I have an OP 9 LE 2115 Global in USA
I was on LOS 19.
I had some issues and wanted to revert back to stock OOS 11.
First I tried via Recovery to flash Stock ROM OOS 11, but I had an error regarding the system version being too old and it didn't complete. The phone would no longer boot to OS.
I got the MSMDownloadTool from here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R/
I used the tool successfully and got my phone booting to OS again.
But now my power button IMMEDIATELY turns off the phone whenever pressed, and does this kind of CRT TV shutdown, where the screen phases out vertically with colors.
This happens in recovery/fastboot menus as well, most of the time, and makes booting into recovery/fastboot *almost* impossible, as when I let go of the power button it turns off, and when I select and option with the power button it shuts off.
Any information would be so helpful! Thank you fine knowledgeable people of XDA.
For anyone to help, we need to know which model you have and which version of msm tool did you use?
Updated my original post. My apologies for the lack of important details.
Also I got a TWRP recovery successfully installed, so I have a recovery again.
I found this article that explains how to install each part individually via fastboot
Do you think this would help with my errors of non-existent partitions?
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
I'm tempted to try, but if anyone could chime in first?
Still having this issue, has anyone ever even heard of this problem?
wakeeshi said:
Still having this issue, has anyone ever even heard of this problem?
Click to expand...
Click to collapse
This sounds like a hardware problem. If just after msm the phone does this, hardware it is then.
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
wakeeshi said:
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
Click to expand...
Click to collapse
Flash with msm again. If problem persist after first time setup, hardware problem.
MrSteelX said:
Flash with msm again. If problem persist after first time setup, hardware problem.
Click to expand...
Click to collapse
I have flashed with MSM a couple more times and same thing.
But for example, I got it to boot without the issue again, and everything works as normal, but as soon as I turn the phone off or it dies, I will struggle to get a boot that works properly.
I end up fiddling with the holding the volume buttons and power buttons in different combinations and eventually it works. I'm not sure if that's just random, or if I'm actually causing it.
If I can have a completely working boot, where the power/sleep button functions as normal, it seems like it's a firmware, data issue. Could you elaborate?
Thank you!
Hoping to bump this and try to get some help. My GPS also has failed to get a fix in this kerfuffle. (this is one of the reasons I was originally resetting to stock from LineageOS 19). Any advice?
Hardware problem and the fact it is 100% repeatable is a sign of hardware problem.
Related
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.
If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).
how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse
bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse
Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.
Hey guys was using my phone, Bluetooth on music streaming and I was typing away on WhatsApp and all of a sudden my phone froze up and then black screen. Then a few seconds later got a Qualcomm Crash dump screen with something about modem crash?
Anyone have this issue? Was able to reboot device after holding volume up and power button for a few seconds.
I havent had the issue myself but I've heard other OnePlus devices with this problem. Luckily you were able to fix it with a reboot but worse comes to worse you'll have to use the MSM tool.
What does the msm tool do? I've seen weird things with the phone, it does this shift to the screen sort of like you are taking a screen shot of the screen.
I do have this problem too since 2 weeks. I´m not rooted and not Bootloader unlocked. (waiting for my favourit rom)
It happens randomly. I didn´t had the time to go into it.
This is the issue see image
ludester said:
This is the issue see image
Click to expand...
Click to collapse
Yesterday, after flashing OOS 10.0.1 again to go back to stock kernel and after flashed xXx_NoLimits_module, and while REBOOTING, I got into Qualcomm Crash dump screen and somehow I managed to boot back to system.
After trying couple times to enter twrp(VolDown+Power Button), with VolUp+Power Button I got into system again
id get that when is select wrong slot in twrp but when i change it back to slotA it reboots as normal i never get it at random though came up when selecting slot b to active.
refedit said:
Yesterday, after flashing OOS 10.0.1 again to go back to stock kernel and after flashed xXx_NoLimits_module, and while REBOOTING, I got into Qualcomm Crash dump screen and somehow I managed to boot back to system.
After trying couple times to enter twrp(VolDown+Power Button), with VolUp+Power Button I got into system again
Click to expand...
Click to collapse
Use msm tool to load everything to stock and then try update again. Using msm tool fixed my issue
ludester said:
Use msm tool to load everything to stock and then try update again. Using msm tool fixed my issue
Click to expand...
Click to collapse
So far I'm good. It didn´t boot to QUalcomm screen again.
Although, to prevent future issue, I'm backing up everything so I use the msmtool. Although, I don't if the issue isn't related from Upgrading from Android Q to A10. So I rather'd use the msm tool with Android 10. As far as I know, there's no msm tool for BA version
Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan
Check this:
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode
Mohamedkam000 said:
Check this:
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode
Click to expand...
Click to collapse
As I have said earlier it is hardware issue not software so MSM tool has low chance of fixing it. It might succeed and boot but crashdump will come back again.
drsaog said:
Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan
Click to expand...
Click to collapse
Same here..
Now i'm scared of using OOS
My phone was hard bricked after my battery ran out. It only shows a red light when charging.
Luckily the 9008 mode works and through the testpoints i'm able to connecti via edl.
Unfortunately MIFLASH doesn't work since you need an authorized account. However, i'm trying to use QFIL to flash on a fastboot rom. It doesn't seem to work.
Would anyone be able to help me with:
1. a guide on how to flash through QFIL (and which rom i need to use)
2. a No Auth Firehose file for this phone so i can use MIFLASH without authorization.
Thanks!
ok. Some progress now. I'm able to access fastboot. However, the phone is not detected on the computer. Red light while charging is also not present anymore, although i doubt that this is the flexcable issue.
Does anyone know how i can reflash with a locked bootloader in Fastboot?
pimf said:
ok. Some progress now. I'm able to access fastboot. However, the phone is not detected on the computer. Red light while charging is also not present anymore, although i doubt that this is the flexcable issue.
Does anyone know how i can reflash with a locked bootloader in Fastboot?
Click to expand...
Click to collapse
With Mi Assistant but if the phone is not detected it is mission impossible.
some more progress.
Phone is turning on now, but is stuck at the miui logo. I have no idea why this phone is coming back to live so randomly. Still not able to see the phone in windows. (nothing in device manager)
I also don't understand what is going wrong. I didn't reflash anything. I only replaced the flex cable and then my phone only lid up with the red charging light (staying red).
Now the red light is not on anymore. But i'm sure there is connection since i was able to get into 9008 mode with the computer connecting to the phone in EDL.
pimf said:
some more progress.
Phone is turning on now, but is stuck at the miui logo. I have no idea why this phone is coming back to live so randomly. Still not able to see the phone in windows. (nothing in device manager)
Click to expand...
Click to collapse
Try wipe data with recovery.
NOSS8 said:
Try wipe data with recovery.
Click to expand...
Click to collapse
Ill try again, however volume up + power button does not work (and I can therefore not enter recovery mode).
I'll keep trying.
pimf said:
Ill try again, however volume up + power button does not work (and I can therefore not enter recovery mode).
I'll keep trying.
Click to expand...
Click to collapse
Wiped the data, and the first boot still is stuck at the miui logo. Waited for a good 25 minutes. Mi assistant in the recovery menu doesn't let me connect with the computer either. I'm really curious why that is.
pimf said:
Wiped the data, and the first boot still is stuck at the miui logo. Waited for a good 25 minutes. Mi assistant in the recovery menu doesn't let me connect with the computer either. I'm really curious why that is.
Click to expand...
Click to collapse
Change the flexcable and try with Miflash
NOSS8 said:
Change the flexcable and try with Miflash
Click to expand...
Click to collapse
already did that. No go. I'm a bit frustrated as to why the pc doesn't see the phone.
pimf said:
already did that. No go. I'm a bit frustrated as to why the pc doesn't see the phone.
Click to expand...
Click to collapse
If the problem occurred after replacing a component (battery, cable, etc.), surely something is incorrectly mounted or defective.
I have a spare charging pcb. can try that. But i'm not sure that's going to help since i can see the phone in 9008 mode. Just cannot flash the phone due to the mi account restrictions.
tried the new pcb. Same problems. I'm wondering. How do i activate wlan when in recovery mode. It shows that you can download a software package over wlan in recovery mode but everytime i click wlan it activates and immediately deactivates again.
pimf said:
tried the new pcb. Same problems. I'm wondering. How do i activate wlan when in recovery mode. It shows that you can download a software package over wlan in recovery mode but everytime i click wlan it activates and immediately deactivates again.
Click to expand...
Click to collapse
Btw:
Have you changed the battery?
Was the phone detected before?
What is the rom installed?
And now the phone is bootlooping. There is more and more life coming in this phone. But i really cannot understand why this phone is not properly working. There is nothing i'm changing here so the fact it's all of a sudden bootlooping doesn't make much sense to me.
NOSS8 said:
Btw:
Have you changed the battery?
Was the phone detected before?
What is the rom installed?
Click to expand...
Click to collapse
1. Have not changed the battery. Battery seems to be fine.
2. Yes Phone was detected before. I used the last bit of power to get most of my pictures off the phone. Also, now it's still detected under 9008 mode.
3. Rom installed was the stock rom (poco f2 pro global) that came with the phone.
battery is at 98%. Phone just turned on for the first time. It's asking me to login to my mi account to unlock my phone. However, it cannot verify the password because there is no network connection. Wifi is not working, and there is no way of setting the sim settings until my phone is unlocked.
So, now i need to understand why the wifi is not working.
This is seriously the strangest thing i've encountered with phones. just doesn't make sense at all
ok. Just got my phone unlocked. However, phone keeps powering off during first setup. Phone is still highly unstable and the wifi doesn't seem to work well. The phone is at the moment useless. It's too unstable to use as a daily driver. Hopefully this will get better. Does anyone know why the wifi doesn't seem to work. seems to be a problem in all modes (rescue, and normal phone
edit: phone just turned off again while setting the pincode.
edit2: just updated with a new version of miui, wifi is still a problem, and phone turned off during updating all the system apps. Really not sure why this phone is so unstable now.
Ok, still an unstable phone. Seems like WIFI Bluetooth and usb connection don't work.
Does anyone know if it might be a loose cable that i need to reseat? Does it sound like a certain chip that needs to be replaced?
nobody has a clue?
pimf said:
nobody has a clue?
Click to expand...
Click to collapse
From the symptoms described above, it seems that your F2 pro has soldering problems with the SoC (system on chip) which is basically reballing the cpu
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
travy said:
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
Click to expand...
Click to collapse
Same boat as you two. Used "fastboot set_active b" after flashing stock firmware and ignored the bootloader warning. Now im stuck hardbricked with no success blankflashing. Including info for EDL Mode and log from one of my blankflash attempts as well as the correct firehose programmer for this device.
ezril said:
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
Click to expand...
Click to collapse
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Linux_SF said:
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Click to expand...
Click to collapse
I have had no luck whatsoever. Originally I thought I was successful using a blankflash although it was not. I've pretty much given up on that device for now although if you have anything that may help, I have no problem being the guinea pig, lol.
Keith