"Warning" Total Brick After Flashing Android 12 Beta - OnePlus 8 Pro Questions & Answers

My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad

Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.

A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.

xtcislove said:
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
Click to expand...
Click to collapse
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.

nkhater said:
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
Click to expand...
Click to collapse
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?

daviddosa said:
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
Click to expand...
Click to collapse
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
xtcislove said:
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
Click to expand...
Click to collapse
Yes fail-safe a/b partition, and Yes I have tried several cables

nkhater said:
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
Yes fail-safe a/b partition, and Yes I have tried several cables
Click to expand...
Click to collapse
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.

daviddosa said:
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
Click to expand...
Click to collapse
did that too, leaving it overnight did not work either.
I hope this will be an eye-opener for other flashaholics, things are different in A12

my phone has the same problem, have you fixed it, i need help

[email protected] said:
my phone has the same problem, have you fixed it, i need help
Click to expand...
Click to collapse
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad

nkhater said:
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
Click to expand...
Click to collapse
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com

ProtoDeVNan0 said:
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG

Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.

Mar 3rd I posted for the 1st time about it.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com

djcrystals said:
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Click to expand...
Click to collapse
That's so fed'ed up man, I am in the same boat as you, total loss, I am done with OnePlus, they can enjoy Oppo and ColorOS, A12 sucks and it's not for me.

Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.

Andre Cancian said:
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Click to expand...
Click to collapse
how much did you pay for the motherboard?

nkhater said:
how much did you pay for the motherboard?
Click to expand...
Click to collapse
I paid something like 250 USD for a working 8 Pro with a broken screen. Motherboards on their own were available for a similar price on sites like aliexpress, but the wait was too much.

nkhater said:
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Click to expand...
Click to collapse
hello, did you solve your problem? Or did you change your motherboard? I'm having the same problem right now and I don't know what to do

you need to replace the motherboard, the phone is completely dead, it's gone

Related

[RE-OPENED] Possibly Bricked My Phone. AGAIN.

Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Car Transport in mumbai
Car Transport In Mumbai[/URL]
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:
..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
You'd probably be better off seeking support in the mod thread.
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.
..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.

Can anyone share a dump folder of .ops file? (python)

