Related
I have just received the OTA and it is failing to install...
Anybody else facing this issue? Any ideas on how to fix it?
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
luizffgarcia said:
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
Click to expand...
Click to collapse
Being rooted is your issue
krelvinaz said:
Being rooted is your issue
Click to expand...
Click to collapse
What is the easiest way around it then? Do i have to download the factory image and flash it losing everything i have configured? Or is there another way?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
UpGrad3 said:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
Click to expand...
Click to collapse
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
luizffgarcia said:
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
Click to expand...
Click to collapse
That happened the first time I tried to root. Had to flash the factory image and start over. Guess I could do that...but seems there has to be an easier way. I'm really curious why the method in that guide doesn't work for me.
Does flashfire work to install the OTA?
luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
TonikJDK said:
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
Click to expand...
Click to collapse
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
JayBlack_686 said:
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
Click to expand...
Click to collapse
Redo it, otherwise you are a month behind on the boot IMG.
TonikJDK said:
Redo it, otherwise you are a month behind on the boot IMG.
Click to expand...
Click to collapse
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
JayBlack_686 said:
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
Click to expand...
Click to collapse
Correct, you can use whatever boot IMG you want. Snoke may be updated to November... don't know...bit if it is and you like it use it.
Waiting for answers. I finally succeeded with rooting my xiaomi mi a2 lite, everything works perfect, I was so excited to install Xposed but then my phone started to lag AF. I uninstalled it and then the update show up in the notification bar, great but "couldn't install system update". Is it because of the root or TWRP?
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
ItsCrewz said:
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
Click to expand...
Click to collapse
Try flashing Magisk 16.7
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
manasgirdhar said:
Try flashing Magisk 16.7
Click to expand...
Click to collapse
Yea I tried that, didnt work
RiTCHiE007 said:
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
Click to expand...
Click to collapse
No idea what a Patched Boot is xD
ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
ItsCrewz said:
No idea what a Patched Boot is xD
Click to expand...
Click to collapse
patched boot with magisk
manasgirdhar said:
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
Click to expand...
Click to collapse
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
ItsCrewz said:
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
Click to expand...
Click to collapse
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
manasgirdhar said:
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
Click to expand...
Click to collapse
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
ItsCrewz said:
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
Click to expand...
Click to collapse
Order shouldn't really matter in a batch restore
manasgirdhar said:
Order shouldn't really matter in a batch restore
Click to expand...
Click to collapse
I mean. Like, I need to remake how my homescreen was made
ItsCrewz said:
I mean. Like, I need to remake how my homescreen was made
Click to expand...
Click to collapse
Wouldn't that be already backed up in the launcher data?
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
You can't flash Magisk 16.7 from TWRP. It causes issues more times then not. You need to flash TWRP 16.4 (1642) then let the Magisk manager update to 16.7.
Magisk 16.7 will often give you an error on boot which looks like a vendor mismatch message. I stick with 16.4.
the reason it fails only with root is because the mod he installed is still installed. It only turns on when you have root. remove mod and problem fixed. also, reflashing rom does not remove magisk mods. only uninstalling mod will fix this or a full format.
the mod lives in /data.
memocatcher said:
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
Click to expand...
Click to collapse
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
vinct94 said:
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
Click to expand...
Click to collapse
Do you have a USB drive with USB C connector?
It is a lifesaver
Why cant you flash 16.7 again. That's the only one I flash in my TWRP and I never have issues.
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712#login
Click to expand...
Click to collapse
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
JJT211 said:
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
Click to expand...
Click to collapse
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
TonikJDK said:
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
Click to expand...
Click to collapse
I usually verify root by downloading root checker app. App says that I'm not rooted.
EDIT: Nevermind, I tried it again and now it says I'm rooted. Thanks!
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.
spotmark said:
Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.
Click to expand...
Click to collapse
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.
Daisymae said:
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.
Click to expand...
Click to collapse
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Eudeferrer said:
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I'll give it a try...
Addendum--Tried both slots=bootloop
Daisymae said:
I'll give it a try...
Addendum--Tried both slots=bootloop
Click to expand...
Click to collapse
Works! Downloaded latest MM then patched file. Root!
kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Try the very latest Canary MM. It works!
Daisymae said:
Try the very latest Canary MM. It works!
Click to expand...
Click to collapse
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one
kngbn79 said:
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one
Click to expand...
Click to collapse
Try again today. He just pushed a new magisk update. (Today)
Anyone tried this on dp3?
I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.
lafester said:
I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.
Click to expand...
Click to collapse
Update: SDK Platform-Tools: r30.0.0
It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now
kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Cant you use direct method? boot the phone with patched boot and flash direct. This method eliminates most issues.
Update: SDK Platform-Tools: r30.0.1
billyt1 said:
It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now
Click to expand...
Click to collapse
Weird I flash the dp4 patched boot without issues
On July 5th update, works great! (Though not all modules work due to the removal of /sbin, etc)
?