Develop Bugs

[Q] Recovery and outdated device questions

Hello,
I got my Htc One on Day 1 that Verizon released it and rooted it using rumrunner, for both S-off and root access with no problems. I have since to update my phone. I would like to update my phone to the latest radios and firmware, and start flashing custom roms.
My problem is I cannot make a backup from TWRP, my company required me to encrypt my phone to get work email but I have since had them remove the encryption but it seems that TWRP is still requesting a password to decrypt my data. I use the same password that I was using to encrypt my device but it says that it is wrong. I was thinking of factory resetting my phone but since there is no SD card will all the data that I have on my internal storage, i.e. the different backs ups I made from various apps still be on the internal storage or will they be deleted too.
Also once the encryption problem is resolved what is the best way to update my phone
Thanks
geterdone11

geterdone11 said:
Hello,
I got my Htc One on Day 1 that Verizon released it and rooted it using rumrunner, for both S-off and root access with no problems. I have since to update my phone. I would like to update my phone to the latest radios and firmware, and start flashing custom roms.
My problem is I cannot make a backup from TWRP, my company required me to encrypt my phone to get work email but I have since had them remove the encryption but it seems that TWRP is still requesting a password to decrypt my data. I use the same password that I was using to encrypt my device but it says that it is wrong. I was thinking of factory resetting my phone but since there is no SD card will all the data that I have on my internal storage, i.e. the different backs ups I made from various apps still be on the internal storage or will they be deleted too.
Also once the encryption problem is resolved what is the best way to update my phone
Thanks
geterdone11
Click to expand...
Click to collapse
Everything you need is in this thread -
http://forum.xda-developers.com/showthread.php?t=2485319
Just download the newest rom, download the newest firmware package. Put the rom on your SD card, put the firmware in your adb / fastboot firectory etc.....instructions should all be on that page.
Flash the firmware first, get the newest version of TWRP from the original development section here, flash it next, then flash the new sense 6 / 4.4.2 rom from recovery. Profit. You are s-off, so should be easy. I don't think your encryption glitch will even effect the process. And if you mess something up, since you are s-off you can just RUU back to stock. Hope this helps.

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron

ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.

No need to relock the bootloader for an ota. People should stop spreading that info

Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!

ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.

You can be unlock and have OTA.
You just need a stock recovery.

HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.

Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.

jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron

ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates

jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.

ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..

vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.

Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.

jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

Tab Pro 8.4 Needs an upgrade. Cyanogenmod 13?

I've had this tab for awhile now and the lack of updates wasn't an issue for me while my Nexus 7 was still my workhorse. USB port and charging issues has forced me to use the Pro almost exclusively now and it's frustrating. I'm thinking CyanogenMod 13 because it's available and the latest version of android. But I have a couple questions. Please help. I've searched and will continue but a little help would be appreciated.
Internal storage is at the top of my list right now and I believe Cm allows the ability to use SD card as internal storage. It's available in CM12 but apparently not CM13 as it sits as a nightly. Is this still true? I'm going to flash this tab today. Would rather go with 13 but I'll flash a stable 12 because I need this ability.
This isn't really that important but would help with dealing with all my remote controls. Does Cm now have the ability to take advantage of the RF sensor for remote control? In the past it was always blamed on closed source drivers. Still an issue or no?
Thanks for your input. After being away from the scene for awhile I've answered most of my questions. These are the last two.

I have the CM13 version from about a week ago, and it has the option for using the SD card as internal storage. As for the IR blaster, there are a couple of apps on the play-store that worked with CM12, so I assume they will also work with CM13.

Sicron said:
I have the CM13 version from about a week ago, and it has the option for using the SD card as internal storage. As for the IR blaster, there are a couple of apps on the play-store that worked with CM12, so I assume they will also work with CM13.
Click to expand...
Click to collapse
Thank you! Guess I'll grab a 13 nightly and get to work :good:

Hey guys. The install went smooth but I'm getting parsing error when trying to install apps from unknown sources. In particular right now I'm trying to get PS Remote Play setup but the only remote app I can get to install needs updating. Every single other download I've tried has failed due to parsing error.
Edit: Now I'm stuck. Cm13 is running fine. Rooting was smooth, flashing Twrp 3.0.0-2 was smooth. But then I started installing my apps from unknown sources. Parsing errors even though it's set to allows unknown sources. Hours of searches, tons of articles dealing with parsing errors and everyone recommends check the unknown sources box. Nice!
During this process I've booted into recovery and even though it worked fine before now it freezes in different areas. The menu will sometimes freeze right away or wait till I try and reboot into recovery, OS, download it doesn't matter. Reinstall Twrp and no change. I originally used Flashify but also tried Twrp manager which was worthless. Shocker.
At this point I want to just start over but I have zero confidence in Twrp. Or is maybe because of flashify? I'm lost. Is clockworkmod available? Most likely regardless of my thinking I'm missing something here. I just need a fresh start. How should I start. I need a recovery first.

