yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] simple23227:
Every day, EVERY DAMN DAY, I come to this thread to find out if there was any new news or update and I read many, TOO MANY, dumb comments and questions about things that have been mentioned throughout the thread AND in the original post.

So just my thought, if you're too slow or don't care enough to even read the original post (IE, the first post of the thread), please restraint yourselves from rooting or messing around with your phone. Samsung has put lots of work in making these phones and I'm sure they are just fine the way they were made, so use them as they were intended. In fact, don't even come to XDA AT ALL !!!

Sorry for those who might feel offended by my post, but I come to this thread two or three times a day to update myself and there are more useless posts from dumb-asses than the actual useful posts.

Thanks for reading, all!
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] IJoxer:
Congratulations! You've only added to the pointless clutter, nobody can resist the temptation to throw in their opinion, myself included. I debated making this post in response, because I'm only proving my own point, however, I'd like to state that XDA as a community really needs to take a step back and realize that, though this is a forum meant for developers, it is absurd to believe we won't have those with lesser knowledge on topics discussed coming in to ask questions, good or bad. I know it's annoying as all hell, I believe I made myself clear in that matter recently, but we really should try to guide those seeking knowledge with a bit more respect, and much less hostility. By responding with unnecessary comments, you're wasting their time, your time, and essentially everyones time. Everybody has the urge to throw in their opinion, again, be it helpful or otherwise. I love this place, I've spent far more time browsing these forums than I care to admit, but to those whom should know better blatantly disrespecting junior members simply out of frustration of the cumulative disruption is quite disheartening. Take this as you wish, but I do mean for this message to help everyone reexamine the ludicrous behavior being displayed here, again, myself included. Make peace, not war, this is a place for intelligent discussion, not childish behavior.

On that note, I'd kindly request this thread to be moved into a new discussion, if OP is willing to do so, I wouldn't blame them if they decided to abandon ship at this point. My suggestion is a simple copy/paste, and maybe reserve a post for the important bullet points being discovered. Maybe a mod could help with the transition and eventually delete this embarrassment of a thread. Also, those with a question seriously need to read the OP a few times, then search before posting, if you cant do something as simple as that, maybe a development forum isn't the place for you.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] lightninbug:
Are there any developers working on a ROM for us?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
I think many developers prefer phones/models that have unlocked bootloaders, because development is only truly possible when you can use what is developed.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Scitzofrenic:
Yes there is an excellent Rom over in the s8 tmobile forum. (Note that I said s8 not s8+).

Turbo is an amazing Rom cooker ,I've used his roms on multiple devices. You won't be able to flash it as is on an s8+, but replace the boot with your specific model and you're good to go
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mopartonyg:
Hi there I am Verizon and did the same as you but I have no lte services in settings, I have the funny s and volte next to it. I know you are ATT but did not see anyone else respond to this.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] LiquidT:
You are absolutely right and I want to take this time to apologize. To everyone.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jawonder:
Try lookin for Volte then.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] mopartonyg:
Its weird don't see anything like that and I flashed the Verizon version of AQGL
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
industry connections for S8+ qpst/qfil files

Some people work for carriers, or have industry connections. If we want to have an unlocked bootloader we need to approach it on a more fundamental level than Odin. So, if you have industry connections, please see if you can obtain qpst/qfil files for S8+. :)
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
loool.. u commented as if it should still be charging to 100% after rebooting the phone which is not true..

you must be doing something wrong or incorrectly if its not working for you..

so why post as if it doesnt work when it absolutely works as intended?

nothing to forewarn people about if you are not successful as it is implying that his hillbilly fix doesnt work..

no high horse here, i will speak up if a known dev is posting a hillbilly fix and ppl are claiming it to not work when it does in fact work is all..

sorry you took offense to that lol i need to remember ppl on here get offended way too easily and i cant be my sarcastic self on here
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
if u followed through step 2 adaway should work with 0 issues
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
that question is out of the context of this thread.. this is a root onky thread, anything outside of rooting is meant for another place
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] bill10:
Omg your going to give yourself a heart attack. If it bothers you this much don't come on XDA.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
why?? we already have those.. heck weve had em since before obtaining eng files.. they have nothing to do with unlocking the bootloader as you can only flash signed files in edl mode which only effectovely works on actual bricked devices..

we can essentially already do what edl can do since we can dd images already to any partition..

