Hello, a few days ago I wanted to decide on the new version of ColorOS 12, after I installed it the phone did not start it just stuck to the Logo, I tried some methods to return the previous version but I can not because I have a bootloader locked, please help me how to fix it.
Try msm tool, that's what worked for me
Try msm tools method.
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com
Related
I have purchased a Chinese variant (KB2000, late December 2020) of the OnePlus 8T which out of the box is running HydrogenOS 11.0.5.6KB05. I downloaded the Global ROM (OxygenOS 11.0.5.6.KB05AA) from OnePlus' website to do the local update, but cannot install as it is saying it is a previous version.
I have been scouring the internet as trying to figure out options, but it seems like I have 2 options:
1. Wait until the Global ROM version is higher than the current HydrogenOS version (11.0.5.6KB05) and do a local update. Note that the unit wants to update, but not letting it.
2. Use the BootlLoader installation method to install a fresh OxygenOS. I found what seems to be a great guides at https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/ or https://www.droidwin.com/restore-oneplus-8-stock-oxygenos-fastboot-commands/.
Note that I don't want to Root or install any custom mods or ROM, but just want to use the latest Global ROM on this phone.
Any insight will be greatly appreciated as I have been researching, but not finding a definitive answer. Thanks in advance!
If you are fine with wiping your phone you should be able to use the msm tools from the unbrick tools thread to convert
Qnorsten said:
If you are fine with wiping your phone you should be able to use the msm tools from the unbrick tools thread to convert
Click to expand...
Click to collapse
Ok thanks for the feedback and will search for the thread. I'm fine with wiping it as it is a new phone. I'll update how it goes.
jvg2001 said:
Ok thanks for the feedback and will search for the thread. I'm fine with wiping it as it is a new phone. I'll update how it goes.
Click to expand...
Click to collapse
I assume you found the thread by now. But this is the thread if anyone else is looking for it. Was on my phone before so couldn't link it easily
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
Click to expand...
Click to collapse
I had to do the same thing. I am using a LE2113 and managed to brick my phone in a way where only EDL could save it. I came from the latest OOS (colorOS) firmware and tried to flash LineageOS when everything went south. I tried to use the Oneplus 9 EU MSM tool but this one did not work for me. Since there is no official EU MSM for the LE2113 the only way I could repair it was by using the EU OnePlus 9 pro msm firmware. It only worked with the "use lite firehose" option for me. After that was done I unlocked the bootloader once again and flashed OOS (Android 11) for OnePlus 9 again. This was the way I got the original firmware back on my device although I do not think it would've been possible to relock the bootloader at this point.
Straight after that I once again flashed lineage and everything is working fine now. Certainly a shady approach but it is the end result that counts I'd say.
Nullifii said:
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
Click to expand...
Click to collapse
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
jab5555 said:
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
Click to expand...
Click to collapse
That's the thing though. I had the LE2115 MSM tool but it was in Chinese for some reason I have a LE2115 phone as well but it said that the files didn't match up. Maybe they uploaded the wrong variant to the website? None of the tools that I had downloaded were in English, all in Chinese.
chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for y
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
This what I used m8, got it off OP when they tried to remote flash my phone , couldn't do it on AMD Ryzen, done on my old pc, driver issue lol, good luck m8
Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .
funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.
So I have the LE2110 version, and been flashing any rom i want and any recovery. Obviously You guys see me on this forum all day everyday.
Well i got my girl a OnePlus 9 5G, model LE2111, now I got the bootloader unlocked and everything. We bought it on eBay. Whoever had it updated it to Android 12, not happy about it. It wont let me fastboot to any recovery, i get the crashdump everytime.
Anyone got any suggestions. Im trying to just downgrade it to 11.2.10.10 pretty much.
illusiveairforce said:
So I have the LE2110 version, and been flashing any rom i want and any recovery. Obviously You guys see me on this forum all day everyday.
Well i got my girl a OnePlus 9 5G, model LE2111, now I got the bootloader unlocked and everything. We bought it on eBay. Whoever had it updated it to Android 12, not happy about it. It wont let me fastboot to any recovery, i get the crashdump everytime.
Anyone got any suggestions. Im trying to just downgrade it to 11.2.10.10 pretty much.
Click to expand...
Click to collapse
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Okay. Yeah that's what I'm doing. I forgot that Android 12 don't like TWRP right?
TWRP not compatible with A12.
does the device still boot normal to A12?
if it does, the best path would be to downgrade from A12 to A11.
there's a thread guide on how to that here.
how do you unlock fastboot? XD i do it with my t mobile oneplus 8 but dont find info for my LE2111.
PS: Never mind.. It was an standar unlock with "fastboot oem unlock" haha
Hi,
While trying to root the OnePlus Nord CE 2 5G (European Edition), I managed to mess up my phone completely by flashing wrong files to the phone using fastboot.
I recieved the A13 update, and I think I flashed the wrong boot.img and some other mismatching files using fastboot. I know, it's the first time I attempted this and probably a beginners mistake. Shame on me.
The phone is stuck at the bootloader (I think), because it's not going past the boot logo from OnePlus.
I tried searching online and the OnePlus support pages for the original OxygenOS image to perform a full recovery, but I have been unsuccessful.
Can anyone provide this image or provide some guidance how I would be able to make it workable again?
Thank you in advance!
Sorry to hear about your phone. From my knowledge, the A13 firmware hasn't been shared yet. You could try your luck contacting OnePlus support. Otherwise you'll just have to wait until someone shares it, but that could take quite a while.
@mr_munch, thank you for your reply. I'll reach out to OnePlus support.
GeneratedUnique said:
@mr_munch, thank you for your reply. I'll reach out to OnePlus support.
Click to expand...
Click to collapse
Have you have any luck? Looks like they released a rollback package that includes the A.13 boot image as part of their Android 12 beta program. Maybe that could help you out if you still need it: https://community.oneplus.com/thread?id=1110424001643544581
Hi @mr_munch,
Unfortunately, so far no luck.
I've reached out to OnePlus support, they asked me to go to one of their service centres, called The Phone Lab in the Netherlands. They tried to flash the phone with the original ROM. It's now giving the error message "the serial is not match" while booting up. According to them this is due to a hard brick and I had to file a case with OnePlus support, but haven't heard anything yet.
I'll keep you posted.
Thank you for all the help!
Hi,
OnePlus repaired the phone, by replacing the motherboard/soc, all under the warranty. Luckily, I got a working phone back.
Thank you all for your support.
GeneratedUnique said:
Hi,
While trying to root the OnePlus Nord CE 2 5G (European Edition), I managed to mess up my phone completely by flashing wrong files to the phone using fastboot.
I recieved the A13 update, and I think I flashed the wrong boot.img and some other mismatching files using fastboot. I know, it's the first time I attempted this and probably a beginners mistake. Shame on me.
The phone is stuck at the bootloader (I think), because it's not going past the boot logo from OnePlus.
I tried searching online and the OnePlus support pages for the original OxygenOS image to perform a full recovery, but I have been unsuccessful.
Can anyone provide this image or provide some guidance how I would be able to make it workable again?
Thank you in advance!
Click to expand...
Click to collapse
Hi,
Same issue here with OnePlus Nord CE 2 5G (European Edition), I'm stuck on the boot logo (the three dots turning around) after flashing boot.img.
A11 update,
I tried to flash stock boot.img but no luck,
I tried a factory reset via TWRP, I tried to flash via fastboot stock firmare following this guide: https://www.getdroidtips.com/oneplu...nstall-Stock-Firmware-on-OnePlus-Nord-CE-2-5G
I don't know what to do to get it working. Do you have any advice?
...sorry, I posted to the wrong device board