*EDIT 05-24
I had a problem where I would get stuck even after using MSMDOWNLOADTOOL completely. With the help of great minds,
#fullofhell #Dark Nightmare #Scott and frankly a god #Eliminater74 I could fix the phone completely. I am heading for modem work, which put me into this situation.
As of this point, I cannot find any misbehavior but I am quite new to this, so I can be deadly wrong. (Well but then, sensors are fine, calls , texts, data, wifi is working just fine. I don't know what else to check!)
I know as a fact that what happened to me is not really that rare (although it is quite rare, it happened before as well.)
So I was about to share how I fixed it but decided not because what I did was so out of experimental and I frankly have no idea if the same would work for others.
Tbh, if you are in the same position as I am, go ahead and contact the Oneplus service team. I did what I did only because I had to, I am Korean, and couldn't get it fixed.
If anyone, comes to this point and has absolutely no way to get it fixed, I will be glad to help,
(only if that person agrees that there is more chance to totally destroy it then fixing it XD.)
Again, Thank you so much Scott, dark nightmare. What you guys shared with me saved a bunch of time and you guys are what the forum truely needs!
P.S, Still couldn't find the moded MSMdownload tool. What can you recall what functions it had? Maybe enabled engineer mode?
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Pain-N-Panic said:
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Click to expand...
Click to collapse
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Somehowko said:
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Click to expand...
Click to collapse
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Pain-N-Panic said:
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Click to expand...
Click to collapse
As the bootloader is locked and I cannot boot, I am can't put enable oem-unlock on the data. Which means, yes I cannot unlock the bootloader as long as oneplus 6t doesn't have a loophole like oneplus 3T. I am pretty sure that was fixed though.
Well, I don't know if it's msm tool really. If I just started with that I would have been fine (at least I believe so). Yes I didn't wanted to lock the boot loader, which is why I used fastboot flash tool. But then, that's why I ended up here. So, if you end up in a situation where you might, might need msm tool or flash tool, always go with the msm tool !
For msm, I am quite certain it doesn't flash all partitions. I think there is some partition checkup somewhere. Here is why I think so
1) Completely formatted OS cannot be on a boot loop unless it's caused by hardware issue.
2) All partitions except vendor, system goes way too fast. It ends within 200 seconds for me. I would assume that kinda makes sense as it really is the problem of usb-pc hardware power but installing the image should take longer I think (but then I truly have no idea)
My conclusion is that the tool checks partition size before flashing, and does not touch / replace every file. I am probably wrong since it is
EDI tool after all, but I simply cannot believe msm tool cannot fix something that has nothing to do with the hardware.
I mean, imagine we can brake our newly formatted PC OS without any single components corrupted! (Is it even possible?)
I don't know man....with the bootloader locked you're not able to fastboot flash ANYTHING?
Somehowko said:
For msm, I am quite certain it doesn't flash all partitions.
Click to expand...
Click to collapse
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Well, tbh, we know as a matter of fact it is not a complete flashing. I mean it clearly says flashing to partition _a only unlike previous versions of msm tools (ah, good days.) What I am curious of is if there is anything we can do about skipping partitions. I am suspecting using qfil would, through unpacking ops files. Although it seems like a long shot.
Btw, thank you for your interest!
Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Siren siren... Watch out the xda police gunna blow down and remove my comment.. oh nooooo aghastt....
Btw u cannot use berklers script without an AES recovery key. There aren't any around as far as I know for fajita.
Easiest thing is if OnePlus bought device, get an exchange.. play dumb.. oops I dunno, your Android Q crap broke it..
Or if tmo bought, add insurance if u don't have it, play dumb. Get a new one. I did for a scratched screen..but made it about the modem not working, bc I erased it...
These corporations owe us nothing.
Get a new phone man
fullofhell said:
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Get a new phone man
Click to expand...
Click to collapse
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Somehowko said:
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Click to expand...
Click to collapse
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I believe, just look for the modded tool that skips the model check, did you do a full system backup before tinkering? If so you can dd files back into place if msm doesn't overwrite them the way its supposed to, I've done some crazy things to the 6t, a bit surprised recovery didn't fix it for you...
And yeah FoH already pointed out that decrypt tool is useless to us.
Dark Nightmare said:
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I .
Click to expand...
Click to collapse
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Somehowko said:
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Click to expand...
Click to collapse
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Dark Nightmare said:
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Click to expand...
Click to collapse
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Somehowko said:
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Click to expand...
Click to collapse
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Dark Nightmare said:
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Click to expand...
Click to collapse
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
That's correct and if you're on windows 10 it may be a system update messing with the drivers, its dumb, but it actually affects the simplest of things.
Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
As crazy as it sounds three reboots and four different ports did the trcik!
And sincerely thank you! Although I couldn't find the modded msmtool you told me I was able to boot into the os finally.

Essential Phone hardbricked after trying to sideload android 10

