Develop Bugs

[ROM][4.3.1][December 3] Slim Bean jfltetmo [stable 2.2]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
Notification drawer & lockscreen Shortcuts
SlimPIE
Customizable NavBar
QuickSettings custom Shortcuts
Full hardware key rebinding!
SlimCenter
..and much more!
Need to find a feature? Want to see screenshots? Check out SlimBean's features!
Changelog
Find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers @ freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build from [here]
Gapps ( if you don't have it already) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the gapps you want, reboot
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb".
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
You can find the full list of credits here
Source
Please visit here for the rom source code.
Kernel source can be found here
XDA:DevDB Information
Slim Bean jfltetmo [stable 2.2], a ROM for the T-Mobile Samsung Galaxy S 4
Contributors
blk_jack
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2013-12-03
Created 2013-08-18
Last Updated 2013-12-08

SlimBean 4.3 stable 2.2
Stable 2.2 is live! Please read the Changelog for more details including proper upgrade/installation methods, as well as notes on activating root and restoring with Titanium Backup.
Changes, Features & Fixes:
Changelog for stable 2.2
SuperUser security fixes
Several BT fixes
Selinux security ehancements
LID control fix
some translation upstrem
nearly all device got device and kernel updates

Please note these builds are under heavy development!
Known issues
Headset in-call mic uses phone
HDR Camera mode may need improvements, but should at least work
4.3 mini-FAQ
Q) I'm stuck at the boot logo and/or a boot loop!
A) Make sure you use TWRP 2.5.0.2. TWRP 2.6 and other recoveries can cause boot loops & hangups
Q) Root doesn't work!
A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.
Q) Titanium Backup isn't restoring apps!
A) Change the backups folder to storage/emulated/legacy.
If you use Philz recovery 5.10.0 you must upgrade to 5.11.0 or you will lose radio!
Since the SGS4 is so new, development is happening very rapidly. This should be taken into consideration when flashing any 4.3 AOSP-based builds on the device. Known issues will be listed here.

I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.

quickquest88 said:
I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.
Click to expand...
Click to collapse
Something is definitely wrong on your end. You're gonna have to give me more info, like your recovery and what steps you did to install the ROM.
If it's stuck at the boot logo, try wiping dalvik cache.
Sent from my SGH-I337M using Tapatalk 4

I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.

quickquest88 said:
I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.
Click to expand...
Click to collapse
The lack of /data in recovery worries me the most. That's definitely not good and I'm not sure how that would be happening.
Are you doing all this w/ your device plugged in? Can you try not plugging it in if that's the case?
EDIT: I've had an issue where sometimes on reboot w/ my device plugged in I need to wipe dalvik to continue booting. I'm not sure why this is at the moment but it's always fixed if I reboot to recovery and wipe dalvik cache.

i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.

quickquest88 said:
i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.
Click to expand...
Click to collapse
From what I'm reading there are issues w/ TWRP 2.6. Downgrade to TWRP 2.5 and your issues should go away.

I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
I spoke too soon. now I'm getting an error when trying to format system that says cwm can't mount /data or /android.secure and /sdcard
now I seem to be soft bricked. I can't get it to go past the Samsung galaxy s4 screen. can't format.

quickquest88 said:
I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
Click to expand...
Click to collapse
You sure you don't have a bad build?? None of my testers are having these issues. Grab it here & flash it w/ goomanager or odin/hemidall http://goo.im/devs/OpenRecovery/jfltetmo

thanks fro the link. twrp 2502 got me out of the softbrick. with cwm, nothing seemed to work to get it past the samsung screen.
twrp got me to the point that i can at least get it running again, however, not even 2502 fixes the original issue of being unable to reboot. this time after getting 4.3 installed, i rebooted at the screen asking what language. it didnt get past the samsung screen. went back into recovery and wipe/format data/yes and then reboot. that got me back into the o.s.
this is really strange, i wish i knew more about developing. as long as i dont reboot, im ok. good thing this isnt windows, or id be in trouble, hah!!

