Related
Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-T377T and SM-T377W models only! Do not flash on Qualcomm models!
They have only been tested on the LTE models.
WARNING: 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.
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/samsunggalaxytabe80exynos.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 OBTAINING ROOT
Extract Odin_3.10.7.zip to your computer.
{
"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"
}
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gteslte.
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 without touching any other options, then press [Start].
Hold [Volume Up] + [Home] 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.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
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.
Go to [Reboot] -> [System].
* 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 - Initial build 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 (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_gteslte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_gteslte (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 Tab E 8.0, Tool/Utility for the Android General
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_gteslte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-07-15
Created 2016-07-16
Last Updated 2016-07-15
Qualcomm modem LTE
jcadduono said:
This is for the Exynos SM-T377T and SM-T377W models only! Do not flash on Qualcomm models!
They have only been tested on the LTE models.
Click to expand...
Click to collapse
Hi, I am very new. My device is a T377W LTE edition... I believe it's a qualcomm snap dragon 410. Looks like this build does not work on mine.. Is there any plan to support Qualcomm tab E please?
Thanks in advanced.
kc2 said:
Hi, I am very new. My device is a T377W LTE edition... I believe it's a qualcomm snap dragon 410. Looks like this build does not work on mine.. Is there any plan to support Qualcomm tab E please?
Thanks in advanced.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-samsung-tab-e-sm-sm-smnu-smp-t3302935
you don't have a T377W you have a T377P / T377R4 if it is snapdragon
Hi, my device is T3777, and it also works fine after installing the twrp and rooting.
Thanks for your valued experience and it really helps me a lot.
There is no .tar
Tacodelish said:
There is no .tar
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24665509702140789
I ended u making a tar...thx though.
Does anyone know of any non-stock ROM's for our T377W?
i tried it, got TWRP on there, but when I run root checker, still says that I don't have root. I have the tmobile T377T version. Tried Flashing the super su beta as well, still doesn't say I have root, but the su icon is on the device now. What did I do wrong?
---------- Post added at 09:43 PM ---------- Previous post was at 09:24 PM ----------
Never mind, got it rooted, i was using the wrong chainfire file. Good to go, Thanks for everything!!!!!!
Drunken1 said:
i tried it, got TWRP on there, but when I run root checker, still says that I don't have root. I have the tmobile T377T version. Tried Flashing the super su beta as well, still doesn't say I have root, but the su icon is on the device now. What did I do wrong?
---------- Post added at 09:43 PM ---------- Previous post was at 09:24 PM ----------
Never mind, got it rooted, i was using the wrong chainfire file. Good to go, Thanks for everything!!!!!!
Click to expand...
Click to collapse
Here is what I ended doing when I had this problem ...
Download the latest STOCK FIRMWARE at this website or use SamFirm
Completely WIPE your device with TWRP (Format everything!)
Use ODIN 3.12.4 to install the STOCK FIRMWARE you downloaded above
Re-Install TWRP
Re-Do SuperSU SR4
That process fixed my same issue with root not sticking. Hope it works for you. Please make sure you have a good download of the STOCK FIRMWARE. If you don't, you have nothing to install after the wipe, there will be no nandroid backup, etc. You need ODIN and STOCK FIRMWARE to have this work!
Everything worked fine but when uninstalling bloatware i uninstalled something (can't remember the name) which i shouldn't have and now i get the error that there is no OS installed. Is there a way to fix this for the t377W?
Does anyone have stock ROM for T377T? I can't find it anywhere.
jcadduono said:
Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-T377T and SM-T377W models only! Do not flash on Qualcomm models!
They have only been tested on the LTE models.
WARNING: 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.
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/samsunggalaxytabe80exynos.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 OBTAINING ROOT
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 gteslte.
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 without touching any other options, then press [Start].
Hold [Volume Up] + [Home] 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.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
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.
Go to [Reboot] -> [System].
* 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 - Initial build 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 (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_gteslte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_gteslte (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 Tab E 8.0, Tool/Utility for the Android General
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_gteslte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-07-15
Created 2016-07-16
Last Updated 2016-07-15
Click to expand...
Click to collapse
I got the dreaded custom binary blocked by FRP lock. I did something stupid. Turned bootloader lock on again as i didn't realize that it would block TWRP and the booting of the device. The root process and installation of TWRP went great. Thank you....
I rooted mine to play with xmodgames, but I can't get it to work unless I get a custom rom or kernel. That is where I can't find a rom or kernel for small t377t 6.0.1 as of right now
I tried flashing the tar file for TWRP and it fails in Odin. I have the Tab E T377T and it's currently soft bricked. Is there an Odin flashable recover file that will work. I can only find IMG file on TWRP webpage.
Solved. Created my own tar file and flashed with Odin. Rooted and working great!
All rooted, working good. Are there any roms out there yet?
Sent from my SM-T377T using XDA-Developers mobile app
s_uperd_ave said:
All rooted, working good. Are there any roms out there yet?
Click to expand...
Click to collapse
I have the same question!
I have the SM-T377T, cpuz says I have ARM cortex-a7. So I assume this is Exynos as my s7 edge has exynos and comes up as cortex as well. Just want to confirm before flashing the incorrect img and soft bricking. Thanks in advance!
sparkx86 said:
I have the SM-T377T, cpuz says I have ARM cortex-a7. So I assume this is Exynos as my s7 edge has exynos and comes up as cortex as well. Just want to confirm before flashing the incorrect img and soft bricking. Thanks in advance!
Click to expand...
Click to collapse
Should work fine. I have the T377T and flashed successfully with Odin.
jdon723 said:
Should work fine. I have the T377T and flashed successfully with Odin.
Click to expand...
Click to collapse
Thanks! I'll give it a shot!
Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T 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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
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.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
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 the next step 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 your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
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-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.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 for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.
ext4 decrypted fine on OnePlus 3 OOS 4.0.2.
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.
Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T
Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.
Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?
chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.
{
"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"
}
This is only for Huawei P9 (EVA)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-eva.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.1-1/twrp-3.1.1-1-eva.img"][U]download twrp-3.1.1-1-eva.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-01
Last Updated 2017-06-11
Changelog
Code:
[B]TWRP 3.1.1-0[/B]
* bump up TWRP version to 3.1.1
* fix backup of /version
* use device specific and updated prebuilts (+kernel)
* remove the ability to flash images to ext4 mounted partitions
[B]TWRP 3.1.0-3[/B]
* kernel updated for proper loop support
* magisk can now be installed and is supported by every rom running b380+ kernel (tested on b383)
* native_package.xml has been changed to device specific version
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD cards or OTG drives
* Enabled direct image flashing to special partitions
(be careful when using it - one wrong klick means brick in a second!)
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
[B]TWRP 3.1.0-1[/B]
* proper handling of decryption (improves booting time by ~10 seconds)
* do not wipe /data/hw_init during /data wipe or factory reset to prevent system errors
* cleanup ramdisk, reduced image size by 10mb
[B]TWRP 3.1.0-0[/B]
* add the ability to format oem specific partitions
* add back f2fs support so we can format /data as f2fs
* bump up twrp version to 3.1.0
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
frenzissi said:
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
Click to expand...
Click to collapse
Yes, should be fine
Atarii said:
Yes, should be fine
Click to expand...
Click to collapse
I can confirm this works fine
Thanks
<<<by scaniathe>>>
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
LE: I flashed @Atarii B378 img and now I am rooted. AdAway is working as expected. Thank you!
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
OldDroid said:
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
Click to expand...
Click to collapse
The one from here https://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947. Dont waste your time. Its working if B378 img from Atarii is flashed.
Atarii said:
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
Click to expand...
Click to collapse
L09 B378 img is ok for now. Still need to test if system apps uninstall. But I am happy Adaway is working!
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Perfect!
Thanks
cbgti said:
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Click to expand...
Click to collapse
Encryption/decryption support is related to the /data partition (where your user files are stored). The encryption scheme changed for Nougat, so this is the first TWRP that supports being able to read/write to that encrypted /data partition.
Read-only system mode (aka systemless mode) - some people do not touch the system partition, so they can later apply OTAs easier (as they perform a diff on system files)
good job OpenKirin team, thx a lot
So supersu from chainfire isn't working even on this, right?
@Atarii : Thanks!
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
maliniaka said:
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
Click to expand...
Click to collapse
Propably the script wont work on huawei, but we work on it.
will this TWRP work for the Honor 6x Nougat Beta too?
sassmann said:
will this TWRP work for the Honor 6x Nougat Beta too?
Click to expand...
Click to collapse
what does the title say, whats the name of the forum where this has been posted?
Hope this answers everything!
PS: Its comming soon for H6X.
{
"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"
}
DISCLAIMER:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
INFORMATION:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing or rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Read more about TWRP here: https://twrp.me/about/
NOTE :
This build of TWRP is based on the kernel source code and no prebuilt kernel was used for building. Because, it is the first build, testers are very welcome for providing feedback regarding the build.
CHANGELOG (3.2.3.0) :
WHAT'S NEW?
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
CHANGELOG (3.3.0.0) :
WHAT'S NEW?
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
* Also, there was a major bug with the previous build which prevented the flashing of any file because of the "digest-verification" has been fixed with this release. Enjoy!
CHANGELOG (3.3.1-0) :
WHAT'S NEW?
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
DOWNLOAD :
You can download the latest build of the TWRP from the official site here:
TWRP(Official)
BUGS:
Encryption (for MIUI)
INSTRUCTIONS :
Download the recovery image and place it in some folder on your desktop and open the Terminal/Command Prompt/Powershell in the said folder.
Connect your device to the PC and boot into the fastboot mode using H/W keys or by typing :
Code:
adb reboot bootloader
Now, type :
Code:
fastboot flash recovery twrp-3.3.0-0-violet.img
OR,
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
Download the recovery image from the link.
Reboot to TWRP.
Hit Install and tap the "Images..." button in the lower right
Browse to the location of the TWRP image on your device and select it.
Select recovery from the partition list and swipe to flash.
For users who are running MIUI :
Thanks to Snehashis Sarkar for a short tutorial.
Your data will get wiped before flashing the recovery so take a backup of the internal storage.
Reboot to fastboot.
Wipe the Userdata via fastboot.
Flash this recovery.
Boot into the recovery and format the data (just format it, don't go for the "advanced wipe" section .
Flash this image file: Patched fstab + vbmeta + thermal configs for better performance
Reboot and enjoy.
CREDITS:
TwrpBuilder for trees
Kernel Source :
Link: android_kernel_xiaomi_sm6150
XDA:DevDB Information
[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO], Tool/Utility for the Xiaomi Redmi Note 7 Pro
Contributors
Doomsday101
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-11
Current Beta Version: 3.3.0-0
Beta Release Date: 2019-04-03
Created 2019-04-02
Last Updated 2019-05-23
Reserved
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Thank you for your build !
Do you know if someone started to work on porting ROMs ?
diamantik said:
Thank you for your build !
Do you know if someone started to work on porting ROM's ?
Click to expand...
Click to collapse
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Can you send me the logcat of the kmsg file present in the /proc directory using adb shell when the twrp is stuck on bootlogo?
Doomsday101 said:
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Click to expand...
Click to collapse
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
diamantik said:
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
Click to expand...
Click to collapse
Sure thing ?
It will boot, try fastboot erase userdata, but you can't flash any ROM (MIUI) atm, as it has encryption bug, which needs to be fixed by the OP!
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
moriyaprateek said:
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
Click to expand...
Click to collapse
The recovery has the encryption bug atm as stated by @talk2indrajit in the last post. So, you will have to erase userdata via fastboot first. I suggest you take a backup, get rid of Miui and continue with the said process and flash the newly built LOS16 by @Dyneteve (if you seek to flash a custom ROM).
Can anyone update the twrp to 3.0.3?
Not able to flash vbmeta.img fastboot mode..
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Aj51 said:
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Click to expand...
Click to collapse
Download latest adb from here
https://developer.android.com/studio/releases/platform-tools
When can it decrypt /data?
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Same problem happen with me
kishangupta009 said:
Same problem happen with me
Click to expand...
Click to collapse
Don't use this command, it was mentioned somewhere, it doesn't work for now, you need to flash it , fastboot flash recovery recname.img.
Guys this TWRP is not working , gets stuck at TWRP logo !
Try the another : https://forum.xda-developers.com/re...ficial-3-2-3-redmi-note-6-pro-violet-t3912400
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
kuhru said:
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
Click to expand...
Click to collapse
Thank you for trying it out previously. I have released a new build today with the latest TWRP version (3.3.0.0) and now the "digest-verification" bug has been fixed.
{
"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"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
Latest for OneUi-3.1
TWRP (Official link)
vbmeta
Odin tool
First time Installation
Note: custom vbmeta needs to be flashed to disable the verification of custom mods, this is a one time flashing in stock firmware
Backup your data
Unlock the Bootloader, View thread
Reboot to Download mode [Check Key Combos Below]
Disable auto reboot in Odin options, Flash vbmeta.tar in AP slot using Odin tool
Reboot again to Download mode and now Flash twrp-[$version]-m30s.img.tar in AP slot using Odin tool
Boot into TWRP Recovery [Check Key Combos Below]
Decrypt Internal Storage - Flash DM-Verity ForceEncrypt disabler
Wipe -> Format Data
Reboot -> System(without root) | Recovery(with root)
Updating TWRP
Download the latest version of twrp-[$version]-m30s.img
Reboot to TWRP recovery -> Install -> Install Image & Select twrp-[$version]-m30s.img, choose recovery partition & swipe to flash
Reboot to Recovery
Patching TWRP with Magisk
Download the latest Magisk Manager here & Install
Download/Copy the TWRP image to your device
Press the Install button in the Magisk card
Make sure “Recovery Mode” is checked in options.
In most cases it should already be automatically checked.
Choose “Select and Patch a File” in method, and select the TWRP image
Magisk Manager will patch the image to [Internal Storage]/Download/magisk_patched.img.
Proceed with the above steps to flash Magisk Patched TWRP.
Key Combos
OneUi-3.0+ Requires usb connected to PC for getting into TWRP
Download Mode - Turn off device, Press and hold [vol + & vol -] connect usb to PC
Recovery Mode - Turn off device, Press and hold [vol + & Power] release power button after screen on, continue pressing [vol +]
Magisk System - Turn off device, Press and hold [vol + & Power] release both keys after screen on
TWRP->Reboot->Recovery to get into Magisk enabled System
Other Downloads
Mega
XDA:DevDB Information
TWRP 3.5.0, Tool/Utility for the Samsung Galaxy M30s
Contributors
santhoosh, thirdsty
Source Code: https://github.com/santhosh6194/android_kernel_samsung_m30s
DT: https://github.com/santhosh6194/android_device_samsung_m30s
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-01-15
Created 2020-01-14
Last Updated 2021-05-12
Changelogs:
Stable v2.0
- TWRP Official
- Added option to wipe vendor and product
- Supports GSI (MTP)
- Kernel tweaks
Stable v1.4
- Updated TWRP version to 3.4.0-0
- Based on latest BTG1 & BTF3 Sources
Stable v1.3
- Fixed reboot during backup
- Used Linaro GCC
- Made some changes to MTP
Stable v1.2
- Supports android 10 update
- Used latest BT6 sources
Stable v1.1
- Changes in MTP, more stable now
- Reverted Ext4 with f2fs on data partition
- Kernel changes
Stable v1
- Based on ASL2 firmware, do not flash on other firmware
- Fixed kernel panic during data wipe in twrp
- Fixed Random reboots occurred after magisk installation
Beta v03
- Fixed brightness slider
- Removed Selinux Always enforce
Beta v02
- Fixed color inversion
- F2FS changed to Ext4 for data partition in twrp
Beta v01
- Initial Builds
Note: This Twrp recovery works with custom kernel, changes to kernel that makes Twrp with magisk work without bugs.
Kernel Changes:
GPU drivers integrated with kernel
Added more cpu governors and i/o schedulers
Removed a bug which causes kernel panic
Removed Selinux always enforce
Thanks for the development brother....
Thank you so much, this was much needed
any chance of this one becoming Official????
sanctioned_k said:
any chance of this one becoming Official????
Click to expand...
Click to collapse
I'm not sure
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
redymedan said:
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
://youtu.be/knqWamnaeho
Click to expand...
Click to collapse
Thank you
redymedan said:
I confirmed It worked on Galaxy M30s, Thanks @santhoosh for developing it, to boot system with magisk we must Reboot to RECOVERY, I think you need to edit it on the top page. I have created video for rooting it and proofing that it worked. Security protection worked with no issue.
Click to expand...
Click to collapse
Thanks for the efforts !
On my way trying , but I'm on a SM-M3070(not 307F) , does this works ?
Thanks for the efforts !
On my way trying , but I'm on a SM-M3070(not 307F) , does this works ?
Click to expand...
Click to collapse
This TWRP is only for ASL2 Firmware, November update. You can try it.. if something goes wrong or failed, just flash the ROM to make it works again.. so i suggest you to download the firmware before root.. I can not answer it.. it works or not, I don't have the model number on my hand..
redymedan said:
This TWRP is only for ASL2 Firmware, November update. You can try it.. if something goes wrong or failed, just flash the ROM to make it works again.. so i suggest you to download the firmware before root.. I can not answer it.. it works or not, I don't have the model number on my hand..
Click to expand...
Click to collapse
Thanks !
Mine is M3070ZCU2ASL2 , looks still have a chance , wish a good luck to me (´・ω・｀).
EDIT : It works on M3070 !
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
lfk0000 said:
Thanks !
Mine is M3070ZCU2ASL2 , looks still have a chance , wish a good luck to me (´・ω・｀)
Click to expand...
Click to collapse
Let we know if it works on M3070, it will help other..
redymedan said:
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
Let we know if it works on M3070, it will help other..
Click to expand...
Click to collapse
I will try that later, I need to make sure this twrp is stable and bug free. So Porting it will be easy. Waiting for more users to try on it
I will try that later, I need to make sure this twrp is stable and bug free. So Porting it will be easy. Waiting for more users to try on it
Click to expand...
Click to collapse
Nice to hear that, let me know if you are ready to port it.. I will be the first to test it. About this TWRP I have used it from last night for daily activity until now there is no issue or bug.. and also I activated some security protection. Thank You
redymedan said:
Nice to hear that, let me know if you are ready to port it.. I will be the first to test it. About this TWRP I have used it from last night for daily activity until now there is no issue or bug.. and also I activated some security protection. Thank You
Click to expand...
Click to collapse
Which device you are using?
santhoosh said:
Which device you are using?
Click to expand...
Click to collapse
I have some devices M30s, A50, A50s, right now I used M30s for testing the TWRP
redymedan said:
Hi @santhoosh, could you porting this TWRP to Galaxy A50s. As we know M30s and A50s have same platform comes with Exynos 9611 and Android 9 Pie, thanks.
---------- Post added at 03:15 AM ---------- Previous post was at 03:13 AM ----------
Let we know if it works on M3070, it will help other..
Click to expand...
Click to collapse
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
EDIT : soveled ,by pressing "vol + & power " to power on , magisk shows up agian !!! Now working on installing xpsoed.
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
Click to expand...
Click to collapse
You must Reboot to recovery, if it does not work. You must start at the beginning by flashing the stock ROM, format data will not solve the problem.. I have experienced about that. for Xposed framework I will test it, it may be you missed a step..
lfk0000 said:
It works , everything goes right as the tutorial , I have the magisk installed properly.
But I used the magisk manager to install the riru-core and EdXposed , after a reboot , the exposed didn't show up , at the same time the magisk has gone ( magisk manage says there is no magisk onboard ).
So I boot my phone to download mode and flash TWRP_ASL2_MagiskPatched.tar via odin agian , then to TWRP format data and flashing Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip , but it does't work , there is still no magisk .
Any suggestion ?
Click to expand...
Click to collapse
Everytime you reboot normally the system without magisk will be loaded, to enable magisk on boot 'turn off device, press and hold [vol + & power] release both keys when screen turns on. This will enable magisk on boot and this is how it works for devices like ours which have system as root. And edxposed I have tested it before having bootloop issues, it might or might not work