Related
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
anirbannath said:
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
Click to expand...
Click to collapse
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
sunshinebhushan said:
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
Click to expand...
Click to collapse
mine also any sol to fix this?
Steps to fix any root mess-up that might happened and/or corrupt system from tampering with files.
1. Follow this guide, you can start from the flashing part
2. Download the mi flash app + a1 fastboot stock rom
3. Flash using the guide, make sure you select 'save user data'! or you will lose all your data!!
4. Once the flashing is complete you will reboot into the august patch, go to updates and install all the updates as usual
5. Root/Flash recovery using your favorite method.
I played around the system partition too much and had some issues with play services, also I couldn't update to october patch, after doing the above, everything works great. just use this guide anytime you want a clean slate.
Also always backup everything on twrp, always a useful thing to do.
Good luck
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
sunshinebhushan said:
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
Click to expand...
Click to collapse
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
Hi. As I mentioned, I am not even on the September patch. I used to be but then I rooted it today (installed Magisk) and suddenly I'm back to the August patch. September patch only installs in 'a', which is not rooted. That doesn't really serve my purpose.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
Hi. There seems to be a problem with what you suggest. The video I followed does almost the same thing. I even have TWRP, along with Magisk of course. The problem is, when I boot to 'a' (the partition that successfully installs the September update), I find that it isn't rooted. Magisk is inactive. And root checker says that root isn't properly installed. So obviously, the question of unrooting is rendered moot.
I want to be able to install the OTA update in my rooted partition and make it stick. People have installed OTA updates to rooted ROMs (mostly using FlashFire), but Flash Fire is giving me an unusual error, something about being unable to install OTA even though it has detected it due to being unable to find some files in boot/recovery folder or something like that.
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Ex-Hunter said:
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Click to expand...
Click to collapse
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?
anirbannath said:
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
Click to expand...
Click to collapse
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
Code:
fastboot getvar all
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
sunshinebhushan said:
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
Click to expand...
Click to collapse
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Ex-Hunter said:
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Click to expand...
Click to collapse
I am trying to edit directly, what is the other way to edit?
sunshinebhushan said:
I am trying to edit directly, what is the other way to edit?
Click to expand...
Click to collapse
You've to use resetprop tool for that. You can modify an existing module or put a script at /magisk/.core/service.d (I think.... haven't done that in a long while). You can ask magisk related queries here (unofficial magisk 13.4) or here (official)
Ex-Hunter said:
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
kiran8631 said:
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74203817&postcount=4
by flashing with flashfire rooted and installed supersu without twrp flash and now wifi stopped working rest everythig works just fine..for now i m back2stock...can any one tell me the most safe procedure wich do not break any drivers. i m on 1st october patch. thank you in advance
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Master_T said:
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Click to expand...
Click to collapse
As I know you could receive updates if you unlock your bootloader and flash magisk, I don't have experience with that, I've read that from other brands people do this and still get their updates.
If I'm wrong correct my.
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
I'm not sure about Mi 9t (have to wait for bootloader unlock), but it was so on Redmi 3s: I can install OTA updates, it goes through TWRP, but after every update I have to flash Magisk.
It was several years ago, so probably they've changed something
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected ?
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
Which twrp and magisk do you use?
grinandbearit said:
Which twrp and magisk do you use?
Click to expand...
Click to collapse
First TWRP that came out (LR Team), but that is because it was the only one available at the time, there might be better ones out now, check the TWRP thread for more info.
Magisk, I used the latest stable release.
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Edit: wrong quote
fabsen said:
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Click to expand...
Click to collapse
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Master_T said:
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Click to expand...
Click to collapse
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
fabsen said:
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
Click to expand...
Click to collapse
You mean the one downloaded through the miui updater? I can't flash that with twrp, it's encrypted. In fact, I can't even open the zip file with file manager, it says the file is corrupted. How do you decrypt/use it?
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Thank you all, it's nice to find this post before I create a new with the same questions.
I bought a new "Mi 9t", it received the latest OTA update, and it has been unlocked after waiting 170 hours.
MIUI Version: MIUI Global 10.3.11 Stable
Android Version: 9 PKQ1.190302.001
Model Name: M1903F10G
Now I need to root it without flashing twrp, I need to be on the Stock recovery because I don't want to lose the OTA update.
I ran this command :
Code:
C:\adb>fastboot boot recovery.img
Downloading ‘boot.img’ OKAY [ 1.404s]
booting OKAY [ 0.127s]
Finished. Total time: 1.560s
but the device reboot to MI-Recovery 3.0, can someone correct me if I'm wrong? also which twrp version support MIUI Global 10.3.11 Stable?
Matthas said:
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Click to expand...
Click to collapse
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Master_T said:
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Click to expand...
Click to collapse
oh I wish I knew After update when I went to flash back old twrp and magisk it resulted in bootloop so I was flashing all twrp I could find just to make them boot and then be able to flash magisk. However name of my file is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" I think its "fixed" chinese one.
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
akha666 said:
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
Click to expand...
Click to collapse
Is any expert have an answer to my questions?
Schnedi said:
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
Click to expand...
Click to collapse
How do i root global stable rom 10.3.11 without bootlooping? Just rooting and no twarp .
Hi, I've got a new update today (11/02) and I want to know if there's already a method to root on Android 10. I've already searched for it but didn't find anything. Thanks.
MatheusPimentel said:
Hi, I've got a new update today (11/02) and I want to know if there's already a method to root on Android 10. I've already searched for it but didn't find anything. Thanks.
Click to expand...
Click to collapse
You searched for it bad, then.
https://dropmefiles.com/PZBqh Here's boot.img patched with current Magisk (canary channel).
kibuuka said:
You searched for it bad, then.
https://dropmefiles.com/PZBqh Here's boot.img patched with current Magisk (canary channel).
Click to expand...
Click to collapse
I have just to flash it on TWRP? In Android 10 I can use the same TWRP as I've been using on Android 9?
MatheusPimentel said:
I have just to flash it on TWRP? In Android 10 I can use the same TWRP as I've been using on Android 9?
Click to expand...
Click to collapse
It's best to wait until a stable twrp is made.
I followed this and it worked perfectly.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
MatheusPimentel said:
Hi, I've got a new update today (11/02) and I want to know if there's already a method to root on Android 10. I've already searched for it but didn't find anything. Thanks.
Click to expand...
Click to collapse
I followed the standard procedure and root remained but lost decryption in twrp:
Rebooted in twrp
Ran latest magisk uninstaller in twrp
Installed Android10
Installed latest twrp of Mauronofrio
Rebooted info twrp
Installed magisk
Rebooted into system
I just updated OxygenOS and didn't see that there was a version change from Android 9 to 10 involved.
TWRP was replaced with the stock recovery during the process. That always happened when running an OxygenOS system update, but I could always flash TWRP again afterwards. That doesn't seem to work anymore now.
I guess my mistake was to reboot to system after updating, correct?
Didn't pay enough attention, I thought it was just another Android 9 update. That'll teach me...
I lost Root mine now is 10.3.0 NO ROOT
help
yahaa08 said:
I lost Root mine now is 10.3.0 NO ROOT
help
Click to expand...
Click to collapse
If you want to root I can help u.
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.
Yes, looks like we are in waiting mode for it to show up...
dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.
galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:
After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr
I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update
Same here global 406 mb ota. It's like not recognizing we have root...
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.
anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA
Hey! haven't seen anyone in this section for a while....
Why I am making this thread
So lately, I was looking through my old phones only only to find my old dusty Samsung Galaxy Note 2 lying around. It had already been rooted with kingroot... Needless to say, it's a spyware and my phone was drastically slow probably because of it.
Long story short, kingroot messed up all the files. Trying to install a working version of SuperSU gave me a headache. Finally, Magisk(v22.1) was supposed to work on the phone as it stated that it's the last version to support v4.4.2 but it doesn't actually work. It keeps on showing N/A whenever I launch it and a million different permutations that I had done in the process of rooting it using Magisk never worked.
This took me days, just jumping from one rabbit hole into another, finding old dead links which really made me so frustrated that at some point I wanted to throw the whole phone away.
That's why I'm creating this thread, so that I save the hassle for myself in the future and hopefully anyone who comes across this.
Updated rooting guide
This guide worked for my GT N7100 android version 4.4.2. It'd also probably work on other devices on other old phones which have an android version less than 5
Just make sure to backup everything before trying it.
Step 1. Flashing TWRP
Download the files from the following link
[TWRP]N7100 TWRP v3.3.1-0 ODIN FLASHABLE [23/05/2019]
Ok there we go this recovery is the latest 3.2.3-2 for t03g only don't flash this on t0lte(N7105). UPDATE: 12/04/2019: official support: https://dl.twrp.me/t03g TWRP 3.2.3-2 for N7100. Bugs: Format as F2FS doesn't work because the option isn't...
forum.xda-developers.com
Download ODIN
https://samfw.com/Odin/Odin3_v3.13.3.zip
Boot the phone into download mode(VOLUME DOWN + POWER KEY + HOME KEY)
Open ODIN and in BL choose the file that you've downloaded whose extension is or is similar to ".tar"
Click start
Step 2. Downloading and flashing Magisk
In here, you need to download a very specific version of Magisk, because anything above this version won't work.
NOTE: If you have installed any later versions of Magisk then make sure to uninstall them first, you can find out how to uninstall it from here(https://topjohnwu.github.io/Magisk/install.html#uninstallation)
Download THESE VERY SPECIFIC VERSIONS of Magisk and Magisk Manager from here
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Get into TWRP recovery mode and then flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
That's the end of it, your device is rooted now
HOWEVER, once MagiskManager has been installed, it would say that there's an update available(a newer version) available that you could upgrade to.
NEVER EVER UPDATE!! Updating your Magisk version to ANYTHING above v21.4 will cause it not to detect root. This is a bug with Magisk and it would probably never get fixed because support for android <5 had been discontinued a long time ago.
In case you ever do accidentally update Magisk, you will have to uninstall the Magisk app and then install MagiskManager-v8.0.7.apk again.
To uninstall and unroot your device, download this file and flash it with TWRP
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
Where I got the links above from
https://github.com/topjohnwu/Magisk/releases/download/v21.4/
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
ze7zez said:
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
Click to expand...
Click to collapse
Nope doesn't work as it wont be able to detect root at all, this is what had initially caused my headache to begin with
The last version of magisk that actually works on GT N7100 and probably any other old phone is the one that I linked in the thread
EDllT said:
(...)
Get into TWRP recovery mode and flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
(...)
Click to expand...
Click to collapse
Thank you for the information.
I checked on Samsung Galaxy S4 Mini LTE i9195 (stock KK 4.4.2) and it works indeed at most version 21.4.
It is not possible to install MagiskManager-v8.0.7.apk because it is installed together with Magisk-v21.4.zip.