Database Users

Phone Bricked Can Someone Help?

This method here seemed pretty straightforward to upgrade to Nougat: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
I was already unlocked so I figured I just need to flash the "Full" package then the "TWRP" package. TWRP is working, the bootloader still shows as unlocked in fastboot mode, but trying to boot just shows a Linux penguin and nothing else!
I just cleared everything in TWRP to see if that was somehow the issue then reboot, and TWRP says no OS installed! HOW?!
All this happened because I'm unclear on everything, and instead of a yes/no answer I get mocked. Someone please help.

Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.

tester2017 said:
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
Click to expand...
Click to collapse
I have access to fastboot mode. However I'm still confused as to what is going on.
At least I've figured out where it goes wrong, at the TWRP step. The "no OS detected" made no sense so I tried flashing using the same method but just the "Full" package first. It eventually does boot and it appears Android 7 is working.
The bootloader shows as unlocked. However when I install the TWRP package after, TWRP is restored but then the phone is bricked and TWRP says no OS detected. I'm not sure if this is because I clicked "allow modifications" and if so why that causes it to go wrong and what I missed. I tried flashing TWRP manually using fastboot mode in case something was wrong with that EDL package, and the result is the same, after installing TWRP and clicking allow modifications the OS is no longer detected.
What am I missing? I must have missed a step.

ok. go to twrp and format data to ext 4 then flash new and restart.

tester2017 said:
ok. go to twrp and format data to ext 4 then flash new and restart.
Click to expand...
Click to collapse
When go to "Format Data", enter yes to allow it, it fails and says:
"mkfs.f2fs -t 0 /dev/block/sda9 process ended with
ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption
Upadting partition details...
Failed to mount '/data' (device or resource busy)
... done"
Even if that went through I'm unsure what you mean flash new? Flash a new what?
When I enter repair/change it says the file system is ext4 anyway.

Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.

Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.

Cyrus D. said:
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Click to expand...
Click to collapse
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
This is clearly posted in the TWRP thread.

flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
Thanks, already read the TWRP thread and found what I was missing.
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Edit: Just to be clear, for step 2, when I said "or you can flash it from Fastboot" I meant TWRP in general, not the TWRP EDL package.

Cyrus D. said:
Thanks, already read the TWRP thread and found what I was missing.
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Click to expand...
Click to collapse
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications. ???

romeoh said:
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications.
Click to expand...
Click to collapse
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.

Cyrus D. said:
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Click to expand...
Click to collapse
Omg bro, To be honest I hate the software experience on that phone. It is the only thing that turning me off from it. I played a little with my brother's S7 edge the other day, and believe me the software experience is extraordinary. However I noticed that the S7 edge overheats a lot too without even using the daydream. In my opinion I think Axon 7 lacks in hardware wise a bigger battery and the support of the new RCS messaging feature, and in software wise a whole new developed system.

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!

Newbie-friendly: TWRP and Root for Samsung S3 Tablet

