Opened Magisk, said there was an update....upon reboot I am Corrupted and froze basically.....now to try and figure out recovery
On A12, Kiriaskura kernal, very few magisk modules...
cmh714 said:
Opened Magisk, said there was an update....upon reboot I am Corrupted and froze basically.....now to try and figure out recovery
On A12, Kiriaskura kernal, very few magisk modules...
Click to expand...
Click to collapse
Magisk support thread
No issue on my Pixel 5, stock kernel, only SafetyNet/systemless host modules.
atm I am struggling to get the device into Recovery mode...wont power down...
cmh714 said:
atm I am struggling to get the device into Recovery mode...wont power down...
Click to expand...
Click to collapse
Hold the power and volume up buttons together for over 30 seconds, maybe longer, and it should force it to power down.
Then if you haven't already, Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Good luck, let us know how you did. I had no trouble updating although at the moment I happen to be on the stock kernel - I don't plan on remaining stock and have previously updated at least one custom kernel.
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
cmh714 said:
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
Click to expand...
Click to collapse
CleanSlate worked well for me when I've been using a custom kernel. I know Kiriaskura is based on CleanSlate, but there are differences.
Glad you got it fixed.
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
roirraW edor ehT said:
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
Click to expand...
Click to collapse
But that's no fun
But seriously, that is probably wise. I've stayed on Canary to make it easier if Google decides to play with us again like they did in December with their load fstab shenanigans and of course earlier with their vbmeta shenanigans. Those were fixed quickly in Canary but took a while to make it to Stable. But with that comes the cons, of course, as evidence by today. But Stable is good advice.
On a side note, I never received the corrupted message like others did when updating Magisk while on Kirisakura today. However, I still have verity and verification disabled. Hmmm.... makes you wonder
"Mama always told me not to look into the eyes of the sun, but mama
That's where the fun is"
Lughnasadh said:
On a side note, I never received the corrupted message like others did when updating Magisk while on Kirisakura today. However, I still have verity and verification disabled. Hmmm.... makes you wonder
Click to expand...
Click to collapse
Sounds likely for what kept you safe to me.
Lughnasadh said:
"Mama always told me not to look into the eyes of the sun, but mama
That's where the fun is"
Click to expand...
Click to collapse
Mama, life had just begun
But now I've gone and thrown it all away
Oh sorry, mine's the wrong mama.
roirraW edor ehT said:
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
Click to expand...
Click to collapse
I might give that a try later, already wasted too much energy on fixing myself but yes, still on Canary
roirraW edor ehT said:
Sounds likely for what kept you safe to me.
Mama, life had just begun
But now I've gone and thrown it all away
Oh sorry, mine's the wrong mama.
Click to expand...
Click to collapse
Mama Queen meets Mama Manfred Mann's Earth Band... I love it!
cmh714 said:
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
Click to expand...
Click to collapse
Same happened to me, but can't get rid of corrupt system at boot...
I'm in the same boat, tomorrow I'm going to fully wipe and see if it go's away. That's the only thing I've seen that gets rid of that warning.
GIKE said:
Same happened to me, but can't get rid of corrupt system at boot...
Click to expand...
Click to collapse
Same here atm....will see if this months update (once it arrives) fixes things.....dont want to wipe but boy the message is a PITA!
I have the weird problem of no longer being able to modify the services.jar since the Magisk update.... I remove the navbar by modifying it. I can't change the size either. Weird that a Magisk update would hinder that.
GIKE said:
Same happened to me, but can't get rid of corrupt system at boot...
Click to expand...
Click to collapse
Blade22222 said:
I'm in the same boat, tomorrow I'm going to fully wipe and see if it go's away. That's the only thing I've seen that gets rid of that warning.
Click to expand...
Click to collapse
cmh714 said:
Same here atm....will see if this months update (once it arrives) fixes things.....dont want to wipe but boy the message is a PITA!
Click to expand...
Click to collapse
Flash an old (I did Feb .003 one.) boot.img, boot, then reboot and flash the current patched boot.img. Should get rid of it.
(don't forget direct install in magisk manager afterwards)
I tried with the newest boot.img, but it didnt work.
Sek0n said:
Flash an old (I did Feb .003 one.) boot.img, boot, then reboot and flash the current patched boot.img. Should get rid of it.
(don't forget direct install in magisk manager afterwards)
I tried with the newest boot.img, but it didnt work.
Click to expand...
Click to collapse
that worked for me, thanks!
Tulsadiver said:
I have the weird problem of no longer being able to modify the services.jar since the Magisk update.... I remove the navbar by modifying it. I can't change the size either. Weird that a Magisk update would hinder that.
Click to expand...
Click to collapse
sounds like something might be wonky with that new canary.
Freak07 said:
sounds like something might be wonky with that new canary.
Click to expand...
Click to collapse
Even more weird, I tried going back to an earlier version and the problem persisted. Bootloop. It doesn't bootloop until I unlock my phone though.
Tried to Fastboot flash boot boot.img with the mid-Feb release. I am still getting "Your device is corrupt". Going to "flash-nowipe"
Edit: While running flash-nowipe, got the same "device is corrupt" message. Thankfully when I hit resume the device went into fastbootd and is getting the image. Still getting device corrupt, but device booted and apps are still intack.
Rolled back Magisk to 24.3.10 with Kiris kernel 1.8.4. Everything is working fine, but still get the corrupt device message. Requires an extra "resume" when rebooting.
Hopefully tomorrow we will get the March release and an updated Magisk which make the problem go away. Hoping!
Related
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.
mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.
mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!
mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?
mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage
mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.
It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/
I've allready discussed this with @talktosam over at https://forum.xda-developers.com/mo...-to-magisk-root-xposed-oreo-8-t3743273/page16.
We both seem to have some trouble flashing magiks after the june patch ota. Our phones are stuck at bootlogo.
So if there's anybody out there who succeded, please let us know, how you did it.
This pertains to 8.x bootloaders and Oreo stock/factory signed. Maybe any 8.x bl rom?
yeah - read the comment about stuck at reboot in first post here
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Thanks @rafikowy
I also wasted a lot of time last night and advise that don't use 16.4 or 16.6, or the latest uninstaller 7-19 - I could not get out of that repeated bootlogo re-boot loop thing with them. I went back to 16.0, and the 7-08 uninstaller, and re-did the terminal commands and finally got it to work. I have no idea why this is so fussy. But then I found that back a bit when using the old universal fix on Alberto's 8.1 AOSPruns on 7.x bootloaders) so starting to learn that if something works, DON'T go to a later version (of magisk uninstaller or magisk combined install) LOL.
As someone said somewhere - after you do this you will probably need to enter magisk and let it update to the latest manager.
Ok, so I will try again with 16.0, but it will take some time as I'm preparing for my holidays travel now :laugh:
hamudistan said:
Ok, so I will try again with 16.0, but it will take some time as I'm preparing for my holidays travel now :laugh:
Click to expand...
Click to collapse
yeah, I am finding that it requires a lot of patience unless I do exactly what @rafikowy said. I have no idea why it's so fussy.
hamudistan said:
Ok, so I will try again with 16.0, but it will take some time as I'm preparing for my holidays travel now :laugh:
Click to expand...
Click to collapse
Well just tried several times, but with same results. Stuck at bootlogo.
Btw: how do you manage to type the "=" sign in twrp terminal? It's not there on my keys.
So I sent the commands via adb shell.
I do not have June yet, so unless you know of a stock that has it I can't test it. I suppose it's possible retus won't get it.
Those special characters are accessed by tapping the thing right above 123 in lower left - has some other special characters like = and > .
KrisM22 said:
Those special characters are accessed by tapping the thing right above 123 in lower left - has some other special characters like = and > .
Click to expand...
Click to collapse
Man I never thougt that key would reveal more...
Ok after some sleep and some coffee I did it again. Followed all steps exactly and the system booted up and I'm rooted.
Thanks for your patience
hamudistan said:
Man I never thougt that key would reveal more...
Ok after some sleep and some coffee I did it again. Followed all steps exactly and the system booted up and I'm rooted.
Thanks for your patience
Click to expand...
Click to collapse
Did you install f2fs module too?
Nnly loopback workaround. Didn't have f2s since my first stock oreo and everything worked as it should, so felt no need to install.
Back in nougat it was absolutly necessary
hamudistan said:
Nnly loopback workaround. Didn't have f2s since my first stock oreo and everything worked as it should, so felt no need to install.
Back in nougat it was absolutly necessary
Click to expand...
Click to collapse
Isn't the loopback bug and f2fs partition one in the same for that magisk specific module?
As long as they have two different names, I treat them as two (slight?) different modules due to not better (deeper) knowing it
Never underestimate the power of coffee/espresso! Great!!!
hamudistan said:
Nnly loopback workaround. Didn't have f2s since my first stock oreo and everything worked as it should, so felt no need to install.
Back in nougat it was absolutly necessary
Click to expand...
Click to collapse
I thought loopback obviously, not patch Never mind, I just installed june patch, flashed magisk 16.0, wrote terminal commands, flashed f2fs and I'm stuck on logo.... Could you please write down exactly all steps which you had done?
Edit: Never mind, I've already figured it out. After reinstaling magisk it booted up with f2fs loopback module.
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
TheKnux said:
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
Click to expand...
Click to collapse
I tried it, but it just hangs while trying to load resources. I think I'm just unlucky lol
I installed it but got a boot loop. I could only start the phone by flashing latest oos without magisk but even after uninstalling live boot, magisk still kept the liveboot00001 file or whatever so I had to remove it manually in twrp in /data/adb/magisk/ (somewhere around there.. ) Just in case someone else has this problem..
No problem here, using it since 4 weeks, several OOS updates never had an issue
TheKnux said:
Looks amazing on the OP6T.
Click to expand...
Click to collapse
It sure does! Thanks for the share. Works great on beta 2, even though I have the McLaren Magisk mod running (which replaces boot animation with McLaren's).
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Ironic said:
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Click to expand...
Click to collapse
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
TheKnux said:
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
Click to expand...
Click to collapse
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
tech_head said:
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
Click to expand...
Click to collapse
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
TheKnux said:
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
Click to expand...
Click to collapse
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
tech_head said:
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
Click to expand...
Click to collapse
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
TheKnux said:
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
Click to expand...
Click to collapse
I didn't change it. No real incentive right now.
This app was my old favorite and I miss it, I hope it still works as I havnt tried... Just wanted you all to know this is the best app ever and the scrolling text (if your developing) is actually SUPER helpful... I remember I would use the filter to find specific debug lines only and it was so usefull... I only installed it because Im a huge nerd so it was an extra awesomeness to have it be super usefull!
2023 BEST APP EVER!#[email protected]#
Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
djy said:
Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
Click to expand...
Click to collapse
The SafetyNet issue had nothing to do with March update and occurred Thursday night into Friday morning on devices of all varieties and versions. There are plenty of other conversations going on including on the thread you linked. Looks like Google is finding unlocked BL again, and Play Store fails certification on reinstall even dirty from what I have seen. You can't flash back to Feb dirty. Going back to previous updates requires a full device reset as far as I know.
I just went in to magisk manager and saw that I also failed cts. I am on the lastest patch, patched with magisk; on beta. It was fine when I was on February
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
TonikJDK said:
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
Click to expand...
Click to collapse
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
I personally had to factory reset my Pixel 3 XL and root it again. I'm passing SafetyNet but the Play store is not certified.
TonikJDK said:
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
Click to expand...
Click to collapse
I paid with GPay at two vendors this morning with filed CTS and "not certified" Play Store. Of course that did not include adding a card, but can't be certified since a couple of dirty flashes this week.,
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
fonixmunkee said:
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
Click to expand...
Click to collapse
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
sliding_billy said:
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
Click to expand...
Click to collapse
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Nope, stock kernel, rooted. Still fails.
Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Again, this did not happen as a result of anything March update related. Tons of devices that were not updated (including two of mine that haven't seen an update in almost a year and a half) started failing CTS as something that Google pushed automatically like Play services or whatever. Nothing to do with Magisk or able to be fixed with Magisk right now. Looks like they are searching for unlocked BL, and nothing is able to obscure it or know what exactly it is looking at yet (kernel, Magisk).
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Exokan said:
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
Click to expand...
Click to collapse
bobby janow said:
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Click to expand...
Click to collapse
I was just posting this because I saw it a lot earlier than others and was trying to quash any more threads about CTS failing. I find the whole thing funny how Google tries to placate app vendors who don't really want fake security but want ad revenue (IMO of course).
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
djy said:
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
Click to expand...
Click to collapse
This is odd. I flashed my 3 XL also with the April update, patched boot.img with Magisk 20.4 last night. Safety Net failed until I deleted the Safety Patch module. I rebooted and was able to have Google Pay working again (used it this morning to make sure). I'm thankful it's working again. Now I can't update MagiskHide Props Config in Magisk. And if I remember correctly, the quick access to GPay with the power button was a feature drop a while ago.