yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S6 Edge] tylerholbrook:
Yeah let me go get it

http://xdaforums.com/showthread.php?t=3082467

Haven't tried it with [MENTION=1124755]Aou[/MENTION] s kernel just yet. Getting it set up. Then going to nandroid then try.

---------- Post added at 08:47 PM ---------- Previous post was at 08:18 PM ----------

Confirmed this kernel v4 works with the Rom. Sweet. Now hopefully Goldie upgrades the Alliance framework to 5.1.1 and we will be right back where we were with 5.0.2
[T-Mobile Samsung Galaxy S6 Edge] Jdom58:
That's good to know, I was checking out the rom and it looks like he removed quite a bit of functionality by trimming it down so much. May wait until the aroma is completed to re-install some features.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Very nice! Glad to hear we've got options now for more ROMs for this device (considering it seems like so many developers are abandoning this device, or XDA altogether).

Completely unrelated, has anyone tried ADB with this recovery? As far as I can tell, the daemon, adbd, is indeed firing and is active. Running "ps" from the Advancd -> Terminal Command shows that it's running as it should. Killing it causes it to re-launch itself, too.

But no devices from Windows ADB... Tried a few different drivers (universal, samsung ... ) and a few different versions of adb (1.0.31 and 1.0.32). Has anyone else had better luck?

Noteworthy that adb works fine once the device is booted into the ROM.

Edit: tried it from my Linux box, also not successful.
[T-Mobile Samsung Galaxy S6 Edge] Lancerz:
Have you tried it with the kernel that comes with it as it should work from what I'm reading? I'll give it a go and see lol.
[T-Mobile Samsung Galaxy S6 Edge] tylerholbrook:
The aroma is complete. It's in post 2. I used it

---------- Post added at 10:32 PM ---------- Previous post was at 10:30 PM ----------

I used it with the kernel that came with it as well. It works. Just flashed this kernel as it is written specifically for our device

---------- Post added at 10:34 PM ---------- Previous post was at 10:32 PM ----------

Never tried adb or needed to use it. Good for pushing a back up from your pc to phone no? Since I have the 32gb that would actually come in handy
[T-Mobile Samsung Galaxy S6 Edge] Lancerz:
Cool, just checking!
[T-Mobile Samsung Galaxy S6 Edge] lurk3r2013:
Edited.
[T-Mobile Samsung Galaxy S6 Edge] Malnilion:
The main thing holding me back from that is the lack of Wi-Fi calling and VoLTE. It's a solid ROM, though, so the main thing I'm glad about is that all the S6 devices appear to be closely related enough that we should continue getting ROM support even if those ROMs don't support all the features of our carrier.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Bingo.
[T-Mobile Samsung Galaxy S6 Edge] tylerholbrook:
I'm curious how much work it takes to add VOLTE or wifi calling into the rom. I don't use either really so doesn't much matter to me
[T-Mobile Samsung Galaxy S6 Edge] wonderingabout:
Is there anyway to get back to stock of6 kernel and stock recovery after you root phone with twrp and custom kernel process and not lose root?
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
Thanks for your efforts guys. I am trying to build a device tree for Aou and once the build works I will make a twrp page on our site using this thread as the maintenance page.

I would be grateful if you guys could test http://build.twrp.me/twrp/twrp-2.8.7.1-zerolte.img.tar to see if it boots and works OK on this device.

I might have to update the prop file for zeroltetmo if you guys want to do that.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
D'oh! I have a private message hanging in my mailbox. Sorry, [MENTION=2638973]bigbiff[/MENTION]. I just flashed it, and it hangs at the boot logo. I'll try to replace the kernel inside with my v4 kernel and see if that lets it boot.

Edit: Yes, replacing the kernel inside indeed let the device boot into recovery. I'll send you a PM with the details.
[T-Mobile Samsung Galaxy S6 Edge] kswa1987:
Been following this thread closely, I've tried to use the thanks button as much as possible but I also just wanted to quickly say thanks to everyone for their hard work!!

Glad the G925T has such a great group of people supporting it.

:)
[T-Mobile Samsung Galaxy S6 Edge] lilmikey201:
where do i download your kernel? all i see that V10 has is twrp

im using a international rom so im trying to get audio to work also ?
[T-Mobile Samsung Galaxy S6 Edge] Aou:
The kernel download links are immediately above the TWRP download links in the OP.

kernels:

v1

v2

v3

v4

TWRP:

v9

v10
[T-Mobile Samsung Galaxy S6 Edge] Matce:
Is this also working for 920F ?

