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.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP for Shield Portable, Tool/Utility for the Nvidia Shield
Contributors
Steel01
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Created 2016-06-01
Last Updated 2016-05-31
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Steel01 said:
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Click to expand...
Click to collapse
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
r3pwn said:
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
Click to expand...
Click to collapse
Yeah, the only thing that changes is the aspect ratio, not the orientation.
Thank you! Thank you!
Just updated to 110, and installed TWRP you posted. All went perfect.
Just FYI, sometimes when I flash a new TWRP recovery, it doesn't take the first time, so I just flash it a few times, then test to see if it took, if it didn't take, I flash a few times more until it finally flashes.
Is there a specific key combo you can use to go right into recovery? Right now, I boot into the bootloader by pressing and holding the back, home and nvidia buttons till it boots into the bootloader, then I select recovery to go into TWRP. Just wanted to know if there's was a key combo to go directly into recovery.
Thanks again for providing and posting the latest TWRP for the Portable!!
Hello, quick question. I have a previous version of TWRP installed and want to update to the new one.
Is it possible to apply the OTA to 110 with this TWRP or do I need the stock bootloader?
If I need the stock one, does anyone have a link to it? I didn't make a backup, unfortunately
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Steel01 said:
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Click to expand...
Click to collapse
Ah, I didn't know nvidia published those files like that. That's actually really great!
I'm all up to date now, including the latest TWRP
Hmm I tried TWRP 3.1 from the TWRP website and the touch interface doesn't work. Also, 3.0.2 seems to have problems mounting and wiping data?
Meh, okay. I saw a similar touch problem on a local twrp build. I've requested that the build be removed from the official site. I'll look into the problem when I have time.
Haven't had any trouble on 3.0.2 myself. Did you enable encryption or adopted storage in your ROM?
Great, thanks!
I didn't enable encryption, and it was the latest stock rom. I'm not really sure what happened. It just seemed to be having trouble mounting and wiping a few partitions on the stock system rom, so I flashed the 3.0.0.0 TWRP from the multirom. I seem to recall that having issues wiping too though. However, now that I've flashed LineageOS onto the system partition, I don't get any errors with 3.0.0.0 anymore. I haven't updated to 3.0.2.0 to see if the errors are gone in that build (nor do I want to wipe anything at this point).
As I wrote in the LineageOS thread, I had the same problem with touchscreen. I was hoping to solve the non working touchscreen problem during Aroma OpenGapps install.. is there any hope it gets solved? I think it would be very useful to be able to choose exactly what to install on the Shield, considering its little system partition.
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
astuermer said:
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
Click to expand...
Click to collapse
I too have this issue. Seems they messed up screen as portrait mode.
I see the problem with touch on the newer builds. Would have sworn I had at least one of those removed due to issue, but it apparently came back. Looking into updating all the internal files for 7.1. Working on testing and fixing that right now. The problem is that the touch screen userspace is trying to start before selinux is set to permissive by twrp. So, I have to make sure everything is labelled correctly and that's causing issues. If I'm lucky, I'll be uploading a test build later today. But as with all this type of work, I can't 100% guarantee anything.
astuermer said:
Landscape would be nice.
Click to expand...
Click to collapse
The rotation code no longer exists, it was deemed too slow and hacky. I have to set it up in portrait or not at all, unfortunately.
Edit:
So, not having much luck with making it play nice on default settings. Here's a build with selinux explicitly disabled and touch works as expected. As I have time, I will continue to work on this and get it upstreamed. For the moment, use this 3.1.1 build.
twrp-3.1.1-0-unofficial-roth.img
Finally got around to pushing updates to official twrp. So if you've had issues in the past, please try again. Should be easier to test and fix stuff now that I've got all that pushed.
Side Note: This is fully a 7.1.1 recovery and build. Blasted recovery from N works better than the roms themselves...
Some updates have been pushed for this. 3.2.1.0 has been release as of a few hours ago. If any issues are found, please report.
When trying to flash the 2018-02-11 LineageOS nightly with 3.2.1.0, I get the following error;
Code:
Updating partition details...
...done
Full SELinux support is present.
Installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Checking for digest file...
Skipping Digest check: no Digest file found
Verifying zip signature...
Zip signature verified successfully,
[B]This package is for device: roth; this device is .[/B]
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Updating partition details...
...done
The flash does not proceed beyond this point - apparently can't identify the device type (see bolded text above). If I repeat the process using version 3.1.1-2 or version 3.0.2.0 it works fine, though.
Let me know if you'd like me to pull any logs etc
Related
Hi All / @bauner,
Does anyone know if there is a TWRP 2.8.7.0 or TWRP 3.0.2.1 available for our Note, that works in Android 4.4.4 (KitKat)?
I've found a TWRP 2.8.7.0 and a TWRP 3.0.2 which I believe @bauner very kindly wrapped up for us, to flash in ISORec. However when I flash 2.8.7.0 it shows as 2.8.1.0 when inside recovery.
I'm not sure if this has anything to do with ISORec, still trying to get my head around that. I understand that it separates the Recovery from the Kernel. But not sure if ISORec is supported on Android 4.4.4 (KitKat) ?
- when I flash 2.8.7.0 on KitKat, and then boot into Recovery, it shows up as 2.8.1.0?
Do those ISORec Recoveries look for a certain API / (SDK?) build of Android, and if it doesn't detect required version it doesn't flash?
I really need to get either 2.8.7.0 or 3.0.2.1 in order for Lanchon Re-Pit program to work... and happy with my build of KitKat until a stable Android 7.0 is out....
Cheers, Lister
Lister Of Smeg said:
Hi All / @bauner,
Does anyone know if there is a TWRP 2.8.7.0 or TWRP 3.0.2.1 available for our Note, that works in Android 4.4.4 (KitKat)?
I've found a TWRP 2.8.7.0 and a TWRP 3.0.2 which I believe @bauner very kindly wrapped up for us, to flash in ISORec. However when I flash 2.8.7.0 it shows as 2.8.1.0 when inside recovery.
I'm not sure if this has anything to do with ISORec, still trying to get my head around that. I understand that it separates the Recovery from the Kernel. But not sure if ISORec is supported on Android 4.4.4 (KitKat) ?
- when I flash 2.8.7.0 on KitKat, and then boot into Recovery, it shows up as 2.8.1.0?
Do those ISORec Recoveries look for a certain API / (SDK?) build of Android, and if it doesn't detect required version it doesn't flash?
I really need to get either 2.8.7.0 or 3.0.2.1 in order for Lanchon Re-Pit program to work... and happy with my build of KitKat until a stable Android 7.0 is out....
Cheers, Lister
Click to expand...
Click to collapse
In official cm11 the isorec recovery should work in builds after Mar 25, 2016.
If you don't use official cm11 then maybe the twrp 2.8.1.0 is the default recovery which is included in the kernel.
Maybe repit will also work with the older twrp version.
But make a backup of your rom on the external sdcard and also backup the files from your internal sdcard to your pc if something should go wrong
Hi @bauner,
First of all, thanks for the prompt reply... and apologies my delayed response back... Work has been a nightmare, been nearly a week Ive been trying to find time to sort phone out, backup data and so on... anyway....
Thanks for the sound advice, my Android 4.4.4 rom is sadly very out of date, as I was using the much loved Dirty Unicorn 8.2 (which hadn't been updated since sometime around 2015) and so therefore certainly didn't have ISORec support, if it at all??? I didn't go down the stock CM11 route, as I loved the tweaks that were in DU.
RePit may of worked, as it bawked out a couple of times, and couple of different errors. But my main error, which took some getting around... Was files and filesystem. It appeared a file got corrupt on the internal SD, and therefore could not be copied or removed. I eventually had to WIPE the partition completely (after copying what I could).
Bit the bullet, and upgraded to your great CM13 build as of now... I'm not a fan of Googles latest Material Design feel, and much prefered the retro (more colourful / 3D icons) of the older Android, ie: KitKat... that appears to have more features available to that OS. It appears no LP / MM / N have the kinda tweakability of yester-year roms.
Upgraded, RePit'd and got 1.5GB System, 6GB Data, and whatever is left (7GB) for internal SD Card. So I THANK YOU BAUNER for your advice, I'm all sorted now...
I'm prolly gonna stick with your CM13 / MM build now, until CM14 / N is stable (this is not a push or ETA... I appreciate your VAST EFFORTS and it's ready when its ready!!!) as I've found Apps that cater for bits from old OS, such as "Driving Mode" where it had built in TTS that would announce SMS / Incoming Calls, and other notifications. And various other visual elements...
Is it possible to restore a backup from a different partition table. Will it just fill those partitions with the data, or do you think it would look for the same size partitions and as they've increased, will fail to restore...
Cheers, Lister
bauner said:
In official cm11 the isorec recovery should work in builds after Mar 25, 2016.
If you don't use official cm11 then maybe the twrp 2.8.1.0 is the default recovery which is included in the kernel.
Maybe repit will also work with the older twrp version.
But make a backup of your rom on the external sdcard and also backup the files from your internal sdcard to your pc if something should go wrong
Click to expand...
Click to collapse
Lister Of Smeg said:
...
Is it possible to restore a backup from a different partition table. Will it just fill those partitions with the data, or do you think it would look for the same size partitions and as they've increased, will fail to restore...
Cheers, Lister
Click to expand...
Click to collapse
You can restore your backup without problems. It will not change the new partition sizes
What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020
temp
Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English
Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.
so everything good other than Android Auto? Well done!
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.
How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:
..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?
Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.
Great, glad all went good for you
Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse
Great work! ROM works great, even Google pay is working good!
I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel
Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!
oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse
Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.
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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 6 that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_oneplus_enchilada
https://github.com/TeamWin/android_device_oneplus_sdm845-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus6.html
Can anyone confirm if it work with the enchilada hotfix update for OOS 11 OB1?
Edit: Nope! Qualcomm Crashdump all the way
does not work. crash_dump. If repackaged with a stock kernel, it hangs on the TWRP logo.
Soft_M said:
does not work. crash_dump. If repackaged with a stock kernel, it hangs on the TWRP logo.
Click to expand...
Click to collapse
The kernel I'm using is Q based as that's the stable one, can you get logs after repacking with stock?
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Nebrassy said:
The kernel I'm using is Q based as that's the stable one, can you get logs after repacking with stock?
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
For me this is a mystery, but now I repackaged it again with the stock kernel, and it started correctly.
Soft_M said:
For me this is a mystery, but now I repackaged it again with the stock kernel, and it started correctly.
Click to expand...
Click to collapse
cool,not much can be done right now though, as the android 11 kernel sources haven't been published yet for custom kernels to integrate what they did, and I nee to modify the kernel for fastboot boot to work, so consider this TWRP for stock 10 and customs, it's working on custom 11 roms
Maby remove the link or hole posted , because now people get crash dump error and that can't be good
NLhardcore said:
Maby remove the link or hole posted , because now people get crash dump error and that can't be good
Click to expand...
Click to collapse
this is for custom roms currently, not for stock 11
anyone can test on latest beta?, join the tg group
uploaded new build supporting stock android 11
Nebrassy said:
uploaded new build supporting stock android 11
Click to expand...
Click to collapse
bro i, we, love you, you just saved my life now, im testing it and i will try to flash something, last build is working but boot only didnt flash it yet, but seems working good, anyway super thx for your work <3
edit 1 : i just flashed a file, flashed without any problem
edit 2 : i flashed current twrp, working good <3
edit 3 :
i tell you guys, this TWRP working PERFTECT for ONEPLUS 6 ANDROID 11 STABLE
data decryption works?
CYB3R0ID694 said:
data decryption works?
Click to expand...
Click to collapse
i dont know what u mean bro, but i have password on my device and twrp asked me for it and i use it to unlock twrp, i think this is ur question? sorry for bad english
Evon88 said:
bro i, we, love you, you just saved my life now, im testing it and i will try to flash something, last build is working but boot only didnt flash it yet, but seems working good, anyway super thx for your work <3
edit 1 : i just flashed a file, flashed without any problem
edit 2 : i flashed current twrp, working good <3
edit 3 :
i tell you guys, this TWRP working PERFTECT for ONEPLUS 6 ANDROID 11 STABLE
Click to expand...
Click to collapse
How do I root after this? can I directly install magisk zip or is it not supported yet?
Nitesh Gohil said:
How do I root after this? can I directly install magisk zip or is it not supported yet?
Click to expand...
Click to collapse
i was hava a problem with my root, i installed GPU Booster and its bootloop ( before TWRP ) so i installed official boot.img again, and i was trying to root again with patched boot.img its bootloop again so i flashed official boot.img again and my phone start working normal,
AFTER TWRP, i FLASHED magisk uninstaller and boot to sys, work 100%
reboot to TWRP and install MAGISK installer and flashed 100%
now im rooted by TWRP
sorry for saying all this but just to make u sure that i FLASHED uninstaller once, and installer and working super fine
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Evon88 said:
i was hava a problem with my root, i installed GPU Booster and its bootloop ( before TWRP ) so i installed official boot.img again, and i was trying to root again with patched boot.img its bootloop again so i flashed official boot.img again and my phone start working normal,
AFTER TWRP, i FLASHED magisk uninstaller and boot to sys, work 100%
reboot to TWRP and install MAGISK installer and flashed 100%
now im rooted by TWRP
sorry for saying all this but just to make u sure that i FLASHED uninstaller once, and installer and working super fine
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Click to expand...
Click to collapse
Thanks! I just flashed magisk zip directly and I can confirm it's working without any hiccups
Evon88 said:
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Click to expand...
Click to collapse
Battery calibration apps don't do anything that any android rom couldn't do. What those apps do is reset your battery stats. But every time your phone is charged to 100% and you unplug it, your battery stats get automatically reset.
Any chance for 6t build?
Moe2003 said:
Any chance for 6t build?
Click to expand...
Click to collapse
same build should boot on 6t
Siddk said:
same build should boot on 6t
Click to expand...
Click to collapse
if thats true then why is there a 6t and 6 twrp separate?
I saw old guide but guy who made this can't help me because he not have this phone I need to find dm-verify disabler and other files to root my motoG6 but what to do if i get into a bootloop?
Will I be able to install android via Smart Assistant after doing the wipe? (if I broke something)
Someone know how can I make copy for my apps and data? I have mutch modded apk.
i know what adb is for but i don't know kommend anyone can help with root?
XWacoX said:
I saw old guide but guy who made this can't help me because he not have this phone I need to find dm-verify disabler and other files to root my motoG6 but what to do if i get into a bootloop?
Will I be able to install android via Smart Assistant after doing the wipe? (if I broke something)
Someone know how can I make copy for my apps and data? I have mutch modded apk.
i know what adb is for but i don't know kommend anyone can help with root?
Click to expand...
Click to collapse
I used:
https://forum.xda-developers.com/t/guide-root-moto-g6-ali-twrp-root-and-magisk-installation-guide.3816569/page-41.
It worked out well. As long as you have TWRP, you should be able to recover from bootloops.
HDXKohl said:
I used:
https://forum.xda-developers.com/t/guide-root-moto-g6-ali-twrp-root-and-magisk-installation-guide.3816569/page-41.
It worked out well. As long as you have TWRP, you should be able to recover from bootloops.
Click to expand...
Click to collapse
page not found ( (sorry is my second acc I can't log in to my main acc)
RogalDDL said:
page not found ( (sorry is my second acc I can't log in to my main acc)
Click to expand...
Click to collapse
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
HDXKohl said:
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
Click to expand...
Click to collapse
ok I will try tomorrow.
HDXKohl said:
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
Click to expand...
Click to collapse
there is problem I downloaded twrp-3.5.2_9-0-ali.img but it stuck at twrp logo it only responds to vol + power but after that it starts to turn on the system. I using Windows 8.1 v. 6.3.9600. So why it not working???
When I turn on rebbot recovery I got stock recovery not twrp.
HDXKohl said:
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
Click to expand...
Click to collapse
hey dude next problem after install magisk I CAN'T BOOT INTO SYSTEM
RogalDDL said:
there is problem I downloaded twrp-3.5.2_9-0-ali.img but it stuck at twrp logo it only responds to vol + power but after that it starts to turn on the system. I using Windows 8.1 v. 6.3.9600. So why it not working???
When I turn on rebbot recovery I got stock recovery not twrp.
Click to expand...
Click to collapse
Which img did you use? I used:
[TWRP][UNOFFICIAL] TWRP 64 bit for ALI
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...
forum.xda-developers.com
Here's a newer one:
[TWRP][UNOFFICIAL] TWRP [64 Bit][3.7.0]
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...
forum.xda-developers.com
I have not used it before. I am by no means a pro at this, so maybe try looking around.
RogalDDL said:
hey dude next problem after install magisk I CAN'T BOOT INTO SYSTEM
Click to expand...
Click to collapse
How did you install? A lot of older guides say to flash magisk, but I did it through the apk, as that's what magisk recommends.
Also did you get recovery to work. From my experience, it's generally not good to proceed without recovery, as it is harder to recover from boot loops and other issues.
HDXKohl said:
How did you install? A lot of older guides say to flash magisk, but I did it through the apk, as that's what magisk recommends.
Also did you get recovery to work. From my experience, it's generally not good to proceed without recovery, as it is harder to recover from boot loops and other issues.
Click to expand...
Click to collapse
I had a copy of the system previously made, but after rebooting into the system it only turned on twrp, I had to upload the firmware again via smart assistant. First I did a wipe, then I installed no verify and magisk but later it did not boot system but it returned to twrp. I searched 1000 pages for .img to moto g6 android 9.0 Is it possible to downgrade to android 8.0 without root? I have no idea how to root on this anymore. my model is XT1925-5.
PLEASE BEFORE YOU decide to try this recovery, you MUST read all of post 1 and 2 (about 3 minute read). If you think this is an unreasonable request, then stop reading now and find another recovery. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this software.
BACKUP YOUR DATA BEFORE trying this TWRP.
Source code
Kernel source
https://github.com/retiredtab/android_kernel_samsung_universal5433
Device tree
https://github.com/retiredtab/TWRP_gts28wifi/tree/main/gts28wifi
TWRP source code (built using minimal manifest TWRP 7.1)
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Download TWRP from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/
Installation Instructions
You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP.
Note I do NOT run Windows OS so there are no provided instructions on how to install TWRP using Windows. There's lots of tutorials and videos online on how to install TWRP via Windows. Do your own research. If this is unreasonable to you, don't use this TWRP. Questions regarding how to install TWRP using Windows/odin will go unanswered.
You need to boot the T710 into download mode. Power off. Press home button + power + volume down (farthest away from power button) at the same time. Let go when you see "Warning" text on the screen, then choose volume up to continue. Your screen should now show "Downloading... Do not turn off target"
Linux users can use heimdall to flash this recovery. For example,
Code:
heimdall flash --RECOVERY TWRP_3.5.2_9_SM-T710_20210719_Unofficial.img
After flashing the recovery image, you must boot into recovery immediately (using the hardware key combination) to run TWRP, otherwise the Samsung software will overwrite TWRP and you will have to start over again. I usually am already pressing the recovery hardware key combination while the recovery image is being flashed. The flash process will be very quick (a few seconds at most).
The recovery hardware key combination is home button + power + volume up (volume up is closest to the power button) all pressed at the same time.
Updates
Unless Android 12 or LineageOS 19.0 requires some mandatory changes to TWRP, this will be the only TWRP build I make for the forseeable future. There will be no planned updates to 3.5 unless there's a major bug or security vulnerability. The only time you need to boot into TWRP is to upgrade the custom rom.
I have been using this TWRP since Aug 19, 2021.
The "official" TWRP T710 ALL have broken MTP and adb in every version which is why I built my own despite reporting these problems to the maintainer.
Reserved.
Thank you so much for this! I teared my hair out for many, many hours thinking I had issues with drivers on my PC why adb or MTP never worked in every official TWRP release I've tried... I thought I'd give yours a try and voila! It works! Beautifully so.
Thank you, thank you, thank you!
Whenever i flash this specific build of TWRP my tab instantly bootloops.
cammykool said:
Whenever i flash this specific build of TWRP my tab instantly bootloops.
Click to expand...
Click to collapse
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.
retiredtab said:
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.
Click to expand...
Click to collapse
Sorry. Was a quick type. And I've done a bit more troubleshooting. The older builds with broken MTP seem to boot perfectly. But flashing the build outlined here seems to get the tablet stuck at the Tab S2 screen. The only place it can go is DL. system won't boot again unless I reflash a system image. The tablet was still on a build of 5.1.1 though and I know these modern recoveries probably don't expect that so i am letting it update the stock stuff now.
Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!
cammykool said:
Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!
Click to expand...
Click to collapse
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
retiredtab said:
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
Click to expand...
Click to collapse
Thank you! That was actually the plan! Running it now and posted in the other thread!
Thank you for nice work, I've installed it on my T715, it works very well, just now my device is recognized as T710 too. Could you please provide a build for T715? As the function of adb/mpt doesn't work on all of twrp for T715 too.
Was running LoS 16 and decided to update. Went to stock 7.0 then LoS 18.1 using this version of TWRP without any problems or the issues some other versions of TWRP have! Thanks