• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[V2][Update][Root][G955U]PartCyborgRom - SamFail Rooted/Debloated/Audio/More

Search This thread

Goddly

Inactive Recognized Contributor
Jan 7, 2013
4,269
5,540
Binghamton
2 days. fails all around

Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
All threads completed. (succeed 0 / failed 0)
Added!!
Odin engine v(ID:3.1203)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
system.img.ext4
FAIL! (Auth)

Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)

What am I doing wrong?

First, please don't copy the op. What model S8+ are you running? Ok I see Sprint S8+...

Second. Which version of Odin are you using?

Ok. I see prince, correct.

Third, are you using a different port? Most newer laptops strictly use 3.0s. try a PC. When you plug the phone in while in download mode, does the blue box appear as it should? Should say com 10 or 8, does it?

Fourth, you should be admin in Odin. Are you using it as ADMINISTRATOR ? (Right click and "run as administrator"

Fifth.. it's going to fail after part 1 flash. At the end. Then it should boot into upload mode.

Sixth, reboot into download mode (with different look, but it's still download mode, so don't worry)

Then flash part 2. It will reboot into recovery (hopefully) then you have to factory reset. (Down and up with the volume keys, enter with the power button)

Try this, and let me know. I'll work with you.


Sent from my SM-G955U using Tapatalk
 
Last edited:
  • Like
Reactions: unk2009

pr1m317

Member
Sep 14, 2017
29
4
I have a s8+ from sprint. I've used princecomsey one as well, it fails every single time. Where can I find exact detailed tutorial, it feels like im missing a lot of steps here. Do i need to do anything before on the phone such as install anything? or is it simply putting the phone in debug, turning off verify apps option?

Aside from the flamming you've received which I do not think helps anyone, some people just need to be themselves more than helpful, After it fails and you put phone back into DL mode, DO NOT forget to RESET Odin, Looks like you may have missed that, I could be wrong.
Other than Debug mode, which I'm not even sure needs to be applied due to the method, I haven't had to do anything special before flashing. Once up I also haven't had any of the other issues listed, Amazon is fine, Snapchat, bixby button remap, Xposed, and SU all work and survive a reboot. Runs great, fast, and smooth.
Thanks again Partcyborg!
 

Lurkingzombie

Member
Mar 6, 2018
5
0
First, please don't copy the op. What model S8+ are you running? Ok I see Sprint S8+...

Second. Which version of Odin are you using?

Ok. I see prince, correct.

Third, are you using a different port? Most newer laptops strictly use 3.0s. try a PC. When you plug the phone in while in download mode, does the blue box appear as it should? Should say com 10 or 8, does it?

Fourth, you should be admin in Odin. Are you using it as ADMINISTRATOR ? (Right click and "run as administrator"

Fifth.. it's going to fail after part 1 flash. At the end. Then it should boot into upload mode.

Sixth, reboot into download mode (with different look, but it's still download mode, so don't worry)

Then flash part 2. It will reboot into recovery (hopefully) then you have to factory reset. (Down and up with the volume keys, enter with the power button)

Try this, and let me know. I'll work with you.


Sent from my SM-G955U using Tapatalk

Sorry, probably my 3rd post on the site, but i've already taken care of it. Without doing all those steps lmao thanks anyway
 

striker661

Senior Member
Nov 17, 2006
61
12
New Bedford, MA
so. ive tried giving this a go and odin just isn't even rebooting my phone after the very first AP step. stays in downloading... do not turn off target screen.

this is what happens in comsey odin(running as admin on win 10 usb2 port.

<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

so confused. never had an issue flashing anything with odin before
 

TheMadScientist

Recognized Contributor
so. ive tried giving this a go and odin just isn't even rebooting my phone after the very first AP step. stays in downloading... do not turn off target screen.

this is what happens in comsey odin(running as admin on win 10 usb2 port.

<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

so confused. never had an issue flashing anything with odin before

that is normal the ap will always fail follow up with a reboot to modded dl mode which should say unauth software blah blah Now flash the bl and factory reset
 

striker661

Senior Member
Nov 17, 2006
61
12
New Bedford, MA
that is normal the ap will always fail follow up with a reboot to modded dl mode which should say unauth software blah blah Now flash the bl and factory reset

I'm 100% sure that nothing is happening. It gives me that error five seconds after pressing start and here I am still able to reboot the phone and use it as if nothing has happened. I don't believe anything was changed or pushed to the phone due to how fast it says failed after starting. I also don't get a chain of other info in the log that other people are getting. Odin recognizes my phone but it seems like it's on com3 and 5 on my 2 only usb2.0 ports and notice everyone gets 8 and 10? Is that normal?
 

TheMadScientist

Recognized Contributor
I'm 100% sure that nothing is happening. It gives me that error five seconds after pressing start and here I am still able to reboot the phone and use it as if nothing has happened. I don't believe anything was changed or pushed to the phone due to how fast it says failed after starting. I also don't get a chain of other info in the log that other people are getting. Odin recognizes my phone but it seems like it's on com3 and 5 on my 2 only usb2.0 ports and notice everyone gets 8 and 10? Is that normal?

ports can be different on pcs mine is set to 40
 

Goddly

Inactive Recognized Contributor
Jan 7, 2013
4,269
5,540
Binghamton
so. ive tried giving this a go and odin just isn't even rebooting my phone after the very first AP step. stays in downloading... do not turn off target screen.

this is what happens in comsey odin(running as admin on win 10 usb2 port.

<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

so confused. never had an issue flashing anything with odin before
What does the red box say when it fails? Auth?

Have you tried right clicking and running Odin as administrator?

Sent from my SM-G955U using Tapatalk
 

striker661

Senior Member
Nov 17, 2006
61
12
New Bedford, MA
that is normal the ap will always fail follow up with a reboot to modded dl mode which should say unauth software blah blah Now flash the bl and factory reset

What does the red box say when it fails? Auth?

Have you tried right clicking and running Odin as administrator?

Sent from my SM-G955U using Tapatalk

Yes sir. Stated I'm running as admin. Nothing happens in the com box like normal. It doesn't change to fail or anything. I'm going to try and reload the Samsung USB drivers and give it another whirl.
 
  • Like
Reactions: TheMadScientist

Goddly

Inactive Recognized Contributor
Jan 7, 2013
4,269
5,540
Binghamton
Yes sir. Stated I'm running as admin. Nothing happens in the com box like normal. It doesn't change to fail or anything. I'm going to try and reload the Samsung USB drivers and give it another whirl.
It doesn't show a com number, then it's the cable or the Sammy drivers

Sent from my SM-G955U using Tapatalk
 
Jan 27, 2018
13
1
What does the red box say when it fails? Auth?

Have you tried right clicking and running Odin as administrator?

Sent from my SM-G955U using Tapatalk

I'm now having the same issue. Only mine failed to go into the modified download mode after flashing the AP, but it did when I manually rebooted into download mode to try again. Since it went were it was supposed to go in the first place, I went ahead and flashed the BL, part two. It rebooted directly into factory mode (for the first time) and I thought I was golden. Did my factory reset, rebooted the device and what do i get? UPLOAD mode. Reset again, it goes to modified download. Tried to just start over and flash the AP, and I get the aforementioned error, not 5 seconds from my pressing start, it fails and exits. was running it as an administrator, I disabled my computers USB 3.0 capabilities.. I am at the end of my rope with this. This is my first time trying to root something so i figured I should start in the deep end.. I have no idea what I am doing wrong and would love a little assistance. Luckily, i found a stock ROM (although its for sprint and i have T-mobile) so hopefully the device is at least functional tomorrow.
 

partcyborg

Recognized Developer
Jun 23, 2017
2,543
2,278
I'm now having the same issue. Only mine failed to go into the modified download mode after flashing the AP, but it did when I manually rebooted into download mode to try again. Since it went were it was supposed to go in the first place, I went ahead and flashed the BL, part two. It rebooted directly into factory mode (for the first time) and I thought I was golden. Did my factory reset, rebooted the device and what do i get? UPLOAD mode. Reset again, it goes to modified download. Tried to just start over and flash the AP, and I get the aforementioned error, not 5 seconds from my pressing start, it fails and exits. was running it as an administrator, I disabled my computers USB 3.0 capabilities.. I am at the end of my rope with this. This is my first time trying to root something so i figured I should start in the deep end.. I have no idea what I am doing wrong and would love a little assistance. Luckily, i found a stock ROM (although its for sprint and i have T-mobile) so hopefully the device is at least functional tomorrow.

What specifically does it say when it goes to upload mode? Does it say "Unknow Error"? "Modem Crash"? "User pressed power key for 7 seconds?" Look at the small text (if there is any), does it say something about "ext4"?

Upload mode is just the default state a phone running the factory firmware goes to when it cant continue running, where if you were running stock it would just hard reset. There are tons of different reasons for why this could happen: Linux kernel panic, Modem crashed, Cant mount root filesystem, cant find init, something very low level in the device crashed, etc etc etc. In most cases, it will tell you somewhere on the upload mode screen at least what general thing caused the crash, and maybe more specifics if its one of a slightly less number of possible causes.

And since you are new, welcome to the world of Locked bootloaders and root! It is tricky because we are doing things that Samsung spent a lot of time, money and engineering effort specifically to stop us from doing. In all honesty next device around if you want something that is much easier and more "turnkey" than this, the only option for Samsung is to pick up one of the exynos devices from europe. They don't support CDMA carriers (there arent any in Europe), but they have bootloaders that you can unlock and then its open season, you can flash whatevever you want without Auth errors and Invalid Arguments and all the stuff we deal with here.
 
  • Like
Reactions: TheMadScientist

machx1111

Senior Member
Oct 8, 2013
193
39
Just came here to say this worked flawlessly for me. Rom seems buttery smooth, looking forward to seeing how the battery works.

Also wanted to mention I have all USB3 ports on my laptop and I used a USB2 hub without a single issue. Done in maybe 15 minutes tops.

Thanks a million for this effort to make Samsung's locked down not quite so miserable ??
 

matthewd769

Senior Member
Aug 21, 2017
288
57
None of the things you mention have anything to do with the rom. Facebook is not even installed so I'm guess you did that yourself or maybe you dirty flashed the rom? The section in the op on dirty flashes explicitly states that you need to reproduce an issue found via dirty flashing on a fresh install before recording it as an issue.



Let me take this opportunity to remind everyone what kind of feedback is actionable, and what to do if you want me to be capable of even trying to reproduce your problem so that i might fix it.

Bugs you encounter need a LOT of debugging info on a device this complex. If logs aren't possible to get, then i absolutely need a way to make it happen myself. Without one of these things, i can not even begin to imagine what happened or how it could possibly be fixed.. I really dont want to be one of devs who just ignore unactionable reports or questions, but it gets to be a lot across the devices im supporting.

Thanks!

Ps: the anwer ti your question is in the op
@partcyborg .... Ive been a huge fan of you and your work, so the bluetooth isnt something you want to know about? I never dirty flash btw. I followed YOUR directions to the T. I know your doing alot of work and damnit its great work. Ok ill re read the OP for the 20th time and see where it mentions the bluetooth issue i was having.

Yep read it again and nowhere does it say your bluetooth might drol or not work. I even flashed the files you made available, much appreciated. I will follow the OP one more time and see what happens. Again your work is amazing.
 
Last edited:

Yliria

Member
Mar 7, 2018
15
1
I'm now having the same issue. Only mine failed to go into the modified download mode after flashing the AP, but it did when I manually rebooted into download mode to try again. Since it went were it was supposed to go in the first place, I went ahead and flashed the BL, part two. It rebooted directly into factory mode (for the first time) and I thought I was golden. Did my factory reset, rebooted the device and what do i get? UPLOAD mode. Reset again, it goes to modified download. Tried to just start over and flash the AP, and I get the aforementioned error, not 5 seconds from my pressing start, it fails and exits. was running it as an administrator, I disabled my computers USB 3.0 capabilities.. I am at the end of my rope with this. This is my first time trying to root something so i figured I should start in the deep end.. I have no idea what I am doing wrong and would love a little assistance. Luckily, i found a stock ROM (although its for sprint and i have T-mobile) so hopefully the device is at least functional tomorrow.


This happens when I flash this ROM. When it fails the first AP flash, restart the phone into DL mode and go ahead and flash the BL. When it goes to recovery, do reset and clear cache. Then back into DL and start process over. This time when AP is flashed, it always crashes into the appropriate upload mode and the second BL flash finishes the process. No clue why I have to do it twice to make it work, but it does work.
 

striker661

Senior Member
Nov 17, 2006
61
12
New Bedford, MA
This happens when I flash this ROM. When it fails the first AP flash, restart the phone into DL mode and go ahead and flash the BL. When it goes to recovery, do reset and clear cache. Then back into DL and start process over. This time when AP is flashed, it always crashes into the appropriate upload mode and the second BL flash finishes the process. No clue why I have to do it twice to make it work, but it does work.

Did you need to manually reboot the phone? Also, did you only get like 4 lines of log and the fail only 5 seconds after clicking start? It's hard to think the target file is a couple gigs large and ANYTHJNG happens only after 5 seconds. Really want a custom rooted rom. DON'T want a brick.
 

siulmagic

Senior Member
Jun 23, 2007
3,512
2,565
Bridgeport
Hey guys quick question, if i root with this , can i update to oreo trough stock recovery? i don't care about loosing root, i just need to root so i can restore my apps with TB. My model is G955U on oreo beta.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 87
    SamFail presents...

    PartCyborgRom
    BQL1


    A Rooted Custom Rom

    For G955U/W, Bootloader Revisions 1, 2, 3


    Updates
    NOW Supporting Bootloader V3!
    I am happy to announce that BL version 3 phones are now supported by PartCyborgRom!
    Just download the Version 3 BL further down in this post (after reading everything in between!) and use it in place of the normal BL Part2 file.

    NOTICE: Rooting Process Steps Updated!
    Enough people are coming from later bootloader revisions that have some extra protections that I updated the process to use an additional step. Many of you have used this step already at my suggestion when your AP flash was failing with Auth Error without a reboot to Upload.


    Featured Modifications

    Deodexed
    Deodexed for all devices.
    I found a way that works!
    It should keep working as long as nougat
    (is that a haiku?)

    Xposed Preinstalled
    PCR now comes out of the flasher with xposed pre-installed!
    NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot

    New Boot Animation
    Another great one from @Ryan-refoua.
    This one is my favorite so far.

    JamesDSP
    I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.

    ITYBP Modded YouTube
    A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR

    Improved Debloating
    Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
    If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.

    Improved Battery Life
    Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.

    Performance Improvements
    That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.


    Other Features
    New for first time flashers
    - Pre-Rooted with SuperSU installed
    - CSC OYN pre-installed. Tested working on several carriers
    - RCS and VoLTE icons removed from status bar.
    - High quality audio mods, including
    - Viper Audio (V4A)
    - Dolby Atmos from the Axon 7
    - Pandora hifi audio framework
    - Native Google Dialer & Contacts support, including local search, spam call blocking
    - Oreo 8.1 Emoji Icon Set
    - Custom Lockscreen Clock font
    - Stock system display fonts replaced with Apple's original San Francisco Font


    Special Thanks
    - @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
    - The Aiur crew for Pandora (now a legacy mod but works great on the s8)
    - @syndre for the Google Dialer and Contacts framework mod
    - @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
    - Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
    - everyone who tested


    Warnings/Disclaimers/Known Issues
    - 80% Battery life like every other rooted US snapdragon device
    - Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
    - If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.


    SamFail Rooting Process
    and Rom Installation


    WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
    If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.

    Prepare the Following:
    - complete stock rom at your bootloader rev in case things dont work
    - Everything backed up
    - Both Prince Comsy Odin, and Regular Odin for flashing stock
    - A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.


    What is my Bootloader Revision?
    Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G955USQS2BQL1
    Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G955UEU2AQK2. Can you tell which revision it is?


    Is my Phone Compatible?
    Is it a G955U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G955UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.




    Steps to Root

    1) Download and unzip AP Part 1 and BL Part 2 zip files.

    2) Download and unzip Prince Comsey Odin and start it up

    3) Reboot device into Download mode and connect it to your pc

    4A) Open Comsy Odin and Reboot into Download mode. Add Only the BL Part2.tar.md5 file. Go to the options tab and remove the checkbox next to "Auto-Reboot". Do not check any additional checkboxes and leave the other ones alone. Connect your phone and Start. Odin will flash the BL file to your device and will say PASS, but will just sit in download mode (because we turned off auto-reboot!). This makes the next part a little easier...


    4B) Reset Comsy Odin and use the "three button salute" on your device to Reboot back Download mode. This time only add the AP Part1.tar.md5 file. Select only the following options:
    - "Auto-Reboot"
    - "F-Reset Time"
    - "Nand Erase All"

    NOTE: Odin will freeze while checking the AP tar.md5 hash.
    Be patient, it will come back. If your computer is old this will take even longer.

    5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while.

    ATTENTION
    When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".

    If your device stays in Download Mode:
    If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have likely suffered from the usb3 corruption

    When you see the upload mode page, do the 3 button salute to reboot into download mode again.

    WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.

    When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
    Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.

    6) Close and re-open Comsy Odin or hit the reset button, and once again add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.

    7) Do not change any of the options checkboxes, thus leaving the checkboxes checked for "F Reset Time" and "Auto Reboot". Click "Start" and flash the BL (part 2) to your device.
    Note: Flashing BL twice is necessary as some newer stock BLs have patched the Root method we use, but the Combo Factory firmware is still vulnerable. In other words, the SamFail nickname continues to be prolific :good: :good:

    Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.

    8) Wait for the flash to finish . It won't take very long at all as the files are small.

    9) When it has finished, Odin will say PASS and your device will reboot into recovery.
    From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.

    Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage

    10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.

    11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.

    All done!


    FlashFire Instructions


    - Get the ROM on your phone and unzip it
    - Open up FlashFire
    - Add a Wipe task, select the top 3 items only
    - Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
    - Select Reboot to Recovery
    - Make sure "Inject Root" is NOT checked
    - Press go. Wait for the rom to flash and your device to reboot into recovery
    - From recovery do a factory reset
    - Then select reboot to Download Mode
    - When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5

    You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.



    Dirty Flashers


    Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
    To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.

    Odin
    Skip "Nand Erase All" during the Part 1 flash. Do everything else the same

    FlashFire
    For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.

    NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.

    ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.



    Help! I Got a Boot loop!
    If you get a boot loop or your device hangs at boot, try the following:

    1) Reboot to recovery and factory reset again.
    To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
    2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.

    Kernel Panic, Invalid Argument

    Start Over
    Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:

    1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
    2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
    3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.

    I Dont Have Another USB Port!
    Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
    If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.


    None of that Worked! I'm Screwed!
    No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.



    And they all rooted happily ever after.
    The End.


    XDA:DevDB Information
    PartCyborgRom, ROM for the Samsung Galaxy S8

    Contributors
    partcyborg
    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 4.x
    Based On: TouchWiz/Samsung Experience

    Version Information
    Status: Stable
    Current Stable Version: BQL1
    Stable Release Date: 2017-12-10

    Created 2017-12-11
    Last Updated 2018-2-10
    9
    Thanks to everyone who volunteered! I have enough testers for now, but if i need some more i will reopen this.


    Calling for Testers!!

    Its that time again. I've got a new rom ready and I need some 955u testers.

    I have some special surprises in store for this one, as its been too long since the last version.

    Please only volunteer if you meet the following requirements:

    - Are comfortable with wiping your phone completely, and then going right back to what you have now if something is broken off the bat (unlikely, but possible)
    - Are comfortable with instability, crashes, stuff not working right, etc.
    - Able to flash the rom sometime in the next 24 hours
    - Are currently running, or have run PartCyborgRom recently, as in you ran the current release at some point
    - Have a basic understanding of how to troubleshoot and provide decent feedback. Nothing too major, just things like:
    - figure out how to reproduce the issue (if possible)
    - know how to get a logcat during when the issue occurs, or right after (again if possible). I can do a little writeup on this stuff if people are interested
    - Have a usb2.0 port to flash from (i get too many bugreports caused by usb3 corruption, gotta clean up the signal a bit). PLEASE check before asking


    If you meet all (or most, and are sure you can cover for the ones you dont), shoot me a message here or on telegram. I'll be checking on both of them throughout the day.