General DVK1 - ANDROID 13 & One UI 5.0 | GALAXY S21 Ultra 5G | Official Firmware (SM-G998B) | 15th November

Search This thread
Today my phone restarted out of nowhere on 4.1. Did anyone have this issue with the update? Overall the update is very stable and this really surprised me.
I don't have auto restart or any other optimization option turned on.
I've been getting a few random soft restarts (not the same as regular hard restarts) and can't figure out what's causing them. Sometimes phone just hangs and soft restarts.

Thought it could be because of some Good Lock modules, because these kinds of restarts often happen because of SystemUI issues, but I tried uninstalling and kept happening.

No idea what's doing this but I really don't feel like wiping... 😓
 
  • Like
Reactions: MrDusan

Beso

Senior Member
Oct 15, 2008
1,008
92
Samsung Galaxy S21 Ultra

Attachments

  • SmartSelect_20220403-154653_Samsung Keyboard.jpg
    SmartSelect_20220403-154653_Samsung Keyboard.jpg
    276.2 KB · Views: 64
  • Screenshot_20220403-154718_Air command.jpg
    Screenshot_20220403-154718_Air command.jpg
    390.1 KB · Views: 64
Thanks.But on my S22U I have option to write text automaticly.
That's true. But S21U does not gets a signal that an Spen has been pulled out.

I use Spen all the time. If you use Spen on S21U to click in text field, the keyboard automatically selects the handwriting option. As automatic as I had with Note 10+. Not sure how it could be more automatic.
 

Beso

Senior Member
Oct 15, 2008
1,008
92
Samsung Galaxy S21 Ultra
That's true. But S21U does not gets a signal that an Spen has been pulled out.

I use Spen all the time. If you use Spen on S21U to click in text field, the keyboard automatically selects the handwriting option. As automatic as I had with Note 10+. Not sure how it could be more automatic.
My S21U react same as my S22U when I pull out spen. Only ear commands dont work on s21U
 

joloxx9joloxx9

Senior Member
Jul 6, 2011
1,265
387
UK
Thanks for pointing out my mistake and I appreciate the info, but did u resolve the actual question. Is the shared Apk for camera working on your arm exynos phone??
I did not, however if it is made for snapdragon it will not work on exynos not because of architecture but due to different drivers (exynos drivers are not open sourced which is not helpfull)
 
  • Like
Reactions: sn809
I did not, however if it is made for snapdragon it will not work on exynos not because of architecture but due to different drivers (exynos drivers are not open sourced which is not helpfull)
I'd like to believe a lot of samsung's problems with exynos chips are due to the fact that they're not open source. It'd be easier for devs to make proper optimizations to their apps if the drivers were open source but samsung is being too rigid with that
 
  • Like
Reactions: sn809
@MrDusan about the random reboots. They're still happening and I noticed it happened while I was asleep and finally got some logs.

