The announcement you have all been waiting for is finally here!
SamPWND
the world's first U.S. Samsung Galaxy S8/S8+ root!
Disclaimer
There are quite a few steps involved in achieving the desired root, but it is all straightforward if you follow the directions!! We will be here to assist with the rooting process only! The reason i say that is due to the fact of all that the ENG system.img contains, you can nuke your phone to oblivion if you aren't careful, hence this next part... Anything and everything done with the ENG system.img and root after root is achieved is on YOU, and the team and I will NOT be held RESPONSIBLE! Don't blame us for your experimenting! Root works, and won't mess your device up that is what we are here for, any further research/testing is all on the USER!!
After a long 4 months, we have finally achieved our main objective! Countless hours have been put into this process, as well as much lost sleep; so we could be here, at this point releasing root to you, the community! However before we get to that point there are some people need to be thanked, whom without; none of this would have been possible!
The Crew
@elliwigy
@Harry44
@akiraO1
@BotsOne
@GSMCHEN
First off i would like to apologize about the delay i planned on having this uploaded shortly after @elliwigy made his thread, however my internet was not being the greatest and i was having issues uploading the needed files. Now after all day it is finally done and i am here to present to you the community, ROOT for the USA Samsung Galaxy S8/S8+ This thread will be focused on the regular S8 variant, the S8+ thread can be found here Root Samsung Galaxy S8+ Now without further ado, we shall begin!!!
Description
Samsung won this one for us! We flash 4 ENG Odin files, then the way we achieve root is by executing an su binary that they so graciously provided us within the ENG systems xbin. Afterwards we run a script that pushes the rest of what we need in and installs superSU to the system. At that point root is done, however it is not the most stable/smooth. The next process is optional, but recommended. We will be taking a stock system.img.ext4 from a firmware of your choice either U or U1, a supersu.zip(that will be provided) which installs root to the system. They are then flashed in flashfire, resulting in a stock rooted rom.
Requirements
--4 Firmware Files(provided by us)--
--Odin Prince Cosmey and Regular--
--systemroot.zip(provided by us)--
--SuperSU.zip(provided by us)--
--PC with ADB--
--Full stock firmware, either G950U or G950U1(just in case need to flash stock, as well as for system.img.ext4 and cache.img.ext4)--
--Full combo firmware(for whatever reason... we may need you to have it to fix issues you are having)--
Procedure
[CENTER
Download the SamPWND_S8_4File_Firm, the SamPWND_S8.zip, and the systemroot.zip
Download Odin Prince Comsy and Normal Odin
Extract SamPWND_S8_Firm to your desired destination (desktop works), then open Odin Prince Comsy, and place the files in their respective slot (BL --> BL, AP --> AP, CP--> CP, CSC--> CSC)
In Odin, go to options and select, Auto Reboot, Re-Partition, F. Reset Time, Nand Erase All, and Phone Bootloader Update (This will wipe the device)
Put Samsung Galaxy S8 into Download mode (Power + Volume Down + Bixby) A warning screen will come up warning you about flashing a custom os, to continue press Volume Up.
Press Start in Odin (Flashing will begin, this can take up to 10 min)
When complete device will reboot into recovery mode, at this point just select reboot system now.
Complete the Setup, and accept device RSA Keys, to authorize adb (if popup is not there already, or you have dismissed it; please disconnect and reconnect phone, then accept)
Now take the systemroot.zip dowloaded in step one, and extract it to your adb install directory (usually C:adb)
Navigate to adb directory and CTRL + Shift + Right Click, select open cmd window here
Once you have cmd open and the extracted systemroot folder in your adb directory, we can begin.
Type: adb push systemroot /data/local/tmp/systemroot
When that completes type: adb shell
Once in the shell type: chmod -R 0777 /data/local/tmp
This next one is tricky, type: setsid su (the output will look like this: dreamqltesq:/ $ /system/bin/sh: No controlling tty: open /dev/tty: No such device or address
/system/bin/sh: warning: won't have full job control), you will then be in a very unstable root shell
In order for this shell to become stable you must type exit, it will then drop you into a stable root shell, however this will probably take a few tries as most commands sent to the unstable shell are returned as gibberish. The shell itself will continue to change from standard user to root user, upon a press of the enter key. This will continue until exit is successfully ran and you are dropped into the stable shell (Note: Since the shell is changing from user to root after each command the exit command must be executed will the shell is root, otherwise instead of dropping to a root shell, you will drop to a user shell and have to begin with setsid su again)
Once a stable root shell is achieved you will type: echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper (this will remount system and rootfs as r/w)
Wait 10 sec and type: mount (confirm that system is mounted as r/w)
Now we will execute the script, type: sh /data/local/tmp/systemroot/root.sh (there will be some errors displayed back to you in adb, don't worry about them everything is going accordingly)
When the script is done running your device will reboot, and at this point you are done. However, although root has been achieved it is not the smoothest/most stable, but we have a remedy for that as well!
Part Two
With your device still connected to the computer** Take the SamPWND_S8.zip downloaded from step one, and either put it on your device's internal storage or sdcard
Take your stock firmware of choice, and extract it to your desktop. From this you will take the system.img.ext4 and either put it on your device's inter storage or sdcard
Download flashfire from the Play Store
Open flashfire and grant root permissions (this must be done with airplane mode enabled), exit flashfire
Open SuperSU, go to settings, scroll to the bottom, and enable pro features. Reopen SuperSU, select flashfire, and force user ROOT
Open flashfire again, and select flash firmware package (choose system.img.ext4)
Select flash ZIP or OTA (choose SamPWND_G950U.zip) Under options for the zip make sure to select mount /system read/write!!
Select wipe and make sure the top 3 options are selected, press the check in the right hand corner
This next step is very important! There is a specific order that these are supposed to be in, from top to bottom: WIPE --> Flash Firmware Package --> Flash ZIP or OTA. If your order is not this, hold down on wipe like it is an app and drag it to the top of the list. Make sure it is in that order before pressing the flash button!
Select EverRoot from main screen and under options disable inject SuperSU
Press the lightning bolt to begin flashing, and wait for your device to reboot
Congratulations you now have a very smooth/fast/stable stock rom, with root. Enjoy!!
Thank you for your continuous support over the past few months, all the work put into this root method/Rom project was done for you guys, so that you could experience the best device of 2017 (so far), how you want it! With your own customization's and endless freedom! We truly hope that you enjoy our work, and remember donations help in the process!
The developers that have worked on this project over these past few months, did so while living their lives; attending work,
etc, as well as without pay. Those who pledged a bounty thank you, we hope that you are true to your words and pay your pledge, to do so please visit the bounty thread! All others if you benefited from this in anyway and want to show your appreciation, all the team members have a donation email on their profile, we love to see the support![/CENTER]
XDA:DevDB Information
SamPWND, ROM for the Samsung Galaxy S8
Contributors
STF_TimelessGoD
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2017-08-19
Current Beta Version: N/A
Created 2017-08-20
Last Updated 2017-08-19
Awesome. Going to give this a try. Thank you
Got it working. I appreciate all of the team's hard work to get this out to us.
thanks man. finally got this.
Looks good!
Yes! Thanks guys
Sent from my SM-G950U1 using Tapatalk
Been a long time coming. Has been a hell of a lot of fun! Hope you enjoy the same!
Thank you sooo much!! I will be trying this tomorrow morning and update my reply for the results. Thanks to all!!
awesome news.... this thread is about to become very popular
Just to double check, when i went on the link to download the firmware, it said it was for the S8+, was it just the website saying it was for the s8+ and not for the s8? Got me lost for a second but im still downloading it
DaNamesFrank said:
Just to double check, when i went on the link to download the firmware, it said it was for the S8+, was it just the website saying it was for the s8+ and not for the s8? Got me lost for a second but im still downloading it
Click to expand...
Click to collapse
Correct they are hosted on AFH and the SamPWND_S8.zip is universal between s8 and s8+
SWEEET!!!!! will be staying up for a while to give this a whirl. Thank you, gentlemen.
Thank you all for your hard work for root on the S8!
I have a question in regards to the S8 vs S8+ disclamer. Does the S8 process have the same limitation? My assumption is yes but was wanting confirmation since there was a few differences in the files.
Does the S8 root process end up limiting the charging to 80%? What about SafetyNet and the issues with some apps? Does these issues follow suite for the S8?
Sent from my SM-G950U1 using Tapatalk
Thanks i Was waiting for so much time
STF_TimelessGoD said:
Correct they are hosted on AFH and the SamPWND_S8.zip is universal between s8 and s8+
Click to expand...
Click to collapse
Awesome. Thanks for the heads up.
lipscombja said:
Thank you all for your hard work for root on the S8!
I have a question in regards to the S8 vs S8+ disclamer. Does the S8 process have the same limitation? My assumption is yes but was wanting confirmation since there was a few differences in the files.
Does the S8 root process end up limiting the charging to 80%? What about SafetyNet and the issues with some apps? Does these issues follow suite for the S8?
Click to expand...
Click to collapse
S8 and S8+ use the same process, and the same exact firmware for root, only difference is one firmware is for the s8 and one is for the s8+
AWESOME MAN! Im gonna wait about 48 hours before i do this, just to see if anything else is released. Idk, might just wait until a vid is made. But thanks again.
Already first step have a question after loading the files into odin. It will not allow me to select phone bootloader update. It is grayed out
perfectpitch said:
Already first step have a question after loading the files into odin. It will not allow me to select phone bootloader update. It is grayed out
Click to expand...
Click to collapse
Don't select it then if you can't it isn't needed
The world's first
cool bro
GSM CHEN said:
The world's first
cool bro
Click to expand...
Click to collapse
Alright first released lol elliwigy and I are using same method, we're part of the same group his thread however is S8+ and mine is S8
Related
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
As of the time I'm writing this, there is no way to get the phone back to "Locked" once you've "Unlocked" it. The phone will show "Re-locked" if you relock it so know that until someone figures something out, Verizon WILL KNOW that you've unlocked your phone once you do it IF they bother to check and know how. It's your gamble, but to date, I've not heart of Verizon detecting root/unlock and refusing service to one person I can confirm. Said another way, you can "un-root" your phone (remove su and SuperUser), but that won't hide the more important fact that you've unlocked it. Consider this before continuing. Unlocking VOIDS YOUR WARRANTY. You accept responsibility for following this guide. Myself and other devs only provide information.
In general, here is what you will be doing:
Using the HTCDev.com site to submit your phones key and get an unlock.bin that you can use with fastboot to unlock your phone. NOTE: This WILL WIPE YOUR PHONE. I suggest using a temp-root method to first install Titanium or similar app, and do a app/data backup. This way when you're done, you can restore apps/data and be just about where you were when you started, only better.
Use the zergrush perm-root method to obtain permanent root and install SuperUser.
Install a customer recovery that will allow you to do a nandbackup and then install other roms/kernels (needed for the next step also).
Install Ziggys custom kernel which addresses some important issues for this phone and provides some other nice features.
NOTE: If you intend on flashing one of the newer ROMs ("newer" as of 2012-03-24) that require the 3.11.602.22 firmware, use Scott's directions HERE then come back and continue.
Now for the actual steps:
UNLOCKING - First visit THIS post for detailed instructions on how to unlock your device. This is required for permanent root and just about everything else following. This WILL VOID your warranty as the post says. This will also WIPE your device so again, I suggest first using THIS temp-root method so you can install an app like Titanium Backup to backup your apps/data.
PREPARING ADB - Once you have unlocked and your phone has rebooted, hit the home key to skip HTC Setup (no point doing it just yet really). Now hit, menu, settings, Applications, and check "Unknown Sources" (for good measure), then "Development" and check the box "USB debugging". I recommend then backing up a screen and un-checking "Start automatically", but that's my preference, not a requirement.
CONFIRMING ADB - At this point, I'm going to assume you already have ADB installed and known how to invoke the command because there are at least 9,999,999 tutorials online explaining this. Go ahead and open a cmd prompt and run "adb kill-server" and then "adb devices" and ensure that your device (if you see one, then you should be fine) shows up.
ROOTING - Now visit THIS thread and hit the less-than-obvious link titled "Download - OneClickRoot" to download the zip containing the tool. Follow the directions in that thread to permanently root your phone.
Boot fully into Android before proceeding.
RECOVERY
PREPARE RECOVERY.IMG - Visit THIS thread and download the attachment. Extract "recovery.img" from the zip and place it in a folder from which you can successfully run ADB. NOTE: If you haven't already, putting the adb.exe files folder in your PATH will let you run adb from anywhere. Same goes for fastboot. This makes life with Android tweaking/hacking MUCH easier.
FLASH RECOVERY 1/2 - Now "CD" into the folder (HERE you can find more about the CD command) with recovery.img and run the following command: "adb reboot bootloader". Once the phone has rebooted into the bootloader (a white screen with text menu, should say "*** UNLOCKED ***" at the top now). In white with a red background you should see "FASTBOOT USB". If so continue, if not, ask for help
FLASH RECOVERY 2/2 - The moment you run the following command, you should see a vertical bar on the upper-right hand corner of your phones screen. If so, it's working as expected. In your CMD window, run the following command "Now "CD" into the folder with recovery.img and run the following command: "fastboot flash recovery recovery.img"
REBOOT TO RECOVERY - If you have't touched the volume keys, "BOOTLOADER" is selected and pressing power will take you to the bootloader where you can then use the arrow keys to select "RECOVERY" and again press the power button to get into recovery. Otherwise, reboot any way you see fit and once running, use "ADB reboot recovery" to get into recovery easily.
KERNEL
DOWNLOAD FILES - First download the two files from THIS post (NOTE: The OP most may end up with more updated files, but as of the time I'm writing this, these are the way I suggest).
PUSH FILEs 1/2 - If you haven't already rebooted into recovery, review the previous steps and get your phone into recovery ("ADB reboot recovery" is my preference). Now "CD" into the folder containing the two files downloaded in the previous post. From here, I will use the file names as they were when I downloaded. Yours could be slightly different so adjust accordingly. In the recovery use the volume keys to navigate to the "Mounts" menu and then "Mount /sdcard". Use the Power button each time to select the menu option.
PUSH FILEs 2/2 - Now from your CMD window (the one in the folder containing the two kernel files), run the following commands: "adb push FlashMeInRecovery.zip /sdcard/" and then "adb push PH98IMGZIGGYUNSIGNED.zip /sdcard/PH98IMG.zip".
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 2/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
If you get the notorious "MainVer Error", use one of the following guides to get past the error. NOTE: Neither of these are for the faint-of-heart and the first I consider easier, does carry some real danger if done incorrectly.
Option 1 - Follow the guide HERE <-- Requires the use of a HexEditor and one is recommended if you don't have a preferred one yet.
Option 2 - Follow the guide HERE <-- Requires modification of the PH98IMG.zip you're trying to flash and sometimes this can be problematic. Either way, it provides an excellent description of why the error occurs.
FINISH - Once the 2nd kernel file is flashed and you're prompted, press power to reboot. After your phone is running again, use the following command to rename the kernel file so it doesn't cause you trouble later in the bootloader (but still keep it handy): "adb mv /sdcard/ext_sd/PH98IMG.zip /sdcard/ext_sd/PH98IMGZIGGYUNSIGNED.zip"
If this guide has helped you and you want to show thanks, just hit the "Thanks" button at the bottom of this post. It's not a donation or anything like that, just a counter used here on XDA
I will try to keep this post refreshed as newer files become available, as things get easier, or things change. If you see an error/typo/concern with these directions, PLEASE PM me and don't muddy up the thread. If YOU will do this, "I" will not only try to maintain the post, but I will also try to add/maintain an FAQ post as needed.
Btw, in case you recognize me and are wondering why I've posted here, it's because my site is dead due to childish drama, I still want to help the community and this seems the most reasonable way to do so for now.
EDITS:
20111230_1804 - Added a hint and link about the "CD" command for users who aren't familiar with "DOS" like commands.
20120101_1923 - Added a direction to boot into Android after rooting.
20120101_2325 - Added warning about unlock/relock and warranty in BIG RED text.
20120208_1709 - Added instructions on how to handle the "MainVer" error.
20120324_1636 - Added note about using 3.11.602.22 based ROMs and linked to Scott's (CleanROM) directions.
Great guide, thanks! Worked just fine and wow this thing is fast as BALLS
Using SetCPU to tweak and monitor, any clue on what the best governor is for this kernel?
EDIT: Reading original post about kernel from Ziggy, "lagfree" governor is available, using that now.
Thanks!!!!!
may i flash kernels on custom rom
or has to be stock rooted?
qudwis said:
may i flash kernels on custom rom
or has to be stock rooted?
Click to expand...
Click to collapse
this kernel is based off of the one made for gingerbread, so as long as the ROM you're running is a Gingerbread ROM, you can, or should be able to use this kernel with it.
*EDIT* I believe it may matter whether the ROM is Sense or AOSP based as well. currently we only have sense roms so it doesnt much matter, but it will down the road.
one more question.
i have cwm for recovery. since cwm don't have developer menu,
do i need to change to Amon Ra recovery?
and if i do, how do i change?
The guide is clear, succinct, and accurate. Everything worked perfectly - thanks so much.
I could've got so much more work done over the last two days if I had a tutorial like this! Untold hours have been spent combing these boards to piece together this whole process. Thanks for taking the time to do this for everyone.
Seemed to work!
I only did the recovery / kernel part since I had done the rest previously. For some reason it partially wiped my phone storage and SD card. Directories are there, but nothing is in them. No idea what happened, but oh well.
At least now I can start messing with stuff.
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
bal1985 said:
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
Click to expand...
Click to collapse
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
rainabba said:
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 1/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
Click to expand...
Click to collapse
This looks very clear and helpful. I'm not ready to use it yet, still need to study up on all this root stuff but thanks for posting.
Just wanted to point out that there may be a small and not so important typo. Both flash files are 1/2, shouldn't the second one be 2/2?
I have downloaded both files into my sd card, flashmeinrecovery.zip worked fine. The pmhimg.zip keeps saying aborted. I am running cwm, should I be running a different rom? What can I do to get the pmh zip to work?
I downloaded them via the qr codes, and they are in the download folder on my sd card. I did change the name on the second zip.
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
pwned3 said:
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Just reboot normally after flashing
sent from my cm7 rooted fire
And move the file. It will read it every time you go into the bootloader
sent from my cm7 rooted fire
Followed instructions and kernel would not flash. All steps completed without errors and still has same kernel. Any advice?
rainabba said:
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
Click to expand...
Click to collapse
so I just unistall SU from the Market? Or do I have to go in with Root Explorer and delete the file? once that is done don't I have to lock the bootloader using that htcdev guide again?
remmy5r said:
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Click to expand...
Click to collapse
Following step 7 specifically prevents you from having to deal with that. So long as the PH file exists in your sdcard root, when you go into bootloader, you will be prompted. Once your running normally, just go follow step 7 and you'll be good to go.
I just went through the unlock and root it is fresh in the mind. These directions ASSUME AN SD CARD IS INSTALLED to the tablet and a WINDOWS OS!
Downloads, get them and put them in a folder on your computer:
Asus Unlock Tool download link from ASUS:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Fastboot EXE:
I got fastboot.exe when I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
TWRP:
Get TWRP for TF201Jellybean, here is their page I have posted the download link below:
TWRP Page
On that page are instructions including a download link.THIS LINK IS FOR TF201 RUNNING JB BOOTLOADER ONLY! DO NOT USE IT IF YOU ARE NOT SURE WHAT YOU ARE RUNNING STOP NOW!
TWRP Download for TF201 running STOCK JellyBean OS:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
MD5 Checker:
When TWRP is downloaded you can compare the MD5 hash of what you downloaded to confirm it is the a good download. If you don' do this and flash a bad copy of TWRP your tablet is now garbage. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Unzip the above download and run WinMD5.exe to generate an MD5 hash of the TWRP file you downloaded. Compare it to what it says the files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Once the MD5 is verified rename the TWRP you downloaded to TWRP.blob just to shorten the name for scripts later and copy it to where you have fastboot unzipped.
ADB command:
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
SuperSU:
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
How To Use The Downloads:
Unlock Device:
First we need to unlock the device. Copy the unlocker APK to the root of your SD card for your tablet via the USB cable or putting the SDCARD in to your computer directly or with the ADB PUSH command if you know how to do that. Run the built in file explorer on our tablet and browse to the SD card (/Removable/MicroSD). Tap the Unlock APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes and reboot one or more times. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
If you don't get the command window here option then you will have to open a command prompt. Open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window copy and paste the following line:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
Install SuperSU:
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card, or by inserting SDCARD in to my computer and copy it over to ROOT of card or with ADB PUSH. Once the copy completes shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) highlighted so press volume up to load TWRP recovery.
OPTIONAL - BACKUP IF YOU WANT TO:
In TWRP there is a backup option. I chose to backup to my SD CARD and made sure to backup everything and generate an MD5. It takes a While but you can flash this back ANYTIME to put your device back to the STOCK JB OS without root. You can use the backup anytime you like to preserve your devices COMPLETE STATE. Just use the restore option in TWRP to put it back.
To flash root, once TWRP loads, the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When successfully done, reboot (flash should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tablet must be plugged in to the USB port of the computer of course.
If you installed the SDK tools ADB is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the shift and right click method in explorer on the "STUFF" folder for the unzipped files or use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder.
In the command windows type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time I want root in a terminal I type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Final thoughts:
There are other ways to copy content to the device such as using ADB PUSH etc... and I am sure this could be mostly if not all scripted but now that my tablet is rooted I am not going to write one and flash SuperSU over and over and possibly screw up my device. Follow the directions above and you will be successfull. If someone wants to write a script based on the above knock yourself out.
I HIGHLY recommend checking ALL MD5 hashes of downloads to confirm you got what you were supposed to. This will help prevent bricks.
Nice to see another guide on unlocking and flashing TWRP
McJesus15 said:
Nice to see another guide on unlocking and flashing TWRP
Click to expand...
Click to collapse
I was thinking a "how to root without unlock" one should be next....
hx4700 Killer said:
I was thinking a "how to root without unlock" one should be next....
Click to expand...
Click to collapse
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
McJesus15 said:
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
Yeah, the How to was going to be:
Step1) You can't.
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
abazz said:
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
Click to expand...
Click to collapse
I wanted to flash the Energy rom because of the near double quadrant scores people were posting. Little did I (or the chef) know that the Kernel was set to 1.8GHZ and constantly running 1.6. CPU throttling did little to inhibit that and even if you set it back to 1.4 it still ran 1.6 when max CPU was needed The back cover temp went from 90 deg while playing an interactive game for 20 minutes to 108.5 deg when playing the same game for 20 minutes. I had to think that was compromising stability and longevity as well as battery life so I flashed back my stock backup I made via TWRP and rooted as above.
I wouldnt mind going back when the kernel is more controllable. I'm actually playing with backtrack 5 now that I am rooted and EDS with mounts to truecrypt volumes so glad I am rooted, would have rather not voided the warranty
I think the policy should be that if you unlock things like the screen and wireless etc.. should still be covered but since they can't control overclocking etc... those kinds of issues are not.
Between 3 kids events, Holiday stuff I barely have the time to do the things I want to do let alone invest time in hacking this device =/
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
jetpackjeff said:
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
hx4700 Killer said:
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
Click to expand...
Click to collapse
As far as I know the kernel issue is fixed. Androwook never had the issue. It'll still get hot but not enough to cause concern
Sent from my Zio using xda app-developers app
worked for me :thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
And for me, didn't get much easier - or idiot proof
Thanks worked perfectly, I'm on CM10 now
Btw, you should change this line (because it's kinda wrong):
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
For this part the blue bar across the bottom did show up but not the ASUS logo, for me the tablet stayed on the same page with the USB logo and the other stuff and the blue bar across the bottom (not the Asus logo).
wrong thread
I have always been locked, and RMAed previously. I was able to successfully do this last night, thanks for the links.
Yay! After reading the forums and triple checking every thing I finaly got ROOT!
Thanks! Now I'm off to install the Energy Rom and hopefully enjoy GTA on a 42" TV with a USB controller
Fail
Doesn't work for me. I'm trying to switch to TWRP from an ever flakier CWM that won't do a backup. I'm already unlocked and rooted but still with stock ROM (which won't update any more because I'm rooted.)
The fastboot flash finishes ok but when I try to boot into recovery I get the message that it is loading the recovery kernel and then it just boots into Android. I have no recovery at all now which is kind of scary.
(God I hate this device for noodling with. Whenever you miss a beat you're looking at a 5 minute uninteruptable boot/shutdown cycle to try again. Everything outside of the Andorid zone itself is so baroque, archaic and intricate that feels like Windows 1.0. More than once mine has come within a nat's ass of being introduced to the wall at high velocity.)
---------- Post added at 11:59 PM ---------- Previous post was at 11:28 PM ----------
DonGateley said:
Doesn't work for me.
Click to expand...
Click to collapse
Oh, how utterly silly of me. Because I rooted long ago I didn't get the JB upgrade OTA so I'm still with ICS. The blob I needed was
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.3.0-tf201-ICS.blob
(At least I determined that flashing the JB blob onto ICS is not catastrophic.)
Maybe I'm not the only one in this state. It might be a good idea in the text to tell others of the ICS option.
The reason I'm here is that I want to install CM10 so I wanted to back up first. When I do that upgrade I assume this ICS TWRP will cease working and I will then need to fastboot flash the JB blob, right? Or might I have a "Can't get there from here" kind of problem?
Thanks for the links and write up.
2 questions.
Do I need an SD card or is the internal storage ok to use.
And, what part of this process roots the device?
Thanks!
**EDIT**
Never mind, I am a bonehead. I had my prime replaced due to a camera defect, so they shipped me a new one running JB.
So I have been away from teh forum a couple of months...didn't realize a way to get around locked, un-rooted, JB had been found.
Thanks again!
Sent from my Transformer Prime TF201 using xda app-developers app
Thanks for writing this up, I can't thank you enough. About a month ago I hard bricked my prime and had to send it in to Asus to have it repaired (thankfully I didn'y get charged). I tried installing twrp but didn't check the md5; this was well written. Wish I could give you a hug.
I know maybe some people will think I'm dumb now or something... But I want to ask before I begin and maybe brick it
So this really WORKS with the LATEST OTA update from Asus? I searched everywhere for days/weeks/months already and found this today so I'm a little bit sceptic, hope you understand me.
Introducing:
SamFAIL!
[Size=DEPRECATED]DEPRECATED![/size]
This ENTIRE THREAD is old, busted, and has been deprecated for some time. Please stop reading it, and go to the link below this line of text:
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
It has some very clear advantages over this version:
- Supports All existing bootloader revisions
- Latest version(s) of Nougat
- Huge community of support
- Telegram channel
- Preinstalled audio mods, visual mods, looks really good
- Actually still works
- very debloated without compromising many touchwiz features. It's over 50% faster on my device
- Deodexed, xposed FULLY supported.
- Rooting method improved, essentially foolproof
I don't want to have this thread closed, but I will
A New Alternative Root Method For The US Samsung Galaxy S8! (G950U Snapdragons)
Rooting your s8 just got easier.
DISCLAIMER 1: Although this method does not trip the "Knox Flag" you are still taking a risk by rooting your device. We are not responsible for your blazing fast smartphone with root! Let's hope this one doesn't catch on fire!
DISCLAIMER 1.5: THIS IS NOT FOR EXYNOS!
First and foremost, SHOUTOUTS!
- @partcyborg for finding the root method!
- @me2151 for testing on Note 8 and facilitating root on the Note 8!
- @elliwigy for... Shenanigans! And thread template
- @Chainfire For opening the door to make this root useful. He will be missed! (no he is not dead, just retired.)
- @samsung for the amazing phone and leaving rediculous loopholes open for us to root!
Disclaimer 2: The method to root should be pretty straight forward as the hard work has already been done for you. With that being said, you will need to know how to download files from the internet, extract a zip file and to use ODIN. That is basically it! Oh yea, PLEASE BE SURE TO READ ALL THE INSTRUCTIONS THOROUGHLY BEFORE ASKING FOR HELP!
Once again...
READ THE ENTIRE SET OF INSTRUCTIOMNS BEFORE BEGINNING!
There are important things to note about this process that WILL likely trip you up if you expecting them. Some things are not intuitive and may sound unimportant to follow but trust me they are. Every single step added her is absolutely necessary.
Prerequisites:
- A working computer with a working USB drive that is capable of successfully flashing firmware to your device.
- Comsey ODIN and Normal ODIN (Found in Post #2 As well)(In case you give up and want to go back to stock)
- SamFAIL S8 Custom Hybrid Combo/Stock firmware package (also in Post #2)
- A functioning Snapdragon Galaxy S8 G950U/U1 or ANY other US Snapdragon based Galaxy S8 that can run the standard 950U firmware. Must be able to boot to download mode, and NO EXYNOS OR
- The CSC file for your phone(also in Post #2)(NOTE: You MUST use the CSC matching your device or your network will not function correctly. If your CSC is not in the downloads section you must download your devices firmware and extract the CSC from it and use that one. I will continue to add CSCs as I have time to download them but please be patient as they can take a while to download. Bonus points if you can send me individual .tar.md5 CSC archives so I don't have to download 4GB of ROM.
Part 1 Instructions:
0) BACKUP YOUR CRAP This procedure wipes your entire phone, so anything that you don't want gone for good back up somewhere NOT ON THE PHONE for the duration of this process. TECHNICALLY it should be safe to leave on a SD card, but checking one accidental checkbox in Odin will make you lose it. Take the SDCard out or copy the stuff to your computer.
1) Unzip the SamFAIL S8 ZIP archive. Inside there will be two tarballs (.tar files). If you have flashed a rom before these should hopefully look familiar. NOTE: There is no CP archive because the hybrid BL_ archive contains all drivers needed to operate your device.
2) Boot up Comsy Odin. Reboot your phone into download mode. Connect your phone to your pc and make sure that you get the Blue box that signifies proper connectivity and that the Odin log has said "Added!"
3) In the AP slot, place the AP tarball. There will not be a long pause like stock ROMs as there is no md5 signature to check.
4) In the BL slot, place the hybrid combo/stock firmware package. Again, you can place these in any slot and Odin will handle it just fine.
5) Click on the OPTIONS tab, and select the following checkboxes: Auto Reboot, Re Partition, F. Reset Time, NAND ERASE ALL.
After finishing the above steps, your Odin should look exactly like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6) Read step #5 again and confirm that you have everything selected EXACTLY as shown in the picture and written in the words. Check it again and when you are sure everything is correct press START.
7) Wait for ODIN to complete the flashing of the system partition. Naturally, ODIN and your phone will see this image is not signed and return FAIL. Your device will say "Secure Check Fail: system" or something close to it. THIS IS EXPECTED, DO NOT PANIC OR GIVE UP. Your flash may have failed, but it did not fail hard enough
At this point you may be wondering "What is going on and how does failing to flash get me root?"
The answer is because of a very simople to fix (pre-launch) issue with secure boot verification. I will explain in more detail when we are done and you have root but the short story is, yes they fail the flash when it does not match a known image, but they do so at the end, AFTER all of the data has been written to the disk!
it indicates that everything is ruined and you should bring them your phone right away. Fortunately we are smarer than that. Despite not saying so, while this screen is showing the device is in fact in download mode ready to receive new firmware.
This screen will likely say something like "System Failure" and there will be instructions displayed to take your device to the nearest repair store. Laugh at Samsung's silly attempt at subterfuge.
Now, lets put that data to good use with part II:
8) Reboot the phone into download mode again (hold down power, vol down, bixby) until the device resets back to a blue-green ("Download Mode Color") screen. If you have not seen or experienced a bad flash before, this screen may be new to you. You should see something that says "OPERATING SYSTEM UPDATE FAILED" and find that your phone will boot only to this state and nothing else. DO NOT PANIC! THIS IS EXPECTED and exactly what we want. Odin/Secure Boot are refusing to boot because you flashed unrecognized code, and wants you to flash code it recognizes. Lets give them what they want.
9) If you closed Odin or hit Reset after the first clash, open it again. Plug your phone back in if necessary and ensure that Odin sees you device just like last time.
10) IMPORTANT! IMPORTANT! It is IMPORTANT that you be sure to remember to do the following: Click the RESET button onthe bottom middle of the page. Alternatively, you can Uncheck "NAND Erase All" "Re-Partition", but its extra work to remember which ones.
WARNING: IF you fail to do this, Odin will happily erase your device and have to start from scratch. Worse though is the failure mode. If you don't notice is not obvious that it is caused by this, which will likely cause you and others unecessary grief.
11) Click on the BL row again and Load the same Hybrid Firmware Combination as last time. Be sure the checkbox next to it is selcted.
12) IMPORTANT: If you did not click "Reset", be sure that the AP_ROOTEED_YSTEM tar is NOT loaded. You can uncheck the check box next to it and it will not be sent as part of the coming flash. If you do not do this, you will fail again and it will be for real this time.
13) Click on the CSC row and load the CSC file you downloaded that matches your device and service plan. Be sure that the checkbox next to it is checked.
14) Double check that your screen and options now look like this or has the same options.
- NAND ERASE is UNCHECKED
- F RESET is CHECKED
- REBOOT is CHECKED
This part is basic ODIN flashing here guys... Not rocket science!
15) Press START and watch the LOG tab to see what is happening. If it says the words "Erasing..." you have failed to follow directions and ust start completely over with step again.
16) This is where the Matic happens... Odin will flash all of the fimrware files in the tarball, and will fihnd that all of them are 100% valid signed images by Samsung. Since Odin has a very poor memory, he completely forgets that you had just flashed a bad system image, and marks your secure boot flag as "Safe" and lets you proceed to boot!
17) Have a good laugh (at least i found if funny)
18) The phone will reboot to recovery and dump you there for one of two reasons:
a) You will see the progress bar advance over a feconds to 32% or so and then stop, printing an error about faling to find resize data. This is normal and happens with every flash of CSC OYN that I have ever seen. You are safe to advance to the nxt step.
b) The recovery will immediately exit with an error that says "Failed to mount /system (Invalid Argument)". This is unfortunately bad news as it means that the failed flash attempt was not successful in writing enough data to see the file system. Do not dispair yet though! This happens sometimes with this method. Start off by starting over from scratch. If that does not work, reach out to me and I will walk you through a few procedures that will eventually fix it.
19) If you made it past step 18, all you need to do now is execute a data wipe/factory reset. This is necessary and your device will not boot withiout it, as there is no userdata image file flashed through odin.
Now, wait for the device to boot up (it will take 3-5min like most new isntalls) and then you can try out your new root!
20) Once phone boots up, Setup your device as normal and proceed to the SuperSU app. It will ask you to update the SU Binary. Select Normal method and let it do its thing. A popup should show up to disable KNOX. Follow its instructions then SU should say it was Successful in updating and it needs to reboot(You may have to do it multiple times. I belive its 2 or 3 times then its good) ENJOY SamFAIL ROOT!
NECESARY CLEANUP
The reason that this works at all is that modern filesystems like ext4 (what android uses) are very robust in the face of errors on the disks. Particularly in the days of old when everything was on spinning platters, that may moving parts was a lot more prone to failure, so filesystems were designed to keep your data safe in the face of losing parts of the disk. Fortunately for us this allos us to successfully mount and load android off of an incompleted filesystem. To make sure that the device is table, and that future SamFAIL attmpts do not degrade into "Invalid Argument" errors, we need to do a filesystem repair.
Download fsck.ext4 and push it to your device to fix any errors that cropped up from the SamFail dirty flash.
Connect via adb (or shell on your device) and run the following
FROM YOUR COMPUTER WITH PHONE PLUGGED IN AND AD ENABLED:
Code:
adb push <localpath to fsck.ext4 /tmp/
Then on the Device:
Code:
su
chmod 755 /tmp/fsck.ext4
mount -o ro,remount /system
/tmp/fsck.ext4i -f $(find /dev -name system)
It is possible that oyu will see a LOT of errors reported. Do not worry though all of the stock os will have made it through ok. Press "a" to say auto-yes to all the questions and your filesystem will be healthy from here on out.
EPILOGUE
It is HIGHLY recommended that you follow this step with the flashing of either a custom rom or a full stock /system ROM using FlashFire. The image I provided that is pre-rooted essentially has no more work done to it than that, and I have no plans to do that work anytime soon. Unforutnately my experiments with using SamFAIL to flash more custom /system partitiuons made them a lot more unstable and frequently would not boot at all. Consider this a stepping stone that requires a little less work than SamPWND used to be before more automation work was done.
The AQH3 Image in post #2 has the "warning this device has been modded" message and i took a brief stab at it but wasnt able to get it locked down. If someone wants to do so i will havppily upgrade the rom to a better vesrion. Otherwise there are some really cool bnew roms out for the s8/s8+ now that I recommend checking out.
The more exciting prospect is that this can be used by ANY Samsung device with a permissive Selinux version without dm-verity. That covers a wide range of devices which we will be investifating.
DISCLAIMER 3:
* SamFAIL DOES NOT TRIP KNOX
* SamFAIL DOES NOT FIX THE 80% BATTERY CHARGE ISSUE
* Boot.img is SECURE which means you MUST use SYSTEM ROOT. (Similar to SamPWND)
* This means that MAGISK DOES NOT WORK
* Which also means SAFETY NET FAILS. So any apps you enjoy that require passing Safety Net will most likely not work while you are rooted with SamFAIL
* Again, similar to SamPWND, this root method uses a factory binary boot.img which is necessary to boot the modified system. THIS MEANS BATTERY ONLY CHARGES TO 80% (Thanks Samsung.)
* SamFAIL DOES NOT UNLOCK YOUR BOOTLOADER AND DOES NOT SIM UNLOCK YOUR PHONE.
* This *should* in theory, work for other Snapdragon Models of the Note 8. If you have another model and are successful please post so we can add "support" for other models.
Back to Stock?
- Download the full STOCK firmware of your choice.
- Flash it in ODIN/Comsey ODIN as you would any other time!
- It will take a few reboots for the "custom" splash screen to go away.
Donations:
As always, the devs have been hard at work recently to bring you root. Donations are definitely NOT REQUIRED but if you feel generous and want to spot the devs a few bucks for their hard work you can donate to this Paypal Address:
Donations
NOTE: this message is geared more towards the Note 8 users, for whom this root method is their first and only.
DOWNLOADS will be in POST #2
UPDATES will be in POST #3(RESERVED FOR FUTURE UPDATES)
As always, ENJOY ROOT and thank SamFAIL for making it all possible!
P.S. See why we called it SamFAIL now? Massive fail on Samsungs part.
SamFAIL Downloads​
Rooted AQH3 Android 7.0 System for Galaxy S8 Snapdragon (Flashing in Odin)
AP_SamFAIL_G950U1_AQH3_ROOTED_SYSTEM.tar:
Hybrid Stock/Combination Full Firmware (minus userdata and system) For Rooted Devices.
AQI6 Stock, AQI1 Combo (for Flashing in Odin):
BL_SamFAIL_G950U1_HYBRID_AQI6_STOCK_AQI1_COMBOtar.tar
VZW CSC OYN for US VZW Customers on AQH3 (for Flashing in Odin):
CSC_OYM_SamFAIL_G950U1_AQH3_VZW.tar.md5
Staticly Compiled fsck.ext4 binary for fixing filesystem issues:
fsck.ext4
*YANK*
(reserved for future use)
Yay!
Nice!
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Ad.Shk2 said:
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Click to expand...
Click to collapse
i have 1 or 2 but not gonna upload em until theres more stuff done.. its basically got minor visual mods and deodex n theusual stuff
That sounds promising... I've been patiently waiting for custom ROMs for the Canadian variant... Good luck to you bro!
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
That sounds promising... I've been patiently waiting for custom ROMs for the Canadian variant... Good luck to you bro!
Click to expand...
Click to collapse
but yea,just not enough done yet in order to release.. i hope note 8 root will kick offmore mods n such for us
I'll be going for Aosp based ROMs too, since it's for the Snapdragon
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Click to expand...
Click to collapse
There is one that supports at least everything thats part of CSC OYN:
https://forum.xda-developers.com/tm.../samsung-tmo-galaxy-s8-sampwnd-turbo-t3662719
Its listed under the tmoblle section because the developer has tmobile, but as our devices are multi-csc so is his rom
partcyborg said:
There is one that supports at least everything thats part of CSC OYN:
https://forum.xda-developers.com/tm.../samsung-tmo-galaxy-s8-sampwnd-turbo-t3662719
Its listed under the tmoblle section because the developer has tmobile, but as our devices are multi-csc so is his rom
Click to expand...
Click to collapse
The OP states: "this custom rom is only for tmo. i removed all other carriers config files..."
Also, what's CSC OYN?
Sorry about my illiteracy in this regard, I'm a Nexus/pixel guy which are a breeze to root and customize.
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
The OP states: "this custom rom is only for tmo. i removed all other carriers config files..."
Also, what's CSC OYN?
Sorry about my illiteracy in this regard, I'm a Nexus/pixel guy which are a breeze to root and customize.
Click to expand...
Click to collapse
Aww that's a bummer, last I talked to him he was fine with other carrier use.
partcyborg said:
Aww that's a bummer, last I talked to him he was fine with other carrier use.
Click to expand...
Click to collapse
all he has to do is flash a csc after the rom lol if all he did was remove the other carrier stuff
Will this work for the S8 Plus?
NexusS4gFreak said:
Will this work for the S8 Plus?
Click to expand...
Click to collapse
yes if and when a modified system.img is created lol i dont plan on making it as i am already maintaining SamPWND root
NexusS4gFreak said:
Will this work for the S8 Plus?
Click to expand...
Click to collapse
elliwigy said:
yes if and when a modified system.img is created lol i dont plan on making it as i am already maintaining SamPWND root
Click to expand...
Click to collapse
I'm going to do my best to make one shortly but given I do not have an s8+ to test on I'm not so sure how effective I will be
Does this work? Anyone tried. I really want to root my Canadian model sm-g950w
Ad.Shk2 said:
I'll be going for Aosp based ROMs too, since it's for the Snapdragon
Click to expand...
Click to collapse
I think the usual comment about camera quality degrading still stands when using AOSP ROMs? Have yet to root the Samsung S8 but I'd like to do it soon, along with flashing a debloated ROM for my sister.
partcyborg said:
Aww that's a bummer, last I talked to him he was fine with other carrier use.
Click to expand...
Click to collapse
His rom has all the carrier info in it. He just doesn't update the op except the link to new rom.
Introducing the first Oreo ROM for the S8 and S8+, its basic don't complain.
First of all, before you go any lower read this:
THIS IS NOT ROOT! This is a custom system image that I modded and allows me to add or remove files and still have it boot and keep Knox intact along with Saftey Net. Unless you mess with the build.prop device stuff, Samsung Pay, Secure Folder, and Google Pay should all work.
Second, If you break your phone or mess up and it boot loops, just flash a stock image and start over. Don't come here crying over it not working because these do work and I have had testers use them and run this.
Third, this is pixelish because all I did was add the pixel launcher and a couple pixel files along with S9+ messenger. This is more of an open project.
Forth, If you are a dev interesting and making your own custom system image, message me and I will tell you the ways of this magic.
NOW FOR THE GOOD PART!
This ROM currently contains the stock Pixel launcher, a couple new /etc/sysconfig pixel files, and the S9 messenger. Knox still works and so does Saftey Net. This has yet to be debloated.
To install it:
1. Go to download mode and flash the file install BL.tar with Modded Odin, all files will be linked in like post 2 or 3, I don't know.
2. Reboot back into download and flash the system.tar (names may vary) in the AP slot with the options reparation and NAND erase all selected, you will also need to use the pit file there. This step will say fail in Odin but that's good.
3. Reboot BACK to download mode and flash the CRB9 AP, BL, and CP. In between the system flashing and this step, hit reset at the bottom of Odin to reset the options.
4. Let the phone reboot. It will boot loop, that's good. Now go to recovery and let this boot loop. It will say something about a cache error, that's perfect.
5. From recovery go to download mode, it might be difficult and you may get to upload mode, just keep holding the keys until you get there. Now flash the CSC file.
6. After flashing CSC you should be in recovery, now clear data and cache. Hit reboot the system or whatever and you should be good!
7. Enjoy whatever is in the ROM because I assume some people are going to link back here at some point.
THANKS to @me2151 for finding this and telling me how to do it and such
Downloads:
S8 Firmware: https://www.androidfilehost.com/?fid=818070582850502859
S8 System: https://www.androidfilehost.com/?fid=890129502657593102 (Might bootloop, if so just flash stock ROM)
S8+ Firmware: https://www.androidfilehost.com/?fid=890129502657592926
S8+ System: https://www.androidfilehost.com/?fid=673956719939832330
New Modded Odin: https://drive.google.com/open?id=1cFvAWFX4E5aqoKqSTR_Nf4h3HgzHUgY7 (this flashes all files)
How to mod it yourself!
This is a little thing on how to mod it yourself.
You need to download the system for the device, just use the one I have above. Then you need to mount it in Linux using the command sudo mount -o loop system.img.ext4 folder name. This should mount as an r/w. I did it in Kali Linux and didn't have issues while Ubuntu did some funky stuff. Then you mod the systems normally like making a ROM. Whenever you mod something you need to set the proper permissions with chmod and context with sudo setfattr -n security.selinux -v ubject_r:system_file:s0 filename. You might need to install attr to get it. Then once you're done, unmount with sudo umount folder name and then add it to a .tar file without any compression and flash it in Odin like the instructions. Just use your system instead of mine. If you make it and post it, just credit me2151 and me (mweinbach).
Told yall i was sitting on it til oreo release
This has such great potential. Thank you guys for bringing hope back to Snapdragon models!
Thanks so much.
mweinbach said:
Reserved 2
Click to expand...
Click to collapse
me2151 said:
Told yall i was sitting on it til oreo release
Click to expand...
Click to collapse
Nice:good::good::good:
Shame I cant try it yet
is there any way you can add csc of exynos variant to snapdragon
sahilg009 said:
is there any way you can add csc of exynos variant to snapdragon
Click to expand...
Click to collapse
Probably not.
Thanks a lot! Can you post how to create a custom rom on here for us devs?
I know this rom is for Snapdragon but is there any chance that your methods would apply to exynos firmware too? A custom non-knox tripping rom would be great
Nice work anyway!
JackJoeR said:
I know this rom is for Snapdragon but is there any chance that your methods would apply to exynos firmware too? A custom non-knox tripping rom would be great
Nice work anyway!
Click to expand...
Click to collapse
@me2151 you know what makes this work, can you check?
S8 files up!
Thanks for sharing this! :good:
What's the main difference between this and the Stock Samsung ROM? Does it have bloatwares if I install on my AT&T variant? I'm sorry, I'm asking since it's not listed on the first post exactly aside from a couple of things you mentioned.
sNoxious said:
Thanks for sharing this! :good:
What's the main difference between this and the Stock Samsung ROM? Does it have bloatwares if I install on my AT&T variant? I'm sorry, I'm asking since it's not listed on the first post exactly aside from a couple of things you mentioned.
Click to expand...
Click to collapse
This has bloat. It also has S9 messenger and pixel launcher. Also some pixel stuff. It's more what others can add.
mweinbach said:
This has bloat. It also has S9 messenger and pixel launcher. Also some pixel stuff. It's more what others can add.
Click to expand...
Click to collapse
I see, a debloated version would be a nice option!
Either way, thank you for your work! :good:
sNoxious said:
I see, a debloated version would be a nice option!
Either way, thank you for your work! :good:
Click to expand...
Click to collapse
I am going to do a debloated one at some point. For now, you can just disable the apps with like sabs.
mweinbach said:
I am going to do a debloated one at some point. For now, you can just disable the apps with like sabs.
Click to expand...
Click to collapse
I know I asked in telegram but is there anyway you can include viper or is that not possible becaue of root permissions?
adj998 said:
I know I asked in telegram but is there anyway you can include viper or is that not possible becaue of root permissions?
Click to expand...
Click to collapse
I can set perms, I am going to leave that to a better ROM dev who understands it more. I would probably kill it.
Hey @mweinbach, thanks for taking the time to make this rom! I have a quick question. I have an S8 and am currently running PartCyborgRom (build AQI6). Can I just flash the firmware and system files without doing anything else beforehand? If not, what steps should I take before installing this?
Hi I need the combination and firmware for the Samsung Galaxy SM-J337PVPU3ASC1
I flashed it with a combination file.. but now I'm stuck in the factory binary mode so I need to flash it again
with the stock firmware or whatever to get it working again
Was trying to do a google bypass and kinda goofed because I couldn't find the right firmware :/
If anyone could help me out I'd appreciate it!
I did same, on accident though, trying to bypass fpr lock after factory reset...honestly i think this phone is ****, being as nobody seems to know anythang bout it. I called asurian and got free replacement.
SaitoSama said:
Hi I need the combination and firmware for the Samsung Galaxy SM-J337PVPU3ASC1
I flashed it with a combination file.. but now I'm stuck in the factory binary mode so I need to flash it again
with the stock firmware or whatever to get it working again
Was trying to do a google bypass and kinda goofed because I couldn't find the right firmware :/
If anyone could help me out I'd appreciate it!
Click to expand...
Click to collapse
I did the same exact thing, so far I've figured out that with that being the newest flash of combination we upgraded the bootloader to binary 3 now, the only firmware that will work is going to be the PVPU3ASC2 which is April's update but online you have to have membership or pay to download, unless that's all a scam? I just did this same wipe on a j327p and had no problem going up from binary 2 to 3 and flashing stock ROM. But from what I understand there's a way to just turn factory off in the combination ROM. I've spent hours pouring over different avenues to go. I was going to change device id to j337U being the unlocked version but I'm getting stuck on gaining SU permissions in the Shell with this new factory binary ROM. I can get adb shell while it's running and side load from recovery but nothing installs or flashes. I believe it's running a sort I emulated VM instead of running ON the phones persistent memory.
FINALLY someone to talk to about this specific problem. It was my fault flashing the U3 combo instead of the U2arj2 I should've.
Attaining root J337p? Dirtycow?
To gain su permissions after reflashing stock have you tried using the dirtycow exploit. I have found it to be an almost fool proof method to attain temp root and for flashing twrp or cwm. Depending on the phone you may have to modify the source a bit but basically jus go to github and download the dirtycow zip or if your using Linux then use git clone and clone the Repository then extract it rename to whatever you want i use the simple dirtycow. put that and accompanying files on the root of the phone (/sdcard) . now use ADB push to push it to /data/local/tmp. Then ADB shell cd into /data/local/tmp and chmod 777 *. Once thats done depending on your phone its gonna be a little trial and error but use ./dirtycow /system/bin/applypatch /data/local/tmp/(the name of your dirtycow applypatch file). Then the same process with app_process or app_process64 depending on the phone. Reboot. That should take SElinux to permissive. Here is where things get tricky. ./dirtycow /system/bin/run-as /data/local/tmp/(name of your dirty run-as file). If you have the exact dirtycow applypatch file for your phone then proceed to thw next step otherwise do whatever mods you gotta do to get your file right. Now run-as exec ./(dirtycow)-applypatch boot. Once that is finished run-as su and presto you have temporary root to do whatever you feel like. I do the next step manually if youd like to. Download the appropriate twrp for your phone name it something memorable like twrp.img and move it to the /sdcard root of your phone. now su dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery. Reboot to recovery and you should be free to flash a permanent root method like chainfire supersu or magisk. And that is that. But i warn you not all phones store the recovery image there you may need to search around a bit. I use su ls -al /dev/block/bootdevice/by-name or cat /proc. Between those 2 i usually can find where it is. I claim no responsibility for bricked phones. Thank you. I will be doing this to my j337p later today ill let you know what i come up with
Ps. If your phone is relatively new its more than likley it has a property called dm-verity which is enable that is a huge pain and causes encryption to fail while flashing. There are .zip files online i believe called dmverityopt.zip or something to that effect i suggest flashing that before and after any custom rom flash. Or a custom kernel that doesnt have that problem.