Hiya
looked for other ROM options and most here in XDA seem no longer supported.
Settled on crDroid android 10. one zip files generated TWRP error 7, the other generated a corrupt zip file error.
I cant find any android 9 ROMS....
[RECOVERY][OFFICIAL] TWRP for Galaxy S9 and S9+ (Exynos)
- Thread starter jesec
- Start date
looked for other ROM options and most here in XDA seem no longer supported.
Settled on crDroid android 10. one zip files generated TWRP error 7, the other generated a corrupt zip file error.
I cant find any android 9 ROMS....
Hello everyone!
I'm having a pretty bad time trying to get TWRP installed on my S9+.
First of all:
- My device is a G9650 (Exynos)
- OEM bootloader is unlocked
- Coming from up-to-date stock firmware
- Never flashed anything on this device (I do have experience tho, I was a flash-a-holic back in the day with my S7e and the legendary S2)
- I'm installing TWRP to use it with LOS 17.1
- TWRP version I tried is 3.5.2
I followed every step of this guide's part 1. My problem is, I just can't boot into TWRP.
The steps I did:
1. Logged out every account and factory reset on Stock Rom
2. After reset, unlocked OEM bootloader
3. During the reboot of the OEM unlock reset, booted into odin mode
4. Flashed TWRP while holding [Power]+[Bixby]+[Vol up]
5. Stuck on the following screen
It reads:
[press(?)] any key to shutdown
Set Warranty Bit: Recovery
I have no idea what is written below the triangle...
6. If I shutdown the phone and try to get the recovery, I get to the same screen as above.
7. If I let the phone boot, I get to the Stock Rom and can use it just fine but it'll overwrite TWRP with the stock recovery.
8. Reflashing TWRP get me stuck in the same screen as above.
Well... Did I do something wrong? Anyone know how can I boot into TWRP in this case?
I'm having a pretty bad time trying to get TWRP installed on my S9+.
First of all:
- My device is a G9650 (Exynos)
- OEM bootloader is unlocked
- Coming from up-to-date stock firmware
- Never flashed anything on this device (I do have experience tho, I was a flash-a-holic back in the day with my S7e and the legendary S2)
- I'm installing TWRP to use it with LOS 17.1
- TWRP version I tried is 3.5.2
I followed every step of this guide's part 1. My problem is, I just can't boot into TWRP.
The steps I did:
1. Logged out every account and factory reset on Stock Rom
2. After reset, unlocked OEM bootloader
3. During the reboot of the OEM unlock reset, booted into odin mode
4. Flashed TWRP while holding [Power]+[Bixby]+[Vol up]
5. Stuck on the following screen
It reads:
[press(?)] any key to shutdown
Set Warranty Bit: Recovery
I have no idea what is written below the triangle...
7. If I let the phone boot, I get to the Stock Rom and can use it just fine but it'll overwrite TWRP with the stock recovery.
8. Reflashing TWRP get me stuck in the same screen as above.
Well... Did I do something wrong? Anyone know how can I boot into TWRP in this case?
im not really much help here, although i did translate the chinese red writing for you, it's just a software warning, it reads:
"This phone is not running the software officially released by Samsung. There may be a problem with the function and security of the phone, and you cannot install software updates."
the steps i took to flash twrp on my s9 g960f:
1. unlock bootloader/OEM unlock
2. boot to download mode
3. flash twrp using odin (turn off auto reboot)
4. boot to recovery using power, bixby and volume down, when the screen goes black hold volume up instead of volume down.
let me know if this helps
Thanks a lot but my problem was with the piece between the chair and the keyboard. (
Just to clarify, everything I did was correct except identifying my device model. I have the G9650 which is the International Snapdragon variant instead of Exynos as I previously thought. Binaries are not interchangeable between these two SoCs.
I just wonder why my system booted besides having an incompatible recovery flashed...
Anyway, as soon as I flashed the correct binary, it worked as expected on the first try.
Lesson to newcomers: triple-check your device model before flashing anything. I was damn lucky I didn't brick my phone.
AFAIK don't use TWRP 3.5.x if you plan to use Android 10 (compatibility broken with this version).
Use only TWRP 3.3.1.1 to avoid problems (maybe 3.4.0 will do the job too).
Use only TWRP 3.3.1.1 to avoid problems (maybe 3.4.0 will do the job too).
it's unreleased, and still in development. you can speak to @Baddar90 on telegram, if you ask him kindly, and agree to report bugs, he might give you a copy
TWRP 3.4.0 Definitely works with Android 10.
I'm running a G965F DS with TWRP 3.4.0 RR8.x (Android Q) and Magisk 23.0. All Fine.
Had a lot of problems having TWRP 3.5.x installed. Downgraded to 3.4.0 and all was fine.
Since device trees are forked on 3.5.x and later and there is no actual device tree for Android 10 (just for Adroid 9) it is not recommended to use TWRP later than 3.4.0 (last version before the fork).
I think this is also recomended for other recoverys based on twrp, but it depends on the devs of these recoverys,
i have a question, when wanting to enable OEM unlock, it asked me to factory reset.
this guide mentioned, don't let it complete the whole reset process.
but how exactly? it doesn't tell what will happen on phone screen if we agreed to factory reset, and when exactly to reboot the device to download mode (step7).
so right now i haven't enabled OEM unlock, need a help. thanks
solved, i overlooked this "be prepared to use reboots as chances to flash or reboot into TWRP."
now can flash TWRP 3.4.0.0 (don't use latest TWRP if you're on latest firmware, flashing dm verity will fail), and already flashed magisk 23.
setting up the phone now...
any recommended kernel to use for stock rom?
Last edited:
I'm trying to put an current LOS on my S9. I've already used heimdall to put TWRP 3.5.2.9 on the Phone.
Sadly, TWRP always asks for a password to decrypt the data partition. I don't remember putting in a password. Can I format the partition somehow to get rid of the password?
Thank you
Sadly, TWRP always asks for a password to decrypt the data partition. I don't remember putting in a password. Can I format the partition somehow to get rid of the password?
Thank you
How can I install TWRP for starqltecs (SM-G960W)? Can any of you guys build a TWRP version for starqltecs?
EDIT: no error with twrp 3.5
i get a error message by flashing the dm-verity and force encryption disabler:
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/no-verity-opt-encrypt-samsung-1.0.zip'
Updating partition details...
...done
ive testet 2 roms, no works
i get a error message by flashing the dm-verity and force encryption disabler:
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/no-verity-opt-encrypt-samsung-1.0.zip'
Updating partition details...
...done
ive testet 2 roms, no works
Last edited:
Hello Guys, I installed TWRP. Once i install no-verity zip, I unable to setup fingerprint and my lockscreen pin also behaves weird ? Is the no-verity zip required ?
Can we use the latest magisk ?insert image
Multi_Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip is special for S9+ G965F ? I can also use it for G960F ? has anyone tried / works ? thx
I'm solved ,
pretty good video tutorial
but I didn't use it file bay user video produced I used no-verity-opt-encrypt-6.1 bay Corsicanu file for my fone G960F.
I have the G960F with Android 9 rooted with Magisk 25.1 and G960FXXS7CTA1 and TWRP 3.3.1-1. What is the best version of TWRP to use on this phone? I have tried using the backup in TWRP to my SD card but it keeps stopping and I get a failed error. The SD card is 256Gigs and has almost nothing on it so it has plenty of room.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
103Team Win Recovery Project
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
#include <std_disclaimer.h>
Special Notes:
1. READ THE GUIDE.
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.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy S9:
https://twrp.me/samsung/samsunggalaxys9.html
Galaxy S9+:
https://twrp.me/samsung/samsunggalaxys9plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - Discussion, Testing, Feedback and Support
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
To contribute:
TWRP Code Review
Github pull requests will be ignored.
XDA:DevDB Information
TWRP for Galaxy S9 and S9+, Tool/Utility for the Samsung Galaxy S9+
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2018-03-15
Last Updated 2018-08-1559Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Since Android O, Samsung introduced a new security feature, Remote Mobile Manager (RMM) aka Remote Lock Control (RLC). This feature allows stronger theft protection but unfortunately it also imposes a burden on users like you.
Samsung added a 7-day buffer period for enterprises or device owners to spot a missing/rogue device so they can use this feature to lock the device remotely.
In this 7-day (Prenormal) period, you can NOT flash any custom binaries including but not limited to this TWRP. OEM Unlock option won't appear, either.
(You will meet "custom binary blocked due to remaining installment balance" or "custom binary not allowed" error when you try)
The 7-day timer will start/reset once you completed the setup wizard. After 7 days (168 hours), RLC service will send an inquiry to Samsung's server. If your device is "clean", the RMM state will become "Normal".
Then you can enable "OEM Unlock" option and flash TWRP. Be careful, DO NOT reboot to a stock ROM before you flash patch in part 2 of this guide or you will have to go through another
Whether you have RMM problem or not depends on your model, region and/or carrier.
If you don't have any wait period to enable OEM Unlock option, congratulations but please do NOT mislead other people.
NOT EVERYONE IS AS LUCKY AS YOU.
If you don't have RMM problem when you get the device, it is unlikely that you will get any RMM problems later.
But note that this problem applies to MAJORITY of people.
Note that the special patch will freeze RMM, FRP and OEM lock state.
This is an anti-stupid measure to prevent careless users from enabling security measures which are not compatible with custom binaries.
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, remove all Samsung and Google accounts and if your device is registered to an enterprise, de-register it.
3. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
NOTE: You will be asked to do a factory reset, that's normal.
BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS.
You should take a look at the whole guide and be prepared to use reboots as chances to flash or reboot into TWRP.
4. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
5. Download and extract Odin (Samsung's Flash Tool) to your computer.
6. Download a .tar image of TWRP.
7. 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.
8. Open Odin and place that TWRP tar file in the [AP] slot.
9. Connect your phone.
10. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
11. 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:
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".
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 special 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 may want to flash a root solution (Magisk, SuperSU, etc) or custom ROM but keep in mind that:
1. This thread does NOT provide technical support to any root solution or ROM unless the problem is DIRECTLY related to TWRP and there is no other solution without modifying TWRP itself.
Please contact developer of respective ROM or root solution for technical support.
2. Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection". https://www.samsungknox.com/en/blog/real-time-kernel-protection-rkp
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.31Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Apr 18, 2018 (twrp-3.2.1-2):
Refactor USB configurations (fixes ADB)
Remove /cpefs from filesystem table (fixes /cpefs warning/error)
Rebase Kernel to ARCC. (fixes I/O performance issues)
Use correct OTG mount path
Enable software encryption support (general AOSP only, Samsung method remain unsupported)
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
USB connection fixes
Mar 14, 2018:
Initial version11Changelog - Apr 18, 2018 (twrp-3.2.1-2):
Refactor USB configurations (fixes ADB)
Remove /cpefs from filesystem table (fixes /cpefs warning/error)
Rebase Kernel to ARCC. (fixes I/O performance issues)
Use correct OTG mount path
Enable software encryption support (general AOSP only, Samsung method remain unsupported)
I recommend everyone to update to this build.
Note that for some reasons starlte (G960*) build does not show up on twrp website yet.
Please download the build via this link: http://build.twrp.me/twrp-3.2.1-2-starlte.img.tar6
Please check the new RMM state section of the guide.
It is normal for Samsung to force a reset when you toggle OEM Unlock option.
BUT DO NOT BE TRICKED. You SHOULD NOT complete the whole reset process. (reset, let it reboot, BOOM RMM Prenormal is back and you are in 7-day jail again)
Every reboot is a chance to flash TWRP or boot into TWRP. DO NOT ALLOW your device to boot into system before you boot into TWRP and flash the patch.
(Use "VOL-DOWN" + "POWER" + "BIXBY" to boot into download mode, "VOL-UP" + "POWER" + "BIXBY" to boot into TWRP, "VOL-DOWN" + "POWER" to force a reboot)
Then follow the guide.
There are two scenarios:
1. The device is registered to an enterprise, thus regulated by the policy of that enterprise.
2. The device is not supposed to be used by you. (demo device or stolen device)
Either way, I can't help you with this problem. Please contact your seller or company for assistance.
Yes you can. N has the almost same hardware as F. You should be able to flash any custom ROMs, Kernels, root solutions, etc branded for F on a N device.
But keep in mind that you still need to use N specific modem/baseband and bootloader so you can't flash stock ROM of F on N.
No, encryption is not supported and there is no plan to support it.
Samsung use proprietary hardware disk encryption methods. There is no way to support that without proper sources.
No. TWRP is not something that needs to be updated regularly. A thread title with recent dates may look great now but soon it will look like outdated as f*.
TWRP is meant to be stable not "updated Apr 12 with EXCITING XXX".
I don't have plan to support Snapdragon variant at this moment.
