yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
Is there documentation somewhere on exactly how that works? I really want to play with it
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jeffyv2:
Do I need to check anything or it won't have options when flashing?

Sent from my SM-G955U1
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jrkruse:
Don't do that none of your proximity sensors will work or auto brightness. Non-hlos.bin needs to match the bootloader
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fachadick:
I get this sometimes, but I don't need to reboot to fix. I found that it's specifically tied to autobrightness. The next time that happens, uncheck autobrightness and turn off the display for a few seconds. Then turn the display back on. Phone should look and act normal, and you can turn the autobrightness back on. And for the record, I followed op also.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] thesavagetony:
Interesting. Thanks for the reply - I'll try this.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jrkruse:
Its not auto brightness it happens too me and I dont use auto brightness and it only happens too certain phones my other s8+ it never happens too. Simple turning screen off and back on fixes it
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
I wonder how much we can alter for SM-G955U/950U via misc partition boot commands allowed with ENG boot?

cat /proc/cmdline

[MENTION=3812611]elliwigy[/MENTION]

Good question. I am on the go right now and have attached my misc.img that I dd copied just now. In Hex Editor Free, I preliminarily do not see any non-zero data, but I would need to scrutinize it later in wxHexEditor in Windows to be sure.

https://sourceforge.net/projects/wxhexeditor/files/wxHexEditor/v0.23%20Beta/wxHexEditor-v0.23-Win32.zip
[MENTION=3812611]elliwigy[/MENTION] may know more info, because he first mentioned same. :)

/dev/block/bootdevice/by-name/misc
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fachadick:
Weird - if I don't turn off autobrightness it won't fix itself. Maybe autobrightness just has to be off when you turn the screen off and back on?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] hazmad:
I'm running AQG3 BL and AQGL non-hlos with no problems whatsoever
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
I found content://com.android.chrome.FileProvider/BlockedFile_8544906087356 which looks like it might be how to do it. I will try to build the tools or dd it later on after work and see if I can read anything from it
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jrkruse:
Yes thats probably fine your running updated bootloader and boot.img just dont try it with original files in the OP

Still wont fix the yellow screen issue though. It may help but it still does it on mine
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
*EDIT* I came off too hard here. Rewriting

---------- Post added at 11:03 PM ---------- Previous post was at 10:30 PM ----------

Pardon?

I did this already and everything works fine. In fact things are running better than ever.

Sorry, but what you are saying makes absolutely no sense based on how the boot process works. In general terms that absolutely apply to Android, bootloaders are designed do one thing and one thing only: find a kernel in a preconfigured place and execute it with the right commands and the right safeguards. They literally do not have operating systems! Setting up hardware is very difficult and basically a dark art. They only implement the bare minimum stuff necessary to get to the next stage: 1st boot -> 2nd stage, second stage -> kernel + ramdisk image (for s8s anyways, replace with a hard drive on other systems). Nothing in the boot process pre kernel would have sny need to talk to the sensors, and it would be a huge pain to get them working, so why do it?

Even if they were say on the same controller as the buttons (for dl/recovery/upload modes), running context gets completely reset after each boot step which would reset the controller anyway.

Finally, if you ran sampwnd you are already running in a split brain config, as some boot files are eng and some are from combo. Just like (almost, 99.9%) of Linux kernels can boot any Linux os (and 100% of stock kernels in wide ranging distros such as AOSP) as long as they have the right drivers built in or loaded as modules and are for the right architecture. None of those things will vary across version's of firmware for the same hardware.

Don't believe me? Go download the s8 kernel source from samsung. It's a stock Linux kernel with a specific config, nothing magic.

Given all that, there's just no way i can justify believing what you are saying is true without documentation that backs it up. Do you have a source from a system engineer with bootloader experience at the firmware layer? A TW/android engineer at Samsung?

TBH, what this SOUNDS like to me is the anecdotal stories you hear from people who flash stuff without really understanding any of what they are doing and something goes wrong. They have no idea what to do and if they get no help from XDA, they will likely randomly do things over and slightly different to try and "fix" it and ultimately succeed but for different reasons than they think. This misattrubution gets repeated like a game of telephone, and eventually everyone believes it without question.

One need look no further than the plethora of questions early on in the s8s life on XDA about root/TWRP for snapdragon us devices as so many SEO root sites autogenerated instructions for it despite it bricking your device. Another good example is build.prop tuning, that's something I could rant about all day :).