I had no problems installing with the latest regular version of CWM from ROM Manager. Got root working just by tinkering around in superuser in settings... Not sure what I did but root works. Overall very very nice for a beta release!
I have one inane question(hope I didn't miss it somewhere): is the setting for lock screen rotation removed? It seemed to me to be buggy on cm10.2 anyway. Also can't remember if the phone app rotated to landscape in 4.2.2 build, but I think it did. Again, meaningless issues really, just wondering.
Thanks for the hard and awesome work!

Loving the beta build! It's almost fully stable! All convenient features are working as should!

I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.

Bowmanspeer said:
I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.
Click to expand...
Click to collapse
It'll be under Gallery2
Sent from my SGH-I337M using Tapatalk 4

Flashed 8/20/13 using TWRP 2.5.0.2. No problem, other than some freezing apps here and there. Cleared caches, fixed permissions, and all seem fine now.
Will now run it through my battery tests, etc.
Thank you blk_jack!

I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app

quickquest88 said:
I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This is a notice for others on TWRP 2.6. Please read the OP (post 3 specifically). It has been updated to contain a mini-FAQ for 4.3 that should solve 99% of the issues I'm seeing on XDA.

Any way to get stock DPI?
Sent from my Nexus 7 using Tapatalk 4

[Q&A] [ROM][KITKAT]CyanogenMod 11S OnePlus Edition M10 Released 1

Q&A for [ROM][KITKAT]CyanogenMod 11S OnePlus Edition M10 Released 1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Desire HD with [ROM][KITKAT]CyanogenMod 11S OnePlus Edition M10 Released 1
Folks, I seek your help.
I have DHD rooted running SVHD v2.1.0 on it.
I wanted to try the CyanogenMod 11S OnePlus Edition M10. (http://forum.xda-developers.com/showthread.php?p=54651965#post54651965
Did the following to install it:
1) downloaded the ZIP to the SD card
2) rebooted into recovery - Recovery is using ClockworkMod Recovery v5.0.2.0 (CWM)
3) chose to install Zip from SDcard and proceeded to select the zip.
4) Installation was aborted with following message:
Finding update package...
Opening update package...
Installing update ...
Cant install this package on top of incompatible data. Please try another package or run a factory reset
E:Error in /sdcard/11SM10R1.zip
(status 7)
Installation aborted.
=== After some research ===
5) Chose to
a) wipe data/factory reset
and
b) wipe cache partition
and
c) Wipe Dalvik cache
then
6) chose to install Zip from SDcard and proceeded to select the zip.
7) Installation was aborted with following message:
Set_Metadata_recursive:some changes failed E:error in 11SM10R1.zip file(status 7).
=== some more research ===
Found several threads on several forums.
This one on XDA by Daniel_HK (http://forum.xda-developers.com/showthread.php?t=2532300) talks about updating a binary.
Before I proceed with this, I wanted to check if I'm doing something fundamentally wrong.
Could someone more familiar with this please advise what I'm not doing?
thanks in advance.
Regards.
NS.

You need a selinux recovery. Cwm 6.04 or twrp 2.7.1
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
There are other factors..are u s off...unlocked bootloader? Need to know these things

marknoll said:
You need a selinux recovery. Cwm 6.04 or twrp 2.7.1
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
There are other factors..are u s off...unlocked bootloader? Need to know these things
Click to expand...
Click to collapse
Indeed if S-ON then probably won't able to flash this rom due to error=panic flag and /devlog partition support still present on it. And if he's S-OFF then not limitations.
Well other than that, He's good to go after flashing any of latest custom recoveries like TWRP 2.7.1.0 or Philz Touch 6.0.4.7 and 4ext RC3.
Highly recommend update recovery as @marknoll mentioned.

hi team, just a quick post to say the issue has been resolved. :good:
I will post details a bit later today (after I've had breakfast).
best regards.

As you guys pointed out, indeed I had to update the recovery
I found this yesterday and it provided the path forward.
From Mustaavalkosta
Pre-requites:
Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.29.8 or newer
TWRP 2.7.1.0 ACE or newer
I used CWM on steroids -> PhilZ Touch as detailed by Ruling here:
Download PD98IMG.zip ,
Put in your SD card,and reboot to hboot,
Press the "Volume Up" to Update，
Press "POWER".to Reboot.
After setup remove the file.
So once the Recovery was updated, rest was straight forward.
It's loaded fine, I've not spent time with Apex launcher before and am impressed.
First time I have a de-sensed device.
Cheers guys.
Best regards.
NS

Nihim said:
I 've been using it for the past few days and it works like a charm.
Since yesterday though I am getting some problems. First the phone would stay always awake, I fixed that by going to privacy guard and denying any google apps / services access to keep awake if I saw that they made tons of requests.
Now the wifi keeps staying on regardless if I choose: keep on while plugged or never while sleeping. The phone does go into deep sleep but the wifi appears on the whole time.
Anyone knows a solution to this problem?
Cheers
ps: the only modification I did was changing cpu max from ~1024 to ~1200.
Click to expand...
Click to collapse
komikaze said:
In my opinion ,you should uncheck "Scanning always available" in advanced Wifi settings
Click to expand...
Click to collapse
It was always disabled. Also can't find an app / service that seems to enable / keep the wifi active.

problem with partitions
hey guys,
i have this freaky problem. i've upgraded to the M9 a few months ago, and you all know how the HDH is very light on the space part, so about a month ago i found i can partition my sdcard to add extra space for apps.
i did this on the M9-R1 and everything worked like a charm. BUT - when i tried to upgrade to the M10 the following started to happen - at first everything is great. loads normally, syncing and all. but when i first reboots the device it takes it a very long time to go from splash screen to bootimage (about 10-20 minutes of black screen. i first freaked out i bricked it) and when it finally loaded it wouldn't read the partition. meaning it would SAY it has a total of 1.13G of space in total, but it wouldn't use half of it (the apps that were installed on the partition would not show. system warning of not enough space etc).
rebooting doesn't do much. it boots normally but gets the same result. i tried installing again, to wipe the entire sdcard and repartition, but it didn't help. the partition would become useless after first reboot.
i am using rooted DHD, 4ext for recovery and partitioning.
any help would be very much appreciated!!

cant update nova
hey guys, rom works fine, only one issue, i cant update nova launcher, it says, its already another version installed with missmatching signature.
wiping cache and dalvik doesnt help.
force close doesnt help.
wiping cache and data in settings/apps doesnt help.
pls help

B1gD4ddy said:
hey guys, rom works fine, only one issue, i cant update nova launcher, it says, its already another version installed with missmatching signature.
wiping cache and dalvik doesnt help.
force close doesnt help.
wiping cache and data in settings/apps doesnt help.
pls help
Click to expand...
Click to collapse
i am not an expert, but i think the expert ones don't really watch this thread..
i couldn't upgrade nova, or tesla, either.
i guess there is something wrong with the signature on the apk used to build this rom.
some one just brought it, concerning tesla, to the attention of the devs on the main thread.
in other words, i don't think there's a fix for this, you could try using some app management tool that can uninstall system apps to uninstall the current copy of nova and install it again from the market by yourself (note that if the apk in the rom is the full version, you would still only be able to install the free version over the market).

Every five minutes i get this error. Every time it haapens twice, after that it works five minutes more.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Pikkk said:
Every five minutes i get this error. Every time it haapens twice, after that it works five minutes more.
Click to expand...
Click to collapse
Do you have any xxxhdpi theme installed? All it happens with the default system theme?

Flashly Photo Problem ! :S
Hi. Thanks for Rom.
But, take a flashly photo, get black screen and turn of phone.
i get off/on battery then open my phone. What is problem i dont understand?
Thanks,
Best Regards...

breakofrap said:
Hi. Thanks for Rom.
But, take a flashly photo, get black screen and turn of phone.
i get off/on battery then open my phone. What is problem i dont understand?
Thanks,
Best Regards...
Click to expand...
Click to collapse
If I heard you right you mean you get a black screen when try to take a picture?

Yes, its true...
xdagee said:
If I heard you right you mean you get a black screen when try to take a picture?
Click to expand...
Click to collapse
Take a new photo don't flashlight no problem.
But on flashlight take a photo black screen my phone lightbrick.
Need remove the battery for open my phone.
sorry for bad my english.

HELP!
I downloaded the M11 and installed it, can i just flash the new update M12 over the M11? will it work that way? and will it remove the beat audio automatically? if i do so?

about NOva Launcher/prime
RED = Done with the problem
the M12 comes with the nova launcher/not prime,
can i ask how do i install the new nova launcher 3.3 full apk that i found to this.
Do i need to uninstall previous version(comes with M12) before i install the new version(prime crack)?
sorry newbie here and 1st time rooting my device so im asking a lot.
__________________________________________________________
GREEN= My FIX
I update the defult nova launcher with Lucky Patcher. now the nova launcher prime is working thanks to that

What are the differences between those two download links?

Signature verification
Hi guys, what do a do wrong?
1) Chrome has got some problems with the file calling it "malicious" when downloaded. I allowed the file and copied to SD without problems but something may gone wrong, see point 2.
2) I'm in ClockworkMod Recovery v5.8.1.5 and ROM is not installed. Fill wipe done but there is always an error with signature verification. If the verification is on, it just says "E: signature verification failed, Installation aborted". If signature check is disabled then the package is opened and updated but installation is aborted too: "E: Error, Status 7", some changes failed etc.
What should I do to fix this?
Thanx!

