Develop Bugs

[RECOVERY][Unofficial][Epic4GTouch] TWRP 2.6.3.0 touch recovery [2014-02-11]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
Latest Builds Here
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, your best bet is to PM me directly, 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.[/QUOTE]

Links are up enjoy the light show
Twrp now has haptic feedback.

Wow...first post. I thought this would explode...Lol.
Great job dev.

Like the haptic... Thanx!
Sent from my SPH-D710

Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.

EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.

HighxVoltage said:
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
Click to expand...
Click to collapse
It works to flash jb+ I first built twrp when I was on stock then I flashed jb and went to 4.4
Sent from my SPH-D710 using Tapatalk

This is a repost of the twrp from a while back right?
sent from tumblr
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
I've used an older version of twrp. I install it through Odin then upgrade to this one.
sent from tumblr

@Linux guy this is a new build hint why it has haptic feedback.
Sent from my SPH-D710 using Tapatalk

Working great on my E4GT. Thanks
☞"And on the eight day the Lord made a backup"☜

Any chance for v2.7.0.0 in the near future?

CrimsonKnight13 said:
Any chance for v2.7.0.0 in the near future?
Click to expand...
Click to collapse
This is 2.7 basically I wait for major changes but probably in a week

Unjustified Dev said:
This is 2.7 basically I wait for major changes but probably in a week
Click to expand...
Click to collapse
Thanks! I look forward to your next release.

Any updates regarding 2.7 being compiled & released?

How does one flash this?
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"

os2baba said:
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
Click to expand...
Click to collapse
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk

dirtyhewr said:
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?

os2baba said:
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
Click to expand...
Click to collapse
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk

Surj138 said:
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.

os2baba said:
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
Click to expand...
Click to collapse
This device is different because the recovery comes bundled with the kernel. This particular recovery is only for kk aosp ROMs... It overwrites the recovery those ROMs come with (CWM).
There are custom kernels for stock ROMs that come with a custom recovery. If you're on stock JB I recommend Agats 1.3
Trolling from my SPH-D710 using Tapatalk

F2FS-enabled Kernel and Recovery for JellyBean ROMs

IF you are expert at ROMs and flashing you may find this helpful. I am really happy with the F2FS Filesystem on my OG Note; I've since bought the 2014 version, yet with F2FS the OG Note feels just as fast now. Samsung has put a lot of work into F2FS and reducing flash-based I/O waits is key for eliminating lag on Android.
I did the JB kernel first 'cause that's the source I had lying around. I'm going to build up a proper kernel source tree for KitKat for my 2014 Note in the next few days, then build one for the KitKat OG Note after that. The F2FS is from the tip of Linus' "master" branch, backported to the 3.0 kernel the OG Note uses.
I'm not going to do any newbie handholding- this is for experienced users- but the general way to use this is:
- Backup anything you'll want to save from your INTERNAL /sdcard, as it will be wiped
- Using an EXISTING TWRP (not the one here), make a backup of your /data (onto an external SD-Card)
- flash this recovery, then boot into it
- Wipe the /cache partition- it will reformat it as an F2FS partition
- "Advanced Wipe" the /data partition- use the "scary" wipe that says you'll lose EVERYTHING
- Do a /data (ONLY!) restore from the backup you'd just made from the previous (non-F2FS) recovery
- Wipe Dalvik Cache
- Shut down and go into Download (Odin) mode
- Flash the boot.img provided (it should work on any recent JB Samsung ROM)
- Reboot
- Restore any Internal /sdcard stuff you'd saved
- Enjoy speedy F2FS goodness (give it a minute after first-time booting so it can settle)
The boot.img is here.
The F2FS-enabled TWRP is here.
You know the rules- despite my testing and use, you may lose data, etc. etc. but if anyone uses this, be sure to let me know if it works for you, and especially if you have any issues with it. I'll put out the source to the kernel in time as well.

I've been thinking about going back to Jellybean, this might be the deciding factor.
Any chance on something for 4.4.4 aosp?

Airtioteclint said:
Any chance on something for 4.4.4 aosp?
Click to expand...
Click to collapse
This is fairly easy to add to any ROM where you've got all the source code (i.e., AOSP and its variants like CM, etc.). I'm pretty sure I won't be making one though, as most non-Samsung ROMs are usually lacking some functionality so I never use one.

