Recently, I flashed Magisk v14.0 onto my SM-G920F (galaxy s6), but I found that my root access was constantly disappearing after 3 minutes of use. After 2 weeks of frustration, I decided to try the last stable version of Magisk with my phone, which happened to be v13.3. So the way to keep your device rooted over long periods of time (3 minutes +) are:
1. Make a nandroid backup, because eventhough this isn't really risky at all (although I take no responsibility for any damage to a device), I have learnt the hard way its always nice to have one just in case.
2. Flash the uninstall zip in twrp (or any other custom recovery), which can be found on the original Magisk page right at the bottom of the first post
3. Flash Magisk v13.3, which can also be found on the same page as the uninstaller.
4. Reboot your phone and open any root checker (or root app). This will then re-activate Magisk Manager.
I hope that in the next update of Magisk, this issue is solved as it seems to be device specific
Really ? Which rom you were on? I'm using this device for a year and neither on stock nor on any of the custom rom i got this kinda of issue.
If you use the Magisk Beta 14.3, it shouldn't unroot itself anymore. I installed it a couple days ago and I haven't lost my root since. I had to reboot my phone several times a day before hand.
Just switch your update channel from Stable to Beta in the app.
Having the same issue on Samsung Galaxy Tab A and Magisk 16.0.... Guess I'll see what Beta is doing but if that doesn't work I'll go back to SuperSU because it's just too frustrating.
Related
Hi,
I recepty run into a problem that I can not fix by myself.
My galaxy s7 started to overheat (it overheats during normal usage, browsing Web etc.)
1. I was using the phone rooted with CF autoroot without a problem for a month or so
2. I installed TRWP and then Xposed framework (all the correct files following guides from this forum) and it worked all OK.
3. 2 days after the above installation I decided to make a fresh clean install of ROM. I found a new updated ROM (June update) of the stock XEO ROM that I was using.
I made a data reset and factory reset with TRWP (wiping all) and then flashed the new ROM with Odin.
I rooted it and installed xposed.
4. Phone started to overheat during normal usage.
5. I tried to flash the new ROM without installing xposed, then trying flashing ROM without even rooting it later. I finally even flashed the "old" ROM from before the June update, with no rooting or touching anything, and it still overheats.
The clues I found as far:
1) i read somewhere that xposed can cause overheat like I described but I don't understand how it could be after I wiped de device so many times and running stock unmodified rom?
2) i read somewhere that there is some Google account backup bug that makes devices overheat which seems to be connected with the 3rd point
3) it seems that Android System battery usage is higher than normal
4) the device overheat mostly on the right middle part of the phone, along the right edge of the phone a little below the power button.
5) i don't belive it's user app related because the problem exist even after fresh install of rom without additional apps installed
I would really need some advice, because I ran out of ideas what to do.
Hello, our situation is similar... I've googled the issue and I've found no solution. My overheating problems started after I installed Xposed framework. Few minutes before, I rooted my phone with Odin and installed TWRP. After I used a module on Xposed, my phone began overheating on the right part of my phone below the power button as you described. I immediately uninstalled Xposed.... nothing worked, flashed my phone back to the stock rom....still the same. IF EVER FIND A SOLUTION, PLEASE SHARE IT WITH ME... I'M SO WORRIED. THANKS.
Possibly a long shot, but I would be opening the occulus app and seeing if it needs to update.
That issue was causing a bunch of phones to overheat last week. Solved by opening the app and letting it update.
Sent from my SM-G935F using XDA-Developers mobile app
I upgraded my Note 4 (SM-N910C) to Android 6.0.1 earlier this year and it's been rooted ever since.
Most recently I was using the Chainfire's systemless root with SuperUserSU and SUhide.
However, when attempting to use toggle root 2 days ago I was given a "No Super User Binary installed" message.
So it seems my device unrooted itself somehow and I've been pulling my hair out ever since trying to re-root it.
Since then I've tried re-flashing SuperUserSU, tried Magisk which had worked in the past and finally tried CF-autoroot.
I've even gone so far as to re-flash my original stock rom, wipe the device and start over with no luck.
I'm 7 hours in today and out of ideas. My Note 4 has not only rid itself of root, but become immune to root.
Firmware Auto-update is off. The only idea I've had is that the device HAS reset while root was toggled off, and I hear this can cause you to lose root. But surely everything I've done should have fixed that.
If anyone has and idea's I'd HIGHLY appreciate the help.
I was interested in trying out Xposed and installed the sdk23 for Marshmallow from the Magisk app. Though, I entirely missed the fine print on the many internet articles that Samsung devices need more care in installation, and promptly got stuck on the Samsung logo during boot.
The first of my problems is that none of the Xposed Framework Uninstallers I tried seemed to work. I tried the three different versions released on 20150831 and the version released on 20160211, but none of them seemed to take. I did get past the logo during boot when I flashed the stock ROM onto my device, and got root back with SuperSU, but it looks like I can no longer flash Magisk without something going wrong - either failing outright when installing through the Magisk app, or getting stuck on the Samsung logo again after flashing with TWRP. (Also tried the Xposed Uninstaller versions available to me in the Xposed installer app, the ones under the Systemless and Samsung tabs, and none of them seemed to have any effect either.)
I assume that a factory reset will solve my problems, but before that, are there any less drastic measures I could try first?
AKAAkira said:
I was interested in trying out Xposed and installed the sdk23 for Marshmallow from the Magisk app. Though, I entirely missed the fine print on the many internet articles that Samsung devices need more care in installation, and promptly got stuck on the Samsung logo during boot.
The first of my problems is that none of the Xposed Framework Uninstallers I tried seemed to work. I tried the three different versions released on 20150831 and the version released on 20160211, but none of them seemed to take. I did get past the logo during boot when I flashed the stock ROM onto my device, and got root back with SuperSU, but it looks like I can no longer flash Magisk without something going wrong - either failing outright when installing through the Magisk app, or getting stuck on the Samsung logo again after flashing with TWRP. (Also tried the Xposed Uninstaller versions available to me in the Xposed installer app, the ones under the Systemless and Samsung tabs, and none of them seemed to have any effect either.)
I assume that a factory reset will solve my problems, but before that, are there any less drastic measures I could try first?
Click to expand...
Click to collapse
I had a similar problem and had to reflash with original with original files ......... the file i had to use is named J120WVLU2AQJ3_J120WOYA2AQJ3_J120WVLU2AQJ3_HOME.tar.md5
I will try to add to my drop box and send you a link if it will help?
Please take into consideration i am fairly new to this and am not sure if this will solve your problem but it worked well on my phone same model SM-120w. Hope this helped out!
J120WVLU2AQJ3_J120WOYA2AQJ3_RWC.zip
Odin3-v3.12.7.zip
Hello everyone
It has been a while since I last started anything here.
I have had a few problems with my galaxy note 3, it freezes, sensors go crazy from time to time, things like that, but most of them I have been able to resolve or work around.
Now I have a new one that I was not able to resolve despite going for the last resort fixes. I have a galaxy gear 2 (not s2, just 2) that has this media control app. After using it, I found out that the app stops working a few hours after the device boots up. Right now all I know is this:
1. Everything works fine once system had a few minutes to load after start.
2. After unknown amount of time, the phone stops responding to gear, bluetooth headphones and cord headphones media control attempts.
3. Bug persisted after I flashed a new ROM and then rooted and used TWRP to get back my data partition (nothing else). Than I wiped cache and dalvik and booted up.
4. Currently trying to do the same but without rooting to see if that helps.
My phone before any attempts:
SM-N9005
4.4.2 Kitkat root stock ROM
TWRP
Ultimate kernel
Xposed framework (a few youtube modules xtorch and wanam)
I would appreciate any advice you have for me. I will update this if not rooting fixes the issue. If it does not I will root and reinstall xposed and others
UPDATE: Even no root no xposed system did not help. Flashing back my TWRP backup.
Wipe phone flash stock rom and test first .
I probably will, just not right now, it takes quite a long time to get phone into working order after a flash with no backup. Also if it helped I would have to wipe my gear too because of how pairing system works...
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.