Team 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>
{
"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"
}
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-15
Changelog:
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 version
Guides:
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.
Awesome work Jesse. Thank you!
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
@jesec hey mate, happy to see you again (S7 ROM)
Sorry i don't have this device but my friend will try soon
spackeddie01 said:
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
Click to expand...
Click to collapse
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset.
Click to expand...
Click to collapse
Please boot to recovery instead of system.
Be aware that Android Verified Boot requires data 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 such prompt.
Got twrp installed formatted data, rebooted twrp, do we need Dm-Verity? If so how to get it on as MTP is not working, or OTG, and system bootloop so can't get back in to do it that way.
BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
Click to expand...
Click to collapse
You have to flash dm-verity/magisk.
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
iamnotkurtcobain said:
Awesome work Jesse. Thank you!
Click to expand...
Click to collapse
Dis you try treble AOSP ?
giorgior.r said:
Dis you try treble AOSP ?
Click to expand...
Click to collapse
I can't. This TWRP is for 9+. I have a normal S9.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
BokkieAndijk said:
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
Click to expand...
Click to collapse
You formated system it seems.
Steps are:
-flashing TWRP
-boot into TWRP
-format Data
-reboot recovery
-install magisk
-reboot
iamnotkurtcobain said:
You have to flash dm-verity/magisk.
Click to expand...
Click to collapse
pls can you give me a link to the packages you have used?
Thanks.:good:
Nice to see you doing work on the S9 @jesc
deleted
@jesc good to see you in the s9 forums. Great work as usual
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
BokkieAndijk said:
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
Click to expand...
Click to collapse
check in this site
https://www.sammobile.com/firmwares/database/SM-G965F/
Flashed twrp then flashed no dm verity - seemed to flash ok - but saw one error message that says "failed to mount '/cpefs' - I haven't seen that error before but thought it might be important. THis message happens after the flash has finished -(after it says updating partician details)
Tried to flash magisk after I flashed twrp and phone bootloops had to flash stock in odin
Related
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/hero2qlte/twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
travis82 said:
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
Click to expand...
Click to collapse
It doesn't matter, dm-verity isn't enabled in the fstab, nor does the TWRP image contain any verity signatures to enforce.
finally...
thank god!finally!but the front cam issue have been solved?
Anyone know what roms work with this device? Also how to return to stock?
When compression is enabled on backups the device freezes.
What happened to CROM Service? It's not in the Galaxy Apps and .apk's from mirror websites crash when opened.
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
ryan49er said:
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
Click to expand...
Click to collapse
this recovery is for unlocked bootloaders only. IE chinese and hong kong models only.
Well that sucks
Report...
jcadduono said:
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
Click to expand...
Click to collapse
I had G9350ZCU2APK2 ROM (China), so I installed the Hong Kong ROM G9350ZHU2APK2 (I needed the google services) and the phone work great except the part of receiving or sending SMS's, I have two sim cards cards (China Telecom and China Mobile), if I sent a message from the CT the message was sent also from CM, if I send from CM is not working, when I receive messages I received on both sim cards... , big problem for me, so, I installed the last G9350ZCU2APL3 ROM (China) and is working ok but no google services...
I've tried your method and is working... (kind of) once I installed the TWRP and the last SuperSU the phone had no Wifi and no network signal, so I put back the original firmware...
All I need are the google services because Signal is not working without, the email client is not receiving the email (automatically) without and so on... I've tried all the "possible" ways, no luck...google installer v2 and so on...
Any ideas on how to put the google services?
----- Edit - 28 January 2017 ----
I reinstalled the TWRP provided in the first post and the phone is working, has signal (China Telecom and China Mobile) and also the WIFI is working, I didn't install the SuperSU, kind of weird, with SuperSu installed the phone has no WIFI and no signal...
I've tried to install the gapps pico and the TWRP is saying that "could not mount/data and unable to find crypto folder", "Failed to mount '/data' (invalid argument)", "Unable to recreate /data/media folder", "failed to mount '/data' (Invalid argument)", "Unable to mount storage" , "Unable to mount / data/media/TWRP/. twrps.
The last error is: "Failed to mount'/data' (invalid argument)
After reading more posts on the forum I found the following:
"You CANNOT mount an encrypted partition in TWRP.
You do NOT wipe the partition.
Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button."
Probably I will try this method when I am in the mood...
This works for SM-G935P? It says manufactured in china on the back.
Salanrm said:
This works for SM-G935P? It says manufactured in china on the back.
Click to expand...
Click to collapse
The post is for the Qualcomm, Galaxy S7 Edge SM-9350, China Open and Hong Kong, same hardware, different software (the Chinese one has no google services).
For your phone SM-G935P, search on google and you will find more instructions, I don't know if I am allowed to post here links from other websites.
jcadduono said:
As a joke, here you go USA!
twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
good afternoon
Reference is unfortunately not working
Can somebody share twrp-3.0.2-0-hero2qlte.tar.md5
thank you in advance for your response
So, this will 100% NOT work for the g935A? (Att s7 edge)
Craz Basics said:
So, this will 100% NOT work for the g935A? (Att s7 edge)
Click to expand...
Click to collapse
No. Locked bootloader
Sent from my SM-G935T using Tapatalk
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Craz Basics said:
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Click to expand...
Click to collapse
It's a serious long shot but it is slowly being worked on.. check out this thread. It's for t mobile but the solution if found will apply to all us carriers as we all use the same method to root on marshmallow.
https://forum.xda-developers.com/showthread.php?t=3544220
Sent from my SM-G935T using Tapatalk
UPDATE OF JULY, 13th 2019 : IMPORTANT INFO : This guide is no longer updated. The recent update of June 2019 broke compatibility with my Bootloader Ver. 2 I was using which worked fine from the first Nougat release to the first Pie update (included). As I'm still daily running Android Nougat (7.0), I can't risk to upgrade to BL Ver. 5 and find myself locked under Pie. And the main risk is that I can't know if BL v5 is breaking modem compatibility or not and if it does it means that I'll lose all wireless connectivity under Nougat. So, as I can't risk my device (which is my daily) I have no choice other than dropping the support of this device. I apologize.
SAMSUNG Galaxy Note Fan Edition
Exynos 8890 - International Ver. [SM-N935F/DS]
{
"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"
}
Current Status :
(Pie 9.0) - POST 06/21/2019 Update - Unknown
(Pie 9.0) - PRE 06/21/2019 Update - Rootable
(Oreo 8.0) - Rootable
(Nougat 7.0) - Rootable
Latest Ver. of TWRP: v3.3.1-0
Latest Ver. of Android: Pie (Android 9.0)
1 - ▼ DISCLAIMER ▼
- I DECLINE TOTAL RESPONSIBILITY IF YOU DAMAGE OR BRICK YOUR PHONE WHILE TRYING THIS METHOD ! YOU'RE DOING IT AT YOUR OWN RISKS !
- THIS METHOD IS ONLY VALID FOR THE GALAXY NOTE FAN EDITION (EXYNOS Ver.) SM-N935F/DS VERSION ! IT'S NOT SUITABLE FOR THE KOREAN VARIANTS !
- FLASHING ANY CUSTOM BINARY WILL IRREMEDIABLY VOID YOUR WARRANTY AND KNOX COUNTER WILL BE TRIGGERED (0x1).
- MAKE SURE THAT YOUR DEVICE HAS AT LEAST 70% BATTERY BEFORE ATTEMPTING ANY STEPS !
- ALL THE DATA ON THE INTERNAL STORAGE WILL BE DELETED ! BACKUP ALL YOUR FILES IN A SAFE PLACE BEFORE PROCEEDING !
2 - ▼ Important Infos ▼
To avoid making any mistakes, I HIGHLY recommend you to READ CAREFULLY the WHOLE guide BEFORE attempting anything! Prevention is better than cure remember
The Galaxy Note FE (like many other Samsung devices) use dm-verity and data partition encryption.
► Android 9.0 (Pie) - UPDATE OF THE 06/21/2019 (Bootloader V5) :
The Note FE (International Ver.) Android Pie update of (June 2019) support is unknown.
As I can't try if my patch works, (see above), I can't test if the latest update is rootable or not.
However, the problem is probably similiar to the first Pie release of March 2019, the fix is also probably the same
but due to changes to the kernel or boot routines, the old fix dosen't work anymore.
If you're under an older Pie release (typically with a v4 BL or less) or even under an other Android version, you can still follow this guide.
► About RMM State :
The Note FE (International Ver.) is shipped with a component called "RMM".
This component is able to prevent the end-user from flashing any custom binary on the device while it's active.
You can check if your RMM is enabled or disabled by putting your device in Download Mode :
- If the line "RMM State: Prenormal" is present, then RMM is enabled and you won't be able to flash any custom binary.
- If it's absent, then it has already been disabled which means that you'll be able to flash any custom binary.
This component suddenly disable itself after 7 days of continuous uptime since the device has been last powered on.
You can check your device actual uptime by going into : "Settings" > "About phone" > "Status" > "Uptime"
Or use CPU-Z : "System" tab and "System Uptime". (CPU-Z displays the uptime in days rather than hours.)
Once 7 days are elapsed, it will be desactivated BUT! If you format the data partition for example, which's required to disable data encryption for rooting, it will be back!
Even worse, if you reboot once you've setup your phone, you'll get blocked with a message when you'll powering it on saying ("custom binary has been block due to remaining installment balance") and you'll have to reflash stock to get your device working again...
To avoid that, once the /data partition has been wiped, you'll need to apply the RMM fix (prerequisites section, see below) which prevents the device from re-self-locking itself after rebooting, once the initial setup has been completed.
Everytime you install a new official firmware, RMM might be active again.
It is triggered by an hidden system app called "Rlc" which acts on the bootloader lock.
If your Rlc app is still present, the best thing to do is to simply delete it ASAP to prevent any unpredictable action on your bootloader. (system/priv-app/Rlc)
For custom ROMs, normally they're safe. But still, check if the dev has already deleted Rlc, otherwise you'll have to do it by yourself.
3 - ▼ Prerequisites ▼
1 - A SAMSUNG Galaxy Note FE [SM-N935F/DS]
2 - The Samsung USB Drivers (If not already installed, => [HERE] <= )
3 - Download the lastest Odin (v3.13.1) => [HERE] <=
4 - Download TWRP for the Galaxy Note7 [SM-N930F] (v3.2.1-0.img.tar) => [HERE] <=
5 - For Android Nougat (7.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Click to expand...
Click to collapse
5 - For Android Oreo (8.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Download the /data partition fix (for Android Oreo) [HERE]
Click to expand...
Click to collapse
5 - For Android Pie (9.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Download the Kernel Patch (for Android Pie) [HERE]
Click to expand...
Click to collapse
6 - A PC and a USB-C Cable
7 - A brain, a pair of eyeballs and some fingers (Yeah, that could help... especially the first one..)
4 - ▼ Flashing TWRP 3.2.1-0 on the Galaxy Note FE ▼
If Your RMM is locked you will have to wait 7 days (or 168 hours) while maintaining your device up and running. (NEVER REBOOT DURING THIS TIME ! IT WILL RESET THE RMM TIME COUNTER!)
=> For more info and/or if you don't understand what I'm talking about, please refer to section 2 of this page and read it all.
Once RMM is desactivated (or already desactivated), you can proceed to the next steps :
Make sure to enable "USB Debugging" and "OEM Unlock" in the Dev Options.
Connect your phone to your PC and drag and drop the Magisk package and the RMM fix at the root of your microSD card.
Now, depending on the Android version you're running, drag and drop the additional fix that you've downloaded earlier at the root of your mSD card too. (Only if you're on Oreo or Pie)
Once it's done, backup everything valuable and power off your device.
Enter the Download Mode by pressing simultaneously the "Home" + "Vol. Down" + "Power" buttons for 5 sec. Read the warning message and just answer "Continue".
Launch Odin and select TWRP 3.2.1-0 archive by clicking on the "AP" button.
Go to the "Options" tab and untick "Auto-reboot"
Connect your phone which is in DL Mode to your PC.
/IMPORTANT!\ Make sure Odin is seeing your device properly.
(Once connected, you should see the box under the "ID:COM" tab displaying "0:[COM*]" in blue, meaning your phone has been detected successfully. If not, Install the Samsung USB Drivers, link available in the prerequisites section.)
Flash TWRP.
Wait while Odin in flashing the recovery. /AVOID TOUCHING ANYTHING DURING FLASH PROCESS\
When Odin shows "PASS", take your device in hands, disconnect the USB-C cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the DL mode disappears.
When at the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to enter TWRP recovery.
You should see TWRP logo just after the Note FE splash-screen.
Click to expand...
Click to collapse
Now TWRP is successfully installed. But we're not done yet ! We still have to deal with the data encryption and disable dm-verity in order to boot properly.
5 - ▼ [9.0] Rooting the Galaxy Note FE under Android Pie ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed.
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and Install the RMM fix package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the kernel patch for Android Pie.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the Magisk package, the root solution.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
6 - ▼ [8.0] Rooting the Galaxy Note FE under Android Oreo ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed.
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and install Magisk package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the RMM fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the /data partition fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
7 - ▼ [7.0] Rooting the Galaxy Note FE under Android Nougat ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed !
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and install Magisk package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the RMM fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
8 - ▼ Disable SecurityLogAgent pop-up & Samsung Anti-Malware ▼
Samsung provides an anti-malware on their phones and the Note FE is one of them. The system will detect that Magisk has been installed and a service called "SecurityLogAgent" will regularly
pop-up in your notification bar to invite you to launch the Device Maintenance app and reboot the device using an orange button to "eliminate" the threat. => DO NOT REBOOT USING THIS BUTTON ! <=
You'll end up soft-brick your phone. And this, won't disappear on it's own.
Here's how to disable and definitively hide that anti-malware crap from the Device Management app :
Download the lastest version of MiXplorer => HERE <= (Or any file manager of your choice. MiXplorer is lightweight, nice to use, free and made on XDA.)
Access the root partition in the left panel and go into the "/system/csc" folder
Open the file "others.xml" with the text editor.
Add the following line at the end :
Code:
[I]<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>[/I]
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
The Samsung Anti Malware is now disabled as well as the annoying pop-up.You're good to go, enjoy!
9 - ▼ Fix Samsung Health ▼
For whatever reasons, Samsung locks-up Samsung Health once Knox has been triggered.. But go figure why, there's only a simple thing to do to re-enable the app and be able to use it again easily.
You can either use a file manager or the app "BuildProp Editor".
Download the lastest version of MiXplorer => HERE <= (Or any file manager of your choice. MiXplorer is lightweight, nice to use, free and made on XDA.)
Access the root partition in the left panel and go into the "/system" folder
Open the file "build.prop" with the text editor.
Simply change the line
Code:
ro.config.tima=[COLOR="Red"][B]1[/B][/COLOR]
to
Code:
ro.config.tima=[COLOR="SeaGreen"][B]0[/B][/COLOR]
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
Samsung Health is now working again. :good:
10 - ▼ Troubleshooting ▼
You have a problem with your Note FE ? Take a look at those answers before posting :
Q: I try to flash TWRP with Odin but a message pops up on my device and says "custom binary has been block due to remaining installment balance". What's happening ?
A: RMM. This message is more likely to appear if you still have RMM enabled. Boot your phone, keep it powered on and running and never reboots during 7 days and it should disappear.
Q: I've flashed TWRP with success, formatted data and stuff but I see the message "custom binary has been block due to remaining installment balance" at boot and I can't boot ! What's happening ?
A: RMM again ! Once data has been formatted and Android first reinstalled, RMM lock is back! Same thing can happen if you did not install the RMM fix with TWRP. To unbrick it, you have 2 options : 1 - Flash stock BUT with HOME_CSC. (It will keep the RMM elasped time, but you'll have to keep in mind since how much time has elapsed already.) or 2 - Reflash stock and follow the entire procedure again and the waiting again. The first one might work, if not, then try the 2nd one.
Q: I've managed to install TWRP, root and get my phone up and running but I've clicked on the orange "Reboot" in the Anti-Malware tab in the Device Management app.
Now my phone bootloops (or) shows the message "custom binary has been block due to remaining installment balance" and I'm stuck with it.
A: You've got trapped into Samsung Anti-Malware crap. This utility can't delete Magisk. Any solutions ? Restore one of your previous TWRP backup but if you have none, the only solution is to re-flash stock, repeat the entire procedure, disable SecurityEventLog service to get rid of those annoying security pop-ups AND stay away from the anti-malware utility !
11 - ▼ Extras ▼
Thanks. If there is any mistakes or errors, please feel free to report them to me, I'll correct them
Credits goes to :
Magisk (@topjohnwu & @phhusson, @Chainfire, @nkk71, @osm0sis, @Captain_Throwback, @Didgeridoohan, @jenslody, @digitalhigh, @DVDandroid)
TWRP Recovery (@TeamTWRP)
The RMM Fix (@BlackMesa123)
The /data partition Fix (@dr.ketan & @RicePlay33)
Odin Soft (@anycallmongolia)
MiXplorer File Manager (@HootanParsa)
How to keep the elasped time (@societyragdoll)
SAMSUNG... (@Samsung) (duh)
Author : RicePlay33
Thanks ! I'll give it a try.
Do you think we can use all the flashable mods and custom roms from S7/S7 edge?
Well the answers are : Maybe and No.
Some mods that you can apply with TWRP may work, some not.
Concerning custom ROMs it's totally no. ROMs are designed for specific hardware and phone models. Unless someone creates a custom ROM for the Note FE, it's not possible.
RicePlay33 said:
Some mods that you can apply with TWRP may work, some not.
Concerning custom ROMs it's totally no. ROMs are designed for specific hardware and phone models. Unless someone creates a custom ROM for the Note FE, it's not possible.
Click to expand...
Click to collapse
Yes you can use custom roms from the Note 7 or Note FE of Korea [emoji12]
Envoyé de mon SM-N935F en utilisant Tapatalk
benyou54 said:
Yes you can use custom roms from the Note 7 or Note FE of Korea [emoji12]
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
I wouldn't try it lol. At your own risks
@RicePlay33 just out of curiosity, what mods have you tried ?
Paninno12 said:
@RicePlay33 just out of curiosity, what mods have you tried ?
Click to expand...
Click to collapse
I've only tried the Dual Speaker mod for the S7 edge as it was my previous device, but it only works partially on the FE actually. Whenever I make a phone call for the first time just after rebooting, the microphone works fine but then if I try any more times after, the microphone stops working without any reasons :/ Quite a weird problem.. Like I said, some mods may work, some not.
any mod you want to try i suggest take it from s8/s8+ version. anyway since you guys has root your device... try to update some of the old apps in system. got a better one out there.
I've tried the Dual Speaker for the Note 8 (Magisk mod) but it simply didn't work. That would be awesome if the dev of this mod for the S7/ S7 edge version could release a NFE one (@zubi182)
Does anyone know if Secure Folder can be somehow enabled? I managed to do it on my rooted S7 Edge , but with dark lord rom and some sort of kernel. I'm guessing this isn't possible on this rooted stock rom?
Anyone know where i can get an international note fe?dont want dual SIM version
Secure Folder can be fooled with a modified kernel yeah. To my knowledge too, it's not possible with the stock one.
please help me remove knox on samsung s7 nN935F. picture in attach. thanks all
Hi ! Was able to reboot and edit some lines (using root explorer) in build.prop ro.securestorage to false and ro.config.tima to 0. Problem is.. the securestorage even at false value i still cant view the saved wifi passwords. So i tried changing the permission to 777 thats when i had the red custom binary blocked and rmm prenormal. Flashed to stock rom last night. Not sure how but i tried flashing only with csc_home but red warning is still there. But with ap it worked. Didnt flash bl, cp etc. Am i doing this right? So now i have to wait again. Can i use supersu instead of magisk? the root is not giving me full privelege in this androdumpper app (on the saved password section ). Thank you for your awesome post RicePlay33.
@donart81 I've searched a bit and I've found this => http://phuongpn.com/how-to-decrypting-wifi-password-on-samsung-galaxy-phone-solved/ Did you done the rest of the operation ?
Also, changing the value of "ro.securestorage to false" maybe triggers the RMM lockdown as it seems related to the security of the device. (Encrypting WiFi passwords)
The message was still there because you've ONLY flashed "HOME_CSC", it was specified to flash stock (so including everything BL/AP/CP etc) but for the CSC, choosing the HOME_CSC one. It will flash stock 99% like usual but the HOME_CSC will keep the time elapsed of RMM, reducing the time needed to re-root it again.
You should have tried to disable RMM Maybe it wouldn't have bricked itself.
oh so that's how you flash hehe. i'm such a noob.
yup i think i have done the rest of the operation. I've successfully rebooted after changing the value of the build.prop (ro.securestorage + ro.config.tima) to see if it was not reverted back to original. device was working. it was only when i changed its permission checked it all suddenly it bricked my phone hehe.
next time i'll try to change the value of the "Support Rmm" in the experiment section and report back if it worked
thank you for your informative reply.
There has been some development about a possible RMM State Fix Over here.
Did anyone try it?
I'm just waiting for the 7 days to pass, and this wait itself is killing me!
Yeah I saw that. I was thinking to talk about it but I didn't had the time recently.
I'll update the main post, although I may need someone to try it first and report me what is going on on his device to be able to document it as clear as possible and also to see if it works without any problems.
Don't worry, 7 days and you'll be free like a bird is
hello i installed twrp on the device and made root and then waited 7 days and 7 days is completed. When the device is off and the device is open, the device has failed.
My fault : custom binary blocked due to remaining installment balance
Please melp me mate
what should I do ?
RicePlay33 said:
Yeah I saw that. I was thinking to talk about it but I didn't had the time recently.
I'll update the main post, although I may need someone to try it first and report me what is going on on his device to be able to document it as clear as possible and also to see if it works without any problems.
Don't worry, 7 days and you'll be free like a bird is
Click to expand...
Click to collapse
I will do it as soon as I'm released from the jail.!
However, "This being free is temporary" I guess as it seems like after a new firmware update from Samsung, This will be a routine process.
mest47 said:
hello i installed twrp on the device and made root and then waited 7 days and 7 days is completed. When the device is off and the device is open, the device has failed.
My fault : custom binary blocked due to remaining installment balance
Please melp me mate
what should I do ?
Click to expand...
Click to collapse
Hi, Im not really qualified to answer your query, But from What I have learned -
You need to flash a Stock Rom,
Do the 7 Day wait until the RMM State is disappeared,
Then Follow the steps in the OP, and Flash the RMM State fix immediately to prevent getting locked again.
{
"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"
}
Official TWRP 3.6.1-* For Galaxy S9/S9+ ExynosOnly for exynos variants - G960F (Europe, Global Single-SIM); G960FD (Global Dual-SIM); G960N (South Korea); G965F (Europe, Global Single-SIM); G965FD (Global Dual-SIM); G965N (South Korea);
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Android 10 kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 9.0/10.0
Downloads:
S9 - https://twrp.me/samsung/samsunggalaxys9.html
S9+ - https://twrp.me/samsung/samsunggalaxys9plus.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
S9 Device tree - https://github.com/TeamWin/android_device_samsung_starlte
S9+ Device tree - https://github.com/TeamWin/android_device_samsung_star2lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9810/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
First:laugh:
Nice af!
support f2fs？
Many Thanls bro ?
Thanks
Congratz Corsi
Thanks for your hard work?
Data decryption working?
thank you bro its working well
but when i go to TWRP i fount the data still encrypted and cannot be mounted although i did full data format and wipe. everytime i need to use TWRP i need to format data.
any solution around?
thanks
Is the issue described here:
https://forum.xda-developers.com/showpost.php?p=81072679&postcount=1832
fixed with this release?
jamaljmys said:
thank you bro its working well
but when i go to TWRP i fount the data still encrypted and cannot be mounted although i did full data format and wipe. everytime i need to use TWRP i need to format data.
any solution around?
thanks
Click to expand...
Click to collapse
I think I have a similar problem. These were my steps:
flashed TWRP through Heimdall
booted into TWRP
wiped data
flashed the no verity opt encrypt zip
flashed LineageOS (official nightly from May 1st), gapps and Magisk
After that I booted the system and encryption was forced during boot. When I rebooted into recovery I was prompted to enter the password, which was not successful (decrypt failed because it took too long).
Before all that I was running an official and up-to-date Android 10 Samsung (April security patch).
Hi. I need emergency help. I'm new on s9+ & flashed twrp as well formatted data partition then flashed no-verity-opt-encrypt-6.1 but whenever entered to system then returned to recovery mode then i lost internal storage again again & again. Please help me. I'm on latest android 10 firmware.
Hi ?
Will you update the SHRP to latest TWRP Base ?
And will be very good if you will support the Orange Fox Recovery
I like those two recoveries because of password protection and they have more features…
Thanks for your work for our devices!
Seems the dl link isn't working. I tried connecting to the dl site on my phone and my PC and both returned with a "This site can't be reached" error.
I just tried contacting TeamWin through the contact form on the TWRP website and it seems as though the submit file for the form was deleted.
Could I live WITHOUT disabling encryption via flashing no-verify? I want to have my /data encrypted.
Hi Mate just wondering would this working with a Samsung Galaxy S9 plus
Model SM-G96F
Android version 10
One UI version 2.1
Cheers
Dan Ger said:
Lineages os not support encryption ..so that why you have it problem like that...feel free to check on telegram support group So you will understand
Click to expand...
Click to collapse
So are you saying that LOS does not support disabling encryption? I tried the whole procedure multiple times and it seems that the patch fails because the fstab entries are not found in LOS.
Could an encrypted data partition cause issues recognizing the sim card? I find this hard to imagine, but I have both issues pretty persistently.
Cheers
The OP says:
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
I've downloaded twrp-3.3.1-1-starlte.img.tar (as recommended elsewhere for my S9) but how do I do the last part?
What is TWRP_*.tar.md5 file? How do I get it?
Is there anyone who got TWRP 3.4.0 working with encryption on a Samsung Galaxy S9?
My experiences after 1 hard week:
1. On Stock: TWRP always showed an unlock option via PIN, but it was never able to decrypt (neither default_password, nor disabling lockscreen, nor setting another PIN/Password in locksetings helped)
2. On Magisk: TWRP never showed an unlock option & was never able to decrypt
3. Only option was to disabled encryption --> the old encryption disabler from OP doesn't work, updated Disable_Dm-Verity_ForceEncrypt_03.04.2020 has to be used ( https://forum.xda-developers.com/an...rceencrypt-t3817389/post77091359#post77091359 ) --> patter lock & fingerprint cannot be used in the future
A little disappointing considering that the unlock option of TWRP & changelog suggests that decrypting should work.
@moocou
BTW: Put TWRP_*.tar file into AP tab
{
"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"
}
Unofficial TWRP 3.4.0.0 For Galaxy note 7 FE (N935X)
Disclaimer:
I do not own this device, however i work on the S7/S7E and there was enough requests for a FE support. so here we are.
This TWRP has been tested on 2 devices so far, it fixes mounting issues, and is based on new device trees. This should pave the way for other S7 developers to join in and add support to the FE since its not that difficult.
My custom kernel (Cronos) and Floyd Q Rom will make it to this thread once they are validated more.
Thanks to @butchieboy and Đỗ Gia Huy for testing
Also moving forward with this thread, you take full responsibility of any modifications done towards your device.
Features: :
Code:
- built from latest Pie source
- built from android-9.0 recovery sources
- fully compatible with Android 8.*/9.0/10.0
- Full F2FS Support for data and cache
- Full support for FLoydQ ROM
- Built with Busybox and resetprop
Downloads:
N935X (N935F/FD/S/L/K) : Download
Instructions:
Odin
Download latest Odin zip from Here
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home + Volume down + Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in your hands, disconnect the usb cable and press simultaneously the Home + Volume down + power until the Download mode pop-up shows
Press volume DOWN (so the phone reboots) then quickly press Home + VolumeUp + Power until the TWRP screen shows up
If it didn`t worked, redo the steps from #1 being more careful. and faster
TWRP (If you have a previous twrp installed)
Download TWRP_*.img, push it into phone storage (or external sdcard if thats not avalible), choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods due to RMM Lock / KG State, make sure you check this thread
Rooting and Internal Storage:
Finally, if you want to be able to read/write to the internal storage, you must format it to clear encryption, take a backup of your stuff before hand.
Go to TWRP > Wipe > Format Data > Type YES.
your data is now usable. if you didnt flash noverity-opt-encrypt or MagiskRoot your data will be encrypted again.
If you want to root your device now, simply download the latest magisk and flash it in your new recovery.
Sources:
Device tee : Github
Kernel : Github
Credits:
TeamWin, corsicanu, morogoku, Shariq3422 and testers
XDA:DevDB Information
TWRP-3.4.0.0, Tool/Utility for the Samsung Galaxy Note FE
Contributors
ananjaser1211, morogoku, corsicanu, Shariq3422
Source Code: https://github.com/ananjaser1211/android_device_samsung_gracerlte
Version Information
Status: Testing
Current Stable Version: V1.0
Stable Release Date: 2020-06-23
Current Beta Version: V1.0
Beta Release Date: 2020-06-23
Created 2020-06-23
Last Updated 2020-06-25
Misc Links:
Telegram Support Group
[*]Telegram news Channel
Latest Magisk
FloydQ Oneui 2.0 Beta ROM + N7FE Kernel
F.A.Q
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Can,t find OEM Toggle, RMM Locked
A : Read this thread
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Make sure you have the latest samsung stock firmware installed (to be on latest bootloader and modem combo)
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: How to Use F2FS ?
A : This requires you to be on Floyd ROM and the latest FE CronosKernel build. otherwise you wont be able to boot. Follow these steps
1) Wipe > advanced wipe > Data > CHANGE > F2FS (Your entire internal storage will be wiped out!)
2) Reboot and you will have DATA as F2FS, the same can be done to CACHE as well. Do not do it to SYSTEM
P.S : Again, make sure BOTH your ROM and KERNEL support F2FS.
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Yo ma...man
Well done bro!
USB OTG works. Got this error when formatting data. Restored backup that was generated, everything went fine booted up as normal.
Sent from my SM-N975U using Tapatalk
TWRP-3.4.0.0-gracerlte-20200625
TWRP-3.4.0.0-gracerlte-20200625
* Fix error in SAR disable script (Fixes installing android 9 roms while 10 is installed)
* include resetprop (required for SAR script)
* Add custom TWRP Ver Name
Download : Github
This should fix the error reported above, and fix installing Pie roms while having 10 installed.
Wow, you are all over the place my friend. Thank you..lol[emoji481]
Sent from my SM-N975U using Tapatalk
Error no longer present
Sent from my SM-N975U using Tapatalk
Getting error again when trying to create backup or flash anything
Sent from my SM-N975U using Tapatalk
butchieboy said:
Getting error again when trying to create backup or flash anythingView attachment 5048397
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Could you try to flash a pie rom while having my Q rom installed ?
the script is there to change /system_root mount point back to /system . which is due to recent TWRP changes
i think the script is erroring due to line endings, but im not sure. let me know if the ROM flashed.
for System backup always use the system image format while dealing with android 10. ill update you if twrp pushes any more updates to this
The only Pie roms that we had for FE caused major issues. Not sure if anyone even uses them there was 1 I think. Developer threw a rom together that would throw malware on your device, lock it up and made device unusable then vanished without fixing anything. So not sure if anything is out there and really don't want to update my bootloader.
Sent from my SM-N975U using Tapatalk
ananjaser1211 said:
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Click to expand...
Click to collapse
Installed TWRP 3.4.0.0 on the SM-N930, everything works ... Thanks Bro !!!
---------- Post added at 10:02 AM ---------- Previous post was at 09:18 AM ----------
ananjaser1211,may I ask you to build a core for SM-N930X???...I will be grateful.
I have released my cronos kernel for Pie
For a feature list , they are mentioned on this thread here
So now you can use the same kernel from Q on pie ROMs if you choose so.
Download : Github
Enjoy
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
thank you thank you THANK YOU
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
It's work
butchieboy said:
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
Click to expand...
Click to collapse
Did you have issues booting into system after you rooted? I know it's old but I just can't do it after flashing and following the root guide here
Nope sure didnt
Sent from my SM-N975U using Tapatalk
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
ripee said:
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
Click to expand...
Click to collapse
link broken
Well, I found this in a Telegram group (which I know I can't share the link) and when performing all possible tests, it works perfectly with my 4/128 spes.
And as we would all say, I am not responsible for any damage and loss of data caused to your device. I only share the information "as is" and the tests performed by myself on my personal device. Everything is at your own risk.
So, let's start with the post:
New Developer on this version:
@jabieff
Previous Developer
@dblenk9 - Telegram
2022/11/06 Update Changelog:
Synced latest TWRP 12.1 source
Fixed Android 13 ROM flashing issue (source side)
Changelog in the previous version by @dblenk9
Sync with latest TWRP
Update kernel to MIUI V13.0.4.0.SGCMIXM
Update blobs to MIUI V13.0.4.0.SGCMIXM
MTP fixed
Decrypt works
Features I tried and didn't have any problems
Flashing and decrypt data from A13 ROMs
Flashing and decrypt data from A12.1(A12L) ROMs
Flashing and decrypt data from MIUI-based ROMs (custom and Stock) with A12
Flashing Magisk
MTP fully functional
ADB sideload
Install recovery ramdisk and "Flash current TWRP" from Advanced menu
DO NOT USE WITH ANDROID 11 ROMS!!!
Bugs I've found so far
If you perform a format data, the internal memory will not be recognized in MTP mode of TWRP, which will not be displayed in Windows file explorer
SOLUTION: Boot into the OS at least once so that the internal memory is rebuilt and made available again in MTP mode
Sometimes, when checking the option "Automatically reflash TWRP after installing the ROM", it does nothing when it finishes installing the ROM
SOLUTION: The option seems to be somewhat bugged, so before restarting always reinstall TWRP with the methods that I will explain below
When flashing some ROMs, "Failed to mount *partition*" errors come out when you finish installing
SOLUTION: In some ROMs you may get errors when mounting some partitions, commonly "system_ext", "product" and "vendor".
If the installation process ended without any problem and without showing any error code, that's fine, you can restart without problems, This bug has been in all unofficial TWRP for this device
Steps to install
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
Tutorial for Windows only because zero knowledge for Mac and Linux
From PC:
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the TWRP image file from here, or from the post attachments
SHA256: 8F25AC88628E6D7BC5E29D8572CF4ACA3499B7D626685654B3C4548323B8D591
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device
Code:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command
Code:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end
Code:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
fastboot boot
Now, drag the image file (twrp-3.7.0.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot boot "C:\location\to\your\file\twrp-3.7.0.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in TWRP
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1
While in the TWRP menu, tap the Advanced button
Now tap on the option "Flash current TWRP"
"Swipe to confirm" and the TWRP installation process will begin
Method 2
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 3
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP if you already had it previously installed.
Conclusion
I did everything I could but I couldn't find the source code for this TWRP, so I'm sorry for that.
05/05/2023
POST
- Link to GDrive fixed
11/11/2022
POST:
- Reverted to previous version as @jabieff TWRP is unable to flash MIUI ROMs due to dynamic partitioning error.
07/11/2022
POST
- Added info about Android 11
- Updated to latest TWRP and new developer
19-10-2022
POST:
- Fixed typo and A11 ROMs info added
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
essor-13 said:
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
Click to expand...
Click to collapse
I think this version of TWRP works only with MIUI13 A12. You're on A11 version of MIUI13.
essor-13 said:
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
Click to expand...
Click to collapse
This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
NeoSDAP said:
This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
Click to expand...
Click to collapse
Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.
I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).
I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.
Thanks !
@NeoSDAP You could add sth like 'only for A12/A13'-roms to the title and add a highlighted note, that You need 3.6.1 for A11 roms to the OP.
essor-13 said:
Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.
I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).
I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.
Thanks !
Click to expand...
Click to collapse
Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.
If you want to keep everything in order:
- Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
- If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
gentano said:
@NeoSDAP You could add sth like 'only for A12/A13'-roms to the title and add a highlighted note, that You need 3.6.1 for A11 roms to the OP.
Click to expand...
Click to collapse
Thanks for the correction. I have already modified the title
NeoSDAP said:
Thanks for the correction. I have already modified the title
Click to expand...
Click to collapse
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
sarib said:
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
Click to expand...
Click to collapse
Nope. You need a PC to install the recovery. Something that can also work is to use a phone rooted with Magisk and the ADB and fastboot module
NeoSDAP said:
Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.
If you want to keep everything in order:
- Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
- If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
Click to expand...
Click to collapse
Thanks a lot for those infos. I understand a bit better now.
By any chance do you know a rom (debloated) that works flawlessly (camera, wifi, NFC, BT, etc) with the redmi note 11 ? I had LOS on my S7, that was fine because it made the device last longer, but it wasn't withoutt issues.
am I doing something wrong
Thank.
{
"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"
}
Appl1 said:
War mache ich falsch? Hat jemand eine Idee?
Thank.
View attachment 5779933
Click to expand...
Click to collapse
According to the rules, English is required.
Boot to a different version from TWRP. The v3.62 will help, then flash the v3.7.0 through TWRP. It happens, probably, because some custom recoveries, doesn't allow this version to boot to.
SubwayChamp said:
Gemäß den Regeln ist Englisch erforderlich.
Booten Sie mit einer anderen Version von TWRP. Die v3.62 wird helfen, dann die v3.7.0 über TWRP flashen. Es passiert wahrscheinlich, weil einige benutzerdefinierte Wiederherstellungen es dieser Version nicht erlauben, zu booten.
Click to expand...
Click to collapse
danke werde ich im laufe des tages ausprobieren. Ich habe auf Englisch geschrieben. Verzeihung
Appl1 said:
am I doing something wrong
Thank.
View attachment 5779933
Click to expand...
Click to collapse
Do you have unlocked bootloader?
Appl1 said:
danke werde ich im laufe des tages ausprobieren. Ich habe auf Englisch geschrieben. Verzeihung
Click to expand...
Click to collapse
Thanks for the edit of your first post and the switch to English. However, if you check you post above it's again only in German. Did you check your browser's settings if it automatically translates to German even if you wrote in English?
Regards
Oswald Boelcke
Senior Moderator
sarib said:
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
Click to expand...
Click to collapse
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Flammable98 said:
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Click to expand...
Click to collapse
There´s not such a thing; "...properly update without losing the root", any major update causes the loss of root, because of boot partition, but, if the update is only about security policies, then you shouldn´t lost root. Rooting this device can always be done, flashing the Magisk zip over the ROM.
Anyway, you can choose, not to update automatically, so, this is up to you, get it or not.
Flammable98 said:
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Click to expand...
Click to collapse
There's a new update "November patch" and I'm now thinking what I should do