Not working on 8013
I followed the instructions, but when I install the recovery, get a boot loop every time. But it was worth a try. Thanks for all your hard work.
:crying:
kcrudup said:
IF you are expert at ROMs and flashing you may find this helpful. I am really happy with the F2FS Filesystem on my OG Note; I've since bought the 2014 version, yet with F2FS the OG Note feels just as fast now. Samsung has put a lot of work into F2FS and reducing flash-based I/O waits is key for eliminating lag on Android.
I did the JB kernel first 'cause that's the source I had lying around. I'm going to build up a proper kernel source tree for KitKat for my 2014 Note in the next few days, then build one for the KitKat OG Note after that. The F2FS is from the tip of Linus' "master" branch, backported to the 3.0 kernel the OG Note uses.
I'm not going to do any newbie handholding- this is for experienced users- but the general way to use this is:
- Backup anything you'll want to save from your INTERNAL /sdcard, as it will be wiped
- Using an EXISTING TWRP (not the one here), make a backup of your /data (onto an external SD-Card)
- flash this recovery, then boot into it
- Wipe the /cache partition- it will reformat it as an F2FS partition
- "Advanced Wipe" the /data partition- use the "scary" wipe that says you'll lose EVERYTHING
- Do a /data (ONLY!) restore from the backup you'd just made from the previous (non-F2FS) recovery
- Wipe Dalvik Cache
- Shut down and go into Download (Odin) mode
- Flash the boot.img provided (it should work on any recent JB Samsung ROM)
- Reboot
- Restore any Internal /sdcard stuff you'd saved
- Enjoy speedy F2FS goodness (give it a minute after first-time booting so it can settle)
The boot.img is here.
The F2FS-enabled TWRP is here.
You know the rules- despite my testing and use, you may lose data, etc. etc. but if anyone uses this, be sure to let me know if it works for you, and especially if you have any issues with it. I'll put out the source to the kernel in time as well.
Click to expand...
Click to collapse

It's probably the overclocking. Let me make up a non-OC set soon.

I just got a Notification from the "PM Bot" about this- if anyone's (still interested in?) using this, let me know.

I'd love to use this if we could get F2FS with CM12! By i presume for jellybean only.

This is cool, as just about everyone else said would be great to see KK support for the GT-N8000 KK ROMs ported to GT-N8013. THANK YOU either way AWESOME WORK!

[GUIDE] How to flash Android 9 Pie (PixelExperience, Havoc OS etc.)

Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):

Don't need to flash p lag fix, volte fix and other stuff?

Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)

bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?

moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.

Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help

moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?

Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.

GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/

sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie

Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.

HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.

Is hotspot working in PIE GSI?

dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!

Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom

it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem

And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?

moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok

expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.

soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on

Full Nandroid Backup Solution for LineageOS 17??

I got Lineage 17 w/ Magisk root running now neat and great and I want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for. Suggestion?
thank you for help!

It is unsafe to perform backups while booted into Android, as files may be changed/added/removed while the backup is taking place.
This is why it tends to be a feature of custom recoveries.
Titanium Backup is good. It doesn't support split APKs like YouTube but the data restore works flawlessly. This is an old utility app so you can trust it with root. You can find Titanium Backup on the play store, it is the one with the star and "root required".
If you want to perform full backups of your PHONE you will want TWRP. If you want to perform full backups of your APPS then you will want to use an app like Titanium Backup (however Titanium Backup is not updated for split APKs, like I said above), which will allow you to transfer your backups to a new phone and fully restore all apps & data (as long as both phones have root).

Sure problem is I want to perform a full backup of my phone, but TWRP ist not available. What are my options?

dadu1257 said:
Sure problem is I want to perform a full backup of my phone, but TWRP ist not available. What are my options?
Click to expand...
Click to collapse
Does TWRP for Pixel 3a XL not work for you? All you have to do is download the "twrp-installer-3.4.0-0-bonito.zip", install it as a Magisk module, then direct install Magisk again, then reboot into recovery and you'll have TWRP.
When accepting OTAs, you will want to use the "TWRP A/B retention script" before you install Magisk to the inactive slot. The script is available as part of the Magisk modules repository, so you should be able to install it directly from within Magisk Manager.

TWRP doesnt work for me, see here what user 41rw4lk wrote, too..
Is there a tutorial on how to install twrp as a masgisk module?
Also, how else can I perform a backup img for my phone?
thank you

