I decided to encrypt my S8+, and it's been stuck at the padlock encrypting for 3 hours now.
Yes, I know there are other threads on this (https://forum.xda-developers.com/galaxy-s8/help/rooted-phone-stuck-encryption-t3640805), but they don't seem to offer a solution.
Is it ACTUALLY encrypting, and I should wait longer, or is it stuck?
I was rooted with Magisk and had Xposed installed Systemlessly, on a custom ROM.
Thanks.
Related
I upgraded my Note 4 (SM-N910C) to Android 6.0.1 earlier this year and it's been rooted ever since.
Most recently I was using the Chainfire's systemless root with SuperUserSU and SUhide.
However, when attempting to use toggle root 2 days ago I was given a "No Super User Binary installed" message.
So it seems my device unrooted itself somehow and I've been pulling my hair out ever since trying to re-root it.
Since then I've tried re-flashing SuperUserSU, tried Magisk which had worked in the past and finally tried CF-autoroot.
I've even gone so far as to re-flash my original stock rom, wipe the device and start over with no luck.
I'm 7 hours in today and out of ideas. My Note 4 has not only rid itself of root, but become immune to root.
Firmware Auto-update is off. The only idea I've had is that the device HAS reset while root was toggled off, and I hear this can cause you to lose root. But surely everything I've done should have fixed that.
If anyone has and idea's I'd HIGHLY appreciate the help.
I was interested in trying out Xposed and installed the sdk23 for Marshmallow from the Magisk app. Though, I entirely missed the fine print on the many internet articles that Samsung devices need more care in installation, and promptly got stuck on the Samsung logo during boot.
The first of my problems is that none of the Xposed Framework Uninstallers I tried seemed to work. I tried the three different versions released on 20150831 and the version released on 20160211, but none of them seemed to take. I did get past the logo during boot when I flashed the stock ROM onto my device, and got root back with SuperSU, but it looks like I can no longer flash Magisk without something going wrong - either failing outright when installing through the Magisk app, or getting stuck on the Samsung logo again after flashing with TWRP. (Also tried the Xposed Uninstaller versions available to me in the Xposed installer app, the ones under the Systemless and Samsung tabs, and none of them seemed to have any effect either.)
I assume that a factory reset will solve my problems, but before that, are there any less drastic measures I could try first?
AKAAkira said:
I was interested in trying out Xposed and installed the sdk23 for Marshmallow from the Magisk app. Though, I entirely missed the fine print on the many internet articles that Samsung devices need more care in installation, and promptly got stuck on the Samsung logo during boot.
The first of my problems is that none of the Xposed Framework Uninstallers I tried seemed to work. I tried the three different versions released on 20150831 and the version released on 20160211, but none of them seemed to take. I did get past the logo during boot when I flashed the stock ROM onto my device, and got root back with SuperSU, but it looks like I can no longer flash Magisk without something going wrong - either failing outright when installing through the Magisk app, or getting stuck on the Samsung logo again after flashing with TWRP. (Also tried the Xposed Uninstaller versions available to me in the Xposed installer app, the ones under the Systemless and Samsung tabs, and none of them seemed to have any effect either.)
I assume that a factory reset will solve my problems, but before that, are there any less drastic measures I could try first?
Click to expand...
Click to collapse
I had a similar problem and had to reflash with original with original files ......... the file i had to use is named J120WVLU2AQJ3_J120WOYA2AQJ3_J120WVLU2AQJ3_HOME.tar.md5
I will try to add to my drop box and send you a link if it will help?
Please take into consideration i am fairly new to this and am not sure if this will solve your problem but it worked well on my phone same model SM-120w. Hope this helped out!
J120WVLU2AQJ3_J120WOYA2AQJ3_RWC.zip
Odin3-v3.12.7.zip
Hello XDA! I recently came into ownership of two Galaxy Tab 4 10.1 WiFi tablets that came factory reset with Android 5.0.2, they are the SM-T530NN variant for education as these came from a school - and I wanted to flash them with LineageOS. I had already rooted and flashed my Nexus 7 with LOS with no issues and really like it, so I figured I would do that too on these Tab 4's.
The problem I am running into is once I install LineageOS and Supersu from TWRP, the tablet reboots and can't get passed the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've read that this is not an error, and has something to do with the rooting process or possibly the ROM that I used itself, but nonetheless, it just sits at that error and never fully boots, hence why I can't just ignore it. My OS appeared to install with no errors. Other posts that I have researched on this forum concerning that message don't fully provide me with a solution I can replicate. However, I still have access to download mode and TWRP recovery upon boot so all does not appear to be lost.
I started with thisisapoorusernamechoice's guide (which was awesome by the way) for rooting and have kinda gone from there, trying newer version's of TWRP but am still stuck at boot.
Here are the files/versions I have used:
Odin 3.11.1
twrp-3.0.0.9_matisse_20160314-0843.tar (and 3.0.3.0)
lineage-14.1-20170319-UNOFFICIAL-matissewifi
supersu 2.79
Any help would be greatly appreciated.
***UPDATE***
Never saw any replies to this post so I decided to just try a different ROM, went for Bliss 6 to see if it would boot. Sure enough I still get the same message as before but it does boot up and is usable! Some minor things are not working like the camera app crashes upon opening, and the lock screen date and time are all smashed together - but these are minor inconveniences as these tablets will only be used for Plex, not taking pictures. Plus I still have a TWRP backup of the stock ROM should I choose to go back to that.
Hey guys, just picked up a G935T from my sister since it wasn't working for her after a fall.
So. It rarely boots all the way into the GUI, and it'll reboot within seconds of getting that far.
Tried booting to recovery, only gets there about once every 20 attempts. Download mode works okay.
Figured I'd flash a new recovery, but I can't because the BL is locked, it fails out almost immediately.
Figured I'd flash the latest BL...anyone have a link to that? Ideally I don't want to factory reset just yet because my sister would still like to recover the data she has on this thing.
Thanks in advance!
(Meanwhile, I told her to get an F model next time. )
Nobody, huh?
Try looking up on youtube how to unlock bootloader, I have a TMobil locked Samsung Galaxy S6 Edge and it wouldn't root regular had to flash it and to flash it I had to have a customed recovery so i used TWRP 3.3.1.0-zerolte.img and md5 etc worked like a sword taken off the fire and put through a cow, "easy" flash TWRP,Romed with Lineage 15.0 which is 9 Pie, opengapps64x full,Aroma Debloater for commercial programs to take out, Uninstaller Galactica to uninstall system programs to like google apps, etc., and to top off customed boot logo animation Marvel comics intro. So yea if you need help on links message me..........
So, I rooted back in 2015 or so, but Nintendo Online App won't load. After a bit of googling I discovered it's because I have SuperSU, with Xposed, and can't pass safetynetcheck.
It's the Verizon SM-N910V model.
My problem is, when I originally rooted it, it took so many attempts. It took probably two days of just non-stop rooting, and failing, and rooting and failing. There were times I got locked into a bootloop. But finally I got there, I got SuperSU, and I haven't looked back.
But I really want to pass safetynetcheck.
I've heard there are new root methods, and I fear I'm going to need to re-root my phone to get this to work......but I'm scared of doing that.
I've tried hiding Nintendo app in Magisk, and then I straight up hid literally everything on that list including system apps. Nintendo still crashes. I've tried running boot core mode. Nintendo still crashes.
Does anybody have anything I'm overlooking?