A few weeks ago, my hidden Magisk Manager (hidden as "Settings") stopped working. When I try and launch the generic Settings app it sets up, I get the normal FC menu ("Settings keeps stopping") error. I also get it when I open up any app that I previously allowed root access to, but obviously I cannot add new apps superuser access. I also get the FC every time I reboot the phone.
I haven't updated my OnePlus 9 Pro since the ColorOS 12 update came out, as 1) was not a fan, and 2) everything I read said I'd need to wipe the phone to get root back. Needless to say, it's been a while. My phone is currently on the 11.2.10.10.LE15AA version.
This just started happening one day, but I have no idea why. I am not sure what version of Magisk I am on, because I can't open the app. I also tried downloading the latest and installing the APK, but when I launch it, it's says things need to be "fixed" and to reboot. I then get the choice the normal Magisk installer brings up. I tried doing a direct install, but it failed. I also tried to restore the boot image, but it said the backup wasn't found (never seen that either, as I restore images every time I do an OTA).
Not sure what to do at this point. I'm at a complete loss. I would appreciate any help you guys can provide!
Do a LOGCAT to get the very reason why Magisk is not working.
I tried to get it as quickly as possible to minimize clutter, but it's still pretty long. I believe I've found where in the log the FC I captured (by looking for "zygote", but not sure what to make of it. It sounds like a file or something is missing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't seem like the logcat file got attached.
Oh well, here's a link:
FilePost
filepost.io
Related
So.. it all started with google services framework.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It kept crashing every 30 seconds. I tried to clean cache, clean data, force stop, reboot phone, remove google account in "Accounts & Sync", everything you can find on the internet (except for an actual solution, which i still didn't find). I thought re-installing it would help. I found an apk for Android 2.3.4, and installed it. I rebooted the phone. I had the same problem with play store a couple of months earlier, and I thought it would be the same.
Android didn't boot after that. Tried removing battery, rebooting phone, nothing. Had to do a factory reset. Once the phone booted (after factory reset) i got to the part where I get a green android with a message "Touch the android to begin"
I tried factory reset a couple of times, with and without sd and sim cards, no luck. Tried tapping the corners, but nothing. Found some other **** online, same result.
Why did you try to install an OS using an apk? It sounds like what you should have done was reflashed GAPPS which should have overridden the framework you were having a problem with and solved the problem. If your phone is not rooted, the only way you can fix it is to boot into recovery and reset from there. If you do have a rooted phone, it'll probably be easier to go into CWM and reflash your ROM.
syung said:
Why did you try to install an OS using an apk? It sounds like what you should have done was reflashed GAPPS which should have overridden the framework you were having a problem with and solved the problem. If your phone is not rooted, the only way you can fix it is to boot into recovery and reset from there. If you do have a rooted phone, it'll probably be easier to go into CWM and reflash your ROM.
Click to expand...
Click to collapse
i agree wid u syung...
Sent from my Canvas 2 using xda premium
Hey guys,
Big thanks to @autoprime for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.
If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.
If System Update is constantly bugging you to update, follow the directions below:
1) Enable USB Debugging
-Go to About phone and tap on Build number 10 times to enable Dev Options
-Enter Developer Options and enable USB Debugging
2) Download and Install the Debloater tool (this happens on your computer)
-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe
-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg
3) Connect your phone via USB. Make sure to install any drivers needed
4) Watch for pop up requesting ADB Access on your phone
5) Launch the Debloater tool
6) Select OK on the popup
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) Click the top left button
8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top
Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
I just got the G4 yesterday. I didn't do my homework first and did the updates. Am I screwed when it comes time to root? (If ever)
Delete
I just went into Settings/Apps/Google Services Framework and unselected Show Notifications. This took the warning out of the Notification Bar.
Not certain yet in the event that it will keep the popup for the framework OTA overhaul.
Deleted
I saw on a website that there were other things listed in addition to what you blocked to avoid OTA updates. Should these be taken into consideration?
LGUpdateCenter.apk
LGFOTA.apk
LGLDB.apk
EDIT: I used that debloater tool and disabled that stuff. I've had no problems with the phone after that except for the AT&T bloatware.
Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but after flash super user zip phone stop work at bootloader warning
same thing happen to me too..plz someone answer.
Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.
mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte
Love you!!!
You pacified my pain.
Hello guys,
I'm new here, I've read a lot about your different topics and I'm admirative for some level god members with their answers :good: :laugh:
Indeed I'm a dev, but for websites so it's a bit different with phones for me, and I will try to explain as detailed as I can.
I have a samsung SM G965F, bought in Poland (I work here for the moment); And indeed tried to root it for private purposes.
I followed a tutorial; I was on Pie 9 (****tiest ever update for me); from there OEM in DEV tools was activated, and the TWRP was installed.
the phone wasn't root, but I had the TWRP options (when push Volume up+bixby+lock) so thought I'm on the good way, but only after, and there is my mistake, I understood by reading something that I should make faster an operation when enabled the OEM (before it start to delete all my infos) that I should switch to recovery mode (or installation) and if not there was a story with 7 days to wait.
So the phone was just reseted with only memory card datas not deleted, and the phone was working, just the OEM always disabled, and when you select to enable it it says "ok we reboot the phone you will loose all your files etcc..." and anyway after many attempts, it says always the same after the reboots, and never is enabled after. So I tried to install a new rom, and then I thought I had a problem, in the installation it was written "Secure Check Fail : PIT".
So I tried to found the right rom, with the number "6" inside as per this screen :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the Secure Check Fail : PIT dissapeared and now its just Fail in Odin.
Also, I tried to reboot normally but it says that there was an error and I need to reinstall with smart view or smart touch, I don't really remember, so I just reinstalled the first TWRP and now the screen of my phone is looping on Samsung, and rebooting.
I'm lost, I spent from 3pm to 4 am yesterday in the internet to found a solution, so my final option is write to ask your help guys.
Hope you can help me, thank you in advance
PS: Sorry for the big picture, there is no acceptance unfortunately for resizing codes, or maybe I just still don't have access to this option cuz I have less than 10 messages, if need delete it or explain me if you need pictures, I did it 10 min ago, even if there is not a lot to do because i'm limited with my phone now
Hello,
I have a rooted EU phone (4a, not the 5g version). The OTA updater does not find the security updates, and all the rooting guides seem to indicate that they should show.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can I check what's going on?
Long, more detailed version:
I have rooted my Pixel 4a (using Magisk). I think I have done things right¹, but my phone seems to be unable to find the November security update. I thought it was just a lag in the rollout of the update, but I got a message warning me that "it has been two weeks and I haven't installed the update yet".
When I go to Settings → System → Advanced → System update, it tells me my system is up to date, with Android 11 and the security update from the 5th October 2020.
I have tried removing Magisk to no avail, the update still does not show.
Does anybody know what's happening, or what I am missing?
¹ For what it's worth, the flashed version of the OS is sunfish-rp1a.201005.006 (using the flash-all.sh, then I have flashed the bootloader that came with it, patched with Magisk Manager beforehand).
You will need to flash back the stock boot.img and then search for updates, as if you mess with that (you did by rooting) you wont get OTA updates.
Thanks. I'll try that once I've figured how to do a full system backup.
You could simply sidleload the ota since you know it's there
Beware u will need to repatch your boot.img to have root again after applying the dec ota update.
I just tried sideloading the december OTA update (201205.008). It seemed sucessful from adb, but got stuck on the boot animation for a few minutes, and I ended up force-rebooting the phone. When the operating system started, I was still on 201005.006.
To be completely honest, I'm far too unfamiliar with the Android flashing and boot process to be confident in anything I'm doing here. I'm fairly comfortable with Linux and its boot process, but Android albeit similar is too different. I need to read up on that.