Develop Bugs

after root freezes on the logo

Hello, I would know because my Samsung j3 2016 smJ320FN, after I have completed the root, he is firm on the logo, it appears and it disappears but he remains always on the logo, Thank you very very much
information:
Android version : 5.1.1
Baseband version: J320FNXXU0AQC6
Kernel version: 3.10.65-10519280
[email protected] #2
Mon Feb 27 20:36:15 KST 2017
Build number: LMY47V.J320FNXXU0AQB3
SE for android status: Enforcing
SEPF_SM-J320FN_5.1.1_0072
Mon Feb 27 20:51:45 2017

Ono Minori said:
Hello, I would know because my Samsung j3 2016 smJ320FN, after I have completed the root, he is firm on the logo, it appears and it disappears but he remains always on the logo, Thank you very very much
information:
Android version : 5.1.1
Baseband version: J320FNXXU0AQC6
Kernel version: 3.10.65-10519280
[email protected] #2
Mon Feb 27 20:36:15 KST 2017
Build number: LMY47V.J320FNXXU0AQB3
SE for android status: Enforcing
SEPF_SM-J320FN_5.1.1_0072
Mon Feb 27 20:51:45 2017
Click to expand...
Click to collapse
You need to flash supersu v2.79SR3 to get root access without bootloop.
Flash Stock ROM via SmartSwitch and try with v2.79

[Question] Running 6.0.1 Stock MM

So here's the thing, I've a "rooted" Z play, it's running 6.0.1 stock, i've TWRP as recovery.
I want to go back to the most updated firmware (or atleast to 7.1.1)
Here are the details:
Software channel - retapac
Android version - 6.0.1
Android security patch level - August 1, 2016
Baseband version - M8953_10229.50.04.65R ADDISON_ROWDSDS_CUST
Kernel version - 3.18.24-perf g0c283d2
[email protected] #1
Mon Aug 29 01:19:37 cdt 2016
Build number - MPN24.104-44
Sorry for the extra noob question but i just want to get back to the normal unrooted firmware
Please help me out, what is the best 1st step towards going back to 7.1.1?
Thank you and regards!

carlosmacapagal said:
So here's the thing, I've a "rooted" Z play, it's running 6.0.1 stock, i've TWRP as recovery.
I want to go back to the most updated firmware (or atleast to 7.1.1)
Here are the details:
Software channel - retapac
Android version - 6.0.1
Android security patch level - August 1, 2016
Baseband version - M8953_10229.50.04.65R ADDISON_ROWDSDS_CUST
Kernel version - 3.18.24-perf g0c283d2
[email protected] #1
Mon Aug 29 01:19:37 cdt 2016
Build number - MPN24.104-44
Sorry for the extra noob question but i just want to get back to the normal unrooted firmware
Please help me out, what is the best 1st step towards going back to 7.1.1?
Thank you and regards!
Click to expand...
Click to collapse
I just wanted to tell you that 8.0.0 is now out for the MZP. But if you want 7.1.1, there are lots of guides in the forums of our device on how to flash the firmware and relock the bootloader

S9 still stuck in Apr 2018 security patch, no updates whatsoever...

Hi, my Samsung S9 (SM-G960F, dual SIM) was purchased in May 2018 from Dubai (fully unlocked) and is being used in India. There were no carrier restrictions at the time of purchase, it was purchased fully unlocked.
Even today, it still shows Android Security Patch Level at 1/April/2018. I have enrolled into Samsung Pie beta, and I try everyday to download software manually, but no update has come, either in security patch or in software version. The details are given below:
When I try to update software manually by going to software update - download updates manually, it says 'The latest updates have already been installed. Current version : G960FXXU1ARD4/G960FOXM1ARCA/G960FXXU1ARD6'
When I go to settings - software information, the android version is 8.0.0, samsung experience version is 9.0, baseband version is G960FXXU1ARD6, build number : R16NW.G960FXXU1ARD4, kernel version : 4.9.59-13138374-QB17882910 [email protected] #1 Tue Apr 24 11:50:17 KST2018, android security patch level : 1 April 2018
I have even downloaded Samsung Smart Switch and tried downloading latest software but no use. The message I get there is 'Your software is up to date : RD4(INS)'
Please help. At this rate, I am not sure if I will receive any updates at all, even security patches. I dont know what is the problem.
Thanks in advance.

Flash it manually with ODIN, loads of guides all over XDA if you look

Thanks a a lot.

*Detection* said:
Flash it manually with ODIN, loads of guides all over XDA if you look
Click to expand...
Click to collapse
Thanks.
I have downloaded Odin v 3.13.1. I have downloaded the Android Pie firmware available in Sammobile applicable in UAE and the firmware is G960FXXU2CRLI/G960FOXM2CRLI.
Can I directly update my firmware from G960FXXU1ARD4/G960FOXM1ARCA using Odin 3.13.1 to G960FXXU2CRLI/G960FOXM2CRLI. Please advise.
Thanks.

Kssomu said:
Thanks.
I have downloaded Odin v 3.13.1. I have downloaded the Android Pie firmware available in Sammobile applicable in UAE and the firmware is G960FXXU2CRLI/G960FOXM2CRLI.
Can I directly update my firmware from G960FXXU1ARD4/G960FOXM1ARCA using Odin 3.13.1 to G960FXXU2CRLI/G960FOXM2CRLI. Please advise.
Thanks.
Click to expand...
Click to collapse
Yea, just flash as normal, your bootloader will change to version 2 so you will not be able to downgrade back to that current firmware you are running as it is version 1

