{
"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:
* Your warranty is now void.
* 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.10.5
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 8.0
How to flash TWRP with Odin
1. If your phone 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 simultaneously. When the warning screen appears, release all buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".
3. Disable auto reboot in Odin and press start.
4. You can then boot directly into TWRP by pressing the Power, Home and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 8.0").
How to flash TWRP within a previous version of TWRP
1. If your phone 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 buttons when the boot screen appears ("Samsung Galaxy Note 8.0").
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.
Bugs
- You tell me!
Credits
TWRP Team and all people who worked / are working on the exynos 4 devices.
Sources
- n5100 repository
- n5110 repository
- n5120 repository
- TWRP repository
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my spare time and every donation keeps me motivated.
donate
XDA: DevDB Information
TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 8.0
Contributors
@html6405
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-03-14
Created 2021-02-21
Last Updated 2021-10-12
is the file corrupted? it's only 7KB instead of 7MB
begucu said:
is the file corrupted? it's only 7KB instead of 7MB
Click to expand...
Click to collapse
Hi, which file did you try?
They are all about 7.2MB, if you downloaded it with your device, check if it didn't downloaded the html page instead (I've seen this many times)
html6405 said:
Hi, which file did you try?
They are all about 7.2MB, if you downloaded it with your device, check if it didn't downloaded the html page instead (I've seen this many times)
Click to expand...
Click to collapse
I tried to download
Code:
https://dl.twrp.me/n5100/twrp-3.5.0_9-0-n5100.img
And as you said, I only got the html file
I'm using Google Chrome with Internet Download Manager.
It took a couple times to download the 7MB file
TWRP 3.5.1_9-0 is now ready to download , if you should find any bugs, let me know.
Does anyone know anyone who wants to sell his GT-N5120? Thanks
TWRP 3.5.2_9-0 builds are up, I've readded some file systems.
Can anyone access an encrypted data partition from TWRP?
I tested TWRP 3.3.1, 3.5.0_9, 3.5.1_9, 3.5.2_9-0 and 3.5.2_9-1 on my n5110, and no version asks me for the password, and the mounting process fails.
I encrypted the device shortly after @html6405 added support for it in his LineageOS 16 ROM. I selected "resize partition" in TWRP for the data partition, then the encryption succeeded in LineageOS. Since then, TWRP fails to access the data partition.
I attach recovery.log. This is from TWRP 3.5.2_9-1.
The most interesting line is probably
Code:
E:Unexpected value for crypto key location
Is my data partition messed up (although Lineage functions correctly), or has TWRP a problem with encryption, which @html6405 might be able to solve?
Mynacol said:
Is my data partition messed up (although Lineage functions correctly), or has TWRP a problem with encryption, which @html6405 might be able to solve?
Click to expand...
Click to collapse
Hi,
the encryption in TWRP was never supported for these devices, but I will take a look at it and try to find a solution.
Update 16.06.2021:
Brought support for GSI flash & reused old HIDDEN partition as vendor.
Brought support for encrypted /data partition.
Can i use this recovery img for my device gt-n5100 with build number KOT49H instead of KONA3G which is the only one available at twrp website?
sparks2012 said:
KOT49H
Click to expand...
Click to collapse
This code is only software related from samsung's side.
You can use the recovery.
html6405 said:
This code is only software related from samsung's side.
You can use the recovery.
Click to expand...
Click to collapse
Thanks
Hi,
After trying to revert my device to stock I lost twrp as well as the system..
Now my device is only showing start screen with samsung logo.
I want to reinstall TWRP so I followed procedure and with the device in download mode, from Linux I do:
Code:
heimdall flash --RECOVERY twrp-3.5.2_9-1-n5110.img
It seems to work (see logs below)
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
but when I restart the device and try to enter TWRP I get nothing but the same screen with Samsung logo.
I retried flashing several times but always same result.
Do you have an idea what could be wrong and how to solve it?
Thanks,
mutonic said:
Hi,
After trying to revert my device to stock I lost twrp as well as the system..
Now my device is only showing start screen with samsung logo.
I want to reinstall TWRP so I followed procedure and with the device in download mode, from Linux I do:
Code:
heimdall flash --RECOVERY twrp-3.5.2_9-1-n5110.img
It seems to work (see logs below)
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
but when I restart the device and try to enter TWRP I get nothing but the same screen with Samsung logo.
I retried flashing several times but always same result.
Do you have an idea what could be wrong and how to solve it?
Thanks,
Click to expand...
Click to collapse
If your device won't enter TWRP or the stock ROM (if you've flashe a full Firmware),
it could be that your eMMC is locked and need to get replaced.
html6405 said:
If your device won't enter TWRP or the stock ROM (if you've flashe a full Firmware),
it could be that your eMMC is locked and need to get replaced.
Click to expand...
Click to collapse
locked eMMC?? never heard of that before... what is it?
My device is in this state since I tried to flash the stock back ...
Could't it be related?
Edit:
Also I was surprised when I flashed the stock rom back to see the customized boot logo (with your nickname + xda developer) still displayed.
So it seems something went wrong or wasn't completely restored as I should see the original Samsung logo..
mutonic said:
locked eMMC?? never heard of that before... what is it?
Click to expand...
Click to collapse
The eMMC firmware lock's the storage if there are no blocks left.
Than it's read only.
mutonic said:
Also I was surprised when I flashed the stock rom back to see the customized boot logo (with your nickname + xda developer) still displayed.
So it seems something went wrong or wasn't completely restored as I should see the original Samsung logo..
Click to expand...
Click to collapse
This would be gone if the eMMC would store the flashed data.
html6405 said:
The eMMC firmware lock's the storage if there are no blocks left.
Than it's read only.
This would be gone if the eMMC would store the flashed data.
Click to expand...
Click to collapse
Very strange.. can it be fixed?
I wonder how something like this can happen.. I don't think I did anything wrong while flashing.
mutonic said:
Very strange.. can it be fixed?
Click to expand...
Click to collapse
Yes, your eMMC need to get replaced.
mutonic said:
I wonder how something like this can happen.. I don't think I did anything wrong while flashing.
Click to expand...
Click to collapse
Also a storage has it's physical end, the blocks are limited.
html6405 said:
Also a storage has it's physical end, the blocks are limited.
Click to expand...
Click to collapse
Thanks for precisions.
So this means it would be wearing issue? which would make sense given age of this device...
html6405 said:
Yes, your eMMC need to get replaced.
Click to expand...
Click to collapse
You mean hardware, how can it be?
Originally I wanted to restore device back to stock to benefit from trade in bonus offer from samsung.
I guess I'd rather getting it traded as it is than trying to repair it...
Related
Team Win Recovery Project 3.0.2-0
This is for the Exynos WiFi SM-T580 model only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your retailer 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/samsunggalaxytaba101wifi2016.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
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.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
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 gtaxlwifi.
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, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
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/jcadduono/android_device_samsung_gtaxlwifi (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thanks for this work!
I managed to flash and boot into TWRP recovery but i have partition problem :
"failed to mount data"
"internal storage is listed as 0MB"
http://imgur.com/a/Ut3S7
http://imgur.com/qDCs9iS
EDIT2: As mentionned by @jcadduono , there is a simpler method than mine :
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Click to expand...
Click to collapse
EDIT3: use@ashyx' patch to remove encryption:
BOOT IMAGE PATCHER
Boot image patcher to remove DM-verity and Forced encryption.
Flash the zip below with TWRP.
This was built by jcadduono not me, so props to him, I just modified it to work for this device and to remove the SEANDROID ENFORCING message.
NOTE: IF YOU INTEND TO ROOT THEN FLASH THIS AFTER SUPERSU.
no-verity-no-encrypt_ashyx
.
Click to expand...
Click to collapse
bws78 said:
Thanks for this work!
I managed to flash and boot into TWRP recovery but i have partition problem :
"failed to mount data"
"internal storage is listed as 0MB"
http://imgur.com/a/Ut3S7
http://imgur.com/qDCs9iS
EDIT: I found out a solution to solve my problem, at least to root my device.
-Flash back stock recovery using odin
-Boot in stock recovery and Wipe data/factory reset
-Boot DIRECTLY in download mode (DO NOT NORMAL BOOT)
-Flash TWRP recovery using odin
-Boot DIRECTLY in TWRP recovery (DO NOT NORMAL BOOT)
(/data partition should be visible)
-For root flash Supersu.zip (or what you want)
-reboot system (device is now rooted)
Each time my device boot on android I lose /data partition in TWRP, maybe due to partition encryption
Click to expand...
Click to collapse
yes Exynos 7870 devices currently have a bug where Samsung is using their own crypto daemon and telling vold to force encryption regardless of fstab flags, I reported it to Samsung security team but not sure if they are looking into it. So far haven't found a way to prevent encryption from happening. (I removed all references to encryption in ramdisk & system.prop and it still encrypts, wow!)
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Could it possibly work for SM-T585? Would it be possible to use your repos and compile a build for my tab?
Alexander_the_B0ss said:
Could it possibly work for SM-T585? Would it be possible to use your repos and compile a build for my tab?
Click to expand...
Click to collapse
I've been hoping someone would show up with the T585 in the #twrp channel on freenode so we could work on it, it would only take minimal changes (basically just take the dtb from stock T585 rom I guess, kernels should be exactly the same)
You could try flashing T580 TWRP and let me know if it works though, then I can just combine them if so.
jcadduono said:
I've been hoping someone would show up with the T585 in the #twrp channel on freenode so we could work on it, it would only take minimal changes (basically just take the dtb from stock T585 rom I guess, kernels should be exactly the same)
You could try flashing T580 TWRP and let me know if it works though, then I can just combine them if so.
Click to expand...
Click to collapse
I am too tired right now and not in the mood. Very sick, having some tooth issues and maybe we can sort this out somehow. But not today, I am really sorry. May be tomorrow. Add 13 hours to your time and you'll know if I am on-line or not. It's about 7 am here, been up all night and need some sleep. Just PM me whenever you can and I'll hop on Freenode.
I'm having problems booting from Download mode (after flashing recovery via Odin) directly into Restore mode... Is there a trick I'm missing? I can't seem to find a way to get the battery out so right now all I can do is reboot in Download_mode>cancel>volume up and I'm in TWRP but same partition/data issue as above. Thanks for any help
8BitAirwaves said:
I'm having problems booting from Download mode (after flashing recovery via Odin) directly into Restore mode... Is there a trick I'm missing? I can't seem to find a way to get the battery out so right now all I can do is reboot in Download_mode>cancel>volume up and I'm in TWRP but same partition/data issue as above. Thanks for any help
Click to expand...
Click to collapse
In download mode press [power + vol down + home], when the screen turn off press [power + vol up+ home].
But you should try format data in twrp (on wipe page) as mentioned by jcadduono. It's a easier way to remove partition encryption (wipe everything on /data)
bws78 said:
But you should try format data in twrp (on wipe page) as mentioned by jcadduono. It's a easier way to remove partition encryption (wipe everything on /data)
Click to expand...
Click to collapse
First off thank you so much for the fast reply, I should have thought of that- well the button swap I never would have come up with the quoted I'm rather new/in middle of a dedicated but gradual move from iOS Dev to Android! Loving it and this community, thanks again
root sm-t580
@bws78
Hello,
Sorry for my bad english, first!
To Boot DIRECTLY in download mode from stock recovery correctly once i wipe data/factory reset, do i have to power off and then use buttons power + (volume -) + home?Is that correct?
Same thing when i finish to Flash TWRP recovery using odin to boot DIRECTLY in TWRP recovery, buttons : power + (volume +) + home ?
Thanks fo your response
yetibiker said:
@bws78
Hello,
Sorry for my bad english, first!
To Boot DIRECTLY in download mode from stock recovery correctly once i wipe data/factory reset, do i have to power off and then use buttons power + (volume -) + home?Is that correct?
Same thing when i finish to Flash TWRP recovery using odin to boot DIRECTLY in TWRP recovery, buttons : power + (volume +) + home ?
Thanks fo your response
Click to expand...
Click to collapse
To boot in download mode from stock recovery, go to power off or reboot system and when the screen turn off press
[power + vol down + home].
To boot in recovery mode from download mode, long press [power + vol down + home], when the screen turn off press [power + vol up+ home].
But this method it's tedious. Try @jcadduono method to wipe /data encryption from TWRP:
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Click to expand...
Click to collapse
recovery t580
Hello,
I flash the TWRP in download mode whithout doing data/factory reset before in stock recovery but when i try to reboot in TWRP, because odin say success, i'm finally in stock recovery!
How many times i've to wait the bar stop in download mode? Because the bar wasn't totally full when i reboot, miss just a very little bit, but after few(too long) minutes i try to reboot to go on TWRP but not here, just stock recovery. I missed up something? I can't remove battery, is that for?
Thanks for your time
So this replaces the regular recovery image? If so the first thing I'd want to do is make a backup I guess right?
I know this looks to be early days, but anyone looking into cm on this device(just got it today) also any luck with xposed?
---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------
UntouchedWagons said:
So this replaces the regular recovery image? If so the first thing I'd want to do is make a backup I guess right?
Click to expand...
Click to collapse
Samsung is really good about having odin flashable packages available so if there is issues you can always restore via download mode (never heard of a permanent soft brick in years for a Samsung device)
jaykoerner said:
Samsung is really good about having odin flashable packages available so if there is issues you can always restore via download mode (never heard of a permanent soft brick in years for a Samsung device)
Click to expand...
Click to collapse
Do you know where I'd get one of these packages just in case?
I've used the first site not the second, sammobile is trustworthy. The other is for redundancy.
http://www.sammobile.com/firmwares/database/SM-T580/
http://samsung-updates.com/device/?id=SM-T580
Also recovery and stock firmware is on xda, somewhere it's just hard to find since this device doesn't have a forum.
jaykoerner said:
I've used the first site not the second, sammobile is trustworthy. The other is for redundancy.
http://www.sammobile.com/firmwares/database/SM-T580/
http://samsung-updates.com/device/?id=SM-T580
Also recovery and stock firmware is on xda, somewhere it's just hard to find since this device doesn't have a forum.
Click to expand...
Click to collapse
What's with all the countries? What would I choose for North America?
UntouchedWagons said:
What's with all the countries? What would I choose for North America?
Click to expand...
Click to collapse
Yes, but the only real reason is so the device has the correct language settings. They should all be compatible but if you choose your region you don't have to worry.
Step 8 says to download the tar file in the AP slot, but the download page for TWRP is an img file, do I just tar the image using 7zip?
UntouchedWagons said:
Step 8 says to download the tar file in the AP slot, but the download page for TWRP is an img file, do I just tar the image using 7zip?
Click to expand...
Click to collapse
You'll find the link for the tar file in the OP (Temporary Download).
Team Win Recovery Project 3.0.2-0
This is for the SM-P580 (gtanotexlwifi) and SM-P585, SM-P585N0, SM-P585M, SM-P585Y (gtanotexllte) Exynos models only! Do not flash on other models!
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 Tab A 10.1 (2016) 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:
WiFi version: http://teamw.in/devices/samsunggalaxytaba101wifi2016spen.html
LTE version: http://teamw.in/devices/samsunggalaxytaba101lte2016spen.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 a link to Samsung's Mobile drivers page here:
https://build.nethunter.com.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.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
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 gtanotexlwifi (WiFi) or gtanotexllte (LTE).
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 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 6.
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.
--- or (not both) ---
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force 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.
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 (WiFi): https://github.com/TeamWin/android_device_samsung_gtanotexlwifi (android-6.0)
Device tree (LTE): https://github.com/TeamWin/android_device_samsung_gtanotexllte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
It's possible to use this metod with T585 ?
Working very well on my tab A 10.1 P585Y.. bug.. cant read internal storage but it can use sd card..
I already root my tab a 10.1 p585y using this twrp.. thanks for making this recovery for our p585y.. now we need custom rom such as resurrection remix..
Worked well
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
Im using p585y version.. same here i didnt find any firmware on internet.. so my solution is using kies.. just install kies and recover it.. work for me.. right now sammobile also doesnt have the firmware yet..
Hope im helping.. press thanks if im help..
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
Will try it bro.. right now im using s7 mod on p585y but doesnt show on settings>storage but it seem working background..
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
cliemonster said:
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Click to expand...
Click to collapse
It is not your system - I had the same issue with the swipe bar. Like you, I tried several times and it finally accepted the swipe (even the pen had a few non-registering swipes).
Hi, can you plz update the links. Cuz idlekernel.com is currently not reachable nor the page of your source code for kernels :-/
And I remain highly unclear if I need a kernel for this dm-verity thing or not. I don't understand the issue reg. system boot partion. What is this? Android is already installed on the TabA - so what should I change there? Or is it for root apps?
If you want to root your tab and install TWRP you need the Kernal to turn off dm-verify and encryption. Do it in the exact order in the OP and don't let your tab try to boot rooted without turning off dm-verify.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
I think you'll find it does. Works on pretty much any Samsung device running Marshmallow.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
focus-pocus said:
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
Click to expand...
Click to collapse
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
BohArie said:
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
Click to expand...
Click to collapse
Restore your stock boot image. Apply the patch. Format your SD card as portable storage, reboot.
Look out in status bar for an SD card notification.
If you don't see it go to settings>storage. Tap the SD card choose format then internal.
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
BohArie said:
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
Click to expand...
Click to collapse
Take that with a pinch of salt. Make sure you migrate your data to the sdcard.
focus-pocus said:
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
Click to expand...
Click to collapse
Could you tell me what your baseband version / build number is? I might try flashing one of the other region's ROMs since there's a few from Hong Kong, Turkey, etc out on Updato
soft bricked device,
i soft bricked my device trying to do the TWRP recovery and it kept saying unable to mount data so i factory reset and it still didnt work so then i wiped a bunch of stuff and now it's soft bricked.
im going to download the Korean Firmware for this device, but is there anyway i can avoid that? any tips?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note8 ExynosOnly for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote8.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_greatlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
No Download. Img file?
corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?
Found and is working Thx!...
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.
Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?
Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.
@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.
Good job mate :good:
Really glad we have this dev around. Will flash shortly
{
"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"
}
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this low-cost tablet. My thanks to @mehanik6 for blazing this trail on 4PDA.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.7.0_11-0-T290XXU3CVG3-20221120.tar.md5
twrp-3.7.0_11-0-T290XXU3CVG3-20221120.img
Build Archives:
Android File Host
Change Log:
v3.7.0_11-0: (2022-11-20)
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to T290XXU3CVG3 OEM stock kernel.
v3.6.1_11-0: (2022-03-27)
Updated to TWRP 3.6.1 release built from AOSP-11 branch.
Updated to T290XXU3CUK4 OEM stock kernel.
Using FFS MTP so that custom kernel builds are no longer necessary.
v3.6.0_11-1: (2022-02-20)
Added wipeingui for ext4 partitions.
v3.6.0_11-0: (2022-01-23)
Updated to TWRP 3.6.0 release built from AOSP-11 branch.
v3.5.2_9-0: (2021-10-17)
Updated to T290XXU3CUG4 posted kernel source.
v3.5.2_9-0: (2021-05-16)
Updated to T290XXU3BUC1 posted kernel source.
Updated to TWRP 3.5.2 release built from android-9.0 branch.
v3.5.1_9-0: (2021-03-30)
Updated to T290XXU3BUB2 posted kernel source.
Updated to TWRP 3.5.1 release built from android-9.0 branch.
v3.5.0_9-0: (2021-01-02)
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
v3.4.0-1: (2000-12-09)
New custom T290XXS3ATC1 kernel that actually fixes MTP support.
v3.4.0-0: (2000-12-04)
Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.
v3.4.0-0:
Initial release based on @mehanik6's device tree and T290UES3ATC1 kernel.
Fixed MTP
Default language is now English
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler that preserves encryption from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gtowifi
Donations:
Your support is always appreciated! Just click here.
are there any custom roms for sm-t290?
Tralien said:
are there any custom roms for sm-t290?
Click to expand...
Click to collapse
I'll have a release of my Nexus Stock custom ROM shortly. It's basically the same as what I've been releasing for the 10.1" version of this tablet over the past year. I'm basically just waiting for Samsung to post the latest kernel source.
Update for TWRP v3.5.0 release...
Downloads:
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img
Change Log:
v3.5.0_9-0:
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?
dark_friend said:
I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?
Click to expand...
Click to collapse
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Magendanz said:
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Click to expand...
Click to collapse
Got it! thank you very much!
Magendanz said:
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Click to expand...
Click to collapse
Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)
Heeni said:
Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)
Click to expand...
Click to collapse
If you miss, hold Power + Vol Down for 7 seconds during the boot animation to do a hard reset and try again. Alternatively, you can wait for it to finish booting and then restart, but then you risk Samsung's VaultKeeper "feature" putting the bootloader into a stealth locked state. You can prevent that by connecting to the Internet, enabling Developer Options, and then confirming the OEM Unlocking state as soon as you finish setup. (You don't need to log into Google or Samsung services for Vaultkeeper to maintain the bootloader unlock, but you've got to have Internet access and reenable Developer Options right away.)
Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.
Heeni said:
Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.
Click to expand...
Click to collapse
Yeah, it never ceases to amaze me how Samsung believes it's adding value with Knox security features like Vaultkeeper and its special Download mode that only works with Odin. My main phone is a Pixel 4a, and I've never felt that Google has taken any flak for making bootloader unlocking and firmware flashing painless. Why does Samsung feel the need to reinvent the wheel?
Somewhat to my surprise, I was able to get TWRP installed and boot into it on the first try. In fact, the biggest difficulty by far was getting Samsung drivers to work in my Windows 10 vm. The vm is still having problems, so hopefully, now that TWRP is installed, I won't need to use Odin for a while.
Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.
I think I can live without root much more easily than without wifi!
Heeni said:
Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.
I think I can live without root much more easily than without wifi!
Click to expand...
Click to collapse
I have root and wifi, but didn't use the TWRP install method
Further to this post about the inability to set a password, PIN or pattern:
I reflashed the stock ROM and I can verify the following:-
Stock ROM with (or without) bootloader unlocked will allow me to set up a PIN (I didn't try the other options but would expect that they'd work.
As soon as I install TWRP, the stock ROM will no longer allow me to set up a PIN. I can have "swipe" or "nothing" to unlock, and that's it.
I've tried installing LineageOS 17 GSI, LineageOS 18 GSI and Magendanz's Nexus stock ROM. None of these will accept a PIN, password or pattern.
Therefore, I think that the issue has to do with TWRP, or possibly with something in the multidisabler script.
Googling has come up with nothing other than the instruction to remove /data/system/locksettings.db and related files. I've tried this numerous times without success. I've even tried comparing permissions and ownership with the (working) equivalent on my Moto phones, with no luck.
I'm happy to do any tests, provide logs etc if it would help. The only other alternative seems to be to revert to stock if I need to travel.
I'm going to be using the table in an install that does not allow easy access to be able to use the physical buttons, if I lock the boot loader back after all this will it keep root?
I need root so that I can modify the files necessary to make the tablet turn on automatically whenever power is connected.
New release posted...
Downloads:
twrp-3.5.1_9-0-T290XXU3BUB2-20210330.tar.md5
twrp-3.5.1_9-0-T290XXU3BUB2-20210330.img
Change Log:
v3.5.1_9-0: (2021-03-30)
Updated to T290XXU3BUB2 posted kernel source.
Updated to TWRP 3.5.1 release built from android-9.0 branch.
Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?
Heeni said:
Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?
Click to expand...
Click to collapse
You can just flash the new .img file from an existing TWRP install. The version of the kernel is only important if you're using Magisk (which boots through the recovery partition).
Thanks. That was easy. As far as I can tell at this point, it all works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
BUGS:
You tell me.
FLASHING INSTRUCTIONS:
fastboot erase recovery
fastboot flash recovery twrp-3.x.x-x-togari.img
Click to expand...
Click to collapse
Changelogs:
2022/12/13
Updated to TWRP 3.7.0.
2021/10/03
Fixed SONY boot logo.
2021/09/24
Fixed touch issues.
Click to expand...
Click to collapse
CREDITS:
@ 115ek on Github for his amami base trees.
SOURCE CODE:
device-tree: LINK
DOWNLOADS:
DOWNLOAD
On C6802 3g model, There is no recovery partition. Only boot and FOTAkernel partitions. So I got boot into this recovery by "fastboot boot twrp-3.5.2_9-0-togari.img". Touchscreen not works. Seems adb working but have no idea what should I do.
Bikkoism said:
On C6802 3g model, There is no recovery partition. Only boot and FOTAkernel partitions. So I got boot into this recovery by "fastboot boot twrp-3.5.2_9-0-togari.img". Touchscreen not works. Seems adb working but have no idea what should I do.
Click to expand...
Click to collapse
Thanks for reporting, but since i don't have this device in hand so i can't really debugging with the touch issues, can you grab dmesg from adb for me?
tarkzim said:
Thanks for reporting, but since i don't have this device in hand so i can't really debugging with the touch issues, can you grab dmesg from adb for me?
Click to expand...
Click to collapse
Something more serious problem is going here. After boot into your twrp once, and then reboot to system by adb reboot, My device stuck at bootloop. At last, after factory reset(Originally installed bootstrap recovery), my device got blackscreen bricked. I need to handle this problem first.
Edit: My device can not boot into system now but I could managed get into your twrp again. So I attached dmesg file. https://www.mediafire.com/file/tassxmx7fac9qwm/dmesg.txt/file
Bikkoism said:
Something more serious problem is going here. After boot into your twrp once, and then reboot to system by adb reboot, My device stuck at bootloop. At last, after factory reset(Originally installed bootstrap recovery), my device got blackscreen bricked. I need to handle this problem first.
Click to expand...
Click to collapse
Damn it... sound not good bro,
I found a scripts in XDA for fixing touch issues, maybe i can integrate it into my TWRP...
Bikkoism said:
Edit: My device can not boot into system now but I could managed get into your twrp again. So I attached dmesg file. https://www.mediafire.com/file/tassxmx7fac9qwm/dmesg.txt/file
Click to expand...
Click to collapse
Thanks for your dmesg logs, it seems like the driver was loading fine, i will see what i can do.
BTW, for your current ROM, maybe you should try to flash the boot.img of it again?
tarkzim said:
Thanks for your dmesg logs, it seems like the driver was loading fine, i will see what i can do.
BTW, for your current ROM, maybe you should try to flash the boot.img of it again?
Click to expand...
Click to collapse
I flashed stock 14.6.A.1.236 customized US to unbrick. Fortunately It revived.
If you mean that I should flash your twrp on boot partition, It also not fix touchscreen issue. Here is the log when your twrp actually flashed on the device.
Bikkoism said:
I flashed stock 14.6.A.1.236 customized US to unbrick. Fortunately It revived.
If you mean that I should flash your twrp on boot partition, It also not fix touchscreen issue. Here is the log when your twrp actually flashed on the device.
Click to expand...
Click to collapse
Oh that's not what i mean, but glad you unbricked it.
I will try to include a fix for touchscreen and upload it again, thanks.
New build released - 2021/09/24
Fixed touch issues.
New build released - 2021/10/03
Fixed SONY boot logo.
on my device C6833 is replaced LCD screen. try flash your recovery and system but touch not works. on stock rom 5.1.1 touch works. Its posible get working touch screen on device with replaced screen?
thanks
kluknawa235 said:
on my device C6833 is replaced LCD screen. try flash your recovery and system but touch not works. on stock rom 5.1.1 touch works. Its posible get working touch screen on device with replaced screen?
thanks
Click to expand...
Click to collapse
Actually all supported touch screen firmwares were already included in both of my recovery and ROM, and those are extracted from STOCK ROMs, so it shouldn't happen...
Do you have your C6833 stock rom backup file that i can take a look?
tarkzim said:
Actually all supported touch screen firmwares were already included in both of my recovery and ROM, and those are extracted from STOCK ROMs, so it shouldn't happen...
Do you have your C6833 stock rom backup file that i can take a look?
Click to expand...
Click to collapse
HERE is twrp backup stock rom. I use hot boot kernel with twrp 2.7.0.0. this recovery works good. on my device.
firmware version is 14.6.A.1.236_R2D android 5.1.1. all is included in mega folder.
Another twrp 3.0.0.0 and android 7.1.2 roms work for first time. but if screen is turn off and then i turn on touch not work. or if device is rebooted. I must completly turn off device and then turn on. thed touch works.
after replace device screen now works only stock rom
kluknawa235 said:
HERE is twrp backup stock rom. I use hot boot kernel with twrp 2.7.0.0. this recovery works good. on my device.
firmware version is 14.6.A.1.236_R2D android 5.1.1. all is included in mega folder.
Another twrp 3.0.0.0 and android 7.1.2 roms work for first time. but if screen is turn off and then i turn on touch not work. or if device is rebooted. I must completly turn off device and then turn on. thed touch works.
after replace device screen now works only stock rom
Click to expand...
Click to collapse
Can you try this TWRP image? (See attachment)
i try but touch not work. only OTG
kluknawa235 said:
i try but touch not work. only OTG
Click to expand...
Click to collapse
Try this one instead.
tarkzim said:
Try this one instead.
Click to expand...
Click to collapse
Same. As older recocery. Not works
kluknawa235 said:
Same. As older recocery. Not works
Click to expand...
Click to collapse
Well, I have no idea then...
Because I've already included the firmware update scripts from stock with stock binaries.
Can't help with your replaced touch panel for now, sorry.
Its ok. Thanks for your time
I just restored my XZU from a soft brick. Does the touch screen work with this version of TWRP?