IFLATLINEI said:
flashing Twrp 3.0.0-2 was smooth.
During this process I've booted into recovery and even though it worked fine before now it freezes in different areas. The menu will sometimes freeze right away or wait till I try and reboot into recovery, OS, download it doesn't matter. Reinstall Twrp and no change. I originally used Flashify but also tried Twrp manager which was worthless. Shocker.
At this point I want to just start over but I have zero confidence in Twrp. Or is maybe because of flashify? I'm lost. Is clockworkmod available?
Click to expand...
Click to collapse
Are you flashing TWRP 3.0.0.2 every time? I wasn't even aware they had a 3.0.0.2 build. And once in a while, they release a build with some problems. If you haven't already, try 3.0.0.0. I'm still back on 2.8.5.0 and no issues like you describe.

redpoint73 said:
Are you flashing TWRP 3.0.0.2 every time? I wasn't even aware they had a 3.0.0.2 build. And once in a while, they release a build with some problems. If you haven't already, try 3.0.0.0. I'm still back on 2.8.5.0 and no issues like you describe.
Click to expand...
Click to collapse
Yeah but its 3.0.0-2. https://dl.twrp.me/mondrianwifiue/
Somehow I got it all worked out. Starting over from scratch. The problem now is how to update to more recent nightlies. TWRP doesn't see any files anymore.

IFLATLINEI said:
Yeah but its 3.0.0-2. https://dl.twrp.me/mondrianwifiue/
.
Click to expand...
Click to collapse
I don't know why they just switched from the last digit in the version number being -1, -2, etc, instead of .1, .2 (dash instead of dot) which they used for years.
But that misses the point. If you are having trouble on a brand new TWRP version, try a previous, known good one.

redpoint73 said:
I don't know why they just switched from the last digit in the version number being -1, -2, etc, instead of .1, .2 (dash instead of dot) which they used for years.
But that misses the point. If you are having trouble on a brand new TWRP version, try a previous, known good one.
Click to expand...
Click to collapse
Yeah I got ya. I may try another one. Problem is I couldn't begin to guess which one is a "known good one". I know I've used a few starting with a 2.8 something up to the one I'm using now. None of these were even able to get me this far. But thanks

IFLATLINEI said:
The problem now is how to update to more recent nightlies. TWRP doesn't see any files anymore.
Click to expand...
Click to collapse
You have the right location selected, correct (internal storage vs. SD card)? A number of times, I've switched the location in TWRP, then forgot to change it back and scratched my head wondering where the files went.

redpoint73 said:
You have the right location selected, correct (internal storage vs. SD card)? A number of times, I've switched the location in TWRP, then forgot to change it back and scratched my head wondering where the files went.
Click to expand...
Click to collapse
Yeah I ran into that as well. I can assure you now its set correctly but I did experiment with placing the zip file in folders on both.
I got fed up last night and just started over. I flashed back to stock, Rooted, and flashed TWRP 3.0.0.0 this time and it worked! Installed CMs latest nightly and im up and running. Havent tested yet to see if zip files now show up in TWRP. Ill be looking after lunch

IFLATLINEI said:
I got fed up last night and just started over. I flashed back to stock, Rooted, and flashed TWRP 3.0.0.0 this time and it worked! Installed CMs latest nightly and im up and running. Havent tested yet to see if zip files now show up in TWRP. Ill be looking after lunch
Click to expand...
Click to collapse
If you don't know if zip files show up in TWRP, how did you flash CM? Did you sideload?
To be clear, when you were having trouble seeing zip files in TWRP before, it was using the "Install" function in TWRP? Or were you trying to "Restore"?

redpoint73 said:
If you don't know if zip files show up in TWRP, how did you flash CM? Did you sideload?
To be clear, when you were having trouble seeing zip files in TWRP before, it was using the "Install" function in TWRP? Or were you trying to "Restore"?
Click to expand...
Click to collapse
Because adopted storage wasn't setup till after CM13 was installed. Adopted Storage is the key in this whole mess. Unfortunately for me its also the one key component I need to make this tab last me another year. What I was trying to do was flash the latest nightly with TWRP. That's when I realized TWRP couldn't see any of the files in any folder.
But get this. I forgot to repost after lunch. Seeing as though this time I successfully used 3.0.0.0 to flash CM I thought my chances of it seeing a zip file were pretty good. And it did! But then it freezes. Multiple reboots and all attempts to select a file or folder resulted in TWRP freezing. But at least 3.0.0.0 seen the files as you would expect. Maybe I should give 3.0.0.0-1 a shot again.