Found this in the logcat:
04-04 06:46:02.816 F/libc ( 8422): Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 8892 (Binder:8422_8), pid 8422 (system_server) 04-04 06:46:05.510 F/DEBUG (18238): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 04-04 06:46:05.510 F/DEBUG (18238): Build fingerprint: 'samsung/p3sxeea/p3s:12/SP1A.210812.016/G998BXXU4CVC4:user/release-keys' 04-04 06:46:05.510 F/DEBUG (18238): Revision: '22' 04-04 06:46:05.510 F/DEBUG (18238): ABI: 'arm64' 04-04 06:46:05.510 F/DEBUG (18238): Processor: '1' 04-04 06:46:05.510 F/DEBUG (18238): Timestamp: 2022-04-04 06:46:03.814164211+0100 04-04 06:46:05.510 F/DEBUG (18238): Process uptime: 58475s 04-04 06:46:05.510 F/DEBUG (18238): Cmdline: system_server 04-04 06:46:05.510 F/DEBUG (18238): pid: 8422, tid: 8892, name: Binder:8422_8 >>> system_server <<< 04-04 06:46:05.510 F/DEBUG (18238): uid: 1000 04-04 06:46:05.510 F/DEBUG (18238): signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 04-04 06:46:05.510 F/DEBUG (18238): Abort message: 'Scudo ERROR: internal map failure (NO MEMORY) requesting 224KB 04-04 06:46:05.510 F/DEBUG (18238): ' 04-04 06:46:05.510 F/DEBUG (18238): x0 <private info omitted>0 x1 00000000000022bc x2 <private info omitted>6 x3 000000751fb69a40 04-04 06:46:05.510 F/DEBUG (18238): x4 <private info omitted>0 x5 <private info omitted>0 x6 <private info omitted>0 x7 <private info omitted>0 04-04 06:46:05.510 F/DEBUG (18238): x8 00000000000000f0 x9 637ee69d1bf54905 x10 <private info omitted>0 x11 ffffff80fffffbdf 04-04 06:46:05.510 F/DEBUG (18238): x12 <private info omitted>1 x13 000000012338a3e7 x14 00303e443289d37a x15 <private info omitted>0 04-04 06:46:05.510 F/DEBUG (18238): x16 00000079b584f058 x17 00000079b582c570 x18 000000751f142000 x19 00000000000020e6 04-04 06:46:05.510 F/DEBUG (18238): x20 00000000000022bc x21 00000000ffffffff x22 <private info omitted>0 x23 000000000003a000 04-04 06:46:05.510 F/DEBUG (18238): x24 000000734d461000 x25 000000734d462000 x26 <private info omitted>0 x27 <private info omitted>0 04-04 06:46:05.510 F/DEBUG (18238): x28 000000734d49a000 x29 000000751fb69ac0 04-04 06:46:05.510 F/DEBUG (18238): lr 00000079b57defe4 sp 000000751fb69a20 pc 00000079b57df010 pst <private info omitted>0 04-04 06:46:05.510 F/DEBUG (18238): backtrace: 04-04 06:46:05.510 F/DEBUG (18238): #00 pc <private info omitted>0 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #01 pc <private info omitted>4 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::die()+8) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #02 pc 0000000000040c80 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::dieOnMapUnmapError(unsigned long)+96) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #03 pc <private info omitted>4 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::map(void*, unsigned long, char const*, unsigned long, scudo::MapPlatformData*)+188) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #04 pc <private info omitted>4 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::MapAllocator<scudo::AndroidConfig>::allocate(scudo::Options, unsigned long, unsigned long, unsigned long*, scudo::FillContentsMode)+512) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #05 pc 0000000000042fcc /apex/com.android.runtime/lib64/bionic/libc.so (scudo::Allocator<scudo::AndroidConfig, &(scudo_malloc_postinit)>::allocate(unsigned long, scudo::Chunk::Origin, unsigned long, bool)+1216) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #06 pc <private info omitted>4 /apex/com.android.runtime/lib64/bionic/libc.so (scudo_malloc+36) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #07 pc 000000000003dc9c /apex/com.android.runtime/lib64/bionic/libc.so (malloc+36) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.510 F/DEBUG (18238): #08 pc 0000000000051df0 /system/lib64/libbinder.so (android::Parcel::continueWrite(unsigned long)+700) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #09 pc <private info omitted>c /system/lib64/libbinder.so (android::Parcel::appendFrom(android::Parcel const*, unsigned long, unsigned long)+352) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #10 pc 0000000000153eec /system/lib64/libandroid_runtime.so (android::android_os_Parcel_appendFrom(_JNIEnv*, _jclass*, long, long, int, int)+52) (BuildId: 5d93c2cf9d9e0c9da924b8b1da837a0c) 04-04 06:46:05.510 F/DEBUG (18238): #11 pc 000000000026fc88 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (art_jni_trampoline+120) 04-04 06:46:05.510 F/DEBUG (18238): #12 pc 00000000007d3dac /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.os.BaseBundle.readFromParcelInner+668) 04-04 06:46:05.510 F/DEBUG (18238): #13 pc 00000000007efc30 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.os.Parcel.readBundle+128) 04-04 06:46:05.510 F/DEBUG (18238): #14 pc 00000000005ec520 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.content.Intent.readFromParcel+1600) 04-04 06:46:05.510 F/DEBUG (18238): #15 pc 00000000005ec48c /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.content.Intent.readFromParcel+1452) 04-04 06:46:05.510 F/DEBUG (18238): #16 pc 00000000005e4090 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.content.Intent$1.createFromParcel+144) 04-04 06:46:05.510 F/DEBUG (18238): #17 pc 00000000007ee860 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.os.Parcel.createTypedArray+240) 04-04 06:46:05.510 F/DEBUG (18238): #18 pc 00000000006d024c /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.app.IActivityManager$Stub.onTransact+43724) 04-04 06:46:05.510 F/DEBUG (18238): #19 pc 00000000019707ac /data/misc/apexdata/com.android.art/dalvik-cache/arm64/[email protected]<email omitted>@classes.odex (com.android.server.am.ActivityManagerService.onTransact+2700) 04-04 06:46:05.510 F/DEBUG (18238): #20 pc <private info omitted>c /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.os.Binder.execTransactInternal+892) 04-04 06:46:05.510 F/DEBUG (18238): #21 pc <private info omitted>8 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot-framework.oat (android.os.Binder.execTransact+296) 04-04 06:46:05.510 F/DEBUG (18238): #22 pc 00000000002ca764 /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb) 04-04 06:46:05.510 F/DEBUG (18238): #23 pc <private info omitted>0 /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithVarArgs<art::ArtMethod*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, art::ArtMethod*, std::__va_list)+880) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb) 04-04 06:46:05.510 F/DEBUG (18238): #24 pc 00000000005a0ff8 /apex/com.android.art/lib64/libart.so (art::JNI<false>::CallBooleanMethodV(_JNIEnv*, _jobject*, _jmethodID*, std::__va_list)+300) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb) 04-04 06:46:05.510 F/DEBUG (18238): #25 pc 00000000000b621c /system/lib64/libandroid_runtime.so (_JNIEnv::CallBooleanMethod(_jobject*, _jmethodID*, ...)+120) (BuildId: 5d93c2cf9d9e0c9da924b8b1da837a0c) 04-04 06:46:05.510 F/DEBUG (18238): #26 pc 00000000001660d4 /system/lib64/libandroid_runtime.so (JavaBBinder::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+156) (BuildId: 5d93c2cf9d9e0c9da924b8b1da837a0c) 04-04 06:46:05.510 F/DEBUG (18238): #27 pc 000000000003c810 /system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+248) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #28 pc <private info omitted>8 /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+1024) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #29 pc 0000000000045ba0 /system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+160) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #30 pc <private info omitted>0 /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+68) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #31 pc 000000000006c500 /system/lib64/libbinder.so (android::PoolThread::threadLoop()+380) (BuildId: dbb5bb014cda8403623b6a0c7db675dc) 04-04 06:46:05.510 F/DEBUG (18238): #32 pc 00000000000120a8 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+260) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0) 04-04 06:46:05.511 F/DEBUG (18238): #33 pc 00000000000beecc /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+144) (BuildId: 5d93c2cf9d9e0c9da924b8b1da837a0c) 04-04 06:46:05.511 F/DEBUG (18238): #34 pc <private info omitted>0 /system/lib64/libutils.so (thread_data_t::trampoline(thread_data_t const*)+404) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0) 04-04 06:46:05.511 F/DEBUG (18238): #35 pc 00000000000b2fd0 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:05.511 F/DEBUG (18238): #36 pc <private info omitted>4 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 673fbd01d6413e96a0627f6f32291870) 04-04 06:46:06.408 E/AndroidRuntime(18154): FATAL EXCEPTION: highpool[1] 04-04 06:46:06.408 E/AndroidRuntime(18154): Process: com.google.android.gms.persistent, PID: 18154 04-04 06:46:06.408 E/AndroidRuntime(18154): DeadSystemException: The system died; earlier logs will point to the root cause 04-04 06:46:06.414 E/AndroidRuntime(18154): FATAL EXCEPTION: main 04-04 06:46:06.414 E/AndroidRuntime(18154): Process: com.google.android.gms.persistent, PID: 18154 04-04 06:46:06.414 E/AndroidRuntime(18154): DeadSystemException: The system died; earlier logs will point to the root cause 04-04 06:46:06.416 E/AndroidRuntime(18154): FATAL EXCEPTION: highpool[2] 04-04 06:46:06.416 E/AndroidRuntime(18154): Process: com.google.android.gms.persistent, PID: 18154 04-04 06:46:06.416 E/AndroidRuntime(18154): DeadSystemException: The system died; earlier logs will point to the root cause --------- beginning of system