Tested SM-T820, for Android O. It is reported that it works for Android P as well, with small modification (see below).
This post is designed to gather information found across this forum to give a step-by-step guide for obtaining a custom recovery TWRP and Root (via Magisk) for the Samsung S3 tablets running Android O. This process works if you are upgrading or staying with Oreo. [If you wish to run Android N, there is a slightly different process.] This process will wipe the contents of the tablet, so make backups as appropriate.
Credit to the software authors, original post creators (especially ashxy) and all those who contributed to the discussions to clarify all the issues. Most of the specifics below were hammered out in https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359.
WARNING Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on. You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering. [credit: jcadduono]
The below instructions are for Android O (Oreo). User BenG7 reports (I have not verified) that the same process, with slight modification, will work for Android P (Pie). See posts #38 and #39 for those modified instructions.
1. DOWNLOAD
a. ODIN​https://samsungodin.com/ (I used 3.13.1)​b. Samsung USB Drivers​https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows​c. Original firmware​Search for SM-T820 and download latest version 8.X at http://updato.com/firmware-archive-select-model​d. TWRP​At some point, it will likely find an official version at https://twrp.me/Devices/. For now, grab the latest beta version at https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359​e. Magisk​Get the latest stable Magisk version from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445​f. Ashxy's oreo encryption disabler https://androidfilehost.com/?fid=890278863836288163​​
2. PREPERATION
a. While running your tablet in Android, go to Settings -> About device. Tap 7 times on Build number to enable Developer options. [credit: jcadduono]​b. Now go to Settings -> Developer options. You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on. Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore. [credit: jcadduono]​c. Turn off your tablet.​d. Get a micro SD card​e. Copy Magisk and oreo encryption disabler onto microSD card​f. Install microSD card into Tablet​g. Install Samsung USB Drivers on Windows machine​h. Unzip ODIN (1a) and Original firmware (1c) on your Windows computer​i. While tablet is off, plug in usb cable between tablet and Windows computer​​3. REFLASH ORIGINAL FIRMWARE (Optional if your tablet is already running Oreo)
a. Enter Download mode, press and hold Home, Down Vol, and Power until you see the Warning screen of the downloader mode. Press Vol up to continue​b. Open up ODIN, confirm that ODIN can see your tablet. We will fill in three files for flashing. Click AP button on Odin. In popup, select AP_[blah blah].tar.md5 (whatever AP file you downloaded in step 1c). After selecting the file, Odin will check the signature of the file you downloaded and appear to freeze up. Let it finish, and it will report: <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. In a similar way, fill in the BL and the CSC files. As these are much smaller, the signature checks will go much faster. [Use the CSC file, not the HOME_CSC file, in the CSC slot. This will completely erase your data on the tablet, which minimizes the likelihood of future problems. You will be erasing all of the /data partition later, so there is no point in saving your data now by using the HOME_CSC file.]​c. Make sure that in the options, Auto Reboot is selected. Then click Start. The screen of the tablet should show a progress bar as your tablet is being restored to its original firmware.​d. At this point, your tablet will reboot into the default recovery mode, with a full blue screen and an android figure with the spinning arrows. The tablet will then self reboot again (perhaps more than once). After a while, you will be greeted with the Welcome screen where you can select your language. Be patient.​e. Power off the tablet using the power button​​4. FLASH TWRP
a. Enter Download mode (press and hold Home, Down Vol, and Power) until you see the Warning screen of the downloader mode. Press Vol up to continue​b. (Re) Open up ODIN, confirm that ODIN can see your tablet,​c. Important We do not want the tablet to automatically reboot after installing TWRP. If the tablet does reboot into Android before completing the steps in Section 4 and 5, there is a good chance the stock recovery will overwrite TWRP. So click the Options tab on the left and deselect Auto Reboot. After doing that, click the Log tab so you can monitor progress​d. Click AP button on Odin. In popup, select twrp-[blah blah].img.tar (downloaded in step 1d), but make sure that the BL and CSC slots are unchecked, i.e. we will only be flashing an AP file this time. Then click Start. You will see the progress bar on your tablet. Watch the log window of Odin and wait for the message "<OSM> All threads completed. (succeed 1 / failed 0)"​​5. ENTER TWRP AND CONFIGURE
a. At this point, from the last section, you should still be in Download mode on the tablet. It is important that, after flashing TWRP, to go straight to TWRP without letting the Android System reboot. To do this, Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] (while still holding [Home] + [Power]) when the screen blanks. [credit: jcadduono]​b. In a few secs, you will see the TWRP first screen, you can let go of all the buttons.​c. If you don't see then TWRP boot splash try again from the start of 4. FLASH TWRP.​d. Swipe to Allow Modifications. (For some reason, TWRP has some issues with the touchscreen for some tablets. If you experience this, expect to make several swipes or taps until it properly registers. You have succeeded when you see the classic 8-button main screen of TWRP.)​e. Click Wipe then Format Data (do not just Wipe data), type yes and let it complete. Then click back until you get to the 8-button main screen of TWRP.​f. Click the Mount button. Select Storage button, and confirm that the Internal Storage shows non-zero MB. If it is, you know that the /data partition is now mounted properly. However, since we put the needed install files on the microSD, go ahead and select Micro SD Card as our storage. Click Back until you are back at the 8-button main screen.​g. Click the Install button, install the Magisk zip file you downloaded in step 1e and copied to your microSD. Once finished, click Back to get back to the install screen (do not reboot yet).​h. Install the oreo encryption disabler zip file from step 1f. When it completes, you can press the Reboot System button and let your tablet reboot into Android. You can also disconnect the usb cable connecting the tablet from the computer. The tablet may reboot itself once or twice, let it do its thing, and eventually you will see the Samsung Welcome! Screen, where you can select your language.​​6. CONFIRM DATA ACCESS IN TWRP
a. Before going into configuring your tablet, go ahead and turn off the tablet and re-enter TWRP (Home, Vol up, Power).​b. *Important* Since you will not be changing your system partition, this time, when you get to the "Keep System Read only?" screen, click the Keep Read Only button.​c. In the 8-button screen of TWRP, click Mount, click Select Storage. Confirm that the Internal Storage is greater than zero MB. If it is, congratulations, you have TWRP installed with /data mounted.​d. Reboot to System​​7. FUTURE USE OF TWRP
a. Unless you are planning to make changes to the System, continue to choose the Read Only System when you return to TWRP.​B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5g​​
8. Click the Thanks button if my guide helped you.