alirezajaberirad said:
What are the differences between those two download links?
Click to expand...
Click to collapse
Its in twos, one with gapps preloaded and the other without gapps.
resuah said:
Hi guys, what do a do wrong?
1) Chrome has got some problems with the file calling it "malicious" when downloaded. I allowed the file and copied to SD without problems but something may gone wrong, see point 2.
2) I'm in ClockworkMod Recovery v5.8.1.5 and ROM is not installed. Fill wipe done but there is always an error with signature verification. If the verification is on, it just says "E: signature verification failed, Installation aborted". If signature check is disabled then the package is opened and updated but installation is aborted too: "E: Error, Status 7", some changes failed etc.
What should I do to fix this?
Thanx!
Click to expand...
Click to collapse
Flash the latest TWRP recovery and it should work fine.

[root] [ZS570KL] Asus Zenfone 3 Deluxe fast rooting method. Despite TWRP

Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75

Your links do not work.

jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!

You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...

Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app

Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA

You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat

Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!

I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).

Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??

Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.

Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry

Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.

Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website

This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!

Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files

Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.

Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.

Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname

Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.

Messed up TWRP - stuck on decrypting

So, recently, my Magisk stopped working. I thought I fixed it with seveal steps, including updating Magisk and TWRP, and it worked fine at first, but after one of restarts TWRP started requesting encryption password and doesn't boot into system. Entering system pass/pin doesn't let me into TWRP either, it's stuck on "Attempting to decrypt FBE for User 0".
I haven't done anything related to flashing in 1.5 year so I'm kind of lost now. What would be the best way to recover from this without losing any data? I assume some ADB actions, but what do I need to do exactly?