I really don't know how to read logs, but it seems like a memory problem from this line:
04-04 06:46:05.510 F/DEBUG (18238): Abort message: 'Scudo ERROR: internal map failure (NO MEMORY) requesting 224KB

I had changed RAM Plus to 2GB instead of the default 4GB, but after seeing this I have reverted and updated to latest CVCG April firmware and I will see if it keeps happening.


I also have tons of these on my logcat:
04-04 06:46:06.414 E/AndroidRuntime(18154): FATAL EXCEPTION: main 04-04 06:46:06.414 E/AndroidRuntime(18154): Process: com.google.android.gms.persistent, PID: 18154 04-04 06:46:06.414 E/AndroidRuntime(18154): DeadSystemException: The system died; earlier logs will point to the root cause

and

04-04 06:45:34.085 E/AndroidRuntime(18042): FATAL EXCEPTION: main 04-04 06:45:34.085 E/AndroidRuntime(18042): Process: com.google.android.gms.persistent, PID: 18042 04-04 06:45:34.085 E/AndroidRuntime(18042): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } in [email protected] 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0$LoadedApk$ReceiverDispatcher$Args(LoadedApk.java:1815) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run(Unknown Source:2) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Handler.handleCallback(Handler.java:938) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Handler.dispatchMessage(Handler.java:99) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Looper.loopOnce(Looper.java:226) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Looper.loop(Looper.java:313) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.ActivityThread.main(ActivityThread.java:8663) 04-04 06:45:34.085 E/AndroidRuntime(18042): at java.lang.reflect.Method.invoke(Native Method) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135) 04-04 06:45:34.085 E/AndroidRuntime(18042): Caused by: java.lang.SecurityException: uid 10318 does not have android.permission.UPDATE_APP_OPS_STATS. 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Parcel.createExceptionOrNull(Parcel.java:2437) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Parcel.createException(Parcel.java:2421) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Parcel.readException(Parcel.java:2404) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.os.Parcel.readException(Parcel.java:2346) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.android.internal.app.IAppOpsService$Stub$Proxy.noteOperation(IAppOpsService.java:1279) 04-04 06:45:34.085 E/AndroidRuntime(18042): at java.lang.reflect.Method.invoke(Native Method) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.lbe.doubleagent.client.hook.e.b(HookedMethodHandler.java:6) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.lbe.doubleagent.client.hook.a.invoke(BinderHook.java:4) 04-04 06:45:34.085 E/AndroidRuntime(18042): at java.lang.reflect.Proxy.invoke(Proxy.java:1006) 04-04 06:45:34.085 E/AndroidRuntime(18042): at $Proxy16.noteOperation(Unknown Source) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.AppOpsManager.noteOpNoThrow(AppOpsManager.java:8529) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.AppOpsManager.noteOpNoThrow(AppOpsManager.java:8507) 04-04 06:45:34.085 E/AndroidRuntime(18042): at aljh.f(:com.google.an[email protected]@22.09.20 (190400-434869283):2) 04-04 06:45:34.085 E/AndroidRuntime(18042): at bxby.a(:[email protected]@22.09.20 (190400-434869283):4) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.google.android.location.reporting.service.LocationReportingController$WifiStatusReceiver.a(:[email protected]@22.09.20 (190400-434869283):12) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.google.android.gms.libs.punchclock.tracing.TracingBroadcastReceiver.onReceive(:[email protected]@22.09.20 (190400-434869283):2) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.lbe.doubleagent.client.a.onReceive(BroadcastReceiverDelegate.java:13) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0$LoadedApk$ReceiverDispatcher$Args(LoadedApk.java:1805) 04-04 06:45:34.085 E/AndroidRuntime(18042): ... 9 more 04-04 06:45:34.085 E/AndroidRuntime(18042): Caused by: android.os.RemoteException: Remote stack trace: 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.ContextImpl.enforce(ContextImpl.java:2273) 04-04 06:45:34.085 E/AndroidRuntime(18042): at android.app.ContextImpl.enforcePermission(ContextImpl.java:2282) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.android.server.appop.AppOpsService.verifyIncomingUid(AppOpsService.java:4510) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.android.server.appop.AppOpsService.noteOperationImpl(AppOpsService.java:3538) 04-04 06:45:34.085 E/AndroidRuntime(18042): at com.android.server.appop.AppOpsService.access$4000(AppOpsService.java:225) 04-04 06:45:34.085 E/AndroidRuntime(18042):