dadu1257 said:
TWRP doesnt work for me, see here what user 41rw4lk wrote, too..
Is there a tutorial on how to install twrp as a masgisk module?
Also, how else can I perform a backup img for my phone?
thank you
Click to expand...
Click to collapse
https://puu.sh/GWiul/2611f0cdf4.mp4 - video showing how to install TWRP
Edit: https://puu.sh/GWiAe/6f620419c8.mp4 is more compatible and smaller. same video

.....

LoganDark said:
https://puu.sh/GWiul/2611f0cdf4.mp4 - video showing how to install TWRP
Edit: https://puu.sh/GWiAe/6f620419c8.mp4 is more compatible and smaller. same video
Click to expand...
Click to collapse
Benn trying to get this to work for a little bit now and no luck at all....
Let me start by saying i an NOT running LOS so that might be the whole issue...
I have tried with pure stock and stock with ex kernel
Same results for each
1) TWRP loads as the recovery and can be booted into, BUT the rom is now soft bricked and wont boot at all
2) Even when in twrp I cannot flash anything, cannot see sdcard and cannot backup data partition (the data partition shows as 0 space)
Perhaps the LOS kernel or rom adds something thats missing in my two setups?
The sample video is for another phone. My recolection is that twrp and pixels on android 10 or 11 wont work. Lineageos 17.1 is android 10 based. I think it worked on that other phone as it was not a pixel.
Can anyone confirm or deny if this works in any configuration of android 10 or 11 on our phones?

adm1jtg said:
Benn trying to get this to work for a little bit now and no luck at all....
Let me start by saying i an NOT running LOS so that might be the whole issue...
I have tried with pure stock and stock with ex kernel
Same results for each
1) TWRP loads as the recovery and can be booted into, BUT the rom is now soft bricked and wont boot at all
2) Even when in twrp I cannot flash anything, cannot see sdcard and cannot backup data partition (the data partition shows as 0 space)
Perhaps the LOS kernel or rom adds something thats missing in my two setups?
The sample video is for another phone. My recolection is that twrp and pixels on android 10 or 11 wont work. Lineageos 17.1 is android 10 based. I think it worked on that other phone as it was not a pixel.
Can anyone confirm or deny if this works in any configuration of android 10 or 11 on our phones?
Click to expand...
Click to collapse
Huh, that's weird... I apologize, I'm not very good at supporting devices I don't own. I'm not running Lineage either, I'm running stock plus mods.
It's possible that it doesn't work on your phone for whatever reason. There are a couple ways to install TWRP nowadays, check them out maybe? I promise TWRP is what you want for backups.

LoganDark said:
Huh, that's weird... I apologize, I'm not very good at supporting devices I don't own. I'm not running Lineage either, I'm running stock plus mods.
It's possible that it doesn't work on your phone for whatever reason. There are a couple ways to install TWRP nowadays, check them out maybe? I promise TWRP is what you want for backups.
Click to expand...
Click to collapse
Agreed but twrp simply doesnt work on our phones, or even any pixel 3 or above. It can't read the partitions correctly. Just trying to keep people from soft bricking their phone. Something about andriod 10 and 11 and the phones a/b partition configuration

adm1jtg said:
Agreed but twrp simply doesnt work on our phones, or even any pixel 3 or above. It can't read the partitions correctly.
Click to expand...
Click to collapse
Where did you hear this? I'll admit, I haven't heard about TWRP not working on Pixels, but it's relevant and it would be good to know if I ever help another Pixel user in the future.
adm1jtg said:
Something about andriod 10 and 11 and the phones a/b partition configuration
Click to expand...
Click to collapse
That's interesting, because my OnePlus 7 Pro runs Android 10 with an A/B configuration and TWRP works just fine. Haven't found a single feature that didn't work. Flashing custom ROMs, changing boot slots, etc. all work fine. So it can't be the A/B configuration.

