Flashed LineageOS on my SM-G920R4 with TWRP and it's not working correctly
On boot the device says "Not seandroid enforcing" and then boots after a few seconds. Once the device is booted I can't do anything because touching the screen does nothing, but all buttons work fine including the touch buttons.
I don't have a lot of experience with android phones.
You need to flash stock ROM via Odin. None of AOSP ROMs are stable now.
Related
So yesterday I was flashing my recovery rom on my SM-P605 with philz advanced rom from this thread http://forum.xda-developers.com/showthread.php?t=2570829. It flashed successfully but the recovery says recovery booting..... recovery is not seandroid enforcing set warranty bit :recovery. However I know i could just boot into download mode and flash on a clean recovery but no whenever i try to boot the device into recovery or even try to turn it off it goes straight back into recovery. I tried every single button combination imaginable and nothing is working! What can I do! I really need to be able to resolve this because this is the tablet I use for school and without it I am literally and utterly screwed over. Please help me.
Hi everyone, I just bought a N5 yesterday (i was using a N4 for almost 2 years) and I unlocked my device using the Nexus Root Toolkit, flashed the latest TWRP, installed ParanoidAndroid as my main OS and everything was fine untill the next step...
I was an avid user of MultiRom on my N4, so I flashed MultiRom on my N5 and everything was fine, I even tried to flash the official MiUI as a secondary OS but i got some errors and I just deleted that listed rom, no biggies... after that I booted into PA and flashed a custom kernel.
First, I flashed Franco's using his tool, and everything went smooth. I even restarted the device like 2 or 3 times while i was installing the usual apps (xposed, changed the font etc), the problem started when I downloaded the HellsCore kernel app from the playstore and flashed the kernel, after that, every time I try to boot my device it gets stuck on a black screen, it doesnt even show the Google logo with the unlocked icon at the beginning, it just gets stuck at that point.
My guess was that the Hellscore kernel had some issues with Multirom, and I started the fastboot recovery via ADB and flashed Franco's Kernel again... nothing happened, I still got a black screen.
I tried flashing the entire rom again (PA) and the same, black screen.
I also tried installing the original TWRP (not the MultiRom modded TWRP) and guess what??? I stilll got the same black screen.
The only way to get past thu it is to disconnect my device from USB, press power for 10 secs and after that i have to press power+volup+voldown.
That gets me to the fastboot. If I try to boot to the OS from there, i get a black screen. If I try to boot into the recovery, it boots ok.
The only way to boot into ParanoidAndroid is using the Nexus Root Toolkit and using the Franco's Kernel (r57) to boot TEMPORARY into the OS.
I dont know what else can I try, can someone please give me some advice??? Please. D=
Thanks in advance!!!
Return to stock. Links via signature.
Sent from my Nexus 5 using Tapatalk
I flashed CO15 Bootloader and Modem in ODIN. Reboot went fine. Held down power and tried to reboot into recovery. Stuck on splash screen. I can only get into Fastboot. I installed TWRP through ODIN but still can't get into recovery. Not sure what to do?
Stuck on Samsung Galaxy note 5 Screen
On top of screen in red text: RECOVERY IS NOT SEANDROID ENFORCING
Tried holding Volume up, Power, Home to enter recovery but not working
re-flash coi5, and let it boot all the way out.. at this time (for me) it will bootloop at the tmobile screen. catch the reboot with vol up + home + power, and let whatever happen happen (for me it said no instructions or something after the little green man) then click down to factory reset/wipe data, click that, then let it reboot all the way out to home screen.
THEN flash the stuff yo uwant.
I tried to reflash twrp and the boatloader and the modem but none of that worked. I had to download and extract stock firmware package(over night) because sammobile has very slow download speeds for free users. This morning I flashed package, rebooted into fastboot and flashed Twrp and was finally able to boot into recovery and restore.
Thank you
UnderCoverLover said:
I tried to reflash twrp and the boatloader and the modem but none of that worked. I had to download and extract stock firmware package(over night) because sammobile has very slow download speeds for free users. This morning I flashed package, rebooted into fastboot and flashed Twrp and was finally able to boot into recovery and restore.
Thank you
Click to expand...
Click to collapse
Do you still have the RECOVERY IS NOT SEANDROID ENFORCING on the boot up screen? Instead of recovery mine says "KERNEL is not seandroid enforcing" and I'm not stuck in a boot loop. And I'm assuming that after you flashed the stock firmware you attempted root, and after root was the message gone?
raider09 said:
Do you still have the RECOVERY IS NOT SEANDROID ENFORCING on the boot up screen? Instead of recovery mine says "KERNEL is not seandroid enforcing" and I'm not stuck in a boot loop. And I'm assuming that after you flashed the stock firmware you attempted root, and after root was the message gone?
Click to expand...
Click to collapse
The "recovery is not seandroid enforcing" message is normal for having a custom recovery installed & should only appear when booting to custom recovery, well for TWRP anyway.
The "kernel is not seandroid enforcing" message will appear for a number of custom kernels on every bootup, at least in my experience. I don't get this message when using arter97's kernels.
On my LG G2 VS980 I lost my TWRP recovery by trying to flash CWM Touch. Now when it boots into recovery I see a black screen with some tiny writing that instantly disappears back into a black screen and stays there until I hold power down for about 15 seconds. Originally I had stock 26A (KitKat), rooted with Stumproot and used Autorec to put TWRP on and that worked fine. Then I flashed CyanogenMod 12.1, that worked fine. Today I decided since I had CyanogenMod, I would try out their Touch recovery instead of the older TWRP. I downloaded Flashify and the latest CWM Touch recovery and downloaded Flashify and flashed the recovery with no error messages. I gave it root permission (the built-in CM root permission) and then booted into the mess I have now. I have tried to flash TWRP, but it does the same exact thing- same for trying CWM regular (non-Touch) recovery flash. None of the button combinations except power + up buttons do anything except boot into the regular phone or they boot into the broken recovery that shows the white writing that turns to the black screen of death. I tried going into settings and turning the developer settings on that says Update Recovery When Updating ROM, but that doesn't change anything. I also tried using ROM Manager, but it never worked flashing, even before. (It still does the same thing, it acts like it flashes, says its successful, then the recovery is the same. Useless.)
One thing that is odd is that I tried to use Autorec again. I downloaded the latest version from Play Store and when I tried to flash recovery with it it told me my phone was not supported- that it only works on VS980 model!?! That IS my model. So that's the gist of it. I really would appreciate any help at all. I love my phone.
AndyGumpp said:
On my LG G2 VS980 I lost my TWRP recovery by trying to flash CWM Touch. Now when it boots into recovery I see a black screen with some tiny writing that instantly disappears back into a black screen and stays there until I hold power down for about 15 seconds. Originally I had stock 26A (KitKat), rooted with Stumproot and used Autorec to put TWRP on and that worked fine. Then I flashed CyanogenMod 12.1, that worked fine. Today I decided since I had CyanogenMod, I would try out their Touch recovery instead of the older TWRP. I downloaded Flashify and the latest CWM Touch recovery and downloaded Flashify and flashed the recovery with no error messages. I gave it root permission (the built-in CM root permission) and then booted into the mess I have now. I have tried to flash TWRP, but it does the same exact thing- same for trying CWM regular (non-Touch) recovery flash. None of the button combinations except power + up buttons do anything except boot into the regular phone or they boot into the broken recovery that shows the white writing that turns to the black screen of death. I tried going into settings and turning the developer settings on that says Update Recovery When Updating ROM, but that doesn't change anything. I also tried using ROM Manager, but it never worked flashing, even before. (It still does the same thing, it acts like it flashes, says its successful, then the recovery is the same. Useless.)
One thing that is odd is that I tried to use Autorec again. I downloaded the latest version from Play Store and when I tried to flash recovery with it it told me my phone was not supported- that it only works on VS980 model!?! That IS my model. So that's the gist of it. I really would appreciate any help at all. I love my phone.
Click to expand...
Click to collapse
Hi AndyGumpp
Thanks for using XDA Assist.
I see you've solved your problem here http://forum.xda-developers.com/ver...lipop-lost-t3324510/post65560638#post65560638 I'll close this thread now. Apologies for the late reply.
Thread closed.
I have a samsung galaxy s3 (canada) which i installed twrp for d2att (at&t) and thats how i flashed the custom ROM without any problems as seen on another thread:
https://forum.xda-developers.com/showthread.php?t=2624413
But now when i try to get back onto custom recovery, it shows the blue text at the top left corner of the screen, flashes the samsung logo, but then the screen goes blank. it is only after i release the power + home + volume up that it goes back and just boots normally. I thought that it might of got uninstalled while flashing the custom ROM, so since i forgot to get gapps (to use playstore and find useful apps) i used odin v3.0.9 to flash the custom recovery. But i did everything but it still does not want to enter custom recovery.
Can anyone help me please?