yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S23 Ultra] pjaysnowden:
Turn off the Download over WiFi toggle and it just won't download the update. It might tell you that there is an update...but it will not force it...and it is totally optional.
[Samsung Galaxy S23 Ultra] blackhawk:
Never was before. Eventually it will force download it and install. If it's an AT&T variant and goes near an update tower, bam!

The only other way is to request the carrier to block OTA updates.

View attachment 6049987
[Samsung Galaxy S23 Ultra] pjaysnowden:
In Europe, this is definitely not a thing. You can permanently defer the updates.
[Samsung Galaxy S23 Ultra] blackhawk:
Europe's a different animal. Much better consumer protection.

I have a carrier N10+ and an unlocked N10+ (N975U, N975U1 respectively). The AT&T variant will definitely behaves this way and as for the unlocked one I'm not taking any chances of it happening.
[Samsung Galaxy S23 Ultra] bodomfan:
This is one UI 6 December patch
[Samsung Galaxy S23 Ultra] blackhawk:
How bright are you running it?

Try using manual brightness control. Double check display settings. Toggle Developer options off, then back on. Clear system cache...

The phone usage seems excessive too.

Network reset and clear the Sim Toolkit data.
[Samsung Galaxy S23 Ultra] bodomfan:
This bright,that's over a day into day 2,so 6 hours sot in the first 24 hours 4 hours 50 after
[Samsung Galaxy S23 Ultra] bodomfan:
This is now (see pic)
[Samsung Galaxy S23 Ultra] blackhawk:
That looks reasonable. The apps seem to be hungry though...

Using the SD Maid pro version to clean it never hurts.
[Samsung Galaxy S23 Ultra] bodomfan:
Do you mean clean cache of gsam app
[Samsung Galaxy S23 Ultra] blackhawk:
You think the problem is that app?

SD Maid Pro can help increase SOT and system speed. I use it about once a week and clear the system cache many times as well. Galaxy App Booster also helps.
[Samsung Galaxy S23 Ultra] bodomfan:
What setting do you use in the app
[Samsung Galaxy S23 Ultra] bodomfan:
My sot is very good
[Samsung Galaxy S23 Ultra] blackhawk:
Quickacces, mostly default settings.

Review the settings first.

SD Maid has a good track record for me, zero damage. I clear the Memory first in Device Care and immediately run Quickacces then.

View attachment 6050064
[Samsung Galaxy S23 Ultra] bodomfan:
Done 👍✅
[Samsung Galaxy S23 Ultra] blackhawk:
Don't know if it will solve your problem but it's the only cleaning app I use other than Device Care.

My last factory reset was over 3.5 years ago so it does a good job. It cleans up my SD card as well. It removed a bunch of uninstall garbage that other apps couldn't touch on a stock phone.
[Samsung Galaxy S23 Ultra] bodomfan:
Nice ,I'll keep using it from now on ,thanks for the tip 😀
[Samsung Galaxy S23 Ultra] easyrider77:
So I did notice that it looks like the battery stats get reset every day, wtf Samsung?!?!

So I'm thinking battery life may not be so bad after all.

Notice in both the battery is 29% that's a day plus over into the next morning. These pics are 2 different days, one is like 5ish pm on Sat, the other is Sunday morning at 9ish. I never plugged in to charge at all, so the battery stats are getting reset at some point. My guess is, it resets at around midnight, but sure honestly, but I do know it's getting reset, the pictures show that.

Normally it won't reset until you plug in then phone and hit 80% but not now, I hinestly don't get it

So I gotta ask, what gives? Why the reset every day?? Not liking this oneui 6 at all 😞
[Samsung Galaxy S23 Ultra] blackhawk:
That's why I use Accubattery. For it's history page mostly and battery temp when charging.

It gives the bottom line for each session. Once activated I firewall block it.

View attachment 6050217
[Samsung Galaxy S23 Ultra] easyrider77:
Ty, I was looking for an app, problem is, if battery stats resets every day on the phone will accu battery read from that or does it read it a different way?

Not sure why Samsung thought it was a good idea to reset it every day rather than per plug in, to me it's hard to keep track of battery if you. Just reset it mid stream. Seems like it would be more accurate like it was, per plug in as apposed per day, but that's just me in guess
[Samsung Galaxy S23 Ultra] blackhawk:
It runs ok on Android 9 and 10 with no adb edits needed. Not sure how it does on Android 11 and higher. I'm sick of the new Gookill scoped storage junk and refuse to use it.
[Samsung Galaxy S23 Ultra] easyrider77:
Well I'm either doing something wrong or else it's not working.