This makes me think that there's something wrong with Google Play Services, but I checked on APKMirror and I have the latest version.

But like I said, I don't really know how to interpret logs.

@dr.ketan maybe you can help understand what this means?

I can upload the full logcat for you if you need.
 
  • Like
Reactions: MrDusan

Top Liked Posts

  • 1
    GeeAyeZee, thank you, I updated and it preserved my data
  • 5
    Android 13 is now available S21 Ultra

    DBT
    Screenshot_20221107-072319_Software update.jpg
    3
    Already available through Frija
    frija.png
    3
    The only malware on your phone is McAfee, trust me.
    Anyone else getting this with todays Link To Windows update?

    View attachment 5762769
    3
    Having been on beta, I am just glad to get Google Pay back :D
  • 36
    In this thread, you can discuss and share the Mega links of new firmwares (OFFICIAL STOCK) for the Galaxy S21 Ultra 5G!
    NO CUSTOM ROM's and/or ROOT-talk

    How to flash the firmware to your phone:

    Odin.png


    1. Extract (un-rar) the firmware file (i.e. to folder C:\Odin) ***
    2. Download Odin v3.14.4
    3. Extract the Odin ZIP file (i.e. to folder C:\Odin)
    4. Open Odin
    5. Power OFF your S21 Ultra 5G
    6. Reboot Phone in Download Mode: Connect USB-cable to your computer. Hold down "Volume up" and "Volume down" at same time. While holding down, connect the USB-cable to your phone. Or use the command "adb reboot-bootloader".
    7. Wait until you get a blue sign in Odin
    8. Add the firmware files to their designated slots (AP in AP, BL in BL, CP in CP, HOME_CSC in CSC). USERDATA stays EMPTY!
    10. Click the start button, sit back and wait few minutes for the device to automatically restart.

    *** You can always find the LATEST firmware in message #2

    I have taken over these threads and they are dedicated to the memory of Henk, you can read more about him here:
    21
    batman-listen.gif

    Greetings to all. Just dropped by for a little more "Unsubstantiated Update Claim Game" or UUCG for short, cleaning! Since this appears to be an ongoing matter, I will be happy to just drop by everyday and remove these little buggers with immediate effect in an effort to keep the thread on topic, which is why some of you reported these in the first place.

    This way, it will eliminate the reports, and save our Mods, me in particular, extra typing practice, even though I need it!

    Cheers to all: Badger50
    pacman-game-over.gif
    16
    You know One great thing noticed in OneUI 5.0 is that battery killer shacking wakelock finally completely removed by Samsung. Just 5 minutes ago it came to my knowledge while digging oneui 5.0 for development purpose.

    @Badger50 sorry for posting oneui 5.0 related stuff but indeed this matter most discussed in this thread so sharing good news that going to happen in future for all! This is something that users on this thread like to hear too!
    Kindly feel free to remove if you find it inappropriate.
    15
    For the love of Pete!! Thread cleaned again!
    Can we PLEASE stop with all the unnecessary back-n-forth with these updates!!!! I keep getting reports from various members about constant OT, griping, whining, this that, he said this he said that, and disrespectful and snarky comments CRAP!! So from now on, if I have to action further reports from members that have been repeatedly warned, I will take up the issue with you regarding XDA Rule #2 for member conduct via PM, which can/may result in disciplinary actions regarding your account.

    So Please, keep this thread "ON TOPIC" out of respect for the OP, and for all other XDA members. THANK YOU!!

    -Regards: Badger50
    15
    I love the tension when an update comes. The anticipation of an update, the climax when it's released and then the oh....that was crap. Cycle restarts.