If yes, any known issues?

thanks!
[T-Mobile Samsung Galaxy S6 Edge] ktetreault14:
Is there any way to add drive drops support to the kernel?
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
Sorry guys, I posted the wrong link before, [MENTION=1124755]Aou[/MENTION] can you test http://build.twrp.me/twrp/twrp-2.8.7.1-zerolte.img.tar

It boots on my g9250 but the touch panel is different. I might look at that soon hopefully.
[T-Mobile Samsung Galaxy S6 Edge] Malnilion:
This one definitely boots. No graphical issues. Successfully makes backups. I think it's probably a winner ?
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
Does the read-only patch work?

Device Tree: https://github.com/TeamWin/android_device_samsung_zeroflte

Kernel with help: https://github.com/TeamWin/android_kernel_samsung_zerolte
[T-Mobile Samsung Galaxy S6 Edge] Malnilion:
Is the best way to test this to flash a stock kernel? I got the message on startup that it would not mount system if I was worried about bootloops, but I told it to allow write and not show the message again since I'm on the unikernel.
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
You need to flash stock odin tar and see if it allows you to boot. If it does, I need to update the fstab to allow emmc backups of system (dd).
[T-Mobile Samsung Galaxy S6 Edge] Malnilion:
Huh, okay, I might be able to test that later on.

Edit, just to clarify, we'd need to go fully stock, then flash this twrp, then boot into it and tell it not to write to system, then do a backup or something and afterwards see if it still boots?
[T-Mobile Samsung Galaxy S6 Edge] Aou:
It showed the read-only screen, despite a modified System. Re-downloading the omni source at the moment, I'll clone these two and build it again hopefully tonight.

Edit: Well, it built. And boots. I definitely had to replace kernAl with the kernel built from the source you mentioned. Without doing that, the kernAl included in android_device_samsung_zeroflte does not boot TWRP. Black screen.

I noticed that it's showing 2.8.7.0 in TWRP. Is that intented, or was something skipped in the github? ;)
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Alright, I've cleaned everything out and rebuilt from scratch, using the two sources [MENTION=2638973]bigbiff[/MENTION] provided. I've updated the first post considerably, including new, omewhat-more-detailed build instructions. I did not make any modifications to the source apart from what I noted in the OP.

Noteworthy that this new v11, built from source, does not seem to have the read-only warnings, even on a clean/unmodified system. I assume that the source currently does not have the read-only patch included at this time?

Also noteworthy that [MENTION=2638973]bigbiff[/MENTION]'s compiled recovery DOES prompt me about "unmodified system," whether or not the system has actually been modified.

I'll leave v11 up for now, but I'll be building a v12 once the read-only patch is included. ;)

(the warnings in the OP are fairly generic and self-explanatory now, so hopefully people get the idea about the risk of boot-loop...)

Edit: Note: after the warning screen, I proceeded with read-only. I reboot on stock firmware, and it was fine (because it didn't rename the file to .bak upon exiting). However, I reboot back into TWRP, and the warning was gone, and the checkbox was UNchecked! Seems that the read-only patch is only applicable for the first boot of TWRP?
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
The read-only patch has to be cherry-picked from the omni Gerrit. The version is usually arbitrary when I am building tests btw.

I will pass the information you said to [MENTION=912474]Dees_Troy[/MENTION], he has been the originator of the code for this particular issue on new phones coming with dm-verity.
[T-Mobile Samsung Galaxy S6 Edge] Matce:
guess my little post got lost...

does this also work for the G920F model?
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
The G920F has a different panel. I believe we are all using the G925F source from samsung.

I have major misgivings on using different panel drivers in the same kernel base without understanding any issues involved. This is why I am always just using the source from Samsung.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Thanks!

Part of the problem with our device is:

if (sys->Check_Lifetime_Writes() == 0) {

Specifically because, even on a STOCK, bootable, unmodified OF6 System partition on G925T, the lifetime writes is still about 36mb - or in this case, explicitly 39652. This happens because the OF6 patch (and Odin package) populates a patch into cache.img, and, upon first boot, it patches /system with this. So, the lifetime writes increments, but the system is still "Official". TWRP doesn't understand that, so it just doesn't care.

I would like to see the following changes:

a) Add a build parameter/flag that allows us to specify (in the device tree) at least 1 more value that is "considered" zero, such as 39652 in this case. Something like:

if (sys->Check_Lifetime_Writes() == 0 || sys->Check_Lifetime_Writes() == <some_build_variable_that_is_set_to_39652>) {

Or even if it were to check a list of variables (an array) that could be populated in the config. That'd probably be handy for rare cases, but I wouldn't worry about it too much - a single variable would be fine enough for this device/version.

b) It definitely needs to display this message every time, until the user makes a change to System (changes lifetime writes), OR they check the box for "never show me this again" (or whatever it says). Currently, even if the user chooses read-only on this screen and reboots back into TWRP, the warning is gone and TWRP begins mounting it read-write.

Thanks, guys! ^_^
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Just a minor correction: in this thread, we're using G925T source (for my kernel, at least).

I think the problem here is that the source for both devices ends in "OF6" ... but in reality it's "AOF6" and "COF6" ...
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
I will send another test build tonight with the updates by [MENTION=912474]Dees_Troy[/MENTION] https://gerrit.omnirom.org/#/c/14015/2/twrp.cpp
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Actually, I went ahead and cherry-picked https://gerrit.omnirom.org/#/c/14015/ and rebuilt. Version 12 is posted in the OP.

- The read-only warning does, indeed, show on the first boot of TWRP (if I delete my twrp settings file, pretending to be a new user), regardless of it detecting a modified System partition. This is excellent for our device. I would recommend EITHER:

a) changing the wording to make more sense if the system partition has indeed already been modified (currently it says, "TWRP may have detected an unmodified system partition"). If that were to show for every device, always, then it might be confusing. Or,

