Develop Bugs

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

20gb System storage alotment and unable to flash anything

Hello all! I've got a puzzling issue (for me, at least) that I'd like to see if anyone else has encountered and what their possible fix might be.
So I've been alternating between running Resurrection Remix and Pure Nexus the past few months and have had no issues flashing new builds or kernels. Last night when I went to switch back from RR to Pure Nexus I encountered and error I haven't seen before and some weird results from it.
When I went to flash the Pure Nexus it kept failing stating TWRP was unable to find the meta/inf/com/Google (I think) data in the zip. I tried flashing RR again with the same issue. I then tried to wipe and restore a TWRP backup that didn't end up working even though it said it did. I then decided screw it and flashed the factory image for the Pixel XL and was able to at least get booted and running on stock. However, my storage is pretty much gone and now only have like 6gb out of 8gb total. Upon I spection System is currently taking up 20gb worth of storage and even after flashing the factory image again it is still not resolved.
Can anyone tell me what I managed to do here and if there is a fix? Realistically I'd love to figure out how to actually repartition everything in the phone and start from scratch again.
Any advice or insight would be greatly appreciated as I'm not new to rooting and rom'ing but am getting uinely confused as to what has happened here.
PS: I attached a picture of my storage breakdown but can't inspect further due to not having root and being on stock. Viewing storage in TWRP didn't yield much more I formation either.

MR H3LLMAN said:
Hello all! I've got a puzzling issue (for me, at least) that I'd like to see if anyone else has encountered and what their possible fix might be.
So I've been alternating between running Resurrection Remix and Pure Nexus the past few months and have had no issues flashing new builds or kernels. Last night when I went to switch back from RR to Pure Nexus I encountered and error I haven't seen before and some weird results from it.
When I went to flash the Pure Nexus it kept failing stating TWRP was unable to find the meta/inf/com/Google (I think) data in the zip. I tried flashing RR again with the same issue. I then tried to wipe and restore a TWRP backup that didn't end up working even though it said it did. I then decided screw it and flashed the factory image for the Pixel XL and was able to at least get booted and running on stock. However, my storage is pretty much gone and now only have like 6gb out of 8gb total. Upon I spection System is currently taking up 20gb worth of storage and even after flashing the factory image again it is still not resolved.
Can anyone tell me what I managed to do here and if there is a fix? Realistically I'd love to figure out how to actually repartition everything in the phone and start from scratch again.
Any advice or insight would be greatly appreciated as I'm not new to rooting and rom'ing but am getting uinely confused as to what has happened here.
PS: I attached a picture of my storage breakdown but can't inspect further due to not having root and being on stock. Viewing storage in TWRP didn't yield much more I formation either.
Click to expand...
Click to collapse
Format userdata should fix it.

toknitup420 said:
Format userdata should fix it.
Click to expand...
Click to collapse
I believe I tried that at one point last night but will try it again here shortly. Any thoughts on what it could be if this does not fix it? And what method would you recommend to format userdata? Do I do it through TWRP?

fastboot format userdata

swapavi said:
fastboot format userdata
Click to expand...
Click to collapse
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha

MR H3LLMAN said:
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
Click to expand...
Click to collapse
You may need to fast boot new boot images to slot a and b. You just have to unzip factory image and you will see them in there. Or just flash the factory image all over. Start fresh.

MR H3LLMAN said:
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
Click to expand...
Click to collapse
Don't flash recovery, you're pixel will get all screwed up lol. You temp boot it and install via the twrp installer zip.

I need some advice on downgrading from MM, rooting etc

My T800 is in a right state. I was running one of the first MM roms to be released in the wild, with root and twrp. But a couple of months ago, I mistakenly installed the correct official MM rom, breaking everything. Now I can't root it, install twrp and adopted storage doesn't work.
So I was hoping I could downgrade to lollipop, root, install twrp and then update to one of the root-friendly MM roms on here. Is it possible to do that?

mickrick said:
My T800 is in a right state. I was running one of the first MM roms to be released in the wild, with root and twrp. But a couple of months ago, I mistakenly installed the correct official MM rom, breaking everything. Now I can't root it, install twrp and adopted storage doesn't work.
So I was hoping I could downgrade to lollipop, root, install twrp and then update to one of the root-friendly MM roms on here. Is it possible to do that?
Click to expand...
Click to collapse
I’ve flashed lollipop KitKat marshmallow upgrade downgrade without any issues. These are official firmware’s i been flashing via Odin SM-T705 my model is hope that answers your question..

mickrick said:
My T800 is in a right state. I was running one of the first MM roms to be released in the wild, with root and twrp. But a couple of months ago, I mistakenly installed the correct official MM rom, breaking everything. Now I can't root it, install twrp and adopted storage doesn't work.
So I was hoping I could downgrade to lollipop, root, install twrp and then update to one of the root-friendly MM roms on here. Is it possible to do that?
Click to expand...
Click to collapse
I'm not sure what you mean by break everything?
A few more specifics is required.

