Deleting the Mi Feedback App - Xiaomi Mi A1 Guides, News, & Discussion

I'm on Mi A1 Oreo with January patch. I recently rooted it with Magisk. Everything is fine, except for the Mi Feedback app. It is sending a hell lot of data to Xiaomi. So, shall I uninstall it? If I did, will my phone bootloop? I'm asking this because it's a system app which cannot be force stopped.

guy_infinity said:
I'm on Mi A1 Oreo with January patch. I recently rooted it with Magisk. Everything is fine, except for the Mi Feedback app. It is sending a hell lot of data to Xiaomi. So, shall I uninstall it? If I did, will my phone bootloop? I'm asking this because it's a system app which cannot be force stopped.
Click to expand...
Click to collapse
Yes you can..

guy_infinity said:
I'm on Mi A1 Oreo with January patch. I recently rooted it with Magisk. Everything is fine, except for the Mi Feedback app. It is sending a hell lot of data to Xiaomi. So, shall I uninstall it? If I did, will my phone bootloop? I'm asking this because it's a system app which cannot be force stopped.
Click to expand...
Click to collapse
OFF TOPIC: Can you please guide me on how you rooted Oreo (Assuming you're running Stable build OPR1.170623.026.8.1.10)? I tried booting the patched image but it failed.

KalolParty said:
OFF TOPIC: Can you please guide me on how you rooted Oreo (Assuming you're running Stable build OPR1.170623.026.8.1.10)? I tried booting the patched image but it failed.
Click to expand...
Click to collapse
Worked for me. I did the same thing.

KalolParty said:
OFF TOPIC: Can you please guide me on how you rooted Oreo (Assuming you're running Stable build OPR1.170623.026.8.1.10)? I tried booting the patched image but it failed.
Click to expand...
Click to collapse
Short way:
Clean rom install, boot the phone, install latest magisk apk,
open magisk, press install, create patch_boot.img.
Push patched_boot.img to your fastboot folder on your PC.
Phone to fastboot mode, cmd on PC and fastboot boot patched_boot.img and you're done.
If you want to use twrp and don't care about ota ( like me )
read this thread and just flash latest magisk.zip with twrp
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472

How are you able to remove feedback app without root?

pow01 said:
How are you able to remove feedback app without root?
Click to expand...
Click to collapse
Root needed.

pow01 said:
How are you able to remove feedback app without root?
Click to expand...
Click to collapse
If you don't want root, just flash twrp recovery, mount system,
use the twrpfilemanager to delete the apps of your choice,
flash back stock boot.img to get back to stock recovery.
Root is not needed, if you got a problem with it.

But uninstalling it will disable OTA, right?

guy_infinity said:
But uninstalling it will disable OTA, right?
Click to expand...
Click to collapse
How about only freezing the app?

matcho13579 said:
How about only freezing the app?
Click to expand...
Click to collapse
Paid tibu should work

Thanks. Worked ?

What is this tibu?

debuti said:
What is this tibu?
Click to expand...
Click to collapse
Titanium backup , you find it at the playstore.
You can delete or freeze mi feedback and Google feedback too.

matcho13579 said:
How about only freezing the app?
Click to expand...
Click to collapse
If your device is rooted (Magisk), check my thread here for systemless debloating:
http://en.miui.com/forum.php?mod=viewthread&tid=1780147&extra=

Related

magisk

Anyone uses magisk ? Is it worth??
cline2 said:
Anyone uses magisk ? Is it worth??
Click to expand...
Click to collapse
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
Ok. Too much pain to do. I will stay with SuperSU
ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
What are you rooted with now? And what build is your firmware?
ante0 said:
What are you rooted with now? And what build is your firmware?
Click to expand...
Click to collapse
I'm rooted with phh, and I'm on L29-567-190. Thanks a ton for the help.
McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
If you want to root with magisk, just flash the zip and you are done.
Powerlated said:
If you want to root with magisk, just flash the zip and you are done.
Click to expand...
Click to collapse
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
McRoberts said:
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
Click to expand...
Click to collapse
You need to be on recovery 3.0.1-1
albertobom said:
You need to be on recovery 3.0.1-1
Click to expand...
Click to collapse
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
ante0 said:
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
Click to expand...
Click to collapse
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
McRoberts said:
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
Click to expand...
Click to collapse
You need to be on firmware B182+ (which you are)
You need to have twrp 3.1.0+
You need to flash stock boot image before Magisk.
You can get stock boot either from rom zip (boot.img) or stock firmware (update.app) and extract boot using Huawei Update extractor. Then flash boot image manually.

How to Root J7 Prime (G610F) on Nougat?!

Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.
vishnurmcf said:
Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.
Click to expand...
Click to collapse
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.
anubhab723 said:
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.
Click to expand...
Click to collapse
man i need a working root i... tried by twrp by install the root latest version so now i am flashing a stock firmware hhhhhh ....will magist work 100 percent ?? i need the full confidence answer thanks a lot
lI also just updated, I tried using CF Auto Root but that didn't work and made my phone bricked (verification failed). Will Magisk work certainly because I don't want to have to reset again.
Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Sent from my SM-G955U using XDA-Developers Legacy app
fast69mopar said:
Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Click to expand...
Click to collapse
Will try that. Thanks!
wsty said:
Will try that. Thanks!
Click to expand...
Click to collapse
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask
fast69mopar said:
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask
Click to expand...
Click to collapse
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?
wsty said:
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?
Click to expand...
Click to collapse
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Before you flash any root zip in TWRP, make a backup of your stock boot image. That was ifsomething goes wrong you can revert back and try again with a different version if Magisk.
Make sure you read the info that @topjonwu has made available for us for Magisk. The link below is full of information pertaining to Magisk.
There is one other thing that I forgot to put here. Magisk is a pretty universal root solution that patches the boot image just like Chainfire's SuperSU. There is not a device specific Magisk zip so you can flash any version if Magisk to attempt to gain root access in your device. Like I said before, I would start with flashing V12.0 and start from there. If V12.0 works and you have root, boot to TWRP and make a backup of your boot image to save it. That was if you flash, for instance, V13.0 and it doesn't work or fails to flash then you can boot back to recovery and restore your boot image and have working root.
fast69mopar said:
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks!
wsty said:
Thanks!
Click to expand...
Click to collapse
No problem
Any working Twrp for this?
Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...
denizbay said:
Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...
Click to expand...
Click to collapse
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app
Looking this: https://forum.xda-developers.com/ga...ared-root-file-j7-prime-g610f-nougat-t3678253
inamie said:
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app
inamie said:
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
What Magisk version, Version 14 tripped the verification error on my 610M
Try Magisk v14.0
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-sys
FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.
vishnurmcf said:
FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.
Click to expand...
Click to collapse
Looking forward to your instructions. Please release soon! Thank you!

Can't flash anything in 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.

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

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

Warning - Notchbarkiller Magisk Module!

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

Categories

Resources