Good guide. In 5, a, at least for the t-820 and if assume other variants, you can hold power, vol up, and home until it boots to recovery. You don't need to hold the keys to boot the bootloader and then quickly switch to the vol up. It's a little easier for me to do it that way.
Sent from my [device_name] using XDA-Developers Legacy app

Good guide and HNY!
klaberte said:
7. FUTURE USE OF TWRP
.....
B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5h
Click to expand...
Click to collapse
I would flash magisk *after* flashing a new ROM, i.e. install the ROM just before Step 5g.
Btw, I installed TWEAKED for T820 by @rorymc928 which comes already with encryption disabler.

Great guide!
But, anyway to install SuperSU instead of Magisk?

Frunktz said:
Great guide!
But, anyway to install SuperSU instead of Magisk?
Click to expand...
Click to collapse
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359

klaberte said:
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
Click to expand...
Click to collapse
Already asked but it SEEMS not possible because SuperSu was discountinued. But somebody has successfully installed it on Oreo 8.

I am new to rooting my Tab s3 so pardon me if any of my questions are redundant. I will be following the directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet". Can someone please confirm the following for me before I root -
1. I am running on the most recent firmware T820XXU2BRL1, do I need to complete process #3 REFLASH ORIGINAL FIRMWARE?
2. After I complete root process will my Tab s3 automatically be set to recognize SD Card as internal storage or will I need to complete another setting or process? This is my main reason to rooting.
3. Second reason is to remove bloatware. Does anyone know of a post advising which bloatware on Tab s3 to remove safely and which ones to leave alone?
4. After completing root process following directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet" has anyone experienced any Tab s3 functions or app not working properly? Is USB-OTG working?

my Tab S3 delivered today and followed ur guide and did in first try! send Thanks!

Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk

cdeitrich00 said:
Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
I had the sony framework module installed for ps4 remote play. But that was it. I cant figure it out.
Sent from my SM-N960U using Tapatalk

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...share_tid=3641443&share_fid=3793&share_type=t
This was my issue. I love this forum.
Sent from my SM-N960U using Tapatalk

Quick question. I'm already on the latest firmware, my bootloader is unlocked so can I just run Odin, flash twrp and then any pre-rooted Rom? Or do I need to follow all these steps? It's been awhile since I've flashed anything and just want to make its done properly. TIA

after rooting, the secure folder works or not

jawalexander said:
after rooting, the secure folder works or not
Click to expand...
Click to collapse
That's correct.

Is that the only drawback?

On reboot I got: Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.
Now what?
UPDATE: Oh I see, I totally skipped e. "Click Wipe then Format Data". Now it's fixed and working properly. Now to remove some bloatware.
David C.

I posted something silly before. Deleted.

THANKS ! Works also for Android PIE
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi

baudi said:
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi
Click to expand...
Click to collapse
Thanks for the update! Just wondering, why did you add busybox and XDA developers at the end of step 5g? XDA developers could have been installed as a standard app once the tablet is up and running, no?
Why manually installing BusyBox at this point of the setup?

Setting up Lineage with a broken display

Hi, I'm trying to run Android on my Switch, but the LCD is broken. The digitizer works fine, but everything beyond the far right side of the screen is unintelligible. Lineage itself works fine docked, but to install OpenGApps and/or Magisk I need TWRP. Unfortunately for me, TWRP doesn't display anything on the second screen, it's completely blank.
First, I tried installing Magisk manually. I made sense of the install script as best as I could, but the Magisk app says it's not installed. I tried TWRP ADB, but I've gathered from the guide thread that USB doesn't work. Then I tried enabling root with ADB and connecting over the network, but I can't get it to authenticate. I couldn't find the adb_keys file, so I created it at (the main partition with the most space? It's unnamed)/adb/adb_keys and have set the permissions to 0644 and owner to 0:0 with no luck. I revoked keys in settings and nothing happened, so this might actually be the wrong place. I've done quite a bit of Google-ing over the last few hours, and nothing I can find applies here.
I'm not quite sure where to go from here, I would greatly appreciate any ideas. Thanks!