LoganDark said:
Where did you hear this? I'll admit, I haven't heard about TWRP not working on Pixels, but it's relevant and it would be good to know if I ever help another Pixel user in the future.
That's interesting, because my OnePlus 7 Pro runs Android 10 with an A/B configuration and TWRP works just fine. Haven't found a single feature that didn't work. Flashing custom ROMs, changing boot slots, etc. all work fine. So it can't be the A/B configuration.
Click to expand...
Click to collapse
You can read through this:
[CLOSED]TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]
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
And this:
tips for preserving twrp from Pie to Q
hi i'm not an expert so sorry maybe for foolish question but coudn't find a clear answer yet.. i'm still on pie and twrp 3.3.1.1; i'd like to upgade to ten but preserving twrp (maybe upgrading to 3.4.0 if necessary) which are the steps to keep...
forum.xda-developers.com
No method I have tried results in anything but an unusable twrp or a boot loop. Cant even fastboot boot current version. All about dynamic partitions and lzma compression as I guess the partition isnt big enough. But bottom line is I have yet to find anyone including myself who can get twrp to in any way shape or form be usable on our phones for android 10 or newer.
this is what command prompt gives with fastboot boot
Sending 'boot.img' (65536 KB) OKAY [ 1.509s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
This is likely due to the kernels I use likely not having lzma. Checking into it.
fastboot: error: Command failed

LoganDark said:
If you want to perform full backups of your PHONE you will want TWRP
Click to expand...
Click to collapse
I'm not sure how reliable is that. I just did a backup of Lineage 17 in TWRP, System and Data, restored it a few hours later through OTG and it got stuck on a google boot screen... Now I installed the LOS 17 ROM again (which I had in internal storage) but restored only Data (excl. storage).
It boots up now, but most apps are corrupted - if I open them they crash ('App ... keeps stopping').
I wouldn't count on it. TWRP nandroid backup is very unreliable.

Open Gapps size problem

hello, tried to install
LineageOS 18.1​LineageOS 19.0​bother ae to large to allow OPEN Gapps PICO to also be installed
i was able to get it to fit with
LineageOS 16.0 + open gapps pico​
with LineageOS 18.1 it was about 15mb short of space. any ideas how to get around this? and upgrade to 18 nor 19. thanks

It doesn't even fit pico??
Flash the rom, then in twrp go to wipe/format, then go to advanced and select your system partition, then select advanced on that and click resize file system.
If it still won't work and you absolutely NEED lineage 18 or 19, then i guess you could try installing 16+gapps, then dirty flash 17 on top of that, then dirty flash 18, then 19.

PhotonIce said:
It doesn't even fit pico??
Flash the rom, then in twrp go to wipe/format, then go to advanced and select your system partition, then select advanced on that and click resize file system.
If it still won't work and you absolutely NEED lineage 18 or 19, then i guess you could try installing 16+gapps, then dirty flash 17 on top of that, then dirty flash 18, then 19.
Click to expand...
Click to collapse
thanks, but i already tried all that many times. as explained once both are side loaded its short 15mb
is there is any way to skink LineageOS 18.1 or 19 a little ?
when you say dirty flash can you explain more? thanks

Dirty flash means to flash a newer version ontop of an old one, without wiping. Though, that will not work in your situation, my bad.
I guess you could try looking for a rom which takes up less space than lineage, there are many out there.

thanks, but cant find many that support the samsung galaxy 8.0 note tab n5110
i also have little experience to know which roms to trust and what's out there

use litegapps lite:
Get LiteGapps
The LiteGapps Project Official Website
litegapps.github.io
Use arm x32, as you have an armv7 processor. select the correct android version, and download the lite package. Then flash via twrp.

PhotonIce said:
use litegapps lite:
Get LiteGapps
The LiteGapps Project Official Website
litegapps.github.io
Use arm x32, as you have an armv7 processor. select the correct android version, and download the lite package. Then flash via twrp.
Click to expand...
Click to collapse
thanks
i have linageos 16 installed right now
this is the first time i have tried this, could you tell me what is the best way to upgrade now that i have setup the device with all my apps and stuff?
does the twrp backup fully backup everything, how does it work?
if i backup and install linage 19 with litegapps will it restore ok?
are the backup version specific? or rom specific? or device specific?
if for example my device dies can the backup restore to a different device?
thanks

lhedb said:
i have linageos 16 installed right now
this is the first time i have tried this, could you tell me what is the best way to upgrade now that i have setup the device with all my apps and stuff?
Click to expand...
Click to collapse
The best way to upgrade would be to make a full twrp backup, just in case things go sideways, then dirty flash lineage os in the order of android versions. So if you have lineage 16 installed, then flash 17, reboot your device, then flash 18, then reboot, then flash 19 - only wipe cache and dalvik cache between installs, and do not flash gapps. Here's the problem, however. You already mentioned in your first post that lineage 18 and 19 were too big to install with opengapps pico, which means that if you dirty flash and upgrade till 18 or 19, it just wont work as there wont be enough space. Although, this is just a logical assumption, it is also fully possbile that it does work, and you get to use your device. If things go wrong, just restore the TWRP backup.
lhedb said:
does the twrp backup fully backup everything, how does it work?
Click to expand...
Click to collapse
When making your TWRP backup, select all the checkboxes. This will make a complete backup of your device. It will include your entire android system, your settings, apps and data in internal storage, literally EVERYTHING.
lhedb said:
if i backup and install linage 19 with litegapps will it restore ok?
Click to expand...
Click to collapse
It does work like that. The data partition contains all your settings etc, it won't be compatible with lineage 19, and it wont work as opengapps is installed to it. So no, it won't restore ok, don't even bother trying that.
lhedb said:
are the backup version specific? or rom specific? or device specific?
if for example my device dies can the backup restore to a different device?
Click to expand...
Click to collapse
The backup can be restored at any time using twrp. Just as custom roms are device specific, the twrp backup will also be device specific. This means that it will only boot if you restore it to a device with the same model number as yours, whether that be your own tablet, or someone else's.
My recommendation is that you wipe System+Data+Cache+Dalvik, then flash lineage 19, then flash litegapps lite. This will be a clean install, it will help you avoid bugs, and it is probably the best, if not only, way (in your situation). Your photos and videos etc will not be wiped, but you will lose your settings and installed apps. If, for example, it does not install (due to space issues) or you do not like lineage 19, then you can always restore your backup.

thanks for the info,
im just unclear on the backup specifics
did you say the backup wont work if i have gapps? or only if i change versions?
i installed 16 from
Downloads for : Samsung Galaxy Note 8.0 (Tablet) | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
but there is no 17
does that mean i cant flash 18.1 or 19?
and if i have 16 with gapps pico, does that mean it cant upgrade? as i need to flash both packages?
most importantly, if i back up linos16 with gapps pico. does that mean i am stuck with that install type.
will other linage roms work. or only the same coder version?
if i wanted to upgrade to linos19 and litegapps is there any way to keep my current data and apps setup.
thanks again

First things first, before messing with anything, take a TWRP backup (all partitions) onto prefferably an sd card.
Ok, so if you want to try and keep your data and move to lineage 19, then just download 19, boot into twrp, click install, select lineage 19 zip and flash it. Then reboot. If your device boots into lineage 19, then all's good and well, though you may experience some bugs. It is also possible that your device will begin to bootloop, or it just wont install (due to space errors). In this case, you can either restore your lineage 16 backup and stick with that, or you can wipe system+cache+data_dalvik, then flash lineage 19+litegapps lite.
If you have any gapps installed, then when you upgrade by flashign a newer version of android onto the old one, you shouldnt flash new gapps, else it will bootloop. So no, you cant upgrade from lineage 16 opengapps pico to lienage 19 litegapps lite, you can try following my instructions from the first paragraph, which will help you upgrade from lineage 16 pico to lineage 19 pico (both opengapps).
When you backup with TWRP, youre basically jsut picking up all the files in the phone (other than bootloader, but thats not important), and copying it to an sd. When you restore a TWRP backup, then it takes the files from your sd card and copies them back to their designated places on your phone. Taking a twrp backup does not limit anything, it is a passive process, it will nto affect your device in any way. If you backup lineage 16, then you are onyl doing that for your own satisfaction, you can stil flash whichever roms however you like with whatever mods you like, as long as they are compatible with your device.
Again, my recommendation is that you make a backup of lineage 16 if possible (just to be safe), then wipe System+Data+Cache+Dalvik/ART Cache, then install lineage 19 and litegapps lite. This way, you will get a clean install, meaning there shouldnt be any bugs and it should work smoothly (plus its kinda your only option anyways). You photos and media will remain intact, but your apps and settings will be cleared.
Upgrading from 16 to 19 by flashing 19 over 16 will most likely not work, as you are upgrading from android 9 directly to 12, when you are supposed to upgrade in steps, and you said your device had space/size issues when installing gapps pico with lineage 19, so it will not work if you flash 19 over 16.
When you are done flashing whatever you like and you've tested it, you can delete the backup.

PhotonIce said:
First things first, before messing with anything, take a TWRP backup (all partitions) onto prefferably an sd card.
Ok, so if you want to try and keep your data and move to lineage 19, then just download 19, boot into twrp, click install, select lineage 19 zip and flash it. Then reboot. If your device boots into lineage 19, then all's good and well, though you may experience some bugs. It is also possible that your device will begin to bootloop, or it just wont install (due to space errors). In this case, you can either restore your lineage 16 backup and stick with that, or you can wipe system+cache+data_dalvik, then flash lineage 19+litegapps lite.
If you have any gapps installed, then when you upgrade by flashign a newer version of android onto the old one, you shouldnt flash new gapps, else it will bootloop. So no, you cant upgrade from lineage 16 opengapps pico to lienage 19 litegapps lite, you can try following my instructions from the first paragraph, which will help you upgrade from lineage 16 pico to lineage 19 pico (both opengapps).
When you backup with TWRP, youre basically jsut picking up all the files in the phone (other than bootloader, but thats not important), and copying it to an sd. When you restore a TWRP backup, then it takes the files from your sd card and copies them back to their designated places on your phone. Taking a twrp backup does not limit anything, it is a passive process, it will nto affect your device in any way. If you backup lineage 16, then you are onyl doing that for your own satisfaction, you can stil flash whichever roms however you like with whatever mods you like, as long as they are compatible with your device.
Again, my recommendation is that you make a backup of lineage 16 if possible (just to be safe), then wipe System+Data+Cache+Dalvik/ART Cache, then install lineage 19 and litegapps lite. This way, you will get a clean install, meaning there shouldnt be any bugs and it should work smoothly (plus its kinda your only option anyways). You photos and media will remain intact, but your apps and settings will be cleared.
Upgrading from 16 to 19 by flashing 19 over 16 will most likely not work, as you are upgrading from android 9 directly to 12, when you are supposed to upgrade in steps, and you said your device had space/size issues when installing gapps pico with lineage 19, so it will not work if you flash 19 over 16.
When you are done flashing whatever you like and you've tested it, you can delete the backup.
Click to expand...
Click to collapse
i will give it a try when i get some time,
is there a lineage 17 ? for the n5110 as the dev only had 16,18, 19 (so i can upgrade in step)
just to be clear the space issue is with the system partition. once i load the linage rom. it seems to make a backup or something that takes the 2ish gig almost all up
im still not clear how the backups work over different versions of android, but i think doing a version by version upgrade would be more stable on the apps and os?
for me its not the pictures and what not. its all the apps and sign ins, and settings that need to be setup on a new install. i use this device for work and im looking for a way to backup everything easy so if the device gets lost or broken i can be back and running fast
again thanks for all the help, anything i learn i will pass on to the next person i can help

a twrp backup is not what you want if you're trying to backup your stuff incase your device gets broken or lost, try using google to backup, or some 3rd party backup software.
Again, I DO NOT recommened dirty flashing step by step or dirty flashing at all, your best option is to do a clean install. The storage size error in the system partition will most likely prevent you from upgrading anyways.

PhotonIce said:
a twrp backup is not what you want if you're trying to backup your stuff incase your device gets broken or lost, try using google to backup, or some 3rd party backup software.
Again, I DO NOT recommened dirty flashing step by step or dirty flashing at all, your best option is to do a clean install. The storage size error in the system partition will most likely prevent you from upgrading anyways.
Click to expand...
Click to collapse
thanks, really the back is my main issue. i dont think google or most apps do a full backup.
im hoping to do a full system backup i can just restore, without having to reset up all the logins, layouts and stuff.
even if it means having 2 of the same devices spare if that is a limiting factor.
once last thing, do you think there is a speed gain from linos 16 to 19? on the n5110

twrp backups dont work like that, the settings etc are part of the /data partition, if you back this up from a lin 16 rom and restore it on a newer or olde version your device will bootloop. Heck, restoring the data partition from lin 16 on another android 9 rom may not work. The only thing which you can backup which will work on literally any system with any rom is the internal storage partition (photos media etc.). The only thing i can think of for you is to set up your new phone and choose "i have an another device" or "i am migrating from another device when setting up lin 19. Backup lin 16 full and flash it to another tab if you have one, then choose the migrating one and migrate your stuff from the first tab onto the other. There's probably a better way of doing this, but i dont know any off of the top of my head.
Lineage 16 will probably be much faster than 19 on your device. Android 8, 9 and 10 seem to work the fastest on old devices, 11 is a little slower, havent tried 12 (excluding 7 and below as they have the old ugly ui). Maybe just stick to 16.