{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Tab S2 8.0 2015 (LTE)
TWRP for Samsung Galaxy Tab S2 8.0 2015 (Wi-Fi)
TWRP for Samsung Galaxy Tab S2 9.7 2015 (LTE)
TWRP for Samsung Galaxy Tab S2 9.7 2015 (Wi-Fi)
How to flash a bootloader and/or modem1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import either the bootloader.tar or bootloader_modem.tar file, depending on your variant, with the "AP" button.
How to flash TWRP with Odin1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy Tab S2").
How to flash TWRP within a previous version of TWRP1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy Tab S2").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
E:recv error on uevent
- This warning appears during the process of making a nandroid backup. I assure you that it's perfectly innocence: your backup should complete successfully and it should restore successfully without any reference to this warning. This is a known bug that affects other Exynos devices as well, such as the Samsung Galaxy S7 Edge (hero2lte).
- Technical explanation from bigbiff himself: "I think it must be a bug, probably shouldn't print the log out if we aren't using ueventd to pull in partition information on a target device. I am not sure what devices we are supporting using ueventd however. Looks like it only runs from the process_fstab function. It's harmless, but I wonder if it should be put in an ifdef guard."
Credits
- Inspiration in motivating me to learn how to build TWRP: ashyx
- Updated partition sizes: jcadduono
- Testing of my gts28wifi builds to figure out the X-Y orientation bug: tripLr
- Providing source to fix MTP and ADB: bonuzzz
- Every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the gts28ltexx, gts28wifi, gts210ltexx, and gts210wifi.
Sources
- gts2 kernel repository
- gts28ltexx repository
- gts28wifi repository
- gts210ltexx repository
- gts210wifi repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy Tab S2
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-05
Created 2017-12-15
Last Updated 2022-12-09
Reserved
CHANGELOG
3.2.3-0
* Device now appears properly in adb shell, as per @t-o-f-u's patch in post #69.
Reserved
T710 only
Tested original version bad
Tested version ending in 1 working.
Backup all partitions pic below
T710 only Root access confirmed in file manager
You Might change title to [TWRP][Unofficial] xxxxxxxx
TotalNoobTrucker said:
You Might change title to [TWRP][Unofficial] xxxxxxxx
Click to expand...
Click to collapse
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
ripee said:
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
Click to expand...
Click to collapse
Ok,
Flashed back to ashyxx
Flashed file ending in 2. It works ...!
Flashed back to ashyx
Flashed file ending in 3. It works too!!!
Don't know what u did, but 1 2 and 3 worked.
I checked your md5 and they were all different.
So something was different in each one but the last 3 of 4 work.
Flashing your un numbered file now.. rechecking
There are 2 TWRP flash that rotate the screen orientation from portrait to landscape that must be added if the TW_THEME is set to landscape:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
My first link from a few hours ago was build with both of these included, and we established that it didn't work.
Build 1 from a while ago had both of these removed, build 2 only included the top one, and build 3 only had the bottom one. Do all 3 numbered builds work equally well?
Great! Just tried lastest version of TWRP for T710 (dec-15) and touch is working great! Thank you for your work!
ripee said:
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
Click to expand...
Click to collapse
Ok. Reloaded the file from basket build with no number. It works same as 2 and 3
Send it off. By the way if there is a way to append the 3.2.1-0 with ripee I would do it ashyxx did. Haha
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
ripee said:
There are 2 TWRP flash that rotate the screen orientation from portrait to landscape that must be added if the TW_THEME is set to landscape:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
My first link from a few hours ago was build with both of these included, and we established that it didn't work.
Build 1 from a while ago had both of these removed, build 2 only included the top one, and build 3 only had the bottom one. Do all 3 numbered builds work equally well?
Click to expand...
Click to collapse
Your build one is now not named 1 it works but does not rotate.
Lemme check 2 and 3
TotalNoobTrucker said:
Ok. Reloaded the file from basket build with no number. It works same as 2 and 3
Send it off. By the way if there is a way to append the 3.2.1-0 with ripee I would do it ashyxx did. Haha
Click to expand...
Click to collapse
I'd have to add the optional flag TW_DEVICE_VERSION := _ripee to the BoardConfig.mk file, but with all due respect to ashyx, I'm not particularly interested in labelling my builds. But TWRP's Jenkins builder just appends the next available version number after the dash anyway.
Ok, the code is sent off for official support!
1 2 and 3 do not rotate. Portrait only, no landscape, flip, or flip landscape . Who cares. The root works in all 3 with touch screen on each file and directory. So the screen works great
I tested a full backup in 1, 10 gig to the SD card. So mounts are working.
Wohoo
---------- Post added at 04:16 AM ---------- Previous post was at 04:15 AM ----------
By the way rebooting into download mode directly from TWRP saved a ton of boot time
---------- Post added at 04:26 AM ---------- Previous post was at 04:16 AM ----------
Running twrp-3.2.1-0-gts28wifi.tar from Odin now full time. Thanks.
Let me know if you want to play with lineage 8.0. the t710 has 64 bit processors, and the developer from posiedon 1.0 got the source from Samsung to build it.
I just tested the version for the T810:
- flashing is successful
- touchscreen is working well
- besides the normal partitions there are "modem" and "efs" listed
- a test backup throws a lot of "E:recv error on uevent" errors.
So for now I went back to TWRP 3.1.1
hurray said:
I just tested the version for the T810:
- flashing is successful
- touchscreen is working well
- besides the normal partitions there are "modem" and "efs" listed
- a test backup throws a lot of "E:recv error on uevent" errors.
So for now I went back to TWRP 3.1.1
Click to expand...
Click to collapse
I can imagine that they used the same partitions as the mobile data variants. Do modem and efs cause problems with backing up? I'll run my own backup today to confirm.
If you're using my 3.1.1, well I built it from the same sources as 3.2.1 so let's see.
I did not run the backup till the last partitions as the error came directly with the first partition. Then I interrupt the backup. I can upload the recovery.log if it is useful for you.
hurray said:
I did not run the backup till the last partitions as the error came directly with the first partition. Then I interrupt the backup. I can upload the recovery.log if it is useful for you.
Click to expand...
Click to collapse
Sorry but I'm unable to reproduce your error so please post the log. Here's what I did:
I made 2 separate backups on my T810, one with a password and one without, of the 3 partitions that are checked off by default when you go into the Backup screen. Yes, modem and EFS are present and listed as having some data, but I didn't check either of them off.
At no point in either of the backup or restore procedures did I get the "E:recv error on uevent" error, or any error for that matter.
ripee said:
Sorry but I'm unable to reproduce your error so please post the log. Here's what I did:
I made 2 separate backups on my T810, one with a password and one without, of the 3 partitions that are checked off by default when you go into the Backup screen. Yes, modem and EFS are present and listed as having some data, but I didn't check either of them off.
At no point in either of the backup or restore procedures did I get the "E:recv error on uevent" error, or any error for that matter.
Click to expand...
Click to collapse
Here is the log of my backup. As I wrote I did not finished the backup. I interrupted it as soon as I saw the error.
I don't think that the error cames from selecting the modem and EFS partitions.
Here is a litte snipped from the relevant part of the log (on line #2641 in the log):
Code:
I:addFile '/system/fonts/RobotoCondensed-BoldItalic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent
I:addFile '/system/fonts/RobotoCondensed-Italic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
I don't know why this behaviour accours. The TWRP "twrp-3.1.1-0-gts210wifi.img" from you works without error (backup AND restore ). I don't use a password or encryption on the Tab S2. The only option I use is "compress" to save some space as my backups are space consuming on the external sdcard without it.
@ripee
Hello my friend. Thank you for your effort, I want to mention about the issue in TWRP , when you run any aroma it ru in wrong orientation. I want to ask If you fix that issue in your build.
My device is T815
Sent from my SM-T815 using Tapatalk
hurray said:
Here is the log of my backup. As I wrote I did not finished the backup. I interrupted it as soon as I saw the error.
I don't think that the error cames from selecting the modem and EFS partitions.
Here is a litte snipped from the relevant part of the log (on line #2641 in the log):
Code:
I:addFile '/system/fonts/RobotoCondensed-BoldItalic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent
I:addFile '/system/fonts/RobotoCondensed-Italic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
I don't know why this behaviour accours. The TWRP "twrp-3.1.1-0-gts210wifi.img" from you works without error (backup AND restore ). I don't use a password or encryption on the Tab S2. The only option I use is "compress" to save some space as my backups are space consuming on the external sdcard without it.
Click to expand...
Click to collapse
Please allow the backup to finish without stopping it. Let me know of any other errors that pop up and, if it stops by itself, which partition it was backing up when it stopped. In the meantime, I'll take a look at your log.
NeWONEx said:
@ripee
Hello my friend. Thank you for your effort, I want to mention about the issue in TWRP , when you run any aroma it ru in wrong orientation. I want to ask If you fix that issue in your build.
My device is T815
Sent from my SM-T815 using Tapatalk
Click to expand...
Click to collapse
Is Aroma displaying in portrait orientation while TWRP is in landscape? Which exact Aroma build are you trying to flash? Did this also occur on older versions of TWRP? Are you able to tap on Aroma's menus properly, or does the tap location not correspond to the place that Aroma thinks you tapped? I need more details to be able to help.
There is a chance that Aroma needs to be updated to TWRP 3.2.
Related
Team Win Recovery Project 3.0.2-1
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 S6 edge (6.0+) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
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/samsunggalaxys6edge.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
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.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] 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 without touching any other options, then press [Start].
Hold [Volume Up] + [Home] + [Power] buttons near the end of the flash, and keep holding them until you are in recovery.
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 12 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.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 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 (twrp.me) - same as v3.0.2-1
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
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)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (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: https://github.com/TeamWin/android_device_samsung_zerolte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (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 S6 edge, Tool/Utility for the Samsung Galaxy S6 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zerolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-05-27
Created 2016-04-08
Last Updated 2016-10-02
Builds are coming soon, just putting a thread up for a reference on the device page!
jcadduono said:
Builds are coming soon, just putting a thread up for a reference on the device page!
Click to expand...
Click to collapse
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
christopherrrg said:
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
I have successfully flashed the latest twrp. Though I had issues with the older one in backup restore area. Does the new do up backup and restore without error?
Nothing for SM-G925I ? zeroltedv
Ognjen123 said:
Nothing for SM-G925I ? zeroltedv
Click to expand...
Click to collapse
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
jcadduono said:
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
G925W8 PC5 sources are up. Nothing for the 920W8 yet.
violin.siva said:
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
Click to expand...
Click to collapse
Can you please pm the link ?
---------- Post added at 11:16 PM ---------- Previous post was at 11:06 PM ----------
Can the twrp-3.0.2-1-zerolte.tar.md5 be flashed on the g925i ?
Why aren't the link working?
G925f link?
Inviato dal mio SM-G925F utilizzando Tapatalk
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Ognjen123 said:
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Click to expand...
Click to collapse
Twrp 3.0.2 with arter97 kernel. Working flawlessly in my g925i.
This is making me crazy , is there any suport here ? Links not working , where from to dl the 3.0.2-1 ver for g925i ?
OEM Unlock ??
I can't find it in my Developper Menu. I have 6.0.1 !
Help please...
Anyone found a working link for the recovery file?
Questions about TWRP versions found over some threads
I would like to know some things. Firstly say there's still nothing when you open http://teamw.in/devices/samsunggalaxys6edge.html
so, i looked up the link you gave
https://idlekernel.com/twrp/zerolte
but if I don't remember wrong, zerolte is S6 flat.
Does that kernel work anyway?
If that's so, does that mean official http://teamw.in/devices/samsunggalaxys6.html or TWRP S6 Edge Europe Version would also work?
Why wouldn't they?
Also, what's the difference with the twrp from @arter97 found Here
with yours?
Thanks!!
I hope someone could shed some light over those questions.
Sorry for my bad english!
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Ognjen123 said:
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Click to expand...
Click to collapse
See my above post.
Alright, this is what I did for my S6 Edge 925F which works fine so I thought I would share it with you guys:
I flashed the latest TWRP using ODIN from this link:
http://www.arter97.com/browse/S6/ke...r97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
which is the same link given at the bottom of this post along with the instructions as well:
http://forum.xda-developers.com/showpost.php?p=60390986&postcount=5
After rebooting the phone (which looped a couple of times), I flashed the latest SuperSU 2.71 (Beta) from ChainFire in the newly flashed TWRP which is given here:
http://forum.xda-developers.com/showthread.php?t=1538053
And now I have TWRP with SuperSU. I need to mention that I rooted my phone with CF-Auto root previously so it was already rooted, but I just wanted to have custom recovery for flashing other .zip files.
I also tried the latest stable version of SuperSU first, but it had problems finding and installing binaries. But there are no problems with the latest Beta (2.71) so far.
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
[COLOR="Red"]* Your warranty is now void.[/COLOR]
*
* 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 ROM
* 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.
*/
The "N" is for Nougat
some words of wisdom:
1- This is an Android 7.1 Nougat-based release - update your third party addons to ensure compatibility
2- The CM backupscript.sh in recovery will ignore and remove incompatible applications from your system partition (these are usually non-CM apps that users have opted to install). You must install a compatible app (or app pack) to regain that functionality
3- You can flash CM14.1 nightlies directly from CM13 snapshot or CM 13 nightlies (no need to wipe, BUT for optimum results, better follow Clean Update procedure explain below.), provided you read and followed items 1 and 2
ALLERT:
4- Once one CM14 nightlies, you cannot downgrade back to CM13 – if you are thinking of just exploring the release, then take a backup of your existing installation if you want to go back to it.
5- You’ll need an N compatible recovery, i.e. TWRP 3.0.2-1
Happy Flashing,
Latest features :
XDA:DevDB Information
Cyanogenmod 14.1 for Falcon, ROM for the Moto G
Contributors
matmutant, luca020400, LuK1337, Google, CyanogenMod Team, Motorola
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: CyanogenMod13
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-09
Last Updated 2016-11-19
Download & Install
LINKs:
All Downloads
Nightly Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
Either way, you might want to further customize your installation (both gapps and system apps), refer to this tutorial
REMEMBER:
ONLY use TWRP 3.0.2-1 or up
/!\ Before installing, read post #3. /!\
HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
NB: Since 20161118, with a Lollipop compatible recovery like TWRP 3.0.2-0, you will get stuck to recovery, It is MANDATORY to update to 3.0.2-1.; the following error is still present : E:unknown command [log] but will not prevent install.
Place the rom and other like Gapps on the internal Storage or on a USB OTG
Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
Select the Zips
Swipe to install (if using TWRP)
Reboot and wait 2-3 min
-Not confirmed for CM14 as of 20161109- Pro-TIP : To avoid GPS locking issue, refer to #Q7 of the CM12 dedicated FAQ
HOW TO DIRTY UPDATE
Download the rom zip using CM Updater or third party apps like CM downloader, CyanDelta...
Press update.
Wait 2-3 min
HOW TO CLEAN UPDATE : this kind of update helps to avoid any update related issues, you can follow this when coming from CM13 and want to keep you personal data.
ProTip : Read the Changelog and disable features that have been updated between your build and the latest build (this is important when Theme features are updated and it could break things)
Download the rom zip on the CM Website or using CM Updater or third party apps like CM downloader, CyanDelta... make sure you have gapps zip on your device
Reboot to recovery using the power menu or the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Format /system, /cache and /dalvik-cache (advance format in wipe menu of TWRP); do NOT Wipe DATA!
Select the Zips
Swipe to install
Reboot and wait 2-3 min
Notes, Bugs, and miscellaneous.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed.
Nano gapps package is recommended as it fits and provides everything in a base package you will need for gapps support. Then, you can install the other google apps from the store later on if needed.
Remember nightly builds are experimental: they can and will be broken from time to time. Always have a backup at hand.
To transfer files from/to PC when plugged in you will get the charging mode prompt status in the status bar, then click it to change from charging mode to transfer files.
Considering the quite low amount of Falcon users left over here, I'm not sure about making a full-sized FAQ;
For now, the following will take that purpose:
[SIZE=+1]Q1: Where are themes/tiles/whatever gone?[/SIZE]CM14.1 I still at early stage of public development, you should expect to face bugs, missing features, regressions, and other things closely related to WIP. Do not complain about it (even less if someone already discussed it in the thread)
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: Why does swipe to write feature doesn't work although it is enabled? [/SIZE]There is a fix for that "known" issue: see here.
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
reserved
i will try it and will post the results.
Just downloaded the ROM and Pico GApps.
I'm running CM14.1 unofficial before. I'll do the Clean Install anyway.
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Click to expand...
Click to collapse
working fine on my xt1033 both sims are working, sms are also working didnt try the call yet
legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Click to expand...
Click to collapse
same,sim card not getting detected
edit:reflashed it and both sims are getting detected
Can we disable second sim if we want in this latest nightly of 14.1.
Because I need sim disable feature.
drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
yes
drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
Yes, this was fixed a while ago and it is working in this build, head to Settings > Buttons > Configure your home button action(s).
This is build is very stable and the multitasking is unbelievable. Totally worth it!
Hiraethic said:
yes
Click to expand...
Click to collapse
You can change that in buttons option
matmutant said:
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
Click to expand...
Click to collapse
We really appreciate the work you do (in your free time) for our beloved Moto G. I know you guys worked really hard for this to happen, I've been checking the CyanogenMod Gerrit for a while now.
P.S.: I was in no way trying to dissuade anyone from using the dirty update or clean update methods. In my experience, a clean flash is always the most stable in the long run.
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Hiraethic said:
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Click to expand...
Click to collapse
SuperSU over CyanogenMOD should have caused a bootlop, you were lucky.
running 20161109.
* Dual SIM works fine
*Music app is not opening. Showing me that the app is stopped (Is it just me?)
Long press Home button brings Google Assistant after configuring with Buttons settings. (I tweaked build.prop for bringing up Google Assistant)
Battery percentage is showing only on Icon Portrait. None of other icons are working.
It's been 7 hours since I flashed it. The SoT is not that bad.
May be I'll flash abyss kernel later to check if the battery life will be improved and the swipe is definitely working very well on abyss kernel.
{
"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"
}
/* Your warranty is now void! I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the flashlight 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. */
Click to expand...
Click to collapse
Introduction
Red Wolf Recovery is alternatovní recovery based on the source code TWRP.
The main objective of the Red Wolf Recovery is to provide the features that were for some reasonrefusedto add to the official source code Winu Team (besides the maximum utilization of hardware options that device ...).
Hence Recovery supports password protection, since Team Win rejected this method of security because users generally do not read any kind of warning, then it was just a mistake on the part of Team Winu that somebody got into the facility despite a recovery password protected.
For this reason, therefore, I warn that the red wolf is secured in such a way that nobody could get into recovery without the user's password, but no recovery willnot safeguardagainst reinstall the device via Flash or Mi fastboot. So please take a note!
Acknowledgments:
Ray Li: For his help in modifying the source code TWRP.
osm0sis: In the video below scripts which also runs most of the functions recovery.
z31s1g: For the base material. theme.
And all the other developers of the various scripts and installation files as Chanfire,topjohnwu,cofface,etc
Features recovery:
- Brightness can be reduced to a minimum fair value. (TWRP only supports a minimum of 10% Brightness).
- Support for more than 50 sections (including "subsections").
- Possibility of installation of paintings in section Modem and Boot Logos.
- Adjusted ADB - for security reasons already does not start automatically at boot recovery, but now it turns in the recovery
- Recovery allows you to set and remove a password
- Torch phone is now going to turn right in Recovery
- Automatically Block stock recovery
- Recovery contains settings regarding Governor where recovery is currently running. If, therefore, not in a hurry, so just switch to performance and processes such as backup, restore or installation will be up almost 20% faster.
- When you confirm the installation file on the screen appears and warnings checkbox for the finished installation. This recovery will automatically notify the completed installation using the notification LED.
- For safety reasons deactivated TWRP theme engine.
- Official TWRP application was replaced for Snap Camera HDR.
- Access to the folder with zálohama and setting recovery is blocked. Access to these files is only possible from the recovery. (This is only an internal storage)
- The first recovery that is built on OMNI ROM code purely for Kate.
- Folder screenshotama of recovery has been moved to /sdcard/WOLF.res to already screenshots of recovery are not confused with the other screenshotama ..
- Updated Czech translation - Slovak translation can be translated from the strings provided below.
- new terminal supports three commands: unpackbootimg, mkbootimg and zipper (so they may also be retrieved from the script, of course).
- Recovery supports Tap To Wake Engine (dt2w is not supported yet ...)
- Support for "night mode".
- Built AromaFM supports Czech language.
- User can set custom name for the folder backup & ID at the ADB.
- Create backup can also be erased at once (not therefore been deleted one by one as it is in ofiko TWRP).
- Recovery is assembled on AOSP 7.1.2 / TWRP 3.1.1-0 / Omni 7.1.2.
Built-in installation files:
Supers
Magisk
Nitrogen UNROOT
substrates Rescue
Deactivation dm-verity
substrates Rescue Legacy
- Built-in scripts community:
Fix-fp-scanner (script to fix the fingerprint reader if the ROM reports "hardware can not be found")
ramdisk- cleaner (the script automatically cleans content boot from custom kernels and thus need not be renewed when switching to a different kernel stock kernel. However, the script still only supports ElementalX kernel, Radon kernel and Franco kernel.Warning: After cleaning the content boot must just to flash a new kernel - certainly attempt to restart the device to the system !!)
rm-pass(script to remove security currently installed ROM.)
NOS-before-flash-other-kernel(script recently found on 4PDA - deactivates the post-script Nitrogen boot ROM and thus allows better compatibility custom kernel).
Community scripts can thus be understandable added community. If you have your script / tip on a script about it here let me know.
Known Bugs
- The search engine of the camera HDR Snap is momentary assembly inoperable. TWRP still finds the application and if the application is installed TWRP and even prevents installation Snap CAMERA HDR.
The problem is mainly that I do not have complete access to that search engine - probably even if I somehow repaired and recovery will still prefer ofiko TWRP search application. So it probably could not be correct function ofiko TWRP applications not installed. However, definitely I do something in the next builds I make.
Link to download
latest build released: official
https://www.androidfilehost.com/?fid=889764386195913594
Update Changes
Update!
RedWolf-V3.0_006-Kate_Kenzo
Major changes;
- After clicking on the main menu icon coffee displays a new button "folder backups." Here you can now rename your current folder & zálohama or even set a new ID instead of the serial number at the ADB.
- Clicking on the Main Menu button to restore the icon appears at the top "bones". Using this button you can now delete all backups currently displayed. Therefore no longer need to delete one by one separately.
Current info
Version recovery: V3.0
Current build: 006
Number of community scripts: 4
Number of installation files: 6
Date of latest released build: 05-7-2017
Strings of recovery can be download here:
Strings for any translation AromaFM:
Extra Links
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
https://github.com/TeamWin
All Credit to ATG Droid
Source
Ss pls
not in a hurry but will have to remind you that source is not updated.... please add
~peace
AxeCORE said:
Ss pls
Click to expand...
Click to collapse
here!
adithyan25 said:
not in a hurry but will have to remind you that source is not updated.... please add
~peace
Click to expand...
Click to collapse
Visit our Forum - https://androidforum.cz
měj hezký den
Can i flash any rom on this type of recovery ?
xN00Bx said:
here!
Click to expand...
Click to collapse
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
+1
filipino guy said:
Can i flash any rom on this type of recovery ?
Click to expand...
Click to collapse
Yes you can flash it on any roms
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
xN00Bx said:
Yes you can flash it on any roms
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
Click to expand...
Click to collapse
Yaa now working don't know why it didn't worked at first he he he thank you bro
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
anandumohan said:
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
Click to expand...
Click to collapse
Same thing
Recovery was withdrawn because its not yet ready to run on the variant Kenzo fully,
only kate is completely functional!
we will back to you when it's gets fixed
~thanks
Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator
{
"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