Hello everyone.
First of all i was on the beta program for android 10 until like Q4 but since i was't able to play DFFOO i decided to downgrade the OS back to the last official build, and that was the android 9 june/july build.
I followed everything on the essential website in order to downgrade and i got it right, sort of. Everything was working fine except for the fact that the phone just wouldn't update at all. it'd just throw me an error, not big deal i though, until android 10 came out and since i wasn't getting it on my phone on it's own i decided to sideload it and here we are
I also folllowed everyhting on the Essential's website except for the fact of using the last Pie build i thought it was not big deal (idk if that mattered) so everything went fine until the installation reached 94% and then it said: Installation complete (i thought it was weird but not much else) next thing i do is select reboot now and boom.
All i get now is the sound of windows if i connect it to my computer and the "Qualcomm HS-USB QDloader 9008" under the ports section in device manager, no ammount of holding and pressing buttons will make it come back to life, so i come here for help, worst case scenario i'll have to buy a new one (they're pretty cheap second hand)
I'm sorry to say this to you, but you are out of luck... The QDL mode is because of 2 reasons:
-Joined D- and GND on a stripped cable
-Bootloader corrupted.
The most common thing is the Bootloader was corrupted because of 2 files: hyp.mbn and rpm.mbn. Either was downloaded bad or was flashed but have issues on those 2...
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
In a post I made on Reddit I explain something about this issue, and what causes it. But without the Programmer and the Firehose, you can't recover the device.
Why would Andy Rubin not put out the Firehose when Essential is supposed to be a developer friendly phone!?!? Makes no sense.
IngJulian_RVLX said:
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
.
Click to expand...
Click to collapse
Do you think there is a possibility they will release them in the future eg when new model comes out or when support for PH-1 ends? Or are other manufacturers always leaked & not "official" leak? Suppose most leaks for other phones are from service centres, vice kinda answers my own question.
IngJulian_RVLX said:
I'm sorry to say this to you, but you are out of luck... The QDL mode is because of 2 reasons:
-Joined D- and GND on a stripped cable
-Bootloader corrupted.
The most common thing is the Bootloader was corrupted because of 2 files: hyp.mbn and rpm.mbn. Either was downloaded bad or was flashed but have issues on those 2...
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
In a post I made on Reddit I explain something about this issue, and what causes it. But without the Programmer and the Firehose, you can't recover the device.
Click to expand...
Click to collapse
Thanks for the quick reply, oh well, at least i didn't buy it at its 700 dollars lauch price.
i'd like to read that post though, mind sharing the link?
Noct1070 said:
Thanks for the quick reply, oh well, at least i didn't buy it at its 700 dollars lauch price.
i'd like to read that post though, mind sharing the link?
Click to expand...
Click to collapse
https://www.reddit.com/r/essential/comments/cku745/my_ph1_bricked_by_may_ota_qdledl_9008_and_its/
I did the same thing, and ended up in the same situation, so this is definitely a reproducible problem. Contacting Essential support in hopes that they're willing to fix... but from what I'm reading around the web it's not likely. ?
Just adding my two cents. I had this exact same issue and Essential reached out to me. Told me I could ship my phone to them and they would fix it. Low and behold, they did. At the cost of only shipping, we'll worth the wait to get the phone back.
I guess depending on warranty age and registering, retail vs eBay used purchase, etc

6T keeps 'crashing'