edl doesnt unlock the bootloader
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
we've had edl files since before we had eng firmwares.. edl flash files will not unlock the bootloader
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] bill10:
Wow this is the most uptight thread I've ever read lol you guys need to chill. It's only a mobile device
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
towards a solution

Bootstomp exploit finder is interesting and it revealed the bootloader we have is the most secure on the market right now: https://seclab.cs.ucsb.edu/media/uploads/papers/bootstomp.pdf

As for QPST, I was hoping there might be some manufacturer signed firehose image in the industry: https://blog.onedefence.com/signed-firehose-images-and-why-theyre-dangerous/

DD would be useful if we could use in conjunction with Chinese or Hong Kong CROM unlocked bootloaders, but only in conjuntion with a boot image modified to load SM-G955U firmware.

If DD fails, then we would need to recover with QPST. Thanks for your hard work so far! :)
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] LiquidT:
Everything is working great. It was a bad downloaded apk.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] BlackAlien92:
Don't want to make this into a big argument between all the devs and the members of this thread. I come here as well everyday to read any new updates pertaining Root. But to be honest all I ever see is people giving each other rude comments. I understand the devs are extremely annoyed with all the questions asked over and over again. But everyone must remember. We aren't all knowledgeable rooting a phone especially when there's people that have never rooted a phone in their life. I'm not trying to make anyone upset with my comment. But we can definitely be a lot more considerate of the Newbies. Just my opinion
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Heavenly_Abyss2016:
If the most secure phone bootloader is this one, then I guess unlocked bootloader is never happening. No DriveDroid for me though, and I need UMS for that.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] SageChrono:
It's fine if one is not knowledgeable, the problem for some is usually 80% of these threads end up like this. People regurgitate questions because they don't know how to search.. Rush something, mess up and complain. Then the complaint post comes in, then we come in (which doesn't help, even this one).

All in all its a common cycle lol

Hold your head up, stay strong!
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] arrogant437:
I agree to a certain extent. I get both sides but lean more towards the devs opinions. I've been rooting since the LG Optimus, Nexus S 4G days. Root procedures (for US devices) have grown to be more and more complex. At this point, without any kind of background in rooting or pre reading/research, most people will struggle with the methods in this thread no matter how clearly written. The search function is easy to use here. In the search bar just literally type the key words for your question and every post that contains your topic will populate. 90% of the time it's been asked already( unless a new thread). Do your research peeps. If you have no idea what the terms described in the OP are, Google. I actually read up for a few days before I even attempted my first root years ago... I don't post much (as u can see) even tho I've been here years. Just my 2cents
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] BlackAlien92:
I can definitely see the devs point of view. I just don't want people to be discouraged to root their phone because of the lack of them searching and also some of the negative comments when questions are repeated. All in all at the end of the day use search everyone. The devs have done a lot for us here. the least we can do is try to make their time on this thread a little less stressful
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
no.. if you do adb shell setsid su and then type id, if it says your root move to next step..

the exit command repeatedly is only when that initial command doesnt work for them.. for some reason its like 50/50
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fademaydarkness:
Try 7zip or sometimes, if your partition is NTFS. you can`t directly extract more than 4gb files at once. or you downloaded file is corrupted. Use different browser to download.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
thx for the help.. out of curiosity, whats different in your root.sh?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
lmaooo just some idiot that doesnt know what hes talking about.. its actually a VERY LOW chance of ahard brick and even less if you follow directions..

not to mention if anyone wants to safely and fully go back to stock, fash a stock rom in ODIN... THATS LITERALLY IT HAHA

If anything u might gain some skills with this method, try it out with no harm done and if u dont like it go back to stock.. simple
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fademaydarkness:
Nothing. There was a few line which is not needed. Also, I just found out (nameless= false) line is also not needed (but that doesn`t cuz any problems. I assume. tho). Then,I removed "systemroot" from above starting lines. That, line stuck me on bootlogo. I flashed again the eng firmware then, sh that root.sh. It worked.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
i am only losing like 3% an hour with root lmaoi keep forgetyting it ony charges to 80%
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Opensystem:
I'm echoing some sentiments, but I think it probably bears repeating having just read this whole thread.

If you don't consider yourself an "advanced" user, there is no rush to root this instant. People are going to be working on the battery charging issue, releasing video guides, and refining this whole process. We won't have custom roms tomorrow, and the average user isn't going to reap huge benefits from root as it is. If you're not comfortable with ADB, a brand new phone isn't something you want to use for a crash course.