So when I open the app, go-to the charging tab, where it shows the sot, charging since section, right above that it shows a session time.

It shows from and to, but when it shows the session it shows less than a a min, ie: 12:00 to 12:00. Forward to about 5 mins later it then shows 12:05 to 12:05 and shows 0% screen on time.

So, is there a setting in missing or is it just not working

I do have notifications off, so I'll turn that on see if it fixes it
[Samsung Galaxy S23 Ultra] blackhawk:
In it's settings turn on disable task killing.

Leave it run in the background.

Try a reboot and clearing the system cache.
[Samsung Galaxy S23 Ultra] easyrider77:
Nevermind I'm stupid lol

That was the charging tab ie: for when the phones charging, looking at the discharge tab it works rofl

Sorry for the confusion, senior moment
[Samsung Galaxy S23 Ultra] easyrider77:
Update:

I think samsungs new ui6 has some issues, specifically with battery stats.

I charged my phone 45m ago and unplugged full charge.

Now Samsungs says it has a 3h sot, how is that possible after unplugging full battery?????
[Samsung Galaxy S23 Ultra] blackhawk:
That looks like about 7 hours SOT to me.

What's Accubattery history say?
[Samsung Galaxy S23 Ultra] easyrider77:
It's the 2nd pic.

Accu battery is showing things correctly, samsungs battery stats are fubar.

Typically android after 80% resets the battery stats counter. I know this because I tested it out twice, once in my s21 ultra, and then on my s23 ultra, before oneui 6 of course, in think it was either 5 or 5.1 I tested it on.

So...... That given even after unplugging at 96% vs 100% it would still have reset the battery stats counter and restarted it after I unplugged the power cable.

Once I unplugged the cord at 96% Samsungs battery stats tell me I had 3h sot and 47% usage.... That is a physical impossibility.

In 6% of battery down to 90% it said this. There is NO possible way for a battery to use 47% and 3 h sot in 6% use if the battery, no way no how.

Now accu battery tells me I had used it like 2% and like 45min sot, now THAT I can believe

Samsung messed up the battery stats somewhere 🤷

All this time accu battery has been spot on with everything and every time I check it

Here is a pic of the very very latest stats in history
[Samsung Galaxy S23 Ultra] blackhawk:
That's why I said to use it. It's not perfect but better than Device Care battery management.

Again clear the system cache on the recovery menu as this can cure many different types of erratic behaviors.
[Samsung Galaxy S23 Ultra] easyrider77:
Yep did that about 3 days ago. I decided to clear it and see what happens but it's obvious samsungs battery stats are seriously messed up. That much is obvious in accu battery and it showing things correctly.

In all honesty, seriously regret upgrading. Samsung was doing SO well before this update.

I got an offer from VZ earlier today, they will pay off my s23 ultra on tmo, give me the same monthly payments for service and same monthly phone payments I'm paying now for a pixel 8 pro.

I am giving it some serious serious thoughts, but I'm leaning heavily on just ditching Samsung. I did once before with the entire TouchWiz crap, this has that same vibe and feel to it with this oneui 6 update.

Reading on multiple forums more people than not are NOT happy with oneui 6, and looking on Samsung forums there are a LOT of issues cropping up. Saw one that had a camera issue, one had a OS color issue. Oneui 6 is just a hot mess, and I want no part of it. Brings back bad dreams of the TouchWiz days 😞😞
[Samsung Galaxy S23 Ultra] blackhawk:
Your other option is a factory reset, that may tone it down or reflashing to the previous version if that fails.

That's one reason why I continue to run on Android 9 and 10 on my N10+'s. Less downtime means more playtime. They continue to fullfill their mission and are a joy to use.

Both Android and Samsung are a mess now...
[Samsung Galaxy S23 Ultra] easyrider77:
Yep agreed. They did a good thing with oneui then they are just slowly destroying it.

If I flash 5.1 again that's all fine but.... It's inevitable that oneui 6 will eventually show up and android will auto install it again, so I'd be chasing my tail doing that.

I miss the good ole days of nexus 5 and 6 and ease of root if you so wanted.
[Samsung Galaxy S23 Ultra] blackhawk:
You use adb, ladb or Package Disabler to block it.

Bonus it no longer wastes resources in the background. All Samsung's should be optimized.

I currently block about 75 packages. This N10+ was a hot running battery eating hog before it was optimized. Optimizing doubled it's SOT.

View attachment 6050370
[Samsung Galaxy S23 Ultra] easyrider77:
Well knock me down and call me shorty lol

So must those 2 will stop updates from auto. Installing?