ashyx said:
I'm not sure what you mean by break everything?
A few more specifics is required.
Click to expand...
Click to collapse
By "broken" I mean, apps crashing, apps not installing, freezing, random rebooting, overheating. The sorts of things which drive you mental and, in effect, break everything.
I must have wiped and installed the OS a dozen times over the weekend. I was able to get the correct version of twrp and install it with odin, letting me wipe the system and data partitions in order to get a clean install. I restored all my apps, installed a system update. Then I installed twrp again, flashed the su zip and for some reason it would start freezing, reporting the sd card had been removed. So I eventually wiped, installed the rom, and then let Smart Switch install the correct version of MM for my tablet and just installed the really essential apps. Then twrp and finally su. I was even able to set half of my sd card up as adoptable storage (using root essentials app) and it is working perfectly now.
But I think its time I was looking out for a replacement tablet now. Although a great device at the time, and for a couple of years afterwards, it has become a bit long in the tooth lately.

In order to rule out any external issues, I'd use odin to flash the factory firmware (this of course will erase TWRP). Remove the sd card, and use the device for a while as is. If it works, then your past problems were some kind of software-related problem. If it still has issues, then there could be a hardware problem, like memory or the rest of logic board.

Akopps said:
In order to rule out any external issues, I'd use odin to flash the factory firmware (this of course will erase TWRP). Remove the sd card, and use the device for a while as is. If it works, then your past problems were some kind of software-related problem. If it still has issues, then there could be a hardware problem, like memory or the rest of logic board.
Click to expand...
Click to collapse
I think he's got it sorted now. Seems that's what he's already done.

weird thing happend to my pixel xl. it could't update/flash from lower build to 8.1

I've tried to solve this issue over one week now. Just couldn't figure out why it nearly drives me crazy.
It works fine under 7.1.x and 8.0. OTA function works fine under 7.1.x to 8.0. flash to stock image (below 8.1) doesn't show any problem.
1.When I OTA from 8.0 to 8.1,the phone can receive OTA and download and install, it seemed no problem at this procedure. When I clicked restart to complete OTA , it booted to Google with white background and return to boot interface three or four times and get into system, there is still old build there.
2. Flash factory image (8.1), click flash all , the whole procedure seems working properly, when it booted up , screen switched Google image and boot image several times and endend up with a laid down robet and saying NO COMMAND. I've been searching this for days . Have tried as many as method as I can find to flash it to 8.1 . The only result is showing up no command. I v tried sideload OTA.img, the same result . Also tried to switch slot to reflash stock image . Always same result. Keep telling me NO command . I'm so desperated .
The problem I state above only happens when I try to update/flash from lower build to 8.1.
BL unlocked.
Does anyone have the same issue and have solution about it ?

You need to flash whichever factory image you want to both A and B slots with a recent new ADB setup to go backward in versions.

Im guessing youre trying to avoid wiping internal storage and thats why you want to patch with OTA. you might have to bite the bullet and just back everything up and run the latest factory img to get you on the update without issues going forward.
I always recomend when versions change like 7.1.2 to 8.0 to 8.1 to factory reset everything so you dont have to trouble shoot issues later in life.

Im guessing youre trying to avoid wiping internal storage and thats why you want to patch with OTA. you might have to bite the bullet and just back everything up and run the latest factory img to get you on the update without issues going forward.
I always recomend when versions change like 7.1.2 to 8.0 to 8.1 to factory reset everything so you dont have to trouble shoot issues later in life.

SynisterWolf said:
Im guessing youre trying to avoid wiping internal storage and thats why you want to patch with OTA. you might have to bite the bullet and just back everything up and run the latest factory img to get you on the update without issues going forward.
I always recomend when versions change like 7.1.2 to 8.0 to 8.1 to factory reset everything so you dont have to trouble shoot issues later in life.
Click to expand...
Click to collapse
Thanks for the post .
I was not trying to avoid wipe internal storage , just because flash to stock image failed

Android Q beta2 Rollback

Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks

nick w said:
Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
Click to expand...
Click to collapse
Yeah you can either use the "flash-all.bat" file that comes in the android p stock image zip or fastboot boot twrp.img and once booted into twrp just restore a backup. But you'll need to create a folder on you sdcard called TWRP. Then put a backup in it. I've even booted twrp then flashed pixel dust. It's not as critical as it was years ago when once you went up bootloader then downgraded which would cause bricking. At least I haven't run into any issues. Just make sure you turn off any lock screens and have "USB debugging" enabled.

If you are enrolled in the beta, just opt out on the website where you opted in. You'll get an OTA, which will wipe your device, so back up first. Just did this last night. Couldn't have gone any more smoothly.

For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?

You have to have your phone unlocked... Yes, you will lose everything from internal memory, but can restore all your apps and settings.
I made this path twice, on beta 1 and now on beta 2.
First, make sure you have twrp. Back up on twrp everything but you will need only the data partition. Also don't forget to backup your internal memory (different from the data partition).
After that, just flash normally the last factory image from Pie, or at least the same version that you have on your nandroid backup.
After finish the installation, install again twrp. Go into twrp and restore ONLY the data partition!!! You can also restore the boot if you like (if you had magisk installed for instance). This worked flawless with me.
I repeat, no use if you try to restore ALL partitions on twrp!! At least with me, twrp would just reboot in the middle of restoring the system partition (no idea why that happened on beta 1 and now on 2). Second, the same if you try to flash factory image without the -w (without wiping internal memory), it just reboot every time it tries to enter android.

reno218 said:
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
Click to expand...
Click to collapse
This is a bug that was fixed in Q. You can alternatively fix it in pie by flashing a kernel that has Q patches merged in.