One more note that I thought was irrelevant: I installed Viper in Magisk. Didn't expect such patch could do this, but after some googling I found 2 people having simila issue afte installing that. Please help! Would replacing boot image to MIUI's help in that case?

Try flashing stock boot image then. Google it

That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610

"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.

Destroy666x said:
That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610
Click to expand...
Click to collapse
Sorry, I apologize for that

kekesed97 said:
"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.
Click to expand...
Click to collapse
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.

Destroy666x said:
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Click to expand...
Click to collapse
Official upgrades won't lose your data (dirty flashable, as the name suggest "update"). In that case, use fastboot upgrade. I will recommend to hold to somewhere in 12.0.5 or 12.0.6, because if you messed up something, you can still downgrade to many versions, maybe up to initial version?
I did many downgrades before because I have tripped AVB many times, something like <newer A10 version available> -> installed magisk and TWRP -> AVB tripped -> <some A9 MIUI via miflash> -> fastboot update via mi flash pro to <same newer A10 version available> -> rinse and repeat until I got a stable system. Without costing any data. But with headaches, indeed.
Mi Flash is also another option. Make sure you choose the "flash_all_except_data". Or else, more unnecessary headaches.
Destroy666x said:
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.
Click to expand...
Click to collapse
1. App and app data will stay
2. I guess app permission is also stay. But do confirm, since I never had any issue except when I enable/disable MIUI optimizations
3. Personalization will stay

kekesed97 said:
fastboot upgrade
Click to expand...
Click to collapse
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.

Destroy666x said:
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.
Click to expand...
Click to collapse
Oopsie! Swapped fastboot with recovery rom, ehehe.
Use recovery rom (the 2 gb one). This will require stock boot, stock recovery, mi account, and internet connection. Flashing is done via MiFlash Pro (Just click that "Flash in Recovery" botton or go to recovery tab).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1: Mi Flash Pro main interface
Or use Mi Flash by loading fastboot rom (the 4gb one) to Mi Flash, and select "flash_all_except_data".
Figure 2: Mi Flash with "flash_all_except_data" enabled