Also what else do those affect like with other updates and such, will it still update the play store and such?

And if I disable those will they come back? I know with some things you remove it, it just comes right back. Don't remember the name of what it was I was trying to get rid of, but I'd delete/remove it, and as soon as I refreshed the list it was there again.

I bought and use ADB app control which works very nicely, so it won't be a problem getting to the files to disable or remove.
[Samsung Galaxy S23 Ultra] blackhawk:
Not sure what it updates, might Framework which I also block. I don't let Playstore run either.

I doesn't effect my ability to install apps though.

If blocked they never load at boot so they can't interact with the system. OTA updates has all the permissions under the sun but this kills it.

That's all you need although I prefer Package Disabler as I can block/unblock on the fly. LADB edit apps have this capability too I believe but that won't run on Pie. LADB needs Android 11 or higher to run.
[Samsung Galaxy S23 Ultra] easyrider77:
I forgot to ask..... This is a Verizon branded s23 ultra.

I know they aren't rootable, unless that's changed, if that is the case with not being able to root, will me using odin flashing back to 5.1 have any ill affects with it being a Verizon branded phone?

I do realize rooting and flashing odin are different, just wanna make sure since vz pones do not like to be rooted, if odin flash would have any bad after affects as well.
[Samsung Galaxy S23 Ultra] easyrider77:
Ok ran into a snag, need some help.

Phone model is SM-S918U a verizon s23 ultra. It has the latest oneui 6 update.

I grabbed the latest SM-S918U android 13 file from the samsung site.

I Ioaded 4 files into their corresponding slot...........BL file into bl slot, AP file into the AP slot, CP file into the CP slot and CSC file into the CSC slot. Re-partition is NOT selected, Auto reboot and F. Reset time are both check marked.

I hit start and get this info in the window:

<ID:0/009> Set PIT file..

<ID:0/009> DO NOT TURN OFF TARGET!!

<ID:0/009> Get PIT for mapping..

<ID:0/009> Firmware update start..

<ID:0/009> NAND Write Start!!

<ID:0/009> SingleDownload.

<ID:0/009> abl.elf

<ID:0/009> bksecapp.mbn

<ID:0/009> FAIL! (Auth)

<ID:0/009>

<ID:0/009> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

and it fails.

What if anything am I doing wrong? Do I not need the cp file??

Any help is appreciated

Update: I am tried without using the CP file and it failed again. This is what it gives me:

<ID:0/009> Odin engine v(ID:3.1301)..

<ID:0/009> File analysis..

<ID:0/009> Total Binary size: 10872 M

<ID:0/009> SetupConnection..

<ID:0/009> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

So I am under the impression not only can vz branded phones be rooted, but they can't odin flash downgrade either? Dunno maybe I'm wrong
[Samsung Galaxy S23 Ultra] kin201303:
The US version cannot be used v(ID:3.1301) ,

use Odin3_v3.13.3b

Odin3 v3.13.1_3B_Patched_Auto_patech.rar | by PabloSBA_SURI for -All-General-Generic-

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Samsung Galaxy S23 Ultra] KantmiS:
Where I can find SM-S918B A13 EUX firmware with bootloader 3? Can't find in samfw.
[Samsung Galaxy S23 Ultra] _GRIZZLY_:
Are tried download from first site this thread?

Download Galaxy S23 Ultra SM-S918B (EUX) S918BXXU3BWJM in Samfw - Samsung firmware download

Galaxy S23 Ultra SM-S918B (EUX - European Union) S918BXXU3BWJM U(Android 14) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅

samfw.com

Or use sammobile site from this link:

Not Found

www.sammobile.com
[Samsung Galaxy S23 Ultra] enjynox:
please bro I have S918BXXU3BWJM and CEC is EUX can you give me the correct frimware for my s23u to downgrade to 5.1
[Samsung Galaxy S23 Ultra] kin201303:
you cann't downgrade to 5.1

3BWJM ,5.1 is 1AWD1,the number must same

View attachment 6066932
[Samsung Galaxy S23 Ultra] blackhawk:
The same or higher.

That's what I always thought.

Apparently on some Samsung models with locked Snapdragon's people have gotten around this. I think it was S21 or 22 but it was about 2 months ago on XDA and finding that thread be near impossible.

Maybe someone has a better plan...
[Samsung Galaxy S23 Ultra] KantmiS:
Not Found

www.sammobile.com
[Samsung Galaxy S23 Ultra] enjynox:
what about this: Can I flash with this

