Please Delete the WiFi issue is no more this post did not solve the issue changing to a new rom did but caused other errors
reflash bluspark kernel.
you might have flashed magisk over bluspark which is the wrong order. always flash kernel last.
MarcTremonti said:
reflash bluspark kernel.
you might have flashed magisk over bluspark which is the wrong order. always flash kernel last.
Click to expand...
Click to collapse
Which would be completely pointless as you would lose everything magisk did. Magisk should be the last thing flashed
zelendel said:
Which would be completely pointless as you would lose everything magisk did. Magisk should be the last thing flashed
Click to expand...
Click to collapse
Sorry but thats wrong.
Something to read for you:
https://forum.xda-developers.com/showpost.php?p=72996757&postcount=5886
https://forum.xda-developers.com/showpost.php?p=72984150&postcount=5880
Last link is a post from the dev of bluspark kernel btw.
I'm still unable to mount storage via TWRP, if anyone can help and maybe needs more information to do so, just tell me what you need, this is a huge problem for me, I don't know what to do?
Re-flash TWRP?
Not being able to do anything with my recovery really makes me scared to do anything with my phone, when try new apps.
I appreciate anything anyone can do to help me, even just reading this post and giving it a shot is great, any replies would be awesome, this issue occured directly after I flashed RR ROM
MarcTremonti said:
Sorry but thats wrong.
Something to read for you:
https://forum.xda-developers.com/showpost.php?p=72996757&postcount=5886
https://forum.xda-developers.com/showpost.php?p=72984150&postcount=5880
Last link is a post from the dev of bluspark kernel btw.
Click to expand...
Click to collapse
And he is wrong. Check the majisk thread. Or even just thing about it for a second. If majisk makes changes to the kernel and then you flash a new one, what happens?
Never take anyone's word without doing your own research. Look into it and you will see.
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
lebeatnik said:
I'm still unable to mount storage via TWRP, if anyone can help and maybe needs more information to do so, just tell me what you need, this is a huge problem for me, I don't know what to do?
Re-flash TWRP?
Not being able to do anything with my recovery really makes me scared to do anything with my phone, when try new apps.
I appreciate anything anyone can do to help me, even just reading this post and giving it a shot is great, any replies would be awesome, this issue occured directly after I flashed RR ROM
Click to expand...
Click to collapse
By any chance is your system encrypted? I know recovery had an issue with encrypted devices for a while. Can't be sure as I never run encrypted and it's the first thing I remove when getting a new divice.
zelendel said:
And he is wrong. Check the majisk thread. Or even just thing about it for a second. If majisk makes changes to the kernel and then you flash a new one, what happens?
Click to expand...
Click to collapse
Well what happens is that magisk is working fine and new kernel also.
If flashed the other way around like you suggest i end up with broken wifi, and not only me (check bluspark thread).
So flashing like eng.stk advises, magisk first, then bluspark everything is running fine, so...
MarcTremonti said:
Well what happens is that magisk is working fine and new kernel also.
If flashed the other way around like you suggest i end up with broken wifi, and not only me (check bluspark thread).
So flashing like eng.stk advises, magisk first, then bluspark everything is running fine, so...
Click to expand...
Click to collapse
The I will tell you that something is wrong. As I never and I mean never have that issue but then again I don't use that kernel. But have not had the issue with the kernels I have used.
Related
Hi everyone!
I'm using the latest MoKee MK44 ROM for our Ace.
I really like this ROM but there seems to be a problem with the kernel. It reboots randomly during read or write processes.
Does anybody know something to fix that problem?
I attached the last_kmsg, maybe you can tell me whats going wrong here.
EDIT: It seems that it's not MoKee causing this problem.
EDIT2: I got a solution for the problem, take look at this post.
I haven't experienced that....but if I were to,I would definitely just clean flash ROM again.
I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!
Does really nobody knows something about the last_kmsg? Here are so many professionals and none of you can help?
Attached another last_kmsg, I took it right after a reboot.
Pulled battery, booted to recovery and copied it so I think there aren't many non-relevant events at the end of the file.
Attached file is now zip, maybe you don't like rar, I don't know. Thanks
Vega Bullet said:
I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!
Click to expand...
Click to collapse
No reboots here
marknoll said:
No reboots here
Click to expand...
Click to collapse
:good:
Ok, tried clean flashing once again, still the same result.
So what about the last kmsg?
What recovery are you using?
marknoll said:
What recovery are you using?
Click to expand...
Click to collapse
TWRP 2.7.1.0
Used the latest 4ext before that but had some problems, so I changed to twrp which works better I think.
Use the mod twrp jriors... That flashes everything.
marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
So you think it's a flashing problem? Like I said, I think there were no problems (especially random reboots) with other ROMs, that's why I didn't thought it's a flashing problem. But I will try it again.
EDIT: Can you give a link? Would help me saving some time
http://forum.xda-developers.com/showthread.php?t=2780164&page=4
marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
marknoll said:
http://forum.xda-developers.com/showthread.php?t=2780164&page=4
Click to expand...
Click to collapse
Well...
Vega Bullet said:
TWRP 2.7.1.0
Click to expand...
Click to collapse
I didn't know if "jriors" one is a special version but that is exactly the recovery I am using.
I got it from that thread, not from the mirror on page 4 you linked me to but from his first post.
So this would not change anything. Please correct me if I'm wrong.
All I can say is that maybe u got a bad download. Redownload the ROM and check md5. Then flash it with jriors. Should work fine then
Ok, looked for the checksums, matched.
And again, does really nobody know anything about the kernel log file? No idea? No clues?
I'm testing latest CM11 once again, maybe I find something...
EDIT: Tested under same conditions. Same problem with CM11. So I think an app or setting is causing it.
Would be very helpful if someone can take a look into kernel log.
My advice is to factory reset from recovery. Then go under advanced wipe and chose cache, dalvik,android secure and system wipe. Then flash the ROM and gapps..reboot after and let it run before logging in play store or installing any apps
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
[/COLO
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Can I plz have the link you're getting this ROM from? I think that maybe ur downloading an incompatible rom
I'm sure I do the procedures correct, tried simple factory reset (with recovery) and additionally wipe /system and android secure too.
Download ROM from here, look for checksums, flash boot.img separately.
But now, even if I only use it like it's been flashed, I'm getting reboots. Not only reboots. It seems that everything isn't correct.
Freshly flashed, want to reboot device normally but hangs during reboot dialog or bootloops...
Currently I'm testing the first ROM flashed the DHD with, CM11 OnePlusOne Edition and
THAT Rom seems to work. No reboots, hangs or bootloops, very confusing...
So it's getting very difficult to help me, no pattern I can follow to get out what's wrong
I thought Titanium Backup was the problem but like I said, even if it's clean it doesn't work.
Well, I will test everything again, let's see.
Are you s off?
marknoll said:
Are you s off?
Click to expand...
Click to collapse
No, thought of it but I was to lazy to read me through all the things I have to do,
flashing original ROM and what I have to keep in mind and so on...
Maybe I will try it but my time is also limited.
In the last_kmsg you can read that right after "rebooting in 5 seconds" there is "BUG: scheduling while atomic: htc_ebdlogd..."
I simply deleted the file htc_ebdlogd (because I don't know what else to do) and rebooted, seems to be no problem without that.
Till now the problem does not occurred. Till now..
Same problem on CM11 M9?
I think I'm having the same problem with CM11 on my Ace. I installed it this afternoon and have had random reboots on multiple occasions. Can't find a pattern for when it occurs. I don't have a logcat log from when it happens yet, but I'll try to obtain one.
My phone is S-ON (only HTCDev unlocked) and I used the TWRP 2.7.1.0 from [1], the CM11 M9 build from [2] and the PA GApps Modular Nano package from [3]. I installed by:
In TWRP:
1) Wipe (should wipe everything right?)
2) Install CM11 zip
3) Install PA GApps zip
Then flashed the extracted boot.img from fastboot.
I'd be very interested in hearning if deleting htc_ebdlogd really worked for you Vega Bullet.
Cheers,
Elvis
[1] http://forum.xda-developers.com/showthread.php?t=2780164
[2] http://forum.xda-developers.com/showthread.php?t=2533007
[3] http://forum.xda-developers.com/showthread.php?t=2397942
The kernel log is located under /proc named last_kmsg
For now it works fine let's but I don't really know if there are any consequences nor if it works.
EDIT: After a few days of testing a can say there are no reboots anymore, I am using MoKee MK44 for Ace and it's working fine.
Although I still don't know about consequences I can't say there are any but you do it without warranty.
So if you experience the same error
(means random reboot,
look into /proc/last_kmsg,
you should see the line "BUG: scheduling while atomic: htc_ebdlogd..."),
make a nandroid and delete htc_ebdlogd (should be located in /system/bin).
Btw, looking at the MoKee Source I only see one reference to this binary, it's located under ramdisk/init.spade.rc .
Maybe someone know's more and what it's good for, like I said without it I don't see differences...
This is for people who know how to debug to troubleshoot and correct issues in the jf tree, or at least provide relevant info.
Every post in the discussion thread should include your build string and variant, or you will be ignored.
I am not supporting your end user needs, but you can take that to the Q&A thread.
rom: https://www.androidfilehost.com/?w=files&flid=13420
use this gapps: https://www.androidfilehost.com/?w=files&flid=21354
do not flash another kernel
do not bring kk /data
known jf issues:
some overlays disabled
double tap home = camera is not working
swype on google keyboard not working
kernel source: https://github.com/CyanogenMod/android_kernel_samsung_jf
since nightlies are enabled, this thread wont be watched/updated anymore.
thanks for helping with the bringup.
Alright alright alriiiiiiiiiiight
Up & running, have cell and sound. Maybe NFC not working. GPS is, WiFi is. Thank you!
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
hoffreaper said:
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
Click to expand...
Click to collapse
what filesystem is it using?
hoffreaper said:
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
Click to expand...
Click to collapse
Exfat isn't working yet I believe, fat32 does tho
How did you guys install it? I took a look inside the zip and found a lot of stuff missing, there's not even a build.prop, most of the bulk of the zip is on a file called system.new.dat
To the people who have this running What gapps are you using?
archangeles said:
How did you guys install it? I took a look inside the zip and found a lot of stuff missing, there's not even a build.prop, most of the bulk of the zip is on a file called system.new.dat
Click to expand...
Click to collapse
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Gapps
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
dcd1182 said:
For testing...
Most stuff is working.
You tell me whats broken.
https://www.androidfilehost.com/?fid=95784891001613232
Click to expand...
Click to collapse
Did a test on making a call to my VM.while calling works ,trying to hang up it says hanging up but never does and VM lady just keeps talking til VM cuts off due to not entering anything
ShinySide said:
Gapps
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
Did a test on making a call to my VM.while calling works ,trying to hang up it says hanging up but never does and VM lady just keeps talking til VM cuts off due to not entering anything
Click to expand...
Click to collapse
same here on 1st call, but 2nd+ call hung up fine. same for you?
dcd1182 said:
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Click to expand...
Click to collapse
I'm actually running twrp, do you recommend switch to cwm to install the zip?
I used CWM. No problems with 1st call for me, and good since
dcd1182 said:
same here on 1st call, but 2nd+ call hung up fine. same for you?
Click to expand...
Click to collapse
Na Tried 4 times, refuses to hang up. Acts like it hangs up visually but in call screen stays on saying hanging up and vm just keeps talking
archangeles said:
I'm actually running twrp, do you recommend switch to cwm to install the zip?
Click to expand...
Click to collapse
shouldnt matter
dcd1182 said:
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Click to expand...
Click to collapse
dcd1182 said:
shouldnt matter
Click to expand...
Click to collapse
I get an error executing updater binaries in zip
archangeles said:
I get an error executing updater binaries in zip
Click to expand...
Click to collapse
try cwm then
i use philz 6.58.7, works here
edit: were not bringing back file based flashing, so if the recovery doesnt support block based, recovery needs updating
archangeles said:
I get an error executing updater binaries in zip
Click to expand...
Click to collapse
There's something wrong on your end then. I've flashed both builds with twrp 2.8.0.1 without issue
ShinySide said:
There's something wrong on your end then. I've flashed both builds with twrp 2.8.0.1 without issue
Click to expand...
Click to collapse
I know there is, I had a similar problem updating to 4.4.4 from 4.4.2 tw custom rom, and fixing permissions seemed to fix that, but this time it does nothing, could the bootloader be a problem in any way? I'm still on 4.4.2 because 4.4.4 tw never installed properly, but pac-man 4.4.4 worked just fine. Any pointers?
archangeles said:
I know there is, I had a similar problem updating to 4.4.4 from 4.4.2 tw custom rom, and fixing permissions seemed to fix that, but this time it does nothing, could the bootloader be a problem in any way? I'm still on 4.4.2 because 4.4.4 tw never installed properly, but pac-man 4.4.4 worked just fine. Any pointers?
Click to expand...
Click to collapse
not bootloader
try to format system
hello,
(with "this rom" i mean >sultan cm13<. I edited the title, before that it "was can't but sultan cm13", but now i know it doesnt boots any aosp roms)
a few days ago i used this rom as secondary with multirom (primary was freedom 1.10). now today, i wanted to use this rom as my dailydriver rom. i made the normal procedure, making a backup, then wiping the partitions (system, data, cache, dalvik) and after it flashing the rom. on the first try, i did it like i usually do, first the rom, then the gapps and then xposed. then i rebooted, and it was stuck on the 1+ logo screen about 10 mins. then i reflashed it, but just the cm.zip. then i still got stuck.
i tried it with the unofficial and the official twrp recovery. now i did a nandroid restore to the freedomos rom, and it boots normal.
please help me, i really want to use sultans cm13, i really like it!
i don't know why it doesn't work, i mean as a secondary it booted flawless..
btw i'm on the 3.2.7 firmware
(problem exists on all 6.0 aosp roms i tried. Please read further posts)
Did you follow the flashing instructions to the letter? If you did, you would have seen that the CM13 requires a one time flash of the OOS 3.2.6 firmware (linked in the thread).
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
ReNeH99 said:
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
Click to expand...
Click to collapse
BTW, which xposed version did you flash? If it was v86.x then that's the most likely culprit (since the latest patch, v87 works, v86.x causes bootloop).
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
ReNeH99 said:
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
Click to expand...
Click to collapse
Hmm... strange... TWRP doesn't give any errors either?
Hw4ng3r said:
Hmm... strange... TWRP doesn't give any errors either?
Click to expand...
Click to collapse
nope no errors, all the folders and build.prop, etc is in the /system folder too..
i also redownloaded the rom, md5 hash is right and it doesn't help either
May be a silly question but did you uninstall multirom?
Hw4ng3r said:
May be a silly question but did you uninstall multirom?
Click to expand...
Click to collapse
yep
i gonna try to flash RR 5.7.4, to see what happens then
edit: what i forgot to say, i also reinstalled multirom and the multirom recovery for another try. in the multirom menu the touch doesn't work then, and when the primary rom (cm13 sultan) boots after 5 secs, i just get a black screen, the phone isnt of, just a black screen, i have to press all 3 buttons for a reboot then.
edit2: RR also does not boot
edit3: lol i just reinstalled multirom and it boots as secondary rom. then i copied it to the primary slot, and *bling* it doesn't boot again... i dont get this...
Ok i tried it with multiple AOSP roms and it simply doesn't work. Strange thing is, they work as a secondary rom when i have multirom installed.
Does anybody have a solution for this maybe? I hope someone who knows about this problem can help me i don't want oos anymore i need aosp
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far
Hey, folks.
I have a two day old Pixel 2 XL. I have unlocked it and an running the stock ROM (latest factory), but I have rooted it by installing Magisk (flashed a zip file).
I still have the stock recovery, I flashed by booting to twrp via fastboot command.
I keep getting an error that Magisk Manager Keeps closing.
Is there a known issue that I just have not read about yet?
I only rooted so I could use AdAway, but when I tried to check a few settings in Magisk today, this kept coming up.
I'll reboot and see if I can get into it again, but if there is a known "proper" fix, I'd appreciate some gentle assistance.
Thanks
Seems to open up fine after a reboot and passes safety net check.
No clue what causes the issue, but I can live with an occasional reboot.
myk.robinson said:
Seems to open up fine after a reboot and passes safety net check.
No clue what causes the issue, but I can live with an occasional reboot.
Click to expand...
Click to collapse
Are you on stock or custom kernel?
Badger50 said:
Are you on stock or custom kernel?
Click to expand...
Click to collapse
Stock. You and Az Biker helped me with unlocking, and I not flashed the Magisk zip. Still stock kernel and stock bootloader, and I flashed the latest factory image.
myk.robinson said:
Stock. You and Az Biker helped me with unlocking, and I not flashed the Magisk zip. Still stock kernel and stock bootloader, and I flashed the latest factory image.
Click to expand...
Click to collapse
Maybe flash a custom kernel, followed immediately by flashing magisk ???
Badger50 said:
Maybe flash a custom kernel, followed immediately by flashing magisk
Click to expand...
Click to collapse
I mistyped my response, i ONLY flashed the Magisk zip file.
Same prescription, though? Try a different kernel with Magisk again, after taking a backup, of course?
myk.robinson said:
I mistyped my response, i ONLY flashed the Magisk zip file.
Same prescription, though? Try a different kernel with Magisk again, after taking a backup, of course?
Click to expand...
Click to collapse
While backups are always good practice, you'd be fine without one for flashing a kernel+magisk. Unless of course you want to, which is never a bad thing
Badger50 said:
While backups are always good practice, you'd be fine without one for flashing a kernel+magisk. Unless of course you want to, which is never a bad thing
Click to expand...
Click to collapse
You probably already know what my next question will be
I'll read some kernel threads and check out the pros and cons. My main concern is that I retain the features and stability of the stock kernel. Just have bad memories of certain kernels on my Moto G4 Plus breaking the fingerprint reader and messing up the screen saturation
Thanks
myk.robinson said:
You probably already know what my next question will be
I'll read some kernel threads and check out the pros and cons. My main concern is that I retain the features and stability of the stock kernel. Just have bad memories of certain kernels on my Moto G4 Plus breaking the fingerprint reader and messing up the screen saturation
Thanks
Click to expand...
Click to collapse
The past is the past my friend. I will unequivocally just say that whatever custom kernel you choose, they are all extremely good and reliable. I haven't run the stock kernel since the custom ones came out. My battery life is excellent, and functionality is just perfect. Not to mention, that if you use the EXKM app, there's a few extra perks that you may like. If you want the latest Linux changes and updates go with Flash kernel. If you want to stay closer to stock Linux/Google code, then go with Snoke or Ex kernel. I'm not going to try and convince you on what to do, I'm just relaying personal experience my friend ??