Oh ok, I see, recovery ROM, downloadable easily from MIUI website, is something you upload though recovery and fastboot ROM through fastboot/MiFlash. Found them here https://c.mi.com/oc/miuidownload/detail?guide=2 along with MiFlash 2020 version (is this the latest version?) but how do I find older ROM versions, e.g. my 11.0.6.0? The MIUI website seems to be a total mess, honestly. And I don't trust random Google results, bunch of them seem like virus traps redirecing to Mediafire and similar upload websites.
Is this also the official MiFlash Pro website? https://miflashpro.com/
EDIT: yes, it seems, also found https://xiaomiflashtool.com/ for the other app's latest version

Here for a streamlined versions or here if you need betas
Mi flash is included in mi flash pro if you want all in one solution. It also have miui downloader embedded

Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.

Destroy666x said:
Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.
Click to expand...
Click to collapse
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.

kekesed97 said:
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.
Click to expand...
Click to collapse
Fixed that: https://forum.xda-developers.com/t/...ils-because-of-data-misc_ce-10-error.4311899/ and have a backup.
Unfortunately, flashing the recovery ROM = still bootloop. Would flashing the fastboot one be any different if I choose to keep data? Would it flash someting extra?
I read that reading these logs may also help with debugging, but not sue what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
EDIT: well, I tried the fastboot one too, recovery got replaced with stock is the only diffeence I noticed, So I guess that means the data is 100% corrupt and the culprit. How would installing Magisk and the dm-verity/forceencypt zip corrupt the data though? Since that's the only thing I did before he bootloop started happening. Does dm-verity/forceencrypt even affect data? I think Magisk does, but this is really weird anyways. Maybe when I tried to install it on the TWRP with broken encryption it caused some file system failure? Does anyone know which /data dirs does the Magisk zip mess with? Maybe deleting those would help
EDIT2: ran Magisk as uninstall.zip in back installed TWRP 3.3.1, which apparently deletes its data files, but nope, didn't do anything.

I'm sorry I don't have the knowledge to go deeper.

Samsung galaxy tab 3 GT-P5210 - how to backup? and what is recent upgrade?

Dear
I have a old tab 3 tablet, I can't get it update from 4.4.2 to latest available.
Is there also a method to backup the originel android version?
any steps how to to this and also how to upgrade? it will be my first time.
I googled first, found how to enable development settings, but I don't see the OEM unlock .
So I did not want to continue.
I hope to get some info.

Hi there,
So, I don't know about the backup, bc the apps wont run on LineageOS. Just save your data and flash it to a custom rom.
The tablet is years out of date, therefore no updates for the tab3.
The only option is to flash a custom ROM.
I just flashed my 5210 (tab3 10.1 WiFi Santos) with this version of LineageOS (latest available)
[ROM][GT-P52XX][UNOFFICIAL][7.1.2] LineageOS 14.1
Unofficial LineageOS 14.1 for Samsung Galaxy Tab 3 10.1 LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your...
forum.xda-developers.com
her this is just the manual for flashing your phone with Lineage OS
Before you need to do 2 other things.
1. First of all, unlock the bootloader
2. Then flash TWRP.
3. Then flash LineageOS
4. Root with magisk.
Before you start, save your data, everything will be wiped.
1. Unlock bootloader..... its easy. Go to settings-phone info, and tab 10 times onto BUILDNUMBER, to unlock DEVELOPER TOOLS.
Then go back to settings - developer tools, and activate USB DEBUGGING.
Then turn off the tab, and start it with
POWER & MINUS & HOME
THATS IT, YOU UNLOCKED THE BOOTLOADER.
You need this (unlock bootloader), to flash TWRP onto the phone, its like a BIOS, from where you are able to flash/wipe/mount etc .
The manual for "2. Flash TWRP" for the tab3 is here: http://forum.xda-developers.com/gal...covery-twrp-3-x-samsung-galaxy-tab-3-t3340938
After you managed to install TWRP, you can finally flash LineageOS & gapps&magisk. Just follow the step by step instructions in the first thread I linked.
A little advice from me.... Before you start anything doing on your phone, read all steps in the instructions, and download all files needed into a folder.
Also... read some of the pages after page1 and read also several of the last pages in both (!) threads (TWRP and LineageOS), to be aware of mistakes others have already done .
After being confident in which order to to things, and that you have all the files, you can give it a try.
its not a 30min run, if its your first time. Take your time, if you struggle, just repeat the last step, or watch out on XDA forum for the same mistake, and the workaround for the solution.
Sometimes its just, BC you forgot to wipe things in the exact order.
Its very important, that you have the correct LineageOS file (3 available for the tab3). If you are not sure, which model is yours, just install an info app like "Device Info HW". You will find the info there.
godspeed
edit: before I forget: if you managed this, have a look at the SWAP FILE thread. For me it was a little performance booster, even if the LineageOS is already much more fluid than the stock ROM.
Swap for Samsung Galaxy Tab 3 10.1 (GT-P5210)
DISCLAIMER: I AM NOT RESPONSIBLE FOR YOUR DEVICE OR ANYTHING THAT MIGHT OCCUR WHILE USING THIS TUTORIAL. TRY AT YOUR OWN RISK! Credits: [mbm] for teaching me this dd terminal method. As we all know, for what ever reason, Samsung decided to...
forum.xda-developers.com