Model	SM-S918B
Product Code	EUX
Security Patch	2023-08-01
OS Version	Android 13
PDA	S918BXXU3AWGJ
CSC	S918BOXM3AWHH
Build Date	2023-07-28
Changelist	27100863
[Samsung Galaxy S23 Ultra] t-shock:
Use this one to downgrade to Android 13. It has October's security patch

Download Galaxy S23 Ultra SM-S918B (EVR) S918BXXS3AWIF in Samfw - Samsung firmware download

Galaxy S23 Ultra SM-S918B (EVR - United Kingdom) S918BXXS3AWIF T(Android 13) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅

samfw.com
[Samsung Galaxy S23 Ultra] kin201303:
yes you can
[Samsung Galaxy S23 Ultra] UdashinAj:
Is it successful at last?
[Samsung Galaxy S23 Ultra] easyrider77:
Nope it fails sadly. It's a verizon phone so that may be something to do with it.
[Samsung Galaxy S23 Ultra] kin201303:
you must use Odin3_v3.14.1_3B

for usa verizon

SM-S918U S23 ULTRA/918U1 UNITED STATES FIRMWARE FLASHING

Most of us already know how to flash firmware with Odin. Here, anyone can post available firmware for everyone to use as well as general discussion. U firmware can be flashed on a U1 device and U1 firmware can be flashed on a U device using Odin...

xdaforums.com
[Samsung Galaxy S23 Ultra] SayamHossain:
I want to downgrade my S23 ultra from stable 6.0 to 5.1.

Can anyone give me step by step guide.

I am not worried about warranty.
[Samsung Galaxy S23 Ultra] dannytgt:
I'm searching the same, apparently the only avalaible method is trought Odin, but my S23 ultra A14 binary is 3, and there's no Android 13 binary 13 avalaible software.
[Samsung Galaxy S23 Ultra] djoxie:
There are several step-by-step guides on youtube for it, look for the ones from creators TechiBee or munchy.
[Samsung Galaxy S23 Ultra] SayamHossain:
S918BXXS3BXBB is my binary. can I downgrade ?
[Samsung Galaxy S23 Ultra] SayamHossain:
those are for beta to stable not for stable to stable
[Samsung Galaxy S23 Ultra] djoxie:
Procedure is the same
[Samsung Galaxy S23 Ultra] _GRIZZLY_:
Look for this:

How to Downgrade One ui 6.0 to 5 on S918BXXS3BXAD

Hi, I'm planning to Downgrade one ui 6.0 to one ui 5 on my s23 ultra(csc: iraq). But I don't understand which one to flash(A13).

xdaforums.com

And this

Downgrade from official oneui 6 too oneui 5.1

So I finally got the oneui 6 official update. It's been about 2 weeks and my battery life has gone from avg of 10h sot, normally down to 10% at that point, to now at 32% I only have 6h sot. I haven't had time to drop it to 10% yet to see if I...

xdaforums.com

Third same topic isn't need and you can only search in first few pages this s23u section ;)
[Samsung Galaxy S23 Ultra] butchieboy:
If you are trying to go back to bit 2 you can't. If the firmware you want to flash is the same bit number as what you currently have then yes

Samsung Galaxy S23 Ultra Firmware Download SM-S918B Free Download

Samsung Galaxy S23 Ultra Firmware Download SM-S918B Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website

samfw.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] P3lUZa:
Running:

alioth:/ # fsck.f2fs -f /dev/block/bootdevice/by-name/userdata

gives:

Info: Force to fix corruption

Info: No support kernel version!

Info: Segments per section = 1

Info: Sections per zone = 1

Info: sector size = 4096

Info: total sectors = 27865083 (108847 MB)

Invalid SB CRC offset: 2447990271

Can't find a valid F2FS superblock at 0x0

Invalid SB CRC offset: 3500443924

Can't find a valid F2FS superblock at 0x1

Also trying to decrypt with TWSP:

alioth:/ # twrp decrypt

gives:

Attempting to decrypt data partition or user data via command line.

Decrypt process ended with signal: 6

Failed to decrypt data.

Is there anything I can do to fix the partition or recover my data?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DarthJabba9:
If what you want is to format the data partition to get rid of the corruption, try booting into bootloader, connect the device to a PC via USB cable, and then running "fastboot -w". This should format the data partition (you will lose all data).

