Okay I know there are already many threads related to this issue but novice users like me needs a clear answer. I unlocked the bootloader of this device and installed magisk to get root (the method without using twrp, but the modified boot.img). Now when I wanted the ota, I uninstalled magisk using uninstall.zip (worked), flashed stock boot.img(worked) and relocked the bootloader and did a factory reset (worked). (Btw, I haven't installed any modules). Received the ota after several days and downloaded it. But it turns out, it shows an "installation error" everytime I try to update it. I think installing magisk tampers your system partitions hence even though you can get the update, but cannot install it. And then there are many "YouTube tutorials" who claim to have installed the OTA after uninstalling magisk and unrooting it.
The only option left for users like me is to flash the stock oreo rom from mi global and then try to update it. (Please recommend me any other solution if you know) But my question is to the experienced ones in this forum, can you say, once tampering with the system using magisk, you can still successfully install an OTA update?
Related
hi,
I have a rooted moto x play (indian version)
I downloaded the OTA update, which reboots to recovery and fails. I use twrp as recovery.
And then it keeps failing. I want to install OTA update but don't want to reset my mobile.
Screenshot. ( boot loader is unlocked)
Maybe do a search prior to posting about installing an ota when rooted and running a custom recovery. There's more than a few threads regarding this specific situation.
All you're really doing is cluttering the MXP threads with non needed threads.
I'm not even going to help you out because I hate spoon feeding people who can't even or are to lazy to do either a search on XDA or google.
I did try searching for. no help
can anyone help?
Rooting means you're modifying the system. The system will not be like before. You may be able to download the update but that won't get installed. The modification of system files won't allow you to patch them with the OTA update. So the only way is to flash the firmware manually
since Lollipop, Google doesn't let the OTA install on top of a modified system. (any modification at all). If you were rooted, and you unroot, the system is still considered "modified".
you want to install an official update from your manufacturer, the recommended process is to first return your device to completely stock including replacing TWRP with a copy of the stock recovery.
If you have nandroid backup before install SuperSU, first flash that and flash stock recovery and boot into stock and get ota and flash then you can re root and flash recovery again.
My phone is prompting me to update to B29, but when it reboots, it brings me to the TWRP recovery, and I can't seem to find an update.zip or anything. Is it not there, or am I just looking in the wrong places? Will it even successfully update with the bootloader unlock (not the official unlock) and TWRP installed, or do I need to restore the stock recovery?
My phone was originally on B20_boot, but I've since restored using Draken's TWRP files to get to B27 (I'm assuming still B20_boot).
You won't be able to OTA update with your system modifications. DrakenFX has flashable zips posted in another thread, but beware there seems to be quite a few bugs in b29 (I have no in-call audio personally).
You can use my updated post to B29 (bootstack and boot/system) flashable files are there.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
So why am I getting the notification, then? Will it just keep popping up, or is there a way to block it (even though I'm not rooted)?
As for the bugs, I've seen plenty who have upgraded to B29 without issues. How did you update? Could it be something with updating via TWRP?
Have you personally heard of anyone having problems with your update file? Will it wipe my phone (ie: will I have to reinstall everything)?
Bootloader unlocked, normal twrp flash as per DrakenFX's instructions. And yeah but a lot of people are in both boats so your milage may vary.
Thanks. Do you think I'll be able to keep my data partition intact? I really don't want to set everything else up again. It's getting old... lol.
I wiped everything, so I'm not sure. Maybe that's why my stuff is broken lol
You can't do system updates with custom bootloader's. You are getting the message because you still have the update program on your phone. Look for some sort of update.apk and disable or uninstall it.
I didn't think you could do that without root.
Oh well, I plan on putting root back on soon anyway.
That would be interesting, if true. You would think a "dirty flash" would cause more problems than a clean one.
What about the whole "can't root B29" thing. I've seen a comment where someone said they could not root B29 since they didn't root before the upgrade. I'm not rooted now, but I am bootloader unlocked with the latest TWRP. Should I be ok to flash without rooting first? I was hoping to root afterwards, and try to figure out a way to make Magisk work.
You can't root locked bootloader B29 afaik at the moment. You'd either have to unlock your bootloader or stay on B27 to get root.
I am bootloader unlocked.
I'm not rooted now, but I am bootloader unlocked with the latest TWRP.
Click to expand...
Click to collapse
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377
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).
Hello! first time posting and been trolling the forums the last week now since I got my MiA1.
I rooted my device early on the January update (Didn't realize there was more updates.) And now It's rolled into a pile of trouble.
I rooted my device with the patched image and magisk. Then tried to instal Gcam which I apparently did improperly I think because it locked my phones bootloader and gave me the error "The system is destroyed"
Reloading into bootloader and unlocking it fixed this but then I got the OTA update notice and my system has randomly restarted to boot loop a few times. TWRP is also installed I believe from when trying to install Gcam.
So my question is, Can I return to the original stock system and image? I would like to safely remove everything, root, gcam, twrp, magisk and return to how it was, I feel like I need to be more careful and learn more about the root process.
I also attempted to update with the OTA guide by restoring images in Mgisk, but the update failed and also caused a lot of problems rebooting. Any help is appreciated thank you!
You can use the Mi Flash tool to install the global rom.
@KylieDigital
Read ---> https://forum.xda-developers.com/mi-a1/help/reflashing-xiaomi-a1-question-t3763853