Related
Here is a link to my 6/26/2014 build from evervolv sources. THIS IS UNOFFICIAL. If preludedrew wishes me to delete it, I will, immediately. This is a 4.4.4 build.
A recent recovery is required; see
http://forum.xda-developers.com/showpost.php?p=53106281&postcount=1114
I make no guarantees about this build. I am not a developer (yet?); I am only a builder. I have tested it on my own device and it seems to work well. But I do not have an activated phone, so take that with a grain of salt.
http://d-h.st/mZD
Awesome, I'll give it a try this weekend.
polymath257 said:
Here is a link to my 6/26/2014 build from evervolv sources. THIS IS UNOFFICIAL. If preludedrew wishes me to delete it, I will, immediately. This is a 4.4.4 build.
A recent recovery is required; see
http://forum.xda-developers.com/showpost.php?p=53106281&postcount=1114
I make no guarantees about this build. I am not a developer (yet?); I am only a builder. I have tested it on my own device and it seems to work well. But I do not have an activated phone, so take that with a grain of salt.
http://d-h.st/mZD
Click to expand...
Click to collapse
Can either recovery be used or do you recommend one over the other? Haven't flashed my d-inc 2 in a while.
P.S.
Thanks for posting this. I know you're not a dev but there are some people who like to flash new roms for the fun of it.
chuck864 said:
Can either recovery be used or do you recommend one over the other? Haven't flashed my d-inc 2 in a while.
P.S.
Thanks for posting this. I know you're not a dev but there are some people who like to flash new roms for the fun of it.
Click to expand...
Click to collapse
I flashed a previous build with TWRP, CWM, as well as 4EXT. I have done this one (so far) only under TWRP, but any of the most recent recoveries should work.
chuck864 said:
Can either recovery be used or do you recommend one over the other? Haven't flashed my d-inc 2 in a while.
P.S.
Thanks for posting this. I know you're not a dev but there are some people who like to flash new roms for the fun of it.
Click to expand...
Click to collapse
That's how I got into building.
polymath257 said:
I flashed a previous build with TWRP, CWM, as well as 4EXT. I have done this one (so far) only under TWRP, but any of the most recent recoveries should work.
Click to expand...
Click to collapse
I used CWM from your post and it worked fine.
Man... All I can say is wow... :highfive:
I can't believe 4.4.4 is running on my incredible. Only been running it for 30 minutes but so far looks great.
What's Working,
camera, ffc, panorama, wifi, gps, bluetooth, torch, screenshots, rotating hardware buttons, google now, chrome, maps.
My phone isn't activated so I can't test mobile data, etc, but it does show verizon service under my signal strength.
What's Not Working.
Recording video, rear or ffc,
Playing videos.
I can't play videos I have recorder previously. Acts like it is going to play them then just says "Can't play this video."
Videos in you tube app act like they are gonna play but go into an endless buffering loop
No video inside of chrome either. I think it is broke on everything.
Gets a little slow at times but overall very nice work. :good:
Here is a link to the KK gapps if anyone else wants to give it a try.
http://goo.im/gapps/gapps-kk-20140606-signed.zip
Update
Just wanted to post an update for anyone who is curious. I've tried tweaking a few things to get some more speed out of it.
I switched to ART and apps got really slow so i switched back. I'm thinking it has to do with converting the apps because the dex2oat process was running pretty high.
One thing that did help was changing the SElinux mode from enforced to permissive with this app.
link
I also installed facebook, which ran well to my surprise, and overclocked to 1420.
Other than the video and lag issue it seems to be pretty solid.
Maybe this will get someone's attention and breath some new life into an old but solid device. :fingers-crossed:
Doublepost from prev forum and cannot get gsm to work. Worked on 5/16 build but not this one. Cannot get preferred network type to stick. Does not seem to recognize sim card.
#Update#
I know this build doesn't have Dev support but just i just wanted to share what I've found.
Tried to listen to some music via head phones and it hard rebooted my phone. Plays fine through the phone speaker and through Bluetooth but it dies as soon as I plug in my head phones. Hard reboot every time.
Sent from my XT1080 using XDA Free mobile app
chuck864 said:
#Update#
I know this build doesn't have Dev support but just i just wanted to share what I've found.
Tried to listen to some music via head phones and it hard rebooted my phone. Plays fine through the phone speaker and through Bluetooth but it dies as soon as I plug in my head phones. Hard reboot every time.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Do you have a logcat of this? I can see if I can track down what is going on.
polymath257 said:
Do you have a logcat of this? I can see if I can track down what is going on.
Click to expand...
Click to collapse
I will get one this weekend and post it for you.
polymath257 said:
Do you have a logcat of this? I can see if I can track down what is going on.
Click to expand...
Click to collapse
Here are the log files. The logcat looked pretty empty so I got a last_kmsg as well. It wouldn't let me upload them for some reason so I zipped them together. Recommend opening them in wordpad for nice formatting.
Procedure:
booted the phone
launched a terminal
started the logcat
plugged in the headphones
I wiped all partitions, and installed the zip and resulted in a status 7 error. Using EXT4 recovery. Gonna try downloading again. Can I get an MD5?
MD5 matched. Still same error. Something about permissions denied or something and then status 7 installation aborted.
polymath257 said:
Here is a link to my 6/26/2014 build from evervolv sources. THIS IS UNOFFICIAL. If preludedrew wishes me to delete it, I will, immediately. This is a 4.4.4 build.
A recent recovery is required; see
http://forum.xda-developers.com/showpost.php?p=53106281&postcount=1114
I make no guarantees about this build. I am not a developer (yet?); I am only a builder. I have tested it on my own device and it seems to work well. But I do not have an activated phone, so take that with a grain of salt.
http://d-h.st/mZD
Click to expand...
Click to collapse
Osiris19 said:
I wiped all partitions, and installed the zip and resulted in a status 7 error. Using EXT4 recovery. Gonna try downloading again. Can I get an MD5?
MD5 matched. Still same error. Something about permissions denied or something and then status 7 installation aborted.
Click to expand...
Click to collapse
You have to use one of the newer recoveries from the OP. I haven't tried TWRP but can confirm CWM works fine.
I'll try TWRP. Any idea if EXT4 will be supported?
Osiris19 said:
I'll try TWRP. Any idea if EXT4 will be supported?
Click to expand...
Click to collapse
I couldn't say maybe someone will make a build.
Osiris19 said:
I'll try TWRP. Any idea if EXT4 will be supported?
Click to expand...
Click to collapse
The latest version of 4EXT should work. Use v1.0.0.6 RC3, the testing build.
chuck864 said:
Here are the log files. The logcat looked pretty empty so I got a last_kmsg as well. It wouldn't let me upload them for some reason so I zipped them together. Recommend opening them in wordpad for nice formatting.
Procedure:
booted the phone
launched a terminal
started the logcat
plugged in the headphones
Click to expand...
Click to collapse
I have played with this a bit on my phone also. It seems that the streams get messed up when the headphone is plugged in. For me, I can plug and unplug the headphones as long as there isn't any music playing, but the instant I attempt to play music with them in, or plug in when music is playing, the phone reboots. I haven't had much time to dig in the source code yet, but when I do, I will let you know what I find.
polymath257 said:
I have played with this a bit on my phone also. It seems that the streams get messed up when the headphone is plugged in. For me, I can plug and unplug the headphones as long as there isn't any music playing, but the instant I attempt to play music with them in, or plug in when music is playing, the phone reboots. I haven't had much time to dig in the source code yet, but when I do, I will let you know what I find.
Click to expand...
Click to collapse
I thought the dmesg was much more useful for this kind of stuff.
Lgrootnoob said:
I thought the dmesg was much more useful for this kind of stuff.
Click to expand...
Click to collapse
You could be right. I'm not familiar with the different log types. Correct me if I am wrong but I believe that the dmesg is cleared on hard reboots and not soft and this is a hard reboot.
Hello everyone,
So I've looked around on this topic and it's still an issue, albeit a minor one. I have the T-Mobile HTC One M8 phone........ unlocked/rooted, and S-OFF'd. I am currently using ViperOne M8, which is awesome!
When I boot to HBOOT after installing new firmware the OS line is filled in, but after booting to Recovery and going back to HBOOT, the OS line is now blank. I've been told this is a bug in TWRP, and not a bug or issue anywhere else. I've tried 2 different approaches to fixing it. One entailed flashing a new ZIP (or flashing something), but the instructions stated that I needed to boot to Recovery while in Stock Recovery, which my phone does not do. It's only when I use a TWRP Recovery that I am able to go into any Recovery Menu. The other one had to do with flashing a zipped firmware, but even though that flash worked just fine, it still didn't resolve the OS issue. I have tried looking all around, but either I'm missing something, or it's just not knowing enough about what I'm reading to recognize the right answer.
So please, will someone tell me HOW do I get rid of that pesky TWRP bug that causes the OS line in HBOOT to blank out after only 1 visit to recovery post-firmware update?
I would appreciate ANY info you can give me.
Thank You,
RockStar2005
The Answer!!
IGNORE this post!! Scroll down to my "2nd September 2014, 5:17 PM" post instead for what you're really looking for!
RockStar2005
Ok got it!
Download the modified TWRP from here:
http://forum.xda-developers.com/show...php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
RockStar2005 said:
Ok got it!
Download the modified TWRP from here:
http://forum.xda-developers.com/show...php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
Click to expand...
Click to collapse
Unfortunately your link to the modified TWRP leads to a 404.
Is there a new thread?
The True Fix
RealZac said:
Unfortunately your link to the modified TWRP leads to a 404.
Is there a new thread?
Click to expand...
Click to collapse
Hey Zac,
Forget about that TWRP. It wasn't good. Please DELETE any backups you made using it and the twrp image file itself as they are all corrupted and won't boot up (I found this out after my initial post here). Read this post I put elsewhere for the real deal Holyfield lol:
So I ended up finding a RELIABLE fixed current version of TWRP on xda you may wanna check out. You can find it here: http://themikmik.com/showthread.php?16278-SPRINT-RECOVERY-TWRP-Recovery-(UNOFFICIAL)-v2-7-0-4 (Go to that link then Control + F this: "Downloads TWRP Recovery 2.7.1.0 (DH) | Mirror (AFH) - build date: July 13, 2014". I downloaded from the Mirror link.)
Don't worry about it saying Sprint...... the dev CONFIRMED it works for all variants/carriers. So after creating a new backup using the standard twrp, I went back to stock recovery, re-flashed my most recent firmware (2.22.401.5), and then switched over to that new version of twrp........ created a new backup and then restored it using that new version. Worked like a charm!! And the "blank OS" issue........... gone! I highly recommend it!!
If you have any other questions Zac, please post here and I will respond.
RockStar2005
Thank you for this detailed answer!
I will test it.
RealZac said:
Thank you for this detailed answer!
I will test it.
Click to expand...
Click to collapse
You're quite welcome! And make sure to check HBOOT (Bootloader) AFTER going to fixed TWRP to verify the OS line is NOT blank.
RockStar2005
RockStar2005 said:
You're quite welcome! And make sure to check HBOOT (Bootloader) AFTER going to fixed TWRP to verify the OS line is NOT blank.
RockStar2005
Click to expand...
Click to collapse
Every time I flashed the firmware I realized that "OS.." displayed the correct version.
I double an triple checked that.
So I did know that this blank OS only showed up after flashing the TWRP standard version.
RealZac said:
Every time I flashed the firmware I realized that "OS.." displayed the correct version.
I double an triple checked that.
So I did know that this blank OS only showed up after flashing the TWRP standard version.
Click to expand...
Click to collapse
Zac,
Ok cool.
Have a good one!
RockStar2005
RockStar2005 said:
I needed to boot to Recovery while in Stock Recovery, which my phone does not do.
Click to expand...
Click to collapse
It does, when you reach the screen with the small phone in the middle(upside down exclamation mark in it) just press volume up(hold) and tap power button. That takes you into stock recovery menu.
Just for future references... :good:
BerndM14 said:
It does, when you reach the screen with the small phone in the middle(upside down exclamation mark in it) just press volume up(hold) and tap power button. That takes you into stock recovery menu.
Just for future references... :good:
Click to expand...
Click to collapse
Hey BerndM14,
I'm 99% sure I tried doing that when I got that screen you just described, and all my phone did was reboot.... and not to recovery either. I dunno. It's not a big deal as I've since resolved the issue by finding a newer "fixed" version of TWRP and/or firmware (whatever the issue was, I think it was with TWRP though).
Maybe next time I do a firmware upgrade and have to go back to stock recovery, I'll try it again.
Thanks!
RockStar2005
RockStar2005 said:
Hey BerndM14,
I'm 99% sure I tried doing that when I got that screen you just described, and all my phone did was reboot.... and not to recovery either. I dunno. It's not a big deal as I've since resolved the issue by finding a newer "fixed" version of TWRP and/or firmware (whatever the issue was, I think it was with TWRP though).
Maybe next time I do a firmware upgrade and have to go back to stock recovery, I'll try it again.
Thanks!
RockStar2005
Click to expand...
Click to collapse
I also had the phone reboot, problem I had was that I held volume up + power, which wasn't right. Just hold volume up and TAP power. Either way though.
For future references like I said :good:
BerndM14 said:
I also had the phone reboot, problem I had was that I held volume up + power, which wasn't right. Just hold volume up and TAP power. Either way though.
For future references like I said :good:
Click to expand...
Click to collapse
BerndM14,
Ok I see.........so TAPPING not holding Power and holding Volume+Up. Got it.
Thanks for the clarification!
RockStar2005
RockStar2005 said:
Zac,
Ok cool.
Have a good one!
RockStar2005
Click to expand...
Click to collapse
Works great & flawlessly! Thank you for the help!
RealZac said:
Works great & flawlessly! Thank you for the help!
Click to expand...
Click to collapse
Zac,
Sweett!! You're very welcome!
RockStar2005
Hi,
I tried to flash the latest xposed version (version 80) with the latest flashfire version (update from the 2 February) but the screen just goes black and the device reboots after like 3 minutes. Nothing is flashed. Was anybody able to solve this or can someone upload a flashfire version that is older than 20 January?
Sent from my LG-H818 using Tapatalk
With flashfire some some things take a looonnnggggg time to flash. So a flashfire flash will take longer when flashing xposed. Put it in a cool place and let it flash for about 10 minutes (so the device doesnt get hot)if that does nothing then someone else might have to give you advice.
Eddiekool12 said:
With flashfire some some things take a looonnnggggg time to flash. So a flashfire flash will take longer when flashing xposed. Put it in a cool place and let it flash for about 10 minutes (so the device doesnt get hot)if that does nothing then someone else might have to give you advice.
Click to expand...
Click to collapse
Dude.....the device reboots itself and I can't do anything about it.
I found out what wrong though and apparently chainfire, the developer, changed something in the error handling and now our device just reboots instead of flashing. Use version 0.24 and everything will work again.
I did contact him and asked him if he can do something about it.
Sent from my LG-H818 using Tapatalk
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]#
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!