Guys, it's awesome you released this and from what I see there's already renewed interest in development because of the effort you spent achieving root. Thank you for the sleepless nights, and whenever a new exploit for the phone pops up from here out, know that it was you 4 who made that possible :good:
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
to add, anyone can make a twrp for your phone or any phone but if iu dont see it on xda id take it with a grain of salt even then.

as stated, of course we tried haha, no harm in trying.. ODIN will secure check fail before even flashing it.. now if u dd it, of course it will write to the device and your device will even boot into the system.. but any time you try to go to recovery it willsecure check fail and u have to hard reboot
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] BlackAlien92:
OK so I am kind of confused. I see a lot of people posting different commands that have be sent through adb. So is the original post the one I should be using or does someone have the right commands they can share with me. I'm not new to adb or rooting just don't want to get stuck.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
that actually isa bad idea..it says clearly ROOT.. now even if we were saying it isnt for custom recovery, you dont think itd confuse ppl even more just having TWRP in the title?

ROOT NO TWRP G955U BLAH BLAH will confuse ppl even more so the title will stay as is.. twrp is not referenced aywhere on purpose as its a root thread
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
heres another link to the s8+ SamPWNDfirmware package:

https://www.androidfilehost.com/?fid=961840155545589828
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Interceptor777:
Maybe you should add the 80% battery thing as a disclaimer in OP so that one typical XDA guy doesn't go on rambling about how you broke his phone and it won't charge.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jawonder:
Thank you
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Raz12:
Well I guess I'm a be up all night with this. I tried everything. Normally root doesn't take this long. Maybe I don't have the right things on my computer. But I reinstalled all the drivers so now I'm restarting and trying again. I don't know if my phone saying it cannot access any data using my computer or that security log agent thing blocking me but something is making this process harder for me sadly. I'm trying everything sorry for all these questions
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] boostnek9:
What part you stuck on? You can PM me and I'll guide and help you out brother.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fademaydarkness:
Nothing. There was a few lines which was not needed. I removed them. Also,, Systemless=false line is not needed.(I assume) but that don`t cuz any problems. Also, I removed "systemroot" from the root.sh. That didn`t caused stucking on boot logo for me. :o
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Raz12:
Thanks man. I have a screen shot. I don't know if I can send in messages but I will do
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Raz12:
Here
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fademaydarkness:
That`s nothing. Carry on with your adb to get stable #.Ignore that. Or click OK. Doesn`t really matter.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Raz12:
that happen to you too ?
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] fachadick:
I'll give that a try tomorrow - I actually did all of that but without wiping. I'm not really familiar with ff yet, what specifically should be wiped? Thanks for the help btw.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] kleen3r:
The options are listed in the OP. Make sure wipe is listed first in flashfire.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
If this doesn't modify the boot image, then it may work for UMS (not sure): https://iwf1.com/how-to-mount-android-device-as-usb-mass-storage-ums/

I looked up DriveDroid and it looks like it emulates both USB drive and CD-ROM, but CD-ROM may require custom kernel: https://softwarebakery.com/projects/drivedroid

If only root is required to enable UMS (separate from kernel enablement; i.e., trying to flash a custom kernel and running afoul of secureboot), then you should be able to find a workaround.

As for bootloader, we can probably forget about exploit. But, if you can't beat them join them, in the sense that they already provide easily unlocked bootloaders for some S8+ models that have our Snapdragon CPU in Hong Kong and China. DD is a low-level writing program we could use that could duplicate already CROM unlocked partitions and exactly flash them again--bit for bit; we can use DD with root right now. Additionally, modify a boot image to load our SM-G955U firmware and that is much more realistic than finding some bootloader exploit. We would need to recover with Qualcomm's QPST because we would be experimenting for some time. If you can't beat them, join them.... :)
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] meathammer386:
There is already a thread for that s8 s8+ disscution thread you shoud start commenting over there
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] ChrisJK7:
Does anyone know where I can get stock firmware files for my S8+? Need to do this just in case something happens and/or i want to go back to stock
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] xDMONEYx:
I think you and many with your point of view are missing the point, and the issue. See, this isn't a one-click root thread where it's easy to help the uninitiated. This method of root, to the uninitiated, is highly complex. There are people entering this thread who have NEVER rooted before and NEVER used ADB before, essentially asking to be taught how to do this process. They're the same people likely to get attitude/hostile when something in the process goes wrong, because they are depending on the guidance of someone else, through a forum, so they see it as that person's fault if something goes awry.