Sorry for getting on my soapbox a bit there. I just want to see everyone lean everything they want to correctly, and android system changes on your device are nondeterministic enough already without adding less than real stuff to it :D
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
if u cat or look at it using a file explorer it will be blank.. when u echo a command into the partition then reboot to recovery afterwards u can look in the log and see it..

i found this while on eng system.img as there is a "libengmode.so" that talks about FRIGATE_BIRD and steady and misc partitions to enable "ENGMODE" or "EM"

i couldnt figure out what goes where.. theres also an ffbm mode which writes ffbm-01 into the misc partition..

i started looking into this bcuz on hk/ch models the crom service writes a KIWIBIRD flag to the steady partition to unlock the BL..

so i assume if we can figure out what mode we can set in misc or steady partition to unlock the BL we might be in luck but its hard bcuz there isnt any publicly available method to unlock our variants for us to know what it looks for..

similar to other devices with fastboot/qualcomm a few years ago they could write "bp-tools" into one of the two partitions and it would put them in a special mode etc etc

i cant find much documentation on QC or sammy boot modes as it typically only talks about verified boot which is something else
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Araltd:
This brings up my question I asked earlier which never got a reply. Are the files on the OP still relevant? Seems like there are updated files that could potentially be flashed to get better performance and results?

Personal rant: Coming into this thread with 300+ pages is hard to play catch up. The first 70+ pages are fixes to the initial ADB commands issues, the last ## pages are dev talk, Sigh I guess somewhere in the middle is what needs to be read :(
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] IJoxer:
And that is why we have that box up there that allows you to search certain key terms in order to sort through that vast number of posts.

Short answer is yes, they are the current needed files to root, but I challenge you to search beyond that. I'll give you a hint, for step 2, you can use updated firmware files to update, but the only versions I'm aware of already recompiled is for (955U)QGL and (955U1)QH3, and they're located here. Be sure to thank [MENTION=1949695]jrkruse[/MENTION] while you're there! :good:
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
Actually... YES!

I'll give you all a sneak peak....

Attached is a screenshot of my (unmodified) stock default.prop from my new possibly-from-oreo android AQI1 permissive kernel! I found this puppy on a firmware site this morning (see the date it's pretty brand spanking new) and paid for a month long membership just to get my hands on it! (one of the better $15 I've spent in my life) and flashed it successfully on my rooted s8 w/ a G950U1UEU1AQH3 based system, modem, etc, VZW CSC, and the userdata from the G950US____, which if you're not familiar has a whole extra tar.md5 userdata package which I flash to start my installs off as it gives me the VZW specific settings menu that so many people hate but I love for some reason :D. Since flashing the AQI1 boot.img which contains a new kernel and since first booting it I have had NOT ONE incident of the "green screen" or any other kind of screen issue! With the old kernel from the sampwnd boot.img I would have had at least 3 if not more by now. At this point I'm comfortable declaring the screen bug "fixed" at least with the 950u VZW us s8 and the h3 firmware w/ sampwnd. I have no way to test any other model s8 or s8+ as i don't posess them.

I will be downloadingg the 955u combination firmware when I get home tonight from work (I paid for a month long membership to the site) and then I will post both the firmwares for each device and a handy boot.img only for all of you who want to fix this bug too :). Keep an eye out tonight for it!

As of now I have NOT found or seen a user build of AQI1 JUST the combination rom, but I will keep a close eye out and see what I can find. Maybe if I get some free time I will try and cobble together a custom system & data only hybrid rom of the proper Oreo apps/framework that comes with the combo firm and the rest from h3 where stuff's missing, but then again that might fail miserably and could be a terrible idea lol.

If you have a sampwnd rooted s8 this is not an update to miss! Flashing boot.img and radio firmwares does not require a data wipe I just wiped cache to be careful!

My screen is responsive and smooth, my network connections way better (could just be learning that flashing CP in Odin alone does nothing as all the rom binaries are in ap and bl lol), my battery lasts longer (still 80% though, although I have some ideas there to test as well), and I couldn't be happier :D

I'll update this thread when the post is live since you all may be expecting it.

Attached is a screenshot of my new default.prop (unmodified naturally) so you can have a sneak peak :)
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] IJoxer:
Oh boy, I'm hesitant to get excited just yet until I see some uploads, but I can't help but be anxious!!!

I may just be pulling an all-nighter now, just so I can test as soon as you post the files! :silly::D

If you get a moment, do you mind telling us exactly what you flashed? I ask because I was tinkering with a little something myself concerning Oreo, and though I haven't been too hopeful yet, you just boosted my confidence that it may just work. I'm very much looking forward to any updates on this, just hoping for some quick clarification as to what you flashed specifically, if possible.

