[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 8 (Exynos) V3

Search This thread

anakara

Senior Member
Jul 9, 2013
303
104
Dear friends and readers of this thread

I started to work on oreo recently and read about your comments that the current twrp isn't compatible with oreo.

I got bored at university so I'm releasing the twrp now. I can't test it since I don't have my n8 with me, please let me know if everything works as expected :good:

Hence I decided (again) to build my own twrp version with the latest kernel sources (oreo) and the latest TWRP sources. So we got everything up to date! :fingers-crossed:

The update to oreo is the only change, I haven't changed anything else apart from this.

Download:
TWRP flashable img file
Odin flashable tar file
Thank You. Work on note 8

Gửi từ SM-N950F của tôi bằng cách sử dụng Tapatalk
 
Last edited:

kenpaci

Senior Member
Jan 2, 2011
731
197
Kuala terengganu
Dear friends and readers of this thread

I started to work on oreo recently and read about your comments that the current twrp isn't compatible with oreo.

I got bored at university so I'm releasing the twrp now. I can't test it since I don't have my n8 with me, please let me know if everything works as expected :good:

Hence I decided (again) to build my own twrp version with the latest kernel sources (oreo) and the latest TWRP sources. So we got everything up to date! :fingers-crossed:

The update to oreo is the only change, I haven't changed anything else apart from this.

Download:
TWRP flashable img file
Odin flashable tar file

Miss you man,lol
 

ANDROIDXFOREVER

Senior Member
Mar 8, 2014
1,322
400
sanremo
Dear friends and readers of this thread

I started to work on oreo recently and read about your comments that the current twrp isn't compatible with oreo.

I got bored at university so I'm releasing the twrp now. I can't test it since I don't have my n8 with me, please let me know if everything works as expected :good:

Hence I decided (again) to build my own twrp version with the latest kernel sources (oreo) and the latest TWRP sources. So we got everything up to date! :fingers-crossed:

The update to oreo is the only change, I haven't changed anything else apart from this.

Download:
TWRP flashable img file
Odin flashable tar file
thanks bro work great :D:good: i love this kernel
 

shouren04

Senior Member
Feb 17, 2013
1,092
400

VeEuzUKY

Senior Member
Oct 10, 2008
1,314
127
Ive successfully installed TWRP on my system. However I was unable to install TWRP 3.1.10 due to a binary error during the flash sequence with ODIN.. TWRP 3.2.10 flashed correctly.

Everything is still all stock under TW Oreo. What would you recommend to be the best rooting method, Magisk or SU? Ive always used SU in all my previous Samsung devices and never used Magisk before. I have no idea what I should do and worry to screw-up the new phone I just buy :p

Also, after the TWRP install, I get a message that no system updates are allowed because "the system has been modified in an unauthorized way". Is this normal or/and how to go around it?

Thanks a lot for the advice:)
 
Last edited:
Ive successfully installed TWRP on my system. However I was unable to install TWRP 3.1.10 due to a binary error during the flash sequence with ODIN.. TWRP 3.2.10 flashed correctly.

Everything is still all stock under TW Oreo. What would you recommend to be the best rooting method, Magisk or SU? Ive always used SU in all my previous Samsung devices and never used Magisk before. I have no idea what I should do and worry to screw-up the new phone I just buy :p

Also, after the TWRP install, I get a message that no system updates are allowed because "the system has been modified in an unauthorized way". Is this normal or/and how to go around it?

Thanks a lot for the advice:)

This is normal because you flashed something that is not signed by samsung. If you want OTA updates, flash stock firmware via odin.
If you want to root I suggest SuperSU because at my experience at magisk, root always disappears until next reboot. Use SuperSU until this problem with Magisk is fixed.
Edit: It's Magisk problem, not TWRP problem or Note 8 problem.
 
Last edited:

VeEuzUKY

Senior Member
Oct 10, 2008
1,314
127
This is normal because you flashed something that is not signed by samsung. If you want OTA updates, flash stock firmware via odin.
If you want to root I suggest SuperSU because at my experience at magisk, root always disappears until next reboot. Use SuperSU until this problem with Magisk is fixed.
Edit: It's Magisk problem, not TWRP problem or Note 8 problem.

Understood, thanks a lot for the info. The latest SU V2.82 is already one year old, and I found 2 variants with seemingly the same build but different file sizes, SR4-SuperSU-v2.82 and SuperSU-v2.82-201705271822. Not sure which would be better for the Note 8 but I assume either one should work.

Thanks again:)
 

TurricanM3

Senior Member
Feb 4, 2015
887
224
Anyone else noticed the short freeze after getting in the main menu? It hangs about 1-2s and ignores every input. Just wondering.
 
  • Like
Reactions: ghbuur

bobby2703

Member
Jun 18, 2012
9
1
Brilliant

Dear friends and readers of this thread

I started to work on oreo recently and read about your comments that the current twrp isn't compatible with oreo.

I got bored at university so I'm releasing the twrp now. I can't test it since I don't have my n8 with me, please let me know if everything works as expected :good:

Hence I decided (again) to build my own twrp version with the latest kernel sources (oreo) and the latest TWRP sources. So we got everything up to date! :fingers-crossed:

The update to oreo is the only change, I haven't changed anything else apart from this.

Download:
TWRP flashable img file
Odin flashable tar file
Thankyou so much for this .. no more installing data fix
 

Voytec83

Senior Member
Apr 25, 2017
451
625
Koszalin
I've noticed, it is very annoying,in fact it is also present in version 3.2.1-0 for Oereo.I doubt someone's gonna look on that matter.

