So about 6 weeks ago my 4xl froze and I forced a restart. When it booted back up it was stuck on the ”pixel is starting".
I was forced to flash the factory images and I rooted again, flashed a center clock module via magisk and was running again....until it happened again today. Any else ever have this happen?
I want root but I'm tired of this happening.
bigmatt503 said:
So about 6 weeks ago my 4xl froze and I forced a restart. When it booted back up it was stuck on the ”pixel is starting".
I was forced to flash the factory images and I rooted again, flashed a center clock module via magisk and was running again....until it happened again today. Any else ever have this happen?
I want root but I'm tired of this happening.
Click to expand...
Click to collapse
Yes, after I updated to November it happened. I was browsing google feed on the launcher. It froze then restarted to "pixel is starting". Flashing factory image without the -w didn't work, I had to wipe data. I even tried disabling all magisk modules via adb but still had to wipe data.
Interestingly, I was also using the center clock module. I've stayed away from that and haven't had a problem since.
Has anyone notified @Tulsadiver? If not he'll prolly notice this mention and chime in...
CyberpodS2 said:
Has anyone notified @Tulsadiver? If not he'll prolly notice this mention and chime in...
Click to expand...
Click to collapse
I have uploaded November updates but i run center clock and i haven't had any problems.
Tulsadiver said:
I have uploaded November updates but i run center clock and i haven't had any problems.
Click to expand...
Click to collapse
Center clock is one of my favorite mods.
Now that I think of it I was also running a couple modules to pass safetynet. Now I'm only using center clock and systemless hosts.
Thanks for chiming in
I'm starting to think it could be magisk canary. This has never happened when I was on android 10 using stable magisk. Either way I'm up and running again... rooted and still using center clock mod
Related
I've tried searching, but didn't seem to get anything on this one.
I've been trying to install the OTA Update to 4.3 for a minute, now... Currently, I've got the update downloaded, but it won't continue b/c it's saying the battery is too low. The thing is, the battery is at 100%. It is also plugged into a charger... Tried it with and without.
Here's info on my phone:
MJ5
Rooted via Kingo
Xposed Installer installed (very few modules installed - nothing hardcore)
RootCloak [1.4] installed in order to hide root status from the OTA update service
I have a bit of bloat uninstalled by Titanium Backup... But, that was all AT&T stuff like Navigator - I left the OTA service in place. I froze some Samsung bloat, but didn't uninstall it.
Any ideas on why I'm getting this error?
You have to be unrooted. At least that what I hear . When I got the update I did a factory reset and downloaded the update and installed with no issues.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Ah, great. Now Kingo won't re-root the phone. Looks like factory reset is what I'll be spending my evening doing.
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Pscheoverdrive said:
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Click to expand...
Click to collapse
Unfortunately nothing will work except restoring back to stock. I had to do that for the last 2 updates we've received. I just did it to get the last update and I am staying stock until Kitkat arrives then will look for a root solution. I know, it sucks.
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
Pscheoverdrive said:
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Click to expand...
Click to collapse
If you didn't uninstall the Xposed modules the uninstall Xposed that could be your issue right there. Try uninstalling everything root then try again.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Pscheoverdrive said:
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Click to expand...
Click to collapse
Factory reset just wipes your data and cache. It will not reinstall the system files. When you rooted you directly modified some of your system files via root access. Simple solution however. Follow these steps as mentioned before by theorioles33 using Odin and Heimdall. Takes about 10 mins (maybe 30 if its ur first time) Follow every step to the T and when ur back to stock try the OTA. Good Luck!
I have Oneplus 3t with 7.1.1 android. Only issue I am having is that if I turn Notification light on, there is no option to turn battery full, charging, and low notifications off. With them on i cant use the light at all, because it will light up my whole bedroom. I red from online that Light Flow is the best app that could have sleep time without notifications etc. but when i tested it, it could not turn those charging lights off. Is there some way to bybass this? Never seen issue like this before. I am not sure is it just bug that disable option is missing or such. I have been using this feature since 2013 with nexus 4 so unbelivable its missing from this.
It seems custom rom is only way to fix the problem, but what is stable enough for daily use? If I could fix this issue on normal rom I could use it for years, because there is nothing that i am missing or what i would need more from my phone.
If you don't want to change ROM, you can use Xposed and GravityBox, unless you use Android Pay or other SafetyNet protected apps
przemcio510 said:
If you don't want to change ROM, you can use Xposed and GravityBox, unless you use Android Pay or other SafetyNet protected apps
Click to expand...
Click to collapse
I have rooted phone already because of adway. Can you give some help about how? I have no clue how those works.
HTC Tytn user 188 said:
I have rooted phone already because of adway. Can you give some help about how? I have no clue how those works.
Click to expand...
Click to collapse
Are you rooted with SuperSU or Magisk? If the latter, then you can download Xposed through the Magisk Manager, then install Xposed Manager and GravityBox app.
GB has the feature to control LED for all apps, unfortunately the free version is limited to 50 reboots (full version costs about 4 USD).
przemcio510 said:
Are you rooted with SuperSU or Magisk? If the latter, then you can download Xposed through the Magisk Manager, then install Xposed Manager and GravityBox app.
GB has the feature to control LED for all apps, unfortunately the free version is limited to 50 reboots (full version costs about 4 USD).
Click to expand...
Click to collapse
I am rooted with SuperSU so what is the way to go?
HTC Tytn user 188 said:
I am rooted with SuperSU so what is the way to go?
Click to expand...
Click to collapse
If I were you, I would dirty flash current ROM (install it on top of currently installed without removing data), install Magisk and then proceed.
przemcio510 said:
If I were you, I would dirty flash current ROM (install it on top of currently installed without removing data), install Magisk and then proceed.
Click to expand...
Click to collapse
Is there any rom that would contain this automaticly without needing to do those things?
I have messed up my whole phone every time I have tried to update, because of the encryption. I am pretty sure that dirty flashing will mess up once again. Last time I tried magisk It did not work for some reason so i had to install supersu instead, because i allways need to root for adblock.
The second thing i hate in this phone is the constantly coming reminder that there is update avaible. With going to custom rom or such i could get rid of that problem too.
HTC Tytn user 188 said:
Is there any rom that would contain this automaticly without needing to do those things?
Click to expand...
Click to collapse
I don't think so and even there are such ROMs, and I wouldn't depend on them. Consider doing a clean flash and/or another ROM.
HTC Tytn user 188 said:
I have messed up my whole phone every time I have tried to update, because of the encryption. I am pretty sure that dirty flashing will mess up once again. Last time I tried magisk It did not work for some reason so i had to install supersu instead, because i allways need to root for adblock.
Click to expand...
Click to collapse
The encryption is most likely not an issue, at least I didn't have any problems with it.
HTC Tytn user 188 said:
The second thing i hate in this phone is the constantly coming reminder that there is update avaible. With going to custom rom or such i could get rid of that problem too.
Click to expand...
Click to collapse
This is the nature of stock ROMs, unfortunately, but you should be able to hide this type of notification (long-press on it and disable the notification, but it's not always possible).
przemcio510 said:
The encryption is most likely not an issue, at least I didn't have any problems with it.
Click to expand...
Click to collapse
When i got phone and updated and rooted it i managed to get it not to recognise anything meaning soft bricked. Then time went by and i decided to update phone when I was told the root will stay, but then encryption once again soft bricked everything. Never seen **** like that on any phone so I did not know there is such thing. Just one step more to make things harder.
Now I am wondering does that encryption mess things up today when i will install paranoid 7.3.1. Atleast i put up fastboot etc. ready on my computer so it will be easier to fix.
HTC Tytn user 188 said:
Now I am wondering does that encryption mess things up today when i will install paranoid 7.3.1. Atleast i put up fastboot etc. ready on my computer so it will be easier to fix.
Click to expand...
Click to collapse
It is said that one should format data when migrating from OOS to custom ROM.
HTC Tytn user 188 said:
Is there any rom that would contain this automaticly without needing to do those things?
I have messed up my whole phone every time I have tried to update, because of the encryption. I am pretty sure that dirty flashing will mess up once again. Last time I tried magisk It did not work for some reason so i had to install supersu instead, because i allways need to root for adblock.
The second thing i hate in this phone is the constantly coming reminder that there is update avaible. With going to custom rom or such i could get rid of that problem too.
Click to expand...
Click to collapse
clean flash nitrogen os - best rom
change settings for battery light or notification light in the priority mode
https://photos.app.goo.gl/mfnxvTF9mlhjbdDO2 (screenshot for more info)
I have noticed a new update is available for our devices. There isn't much detail but it seems it isn't just a security update.
V2.20A
Ilgazc said:
I have noticed a new update is available for our devices. There isn't much detail but it seems it isn't just a security update.
V2.20A
Click to expand...
Click to collapse
I have received the update as well, although I just updated to the pie update from Oreo yesterday, I noticed that night mode isn't working (is it the same for you) - thinking of performing a factory reset
Also is your device rooted? Cus I can see the magisk icon on your status bar.
Thank you.
keonramses said:
I have received the update as well, although I just updated to the pie update from Oreo yesterday, I noticed that night mode isn't working (is it the same for you) - thinking of performing a factory reset
Also is your device rooted? Cus I can see the magisk icon on your status bar.
Thank you.
Click to expand...
Click to collapse
Hello
There isn't any global dark mode, I heard it is coming in Android 10. Google keeps adding dark mode to their apps though.
It is rooted through the "temp root solution". System and boot partition are still locked and Magisk is stuck on a old version. I just use it for titanium backup etc.
Ilgazc said:
Hello
There isn't any global dark mode, I heard it is coming in Android 10. Google keeps adding dark mode to their apps though.
It is rooted through the "temp root solution". System and boot partition are still locked and Magisk is stuck on a old version. I just use it for titanium backup etc.
Click to expand...
Click to collapse
Thanks I was able to get it working, do you have any modules working well with it (what are they?), Trying to set up edxposed (so I can use lucky patcher) without luck
Ilgazc said:
Hello
There isn't any global dark mode, I heard it is coming in Android 10. Google keeps adding dark mode to their apps though.
It is rooted through the "temp root solution". System and boot partition are still locked and Magisk is stuck on a old version. I just use it for titanium backup etc.
Click to expand...
Click to collapse
How did you get titanium backup running? it keeps saying it can't detect root.
keonramses said:
I have received the update as well, although I just updated to the pie update from Oreo yesterday, I noticed that night mode isn't working (is it the same for you) - thinking of performing a factory reset
Also is your device rooted? Cus I can see the magisk icon on your status bar.
Thank you.
Click to expand...
Click to collapse
keonramses said:
How did you get titanium backup running? it keeps saying it can't detect root.
Click to expand...
Click to collapse
It runs fine here however you can lose the entire root (super user) functionality unless you reboot sometimes. I think phone's hard core power manager kills Magisk sometimes. When it happens Magisk will say new version is available.
BTW I use this root method:
https://forum.xda-developers.com/nokia-x5/how-to/temp-root-solution-nokia-5-1-plus-t3948577
keonramses said:
Thanks I was able to get it working, do you have any modules working well with it (what are they?), Trying to set up edxposed (so I can use lucky patcher) without luck
Click to expand...
Click to collapse
Some users report some stuff working but as there is no TWRP and Magisk manager shell, I am afraid to test things. Basically anything running early will fail, think like running a NT service vs running on user login. This thing runs very late for any advanced hack to work.
Ilgazc said:
It runs fine here however you can lose the entire root (super user) functionality unless you reboot sometimes. I think phone's hard core power manager kills Magisk sometimes. When it happens Magisk will say new version is available.
BTW I use this root method:
https://forum.xda-developers.com/nokia-x5/how-to/temp-root-solution-nokia-5-1-plus-t3948577
Click to expand...
Click to collapse
It's the same method I followed to get root, but titanium isn't detecting it, I attached a screenie
Help Apps being killed
Guys please I need help l my apps that I want to run are being killed, email WhatsApp Adguard etc
Is anyone getting a problem passing safetynet with the March install? Clean wipe and install, I have root but can't pass safetynet. I've wiped it 4x... no luck. Can anyone help?
I have a feeling SafetyNet hasn't been updated with the March builds (hoping anyway). Unless they've figured a way to detect root and we need a Magisk update.
It wasn't giving me any problems before after installing March update but just noticed now it isn't passing. Sometime in the last 2 days something happened.
Having the same problem. Was fine yesterday.
JasDevi said:
Having the same problem. Was fine yesterday.
Click to expand...
Click to collapse
Guessing Google did something to detect unlocked bootloader since a bunch of people are experiencing it.
I flashed back to a clean Feb build and got the same thing. I thought it was me.
Gosimer4 said:
I flashed back to a clean Feb build and got the same thing. I thought it was me.
Click to expand...
Click to collapse
I tried that as well no luck
I too am having this issue.
I tried fixing it with " Magisk Hide Props Config" with no luck.
Guess we just have to wait until there's a Magisk update
same here
wonderlander17 said:
same here
Click to expand...
Click to collapse
It's a widespread problem being discussed over in the magisk forums. Seems like Google is changing something server side with their checks. Don't think it is related to the March updated since checks are failing on older firmwares
Same here for me.
Anyone else have "Device is not certified", under Play Protect certification?
This happens on nearly all phones running March 2020. Saw it on my Pixel 2XL running March 2020 PixelDust and on a Pixel 3XL running Srock with Magisk as well. Just look into the Magisk Discussion Thread and you'll see that Google seems to have changed something again. Reports are coming in on the said thread in masses.
Sent from my Pixel 4 XL using XDA Labs
Was just about to create a thread about this.
I didn't know this was a common issue amongst many users, so I clean flashed twice in just as many days
I thought maybe I had accidentally flashed the AT&T version when that's not my carrier, or that my dtbo or boot image was corrupt, or patching the stock boot image in Magisk went wrong. I also tried switching kernels and so on.
So far no functionality for my use case has been broken so at least that's a plus.
Same thing happened here with Pixel Experience ROM. Used to work fine, then updated to March 5 security patch, and ctsprofile won't pass anymore.
Though at some moment it did pass, as I've even could get Play Store to show certified and such, but then it failed later on.
Google Pay, banking apps and everything seems to be still working, so it's just a visual glitch for me, at least.
Enviado de meu MI 9 usando o Tapatalk
This literally just happened to me today. Was all good on March update until today and now can't pass cts no matter what.
I read somewhere that may be correlated with unlocked bootloader. So we have to wait for new Magisk update probably.
Oh wow I thought I had installed a module that may have failed it but when I tried just Magisk it still broke. Now I know that the March Security update broke it...
tisla said:
Oh wow I thought I had installed a module that may have failed it but when I tried just Magisk it still broke. Now I know that the March Security update broke it...
Click to expand...
Click to collapse
It's something Google has done on their end. So going to an earlier firmware won't help. Definitely looks like the bootloader status is being detected.
It is most definitely on Google's side, I ONLY use Carbon ROM 9 (AOSP) and it hasnt changed in weeks, no updates, no security changes, then out of the blue a few days ago, it fails. The only thing that changed was Google's side, to test it out, I just rebuilt my Pixel 2 XL with the same Carbon ROM OS, same steps, same base Google firmware (which was working last week), and it fails CTS. No changes on my side, not one, this is Google modding changes on their side unfortunately. I will note, that Netflix shows up in the play store NP (when it IS a problem or MAGISK isnt passing correctly, it wont show up in the play store), so it still works perfectly fine for me. I do not use any bank apps but TD (which is fine, but no GPay) so I dont know if it affects GPay.
GPay still working over here on March update
Hello,
The last couple of months and completely out of no where my 4g data randomly stops working. The status bar icon shows that it's stuck on upload and won't download any data. The only way I've found to fix it outside of restarting the phone is to change the cell band type from auto to wcdma then back.
Anyone have any ideas on how to fix this?
Second issue is with Magisk and I know this is for Samsung but I figure why not ask anyway. As of yesterday after a reboot I lost root. Magisk apps shows I need to install magisk and install the app even though I'm in the app. Also a bunch of my apps are acting like I've never uzed them before and they need to be setup again. I haven't installed any updates so I'm not sure what caused it.
I've tried completely uninstalling Magisk and reinstall and that didn't do anything. The install went through fine but after launching the app it still says no root.
Any ideas?
Thanks
Hi, I think it has been updated and Magisk is useless due to new layers of security. I guess we'll wait until a new rom is made for the new update, including stock. I don't know if Magisk can release a new version and overcome this.
Thanks.
Reflashing the custom firmware then also Reflashing Magisk did get it working for me again.
I've since updated to the newest firmware, flashed OneOS and Magisk and it's been working fine until a little while ago when Magisk randomly shows as not installed again after a reboot.
I take it no one else has had this issue still?
Thanks