b) make this a build flag/parameter that can be enabled per-device.

Otherwise, the fact that this shows is excellent!

- If selecting Read-Only, rebooting into TWRP again does indeed keep the "only mount system read-only" checkbox intact, as it should. Excellent!

- The "Never show this screen during boot again" is somewhat arbitrary in this situation, because it never will show again. Ever. (unless the user deletes TWRP settings).

But otherwise, cherry-picking that change is making TWRP work really well. Thanks!
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Forgot to mention that ADB is working well with the new source. Thanks again!
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
Once all testing is done I will push the build out to dl.twrp.me. Are you OK with being the maintainer for this thread?

Please test http://build.twrp.me/twrp/twrp-2.8.7.1-zerolte.img.tar

I added the ability to backup system as emmc instead of tar so that you will not change lifetime writes.
[T-Mobile Samsung Galaxy S6 Edge] Jdom58:
OK so if I'm already running v10 and v4, do I just need to Odin v12
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Neat! What method is the R/O backup using?

And sure! At least until April/May of next year when The Next Big Thing is Here™ ...

Yup! It will write right over it, no issues.
[T-Mobile Samsung Galaxy S6 Edge] mjdavis871:
Flashed the file using flashfire, booted into recovery fine...wasn't sure which option to use at boot so I chose not read only...hopefully that isn't a mistake. Ran a backup...all seems to be ok. Don't have any roms to flash so I haven't tried that yet.

Thanks for the hard work guys.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
The R/O backup/restore is working exactly as expected. For example:

- Restored to OF6 stock.

- Upgraded to OF8 via 3e.

- All is still official.

- Flashed TWRP (your latest test).

- Booted to system and reboot - it restored 3e recovery.

- Flashed TWRP again.

- Immediately booted to TWRP.

- Kept it R/O, took a R/O backup of System (stock) and a backup of Boot/kernel (stock).

- Flashed SuperSU and my v4 kernel.

- Booted system, works fine.

- Rebooted into TWRP, works fine.

- Restored System R/O, restored Boot/kernel (stock).

- Reboot into System, boots fine (no root).

- Reboot into Recovery, and it's back to 3e (the system flashed the 3e again).

- Reboot to System - all is official again.

- Flashed TWRP, kernel, root again because I like it better that way.

Note: you did update the version to 2.8.7.1, but we lost the fonts.
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
Don't pay attention to version #s during tests. I will look into the font issue.

Edit, test http://build.twrp.me/twrp/twrp-2.8.7.1-zerolte.img.tar
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Yeah, figured worth mentioning, but I guess not. ;)

Test boots fine, seems to work fine. But I can't seem to notice any changes between this and the previous test. Font is still not there:

E:Resource (font)-(fixed) failed to load

By the way, when I was compiling from the zeroltetmo source (v7, v10), I had this same message and lack of fonts. When I got the zeroflte image to work (by swapping kernels), the fonts worked fine. A few tests ago (when I built the v12 from the updated zeroflte source), the font was fine there, too (and of course, no error).
[T-Mobile Samsung Galaxy S6 Edge] bigbiff:
Hmm, can you try http://build.twrp.me/twrp/twrp-2.8.7.1-zerolte.img.tar

