Hi all,
Subject line says it all. I've tried various versions but am getting the recovery SEANDROID message. TWRP runs however so I'm not sure if I have a problem or not. Backup function works with TWRP but I have not tried anything else.
My goal is to install lineage but I wanted to check on this issue before I went any further.
Thanks!
it means you are not running stock software (who would have thought):
https://forum.xda-developers.com/ga...-7-1-xsm-p900-unofficial-cyanogenmod-t3524788
Related
So I'm no developer, but I'm pretty good at following instructions and figuring things out by piecing information together. I have a galaxy s6 model sm-g920r7 on 6.0.1 originally bought from Ntelos, which from what I've read in various places, is the same model number and hardware as the c spire version. I've spent nearly 2 years trying to get this thing rooted, and finally managed to get that done somewhat successfully. The way I did it was by using the cf autoroot for the sprint version sm-g920p, because I figured since sprint bought out Ntelos, maybe the sprint version would be compatible.
Well, It went smoothly, and root checker says I'm rooted. But I can't get a successful twrp install. I've tried the twrp app, and I've tried flashing with odin. the twrp app gives me an error when I try to install, and odin just gets stuck and won't finish. Trying to get into recovery mode, it just goes to the samsung load screen with red words at the top saying recovery is not seandroid enforcing. I'm assuming that it has something to do with the SELinux being set to enforcing rather than permissive, but I can't find a way to fix that either. I've tried changing it to permissive with terminal emulator, and that doesn't do anything.
I want to install a custom rom, so I'm trying everything i can find to get it working as it should but there's so little information out there about my phone model. I've dragged this out for way too long to give up now and get a different model. Hell, at this point, it's really just about solving the puzzle anyway, since I upgraded to the s7 edge. If anyone has a clue what I can do to solve any of these issues, I'd be greatly appreciative.
Update: Found this version of twrp, flashed with odin, and now I can get into recover. But it still gives the "recovery not seandroid enforcing" in red letters above the samsung logo before going into twrp recovery mode. So I'm not even sure what's going on with that.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
Hello everybody, about 6 hours ago I attempted to flash my first ROM and I believe I am experiencing a bootloop or something similar.
The device (alcatel idol 3 5.5) starts to boot up but never finished booting
the ROM I installed is BlissPop (not exactly sure which version but I believe it is the latest one) but If i remember correctly the build is "unofficial" so I am not exactly surprised I am experiencing this.
Is there a way to fix this, and if so, how? At the moment I only have access to a quite outdated mac machine and I already tried sideloading a different ROM but I get a strange error that my adb's version is too old (it requires something above 1.0 while mine is something above 3.0). I've tried using a few different download locations for it but they all seem to do the same.
I have also done a TWRP backup before flashing but I have no idea how to recover it since I cannot "boot"/flash the TWRP recovery program without adb
Any help or idea how to solve this would be greatly appreciated
I’ve recently been trying to root my Samsung SM-J710FN. I managed to find a sequence of actions that consistently produces a rooted phone. I found TWRP 3.0.2 (I know that later versions exist, but this is the latest I could find for this model) and flashed it using Odin. I then use it to wipe the data partition (because, apparently, TWRP doesn’t work well with encryption). I use adb push to copy SuperSU 2.79 (downloaded from here) and no-verity-opt-encrypt-6.0 (in accordance with instructions in this thread, downloaded from here) to /data, then I install both of them using TWRP and reboot.
While the phone does appear rooted, it does end up having some serious problems. Here are some that I managed to find:
The camera doesn’t work. When I try to start the Camera app, it just crashes after a few moments.
The flashlight doesn’t work. When I try to turn it on using the button in the quick settings panel at the top, I get a message saying that the Camera app is using the flashlight (and the flashlight doesn’t turn on, obviously).
The phone does not automatically change orientation as I rotate it (in apps that are supposed to support it, such as Google Chrome), even though the appropriate settings are enabled.
The brightness controls do not affect the screen’s brightness in any way.
(I also can’t manage to re-encrypt the phone after rooting it, but that’s probably better left for a different thread.)
Has anyone else encountered similar problems? What can I do to solve them?
Have you tried to reflash stock ROM again?
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
I finally figured it out. Looks like I should have used a different SuperSU version. I repeated the process using SuperSU v2.82 SR5 and the problems stopped.
(I’m still trying to get the phone to be both rooted and encrypted, but that’s a separate story…)
EDIT: I gave up on SuperSU and used Magisk instead. It’s much easier and seems to work perfectly even with encryption!
Can you give me link to download a Android system and Magisk. Which one you used. I have the same problem :c
Here’s Magisk: https://forum.xda-developers.com/apps/magisk
As for “Android system”, do you mean stock firmware? In that case, I’m really sorry but I haven’t really kept a link to the place I downloaded it from Besides, you need stock firmware that matches your specific phone (based on the part of the world where you bought the phone, I think? I’m not quite sure), which may not be the same as mine.
I've already done it, I downloaded all the necessary files from sammobile.com
But thank you for your willingness to help
voidphantom said:
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
Click to expand...
Click to collapse
Can you give me the link of the Stock ROM?
When twrp install j7 max then phone go to bootloop problem please tell me how I fix this problem
dealiyo said:
Can you give me the link of the Stock ROM?
Click to expand...
Click to collapse
As I said before, unfortunately, I have not kept a link to the stock firmware. Further, judging by your other posts, you don’t seem to have a device of the same model as mine (I have SM-J710FN, you said you have SM-J710GN), which means my stock firmware isn’t going to be useful to you anyway.
Hi all,
Installing a custom rom on an XZ Premium; it's my first time dealing with this so its possible I missed something. I successfully installed TWRP and adb sideloaded the most recent Cherish OS rom. I was able to set up the phone with no issue, but upon rebooting for the first time back into system, it hits the boot logo, which animates correctly, but then hangs there indefinitely. I have wiped system memory, reformatted, and reinstalled, and the issue persists. I have also tried other ROMs. Arrow had the same issue, as did the Pixel experience, which leads me to believe that it's not an issue with the rom, but something with how I have configured the set-up.
I looked around for solution, but wasn't able to find much on the specific issue of only having issues on second boot, rather than initial. Any help would be appreciated.
I think your TWRP version is the Problem... (I think there were a lot of complaints about 3.3.?.? and higher) I had a similar Problem; TWRP wanted to use /data and if i formated the device, it would endless bootloop (I think because of the encryption the OS uses by default) So i decided to flash a older version (were this wasn't a problem) and I picked twrp-3.2.2-0-maple.img (maple because i have single SIM variant) and I didn't even needed to format the device and it still works (after i flashed Magisk and some other stuff/ "enhancements", that don't impact he OS) and everything still works smootly.
Maybe you should just flash a older version of TWRP (like 3.2.2-0) But i can't guarrantee, that it'll work on Pie(since i don't have it).