So I just picked up a clean used International 6T. Was going through the root and update (I did the Android 10 update through Oxygen Updater) process and all that, things were going great, then out of nowhere they weren't and I had a complete black screen. I've literally been up all night trying to fix this thing, then again out of nowhere it actually boots, and I was able to use the MSM tool to restore it to that earlier version, then proceeded to get back up and running again.
Thought, phew, dodged a bullet. Nope, after getting rooted and TWRP installed, transferring a bunch of files over from my old SD card and restoring apps through Titanium (again, everything was going great again), and yet now all of a sudden I'm back where it all started earlier, stuck at the 'The boot loader is unlocked and ....' boot screen, it just hangs there, I can reboot into recovery just fine, but no operating system.
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable.
Can anyone help or shed some light on why this has happened again? I didn't update to 10, left it on the last stable Pie (begrudgingly), didn't flash any custom rom or anything, it was restoring most of the titanium apps just fine (some just hang there, not sure what that's about) and now I can't reboot into the os. To say the least I'm beyond pissed and annoyed at how much time I've lost on this thing.
Please please please help if you can, I'm not a newb to rooting (already rooted this one twice) but I don't know what to do at this point.
Thank you in advance, let me know what/if any info is needed.
Edit: I think I know/understand partially that magisk is to blame for this and reinstalling it fixes it, though I just did that through TWRP and it's still stuck on the boot screen.
Edit: Yup, right back where I was, device now shows as HS-USB QDloader..... in device manager. What gives? I have to use the MSM tool again? Why? Why is this happening...I've never had this much trouble with a phone
Try a clean install. Don't root and don't restore the titanium apps. Install them fresh. If your problem persists then it may just be hardware. But something you are restoring may be causing the crash due to the way it is trying to restore the app data.
I had similar problems. For me it was my self-created magisk module that ran without problems under Android 9. As it seems, there are also problems with modules from the magisk repo.Could be the case with you.
Clean install of the apps, after doing another MSM restore? And trust me, I won't be installing ANY other magisk files other than just the magisk.
Is there any way to save all the work I just did though without having to start over again via MSM? I'm guessing not....sigh
Grrrr...ok before the MSM tool worked, the phone was just unresponsive. It's back at that stage where the MSM tool times out and doesn't do a darn thing to save the phone.
I swear this thing is all over the place, now I'm in the bootloader, yay. I guess I'll try a wipe in TWRP and start over.
One thing I forgot to ask, is magisk the ONLY option available for root?
The question would be, how did you root.
TWRP is not working when you don't follow the instructions which involves OldKeysFlasher.zip.
Otherwise you have to flash Magisk with a patched boot image, be sure uyou have one for OOS 10 Stable.
The correct comands are here: https://forum.xda-developers.com/showpost.php?p=80638253&postcount=2853
jgro1976 said:
(...)
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable. (...)
Click to expand...
Click to collapse
I hope that anger is directed towards yourself because you can't hold the device or its manufacturer responsible when you get into the flashing game.
If you had done some reading, you'd know that TWRP doesn't play well with Android 10 and upgrading from 9 takes a very specific procedure. There's a dedicated thread for it even. Happy searching. You may also want to take a peek at my posting history for some pointers.
One more thing, are you absolutely sure it's an international device and not a converted T-Mobile version? Because that can cause a major amount of troubles.
Wrapped with delicious Fajita [emoji896]
I'm well aware it's my own doing, part of the frustration is having too many sources of information all claiming they fix a 'thing'. There's the "fix it with fastboot" camp who doesn't like MSM, and there's the MSM camp that helped me the first time. Phone is currently dead/black screen, going to try MSM again, and will check out the info you provided.
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
jgro1976 said:
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
Click to expand...
Click to collapse
Just remember that dual SIM trays are easy to get and if it's been converted from TMO to international version there will be no indicators till n you try to flash A10. Best bet would be to treat it as a converted TMO, if it is the info in recovering and flashing a TMO device will work and if it's truly an international version it will work too. Best of both worlds.
I'm 99% certain, by the label on the box, etc. Regardless, I'm to the point now that I can't even get it to boot to TWRP after 'fastboot flash boot twrp.img', it just does nothing and when I try to boot to recovery it bounces right back to bootloader. I've been trying all afternoon to fix it with no luck.
Was android 8/oreo good on these phones? That was my sweet spot and I'm just gonna downgrade if possible, there's too many things I don't like about 9 and 10.

How to fix OnePlus 8 pro won't turn on

Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You all are flashing wrong xbl img. Wrong ram versions
what do u mean xbl img? I remember I have read about the ram versions but I think it wasn't the 8 pro...
duxler said:
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Click to expand...
Click to collapse
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
Im am sorry for you guys but you hard bricked your phones for real.
The only thing you can do now is to replace the motherboard.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Unfortunately that's the case...
jimger said:
Unfortunately that's the case...
Click to expand...
Click to collapse
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
xtcislove said:
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
Click to expand...
Click to collapse
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
jimger said:
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
Click to expand...
Click to collapse
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
xtcislove said:
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
Click to expand...
Click to collapse
Yeah tbh I have every photo etc backed up. Also run my daily swiftkey backup before updating. But the big big bummer now is that I have no way to restore banking apps to tablet atm... Anyway let's hope at least they replace it...
As I understand it, the phone can be thrown away
how will Qualcomm ® Package Manager help if the computer does not see the device.
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Tbh at least I hope they replace it... For now found an Mi A1 from a friend...
I know this topic has been brought up before. But there is not always a half and full explanation.I have Oneplus 8 pro too. I can't enter recovery mode. Boots into fastboot. I've printed a wide variety of msm tools files from edl. It writes smoothly, but when opening the boot screen, it says "your device is corrupted it cannot be trusted and may not work properly" and does not open. What could be the reason? Android 10 11 msm roms, Coloros Hydrogenos all but all tried. There is no recovery. I can't open the oem lock, I can't do anything.
xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
AkayamiShurui said:
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
Click to expand...
Click to collapse
Im sorry my friend i dont understand your post.
xtcislove said:
Im sorry my friend i dont understand your post.
Click to expand...
Click to collapse
If your got discord I can show you
duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Hold up. I'm looking for a dead OP8 Pro. I have started a conversation with you; check notification.

Categories

Resources