I have rarely had any bootloop on my previous devices, so I'm not sure if this even counts as bootloop:
An hour ago I found my Pixel 2 (stock 8.1, Magisk 14.5 unmodified, TWRP 3.1.1) restarted itself (with the internal error message it's hard to miss). So I hit OK and enter the pattern to unlock. Upon unlock it reboots and arrives at lock screen again. Another unlock would trigger another reboot, over and over.
Luckily, I had Magisk uninstaller stored on SD card so I went in recovery to flash that, which seems to have restored the backed up boot image, and the phone is properly functional again. Then I flashed Magisk and it's all fine now.
I'm not attributing this issue to Magisk but just wonder if anyone else has seen this issue before. With lock screen being properly loaded, I'm not sure if this even counts as a bootloop.
Another factor to consider is, about two hours before all this happened, I installed AdAway to modify the host file. Don't know if that could be the reason, but now I've modified the host file again, will see if this issue comes back.
I just started having the same problem about the same time. I did a complete shutdown from the lock screen and when it fully booted, it was fine overnight, but it started acting up again this morning, so I did a complete shutdown again. It hung on the shutdown screen, so I had to do the hard reboot. Doing fine again, for now. I also have Magisk and AdAway, but I'd had both of those active for a few days before this started up.
I has something similar but different happen. After updating to 8.1 with magisk, I updated my hosts with adaway. I then had it hang on shutdown (this was the first time this had happened). Hard reset and rebooted and everything seemed to be fine. I then put it on the charger overnight, only to wake up the next morning and find it in the recovery menu saying there was an error booting the system and recommending a factory reset. I ignored that and rebooted, and haven't had any other issues since, but that one was weird.
It's something to do with magisk 14.5 456 beta. I've had the same boot loops, reverted to stock boot.img and problems went away
I haven't has this issue since I posted. To be clear, the problem I had could not be solved by a hard reset - it actually reboots itself every time I try to get past the lock screen for the first time after the previous (self) reboot. It's exactly a bootloop except that the phone makes it into the OS instead of failing to boot.
It can be Magisk or Adaway, no worries. I just pray it's not a hardware issue.
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
I'm still using Magisk 14.3 on 8.1, "Flash" kernel, no issues.
I've not had this issue since I posted about it. I uninstalled one live wallpaper app, which I'm not sure did the trick or not.
froader said:
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
Click to expand...
Click to collapse
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
cswithxda said:
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
Click to expand...
Click to collapse
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
froader said:
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
Click to expand...
Click to collapse
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
cswithxda said:
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
Click to expand...
Click to collapse
Thanks for confirming. I wasn't sure if that was present flashing via TWRP, but makes sense that it would.
Same exact "Internal error" warning and occasional boot loop after upgrading the Pixel 2 (not XL) to 8.1 from Magisk 14.5.1456 using TWRP 3.2.1.0. Also an AdAway user. Glad to hear I didn't mess it up and it's just a quirk of the method and the alpha/beta stages. Hopefully this resolves soon as I hate guessing whether my device will go belly up at random. Seems like Flash kernel with Magisk 14.3 may be ideal - any other confirmations that this is a stable method?
I'm having this same issue as well! Using Magisk 14.5 1456, with the latest TWRP non-beta, and the Unified Hosts Adblock module. Randomly my phone goes into a soft reboot loop like your describing. If I hard reboot using power + volume up it seems to fix it for a time, then it happens again at a, seemingly, random time. It's crazily frustrating. The only other things I have that involve root are a terminal app, Drives roid, and CoSy to sync Facebook contacts. I also had Substratum using the root method, but I uninstalled that today wondering if that was the cause.
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
cswithxda said:
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
Click to expand...
Click to collapse
Were you able to recover from the bootloop at all without uninstalling? For me I was able to force restart it, it would be fine for a few hours then it would bootloop again.
Additionally, I uninstalled Magisk and flashed the stock boot image as well and so far it hasn't come back. I still have TWRP.
Not at all, hard reset still sees the same reboots over and over, so I had to try something. And the only thing I found was the Magisk uninstaller on the SD card lol. I then uninstalled the Magisk and reinstalled it, and the issue has not come back so far.
I'm having that boot loop. I'll try uninstalling magisk
Sent from my [device_name] using XDA-Developers Legacy app
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Interesting about removing AdAway. I had a hosts adblocker as well, I wonder if that has something to do with it.
Related
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
You can try a factory reset.
ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?
I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.
Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.
Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.
fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.
Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
Hi there,
I like OxygenOS but there is a problem that's really annoying to me.
I'm rooted with the latest magisk canary build, however everytime when I don't use the phone for some time, for example when I'm going to sleep and the phone is loading,
I keep loosing root access with magisk.
On a terminal it's always telling me that the daemon is not running and Magisk Manager tells me that I'm not rooted.
However to fix this, I just need to reboot the phone and I'm good to go again.
This is extremely annoying, because I'm using the Input Power Control module to limit the maximum charge amount for the battery.
However if the Magisk daemon is getting killed, this module doesn't work anymore either so it's ignoring the aforementioned maximum charge amount.
I saw in the xXx ROM thread that there was a possible fix for this included, however it has been removed again since it did not work.
On OOS I'm mostly running with SmurfKernel and the xXx and Renove ICE roms but they don't seem to help with this problem.
On custom roms I don't have this issue as they seem to be less aggressive at killing background tasks than OOS.
Does anyone else have this problem or an idea on how to prevent the loss of the root access? It seems OOS is killing the magisk daemon, is there any way to prevent this?
I think I used to have a similar issue where one of my A/B slots was rooted but the other was not. So if magisk was not working then a reboot (which I believe switches to the other slot) would fix the problem until the phone either shut off or restarted (this would cause the slot to switch back to the broken one).
The only recommendation I have is to back up your data, factory reset the device, and re-do the whole process. If anyone else has some good ideas I'd try those first.
klym.software said:
I think I used to have a similar issue where one of my A/B slots was rooted but the other was not. So if magisk was not working then a reboot (which I believe switches to the other slot) would fix the problem until the phone either shut off or restarted (this would cause the slot to switch back to the broken one).
The only recommendation I have is to back up your data, factory reset the device, and re-do the whole process. If anyone else has some good ideas I'd try those first.
Click to expand...
Click to collapse
Thanks for the recommendation, however I have reset my OP7Pro countless times already and that is the one problem that seems to persist over every reset. I don't know if its a problem of Magisk or OOS, but I believe it's OOS related,
cause the Magisk daemon is getting killed and I don't think that Magisk is killing itself