Excellent post! Thank you for sharing!!!:good:
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
lol thats not new.. most including myself dont have screen issues but simply toggling the screen off and on works lol.. but yes, any combo firm boot img works and they are conetantlyvreleasing factory binary firms
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mopartonyg:
Great find , is this for S8 or S8+?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
99% sure they have both. I pulled down the s8 ver this morning and am running it. When I get home (shortly) I will pull down the s8+ ver and I'll share both

---------- Post added at 03:18 AM ---------- Previous post was at 03:15 AM ----------

Lol the build date is 9/4. Bring built 11 days ago (it's only been up for a few days) makes it pretty new for a firmware in my book.

It's even marked "new" on the site lol
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
lol not saying its not new just saying combo firms are released all the time and i always update to latest one i can find, i assumed others did too lol
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mopartonyg:
If it is ok to ask , where does an interested party find the newest combo firmware?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
they are all over.. some sites will charge a few bucks.. u can try z3x server or other forum sites
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Araltd:
So you guys are flashing the boot.img from the combination firmwares? Just over your existing setups?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mdiaz33685:
may one of these updates have a cure for this wicked sickness of the 80% battery fix attached to one of these releases.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] dogredwing1:
Yes that's what I did, works great
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
You are running the combo boot if you rooted with sampwnd.

FYI I finally got the s8 thread about this up: https://xdaforums.com/galaxy-s8/development/sampwnd-green-screen-corruption-fixed-t3673782

I'll have the s8+ one up soon
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
S8+ is up now: https://xdaforums.com/galaxy-s8+/development/sampwnd-root-green-screen-corruption-t3673815

Enjoy!
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] masterzoltar:
Guys I have no idea what is going on on this phone. I have rooted mine and everything works perfect. My wifes on the other hand. It was a verision asurion replacement s8 plus. Im having nothing but problems. Not receiving texts, hurricane icon on notification bar. Ive tried reflashing and cannot get anything to fix it. Used the exact same firmware as on my phone. Obviously an apn issue. Cant seem to solve it.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
Sort of.. you need 4 partitions, just the boot wont do it.. u need abl.elf, devcfg.elf, boot.img and recovery.img from combo, but yes, newer versions seem to run slightly better imo

forgot to respond to this.. answer is a big fat NO
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
lol not really a fix but all good man, illvisitjust for the combo firm haha iamcurrently on AQG3 combo
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] unhcoffee:
Return to Stock From Root

Rooting the phone following the directions worked fine, but I was attempting to return the phone back to stock and got stuck.

The original instructions say:

- It is possible to return to 100% stock and it is very EASY to do.

- This is the reason why I provide both Normal, and Comsey ODIN's.

- All you need is a full stock 4 files firmware of your choice.

- Extract those files. Open ODIN and select the 4 files in their respective slots.

* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)

* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.

I have a G950USQS1AQG1 phone and got the stock G950USQS1AQF7 AP, BL, CP, AND CSC files. I first tied Comsey ODIN to load all to the phone (in download mode) and got the model mismatch error. I tried again using the BL only in the Normal ODIN, but got this set of logs. When I reboot the phone, it stays at the ATT logo for awhile, but eventually got back into phone, but it was still rooted.

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin engine v(ID:3.1207)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection.. <==Soft rebooted phone here back into download mode because nothing was happening.

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

<ID:0/006> Removed!!

<ID:0/006> Added!!

<ID:0/006> Odin engine v(ID:3.1207)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

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

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

<ID:0/006> Can't open the specified file. (Line: 1834)

<OSM> All threads completed. (succeed 0 / failed 1)
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] davidisflash:
Best. Butt dial. Ever
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] masterzoltar:
Returned to stock and redid everything using the u1 firmware and all is good now. Who knows.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mdiaz33685:
Returning to Stock:

- It is possible to return to 100% stock and it is very EASY to do.

- This is the reason why I provide both Normal, and Comsey ODIN's.

- All you need is a full stock 4 files firmware of your choice.

- Extract those files. Open ODIN and select the 4 files in their respective slots.

* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)

* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.

PS.. when I returned to stock I did select nand erase the same way we did root, cause the first time that happened, then I did 1 at a time, then when it stopped at 32% in recovery just wipe cache, and data is what I did, then the 2nd time I did it with the nand erase and I did the full firmware and it went through fine...
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
¯\_(ツ)_/¯ still not a single screen hiccup when otherwise I'd have had many by now
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] unhcoffee:
Thank you, I tried this next.

