Seriously Needing Help
Phone Info - Mi A1
Rom - Resurrection Remix v6.XX OS-8.1.0 November Patch
Magisk v18 stable (used successfully 2 days after updating Magisk from v16 stable with no problem anywhere).
Modules - v4a, aml, dolby, selinux changer, busybox, MiA1 stock cam.
While updating "AML", screen got freezed for more than 5 min so i had to shutdown forcefully. But after restart i lost all installed apps and everything., from everything i mean both internal and external got formated. But that's not only the case. My device Mi A1 keep restarting automatically after few min of starting (it's not bootloop as device restarts to homescreen but freezes and restarts after few sec.). Sorry that i can't provide logcat as everything already formated.
i tried to reflashing using few unofficial and official MI tool (tried both oreo stock and pie latest) but still my device goes to setup screen and after few seconds it restarts automatically.
Isn't there any work around 'coz neither magisk support forum helped nor AML forum.
My only question is whether is this software issue or hardware? Can updating simple module result in hardware failure?
Please reply.
Related
Hey everyone.
Like many Android users, I've been struggling to find a ROM and systemless root combo that passes SafetyNet (ever since Pokemon GO 0.37 update). I eventually found a ROM that can be unrooted cleanly (AryaMod S7 Edge port), and managed to get SafetyNet working via Phh's Superuser (first with Magisk + r251, now using hidesu version r266).
However, I soon ran into a problem: The systemless root appears to be causing my phone to bootloop. There seems to be a gradual degradation of the bootimage somehow caused by systemless roots; my phone would work fine for a while, then gradually apps would force close or the phone would freeze. If I try to reboot, the phone then gets stuck in a boot loop (which occurs before the ROM even starts loading). I am very sure this is caused by an error in the bootloader because this bootloop behavior persists through nandroid restore or clean ROM installations. The only way to fix it is to flash the stock bootloader via ODIN.
I noticed a few users in the dev threads of ROM's I've tried reporting the same issue, but in the dev thread for Phh's Superuser there seems to be a lack of mention of this issue (likely model-specific, as I am using Phh's Superuser on my wife's Note 4 and her phone isn't bootlooping). Just wondering if anyone has experienced the same problem and found a solution?
Try the TMobile forum .
Sent from my SM-N930F using XDA-Developers mobile app
I also have an N900T, and magisk v7 + phh is working fine for me if I don't install any extra systemless modules. When I installed the better battery stats module, I started getting bootloops, so there are definitely some issues with it.
Magisk is still being worked on, so it's probably only at alpha or beta status right now. Hopefully it will get more stable in the future.
btw.. I'm running the latest stock Samsung 5.0 rom (N900TUVSFPH3), which has the latest bootloader, since it seems the most stable to me.
Hi,
I have problems with a Nexus 10 (Lineage OS 13, latest nightly, rooted with SuperSu 2.82 and Nova Prime). Worked fine till now. Then reboots when I want to unlock with gesture. Did a factors reset, worked for about a day. Then reboots again by unlocking.
I saw that when the problems started, on the lockscreen was only the return button visible, I missed the Home- and Taskbutton.
I started in safe mode, uninstalled Nova and everything workes fine now.
If any further Information is needed I will try to give them.
Greetings
P.S. Did a posting in reddit also: https://www.reddit.com/r/NovaLauncher/comments/6z8lmy/bug_nova_crashed_phone_bootloop/
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Happened to me too. Got rid of magisk for now so running stock un rooted until this gets sorted. Haven't ran into the issue since un rooting.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Rowdyy Ronnie said:
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Click to expand...
Click to collapse
I flashed 16.0 too, but I have to say the issue became real even before I installed Xposed. Guess it's something Magisk-related
Try older Magisk, for example 15.3.
Same to me. Just reboot and it´s fine.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Same. I don't have Xposed or other mods, so I think it's a Magisk's issue.
Made over 20 reboots in order to find the"right" combination of substratum themes the last two days.only 2-3 times i had stucked in reboot. I have magisk, xposed ,gravitybox .
Huh, I get this sometimes too. So it's Magisk v16 you say?
TrueMS said:
Try older Magisk, for example 15.3.
Click to expand...
Click to collapse
Good idea, will give that a go. I don't use any modules anyway, only use it for Safetynet-friendly root.
Same problem here.
I Will follow the topic.
Double post, Sorry!
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
laugeek57 said:
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
Click to expand...
Click to collapse
Currently testing 16.4b and no boot issues atm!
Must have been topjohnwu's boot operations code change.
Thank you really much
I don't know what is wrong with my phone, I've searched the web for answers only to find nothing, I've asked in other threads and got no answers, I need help. So basically my issue is Magisk on my Mi A1 this issue happens with both 16.0 and 16.4, on the stock Mi A1 rom occasionally when I reboot my baseband and IMEI is unknown and when I reboot it fixes it's self temporarily I know this is not an issue with EFS partition as when I uninstall Magisk everything is fine and on custom ROMs I don't get this issue but a whole other different one. Also on the stock ROM Magisk causes bootloops sometimes which is fixed by rebooting.
When I use Magisk on a custom ROM I get a different issue, whenever I use Magisk to do anything on my device it causes an issue where sometimes when I power off my device it shows the boot animation before powering off.
I'm really sick and tired of these issues and any help would be really appreciated.
I have the same issue with the no imei/baseband in stockrom with magisk
created a thread like you asking for a solution, got not answers, not sure if is because not enough people mod this device or is something else
I for once as soon as I got it, unlocked bootloader and installed magisk and xposed, everything else is stock
issue still persist, you need to reboot again for imei/baseband to comeback
Sent from my Nexus 6 using Tapatalk
CrazyAndroidModder said:
I don't know what is wrong with my phone, I've searched the web for answers only to find nothing, I've asked in other threads and got no answers, I need help. So basically my issue is Magisk on my Mi A1 this issue happens with both 16.0 and 16.4, on the stock Mi A1 rom occasionally when I reboot my baseband and IMEI is unknown and when I reboot it fixes it's self temporarily I know this is not an issue with EFS partition as when I uninstall Magisk everything is fine and on custom ROMs I don't get this issue but a whole other different one. Also on the stock ROM Magisk causes bootloops sometimes which is fixed by rebooting.
When I use Magisk on a custom ROM I get a different issue, whenever I use Magisk to do anything on my device it causes an issue where sometimes when I power off my device it shows the boot animation before powering off.
I'm really sick and tired of these issues and any help would be really appreciated.
Click to expand...
Click to collapse
If you want people to help you, you need to give more details. A logcat maybe.
Rowdyy Ronnie said:
If you want people to help you, you need to give more details. A logcat maybe.
Click to expand...
Click to collapse
I'm currently running a custom rom and I've discovered that the issue I'm facing there has nothing to do with Magisk, its when I open an app like Titanium backup, even unrooted the app want root permissions causes the boot animation at power off, anyway I'll make a logcat when I get chance.
Any Custom ROM without "no audio during call" bug in Asus Max Pro M1(3GB Ram variant)
Story: Installed LineageOS 4 months back, Had a good working mobile with latest build, & then I tried RR & AEX,
Resurrection OS & AEX latest builds had same "no audio during call" problem
Tried to restore but , facing the same problem in LineageOS too, I checked by installing all the available builds on website.
I checked speakers & mic via whatsapp call ,they working fine
Resurrection OS older builds (7.0.0s) don't have this problem but still they have lots of bugs & crash a lot.
I tried "build.prop" method didn't worked because there were no lines to change.
I tried installing "dolby plus oero patch" it wasn't getting installed via TWRP.
So basically this critical bug exists in every rom I'm trying. U know any rom which doesn't has this problem,
& I was thinking if anyone saved a twrp backup of most perfectly running device online for rescuing other devices later,
hi,
please see this thread
https://forum.xda-developers.com/asus-zenfone-max-pro-m1/help/call-sound-oreo-rom-t3848196
flash DoblyPlus with magisk not twrp.
after that you can restore to stock official roms for permanent fix audio without dobly