Good morning all guys. I have a Tab S4 T-835 with the latest version of Android 10. I'm trying in every way to root it but without success, the terminal on startup keeps restarting to the first Samsung screen. I tried both flashing the recovery and installing Magisk from there and patching the AP with magisk, but the same problem still occurs. How can I fix? Has anyone succeeded? Thank you
Fixed with flash WETA kernel TF5
Related
today i updated supersu to 2.17 and it attempted to update the binary but once it shut off it stayed in a bootloop, how do i fix this without having to wipe everything
Same problem here on S4 I9505 International version after automatic update via Google Play just now (2.12.2014, 15:50). Not sure which version i downloaded. Problem seems to have started after it asked the SuperSu binary to be updated by TWRP. The boot loop here occurs after I enter the pin code, apparently after loading various programs (which all are terminated), then reboot is triggered.
Downloaded UPDATE-SuperSU-v2.37.zip but found no way to get it to the S4...
I still have SuperSu-2v.27 on S4, so I reflashed that. Still on bootloop!
Backed up the S4 with TWRP, where I keep previous backups (just in case ...) and recovered my previous backup (one month old).
We'll see if I can update to v2.37 after that.
Flash a rooted ROM should fix this issue. I never install with twrp. Never had this issue.
Deleted. Old post made relevent from a completely different phone user/variant. ...
Got my Note 4 rooted it right away with no issues been running smoothly for a week or so. This weekend it has just got into a bootloop several times, the only thing I have been able to do is wipe data and start over. I mean I have Titanium Backup of all the apps but it is still a hassle. The only thing I have noticed is in the stock recovery it says "dm-verity failed"
I have read running a non-stock kernel will take car of this but not sure this is the issue. Has anyone else had this issue or have a solution?
It's the root. That root is causing that error to pop. Un-root your device.
I am trying to correct this issue as well for s friend who bought a used note smn910p.
It boots up
Its in the abnormal factory reset, reactivation loop i have to provide samsung account from unknown previous owner
rooted s5 smg900r4
fixed dm verity issue using kies3, updated firmware and initialization option.
rooted s5 smg900r4
Hi all.
I have a Note 8 GT-N5110 that's still running Stock 4.4.2. It's rooted and has Xposed 2.6.1 installed along with some modules. Last night I flashed TWRP 3.0.2-0 with the intention of flashing Magisk, forgetting at the time that it only works on Lollipop and up. I did not do a backup (I know) and rebooted back to the Stock OS just fine. I updated some Xposed modules and rebooted. Then I added some new Xposed modules, updated AdAway and its host files, and rebooted.
Now I cannot boot past the Samsung logo screen no matter how long I wait. I've gone into TWRP and wiped Dvalik and Cache, which lets me boot past the Samsung logo and get to a screen that says "Android is upgrading, starting the apps." It's been sitting on this screen for about 1 hour, which makes me think I can't boot past it. Any ideas how to easily fix this? If I need a full refresh, can anyone point me to the US version of the Stock 4.4.2 ROM?
This may help: https://updato.com/firmware-archive-select-model?q=gt-n5110&exact=1
Hello, just installed lineageos 17 on my galaxy tab s3 and everything seems ok except for one thing. When i open chrome and is about to write or search something the app just crashes, when i pick a saved bookmark everything works fine. Tested with firefox and no problems there just with chrome. Has anyone got any idea what could cause this? Rgs from Sweden
Continues, back to stock
I have a t820 and thought i should try lineage os 17.1. Said and done, flashed the files tablet booted no problems. After a couple of days i thought i liked to go back to stock. Downloaded the latest official fw and started flashing via odin but here is where the problem starts. Odin does not finish the flashing, i have tried many different files and version but same problem. So i thought i will flash lineage again but now the tablet gets to the boot screen but no further. Does anybody have any idea how i shall proceed? Many thanks in advance!
Continues
I managed to install lineageos again but would really like to go back to stock, i have downloaded stock rom from 3 different locations but odin wont flash the whole process, still no fault messages in odin. Does anybody have any idea what could cause this?
Solved
A reinstalled computer and another cable solved the problem!
Hi, I am a noob in flashing ROMs and stuff...
I recently got a Galaxy S9(used) by a family member. It had One UI 2.5, android 10 on it but I missed a couple of Android 11 features that I had on my Galaxy A50
So I decided to get Lineage OS 18.1. I flashed it successfully. When I launched Samsung Wearable app, it said that I had modified the software in "Unauthorized way". So I searched and found that Noble ROM is based on One UI 3.1 so I tried to flash it. I got stuck in a bootloop at first but then flashed again and after some time it booted up in setup screen like select language, etc. then at the data transfer part, the phone screen went black except the status bar, then it lighted up the set up screen went black again, it kept on happening. I rebooted it, tried safemode and also tried factory reset in TWRP. Then the issue still occurs from time to time.
I am ready to go back to stock ROM or should I try flashing newer Noble ROM or something else, please suggest.
Please help me!
I used Odin3_v3.14.4 , twrp-3.5.0_9-1-starlte.img.tar and NOBLEROM1.1_N9_S9_S9P with CAMERAFIX_G960
I didn't install kernel fix as I followed this video .