Depends do you have the T320, or the T325? AFAK the newer version of TWRP is ONLY for the T320. Having installed it to my T325 I lost my Recovery. thankfully I was able enough to recover it by flashing 2.7.8.x though Odin again in Download Mode. Not sure what was so special about the T320 that it needed a point realese fix for, that the T325 never got.

Ichijoe said:
Depends do you have the T320, or the T325? AFAK the newer version of TWRP is ONLY for the T320. Having installed it to my T325 I lost my Recovery. thankfully I was able enough to recover it by flashing 2.7.8.x though Odin again in Download Mode. Not sure what was so special about the T320 that it needed a point realese fix for, that the T325 never got.
Click to expand...
Click to collapse
I have the T320

At the risk of adding confusion to this Thread, it seems that the T325 version of TWRP was also recently updated to v3.0.1.0 recently.
Since that's the version I'm running,
FYI:
mondrianWIFI = T320
mondrianLTE = T325
The trick here is to google mondrian<INSERT DEVICE> TWRP, which should take you to the direct download page.
To flash from rooted stock you'll need a *.img.tar File, with which to flash from Odin. In my case that would apply to v2.8.7.0 (IIRC).
Once that's been installed you can just use *.zip Files from within TWRP to update it.

Ichijoe said:
At the risk of adding confusion to this Thread, it seems that the T325 version of TWRP was also recently updated to v3.0.1.0 recently.
Since that's the version I'm running,
FYI:
mondrianWIFI = T320
mondrianLTE = T325
The trick here is to google mondrian<INSERT DEVICE> TWRP, which should take you to the direct download page.
To flash from rooted stock you'll need a *.img.tar File, with which to flash from Odin. In my case that would apply to v2.8.7.0 (IIRC).
Once that's been installed you can just use *.zip Files from within TWRP to update it.
Click to expand...
Click to collapse
Just to be clear. There was no problem flashing CM13 from stock with TWRP. Its not till the flash is all done and I selected to adopt SD card as internal storage. Then regardless of TWRP version it either won't see any files or and I've only been able to get 3.0.0.0 to see files but it freezes.
Here's the question. Are you using adopted storage?

IFLATLINEI said:
Just to be clear. There was no problem flashing CM13 from stock with TWRP. Its not till the flash is all done and I selected to adopt SD card as internal storage. Then regardless of TWRP version it either won't see any files or and I've only been able to get 3.0.0.0 to see files but it freezes.
Here's the question. Are you using adopted storage?
Click to expand...
Click to collapse
no not yet, I'm still kinda stuck on a 32GB card that I've had since my S1 days. I'm kinda hoping to pick up a 64GB MicroSD for that purpose soonish though.
But, just outta interest, you wouldn't have happened to have Device encryption enabled, would you? As for myself I managed to figure out that if you encrypt the Device early enough (i.e. before you root it), the GSM \ Data Connections still work. Where as if you do it post root, it would kill those functions. (Not that a T320 User should care though).
But, the other side effect of encryption (of the /data Partition), is the loss of said /data Partition under TWRP. Which can no longer 'see', what it thinks should be a valid /data Partition. So reports back to you a 0kb free (e.g. not found).
Now like I have stated I have not used any features which would marry my MicroSD to the Device, yet... But if I had then as I understand how Google implemented Adapted Storage to work. then it would be reasonable to assume that it would become part of the /data Partition.
So to get to the punch line... is your Device encrypted? If so that's your problem right there.

No I haven't encrypted it. Its on my list of things though. I just didn't want to overcomplicate things at this point. I felt as though I was already pushing pretty hard with the CM13 nightlies and adopted storage. I'll tell you this much though. I said it before and I'll say it again. This thing has never ran so well. Also for the first time since I've had it storage is not an issue.
I'd seriously recommend the Samsung Evo+ micro SD card. I haven't noticed any issues with lag when loading or using any app. Since I've installed this setup a few times now though I noticed that when you do select to adopt storage and it tests your card, pay zero attention to what it says. Same card and twice it said the card was too slow and twice it said nothing. There's a flaw there I think. It alternated. First time the card was too slow but the second time there wasn't a problem and so on. Then again maybe not. Could be the SD card that's causing that. Ahhhhhh who knows. Lol

