Database Info

On stock 4.4, 4.4.2 install fails every time, on about 20-30%

I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.

did you install any mods, kernels, change any files? if so its been documented all over the forums.

No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.

danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?

Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).

danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.

wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.

danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?

Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data

try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.

EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.

Never had an issue myself, but I always prefer to flash each image manually one at a time

EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.

wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?

danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb

jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.

danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something

jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?

danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?

jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.

'Root binaries' missing after rooting with guide on XDA forums

I'm having issues with my OPO root. I unlocked my bootloader, flashed TWRP and rooted by installing SuperSU through a zip. All was good and root was working yesterday.
I haven't done any Android updates, but my root is gone! If I open the SuperSU app it does this (see screenshot in attachments)
I tried reflashing the zip through TWRP but the same happens after rebooting.
Any ideas?

Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...

oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Reinstall busybox.
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Sent from N5 or OPO

oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Why on earth did you uninstall Busybox in the first place?
Sent from my Evita

Same problem here.
My OpO was rooted and after uninstalling busybox i have the same issue.
Superuser says no su binaries
i tried flashing again an again. Flash works fine but always the same message no su binaries ..
Busybox was stuck on loading data, that's why i uninstall it .

Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.

wacky.ddw said:
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
Click to expand...
Click to collapse
Don't restore system data when switching ROMs.
Sent via Bacon

timmaaa said:
Don't restore system data when switching ROMs.
Sent via Bacon
Click to expand...
Click to collapse
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.

You guys are totally out of a clue.
First: why do you uninstall busybox? Read twice, flash once. If you knew what busybox is for you probably would avoid such errors. Don't tweak your devices if you're not savvy of what you're doing or xda forum will always be cluttered by such threads.
Second: System options backed up can screw up your phone if they do not apply to the ROM just installed causing various problems if not bootloops. DO NOT RESTORE EM. NO WAY.
Hope this helps.
PS: Install busybox from play store to solve the issue.

wacky.ddw said:
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
Click to expand...
Click to collapse
Read what you just wrote and tell me again that you don't want to restore system data.
Sent via Bacon

DuckMcQUack said:
PS: Install busybox from play store to solve the issue.
Click to expand...
Click to collapse
It don't works, install ok but Busybox crash when i open it

ahytes said:
It don't works, install ok but Busybox crash when i open it
Click to expand...
Click to collapse
Personally i would just clean flash again from the start...
Inviato dal mio One utilizzando Tapatalk

Hi, I have the same problem.
I tried to reflash SuperSU, but not working.
BusyBox was uninstalled from my pocket :crying:
What should I do ?

See post right above yours.
Transmitted via Bacon

Sorry.
But I only flashed the zip version of BusyBox, and it work now.

Brigitte-Bedo said:
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Click to expand...
Click to collapse
I have this same problem as OP. Ok well since the app keeps crashing on startup, flashing a zip seems like a good idea. Where did you find this zip file?

Same Problem
I lrooted my opo and flashed Sabermods Cm Lollipop and am also getting the same notification, any root needed apps are telling me the phone isnt rooted?? I also tried installing this busybox but wont work cause the phone is coming up as unrooted?
Has anyone a straight answer for this dilemma that doesnt include a full wipe/flash rom again...?

http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
mindblizzard said:
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
Click to expand...
Click to collapse
Had this problem to, try to uninstall supersu etc. Flash latest su and problem fixed, im on slimLP rom

Ok, I can't seem to get back root either. I had root and was running ParanoidAndroid. I wiped clean, flashed Cyanogen 12 nightly, flashed Gapps, wiped cache/dalvik. Everything rebooted into Lollipop fine, but I've lost root and can't seem to figure out how to re-root. I flashed the most recent SuperSU (2.46) via TWRP with no luck. Keeps saying I need to re-root first. Any ideas?

bricked, need help

it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx

nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do

Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)

Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot

Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try

Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.

U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101

Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?

Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs

Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand

Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device

You both are awesome ???

Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me

JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.

I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while

JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files

venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?

JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.

Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro

Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.

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

Will we get an OneUI compatible TWRP and/or kernel? Also what can be causing this?

So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)

VDavid003 said:
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
Click to expand...
Click to collapse
Good thing you skip the bootloader and modem.
Are developer who had done kernel and twrp has disappeared.
You can try to send him a pm.
Their are universal twrp that you could try.
What twrp are you using mean build?

mchlbenner said:
What twrp are you using mean build?
Click to expand...
Click to collapse
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...

VDavid003 said:
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
Click to expand...
Click to collapse
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.

Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?

VDavid003 said:
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
Click to expand...
Click to collapse
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.

mchlbenner said:
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
Click to expand...
Click to collapse
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.

VDavid003 said:
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
Click to expand...
Click to collapse
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.

mchlbenner said:
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Click to expand...
Click to collapse
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:

mchlbenner said:
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
Click to expand...
Click to collapse
Didn't see you replied. I'll try that - flashing oreo and restoring backup.

VDavid003 said:
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
Click to expand...
Click to collapse
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.

mchlbenner said:
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
Click to expand...
Click to collapse
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.

So it didn't fix the bootloops, but at least TWRP works now!

VDavid003 said:
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
Click to expand...
Click to collapse
No reformat it will whiipe everything mean your downloaded apps

I was able to install TWRP and root with Magisk when the pie update was uploaded on this forum.
---------- Post added at 01:25 PM ---------- Previous post was at 01:24 PM ----------
And yes you need to erase everything

Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)

VDavid003 said:
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
Click to expand...
Click to collapse
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.

mindlery said:
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
Click to expand...
Click to collapse
Lol
Well, it's good to see it's not me being stupid or my phone being broken

Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.

VDavid003 said:
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
Click to expand...
Click to collapse
Their where no freezing or issues on Oreo.
Android pie was released and it would freeze at boot and watching videos.