*Detection* said:
Yea, just flash as normal, your bootloader will change to version 2 so you will not be able to downgrade back to that current firmware you are running as it is version 1
Click to expand...
Click to collapse
Thanks a lot for the prompt response. I would attempt to directly flash to this version in one step tonight.
Thanks once again.

This is happening to me too...
I have an s9 plus bought from Dubai full unlocked...bt still stuck on December 2018 patch where as other s9 plus recieving April 2019 patch..I'm worried about this..my build number is SM965FXXU2CRLI

Installed Pie update today G965U1

Anyone have any problems that popped up?
On my phone, So far so good. Not noticing anything that isn't working right.
Only had to update 19 apps from the playstore.
I'm using AT&T for my carrier.
One UI version
1.0
Android version
9
Baseband version
G965U1UEU3CSA8
Kernel version
4.9.112-15119402
#2 Tue Jan 15 20:11:43 KST 2019
Build number
PPR1.180610.011.G965U1UE3CSA8
Knox version
Knox 3.2.1
Knox API level 27
TIMA4.0.0

You really made a op about this... Wheres the issue?
PoochyXXX

FastEddieR said:
Anyone have any problems that popped up?
On my phone, So far so good. Not noticing anything that isn't working right.
Only had to update 19 apps from the playstore.
I'm using AT&T for my carrier.
One UI version
1.0
Android version
9
Baseband version
G965U1UEU3CSA8
Kernel version
4.9.112-15119402
#2 Tue Jan 15 20:11:43 KST 2019
Build number
PPR1.180610.011.G965U1UE3CSA8
Knox version
Knox 3.2.1
Knox API level 27
TIMA4.0.0
Click to expand...
Click to collapse
I just got mine today. So far, so good. I guess the silver lining for being last is that everyone else has already tested it on everything.

Software Updated Received Nov 12/13, 2020

Hello all,
The last updated I received on my AT&T Note 4 was the August 1, 2017 Android security patch level, which was probably around September-October of 2017 (obviously I don't remember).
But, mid-morning Nov 12, 2020 I started receiving notifications that a software update was available. I just ignored them, thinking it was some kind of bug. But when I woke up the morning of Nov 13, 2020 I found that my phone had restarted after installing the update. It was waiting on my boot password, and after typing that in it went through the normal "optimizing apps" screen that appears after a system update.
Here is the information from the "About device" page:
Device name
SAMSUNG-SM-N910A
Model number
SAMSUNG-SM-N910A
Android version
6.0.1
Android security patch level
August 1, 2017
Baseband version
N910AUCU2ETI2
Kernel version
3.10.40-8932341
[email protected] #1
Mon Sep 14 16:23:37 KST 2020
Build number
MMB29M.N910AUCU2ETI2
Security Enhancements for Android status
Enforcing
SEPF_SECMOBILE_6.0.1_0029
Mon Sep 14 16:28:02 2020
Security software version
MDF v2.0 Release 6
VPN v1.4 Release 6.1
ASKS v1.2 Release 161011
KNOX version
KNOX 2.6
Standard SDK 5.6.0
Premium SDK 2.6.0
Customization SDK 2.6.0
Container 2.6.0
CEP 2.0.1
Enterprise Billing 1.2.0
OTP 2.6.0
SE for Android 2.4.0
SSO 2.5.0
Shared Devices 2.6.0
TIMA 3.2.003
VPN 2.2.5
So it looks like somebody (Samsung?) in Korea (KST is Korea Standard Time) compiled the Linux kernel on Mon, Sep 14 2020 4:23 pm and pushed out an update. Anybody have any further information?

AT&T has an information page on the update here (I included spaces in the URL which you'll have to remove manually due to forum not letting me post links):
<AT&T Base URL> / device-support/ article/ wireless/ KM1126949/ Samsung/ GalaxyNote4N910A
But there's no information other than the release date was Nov. 10, 2020. Android version is still 6.0.1 (same as last update), and the Security patch level is still August 1, 2017 (same as last update).
The kernel version in this update is 3.10.40-8932341, same as the kernel version from the July 21, 2017 AT&T update, but the compile date of this kernel is Mon Sep 14. So I don't know if Samsung/AT&T applied some patches without bumping the kernel version, or if they just recompiled the kernel for fun.

erichritz said:
AT&T has an information page on the update here (I included spaces in the URL which you'll have to remove manually due to forum not letting me post links):
<AT&T Base URL> / device-support/ article/ wireless/ KM1126949/ Samsung/ GalaxyNote4N910A
But there's no information other than the release date was Nov. 10, 2020. Android version is still 6.0.1 (same as last update), and the Security patch level is still August 1, 2017 (same as last update).
The kernel version in this update is 3.10.40-8932341, same as the kernel version from the July 21, 2017 AT&T update, but the compile date of this kernel is Mon Sep 14. So I don't know if Samsung/AT&T applied some patches without bumping the kernel version, or if they just recompiled the kernel for fun.
Click to expand...
Click to collapse
The information page link is https://www.att.com/device-support/article/wireless/KM1126949/Samsung/GalaxyNote4N910A
It says that the change is to implement a "Network conflict fix".
The build number and baseband version have been updated:
Build number: MMB29M.N910AUCU2ETI (was MMB29M.N910AUCS2EQH1 )
Baseband version: N910AUCU2ETI2 (was N910AUCS2EQH1)
I haven't updated and I haven't noticed any network issues. I'm using a data only SIM from AT&T MVNO FreedomPop which doesn't get updates. I'll probably use an at&t SIM to update in a few days if no one reports any issues with the update.
I took the update around the middle of December (three weeks ago). I haven't noticed any issues or any visual operational changes at all.
`