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
Related
need small help which would benefit others too.
anybody who are ready to format device or has a good backup
try to flash latest magisk 15.0 on u'r device- Ohh, don't flash directly 15.0- i already tried it and it wouldn't work or change device to generic
our device was working perfectly with magisk upto 14.5 but it lost support later
An user in magisk forum with huawei device claimed that- u need to check 2 options which are under safety net check
tick these options
Preserve force encryption
Preserve AVB 2.0
(Check attached pic)
flash 14.5 magisk- then update magisk to 15.0 within the magisk manager checking the above mentioned options
I invested lot of time this morning to troubleshoot this but couldn't get it right but above mentioned method seems reasonable- so anyone who has backup of entire device or going to format device soon- just try whether this method works and report back.
sreekantt said:
try to flash latest magisk 15.0 on u'r device- Ohh, don't flash directly 15.0- i already tried it and it wouldn't work or change device to generic
our device was working perfectly with magisk upto 14.5 but it lost support later
Click to expand...
Click to collapse
Damn, i was updating to my latest build last week and immediately after i flashed TWRP, Magisk V14.6, i was on V14.5 before the update and since that only after this i went to check phone info, noticing the model changed to generic_a15, i thought that i made something bad. It was Magisk's fault so instead! I restored a previously took backup made before updating and now i have to doing again the update. This time i won't flash nothing above V14.5.
RedSkull23 said:
Damn, i was updating to my latest build last week and immediately after i flashed TWRP, Magisk V14.6, i was on V14.5 before the update and since that only after this i went to check phone info, noticing the model changed to generic_a15, i thought that i made something bad. It was Magisk's fault so instead! I restored a previously took backup made before updating and now i have to doing again the update. This time i won't flash nothing above V14.5.
Click to expand...
Click to collapse
Yes exactly- 14.6 and 15.0 are changing vendor partition .....few claim that preserving force encryption and dm verity does the trick
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
looks like this method is working on huawei p9
sreekantt said:
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
looks like this method is working on huawei p9
Click to expand...
Click to collapse
Thanks for sharing. I'm taking a nandroid backup, testing it in 5 minutes...
RedSkull23 said:
Thanks for sharing. I'm taking a nandroid backup, testing it in 5 minutes...
Click to expand...
Click to collapse
good lord ! waiting for results :fingers-crossed:
sreekantt said:
good lord ! waiting for results :fingers-crossed:
Click to expand...
Click to collapse
It worked
RedSkull23 said:
It worked
Click to expand...
Click to collapse
Ooo !!! yeah--- finally :highfive:
sreekantt said:
Ooo !!! yeah--- finally :highfive:
Click to expand...
Click to collapse
After some tests, personally i don't advice to update it to V15.0 yet. Most is working fine by what i've saw, but i've noticed that on MiX it's not possible to modify some system files after updating. I presume that some error is still under-the-hood and even if the update went fine, there must be some lil' issue. In fact i restored the backup took before upgrading Magisk. I'll wait a bit before update it again
RedSkull23 said:
After some tests, personally i don't advice to update it to V15.0 yet. Most is working fine by what i've saw, but i've noticed that on MiX it's not possible to modify some system files after updating. I presume that some error is still under-the-hood and even if the update went fine, there must be some lil' issue. In fact i restored the backup took before upgrading Magisk. I'll wait a bit before update it again
Click to expand...
Click to collapse
Yeah ...may be regular early stage bugs...that explains viper npt working on many phones after v15...lets wait
I've a nice update for you and every EMUI user man; latest Magisk update, V15.1, solved the vendor issue and now it's everything good. I tested it, look here... no need to keep AVB2.0 ticked before updating, just direct install it through Magisk Manager and you're ready to go
RedSkull23 said:
I've a nice update for you and every EMUI user man; latest Magisk update, V15.1, solved the vendor issue and now it's everything good. I tested it, look here... no need to keep AVB2.0 ticked before updating, just direct install it through Magisk Manager and you're ready to go
Click to expand...
Click to collapse
TFS
did u update from v15 ??
btw- Hide u'r IMEI in 2nd pic
Edit - Updated from v15 to 15.1 successfully with AVB 2.0 unchecked and everything is intact as of now
Update- seems like updating from faulty v15 caused issues- Play store was not able to detect apps, not able to change boot animation etc
So i planned to clean install with Magisk 15.1 - uninstalled every trace and rebooted which caused NRD test keys build
Could be the issue caused by magisk modifying vendor partition and couldn't restore properly
Luckily, i had a complete TWRP backup - wiped everything(including cust, vendor, product) except internal storage > restored(including vendor, product)
flashed magisk 15.1 and everything working perfectly without any issue of modified vendor.
Update 2 - Damn EMUI- No sound
flash stock firmware > locked bootloader > unlock again > restore TWRP backup(only data, system, boot)- Vendor restore never worked for me
sreekantt said:
TFS
did u update from v15 ??
btw- Hide u'r IMEI in 2nd pic
Edit - Updated from v15 to 15.1 successfully with AVB 2.0 unchecked and everything is intact as of now ??
Click to expand...
Click to collapse
Whoops, didn't noticed the visible IMEI usually i remove it... thanks for the heads-up. I've updated by V14.5 anyway
I have trouble when update magisk to v15!
no sound at all!!
no mic...no camera, no call, no audio playing,no video playing!
I had a backup but when restored it...problem persist
what can I do!
plz help
GR5 2017 BLL-L21
Med Benarfa55 said:
I have trouble when update magisk to v15!
no sound at all!!
no mic...no camera, no call, no audio playing,no video playing!
I had a backup but when restored it...problem persist
what can I do!
plz help
GR5 2017 BLL-L21
Click to expand...
Click to collapse
Completely uninstall Magisk through Magisk Manager and reboot. Then flash your original boot.img from your build, reboot, reinstall Magisk Manager again and this time directly flash Magisk V15.1. It should work
RedSkull23 said:
Completely uninstall Magisk through Magisk Manager and reboot. Then flash your original boot.img from your build, reboot, reinstall Magisk Manager again and this time directly flash Magisk V15.1. It should work
Click to expand...
Click to collapse
how can i get the boot.img and how can i flash it???
Med Benarfa55 said:
how can i get the boot.img and how can i flash it???
Click to expand...
Click to collapse
The boot.img is backed up (I don't know the exact folder), then flash it using TWRP
Med Benarfa55 said:
how can i get the boot.img and how can i flash it???
Click to expand...
Click to collapse
To get and flash a clean boot.img, you need to:
1 read your build number from phone info
2 download the update.zip matching your build (BLL-L21C432Bxxx, for example) from Hwmt.ru site
3 extract the update.app from the zip file
4 using Huawei Update Extractor program on PC, open the update.app and extract from it the boot.img
5 flash the boot.img by fastboot typing "fastboot flash boot boot.img" (remember to completely uninstall Magisk before doing this, if not you'll face issues)
and that's all. After that, you can reflash Magisk V15.1 back through TWRP
PalakMi said:
The boot.img is backed up (I don't know the exact folder), then flash it using TWRP
Click to expand...
Click to collapse
Yeah it's backed up, but if it's backed up with a supersu app active on system, the su binary files would be already "dirty"... I flash a clean boot.img before every update because if not, the update verification on boot before update will fail, even if stock recovery is clean
So when backing up superSU or magisk, the boot.img is modified! Good to know
PalakMi said:
So when backing up superSU or magisk, the boot.img is modified! Good to know
Click to expand...
Click to collapse
Exactly! Discovered it by myself during updates :cyclops:
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.
Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part
You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!
Next time don't be a twrp and use twrp
dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update
Does anyone have experience with an unlocked HTC U11 Life and MicroG?
I went on a journey trying to get rid of whole Google stuff on this phone, replacing needed services with MicroG (want to use Maps and PlayStore for bought apps). I just wonder which steps have to be taken on the road since we don't have a custom recovery for HTC U11 Life...
I would recommend using this magisk module https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Should work fine if you are able to deactivate all google stuff and the system still works without it.
saturday_night said:
I would recommend using this magisk module https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Should work fine if you are able to deactivate all google stuff and the system still works without it.
Click to expand...
Click to collapse
I already gave it a try but sadly it needs TWRP to be flashed. Got errors on Magisk...
SHA_NDY said:
I already gave it a try but sadly it needs TWRP to be flashed. Got errors on Magisk...
Click to expand...
Click to collapse
In the early days of this module there was a way without twrp, you could take the official firmware file and extract the system.img, get it from your device or just download one from my collection to your pc. There was a patcher to use on a windows pc for this module especially for devices without twrp, i dont know if they stopped this patcher but it was official from the developer of the module. It patches the system to run this magisk module and you just need to flash the patched system to your device, activate the module in magisk and reboot the device.
saturday_night said:
In the early days of this module there was a way without twrp, you could take the official firmware file and extract the system.img, get it from your device or just download one from my collection to your pc. There was a patcher to use on a windows pc for this module especially for devices without twrp, i dont know if they stopped this patcher but it was official from the developer of the module. It patches the system to run this magisk module and you just need to flash the patched system to your device, activate the module in magisk and reboot the device.
Click to expand...
Click to collapse
Sounds nice, I'll give it a try I think. If I extract system.img from my phone and flash it back later will everything be as before? I mean apps and data and so on? Or will I have to restore a backup afterwards?
SHA_NDY said:
Sounds nice, I'll give it a try I think. If I extract system.img from my phone and flash it back later will everything be as before? I mean apps and data and so on? Or will I have to restore a backup afterwards?
Click to expand...
Click to collapse
I cant say something defenitiv. I experienced that i have to reset the device to boot after flashing a system.img but i also know that someone didnt need to reset his device. I think you have to try it, userdatas/apps are on a different partition anyhow so you dont delete them with flashing a system.img the only question is if the new flashed system will boot without a full wipe of the userdatas. But to have a backup is never wrong.
Sadly MicroG isn't available without TWRP, so bye bye! https://forum.xda-developers.com/showpost.php?p=78626349&postcount=5256
I installed the update like i normally did. Went into magisk and installed Magisk on the "After OTA" setting. Now it's boot looping. I'm NOT using TWRP. This is the first time this has happened. Normally I update the OTA, DONT RESET, install Magisk on OTA setting and reboot and it works fine. Anyway to fix this? It boots 90%, but once it gets to main screen RIGHT before it asks for my PIN, it goes to 'rebooting'. Do I need to wipe my phone and start over?
I'm not rooted but From my experience you have to delete modules folder in twrp
RISHI RAJ said:
I'm not rooted but From my experience you have to delete modules folder in twrp
Click to expand...
Click to collapse
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
whitak3r said:
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
Click to expand...
Click to collapse
Only disabling modules won't help,You have to delete the folder,Next time when you update
RISHI RAJ said:
Only disabling modules won't help,You have to delete the folder,Next time when you update
Click to expand...
Click to collapse
Thank you. I'll do that next time, would of saved me a bunch headache if I would of just read a little bit lol
I ended up cleaning my system and everything went back to stock root. So I updated magsik and magisk man. And it fixed everything. I'm in the processes of reinstalling all my stuff now though
For me, there is only one module causing problems - the OOS call recorder enabler.
I simply remove that module and reboot before starting the OTA and all was fine.
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Is this a bug of Magisk?
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
Hi, can you use this command on adb shell? OnePlus 7T Pro doesn't have TWRP yet. Thanks.
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
This. But the module clearly says REMOVE before attempting upgrade!
And like I suppose most people here - I also did not follow that instruction and ended up with a bootloop. lmao. :good:
If you have TWRP you can remove modules if you have a bootloop.