Related
Hello
As the titel says..
Its been a few years since ive done anything like this, so dont really know what i need to do now..
Ive flashes newest twrp-3.2.3-0-20180822 and tryed to install OnePlus5Oxygen_23_OTA_052_all_1910082005_adf7221fba833a0.zip but witout any luck
Log in twrp says:
Installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_052_all_1910082005_adf7221fba833a0.zip'
Checking for digest files
Skipping digest check: no digest file found
vendor partition is not existed, exit ota!!
Updater process ended with Error: 7
Error installing zip file
I have no idea if its even possible to do this if i need other updates first ect.
Kinda rookies now haha..
Iv'e searched forum for help dunno if ive searched wrong or not, but couldnt find any help.
You have to install version 5.1.4 based on Oreo 8.1.0 and boot up the phone to enable vendor partition. Then you will be able to flash the latest Pie OS. If you want a faster way, you can use the 9.0.9 EDL package, but you will lose all data
Well i had a friend that said i could just install 9.0.9 firmware, well now ive ended up witj a phone which i cant enter.. Can still open fastmode and twrp but i cant add files on phone.. Any ideas on how to fix this mess?
mummilana said:
Well i had a friend that said i could just install 9.0.9 firmware, well now ive ended up witj a phone which i cant enter.. Can still open fastmode and twrp but i cant add files on phone.. Any ideas on how to fix this mess?
Click to expand...
Click to collapse
Use this EDL guide https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
PierreVicquery02 said:
Use this EDL guide https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
thanks i will try
PierreVicquery02 said:
You have to install version 5.1.4 based on Oreo 8.1.0 and boot up the phone to enable vendor partition. Then you will be able to flash the latest Pie OS. If you want a faster way, you can use the 9.0.9 EDL package, but you will lose all data
Click to expand...
Click to collapse
So they changed the partition layout with Oreo? I am asking because I currently have the exact same problem.
Currently stucking on 7.1.1 with the same errormessage. I will try to upgrade to Oreo first and then move over to Pie. Thanks.
GoodSoul said:
So they changed the partition layout with Oreo? I am asking because I currently have the exact same problem.
Currently stucking on 7.1.1 with the same errormessage. I will try to upgrade to Oreo first and then move over to Pie. Thanks.
Click to expand...
Click to collapse
Yes, with the version 5.1.5 Project Treble was adopted and it requires a new vendor partition. That partition was created with 5.1.4, so if you are on a version lower than 5.1.4 you will need to install that version, boot once (the repartitioning is made during Android boot, not during the install) and then you will be able to upgrade to latest Pie version.
If you want to upgrade in one step, you can use EDL tool, but you lose all your data. Anyway, I advice you to do so because a format is a good operation when upgrading the Android version
PierreVicquery02 said:
[...]That partition was created with 5.1.4, so if you are on a version lower than 5.1.4 you will need to install that version, boot once (the repartitioning is made during Android boot, not during the install) and then you will be able to upgrade to latest Pie version.[...]
Click to expand...
Click to collapse
I assume I can then also move directly to 9.0.xx, right? Sorry, I forgot that the OP5 got Android 10!
GoodSoul said:
I assume I can then also move directly to 9.0.xx, right? Sorry, I forgot that the OP5 got Android 10!
Click to expand...
Click to collapse
You can install the latest ROM ONLY if you are on a version that is 5.1.4 or newer. If you are on an older version, you have to first upgrade to 5.1.4 and then the newer version (Android 10 will be out in the next months)
Feedback: Works great. Moved to that version, rebooted once, upgraded directly to latest OOS (9.xx whatev) with success. Thanks for all your support & comments!
GoodSoul said:
Feedback: Works great. Moved to that version, rebooted once, upgraded directly to latest OOS (9.xx whatev) with success. Thanks for all your support & comments!
Click to expand...
Click to collapse
You're welcome!
Hi,
quick files that many of us waiting for
OnePlus 8T, 11.0.1.2 KB05BA KB2003
Newest (20.10.2020) OTA:
https://drive.google.com/file/d/1uKV_j8yIQLPeIRJkf1KIUlJcIaH8BppR/view?usp=sharing
boot.img (stock)
https://drive.google.com/file/d/12VopoB984YmJHUJuqMBA4jyID1Sp_sPQ/view?usp=sharing
boot.img (patched, checked, working)
https://drive.google.com/file/d/1V4esvmJCBkwskq2shfWcylPL53h4dd_2/view?usp=sharing
=======================================
You like it?
paypal.me/widmak
=======================================
Thanks!
Thanks. But where's the guide or howto, that the title says ?
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Any idea to flash the EU rom from India?
felata said:
Any idea to flash the EU rom from India?
Click to expand...
Click to collapse
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
The system says that it won't allow downgrade
Which magisk did you use please?
Alvincyq said:
The system says that it won't allow downgrade
Click to expand...
Click to collapse
If you updated to the Indian/Global 11.0.1.2 before doing this, you only have 2 options:
1. Wait for the next OOS update, but when the Indian/Global update comes, don't update.
Instead, wait for the full update zip of the EU to be available, and then follow the steps in the previous comment.
2. Unlock bootloader, flash the full OTA zip of any variant via fastboot, and relock the bootloader.
elliottweaver said:
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Click to expand...
Click to collapse
Your file did not work for me but i modified the stock file from the first post myself and that worked. i guess there is something coded into the file by magisk that is depended on the phone.
theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
I'm on Kb2005 and I'm only able to get an incremental update. Can I pull the bin file from that update
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
MNoisy said:
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
Click to expand...
Click to collapse
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
northmendo said:
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
Click to expand...
Click to collapse
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
MNoisy said:
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
Click to expand...
Click to collapse
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
northmendo said:
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
Click to expand...
Click to collapse
I am familiar with how it works but with brands like HTC and Samsung, if we use a boot.img from a different variation, it will not work or even brick it. Thanks for the heads up! It sounds like there is more room for error for testing with OnePlus and modifying the system.
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
epr said:
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
Click to expand...
Click to collapse
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
MNoisy said:
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
Click to expand...
Click to collapse
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
epr said:
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Click to expand...
Click to collapse
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
MNoisy said:
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
Click to expand...
Click to collapse
Don't know for KB2005, mine is KB2003.
I used stock boot.img from OP and patched it myself, all already patched files didn't work.
I have only *SUCCESSFULLY* tried this on my KB2003 Variant. It will work for all other variants as well, it's just that I haven't tested it (I don't have all variants on hand!)
If you're having some issues rooting your 8T, I'm here to guide you on how to root correctly. I have tried many ways but none have worked. This is the only way I know that actually works. I want to get some thanks out of the way first.
topjohnwu for his amazing Magisk creation!
DroidFreak32 for the boot images required for this method
For this method, we're gonna skip all of the Payload Dumper part of DroidFreaks' Guide (unless your variant of the 8T doesn't have a public boot image). All you need is your phone on hand and your STOCK boot image, which for the purposes of this guide, you can grab from DroidFreaks' guide, or from below (all thanks to him)
KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
https://drive.google.com/file/d/1Ct7IJWWXJlIZX9ekIrTKLC9G6KZLD2eq/view
KB2003 - EU Variant - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
https://www.androidfilehost.com/?fid=10763459528675568456
KB2005 - US Variant
https://androidfilehost.com/?fid=10763459528675569233
You have to have your bootloader unlocked at this point, but this isn't a guide for that, just Google it.
Next, you'll wanna download the latest magisk canary apk. https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk . After this, make sure you have your specific boot image on your phone. Open Magisk Manager, and go to install, beside "magisk". Next, choose "select and patch a file" and choose your specific boot image to patch. For me, it was the KB2003 one. Once it spits out the file, go ahead and move it back over to your PC.
Reboot into the bootloader and use fastboot to BOOT the patched image that you just moved over to your PC.
Code:
fastboot boot magisk_patched.img[/INDENT]
Once you're booted, head over to the Magisk app again. You want to go back to the install page "mentioned earlier" and instead of clicking the patch button, you want to click the new DIRECT INSTALL button, this will "save" magisk and fully install it. After it's done, go ahead and reboot, and you should be rooted!​
Let me know how it goes for you guys down below!​
I am on KB2000 running Oxygen OS 11.0.1.2.KB05DA. Any advise on how to get the stock boot image?
deepuvijay said:
I am on KB2000 running Oxygen OS 11.0.1.2.KB05DA. Any advise on how to get the stock boot image?
Click to expand...
Click to collapse
KB05DA is the Indian variant OxygenOS, so your stock boot image should be the one below:
KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
https://drive.google.com/file/d/1Ct7IJWWXJlIZX9ekIrTKLC9G6KZLD2eq/view
Thanks @zellleonhart, @fxz
Worked just fine. I am now rooted on KB2000 running Oxygen OS 11.0.1.2.KB05DA.
Worked for me. Thank you very much!
First attempt failed cause I failed to set magisk to canary resulting in a patched .img of only 46mb.
Check safetynet was successfull but Netflix doesn't work and does not appear in magiskhide (preinstalled systemapp?).
bernie012 said:
Netflix doesn't work and does not appear in magiskhide (preinstalled systemapp?).
Click to expand...
Click to collapse
Just tick - Show system apps - in magisk hide search. it ll show Netflix as well.
Sent from my KB2000 using Tapatalk
deepuvijay said:
Just tick - Show system apps - in magisk hide search. it ll show Netflix as well.
Click to expand...
Click to collapse
You're amazing! Thank you. I somehow missed that option.
Cleared Netflix and playstore cashe but still wasn't able to start it but after rebooting the device I was able to update Netflix and succesfully watch movies.
zellleonhart said:
KB05DA is the Indian variant OxygenOS, so your stock boot image should be the one below:
KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
https://drive.google.com/file/d/1Ct7IJWWXJlIZX9ekIrTKLC9G6KZLD2eq/view
Click to expand...
Click to collapse
I have the exact same question as the person you replied to, as I bought mine in Hong Kong and is the KB2000 China version.
Phone comes preloaded with Oxygen OS KB05DA version, which you said is the Indian variant. I can assume then there is no relation between the regional variant of OxygenOS and the regional variant of the phone itself?
emzee.mc said:
I have the exact same question as the person you replied to, as I bought mine in Hong Kong and is the KB2000 China version.
Phone comes preloaded with Oxygen OS KB05DA version, which you said is the Indian variant. I can assume then there is no relation between the regional variant of OxygenOS and the regional variant of the phone itself?
Click to expand...
Click to collapse
Same here too. Ordered it online and came from HK. KB2000 with Hydrogen OS also exist. So i guess it's safe to assume that there may be various OS build on the same Physical variant depending on the region.
emzee.mc said:
I have the exact same question as the person you replied to, as I bought mine in Hong Kong and is the KB2000 China version.
Phone comes preloaded with Oxygen OS KB05DA version, which you said is the Indian variant. I can assume then there is no relation between the regional variant of OxygenOS and the regional variant of the phone itself?
Click to expand...
Click to collapse
I am not sure why yours come with KB05DA, but based on OnePlus' own post in their forum, the OxygenOS versions for the 11.0.1.2 update are as follows:
IN: 11.0.1.2.KB05DA
EU: 11.0.1.2.KB05BA
NA: 11.0.1.2.KB05AA​
SourceL https://forums.oneplus.com/threads/oxygenos-11-0-1-2-for-the-oneplus-8t.1324900/
deepuvijay said:
Thanks @zellleonhart, @fxz
Worked just fine. I am now rooted on KB2000 running Oxygen OS 11.0.1.2.KB05DA.
Click to expand...
Click to collapse
Hmm, I took the KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110 boot image and patched it on magisk. Went into fastboot and booted the patched file fine.
That said, when I go back to Magisk, I don't see the option to do direct install. Wonder what the issue is there. Did you encounter this?
emzee.mc said:
Hmm, I took the KB2001 - Indian Variant - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110 boot image and patched it on magisk. Went into fastboot and booted the patched file fine.
That said, when I go back to Magisk, I don't see the option to do direct install. Wonder what the issue is there. Did you encounter this?
Click to expand...
Click to collapse
Strange. It went just fine for me. Did you use the boot image linked in Reply #3?
boot looped on tmobile variant
rtown195 said:
boot looped on tmobile variant
Click to expand...
Click to collapse
How in the **** did you get your boot unlock token from 1+?
Btw i had a doubt once im rooted and there is a new update for oos the root will be lost right or can i just use the install to inactive slot option i had this doubt cuz the boot img i used was specific to my current build
zeusofyork said:
How in the **** did you get your boot unlock token from 1+?
Click to expand...
Click to collapse
i didnt a wizard unlocked my bl
Thanks. Worked fine run the 1st time with KB2003 on Oxygen OS 11.0.1.2KB05BA after some fails yesterday. :good:
rtown195 said:
i didnt a wizard unlocked my bl
Click to expand...
Click to collapse
..... You uhhhhh, know where I can meet him?
zeusofyork said:
..... You uhhhhh, know where I can meet him?
Click to expand...
Click to collapse
PM me
Hi Guys, i tried to root my 8T today. Unlocking the bootloader worked finde. After that i updated tu 11.0.2.3.KB05BA. I extracted the boot.img and did the "installing procedure" at magisk. But even if i flash the magisk image i get no root access. I think the problem is, the stock boot.img is around 96 MB und my magsik boot.img is only 42,87 MB. I tried several version of magisk. Why is my magisk image that small?
EDIT: Okay i did every step a second time and got a function working image with the correct size.
I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?
Remove oos native call recorder module if you have it, if not just remove all modules.
MrEvilPanda said:
I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?
Click to expand...
Click to collapse
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..
dladz said:
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..
Click to expand...
Click to collapse
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.
MrEvilPanda said:
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.
Click to expand...
Click to collapse
Ah yes, always disable Magisk modules prior to upgrading firmware.
As they may not be compatible, this is also in the guide.
Glad you're up and running mate
Nice one
So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??
Arksuga said:
So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??
Click to expand...
Click to collapse
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
galaxys said:
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):
Arksuga said:
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):
Click to expand...
Click to collapse
Yep I've got guides for unlocking the bootloader and rooting in the guides sections.
Both called as such accordingly.
Tbh there are a few guides all should be fine.
Just read through the root guide.
Unlocking the bootloader it's easy.
Code: fastboot OEM unlock
Agree on phone.
Rooting:
Obtain patched image
Fastboot boot Magisk patched
Don't flash it, just wait for boot then open Magisk and click install / direct install.
Again this is all in the guides.
TLDR: I need boot.img (stock or patched) for C.21
I made a huge mistake. I thought the _11 in the new version was OOS11. The upgrade window didn't indicate it was a significant upgrade.
Anyway, I was also on an old version of Magisk because I need Magisk Hide to hide root from applications required for work.
I did the usual OTA by restoring binaries in Magisk, then installing to inactive slot before reboot, but I guess due to the old MAgisk and New OOS12, it failed.
I'm now on the terrible IN2025_11_C.21 and I lost root.
I need a copy of the boot.img from C.21
I cant seem to boot into the latest TWRP (fastboot boot twrp.img) to access adb shell and extract this myself. (Should I be able to? Does TWRP still work?)
I tried downloading the OTA from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87101587 so I can extract boot.bin myself but payload dumper just throws an error.
I tried downloading the images from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87129235 but it seems I have to pay for them. Doesnt seem legit.
I was able to extract the c.21 image from the IN2021 (India) model, but I'm not sure if that's safe for my IN2025 model.
Advice? Help?
x51 said:
TLDR: I need boot.img (stock or patched) for C.21
I made a huge mistake. I thought the _11 in the new version was OOS11. The upgrade window didn't indicate it was a significant upgrade.
Anyway, I was also on an old version of Magisk because I need Magisk Hide to hide root from applications required for work.
I did the usual OTA by restoring binaries in Magisk, then installing to inactive slot before reboot, but I guess due to the old MAgisk and New OOS12, it failed.
I'm now on the terrible IN2025_11_C.21 and I lost root.
I need a copy of the boot.img from C.21
I cant seem to boot into the latest TWRP (fastboot boot twrp.img) to access adb shell and extract this myself. (Should I be able to? Does TWRP still work?)
I tried downloading the OTA from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87101587 so I can extract boot.bin myself but payload dumper just throws an error.
I tried downloading the images from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87129235 but it seems I have to pay for them. Doesnt seem legit.
I was able to extract the c.21 image from the IN2021 (India) model, but I'm not sure if that's safe for my IN2025 model.
Advice? Help?
Click to expand...
Click to collapse
There are boot images.
[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
AFAIK, there isn't twrp for Android 12 yet
bacon612 said:
There are boot images.
https://forum.xda-developers.com/t/guide-how-to-avoid-killing-your-oneplus-8-pr
Click to expand...
Click to collapse
http://
bacon612 said:
There are boot images.
[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
AFAIK, there isn't twrp for Android 12 yet
Click to expand...
Click to collapse
Thanks.
I ended up using the Indian boot.img. it worked.
x51 said:
http://
Thanks.
I ended up using the Indian boot.img. it worked.
Click to expand...
Click to collapse
I have the same problem with IN2025_ 11_C.35 no version of twrp worked for me either. Wondering if c.21 boot.ing will work
Downloaded IN2025_11_C.21 last stable in full zip from oxygen update. Payload dumpered it and fastboot booted the stock boot.img and screwed it up good, restarted thinking it'd go back to original image but no, takes a while to fire up lock screen image comes up, home screen is black. Strangely google assistant works to voice open file manager and oxygen update, downloaded IN2025_11_c.35 incremental zip but "op12 local update" doesn't see it. Twrp doesn't work so can't side load the c.35 zip to restore the boot.img. if anyone's got a IN2025_11_C.35 boot.img or any advice I'd appreciate
Orig-pinetree said:
Downloaded IN2025_11_C.21 last stable in full zip from oxygen update. Payload dumpered it and fastboot booted the stock boot.img and screwed it up good, restarted thinking it'd go back to original image but no, takes a while to fire up lock screen image comes up, home screen is black. Strangely google assistant works to voice open file manager and oxygen update, downloaded IN2025_11_c.35 incremental zip but "op12 local update" doesn't see it. Twrp doesn't work so can't side load the c.35 zip to restore the boot.img. if anyone's got a IN2025_11_C.35 boot.img or any advice I'd appreciate
Click to expand...
Click to collapse
I think boot.img corrupted the system launcher, making the settings, home screen and app drawer black or blank. Had Google assistant open a file manager and uninstalled the launcher and it came back