Related
This guide is for update within versions if you are rooted, if not, simply download and install de ota or with FF.
If you update to B394 from any version, downloading the last complete packet in update system, it locks the bootloader !!! be advised
If you update to B399 or B401, B402 from B394, downloading the last complete packet in update system, DO NOT LOCK the bootloader !!! good news
My first problem was when I was in B380 and rooted , the b389 ota arrived...then I unroot, put stock recovery and unistalled busybox, but ota failed at 8%
The solution to this :
1 - flash stock recovery from version you have
2 - download the last complete packet in update system , for me 2.41 Gb, not the ota
3 - (optional but useful for future) connect to pc and copy the 3 files downloaded the update in HWOUC to pc
4 - make the normal update in update system
7 - copy supersu 2.82.zip original file or Magisk to SD
8 - Flash last twrp recovery twrp-3.1.1-1-frd , enter in twrp recovery and:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
10 - Make a backup of boot (for future) if you want
11- flash supersu 2.82 original or Magisk
12 - reboot and it's done!!!!!!!!
Update to B394
if you have done all the process and you want now to update to b394, you can uninstall first supersu within options menu saying yes to all questions when uninstalling and without errors or bad uninstallation; then, delete binaries of busybox, flash stock recovery and try to install ota...for me the ota not installed and done with errors.
Then I installed b394 full and locked my bootloader, forcing me to format all because i unlocked the bootloader (remember to activate oem bootloader unlock on and usb depuration on).
After installing the same twrp recovery, I tested the magisk v14 and works perfect, but with an inconvenient, you have to disable the option of magisk manager "magisk hide" to work with fingerprint ,At version 15.3 I didn't see this error.
B394 to B399
Tried the uninstaller of magisk flashed with twrp to unroot and then put the stock recovery and failed, then I flashed stock boot and failed ....finally it worked downloading the last complete packet in update system.Then the habitual, flash twrp recovery, magisk v15.3 from twrp and magisk manager v5.5 in android...and worked perfect
B399 to B401
This time I only unistalled binaries from busybox and flashed stock recovery; then launched Full update (2.41 Gb) without problems.Then flashed twrp, magisk 15.3 from twrp as usual and nothing more...magisk manager detected all ok and I have a rooted device again.
B401 to B402
Simplified the process, now only flash the stock recovery 401 and make the full update packet (2.41Gb). Then flash twrp, enter in twrp, flash magisk 16.0, reboot and that's all. Install busybox script, adaway hosts and done.
Notes:
1 - If the system downloaded automatically the small ota update. you must to try to update with an obvious error, then you can download the full update packet.
1 - the installation of magisk is simple, in twrp flash the magisk.zip , reboot and install magisk manager to control all. This is another app to root and don't need supersu. The advantages to make this is magisk hide, it permits to work with apps that can't work if your phone is rooted.
Wow awsome guide. Thanks alot bro .+1
gopinaidu77 said:
Wow awsome guide. Thanks alot bro .+1
Click to expand...
Click to collapse
happy to help!
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
in the options of the twrp, last tab , there's a thick that says this
deadko said:
in the options of the twrp, last tab , there's a thick that says this
Click to expand...
Click to collapse
Bro , y u should mount vendor?
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
gopinaidu77 said:
Bro , y u should mount vendor?
Click to expand...
Click to collapse
to root correctly with supersu original version
deadko said:
to root correctly with supersu original version
Click to expand...
Click to collapse
But i dont think modifying vendor part is good .
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
I didn't say nothing to modify nothing, I said thick this option on, and in my case, I did nothing because is marked by default.
deadko said:
I did nothing to modify nothing, I said thick this option on, and in my case, I do nothing because is marked by default.
Click to expand...
Click to collapse
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
gopinaidu77 said:
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
Click to expand...
Click to collapse
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
deadko said:
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
Click to expand...
Click to collapse
Ok , thanks though
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
at the tab up to the right in update system
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
Click on 3 dots on the top right corner . U will see the option.
deadko said:
4 - download the last complete packet in update system , for me 2.41 Gb, not the ota
Click to expand...
Click to collapse
My option is greyed out, what should i do?
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
fabh2o said:
My option is greyed out, what should i do?
Click to expand...
Click to collapse
the ota is avaliable for you?
deadko said:
the ota is avaliable for you?
Click to expand...
Click to collapse
Yes i'm downloading it right now
Edit: i'm downloading the 2,41 gb update, thanks for the support.
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Snowjack said:
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Click to expand...
Click to collapse
very large process, but you make a hard reset, and my process is to preserve data and use original supersu not the modified , thanks for info
This is totally CLEAN and Typically ENGLISH (OFFICIAL) version that means no chinees APPS no issue.
Donot forget to make a backup before starting.
Steps to Follow: (FOR TWRP installed user)
1. Download 20s OTA file from here.
2. Download 21s OTA file from here. (Donot Download this ZIP file as i got an OTA update of 21S after installing 20s)
3. Goto TWRP recovery.
4. Formate everything. (Cashe, Delvik, Sysytem,Data)
5. Flash the 20s Rom (Provided in STEP 1)
6. After Installing and setting up phone, You are ready to GO BACK to official stock recovery.
Steps to Follow: (FOR already on stock recovery users)
7. Download the 21s recovery (provided in step # 2)
8. change the name to update.zip
9. put it into the root folder.
10. Goto stock updater and slect MANUAL UPDATE from 3dots on top.
11. This is will install the recovery 21s.
12. DONE
Note: you can not install 21s directly on custom recovery as it will give error 7
Can you 1. correct typos 2. move this to https://forum.xda-developers.com/le-2/how-to
Thank you
Thread cleaned up.
If you find some rule violation, please report it.
Also this is not a thread to bring up your personal vendettas. Add the annoying member to your ignore list and move on. No need to use foul language.
Consider this as the first and final warning. If this is repeated any further, there will be action taken against your accounts.
Hope I made myself very clear.
Regards
Vatsal,
Forum Moderator.
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
26s removed
as the provider stopped me to share it. correction in heading done.
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
zogu said:
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
Click to expand...
Click to collapse
As I already mentioned that I have tested these file on my x522(S3) before upload.
Nd x52x series means x520/522/526
Download 20s flash it you will receive 21s automatically
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
Original 26s is available in Chinese only. You can flash it via twrp than root nd remove all Chinese app.
Chinese twrp ?
edan lkr said:
Chinese twrp ?
Click to expand...
Click to collapse
Yes.
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Christhepenguin said:
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Click to expand...
Click to collapse
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
gtd2000 said:
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
Click to expand...
Click to collapse
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Christhepenguin said:
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Click to expand...
Click to collapse
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
gtd2000 said:
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
Click to expand...
Click to collapse
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Christhepenguin said:
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Click to expand...
Click to collapse
I note that this says it's the ROM for the S3.
I'm using the X527 which is the S2 with the Snapdragon chip (now listed as X526 after installing 21s), did you perhaps flash the incorrect ROM?
I had continual problems upgrading from 19s with TWRP - it would go through the whole process and then reboot to 19s..
Even after the replacement of the stock recovery, the first ROM I downloaded (21s) was not accepted. Had to download another one for it to finally work.
Could be a bad download?
Contact
How did you contact leeco and get this. I need all future updates. My phone is rooted and I am unable to completely unroot it and get OTAs.
---------- Post added at 02:59 AM ---------- Previous post was at 02:52 AM ----------
rodogg88 said:
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Click to expand...
Click to collapse
If you don't have TWRP or anything installed, it should work fine if you put the 20s update in the root folder (the folder with the android and download folders). Then just go to system update, press menu, press local update, go through prompts and it should update automatically. Then just repeat the process for the 21s update. If you have twrp installed, I'm pretty sure the chinese ydss version doesn't allow OTA installs. This update requires stock recovery installed because it updates through the recovery. You can find stock recovery images on google (search le s3 stock recovery and click skyneel) or, someone might have posted a recovery image on the le 2 forum. Plz reply if it doesn't work, it worked for me tho.
Is there any bugs? If yes please list. Thank you
does it work for le s3 X626 mtk?
if not, please guide me as I see that this forum support Le S3.
thanks.
Requirements
We are updating MiUI Notch Notification Mod every week for MiUI dev and stable firmwares. In order to install this mod, you need to match the following requirements:
Xiaomi Android smartphone or tablet
v10 ROM
Unlocked Bootloader (for TWRP)
TWRP custom recovery
How-To
Click the download-button and select your Xiaomi rom version from the list to get the MiUI Notch Notification Mod for your correct MiUI ROM version. You can choose from two different packages, which will let you either Install or Uninstall the mod.
Download the ZIP File
Download link for all version
https://mi-globe.com/mod-download/?modtype=notchnot&id=13&codename=platina&phone=Mi+8+Lite
Copy the File to your phone/tablet
Reboot to TWRP Recovery
Select ‘Install ZIP from /sdcard’
Select the ZIP File
Install and Reboot
I'm in global 10.3.1.0, which version do I use?
renan1217 said:
I'm in global 10.3.1.0, which version do I use?
Click to expand...
Click to collapse
First backup your data after backup flashing last version
https://play.google.com/store/apps/details?id=zanini.andrea.notchtest
use this. no need to wait.
Bootloop?
My phone doesn‘t boot anymore. It is trying to but after a while seeing the bootanimation it restarts into twrp... I didn‘t backup my system. Is everything away now? Also tried installing the disable zip. Problem still there. I think I need to install the rom again with MiFlash
I have unlocked bootloader, and I have twrp and magisk
Please tell me how to update, I've received the notification but I don't know how is the process to update on this situation
Well, if the classic way doesn't work, you can try this :
https://c.mi.com/thread-1890305-1-0.html
And if still not, well this way (but with the correct files for your device !!) :
https://www.androidcentral.com/how-download-and-install-miui-9-redmi-note-4
21vm said:
Well, if the classic way doesn't work, you can try this :
https://c.mi.com/thread-1890305-1-0.html
And if still not, well this way (but with the correct files for your device !!) :
https://www.androidcentral.com/how-download-and-install-miui-9-redmi-note-4
Click to expand...
Click to collapse
Thanks man
When I bought my phone 2 weeks ago (global version) I was notified of the 10.3.6 update, I hope it is ready when I arrive or can I install the latest package?
Were you able to flash it with TWRP? Or how did you do it?
How were you able to update?
sonrics1993 said:
I have unlocked bootloader, and I have twrp and magisk
Please tell me how to update, I've received the notification but I don't know how is the process to update on this situation
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
1) download the full recovery rom for your device from here https://xiaomifirmwareupdater.com/miui/
2) reboot to recovery
3) wipe dalvik art/cache and cache
4) flash the rom and magisk (don't reboot to system until you've flashed magisk)
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
1) download the full recovery rom for your device from here https://xiaomifirmwareupdater.com/miui/
2) reboot to recovery
3) wipe dalvik art/cache and cache
4) flash the rom and magisk (don't reboot to system until you've flashed magisk)
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
I’m on stock rom, MIUI Global 12.0.2, rooted with Magisk 21.4 and Orangefox recovery. Now there is an update to MIUI 12.0.3.
I’m not sure what to do. When I go to https://xiaomifirmwareupdater.com/miui/ there is no recovery to 12.0.3. I can only find firmware 12.0.3. Can I still use this solution with firmware type?
svendsvin said:
I’m on stock rom, MIUI Global 12.0.2, rooted with Magisk 21.4 and Orangefox recovery. Now there is an update to MIUI 12.0.3.
I’m not sure what to do. When I go to https://xiaomifirmwareupdater.com/miui/ there is no recovery to 12.0.3. I can only find firmware 12.0.3. Can I still use this solution with firmware type?
Click to expand...
Click to collapse
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
There is the last 12.0.3!?
EDIT, Sorry wrong thread! I have far too many chrome tabs open
joke19 said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
There is the last 12.0.3!?
Click to expand...
Click to collapse
I'm sorry I only see V12.0.1.0.QFGMIXM for Redmi Note 7 Global.
joke19 said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
There is the last 12.0.3!?
Click to expand...
Click to collapse
I’m rather confused. When I go to About phone it says my MIUI version is Miui Global 12.0.2 stable (QFGEUXM). But the EEA version in your link has the same number: QFGEUXM. Does that mean I can use the Redmi Note 7 EEA Stable Recovery V12.0.3.0. (QFGEUXM)?
Edit: I can see when I click Download the Package Name includes "Global". So I guess it is usable? But then do I choose the Incremental Update or must I download Full ROM (.zip)?
Edit2: Just an update in case anyone should have the same question. I flashed the EEA version without problems. And I downloaded the Full ROM.
darhma said:
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
1) download the full recovery rom for your device from here https://xiaomifirmwareupdater.com/miui/
2) reboot to recovery
3) wipe dalvik art/cache and cache
4) flash the rom and magisk (don't reboot to system until you've flashed magisk)
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Is this guide still legit after Magisk 22?
svendsvin said:
Is this guide still legit after Magisk 22?
Click to expand...
Click to collapse
I'm not 100% sure because I don't use MIUI, but I think it's still good, what makes you think it's not good anymore? I don't think there have been any particular changes in how MIUI or magisk works that would make it obsolete
darhma said:
I'm not 100% sure because I don't use MIUI, but I think it's still good, what makes you think it's not good anymore? I don't think there have been any particular changes in how MIUI or magisk works that would make it obsolete
Click to expand...
Click to collapse
Mainly because of the installation guide - https://topjohnwu.github.io/Magisk/install.html#custom-recovery - and Lavender's missing ramdisk. But I'm not sure and therefor I ask.
svendsvin said:
Mainly because of the installation guide - https://topjohnwu.github.io/Magisk/install.html#custom-recovery - and Lavender's missing ramdisk. But I'm not sure and therefor I ask.
Click to expand...
Click to collapse
I'm on official lineageos 17.1 and yesterday I've updated magisk to version 22, then updated the rom without problems. But I've updated magisk from magisk app not from recovery, so I'm not sure that installing magisk from recovery still works in rn7. Anyway after the rom update, magisk still works correctly. Maybe it's better to ask on the magisk thread: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/
svendsvin said:
Mainly because of the installation guide - https://topjohnwu.github.io/Magisk/install.html#custom-recovery - and Lavender's missing ramdisk. But I'm not sure and therefor I ask.
Click to expand...
Click to collapse
FYI there could be a bug in Magisk 22 regarding missing ramdisk in Xiaomi: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84557999
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.