Hello,
I'm trying to root my wife's device (downloaded November fastboot zip - Oreo 8.1) and patched image using Magisk. Everything is working fine except the VoLTE. ( She is using JIO.)
If I revert back to stock boot.img, then VoLTE works fine without issue. Am I missing something ? I'm sorry if this was already asked and discussed.
Thanks.
Answer: It's my own creation Seems like certs are getting downloaded during boot and If you have enabled "startup leak" with magisk, disable it. It should work !
Related
Hello guys,
I had been using Magisk & Xposed on Nougat before Oreo rolled out in December. However after update I lost root. When I flashed patched_boot.img I got stuck in bootloop (So I returned to stock boot.img). I am pretty sure bootloop was caused by some incompatible Magisk module. The problem is that I don't know how to disable them now - I don't want to install TWRP (because I want to be able to get OTAs) and when I use only "bootable" version of TWRP, it can not detect any files/partitions, so I am unable to use "mount-magisk.zip" to remove wrong Magisk modules. So I am kind of stuck.
Here is what I want to achieve:
- remove incompatible magisk modules
- gain root without permanent TWRP
- profit
I have been searching this forum for quite a while but couldn't find some relevant consistent information. Any tips how to deal with this?
At the moment I am running Oreo /w January update.
Thank you
For others looking for similar answers, I was able to solve it:
I flashed TWRP, then using "mount-magisk" removed all modules, then using MiFlashTool flashed original rom (you can do that without loosing data) and then I just followed guide to root using patched boot.img.
Good luck
gexcube said:
Hello guys,
I had been using Magisk & Xposed on Nougat before Oreo rolled out in December. However after update I lost root. When I flashed patched_boot.img I got stuck in bootloop (So I returned to stock boot.img). I am pretty sure bootloop was caused by some incompatible Magisk module. The problem is that I don't know how to disable them now - I don't want to install TWRP (because I want to be able to get OTAs) and when I use only "bootable" version of TWRP, it can not detect any files/partitions, so I am unable to use "mount-magisk.zip" to remove wrong Magisk modules. So I am kind of stuck.
Here is what I want to achieve:
- remove incompatible magisk modules
- gain root without permanent TWRP
- profit
I have been searching this forum for quite a while but couldn't find some relevant consistent information. Any tips how to deal with this?
At the moment I am running Oreo /w January update.
Thank you
Click to expand...
Click to collapse
Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool
RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data
I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).
Hey, i need help please.
I recenty flashed ( successfully ) RR Rom, but before that i used a patched_boot.img for root, it also worked fine. However, i installed faulty Magisk modules and now i can't boot, i tried magisk_uninstlaler but it didn't work and i'm assuming it's because of the patch_boot. Can someone please help ? is there another way i can reboot/uninstall magisk or if someone can just link me the stock boot.img
Thanks.
EDIT: I have successfully removed the faulty modules using methods in TWRP and rebooted my phone - but anyway, do you think i need to reflash stock boot.img ?
You can find stock ROM files (including boot.img) here:
The latest one: http://en.miui.com/download-333.html
Current + previous versions: https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
Good day fellow XDA members,
I recently updated my 8 Pro to 11.0.5.5 and forgot that i should not have rebooted it. (Worst idea ever, i know)
I had Root with Magisk before, but now I don't obviously.
So I thought to myself, that this shouldn't be a problem just flash the patched_boot.img anew and i'll have Root again.
Well that was certainly not the case.
I tried just about anything I could find on some Forums the last two days, but couldn't get the device rooted.
What i tried:
Several boot.img from XDA and also patched my own boot.img from the extracted payload with every Magisk apk from 21 onward(Also beta and Canary).
The old patched boot.img i used before the update.
Horizon bootloader
There is obv no Magisk module present anymore to disable/delete.
I also have EdXposed installed.
Everytime i tried something other than the original boot.img i got either a bootloop or a crashdump screen.
Can i get root back without fully wiping my 8 Pro?
If yes, how?
If not, how can i backup everything because some Data from some Apps is crucial to me and is not saved in the Cloud.
Thanks in advance
Dead1y_Wolf
I'm on the same boat I did direct install instead of install to inactive slot
Just follow my guide, change the payload dumper you're using, use the latest version of magisk
Bare in mind that you need to match the version used to create it.
Also don't flash the image. Just boot it.
Make sure modules are removed beforehand.
If that still fails then use the ADB magisk removal command then proceed.
I've booted, flashed, directly installed and updated then installed a lot and have never had a single problem..
So the process is correct..
Hi,
is anyone running latest B20 Oreo rom on an A2017U phone with Magisk v25?
When I patch boot image and flash it via EDL the phone doesn't boot it, I have to restore original boot.img to be able to boot android again.
Also, fastboot is not available in the stock EDL images, any idea how to get fastboot back?
Thanks
Hi,
For first, I flashed some ROMs earlier in my life but it was like 5 years ago. I'm not expert in that field. That being said... I'm running B02 Oreo ROM on A2017G but i had the same problem. I managed somehow to find somewhere (can't remember which site) that "Magisk 16.4 should work because 16.0 version had some problems". So I tried 16.4 and it worked for me. Unfortunately data partition, although it shouldn't after root, stays encrypted (in TWRP).
Also, if You boot to system and open Magisk manager it will show You that update is available. After updating to the latest app version it will say that your version of Magisk is not supported now and You should update it (meaning, flashing latest zip). I didn't try it but assuming that earlier it didn't want to boot with the latest version on "Magisk-v25.1.zip" it won't at this time too.
It's so hard to find any information about this phone this day's... I would love if someone knew how to disable this encryption. I tried I think every solution and nothings seems to work :/
I hope I'm not late and my post will help You