Tab Pro 8.4 Needs an upgrade. Cyanogenmod 13? - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

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

Related

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine

for anyone looking for twrp for t520 10.1 wifi only

It is auto loaded when you load flashify. Then u can select wether u want twrp or cw recovery.
Hope this helps someone as twrp. Wifi t520 is not available on twrp site.
+1 confirmed it worked on mine (t520).
Can also be retrieved here if you want to flash via Odin.
http://goo.im/devs/OpenRecovery/picassowifi
I fond myself in a situation where my tablet wouldn't boot and I needed to install a custom recovery, so I had to flash via Odin.
I was just going to post a thread about this. Flashify app is the easiest way I have ever used to install custom recovery!
More details?
All,
I rooted my 10.1 yesterday, since ROMS are starting to come out. I used TWRP and CWM on a Toshiba Thrive prior to own the tab pro.
Anyways...I rooted last night with Odin, but still only have the stock recovery.
Please tell me how to get TWRP installed, without messing up the tablet (it is an expensive device, just want to make sure I don't brick it!)
Just flash the zip from the stock recovery?
Unroot and re-root using flashify or Odin?
I can't wait to get rid of all the Samsung crap!!! (but want to backup first)
Thanks a lot,
Damien
Re twrp for t520 and roms
Wish there was some way to help young 14 year old ik4ver [written first custom rom for our device]...some deadbeat loser keeps sabotaging his account now hijacked to extort a rom for the 12.2!!! I have never seen anything like this...hopefully karma works her magic on this scumbag!
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
rom thread back up
Can't help yet ..I haven't had balls to flash rom yet lol. Looks like his rom thread is back up and running for now.
MrBungle67 said:
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
when u figure out can you post solution? would be helpfull
perhaps young ik4evr will surface with a suggestion.
MrBungle67 said:
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
I did...have balls
spton said:
Can't help yet ..I haven't had balls to flash rom yet lol. Looks like his rom thread is back up and running for now.
Click to expand...
Click to collapse
Yep...I tried again...
So, in order, I...
- Rooted using Odin
- Install TWRP using Flashify (thanks to K8108 for the earlier post)
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except internal and external storage
- Install ik4evr's ROM
- Rebooted...
Tablet booted no problem (it stays on "SAMSUNG" for a little bit, which worried me...)
All Samsung apps are gone!!!
that's awesome thanks for the procedure details!
Actually it was young ik4evr that let me know bout twrp being auto loaded in flashify .. that's why I started thread as it's kinda confusing as twrp site doesn't list t520 wifi only.
Good work!
spton said:
Actually it was young ik4evr that let me know bout twrp being auto loaded in flashify .. that's why I started thread as it's kinda confusing as twrp site doesn't list t520 wifi only.
Good work!
Click to expand...
Click to collapse
This all forum is freaking confsuing, as it is about 6 (8?) different devices, where some are kinda similar, and others completely different (thinking especially of Exynos vs Qualcomm).
Plus there is no real guide, and takes hours trying to figure out if this thread/recovery/rom applies to our device or not.
Plus 8.4 became modrian, and 10.1 picasso.
Yay, confusing is the right word!!!
well I've loaded Treo with flashify and done full stock rooted rom
Backup. Now have to grow a pair and flash ver3 of ik4evrs rom! So you have zero issues and everything working?
I was going to wait at least till his thread gets sorted out...hmmm...i voided warranty anyway at this point lol
MrBungle67 said:
This all forum is freaking confsuing, as it is about 6 (8?) different devices, where some are kinda similar, and others completely different (thinking especially of Exynos vs Qualcomm).
Plus there is no real guide, and takes hours trying to figure out if this thread/recovery/rom applies to our device or not.
Plus 8.4 became modrian, and 10.1 picasso.
Yay, confusing is the right word!!!
Click to expand...
Click to collapse
Treo = twrp
Dang spell correction!
spton said:
Backup. Now have to grow a pair and flash ver3 of ik4evrs rom! So you have zero issues and everything working?
I was going to wait at least till his thread gets sorted out...hmmm...i voided warranty anyway at this point lol
Click to expand...
Click to collapse
Zero issue wouldn't the word lol! I did have a bit of a cold sweat yeterday...
I'd say as long as you have the stock rom backup go for it!
I actually started a thread separated from here. I wonder if "wipe internal storage" ok or not...what I can see is that bunch of folders remained from apps installed before flashing the rom.
As far as the steps listed above, I just did it this morning and all went well. As far as deep testing to see if everything is still working, I can't answer yet (at work, no time to play with it).
Let me know if you have any issue...
Ball grown yet?
Alright...so:
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except external storage
- Install ik4evr's ROM
- Rebooted...
Just reflashed the rom, this time wiping the internal storage as well.
After apps update, 472mb used, 11Gb free (was 6gb used before wiping the internal storage).
So far, the only issue is something I read on a post somewhere, but contacts aren't syncing.
I am sure a V4 will be here soon!!
Everything else seems to be working.
MrBungle67 said:
Yep...I tried again...
So, in order, I...
- Rooted using Odin
- Install TWRP using Flashify (thanks to K8108 for the earlier post)
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except internal and external storage
- Install ik4evr's ROM
- Rebooted...
Tablet booted no problem (it stays on "SAMSUNG" for a little bit, which worried me...)
All Samsung apps are gone!!!
Click to expand...
Click to collapse
I did the same. All worked.
Unfortunately I cannot restore apps succesfully from Titanium backup. The restore seems to be ok, but I only get FC's. The apps will not start. I cannot find the cause of the errors.
Something in directions of maps destination changed? Knox?
I do not understand it.
I had a hard time with TB also. Had to get most of my apps back from the play store. Lost some data. Oh well. My contacts are syncing from Google, tho.
k8108 said:
I had a hard time with TB also. Had to get most of my apps back from the play store. Lost some data. Oh well. My contacts are syncing from Google, tho.
Click to expand...
Click to collapse
I always reinstall from the play store... I like it clean and fresh, and I don't have that many apps to restore.
Now...How did you get your contacts? I just installed google+, and my circles finally synced in the contact app. As far as all other contacts (gmail), can't sync them...
Sent from my SM-T520 using Tapatalk
I don't know why my contacts are syncing. The only difference I can see is that in our flashing the rom, I didn't do the advanced wiping. I just did factory reset and cache wipe. I left my system unwiped. I'm not real savvy on this stuff - I have just been a good instruction follower for the past few years and have spent lots of hours reading here on XDA. I am heavily addicted to my tablets and use them for several hours a day so I have over 100 apps. It's a real pain for me to have to go thru the play store for a restore
Sent from my SM-T520 using XDA Premium 4 mobile app

Lineage Update Installation Issues

As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?

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.

Can only flash CM 11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte

I can flash back to stock via the SkipSoft Unified Android Toolkit, but not matter how far back I go, the only 3rd party ROM that will not get stuck on a never-ending bootscreen after install is CM 11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte. Not even the CM nightlies that came immediately before or after would work once this was installed.
I would like to try something newer if there is a stable Lollipop, Marshmallow, or Nougat ROM you would recommend. I don't use as a phone anymore, so I don't even need cellular data to work.
Thank you very much to anyone that even takes a look at this.
More info...
Model Number
1HZGY
Android version
4.4.4
Baseband version
L710VPUDOH1
Kernel version
3.4.104-cyanogenmod-g3652409
[email protected] #1
Mon Aug 31 16:36:33 OCT 2015
Build number
cm_d2lte-userdebug 4.4.4 KTU84Q bdfbe2c9c2
test-keys
SELinux status
Enforcing
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
madbat99 said:
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
Click to expand...
Click to collapse
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
pravus87 said:
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
Click to expand...
Click to collapse
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
madbat99 said:
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
Click to expand...
Click to collapse
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
pravus87 said:
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
Click to expand...
Click to collapse
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
madbat99 said:
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
Click to expand...
Click to collapse
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
pravus87 said:
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
Click to expand...
Click to collapse
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
madbat99 said:
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
Click to expand...
Click to collapse
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
pravus87 said:
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
Click to expand...
Click to collapse
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
madbat99 said:
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
Click to expand...
Click to collapse
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
pravus87 said:
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
Click to expand...
Click to collapse
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
madbat99 said:
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
Click to expand...
Click to collapse
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
pravus87 said:
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
Click to expand...
Click to collapse
Happy to help
madbat99 said:
Happy to help
Click to expand...
Click to collapse
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
pravus87 said:
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
Click to expand...
Click to collapse
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
madbat99 said:
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
Click to expand...
Click to collapse
I did not try Lineage or Vanir again like I did Commotio and CarbonROM to verify the md5s. I will try them and some older builds of each.
I sincerely appreciate the offer. I would certainly be willing to download a large backup if you would be willing to take the time to clean install and upload. Let me try the remaining steps you listed first, though. Don't want you to have to spend time doing all that if we can get it working another way.
Thanks again. Will keep you posted!
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
pravus87 said:
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
Click to expand...
Click to collapse
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
madbat99 said:
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
Click to expand...
Click to collapse
Thank you. No rush - whenever you have time.
I don't get it either. I waited a long time to post about it because I assumed there was something simple I was overlooking that I would eventually figure out. Not sure this will work if nothing else has, but I can't wait to give it a shot.

Categories

Resources