Dear Karl
Thanks for quick reply.
About the backup I mean : If the upgrade fails , or if I want to go back to 4.4.2 original OS, bc I miss some functionality, I want to be able to put back the original OS.
I don’t need apps or data to work with upgraded version .
I have read very fast all you have send me , it seems I have to put some preparation in it.
I will plan this for another time.
So to understand : only possible to upgrade to android 7 using the lineageOs?

"So to understand : only possible to upgrade to android 7 using the lineageOs?"
Yes, because google stopped the update support for this model.
in other words, if you dont flash it with a newer rom than yours, you wont be able to use it, at least for surfing or movies, bc most apps wont run on android 4.
cheers

For the backup thing, just use the search funtction in the subforum of the tab3.

2. Then flash TWRP.
as I need this first, after tablet is in donwload mode,, I have read all the messages in this post
Can I use latest version twrp 3.4.0.3 ? as some have used this and works for them, I assume they also had a samsung tab 3 GT-P5210.
As in the second post, the version is still 3.0.2-0.
If I undertood correcly, I can choose how to flash TWRP, reading , googling, I think Odin will be easy for me on my windows laptop.
I hope I'm correct in undestanding so far?
I stil have to check the posts about things as sideload, , whatever that is, Gapps "X86 "or "arm"
and about what to do after flasing TWRP.
I understnd that : once TWRP is installed on my tablet, I have to prepare the custom rom using Odin, too, and connect tablet in downloadmode ? wil this not erase TWRP? hmm

Can I use latest version twrp 3.4.0.3 ? as some have used this and works for them, I assume they also had a samsung tab 3 GT-P5210.
--> nope. First install the TWRP from the thread (3.0.2-0 )
After you succesfully flashed the twrp, you can upgrade TWRP. I dont know why, but thats the way...
Yes, i flashed twrp via odin on win7. Win10 may be buggy, i have read it in some threads.
You dont really need sideload, you just need to copy all things you want ro flash/install on a sdCard and plug into tab. You just "install" the OS and Gapps (and magisk) via TWRP.
The "x86" and "arm" thing is just a warning, to choose the correct hardware-version of Gapps (GoogleApps - its the google in several different variants, just choose the version you like/need....i dont want google, so i didnt install)
In one post, i mentioned a hardware info app. in this app, you can see which exactly hardware you have. if you know which hardware, you can choose the correct Gapps.
yes, after installing TWRP, you install LineageCustomRom and GAPPs, but not via odin, just via TWRP.
when flashing TWRP is succesfull via ODIN, the mobile restarts automatically. You need to be fast, for pressing (power & plus & home).
With this combo you will finally enter into twrp
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ah, before i forget, first time in TWRP, you can make your backup . Just be sure, your sdCard iS big enough.
In twrp you need to wipe+format ( please look in the lineageOS thread.)
DONT reboot after wiping. You just deleted and formated old data/OS.
After the wipe you install LineageOS, and without reboot you install gapps directly after.
after flashing/installing OS+Gapps you start the first time into LineageOS....This will need some time .
And then, power up the first time, you will see if you did it properly.... it can happen, that you'll have a bootloop. Dont worry then, you just messed up the order for the wiping, or forgot Gaps. if you have a bootloop, just go into TWRP, and restart by the first step
gl&hf

For the backup:.... first time booting to TWRP, you can/should make your backup.
just choose the all boxes, for your full backup...I made a screenshot....
And just fir your info:
my little reminder, that wiping in TWRP is a bit wired

deleted