delete

Status
Not open for further replies.

TheBigEasy88

Senior Member
Aug 12, 2016
122
72
38
I asked the op to at least take samfail out of the name, as I have no idea what this is or how it even works or if it's rooted. I do know for sure it's not the end firmware as our devices can't even boot them.
@TheBigEasy88 ok since you all sorts got the bait and switch here I will try and see what I can do this week if you are able to test it. A lot of my s8 rom was trial and error though so it may be difficult. Although someone with a s8+ accidentally flashed my s8 rom and it worked fine outside of the screen being rotated. So maybe I can confirm it at least doesn't bootloop myself.

I can at least do the heavy debloat (while keeping most of the useful Samsung features) and deodex. I may need to have you all flash a zip instead of preinstalling the mods I added cause I had to do those on the phone. Let me see if I can find some time this week to knock this out.
I'm your man Boss! Appreciate the efforts in advance!!!
 

stillriza

Senior Member
Jul 19, 2009
125
26
0
In the space
I asked the op to at least take samfail out of the name, as I have no idea what this is or how it even works or if it's rooted. I do know for sure it's not the end firmware as our devices can't even boot them.
@TheBigEasy88 ok since you all sorts got the bait and switch here I will try and see what I can do this week if you are able to test it. A lot of my s8 rom was trial and error though so it may be difficult. Although someone with a s8+ accidentally flashed my s8 rom and it worked fine outside of the screen being rotated. So maybe I can confirm it at least doesn't bootloop myself.

I can at least do the heavy debloat (while keeping most of the useful Samsung features) and deodex. I may need to have you all flash a zip instead of preinstalling the mods I added cause I had to do those on the phone. Let me see if I can find some time this week to knock this out.
Haha! Not to hijack the thread but, yes!! Really looking forward to this as well! If time/life permits I mean, no pressure! :D
 
  • Like
Reactions: ExLite23

lightninbug

Senior Member
Sep 17, 2009
4,968
1,789
0
ive had eng bootloader since before releasing sampwnd.. it wont boot with combo boot.img which is needed for root so i didnt release them.. but no, it doesnt enable fastboot
Has there been any progress towards twrp on the snapdragons? Been out of the loop for awhile.
 

jhofseth

Senior Member
Feb 27, 2016
457
239
43
Seattle, Washington
Has there been any progress towards twrp on the snapdragons? Been out of the loop for awhile.
Bootloader unlocked Chinese & Hong Kong Snapdragon S8/S8+ only TWRP:
https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/recovery-twrp-galaxy-s8-s8-snapdragon-t3636718
If you flashed TWRP to a locked bootloader US Snapdragon S8/S8+, you could still boot into Android OS normally; but, the instant you tried to reboot into recovery (e.g., type su, then type reboot recovery in Android terminal as root; or, via normal adb, as with adb reboot recovery) or boot into recovery (i.e., button combo press), you would get a scary-looking warning screen. At that point, you could button combo press into download mode, then press volume down to boot normally. Secure boot just won't allow us to access a custom recovery. I've experimented a couple times but first made a dd backup of official recovery partition, which I simply dd flashed back after booting normally into rooted Android OS. :)
 
Last edited:

moocman42

Member
Nov 13, 2017
30
8
0
Bootloader unlocked Chinese & Hong Kong Snapdragon S8/S8+ only TWRP:
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
If you flashed TWRP to a locked bootloader US Snapdragon S8/S8+, you could still boot into Android OS normally; but, the instant you tried to reboot into recovery (e.g., type su, then type reboot recovery in Android terminal as root; or, via normal adb, as with adb reboot recovery) or boot into recovery (i.e., button combo press), you would get a scary-looking warning screen. At that point, you could button combo press into download mode, then press volume down to boot normally. Secure boot just won't allow us to access a custom recovery. I've experimented a couple times but first made a dd backup of official recovery partition, which I simply dd flashed back after booting normally into rooted Android OS. :)
I've flashed twrp on my s8 and all it did was fail in Odin. Just reboot and that was it
 

jhofseth

Senior Member
Feb 27, 2016
457
239
43
Seattle, Washington
I've flashed twrp on my s8 and all it did was fail in Odin. Just reboot and that was it
I've attached screenshots to show commands, etc. This is just to show that you can still use your bootloader locked US Snapdragon with a custom recovery installed (i.e., booting & re-booting normally), it's just that secure boot won't let you access the custom recovery and puts up a scary-looking warning screen that gives the illusion of bricking. :)

Pic 1: scary-looking warning screen due to rebooting to custom recovery (combo button press to download mode, then press down to boot normally into Android OS)
Pic 2: TWRP download page for S8+ Snapdragon (must extract recovery.img from .tar)
Pic 3: dd commands in root Android terminal to flash downloaded TWRP (after zeroing recovery partition)
Pic 4: 26MAR2017 combo kernel info (tested TWRP with two different combo firmware versions)
Pic 5: 02NOV2017 combo kernel info
Pic 6: flashing with Prince Comsy Odin the latest combo recovery.tar to flash back to normal
Pic 7: Prince Comsy Odin latest combo recovery.tar successful flash

Note: In Pic 6 you will see 4 files from currently latest S8+ combo (archived by 7-Zip into .tar files with store compression level), and the entire ROM of currently latest stock T-Mobile firmware. Relatedly, the only partitions I have that are currently latest combo firmware are: boot.img, abl.elf, devcfg.mbn and recovery.img. The latest stock T-Mobile system.img.ext4 was pre-rooted by me, dd copied from an actual rooted system partition, then added by 7-Zip to a .tar archive with store compression level to be flashed via SamFail method. I'd been consistently updating system partition with latest stock T-Mobile system.img.ext4 + SuperSU system root zip with FlashFire--prior to the aforementioned dd copying, etc.. As such, the dd copying of the pre-rooted system partition was merely to facilitate making sure SamFail still worked with latest currently available S8+ combo + stock T-Mobile firmware.
 

Attachments

Last edited:

TheBigEasy88

Senior Member
Aug 12, 2016
122
72
38
Thanks for sharing, jhofseth! In your opinion, will this phone ever see a working custom recovery (TWRP) or should we just man up and get used to the fact that what we currently have is the best options available? Interesting stuff nonetheless.
 
  • Like
Reactions: jhofseth

jhofseth

Senior Member
Feb 27, 2016
457
239
43
Seattle, Washington
Thanks for sharing, jhofseth! In your opinion, will this phone ever see a working custom recovery (TWRP) or should we just man up and get used to the fact that what we currently have is the best options available? Interesting stuff nonetheless.
It will a long time from now when someone figures out how to unlock our bootloader, but that could take a couple years. Phones will likely be much better then with solid-state glass batteries, etc., so we won't care anymore! :)
https://about.bnef.com/blog/goodenough-making-progress-solid-state-batteries-qa/
 
  • Like
Reactions: TheBigEasy88

jhofseth

Senior Member
Feb 27, 2016
457
239
43
Seattle, Washington
Last edited:
  • Like
Reactions: djcrystals
Status
Not open for further replies.