Kernel is not seandroid enforcing and nothing able to do - Android Q&A, Help & Troubleshooting

So, yesterday i wanted to install the lineage 15.0 on my samsung galaxy tab s 10.5 wifi. to my tab: i already hat lineage 14.1 and twrp installed. so i thougth - no big deal, would be a thing of 10 minutes. so i did like the 14.1, flashed the device, installed the 15.0 and the fitting GApps and so on... then i booted (it was already showing the error in the corner), it worked - for a small time. the setup-manager crashed everytime i tried to enter it and so, i shut it down. after that, nothing works anymore. its just showing the error and the grey charging symbol. when i try to enter download mode, the screen turns black for a second and the same as before appears again. my computer isnt recognizing it eather. what can i do? i couldnt find anything about this case
*Update* : i just had to remove the battery and wait a minunte, then it worked again

Related

[Q] Bootlooping into ROM manager please help

Hi, I've been running PA on my phone. Just an hour ago, I downloaded the PA OTA update file through their OTA updater, and pressed install now. The phone rebooted into ROM manager and spewed out a few lines of code, one of which went like "error processing rom manager script" and to update the ROM manager or something along those lines. The error message appears very briefly before the phone reboots into the samsung logo, then into the ROM manager and the cycle repeats itself.
I've tried taking out the battery for 10 minutes to solve the problem, but when I slide the battery back in it just boots and goes into ROM manager. The hardware key combos for recovery just keeps showing me the samsung s3 logo before switching off and rebooting. I've tried download mode, which I'm able to access. Problem is, my laptop and computer cannot detect the s3. I've tried reinstalling the samsung drivers but to no avail. Anyone got any ideas? I don't think the phone even started updating the ROM, its just stuck at that error message..
Nevermind I've managed to get it to recognise my phone after plugging in and out for like 10 minutes. God damn my s3 is dying soon.

Galaxy S5 Won't Boot!

Last night I downloaded the latest CM13 for Feb. 14 on my phone and was going to update. After the download finished it gave me the option to reboot and update so I said Ok. Ever since then my phone hasn't booted up to anything. I try booting into recovery mode and download mode but all I get is the Galaxy S5 screen and then the Android logo with text under that reads "Installing System Update" but it flashes the logo. What I mean by that is the screen is black for about 10 seconds and then the logo and text just pop up for a second and back to the black screen. I did leave it alone for hours to see if maybe it updated or something but still nothing.
This is what pops up = imgur(dot)com/u6qOC6c
(Sorry, it wouldn't let me post links)
Is my phone bricked? Is there anyway to fix this issue?
Thanks.
Calm down, phones brick all the time. And yours isn't bricked. Anyway, put it in download mode and than flash a stock ROM back.
Than do all the process for installing Cyanogenmod again with a clean install. Good luck!

LG G3 is charging very slowly suddenly

Yesterday I downloaded an update for Resurrection Remix. I flashed it and I saw a new root manager called 'Magisk'. I went into its settings and clicked on update magisk v1.11. It downloaded something and asked me to reboot now. I tapped reboot and the phone wouldn't boot up. It showed some error message on the top left corner and the screen turned off with a blue-red flashing LED. Luckily I could boot into recovery. I somehow flashed the previous build. The phone finally booted up. Everything seemed to work fine except charging. The phone is charging very slowly. It was charged only 45% in 1 hour and 15 minutes. Please help me out.
EDIT: I installed LineageOS 14.1 today but the problem still persists.

Lineage OS / TWRP not booting suddenly

---Edited: After trying to start for the 10th time, it booted just fine. Seems like its time for some backups ^^
The post may get deleted as the problem is resolved
Original Post:
Dear forum,
i flashed LOS on my Samsung galaxy S4 a few months ago, together with TWRP. No problems, only thing i detected is that when i plug the device in when its shut down, the vanilla loading logo pops up for a few secs, then the LOS one shows up and loads normally.
Now I have the following problem:
My phone had low battery, shut itself off, i plugged it in and restarted it immediately. It booted just fine, after a few mins i noticed that the sim card was disconnected, shortly after my phone shut off itself.
Now I can't boot it up into system or TWRP and there is no or just the stock loading screen but stuck at the first frame.
When booting into system, it shows the galaxy s4 front then gets black, and when trying to boot into TWRP it shows the blue loading kernel? logo on top and then shuts off
Pls help as i need my phone ^^
Thank you
Mrluca

TF201 suddenly bootlooping.

So I got myself a cheap TF201 tablet and decided to put Android 7.1 on it using this guide. I followed the instructions completely and everything went perfectly well.
Had TWRP 3.2.3.0 installed, Android 7.1 installed and it was working great. Rebooted a few times, set up my Google account in Android, started installing a few usual apps such as Chrome, etc. when suddenly the Pad completely locked up. It then rebooted and went straight to the TWRP logo screen, sat there for 10-20 seconds then rebooted. And now that is all it does - ASUS screen comes up for a couple of seconds with "This device is unlocked" in the upper left, then tries to go into recovery but it reboots instead.
I cannot access fastboot mode at all - holding PWR + Vol DN does nothing. I can access APX mode and I can briefly use ADB while the TWRP is up.
I have backups of all blobs and I have nvflash installed - I got through the whole guide step by step without a single problem.
Any help would be hugely appreciated!
I got quite the same issue here, I also flashed 7.1.2 yesterday and installed some stuff. Then today I wanted to install Magisk to root it. After the installation (I can't remember that it was successful but I think it wasn't because there was no Magisk app to find) I wanted to boot another time to the recovery and went into a bootloop. When I'm trying to boot to TWRP it stucks at the teamwin logo. Sadly I have no cable here at the moment to maybe reflash the recovery or try some other stuff.

Categories

Resources