I removed TW_NO_TTF from the build.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
Working great! Anything specific I should test out (What's changed?)? Otherwise, seems fully functional. I didn't do the "full test" I described before, but I'm feeling especially lazy today.
[T-Mobile Samsung Galaxy S6 Edge] Jdom58:
After I Odin v12 do I let the phone boot up automatically or do I not and manually boot into recovery and what choices do I select on first not into twrp, thanks
[T-Mobile Samsung Galaxy S6 Edge] wonderingabout:
I know how to root both g925t on 5.1.1 with twrp and v4 kernel without tripping knox or g925t and g920t with unikernel also without tripping knox...if you are nice i might tell you :)

I dare someone to say it is impossible LOL

Fully rooted and KNOX WARRANTY VOID: 0 (0X0000)
[T-Mobile Samsung Galaxy S6 Edge] tylerholbrook:
Lol Knox was out the window from day one for me. Phone breaks smash it. Insurance or lost it. Never had a phone break other than my dropping it anyways. And the pay I could care less about

That being said I'm sure others will appreciate this
[T-Mobile Samsung Galaxy S6 Edge] wonderingabout:
Here is how you root g925t and g920t on 5.1.1 without tripping knox. All credit for rooting method go to original developers. I in no way take any credit for their hard work whatsoever.

Download These Files

1. Samsung USB Drivers (Click Here)

2. Odin v3.10.6

3. SuperSu v2.49

4. UniKernel

5. Auo's v4 kernel

6. Auo's TWRP v12

7. MOD EDIT: Sorry, Samsung have requested this link be removed.

7b. MOD EDIT: Sorry, Samsung have requested this link be removed.

If you plan on using the Unikernel to root your g925t or g920t on 5.1.1 use these steps

1. Install Samsung USB Drivers if necessary.

2. Put phone into download mode. Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.

3. Plug phone in and wait for drivers to install if necessary.

4. Open odin you should now see phone's modem port highlighted in blue.

5. Click on BL tab and select correct sboot.bin that you downloaded above. Then click start.

6. When phone comes back on power off again and put into download mode.

7. Open odin again and this time select AP tab and select UniKernel file and click start.

8. That is it!!! When it comes back on phone will be rooted. To verify that knox has not been tripped go back to download mode and it should still say KNOX WARRANTY: 0 (0X0000)

If you plan on using Aou's Kernel and TWRP to root your G925T on 5.1.1 (DO NOT USE THIS FOR G920T) use the steps below

1. Install Samsung USB drivers if necessary.

2. Copy and Paste SuperSU v2.49 on the root folder of your phone's internal memory.

3. Put phone into download mode. Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.

4. Plug phone into computer and let drivers install if necessary.

5. Open odin and click on BL tab and select sboot.bin file for g925t and click start.

6. When phone is back on put back into download mode again.

7. Open odin again and this time select AP tab and flash Aou's TWRP file and hit start.

8. When phone is back on put phone into download mode one last time.

9. Open odin and select AP tab and select Aou's v4 kernel and click start.

10. When phone is back on unplug it and power it off and put into recovery mode (Volume up, home and power keys)

11. When TWRP recovery is open click on install tab and select supersu file and swipe to flash it. then reboot phone to system.

12. That is it!!! When it comes back on phone will be rooted. To verify that knox has not been tripped go back to download mode and it should still say KNOX WARRANTY: 0 (0X0000)

IT IS VERY IMPORTANT THAT YOU FLASH THE FILES IN THE ORDER THE INSTRUCTIONS TELL YOU TO FLASH THEM!!!

---------- Post added at 08:08 PM ---------- Previous post was at 07:55 PM ----------

If for some reason after you flash UniKernel and phone screen turns white after on main screen for few seconds Just flash Aou's v4 kernel. That will fix that issue if it happens and you will still be rooted.
[T-Mobile Samsung Galaxy S6 Edge] Aou:
While we appreciate your findings and posting these instructions, I feel obligated to warn people about flashing bootloaders (sboot.bin) to their devices, as there are potential risks with this sort of thing. I did notice that the sboot.bin for 925t that you've posted is NOT identical to the one included in the official OF6 Odin tar, nor is it identical to the one included in the OF8 update.zip. Can you tell us where this sboot.bin came from?

