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.
Related
For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS118C.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
INCREMENTAL UPDATE (OFFICIAL) (DRIVE MIRROR LINK by me) (from TOS089A to TOS118C / from decf3a575d to aa4d5d86bc)
In the post below you can have some information on how to grab OTA links from the WileyFox BSP server. Have fun, and don't forget to debloat your system
How to grab the official OTA from BSP's server
In the OP, I left a link to the official incremental update right from the OTA server (which I'll talk about a bit later). If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
... Or you can just wait til someone mirrors it, like I already did
Lastly, as a side note, I'd also like to comment the following, regarding BSP:
Wileyfox's devices software is now in charge of this company, called BSP.ninja and that clearly defines themselves as a company to "launch an Android device without knowing where to start". It's said to be formed by former Cyanogen employees, or, at least Ricardo Cerqueira @aremcee (which btw, is also in charge of the Open Source code available in BitBucket for the Wileyfox devices), since he's the owner of the domain. In any case, what I want to say is that the code is being done quite possibly by the very same people that did the job at the now dead Cyanogen, so it shouldn't be a reason to worry. Also, it'd be awesome if the team released a working device tree so that the community could bring custom ROMs just like you (the team) used to do.
linuxct said:
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
Click to expand...
Click to collapse
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
boa05 said:
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
Click to expand...
Click to collapse
Correct. I'm preparing a new version of my debloater tool, and I'll briefly explain in it's thread how to move from TOS089A to TOS118C without losing anything in rooted and/or debloated devices. Stay tuned!
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
zerospaced said:
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
Click to expand...
Click to collapse
I also skin my phone through substratum (the default orange theme is disgusting), I use magisk and plenty of other tools both systemless or even require modifying the system partition (like Wileyfox debloater), and, using the instructions I wrote in this post here I've found no single problem upgrading my device from a debloated, rooted and themed TOS089A to TOS118C to then debloat, root and theme it again. It's true you will need to install your substratum themes again, but the rest should work perfect.
I've tried the recovery update on my Swift 2X but can't get it to boot. I have TWRP installed (3.1.0-0) and it's rooted via SuperSU. Do I have to unroot first?
Edit for more info: I did the OTA upgrade from the stock CyanogenOS ROM to 7.1.1 TOS089A. Then I installed TWRP and flashed SuperSU. The OTA to TOS118C predictably doesn't work. Flashing the recovery image via TWRP seems to go fine but I'm stuck at the white "Wileyfox powered by Android" screen. Tried wiping Cache/Dalvik but no dice.
Edit 2: flashing Magisk afterwards seems to make it work.
I try to install the ZIP via TWRP and after the process ends the phone reboots but it remains stuck at the "WileyFox" white screen.
EDIT: I tried the fastboot one and it worked. Sometimes is hard to understand our devices
I'm guessing it's some kind of dm-verity issue? Flashing in TWRP worked for me when I flashed Magisk 12.0 afterwards, which seems to take care of dm-verity. Linuxct suggested installing Magisk in his debloat thread and I thought "what's the harm". Now I'm a happy camper.
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Will this Firmware work on my Swift 2 Plus?
Cappucinto said:
Will this Firmware work on my Swift 2 Plus?
Click to expand...
Click to collapse
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Afifus said:
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Click to expand...
Click to collapse
Thank You so much
Installed it via fastboot and now iam stuck in a bootloop :S
EDIT: Did a factory reset in recovery! Works now.
Swift 2 Plus on 13.1.5 Cyanogen. Which method is best to install Android 7.1.1 TOS118C manually. The phone is stock, not rooted. Thanks
gaborkov9 said:
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Click to expand...
Click to collapse
If you use the
Code:
adb reboot "dm-verity enforcing"
can you remove the dm-verity menu on boot or do you need it left as after bootloader unlocked?
TOS373J?
Anyone have the images for the latest update?
TOS373J OTA
other link
Pooh042 said:
TOS373J OTA
other link
Click to expand...
Click to collapse
doesnt work gives me instal error 7 when i try to instal it
DarthBraindrain said:
doesnt work gives me instal error 7 when i try to instal it
Click to expand...
Click to collapse
what is your current firmware version?
If so, how? Thanks!
magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
worked for me perfectly
pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?
Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.
Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?
Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern
This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk
Restore Images
Start OTA update
Downlowd
Step1
Step2
Go Back to Magisk
Install to 2nd slot
Reboot
It was working ... very easy!
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong
quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.
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.
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
You could try searching "direct install not visible in Magisk".
paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
Are you sure you booted the right boot image?
Try with this one:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I think the magisk patched 1.5.2 is not really patched or there are some checks in place that allow only certain imgs to work
If it still does not work, download the stock boot, patch it with magisk select that boot img, fastboot, boot the new patched img
TheNewHEROBRINE said:
Are you sure you booted the right boot image?
Click to expand...
Click to collapse
I tried to boot the images from here:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I tried multiple boot images
AnotherM1m said:
Try with this one:
Click to expand...
Click to collapse
You didnt attach something
paper88 said:
You didnt attach something
Click to expand...
Click to collapse
shift enter is a special combination here on xda i've edited my previous message
AnotherM1m said:
shift enter is a special combination here on xda i've edited my previous message
Click to expand...
Click to collapse
Still no success. I just think I broke something while I did the OTA and I just need to wait till the next update. I restored first the images and installed it over OTA, after restart the update was not installed but Magisk deinstalled. Then I installed it again and restarted it and wanted to flash boot.img, but since then its not working anymore
what command on the terminal are you using for boot.img?
AnotherM1m said:
what command on the terminal are you using for boot.img?
Click to expand...
Click to collapse
Tried fastboot boot img and fastboot flash boot img
paper88 said:
I tried to boot the images from here:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I tried multiple boot images
Click to expand...
Click to collapse
I mean are you sure you booted the patched image and not the stock one? Are you patching the booting yourself?
paper88 said:
Tried fastboot boot img and fastboot flash boot img
Click to expand...
Click to collapse
Are you on a global device or eea?
Have you tried patching the img yourself?
TheNewHEROBRINE said:
I mean are you sure you booted the patched image and not the stock one? Are you patching the booting yourself?
Click to expand...
Click to collapse
AnotherM1m said:
Are you on a global device or eea?
Have you tried patching the img yourself?
Click to expand...
Click to collapse
I tried the stock img and patched by myself and also tried to boot the patched image from AnotherM1m
paper88 said:
I tried the stock img and patched by myself and also tried to boot the patched image from AnotherM1m
Click to expand...
Click to collapse
Do you know if you have an european device or a global one?
is your device's name Spacewar or SpacewarEEA?
AnotherM1m said:
Do you know if you have an european device or a global one?
is your device's name Spacewar or SpacewarEEA?
Click to expand...
Click to collapse
Its Spacewar EEA
paper88 said:
Its Spacewar EEA
Click to expand...
Click to collapse
Ok, the problem is that we just discovered 1.5.2 is not unified at all.
Those images are not working because they are dumped from a global device.
You need a modified eea image which i cannot find for now...
I did root my 1.5.2 EEA without issues with a self-patched 1.5.2 Stock from https://forum.xda-developers.com/t/...g-os-repo-of-nothing-os.4464039/post-87101175
Since you are very fortunate that this device has usable EDL mode, you can always dump your boot image on any firmware you're by using the EDL tool made by @mark332. (However, I suggest you try following @dedors suggestion first).
paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
Perhaps you are simply missing a step, here are Magisk's official Installation Instructions. They give step-by-step instructions on patching.
ethical_haquer said:
Perhaps you are simply missing a step, here are Magisk's official Installation Instructions. They give step-by-step instructions on patching.
Click to expand...
Click to collapse
What did I do wrong? I do it like this since 12 months on oneplus and nothing