Many others, including myself, are all for HELPING people. That's much different than straight up TEACHING people how to do this. I'm not sure why you are anyone would want to encourage the uninitiated to rush into rooting their phone with this method when it could very well result in a brick. Because people who are not familiar with this stuff essentially demanding to be taught this stuff are rushing into this process.

To reiterate, this is not a simple, fail-safe one-click root method of old and the attitude of the thread shouldn't be treated as such either. We're dealing with an $800 phone here, and despite projections of "hostility" that can't really properly be read through text anyways, most of the time those of us telling the "noobs" to take the time to learn this stuff on their own are just looking out for them and their expensive device in the end.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
If you need stock, you could try: https://www.sammobile.com/firmwares/

That is where I got latest T-Mobile stock S8+, but other carriers are there too. Along with that (after stage 1 rooting), I used FlashFire wipe + FF that latest carrier-specific system.img.ext4 + FF provided supersu zip (provided in stage 2 of OP); then that latest carrier-specific CP + CSC in latest Odin (not Comsey).
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
we already have one member of our group who dd'd hk bl and hard bricked.. currently working on an edl restore method but so far not successful yet
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
DO NOT DD HK/CHINESE BL you will hard brick and we currently do not have debrick methods/images and have not been successful with edl yet
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] jhofseth:
Good luck! I suspect he probably just DD'd the ROM images versus getting someone's already CROM unlocked DD copied partitions; the only possible way to succeed is to use stuff that Odin has already signed & flashed.
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] Radix999:
9

Uni 777 7u777877 n. 9io
[Samsung Galaxy S8+ ROMs, Kernels, Recoveries, & Ot] elliwigy:
i think you have a misunderstanding of how it works.. the hk/chinese bl has a crom lock.. in order to determine if its unlocked or not it checks for a "KIWIBIRD" flag on the steady partition which is the only thing the CROM service apk does (write KIWIBIRD" into the steady partition.

Upon boot, the bootloader checks this steady partition for the flag. If it fibds it, it reports the bootloader as being unlocked.

We can use the CROM service apk so long as we push the libkwb.so files, install crom.apk and then run it. Hell I have the KIWIBIRD flag on my steady partition right now.

However, of course, our BL doesnt have a CROM lock, so it ignores the KIWIBIRD flag.Therefore its useless as is.

The way Qualcomms Secureboot works, isn't as easy as DD'ing or flashing images from another variant. You will hard brick, and here is why:

1) Secureboot chain of trust is as follows: Root Certificate, Primary Bootloader, Secondary Bootloader, Applications Bootloader, Operating System, then other images/partitions.

2) The "Root Certificate" and "Primary Bootloader" are burned into the HARDWARE and verify the next in chain which is the "Secondary Bootloader"

3) If the Primary Bootloader cannot verify the Secondary Bootloader your device will immediately fail to boot (hard brick)

4) We cannot change our Root Certificate or Primary Bootloader as this is burned into the hardware.

5) Our "Root Certificate" and "Primary Bootloader" is different than the HK/Chinese certificate/primary BL

So unless you can get a CROM locked/unlocked Bootloader that is signed with keys for the US variants it will not work.

In odin you will get a secure check fail since hk/chinese bl is signed with keys that dont exist on our variants..

If you DD without first being unlocked secureboot will FAIL and since you are messing with bootloaders it will fail before you can get into download mode, therefore wont boot at all and boot straight into edl mode

ANYTIME messing with bootloader files and DD you are adking for a hard brick...

As far as your ODIN comments, ODIN doesnt sign anything. In fact nothing is signed in the process.. The images are already signed by Samsung and the root certificate/keys are stored on the device and in the image files. Any key signing is done on the device, not in odin. ODIN verifies the hash key and during the checks verifies image agaibst keys on the device.

It would be a huge fail on Samsung if they had ODIN sign the keys as this would be a hige security risk.

Even if you coud get it to flash, it still wouldnt boot due to secure boot, this is why when you DD twrpr amodified boot.img the device will not boot and tell you secure check fail.

This is why eng boot cannot be used since although it is signed, our root certificate/primary bootloader is not signed as an ENG device, it is a user device which this flag also appears to be hardwired