All that said, I don't know if I would ever trust rackcdn.com: https://www.google.com/safebrowsing/diagnostic?site=rackcdn.com/
[T-Mobile Samsung Galaxy S6 Edge] wonderingabout:
Racdcdn.com is my private server on rackspace.com. Those sboot bin files are official samsung stock engineering bootloaders. They are used by samsung service techs everyday to service phones. Flashing that to the phone is like giving warm milk to a baby. Hopefully you can learn something from them..
[T-Mobile Samsung Galaxy S6 Edge] Aou:
If you boot "normally" into the system after flashing the TWRP recovery, and you've made no other changes, your system will likely automatically replace TWRP with the stock e3 recovery. It's actually really good at doing that. ;)

I would recommend downloading the SuperSU zip, and the v4 kernel zip and saving those to your SDCARD before even flashing TWRP via Odin. This way, you'll be able to flash them in TWRP upon your first time entering TWRP.

That being said, a good way to avoid this is to, indeed, boot directly into TWRP recovery immediately after flashing it. Given your Odin is configured to reboot after a successful flash (usually is by default, I think), you can do this by pressing the Start button in Odin, and then swiftly switch to the phone and start holding the VOL-UP, Power, and Home buttons. The device will reboot right after flashing the recovery, and if you're holding down those keys, it will of course boot straight into recovery. You'll be able to easily tell it's doing so, because it'll say "RECOVERY IS NOT SEANDROID ENFORCING" across the top of the screen (which, alone, is usually enough to trip KNOX on a stock bootloader). So, if you see that, you're definitely booting into TWRP and can let go the buttons.

Anywho, when you boot TWRP the first time, you'll get the warning about Read-Only. You should be able to still flash the v4 kernel and the SuperSU, even if it's in read-only mode, so there's little reason to let it go into Read-Write mode.

And from the main TWRP screen, you'll want to use "install". Scroll down and/or navigate around to find the two .zips from earlier, and select those to flash them. After flashing one, you can use the "back" softkey to return to the previous screen so that you can select the 2nd one to flash. Once done, just reboot. You should be all set.

I believe it's the SuperSU package that disables the System from automatically replacing your TWRP recovery with 3e, so there's other benefits to it besides the obvious root.
[T-Mobile Samsung Galaxy S6 Edge] wonderingabout:
and even if you have already tripped knox you can still flash the sboot bin and replace that annoying "RECOVERY IS NOT SEANDROID ENFORCING" with pretty green letters instead. no way to untrip knox though. my tutorial is for people who have not tripped knox yet.
[T-Mobile Samsung Galaxy S6 Edge] elliwigy:
this bl only work on tmo?
[T-Mobile Samsung Galaxy S6 Edge] ScottBroker:
ARE YOU SURE THIS WILL WORK? I WILL HAVE TWRP, AND ROOT AFTER THIS ON MY TMO G6? Do not want to brick another phone.

I have the normal G6 G920T

---------- Post added at 12:25 PM ---------- Previous post was at 12:09 PM ----------

Has anyone actually done this and it is ok? I think I may just wait for CF autoroot.....
[T-Mobile Samsung Galaxy S6 Edge] NexVision:
I can tell you this will not brick your phone and you will have root after if using the S6 Edge. However cannot verify for S6 and I cannot verify the validity of Knox as I was already tripped my counter did not go up but since I was tripped cant say it wont.
[T-Mobile Samsung Galaxy S6 Edge] ScottBroker:
Thanks, I'll wait until someone tries it on the regular s6.
[T-Mobile Samsung Galaxy S6 Edge] ScottBroker:
I did it, and it worked :)
[T-Mobile Samsung Galaxy S6 Edge] vfox126:
Has anyone tried it yet?
[T-Mobile Samsung Galaxy S6 Edge] kswa1987:
Ummmm tried this recovery? I Odin flashed v12 of the recovery and then booted right into it and then wiped / flashed xtre sto lite. Works great.
[T-Mobile Samsung Galaxy S6 Edge] jrock79:
How? I tried this kernel on my tmo s6 and it didn't work for me.
[T-Mobile Samsung Galaxy S6 Edge] mjdavis871:
Flashed the newest version of simple kernel and all is good...looks like we got a winner!
[T-Mobile Samsung Galaxy S6 Edge] Master&Slave™:
Did you lose call audio?
[T-Mobile Samsung Galaxy S6 Edge] ScottBroker:
I lost call audio using the UNI kernel. Tried the zip from Mr. Fix, and it did not work, so now I am back to stock no root :(

G920T

5.1.1 BL

Does the Kernel in this thread work for G920T?