1. Booted phone into Recovery Mode.

2. Wiped both the cache and data.

3. Rebooted to Download Mode.

4. Used Normal Odin (V3.12.7 as administrator) to upload stock BL (with Auto Reboot, Nand Erase, Re-Partition, F. Reset Time, and Phone Bootloader Update selected).

5. BL went through successfully and the phone rebooted.

6. Phone reboots, but stays at Samsung Galaxy S8 screen, shows Custom icon, doesn't go any further than this.

7. Soft Reset (Power + Volume Down) still works and I can get into Download Mode, but not Recovery Mode (to reset cache).

8. I tried using, with same options except for Phone Bootloader Update, both the Modified ODIN and Normal ODIN to upload the AP package and it didn't work. For Modified ODIN, I got the model dismatch fail, tied again in the Normal Odin and got the FAIL and Can't open the specified file. (Line: 1834).

Question, is the phone now bricked?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mdiaz33685:
when odin fails and the flashing u must, reboot ur phone back to download mode, and also the pc Odin reset and try again, for back to stock, u should be using reg Odin.. :D
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] unhcoffee:
That worked, thank you. Used the Normal Odin loading each pack with the default settings. Phone rebooted and crashed at 32%, but after wiping the cache and data, then it loaded fine. Thanks for your help.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
u didnt follow the instructions or flash all the partitions.. sounds like u only attempted the bl but it didnt flash

try removing the .md5 extensions.. throw bl in regular odin but untick auto reboot.. once its successful hold vol down, power n bixby until it reboots back into download mode then flash ap, cp and csc in comsey odin and let it reboot
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
if u used the add csc root in post 2 would fix the rcs icon and i have no issues on verizon.. all one really needsto switch out with the add csc root zip is the build prop.. i use the same zip but if im on newer system img i just update the build prop in the root zip..

more info is needed tho, i have no idea what files u used on your phone lol
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
yea, newer combo files seem snappier, just saying some might still experience some issues.. keep in mind its a debug boot not meant for daily use, its bound to have some hiccups

u might have a mod ask u to move your thread too lol, they got on me long ago posting a firmware thread in dev section as its not really development when its just a unmodified firmware

but thanks for the files, i didnt have one that new lol
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
when that screen comes up ive literally had it stop at 32% EVERY SINGLE TIME no matter stock, eng or combo files lol its a bit odd but ive come to like that screen as it usually means im good to go lol
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
lol jumped the gun on the oreo comment.. if it was in fact OREO, you WOULD NOT want to have used it as youd be screwed out of root as oreo will most certainly be incremented preventing down grade
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
soooo.. ive come to the conclusion that yes, misc will work but magic is in build prop edit "sys.boot_mode=------" as this sets the boot mode to misc (or u can echo into misc but would ony last 1 reboot before it clears out)

the issue is theres only 2 boot modes i know of and that is ffbm and normal lol! if its non existent it ignores it so until we find more boot modes that are of use it might not b worth the time

HOWEVER, upon more research ive now moved towards the /param partition.. so far unable to mount it or take a look at what it holds but im 90% sure it holds the key to bl unlock.. ive seen reference to frigate_bird, cc mode, sb flags, param flags, rpmb flags etc..

was looking on the web and came across a write up not too old where he intentoionally wanted to lock download mode and he did.. the magic was in /param
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] partcyborg:
I didn't flash bl so it would have been fine, worst case start over in Odin and flash fresh backup

---------- Post added at 01:24 AM ---------- Previous post was at 01:21 AM ----------

Nice find! Link?

I've been searching all day but there isn't a lot of info out there on the data format in these types of partitions.

Wow it's really just raw ASCII from 0x0? I guess maybe I was over thinking it. Anyway if you have any suggested background reading please send it over I'm trying to fill my head with this stuff lol
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
i have the entire full source code for S8 debug kernel.. havent messed with it much since we cant use custom kernels lol and i havent educated myself on kernel development yet.. its basically ready to build
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
lol any partition could be incremented, its been this way for a few generation of sammy devices.. for example modem is incremented, they could still flash other partitions but couldnt downgrade modem lol.. its not always just the bl thats incremented...

i would have to find the link again lol ill share if i do.. he basically reverse engineered the abl and found how to enableCC mode which disables download mode for "security" lol.. but he also posted an update towards the end, samsung has a cc apk that does it for u without all the labor haha.. not sure y anyone would want to lock dl mode tho