If that doesn't fix the problem, you might need to flash a stock MIUI fastboot ROM, using the Mi Flash tool (just make sure you don't accidentally re-lock the bootloader).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] P3lUZa:
No, what I want to do is to fix the partition and recover my data. I didn't update or anything, I just rebooted the phone and stuck in a bootloop, thats no sense.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] blackhawk:
Wasn't a stable load be it a buggy 3rd party app, maybe malware, possibly a hardware failure or a SEU (single upset event). Chances of recovery aren't good especially if you can't access the encryption keys. If the encryption key(s) were corrupted you're boned. A SEU is rare, only toggles one bit of data, and causes no hardware damage but if it's a critical keystone data bit it can cause hell.

To avoid these kinds of tedious situations always back up critical data redundantly.

Androids rarely crash and burn but it can and does happen.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] P3lUZa:
Is there any tutorial on how to use f2fs dump for Poco F3 (or similar)? I haven't touched anything yet
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] P3lUZa:
Nobody?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] M47Z:
I currently have the same issue as op on a Redmi Note 9S with LineageOS for microg 19.1. It seems f2fs corrupting and then phone not booting is becoming quite a common issue since android phones started using f2fs. So anyone reading this in the future I just recommend you stick to ext4 if possible. Negligible gain in performance is not worth your phone randomly losing all your data.

Back to topic: I think I know how to dump the partition. But keep in mind that besides it being broken it's most likely also encrypted. And the encryption key is NOT on the partition itself, it's NOT just your password, pattern etc. Afaik the keys are stored in a secure location on the soc itself. Usually, you give the soc your password, and if it's correct it will allow access to the keys needed for decryption. But in our case that means: We need those keys to have any chance recovering files from this partition outside the phone. Only alternative could be fixing the partition image outside the phone and then flashing it back, no idea if that would work.

Anyways how to backup the userdata partition, only works on unlocked phones and possibly needs microsd slot.

- put a large enough microsd in

- boot to recovery

- enable adb

- connect to pc

- on pc enter "adb shell", you should now have root access to your phone

- read first before you continue! For me the command to backup the userdata partition to microsd card was:

But the part highlighted, soc/1d84000.ufshc, depends on the device. You have to use the terminal to navigate to /dev/block/platform/ and then search through the subfolders until you find the one containing by-name/userdata. Also make sure your sdcard is mounted and actually at /sdcard1. Then adjust the command above accordingly and run it

- check your microsd on another device, should be around the size of the internal storage of your phone

(If your phone does not have a microsd slot there is probably a work around involving a usb hub and thumb drive but you'd have to figure that out by yourself)

So now that you have the partitioned backed up, let's get to the real question:

How to fix it?

When I try to use fsck.f2fs on the partition on the phone itself through adb I get:

Any idea how to fix the file system? Or maybe even how to decrypt an android userdata partition outside your phone, aka dump the keys somehow?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] shaymala:
Thanks for explanation. can you please clarify what do you mean by critical data (user data or firmware and etc.)?

and if you meant other than user data , do you know anyway to backup firmwares or kernels or things like recovery partitions (any other systematic data) to fix software bricks and bootloops if happened in future .
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] blackhawk:
All user data which is critical to you and can't be easily recreated. Pictures, documents, contacts, bookmarks, notes, music/movie files, passwords/login names and older apps.

Any app that allows for complete backups like Poweramp should be on the data drive.

Backup whatever is in the download folder that you wish to save. Take some time to properly organize your folder system.

NEVER encrypt or password protect SD cards or data drives!!!

Firmware ie default settings are backed up.

User settings are best redone after a factory reset ie a clean hand load.

Bootloops are very rare and generally easy to avoid. 3rd party launchers and power management apps that load at boot up are prime suspects. Bad choices when disabling packages can do it too. For both error on the side of caution. Viruses could do it as well; be careful what you install.

Toss any apps that give the slightest hint of being unstable. Any time you see instability on an Android take it seriously and correct the cause asap as a bootloop could happen on the next reboot! Avoid "sampling" apps for no good reason. Poorly coded apps can alter hidden user settings and then not cleanly uninstall, this is rare but it happens.

Vet of files in the Download folder before moving them into the database. At the very least open them and look for any unusual behavior with them or in the download folder.

Scripted jpegs are real and can damage anything that's in the same folder. Put files into a folder (especially jpegs and media files) before transferring them to the database as it gives some isolation and protection. Delete any unknown files found in the download folder without opening them! Occasionally scan with Malwarebytes but nothing can detect all malware. Pay attention to the device's behavior; Android's should be rock solid stable and predictable. Any deviation from this could suggest malware.

Apk Export can be used to make installable copies of apps including system apps. There are other utilities that do this as well like Package Manager from Playstore. The latter maybe easier to use. All my apps and system apps are backed up and kept on my data drive; everything I need to do a full reload. Not using Playstore during a reload saves time and guesswork.