Team Win Recovery Project
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
Code:
Disclaimer: Your warranty is now void!! I won't be responsible if you flash this on another device besides the prescribed device mentioned..
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
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, European Union for example, forces Samsung to provide hardware warranty regardless of software status.)
More Information from here
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.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
Download: https://github.com/zeroblade1984/samsung_exynos8895/releases/tag/TWRP
Sources: https://github.com/TeamWin
If you love the work you can rate the thread or spare me some beer
XDA:DevDB Information
TWRP, Tool/Utility for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
kairi_zeroblade
Version Information
Status: Stable
Current Stable Version: Update 6/9
Stable Release Date: 2018-06-09
Created 2017-12-20
Last Updated 2018-06-09
Changelog
January 21, 2018
Fixes for touch/responsiveness
Faster Backup and Restore speeds
Should boot up faster than previous
December 20, 2017
Update TWRP base to 3.2.1-0
Use an upstream bringup(dirty) of kernel, credits to @jesec and @geiti94
Bugs: None
Flashing Instructions
Notes: It may wipe all your data including those in internal storage.
Part 1a - HOW-TO FLASH TWRP (for new devices w/o TWRP yet):
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 1b - HOW-TO FLASH TWRP (for devices that already had an earlier build of TWRP):
1. Download the recovery.img from the download page.
2. Place the downloaded image file on your device's memory (internal or external storage or OTG may do).
3. reboot to TWRP either from your Custom ROM menu or by using the previous method where you hold [VOLUME UP] + [BIXBY] + [POWER] when your phone is completely OFF.
4. Go to Install->(locate the file you downloaded)->on the bottom part of TWRP menu you will see flash image, go press it->then you can now select the image file->then choose recovery if you are prompted to what partition you are going to flash->swipe to flash->Profit!!
5. It may be best to reboot to recovery once the procedure is done just to check if things went fine. :good:
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.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- 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.
Thank you very much for your fine work.
I went to the download site, and the file TWRP-3.2.1.0-greatlte.tar does not seem to work with the latest Odin for some reason.
So I used the recovery.img via the older TWRP on the phone and all good.
Tnx team...got the .img and flashed...reboot in recovery...and working like a charm...realy appreciate the works ??
Sent from my SM-N950F using XDA-Developers Legacy app
Thanks for the work!
Enviado desde mi Galaxy Note 8 mediante Tapatalk
What's the difference between this and the original thread? Is this a newer version that's actively maintained? [emoji846] Thanks
white7561 said:
What's the difference between this and the original thread? Is this a newer version that's actively maintained? [emoji846] Thanks
Click to expand...
Click to collapse
This is the newest version. The other is a older version and i think from maintainer. No more Supports, because there are no new Updates since months
Sent from my Galaxy Note 8 using XDA Labs
white7561 said:
What's the difference between this and the original thread? Is this a newer version that's actively maintained? [emoji846] Thanks
Click to expand...
Click to collapse
Yes this is newer upstream (uses android-8.0 branch from Omni) and I will try my best to keep it up-to-date..
I am also looking for kernel testers as I, alone testing my work will be Bias (I do own both S8 and Note8)
kairi_zeroblade said:
Yes this is newer upstream (uses android-8.0 branch from Omni) and I will try my best to keep it up-to-date..
I am also looking for kernel testers as I, alone testing my work will be Bias (I do own both S8 and Note8)
Click to expand...
Click to collapse
So I could just flash this over the old twrp? Also. Any bugs? Thanks so much eh [emoji846][emoji16]
white7561 said:
So I could just flash this over the old twrp? Also. Any bugs? Thanks so much eh [emoji846][emoji16]
Click to expand...
Click to collapse
You can Either use Odin (I re-uploaded a new Tarball) or just flash the image via an earlier version of TWRP..so far this has no bugs, I tried ADB sideload, backup and restore and had no issues..
kairi_zeroblade said:
You can Either use Odin (I re-uploaded a new Tarball) or just flash the image via an earlier version of TWRP..so far this has no bugs, I tried ADB sideload, backup and restore and had no issues..
Click to expand...
Click to collapse
Done. Installed using twrp method. Worked fine. Anyway. Thanks
is it necessary to initialize (wipe/format data) when updating over old twrp?
Wow! I've been out of the Android game for 6 months and it feels damn good to be back, first stop, TWRP lmao!
Sent from my [device_name] using XDA-Developers Legacy app
Hi guys, sorry for the offtopic, what exactly "greatlte" means?
infrasonic13 said:
Hi guys, sorry for the offtopic, what exactly "greatlte" means?
Click to expand...
Click to collapse
Greatlte is the codename for Samsung Galaxy Note 8 Exynos edition. Powered with Samsung Exynos 8895 processor.
Sent from my SM-N950F using Tapatalk
Edit: Tried it a 2nd time and now it was working. The 1st time I flashed the recovery, rebooted into recovery and started the backup. Guess that this was the problem.
Hi,
I just installed the new TWRP 3.2.1.0 and tried to make a full backup.
But it was not finishing it. After more than 45min I canceld it.
Please find enclosed the log file which was created. Hope it helps
Best regards,
dingolino
I dont get it. Why make this thread when there already is a twrp thread ?
Zionator said:
I dont get it. Why make this thread when there already is a twrp thread ?
Click to expand...
Click to collapse
'Cause it's another maintainer
kevinblackwell said:
'Cause it's another maintainer
Click to expand...
Click to collapse
What do you mean?
What's the difference between this and the other ?
Related
{
"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"
}
Introduction:
MultiROM is one-of-a-kind multi-boot mod for Galaxy J5. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.Features:
Multiboot any number of Android ROMs
Restore nandroid backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android.
Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. If something goes wrong you will have to flash factory images again. Make backups. Always.
Installation:
1) Flash the Modified TWRP image with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature.
2) After flashing the recovery image boot into the recovery and Flash the MultiROM zip.
3) That's it you're done. Reboot into system and the multirom menu will show up.
Enjoy!!
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - Not needed for our device.
Your current rom will not be erased by the installation.
Downloads are in 2nd post!!
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings. (it has been set to this option by default)Adding ROMs:
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet):
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs:
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one:
To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus:
Main menu:
Add ROM - add ROM to boot
List ROMs - list installed ROMs and manage them
Inject boot.img file - When you download for example kernel, which is distributed as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
Inject boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - well, settings.
Manage ROM:
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
How does Kexec workaround works:
You need to have a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
NOTE: Stock Lollipop Firmware required. Will not work on MM bootloaders.
Credits:
A big thanks for:
@nkk71 For his kexec workaround
@Tasssadar For MultiRom Source Code
@Nick Verse
XDA:DevDB Information
MultiRom for Galaxy J5, Tool/Utility for the Samsung Galaxy J5
Contributors
ganesh varma
Source Code: https://github.com/Galaxy-J5
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2016-12-18
Created 2016-12-18
Last Updated 2016-12-19
Reserved
Downloads:
MultiRom TWRP Recovery:
Recovery Images for LL Bootloader:-
J500F
J500FN
J500G
J500H
J500M
J500Y
MultiRom ZIP Installer: multirom-20161218-v33-UNOFFICIAL.zip
Changelog:
Code:
18.12.2016
=====================
* Initial release
NOTE: Stock Lollipop Firmware required. Will not work on MM bootloaders.
Hit that Thanks button if you like my work!!
Awesome work bro @ganesh varma ..
Congrats & all the best.. :good::good:
That's really cool buddy.
I'm very impressed
Nice one
John
Sent from my Honor 8 using XDA Labs
Uhh, so that means i can dualboot in android?
anyways, cool
Alright! Time to get our hands dirty ?
Great job @ganesh varma and @Nick Verse to port this Mod to our J5. Thankyou so much!
Nice work bro @ganesh varma
????????
Great job. Just noticed that the screen resolution is not okay. It seems somehow it zoomed a bit in....
Will the data partition be the same for both ROMs or different??
I have installed a new ROM in external SD. When I try to boot it, I can't find it, why??
updesh94 said:
Will the data partition be the same for both ROMs or different??
Click to expand...
Click to collapse
No the secondary ROM creates a folder in the internal storage and uses it as data partition. The two roms have their own data partitions.
MiGuPa said:
I have installed a new ROM in external SD. When I try to boot it, I can't find it, why??
Click to expand...
Click to collapse
Did you see by swiping right to the External tab on the multirom menu? The roms installed to SD card will be shown under External tab in multirom menu.
I think that it's so cool that you have made this for the J5
Good work
Thanks for your time
John
ganesh varma said:
Did you see by swiping right to the External tab on the multirom menu? The roms installed to SD card will be shown under External tab in multirom menu.
Click to expand...
Click to collapse
Yes, I also stayed there, and any new
Good Work, man!
works in J500M?
luisfelipee said:
Good Work, man!
works in J500M?
Click to expand...
Click to collapse
Nope, read the #2 post man... For now only F and FN models.
Sent from my SM-J500FN using XDA Labs
Mixed Review!
ganesh varma said:
No the secondary ROM creates a folder in the internal storage and uses it as data partition. The two roms have their own data partitions.
Click to expand...
Click to collapse
So I tried the multirom, It's working absolutely great.. No issues in any rom...
I installed Stock Lollipop primary rom and Resurrection rom as the secondary rom...
Glitches---
1. In the boot menu where OS are displayed if we tap the multirom icon, a ping pong game starts which says "to exit press power button" but then we are stuck in it and only possible way is to remove battery... :laugh:
2. Sometimes the selected rom doesn't boot and nothing happens.. only 1/10 times... :silly:
3. Storage becomes low in /data and /system has a lot of space, can u suggest a way to transfer dalvik-cache of primary rom to /system ??I tried one but it didn't work!!
By the way, It seems awesome to multiboot Roms...
I'm using j500F btw...
Now I tried to install an ROM on internal memory, and when I tried to boot:
JosephDM said:
Nope, read the #2 post man... For now only F and FN models.
Sent from my SM-J500FN using XDA Labs
Click to expand...
Click to collapse
thanks for reply. i asked cuz some F roms works in M model
updesh94 said:
So I tried the multirom, It's working absolutely great.. No issues in any rom...
I installed Stock Lollipop primary rom and Resurrection rom as the secondary rom...
Glitches---
1. In the boot menu where OS are displayed if we tap the multirom icon, a ping pong game starts which says "to exit press power button" but then we are stuck in it and only possible way is to remove battery... :laugh:
Click to expand...
Click to collapse
try press volume down + power button till restart.
to recovery mode when cel stuck, press all buttons (vol+, Vol-, Home and power) when screen off leave 'vol-' only and keep others
Update
Multirom for J500G,J500H,J500M and J500Y variants is now available. Can be downloaded from the second post!!
These recovery images are for LL bootloader's. Multirom for MM bootloader's will be available by the end of next week. :good:
Make sure that you have read all the instructions from the first post when you ran into problems. Everything is mentioned over there.
thanks @ganesh varma...its really awasome i m using on j500f.
TLDR:
1: MAKE A BACKUP. Seriously.
2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
{
"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"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for OnePlus 2. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still experimental!
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via USB-C OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_oneplus2_YYYYMMDD.img) - download the IMG file from second post and use fastboot to flash it.
MultiROM (multirom-YYYYMMDD-vXX-oneplus2.zip) - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/nkk71/multirom/tree/master (branch master)
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project (branch android-7.1-mrom)
Device tree: https://github.com/MZO9400/device_oneplus_oneplus2-mrom -b twrp-mrom
Thanks
This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.
Issues
- None that are known. If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it in the thread
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
Changelog
Here
Downloads
Downloads in second post
NOTE:
Third party kernels with kexec-hardboot support (can be flashed to primary ROM): THIS IS NO KEXEC MultiROM, you don't necessarily need kexec hardboot supported kernels
Extra Information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error
XDA:DevDB Information
MultiROM for OnePlus2, Tool/Utility for the OnePlus 2
Contributors
MZO, nkk71, martinusbe
Source Code: http://github.com/multirom-dev
Version Information
Status: Stable
Current Stable Version: v33b
Stable Release Date: 2017-05-13
Current Beta Version: v33b
Beta Release Date: 2017-04-20
Created 2017-04-20
Last Updated 2017-05-13
MultiROM (folder):
DOWNLOAD
MultiROM v33b
TWRP MultiROM v3.1.1
MultiROM Uninstaller
MultiROM manager modified with OP2 commits has been attached to this post
Method of flashing multirom.
________________
1. Go to TWRP 3.1.0 officially that u already have
2. Flash the multirom image file .. and select recovery when it asks whether u want boot or recovery.
3. When successful go back to maim page and hit reboot recovery
4. Now its multirom
5. Flash the provided multirom zip file. An auto reboot will occur. Hit cancel and go to MISC tab to hit reboot recovery
6. Now the existing rom u had , is primary
7. Go to 3 dot menu of TWRP on upper right corner.
8. Select add rom
9. Flash desired rom
10. Reboot recovery again when successful
11. Go to 3 dot menu again and select list rom
12. Tap on add zip file and add gapps here... That is whatever u file want to flash on a rom just select that rom from rom list and add zip from there
[when flash a secondary, u have to flash zip, then back, and add zip and flash gapps]
13. Hit reboot system.
14. Now a screen will appear even before boot to.ask which rom u want to flash. For the very first time the option is set to, if u don't select any it will boot to primary after 5 seconds, so u hit cancel on that screen (pop up actually)
15. Select the desired rom , double tap on it and it will boot.
First boot of a new rom takes at least 15 to 20 real life minutes.
Notes:
__
To change the option of count down of rom booting selection, go to settings of multirom twrp and turn off option from there. Now every time u reboot.. it will ask which rom u want to boot. And if u don't select any it will stay on same screen till u click something
Tested so far:
Nougat based ROMs
OOS stock
OOS based ROMs
H2OS
MIUI
FlyME
Okay so @Tomsgt has made an amazing guide on how to set up and run MultiROM for our device (or any device), you can find his video right here:
<Mod Edit: Link removed for promoting paid service.>
Awesome work
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
martinusbe said:
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
Click to expand...
Click to collapse
Fixed!
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
[email protected] said:
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
Click to expand...
Click to collapse
Probably because of the ROM. It might need more tags since we can't agree on ONE name
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
Its working fine now...awesome work... :good:
Great man, thanks a lot.
Sent from my ONE A2003 using XDA-Developers Legacy app
MZO said:
Fixed!
Click to expand...
Click to collapse
cool, thanks for keeping authorship btw
martinusbe said:
cool, thanks for keeping authorship btw
Click to expand...
Click to collapse
My pleasure used your commits and you helped me in the final stage — well deserved!
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
martinusbe said:
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
Click to expand...
Click to collapse
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
MZO said:
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
Click to expand...
Click to collapse
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
martinusbe said:
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
Click to expand...
Click to collapse
Yep it worked with commas. Uploading now two more names: Oneplus2 (pretty common), onePlus2 (what was I thinking??)
Will i need to wipe internel storage for first time
ShaDow18 said:
Will i need to wipe internel storage for first time
Click to expand...
Click to collapse
No you won't.
MZO said:
No you won't.
Click to expand...
Click to collapse
What about recovery do i really need fastboot mode or flasify can also do
Team Win Recovery Project 3.1.1
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.
{
"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"
}
#include <std_disclaimer.h>
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, European Union for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
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.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
Download:
Galaxy S8 (dreamlte - Exynos vaiants - G950F/FD/N/X)
https://twrp.me/devices/samsunggalaxys8.html
Galaxy S8+ (dream2lte - Exynos variants - G955F/FD/X/N)
https://twrp.me/devices/samsunggalaxys8plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - General Discussion
Join to get quick support (when you find my guide confusing or meet any unexpected problem).
You can also discuss about ROMs(this group is "neutral" so you can discuss about or review any ROM. Note: Devs: Do NOT aggressively advertise your work.), get latest updates from developers or report possible bugs.
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
XDA:DevDB Information
TWRP for Galaxy S8 and S8+, Tool/Utility for the Samsung Galaxy S8
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2017-04-24
Last Updated 2018-07-22
Changelog:
Aug. 02:
Merged AQG kernel updates from Samsung.
NOTE: AQG or later bootloader is supported and REQUIRED from this version.
May. 30:
Possible fix for I/O problems.
Backported latest F2FS from Linux 4.12.
Minor kernel updates.
Apr. 27:
Problems Solved:
1. MTP
2. ADB
3. External SD Mount
Features Added:
F2FS - Note: This change ONLY makes it possible to operate F2FS in TWRP. You still need a F2FS-compatible KERNEL to boot into system with F2FS.
Note: As MTP and ADB are available now, flashable zips will no longer be included. Please download them by yourself and transfer them from your computer to phone if you need them.
Useful Links:
Disable dm-verity and make encryption optional: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk: https://forum.xda-developers.com/apps/magisk
Apr. 24:
Initial Release
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.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- 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.
Awesome
Great work thank you very much
Sent from my SM-G955F using Tapatalk
if i wipe data partition in order to disable encryption - is that like erasing my phone and starting from scratch? will i lose all my data?
nk33 said:
if i wipe data partition in order to disable encryption - is that like erasing my phone and starting from scratch? will i lose all my data?
Click to expand...
Click to collapse
Yes you will, make sure you've backed-up as much as you can to your Google Cloud Storage. I promise, it's worth it.
Many Thanks
Kevin_R said:
Yes you will, make sure you've backed-up as much as you can to your Google Cloud Storage. I promise, it's worth it.
Click to expand...
Click to collapse
Thanks.
And if i just install TWRP, and then the root zip file to give me root will it all work ok? will i achieve root ok?
I spent ages getting this phone just like i want it and seriously cant be bothered to do it all again - will i be ok keeping encryption on if all i want to achieve is root?
what will i lose out on if i dont disable encryption?
nk33 said:
Thanks.
And if i just install TWRP, and then the root zip file to give me root will it all work ok? will i achieve root ok?
I spent ages getting this phone just like i want it and seriously cant be bothered to do it all again - will i be ok keeping encryption on if all i want to achieve is root?
what will i lose out on if i dont disable encryption?
Click to expand...
Click to collapse
I found that if I didn't disable the encryption, root wouldn't work as it couldn't mount the file system to make the relevant changes
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
Anyone managed to get Samsung Pass and Secure Folder working? I have Magisk Hide running and Knox Trip is emulated to 0x0. Other apps that would normally detect root don't detect it but Samsung Pass and Secure Folder still can.
Is superSU SR3 working??
its a great work
anyone tried if Samsung Pay still works after this? I have not got my phone yet.
Just for info tried installing the SuperSU binary through TWRP but, as TWRP seems to have no access to the SD card, the flash failed and left me in a boot loop.
Reinstalling TWRP from Odin and reflashing Magisk solved the Boot loop issue.
SuperSU did kill the Knox processes for me though to stop the annoying nagging notifications.
If after flashing from Odin, phone says that needs restore, Just press volume up Bixby Power, wait, then format data, Power off. Now ho back in download mode, reflash with odin, done.
It works all', except personal area and Samsung health
would this work on the SM-G950FD?
if i use this method i lose warranty ? is it possible to do evrything later on normal without having any trouble ?
Phone brick...LOL...
help : just tried to root my g950f Uk 02 - i've flashed it a few times and used the two flash but im getting verification failed and it wont erase anymore when i try use the recovery flash i get invaled mount /data when using that decrypt .zip in flashables do i need to redo the stock firmware and start again?
i am still waiting for my S8(exynos) to arrive and here comes the twrp i did not even wished yet....
Team Win Recovery Project 3.1.1
Snapdragon ONLY.
In NO way it is compatible with Exynos variants including but not limited to International (F/FD), Korean (N), Exynos LDU (X) variants.
Note that this does NOT unlock your phone. You need to have an unlockable variant such as Chinese or HK to flash.
{
"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"
}
#include <std_disclaimer.h>
Special Notes:
1. DON'T FORGET TO TURN OFF REACTIVATION (Samsung Account) LOCK.
2. UNLOCK BL BEFORE FLASH.
3. KNOX will be tripped once you flashed custom binaries to your phone. (Your warranty WILL be voided.)
4. Samsung Pay, Samsung Firmware OTA (System Updates), Secure Folder and other features that require high-level security will NO LONGER once you flashed custom binaries. (You can flash custom ROMs to keep OS up to date.)
Download:
Galaxy S8 (dreamqlte - Snapdragon vaiants)
https://twrp.me/samsung/samsunggalaxys8qcom.html
Galaxy S8+ (dream2qlte - Snapdragon variants)
https://twrp.me/samsung/samsunggalaxys8plusqcom.html
Sources:
https://github.com/jesec
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - General Discussion
Join to get quick support (when you find my guide confusing or meet any unexpected problem).
You can also discuss about ROMs(this group is "neutral" so you can discuss about or review any ROM. Note: Devs: Do NOT aggressively advertise your work.), get latest updates from developers or report possible bugs.
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
XDA:DevDB Information
TWRP for Galaxy S8 and S8+ (Snapdragon), Tool/Utility for the Samsung Galaxy S8
Contributors
jesec
Source Code: https://github.com/jesec
Version Information
Status: Stable
Created 2017-07-14
Last Updated 2018-06-20
Changelog:
July 25:
1. More additional security functions implemented by Samsung have been disabled. (those functions may lead to potential I/O issues)
2. A fatal mistake that leads to incompatibility with plus variant has been fixed.
July 15:
Initial Release
Guides:
Notice: It may wipe all your data including those in internal storage.
Pre - HOW-TO PREPARE FOR FLASH: (Chinese/HK variants)
SPECIAL NOTE: These variants do NOT have "OEM Unlock" option and you don't need to enable it. Only reactivation (Samsung Account) lock needs to be disabled.
1. On your phone, open Settings, go to "Cloud and Accounts" -> "Accounts".
2. Select your Samsung account, open menu, remove account. (That will make sure reactivation lock is disabled. Alternatively you can disable reactivation lock without delete your Samsung account. Result should be same. )
3. Download, install and run official unlock tool, CROM service.
4. Your phone is unlocked and ready to flash TWRP at this stage. Now you can proceed to part 1.
Part 1 - HOW-TO FLASH TWRP:
1. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
2. Download and extract Odin (Samsung's Flash Tool) to your computer.
3. Download a .tar image of TWRP.
4. 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.
5. Open Odin and place that TWRP tar file in the [AP] slot.
6. Connect your phone.
7. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
8. 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.
AT THIS STEP YOU CAN DIRECTLY GO TO PART 3 OF THIS GUIDE IF YOU WANT TO ROOT.
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.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- 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, Kernels via TWRP.
Part 3 - HOW-TO ROOT:
Note: Additional security layers implemented by Samsung make it impossible to get root access with a modified stock kernel. Thus, a custom kernel with security features disabled is MANDATORY.
1. Download a custom kernel with security features disabled.
- Reference: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-s8-t3637640
1. Download the root package.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zips to your phone.
3. Flash the kernel.
4. Flash the root package.
how does this even work?
unitz0mbie said:
how does this even work?
Click to expand...
Click to collapse
You never heard about Jesec, the mighty one?
diazepambr said:
You never heard about Jesec, the mighty one?
Click to expand...
Click to collapse
i have seen the name before but never realized the power of a God among earth
Jesse is like the Matrix he only see's code format :laugh:
Amazing work!
Is this legitimate?
Anyone tried flashing it yet? Will it work without an unlocked bootloader?
I thought bootloader was locked?
Sent from my SM-G955U using Tapatalk
GHolbrook4 said:
Anyone tried flashing it yet? Will it work without an unlocked bootloader?
Click to expand...
Click to collapse
Prob not, I figured I would try anyway just to be 100% Certain does not flash through Odin and Fastboot OFC Doesnt ever connect to device since locked bootloader... Pretty sure it was uploaded for once the SD Version has Bootloader access
---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ----------
lilrich17892 said:
I thought bootloader was locked?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
It is
It's for the version with snapdragon and boot loader unlocked, i.e. China.
NeedleGames said:
It's for the version with snapdragon and boot loader unlocked, i.e. China.
Click to expand...
Click to collapse
China has SD?!?! Thought it was Exynos
GHolbrook4 said:
Anyone tried flashing it yet? Will it work without an unlocked bootloader?
Click to expand...
Click to collapse
Nope. SW REV CHECK FAIL : [recovery] Fused 1 > Binary 0 is the error on locked Bootloader
Does audio mods work for you guys?
Does this mean that it works with S8s on T-Mobile?
explorer-10 said:
Does this mean that it works with S8s on T-Mobile?
Click to expand...
Click to collapse
No, only for the Chinese Snapdragon phones. You can't root a s8 in the US because no one s figured out how to unlock the bootloader yet.
GHolbrook4 said:
No, only for the Chinese Snapdragon phones. You can't root a s8 in the US because no one s figured out how to unlock the bootloader yet.
Click to expand...
Click to collapse
well, damn. i wish it would say that in the headline on my Google feed instead of getting my hopes up. its like almost getting me there and then stopping right before i can finish on her face
NeedleGames said:
It's for the version with snapdragon and boot loader unlocked, i.e. China.
Click to expand...
Click to collapse
Also lock in China.
Team Win Recovery Project 3.1.1
{
"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"
}
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
Changelog:
Sep.21
Removed Mouse cursor. thx alot to @Tkkg1994 that joined now us too on n8
Added F2FS Support
Sep.17
Fixed MTP
Fixed ADB
Sep. 16:
Initial Release
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.
Omg I'm gonna die happy lol. Let me go and root now.
Sent from my SM-N950N using XDA-Developers Legacy app
Good work keep it up
This is great. Many thanks
Great job and many thanks for your efforts!
Do I get this right?
When I'm in download mode, I have to hold the 3 buttons again and press start in odin ?
Doesn't that interrupt the flash process ?
Pinu'u said:
Do I get this right?
When I'm in download mode, I have to hold the 3 buttons again and press start in odin ?
Doesn't that interrupt the flash process ?
Click to expand...
Click to collapse
No go To Download Mode in The smartphone and Then .via Odin Select AP and The Recovery IMG Then Flash ans Phone Reboot automaticly
Oh yeah baby
Thanks time to de bloats and install my favorite apps
Sent from my SM-N950N using XDA-Developers Legacy app
Thanks a lot TWRP up and rocking. Great work !!
Edit : Can confirm that SuperSU v2.82 is working also !!
Anybody know if this will also work with N950F/DS model? Thanks.
xpdragon said:
Anybody know if this will also work with N950F/DS model? Thanks.
Click to expand...
Click to collapse
Works since i have it byself is the dual sim one right? when yes is same modell as mine
Mine don't have oem unlock options in developers mode. Need to wait for sw update or other opinion. ??
Sent from my SM-N950F using Tapatalk
geiti94 said:
Works since i have it byself is the dual sim one right? when yes is same modell as mine
Click to expand...
Click to collapse
Yes, it is dual sim model. Thanks for the reply.
your fantastic!!! one day without root and twrp!! im so happy now ^^. now i can continue with modding on my new great phone.
Finish work and lets go home flashing
Was just about to port it by myself and then I saw Your thread . Great Job Geiti! Guess I will take care of building AOSP for N950F then .
pswin09 said:
Mine don't have oem unlock options in developers mode. Need to wait for sw update or other opinion.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
There's no guarantee a software update will ever unlock your bootloader if the OEM Unlock option is not available for you. I would suggest selling it and buying a new one that does have the option. If you really want to root or install custom ROMs, why take the risk when you spent $1000 on this phone for a specific purpose?
If you just bought your phone, it must still be brand new and in pristine condition. You should sell it for almost full price. The demand is really high right now so you'll have no problems selling it fast.
pswin09 said:
Mine don't have oem unlock options in developers mode. Need to wait for sw update or other opinion.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
can be your carrier blocked the oem unlock. download a debranded firmware like the one with AUT or DBT csc and flash it with odin and look if you have then the menu. But flash it only when you have a N950F or a N950F/DS
Has anyone tested Android Pay after doing this?