Hi Folks:
I had been running CM12 and deciding to upgrade to CM13 last night as the several issues seemed to have been addressed most recently in the most recent string of Nightly's.
I followed the instructions from RootJunky dude and all went just fine.
HOWEVER
I lost my root in the process. Not pleased about that.
Any way to get it back now that I'm on CM13, or do I have to roll it all back via a recovery?
Thanks for your assistance

whitehawk66 said:
Hi Folks:
I had been running CM12 and deciding to upgrade to CM13 last night as the several issues seemed to have been addressed most recently in the most recent string of Nightly's.
I followed the instructions from RootJunky dude and all went just fine.
HOWEVER
I lost my root in the process. Not pleased about that.
Any way to get it back now that I'm on CM13, or do I have to roll it all back via a recovery?
Thanks for your assistance
Click to expand...
Click to collapse
Settings - > About Tablet -> click the build number a few times to enable "Developer options" then Click the back arrow or back button -> Developer options -> Root acess - Click Apps and ADB
now apps that need root will prompt you

How long after flashing superSU zip does first boot take?

First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.

Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first

l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.

Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.

Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly

Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.

Maybe this has something to do with Keymaster?

So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?

Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.

New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks

Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!

Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/

Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though

The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.

Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.

Rooted T-800 (wifi model), looking to update to Android Nougat or Later

So I had rooted my Tab S back in 2016 or so (if you check the forums here you'll see my posts for this...). Have had that working for a while now. It tripped the Knox (I didn't personally care about this) except now I want to install a couple streaming apps on the tablet and the OS is too old to handle it
I had loaded TWRP onto the Tab S and rooted it with Lollipop stock ROM and loaded it with SuperSU. It has worked like a charm up till now, issues with Link2SD notwithstanding (I have ZERO intentions of going back to that app).
My question is: what do I need to do to install the newest possible version of Android that the tablet can take? I know it's an older tablet now but I still use it for reading and other stuff, and I'd like to keep it alive a bit longer by installing a new Android OS and ROM on it.
(aside: I did remove a bunch of stuff once I rooted it, so I am not sure how much this may interfere with any attempt to update it to a newer version of Android)
(aside #2: I never updated SuperSU through the app store as I was afraid it would break the root process, so I left that app alone and eventually it stopped showing up in my update list on google play. I'd have to check the tablet to see what version of it I have installed at present)

Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.

cbb77 said:
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
Click to expand...
Click to collapse
Hey thanks for your reply!
Do you need to update the android version to get Lineage OS installed?

No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.

Hi again,
Sorry could you point me in the direction of said thread?

cbb77 said:
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Click to expand...
Click to collapse
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080

bsquared938 said:
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
Click to expand...
Click to collapse
Yes, that is the correct thread.

cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
Perfect. Will also update this table to give it a further lease on life .
Thanks man!

cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
@cbb77
Cannot find the Lineage OS ROM image, I think it may have been removed from their site given the age.
Do you have a working download link for this?
Edit: please ignore post, I found it as soon as I posted this -.-

T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.

Trung Gs said:
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Click to expand...
Click to collapse
I assume I have to load the marshmallow bootloader before I do anything?

bsquared938 said:
I assume I have to load the marshmallow bootloader before I do anything?
Click to expand...
Click to collapse
Personally I like the Resurrection Remix rom. https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243
Just do the standard stuff. You've got TWRP installed, so you're most of the way there. Back up whatever you want to back up, and then:
1. Wipe System, Data, Cache, and Dalvik Cache.
2. Install OS.
3. Install Magisk (if you want to use Magisk for your rooting needs. It seems to be the popular root tool now. It's pretty boss.)
4. Reboot into system, then back into recovery, and:
5. Install GApps or whatever. I like NanoDroid myself. It's the alternative to GAPPS. There are a few odd programs that just plain won't work with it yet, but the official Google apps have an annoying habit of wasting processing power on pointless background nonsense, so I prefer the alternative. Also there's an Xposed module that improves compatibility. https://nanolx.org/nanolx/nanodroid

Hmm I'll take a look at this other ROM
Currently, I have a rooted stock ROM (SuperSU ad root manager), and interested in moving to a custom ROM that is well supported
My only 2 concerns before starting are:
1) Do I need to update SuperSu
2) Do I need to update the bootloader before doing anything else (even the ROM that you suggested @FailSafeNow ? )

Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now

bsquared938 said:
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
Click to expand...
Click to collapse
I know this is a somewhat old thread. I have a T800 myself and am looking for a ROM. Want to try Lineage OS 14.1 like you have tried. Was curious as to whether you still have it and if you still liked it? If so, what version are you running now and how is your battery life compared to stock? Thanks so much! :good: