S9 (SM-G960F) after root constantly restarts... - Samsung Galaxy S9 Questions & Answers

Hy,
I root my Samsung S9 (SM-G960F on android 9 Pie) and everything is fine and working very well, but if I set lock screen (pattern, pin or password) then mobile just constantly restarts and I must over odin flash it again.
So is it posible and how can I repair it that can I set lock screen?
I root using this tutorial..
Code:
youtu.be/DsXfeOxUX_E
and used this root file for Samsung S9 SM-G960F-U7 Andoid 9 pie
Code:
firmwarebd.com/2019/12/how-to-root-samsung-galaxy-s9-all-model.html

Just dl a custom stock rom after flashing twrp
Like soldier or ultimate, problem solved in one second

Related

A5 2017 - lockscreen problem hangs with PIN/shape

Hi,
I have a problem with my A5 2017 running official nougat with magisk. I can use my fingerprint to unlock my phone easily, however when I try using my PIN/model, when I enter the right code, it just freezes until screen goes off. This was a real problem when I had to restart my phone, and it was asking me my model and I could drax it but then the screen would freeze until it went black and it was still asking me my model, and freeze etc. So i erased data/cache, but I still have that problem.
Thanks in advance
my problem is similar to this. when i try to unlock the lock screen with my pin, pw or model it takes about 5 seconds before the phone is unlocked. when i use fingerprint its unlocked instant. my A5 2017 (7.0 nougat) is rooted with magisk too. perhabs this is the problem?
in my case the problem was Magisk. I flashed my OS completely new with this instructions ( https://forum.xda-developers.com/sa...ficial-nougat-release-download-guide-t3654413 )
then i root with supersu instead of magisk and now it works !

I need help A520F/DS frozen is black turn on

Hi mi a520f/ds is say on turn on only official released binaries are allowed to be flashed
of rest is all black, it does not have the logo of samsung
I was trying to install oreo 8.0 but at the time of flash bl and cp my phone did not start anymore.
I can enter download mode perfectly but any rom that install say fail.

Samsung Galaxy S9(Exynos) stuck on Logo screen

Hi xda forum I'm new here so nice to meet you all.
I'm currently facing issue with rooting my s9 (Exynos).
which is I was trying to root My phone with twrp and simply format data and install all the essential files
such as no-verify-opt-encrypt-6.0-star.zip, RMM Bypass, samsung anti removal 2.4 and supersu or magisk.
After I complete my installation I rebooted the system from twrp.
And I face this problem which was stuck on the samsung galaxy s9 logo and doing nothing.
I forced shut down my s9 and went to download mode to flash new firmware by odin and It cameback nicely
But everytime when I try to root with twrp like I just said my phone just bricked and stuck on the logo.
I tried it about like 4 times fo this and nothing can solve it. I can use my phone without problem without root
but I really want to root my phone are there any solution for this?? please help:crying::crying:
gkfajsl99 said:
Hi xda forum I'm new here so nice to meet you all.
I'm currently facing issue with rooting my s9 (Exynos).
which is I was trying to root My phone with twrp and simply format data and install all the essential files
such as no-verify-opt-encrypt-6.0-star.zip, RMM Bypass, samsung anti removal 2.4 and supersu or magisk.
After I complete my installation I rebooted the system from twrp.
And I face this problem which was stuck on the samsung galaxy s9 logo and doing nothing.
I forced shut down my s9 and went to download mode to flash new firmware by odin and It cameback nicely
But everytime when I try to root with twrp like I just said my phone just bricked and stuck on the logo.
I tried it about like 4 times fo this and nothing can solve it. I can use my phone without problem without root
but I really want to root my phone are there any solution for this?? please help:crying::crying:
Click to expand...
Click to collapse
Welcome to the fray!! Hopefully we can find the solution you seek, can you tell me which twrp file are you flashing?

Attempting to upgrade rooted Galaxy Tab S4 (Android 8.1)

I currently have a Galaxy Tab S4 (SM-T830 USA-WIFI variant) that was rooted two years ago by me while it was on Android 8.1 and i believe build T830XXU1ARGH. I also had TWRP 2.8.4 installed at the time. I was looking first to upgrade to Android 10 with root and attempted to upgrade TWRP to 3.3.1 (which in hindsight was probably a bad idea since its for Android 10 not 8.1).
Now my tablet will not boot into recovery mode. I can get it into download mode but when using Smart Switch it hangs at 0% in the Emergency Recovery firmware.
When using Odin, I downloaded both SAMSUNG GALAXY TAB S4 SM-T830 XAR CELLULAR SOUTH T830XXU1ARGH FIRMWARE and GALAXY TAB S4 SM-T830 XAR CELLULAR SOUTH T830XXU4CTL2 FIRMWARE from SamMobile but when attempting to flash all I get are 0 succeeded.
At this time I am unable to boot into the OS and am stuck at the Download mode screen. Even after letting the battery go out fully, it keeps booting back here after charging.
Did I mess this up or is there still a way back for this?
I don't know why you can't flash the firmware with Odin, but you can try this firmware https://forum.xda-developers.com/t/...ed-debloated-tf5-weta-kernel-july-26.4137013/

Can i install LineageOS 18 (Android 11) on my S20+ that has been upgraded to official OneUI 4 (Android 12)

Hi,
as the title states, I am looking at installing LOS 18 on my S20+ (I know LOS 19 is out, but i need the older version).
My phone currently is fully stock (boot loader locked) and on OneUI 4 (Android 12).
A quick search on the forums seems to indicate it's not possible to downgrade to an official Android 11 ROM on the phone even using ODIN.
the device as an exynos device.
i managed to get it to work by installing the Android 11 stock rom using odin.
the first attempt it got stuck on boot loop, then I attempted using the HOME_CSC file, it got stuck at prism.img
on restarting it gave an error on failed update.
even then plugging in the USB, OdIN was able to detect it and trying installing it again worked.+

Categories

Resources