Oh come on Guys... ? Please, don't make mountains out of the molehill... Just be happy that someone spend a lot of private time to make it work (probably even few people). And U are pointing 2-3 secs U 'have to wait'. Move back to stocks - no wait time then.

Thx to @geiti94 , @Tkkg1994 and all other Devs putting their efforts and time?
 

phongbv

New member
Mar 6, 2017
4
0
Guides:
Notice: It may wipe all your data including those in internal storage.

Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.

Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.) (for the moment not working)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/". (for the moment not working)
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.

TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.

Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.

Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.

I cannot find enable OEM Unlock option in Dev mode
 

sonhy

Senior Member
Apr 23, 2006
377
65
I think it would be super helpful to add to the instructions that, if you have the OEM Unlock issue that you always flash the RMM-State_Bypass_Mesa_v?.zip every time after a rom flash update. just saves one from having to download another stock rom and flash that to get rid of the unofficial binaries error when trying to boot.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 65
    Team Win Recovery Project 3.1.1

    https%3A%2F%2Ftwrp.me%2Fimages%2Fhome.png
    https%3A%2F%2Ftwrp.me%2Fimages%2Fbackupname.png


    Exynos ONLY.
    In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.


    Special Notes:
    1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
    2. KNOX will be tripped once you flashed custom binaries to your phone.
    (Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
    3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
    (You can flash custom ROMs if you want to keep the OS up-to-date.)


    Download: greatlte (Exynos variants - N950F/FD/X/N)
    https://drive.google.com/file/d/0B7EuVd0yZ8ErSE5EQW12TVEtcVk/view?usp=sharing

    Sources:
    https://github.com/TeamWin
    https://github.com/geiti94/android_device_samsung_greatlte
    https://github.com/geiti94/android_kernel_samsung_universal8895_greatlte

    Changelog:
    Check #2.

    Guide:
    Check #3.

    Bugs:
    -A mouse pointer shows on display

    XDA:DevDB Information
    [RECOVERY]TWRP for Galaxy Note 8 (Exynos), Kernel for the Samsung Galaxy Note 8

    Contributors
    geiti94, @jesec for the S8+ TWRP tree i used as base :)
    Kernel Special Features:

    Version Information
    Status: Beta

    Created 2017-09-16
    Last Updated 2017-09-21
    39
    New TWRP

    Hey guys

    Many of you (including myself) wondered, why there wasn't an official TWRP update available till now. So I decided to build one myself, with the latest source updates included from TWRP directly :)

    Changelog TWRP 3.1.1-0 -> 3.2.1-1
    • Allow restoring adb backups in the TWRP GUI (bigbiff)
    • Fix gzip backup error in adb backups (bigbiff)
    • Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
    • Better support for installing Android 8.0 based zips due to legacy props (nkk71)
    • Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
    • Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
    • Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
    • v2 fstab support (Dees_Troy)
    • Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
    • Various other minor bugfixes and tweaks
    • minui fixes (cryptomilk)
    • Better android-8.0 compatibility in ROM trees (Dees_Troy)
    • Fix missing library in android-8.0 (nkk71)
    • Fix inconsistent SDCard naming (DevUt)
    • Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
    • Fix USB OTG not working (Tkkg1994)

    Download:
    Odin Flashable
    TWRP Flashable

    If you enjoy I'd appreciate to see a thanks/thumbs up :good:
    33
    Guides:
    Notice: It may wipe all your data including those in internal storage.

    Part 1 - HOW-TO FLASH TWRP:
    1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
    2. Go to Settings -> Developer options and enable OEM Unlock option.
    3. Download and Install Samsung Mobile Phones Drivers.
    - Option 1: Download and Install Smart Switch for PC.
    - Option 2: Download and Install standalone driver package.
    4. Download and extract Odin (Samsung's Flash Tool) to your computer.
    5. Download a .tar image of TWRP.
    6. Reboot your device to download mode.
    - Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
    - Read the warning carefully.
    - If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
    7. Open Odin and place that TWRP tar file in the [AP] slot.
    8. Connect your phone.
    9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
    10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.

    Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
    1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
    2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
    3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
    4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
    5. Download the latest dm-verity and force encryption disabler zip on your computer.
    6. Transfer the zip to your phone.
    - Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.) (for the moment not working)
    - Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/". (for the moment not working)
    - Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
    7. Go to "Install" menu of TWRP and flash the zip.

    TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.

    Part 3 - HOW-TO ROOT:
    1. Download the flashable zip.
    - Option 1: Magisk
    - Option 2: SuperSU (untested)
    2. Transfer the zip to your phone.
    3. Go to "Install" menu of TWRP and flash the zip.

    Part 3a - HOW-TO FLASH CUSTOM ROMS:
    1. Download the flashable zip.
    2. Transfer the zip to your phone.
    3. Go to "Install" menu of TWRP and flash the zip.
    Simple.
    21
    Oreo TWRP

    Dear friends and readers of this thread

    I started to work on oreo recently and read about your comments that the current twrp isn't compatible with oreo.

    I got bored at university so I'm releasing the twrp now. I can't test it since I don't have my n8 with me, please let me know if everything works as expected :good:

    Hence I decided (again) to build my own twrp version with the latest kernel sources (oreo) and the latest TWRP sources. So we got everything up to date! :fingers-crossed:

    The update to oreo is the only change, I haven't changed anything else apart from this.

    Download:
    TWRP flashable img file
    Odin flashable tar file
    11
    Changelog:
    Sep.21
    Removed Mouse cursor. thx alot to @Tkkg1994 that joined now us too on n8 :D
    Added F2FS Support

    Sep.17
    Fixed MTP
    Fixed ADB

    Sep. 16:
    Initial Release