Have you another switch?
Reflash Linage on your SD card put it in the other switch install your stuff over twrp press reboot it comes black screen. Shutdown the switch put the SD card in your switch an it works.
Can you access twrp over your pc whit adb?
Try it when the switch is docket.
https://forum.xda-developers.com/umi-z/how-to/guide-twrp-adb-shell-t3601881

evil_santa said:
Have you another switch?
Reflash Linage on your SD card put it in the other switch install your stuff over twrp press reboot it comes black screen. Shutdown the switch put the SD card in your switch an it works.
Can you access twrp over your pc whit adb?
Try it when the switch is docket.
https://forum.xda-developers.com/umi-z/how-to/guide-twrp-adb-shell-t3601881
Click to expand...
Click to collapse
No, no other Switch. What do you mean try when it's docked?

put your switch in the dock while twrp is running. connect the USB port of your dock to your PC and try to connect via twrp. if you don't have a connection cable, try an Android smartphone.

evil_santa said:
put your switch in the dock while twrp is running. connect the USB port of your dock to your PC and try to connect via twrp. if you don't have a connection cable, try an Android smartphone.
Click to expand...
Click to collapse
That's not quite how USB works. I can't run adb from my phone anyways, it isn't rooted.
EDIT: I'm not quite sure I understood you. Did you mean plug the dock into the computer via USB-C? If so, I've just tried that and it didn't work.

I have managed to get ADB working! ADB with root is working fine, but I don't know how I can install Magisk and/or OpenGApps from here.

Ethan Weegee said:
EDIT: I'm not quite sure I understood you. Did you mean plug the dock into the computer via USB-C? If so, I've just tried that and it didn't work.
Click to expand...
Click to collapse
Yes the switch can't speak by the usb C port whit Your computer but when the switch docket he can speak by the dock's usb port.
The reason is that the switches Otg doesn't work.
If that doesn't work for you then I can make you a finished image of what Open Gapps and magisk has already installed.

evil_santa said:
Yes the switch can't speak by the usb C port whit Your computer but when the switch docket he can speak by the dock's usb port.
The reason is that the switches Otg doesn't work.
If that doesn't work for you then I can make you a finished image of what Open Gapps and magisk has already installed.
Click to expand...
Click to collapse
The Switch dock doesn't work without power, I just tested. There wouldn't be a way to connect it via USB.
I would very much appreciate it if you could make an image I can use, though! As long as it isn't a bother!

Ok what image size do you need for your SD card? Do you need an Emunand partition for atmosphere?
But it will take a while.

evil_santa said:
Ok what image size do you need for your SD card? Do you need an Emunand partition for atmosphere?
But it will take a while.
Click to expand...
Click to collapse
My card is 128 GB and I don't need an emunand partition. I can organize the partitions after I write them with gparted, no? It shouldn't really matter.

Yes you can if you know how to do it. If I have the time, I'll make you a finished image.

Do you can boot into hekate?
can you activate root on another way? You can try Flashify, its like a "live System recovery".
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=de
If you will setup android on another switch, you can boot it on your switch, but you wlan and bt dont work.
Maybe it is possible to flash gapps and co, without booting the main system (what will install mac and co. for wireless connections). So you just have to normal boot and all is fine
We have Multiboot pre-build Images:
https://psxtools.de/forum/index.php...c-android-linux-und/&postID=805881#post805881 (Google translator will help you)

Soulreaver1993 said:
Do you can boot into hekate?
can you activate root on another way? You can try Flashify, its like a "live System recovery".
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=de
If you will setup android on another switch, you can boot it on your switch, but you wlan and bt dont work.
Maybe it is possible to flash gapps and co, without booting the main system (what will install mac and co. for wireless connections). So you just have to normal boot and all is fine
We have Multiboot pre-build Images:
https://psxtools.de/forum/index.php...c-android-linux-und/&postID=805881#post805881 (Google translator will help you)
Click to expand...
Click to collapse
I can boot Hekate and use it without the GUI, conveniently it displays text on the right side of the screen which is somewhat usable.
Doesn't Flashify require root access? I only have root access over ADB at the moment, Magisk is not installed. I don't have another Switch to install Magisk or OpenGApps. I checked the link, but it doesn't seem like those are any different at first glance? Correct me if I'm wrong.

Yes, flashify needs root.
Maybe you can try kingroot to get root and then flash magisk and Co. Via flashify.

Soulreaver1993 said:
Yes, flashify needs root.
Maybe you can try kingroot to get root and then flash magisk and Co. Via flashify.
Click to expand...
Click to collapse
Google gives me rather sketchy domains. Can you link this?

I have managed to gain root through Lineage! I found extra addons that LineageOS provides (specifically this one) and manually copied the system items to the system partition, taking care to set permissions right. After that, going into developer settings and checking the root setting now provides an 'Apps' option which is exactly what I'm looking for.
However, I couldn't install OpenGApps. Flashify claimed the flash completed successfully yet nothing new appeared after a reboot, and the OpenGApps app rebooted the Switch instantly when trying to install.

Hmm, cool way to get root.
But sorry IT doesnt Work.
The First Boot after gapps need much time, how Long do you wait?

Soulreaver1993 said:
Hmm, cool way to get root.
But sorry IT doesnt Work.
The First Boot after gapps need much time, how Long do you wait?
Click to expand...
Click to collapse
As long as it took to boot. It didn't take any longer than normal, though.

@Ethan Weegee
I made a pre made image please test and report if it works.
https://drive.google.com/file/d/1_xeNiOairi0KsCIt6EgJxd3bndl3L9mj/view?usp=sharing

evil_santa said:
@Ethan Weegee
I made a pre made image please test and report if it works.
https://drive.google.com/file/d/1_xeNiOairi0KsCIt6EgJxd3bndl3L9mj/view?usp=sharing
Click to expand...
Click to collapse
I'm so sorry I couldn't get back to you sooner! I've been distracted. I've since bought an RCM jig and learned of Hekate autoboot, so that's less painful.
I just tried to boot that image, and it 'Failed to mount SD!'. I can no longer read anything more than the first line though. I'll hopefully be getting my screen replaced soon, so I can finally figure this out.

Issues with rooted S5e running Lineage 17.1

I rooted my S5e (SM-T720) using the method outlined here. Everything seemed to go well, but three annoying issues became apparent as soon as I started using it. I could use some help troubleshooting them.
Chrome hangs frequently, becoming entirely unresponsive. Removing it from the multitasking pane and then relaunching solves the problem, but It happens quite often, and since reading on the Internet is one of my primary uses for this tablet, this is quite frustrating. I often have to relaunch about every 10 minutes or so. I rarely have many other apps open, and I rarely have more than 5 or 6 tabs open.
Google Assistant doesn't recognize my voice. When I go into settings and turn on Voice Match, the button which is supposed to turn on "Hey Google" responds, and walks me through voice training. It retrieves my voice match settings from my account, and after it completes that process, the next screen says that "Hey Google is ready," and after I click "Continue," I am returned to the main Voice Match settings, the "Hey Google" button is turned off. I have tried the "Teach your assistant your voice again," to no avail.
Most disturbingly, the tablet's screen unfailingly powers itself on immediately after powering off. It does so whether I have powered off using the power button, using the magnetic auto on/off function, or by allowing the screen to timeout. Needless to say, this is not conducive to effective battery management, and I really need to find a fix.
I don't recall the tablet doing any of these things prior to rooting/ installing Lineage, although I confess that my memory isn't improving with age. Luckily, I'm getting better-looking, insofar as I can remember. All assistance will be greatly appreciated.
P.S. I just edited this post to fix a broken link, and to clarify that it is the tablet's screen which is powering back on, not the tablet itself.

Your root link doesn't work? How did you root? Are you running a current version of Lineage and current firmware?

lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3
OhioYJ said:
Your root link doesn't work? How did you root? Are you running a current version of Lineage and current firmware?
Click to expand...
Click to collapse
I fixed the link, and it now points to https://forum.xda-developers.com/t/galaxy-tab-s5e-sm-t720-root-instructions-release-1-0.3947806/.
I just edited my post to clarify that it is the tablet's screen which is powering back on, not the tablet itself.
I'm not quite sure how to answer your questions about the version of Lineage and the firmware. The build number identified in Settings/About tablet is lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3. The folder which was created when I unzipped the download of Lineage is named T720XXU1CTK1_T720OXM1CTK1_XAR. If this isn't the information you're looking for, can you please tell me where to find it?
Thank you for weighing in. I was beginning to think that no assistance would be forthcoming.

smilejack1 said:
lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3
I fixed the link, and it now points to https://forum.xda-developers.com/t/galaxy-tab-s5e-sm-t720-root-instructions-release-1-0.3947806/.
I just edited my post to clarify that it is the tablet's screen which is powering back on, not the tablet itself.
I'm not quite sure how to answer your questions about the version of Lineage and the firmware. The build number identified in Settings/About tablet is lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3. The folder which was created when I unzipped the download of Lineage is named T720XXU1CTK1_T720OXM1CTK1_XAR. If this isn't the information you're looking for, can you please tell me where to find it?
Thank you for weighing in. I was beginning to think that no assistance would be forthcoming.
Click to expand...
Click to collapse
You don't need to do all that to root. At least not in your case. For the moment we'll go on the assumption that if you're running a recent build of LOS, you're on the new firmware, as it should check. Since you went with a "non-traditional" root method, I think I would try a reflash of LOS, basically the update method to replace anything that could have gotten "borked". This shouldn't harm any data or apps, as this is normal. Backups are never a bad idea though.
So I would try (from TWRP): (<-- Not sure which TWRP you are using, but make sure you are using at least 3.4.0-5, 3.5.0_9-0 is the latest)
- Flash Lineage (even if it's the same build as you have currently)
- Flash Gapps (if you use them)
- Flash Magisk (Magisk GitHub Here.)
- Reboot. Is it better?
I just tested 21.3 (magisk) on mine, no issues. Although I am running LOS 18.1 now.

OhioYJ said:
You don't need to do all that to root. At least not in your case. For the moment we'll go on the assumption that if you're running a recent build of LOS, you're on the new firmware, as it should check. Since you went with a "non-traditional" root method, I think I would try a reflash of LOS, basically the update method to replace anything that could have gotten "borked". This shouldn't harm any data or apps, as this is normal. Backups are never a bad idea though.
So I would try (from TWRP): (<-- Not sure which TWRP you are using, but make sure you are using at least 3.4.0-5, 3.5.0_9-0 is the latest)
- Flash Lineage (even if it's the same build as you have currently)
- Flash Gapps (if you use them)
- Flash Magisk (Magisk GitHub Here.)
- Reboot. Is it better?
I just tested 21.3 (magisk) on mine, no issues. Although I am running LOS 18.1 now.
Click to expand...
Click to collapse
Thank you for your suggestions. In preparing to implement them, new information came to light which might require that they be altered.
I attempted to perform a Titanium Backup, but when I opened the app, it informed me that I didn't have root. This was puzzling, as I had verified root before, both according to the technique suggested in the rooting instructions I linked to above, and with Root Checker. When I do so now, Root Checker indicates that I don't have root, and the procedure in my rooting instructions results in my tablet booting to TWRP.
Also, Magisk seems to have entirely disappeared from the tablet. I'm thoroughly confused at this point. Should I continue with your suggestions, or pursue other options?

smilejack1 said:
Also, Magisk seems to have entirely disappeared from the tablet. I'm thoroughly confused at this point. Should I continue with your suggestions, or pursue other options?
Click to expand...
Click to collapse
I've had that happen before, typically after installing a new ROM. Usually just reflashing Magisk in TWRP fixes it. Then you can likely run Titanium Backup as planned.

Thanks for your further assistance. Unfortunately, the adventure continues; I can't flash Magisk!
When I attempt to do so from Main Storage, the Magisk zip file doesn't appear on the top level folder visible in TWRP, nor in any subfolder therein. When I attempt to do so from the SD card, I get an error message reading "Invalid zip file format! Error installing zip file '/external-sd/Magisk-21.4.zip'.
I have tried wiping the cache and Dalvik prior to installing Magisk, with the same outcome. I'm really at a loss.

Never
smilejack1 said:
Thanks for your further assistance. Unfortunately, the adventure continues; I can't flash Magisk!
When I attempt to do so from Main Storage, the Magisk zip file doesn't appear on the top level folder visible in TWRP, nor in any subfolder therein. When I attempt to do so from the SD card, I get an error message reading "Invalid zip file format! Error installing zip file '/external-sd/Magisk-21.4.zip'.
I have tried wiping the cache and Dalvik prior to installing Magisk, with the same outcome. I'm really at a loss.
Click to expand...
Click to collapse
I figured it out. I'm embarrassed to say what I did wrong, but thanks again for your help.

smilejack1 said:
I figured it out. I'm embarrassed to say what I did wrong, but thanks again for your help.
Click to expand...
Click to collapse
We've all been there...