Develop Bugs

[please close]Can't flash any other rom after flashing the Android 6.0 gpe rom

Hey guys, hope someone can help me. A few days ago i've flashed the new android m gpe rom and everything was fine. Then somehow i lost root access and tried to fix it. Unfortunately, i'm not even able to flash the fixed rom that was posted a few days later, so i decided to come back to the skydragon sense rom. And for some reason i can't. I try to flash the .zip, it opens in aroma installer, everything goes fine until the installation itself starts. The rom starts to flash, comes to ~20% and then the system just reboots. I've tried both twrp and filz touch, nothing helps.Also supersu doesn't flash properly. I'm not really professional in this, so i might just do somethng wrong, hope someone can help:crying:
Btw i'm s-on.
UPD: I've made an advanced wipe and the everything works now, so if you have the same problem then just try to do the same, see if works.

Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?

redpoint73 said:
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
Click to expand...
Click to collapse
I just flashed the GPE ROM, i'm s-on as i said.

Would this ROM work on Verizon HTC One M8
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help

Are you still able to go into TWRP recovery and are you also rooted?

crispinsaro said:
Are you still able to go into TWRP recovery and are you also rooted?
Click to expand...
Click to collapse
Who was this question adreed to? If you asked me, then i am able to get into recovery, but the supersu doesn't seem to flash, at least i don't get the root.

Miramontes said:
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Click to expand...
Click to collapse
Well, the problem is that i'm s-on, so i hope there is any other solution for this

Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?

paulmartyn said:
I've tried both twrp and filz touch, nothing helps.
Click to expand...
Click to collapse
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
Miramontes said:
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue
Click to expand...
Click to collapse
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.

crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
Will try to erase everything later,maybe tomorrow. Twrp says everything's fine, and aroma doesn't say about any issues, just reboots. Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is. Anyway, thanks for an advice, will try that and tell if it helps or not

redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
I tried filz just to check, because on skydragon everything was fine.
I use twrp 2.8.7.0
hboot 3.19.0.0000
radio 1.25.21331147a1.o6g(if that's what baseband is)
tomorrow i'll try everything you guys advised, see if there is a solution. thanks for the support man

Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!

crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
well, i've tried to make an adwanced wipe as you advised and it worked thanks man, i thought i'll stay on that rom 4ever.
flashing skydragon now:victory:

crispinsaro said:
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
Click to expand...
Click to collapse
guess the problem was caused by different android versions

redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
So i've tried to make a FULL wipe and finally it worked, everithing works fine now, installin' skydragon and waiting for a better 6.0 ROM

Guess i can close the thread now as my problem is resolved.

paulmartyn said:
Guess i can close the thread now as my problem is resolved.
Click to expand...
Click to collapse
Happy that solved your issue, it is normally said that to install a new rom you have to do a full wipe before hand, glad it worked for you though

paulmartyn said:
Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is.
Click to expand...
Click to collapse
You mean flashing SuperSU after Skydragon (you don't specify)? If so, its not necessary, as all custom ROMs are pre-rooted unless explicitly noted.
Also, older versions of SuperSU won't work on Lollipop, so depending on what version SuperSU you tried (again, you don't specify), that may have been the reason for failure.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
crispinsaro said:
I am sure you factory reset through recovery before installing the new ROM
Click to expand...
Click to collapse
I wouldn't be so sure, if the OP didn't state it.
crispinsaro said:
I normally go on advanced wipe and tick all the boxes
Click to expand...
Click to collapse
I would caution users about following this device literally. It is not necessary to wipe internal storage and/or SD card when flashing a ROM (although particular users may have reason to do so for specific reasons). And if the user has their nandroid or ROM.zip on that partition (and they must have the ROM on one of those, unless they intend to sideload it), its going to get wiped out; causing some confusion and probably panic.
The advice I normally give is: Its called "Advanced" for a reason, and don't wipe it unless you know what the result will be; and you have a legitimate reason to do so.
For instance, I've lost count of the times folks have posted that they wiped system, and don't understand why the phone will no longer boot into OS. Or they wiped internal storage or SD card; and didn't know that it would wipe out their nandroids.
The TWRP default wipe (data, cache and Dalvik) says "most of the time, this is the only wipe you will ever need" and it says that for a reason. If one runs into problems flashing a ROM, they might elect to wipe system. So like I said, a legitimate reason to wipe a particular partition.
But on the other hand, I've done a countless number of ROM flashes on a number of devices (including Skydragon), and never wiped any partition outside the "default wipe", and never had any such issues. Even wiping system (which many swear by) I suspect is often a placebo. When you flash a ROM, system will be wiped by definition, so doing it manually is redundant.
I suspect the failure by the OP was not wiping data and/or cache (they never specified they did that originally or not).

Thats true yes, i dont think I made it clear to do the default TWRP wipe first to see if it would solve anything and then try advanced wipe if all fails, but again with caution.

After reading a litte I've got one question...So if I want GPE rom do I need to convert my phone to GPE or just to flash the rom ?!

After updating from cm13 to cm14 cant access TWRP recovery mode

Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help

If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.

luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.

nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you

Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.

DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"

This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:

DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/

luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?

DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk

luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?

DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.

luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far

Phone bricks when trying to flash new ROM?!

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Does anyone know what the problem could be?

I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk

Wrong forum.

danecr7 said:
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong

RazorBlade123 said:
Wrong forum.
Click to expand...
Click to collapse
Yeah I thought it seemed a little out of place but I don't know where to post it? Is there a general questions forum?

evilkitty69 said:
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
Click to expand...
Click to collapse
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.

danecr7 said:
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
Click to expand...
Click to collapse
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly

evilkitty69 said:
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
Click to expand...
Click to collapse
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.

danecr7 said:
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
Click to expand...
Click to collapse
All of the ROMs I tried with were android 6.0.1, I'm avoiding touching android 7 because I'm not a fan
The strange thing is that in TWRP under "mount", system is unchecked and it won't stay checked when I reboot or try to flash something and then the flash fails. Strangely however, I can flash RR afresh and it will work but nothing else works
Therefore I don't think OOS would work either

TWRP

I just got my 5t. It's unlocked, stock Oreo latest update. I am encrypted. The only thing I'm not sure of is which TWRP to install. Is one fof them for nougat?
Does it matter that I'm encrypted. I've been a fan of Dirty Unicorns for years and thinking about trying that first. Any help is really appreciated. Thanks

I don't think there is a dedicated 5T Dirty Unicorns thread on XDA. But I read it is an unencrypted ROM. Correct me someone if I am wrong. There is a Dirty Unicorns Google+ thread. People who have encrypted ROMs seem to use codeworkx or blu_spark TWRP. But for unencrypted ROM I hear official TWRP is fine.
However, since stock is encrypted, perhaps take codeworkx or blu_spark nandroid first.
And going from encrypted to unencrypted needs data reformat + factory reset.
Moreover, going back from unencrypted to encrypted can be tedious. In short, one not only needs to data reformat + factory reset, one needs to pass through stock recovery if I understand well. I find instructions somewhere in the official TWRP thread or elsewhere.
In short: going unencrypted is almost a one way street. But there always is a way back.

Dior DNA said:
I don't think there is a dedicated 5T Dirty Unicorns thread on XDA. But I read it is an unencrypted ROM. Correct me someone if I am wrong. There is a Dirty Unicorns Google+ thread. People who have encrypted ROMs seem to use codeworkx or blu_spark TWRP. But for unencrypted ROM I hear official TWRP is fine.
Click to expand...
Click to collapse
You're right. DU stopped posting on xda awhile back but think I saw a dumpling build online, however I'm not sure if it's nougat or Oreo...
I don't necessarily need encryption but is that the only issue? So if I want unencrypted, the official version will be fine? Does anyone know if I can decrypt with TWRP? (I'll probably have to format data but that's fine) Thanks

KLit75 said:
You're right. DU stopped posting on xda awhile back but think I saw a dumpling build online, however I'm not sure if it's nougat or Oreo...
I don't necessarily need encryption but is that the only issue? So if I want unencrypted, the official version will be fine? Does anyone know if I can decrypt with TWRP? (I'll probably have to format data but that's fine) Thanks
Click to expand...
Click to collapse
DU no doubt is 8.1 and YES you need to format data.
The other way back to encrypted seems the harder part.

Dior DNA said:
I don't think there is a dedicated 5T Dirty Unicorns thread on XDA. But I read it is an unencrypted ROM. Correct me someone if I am wrong. There is a Dirty Unicorns Google+ thread. People who have encrypted ROMs seem to use codeworkx or blu_spark TWRP. But for unencrypted ROM I hear official TWRP is fine.
However, since stock is encrypted, perhaps take codeworkx or blu_spark nandroid first.
And going from encrypted to unencrypted needs data reformat + factory reset.
Moreover, going back from unencrypted to encrypted can be tedious. In short, one not only needs to data reformat + factory reset, one needs to pass through stock recovery if I understand well. I find instructions somewhere in the official TWRP thread or elsewhere.
In short: going unencrypted is almost a one way street. But there always is a way back.
Click to expand...
Click to collapse
I now have codeworkx twrp, rooted with magisk. I gotta say I'm pretty impressed with stock but I KNOW I'm gonna want to flash a custom ROM soon and that's not a fast process when you're encrypted.
You said make a nandroid...have you ever restored just data from stock to a custom ROM? I may have but it's been awhile. I'm thinking I might have issues.
If I want to flash ROMs I'm going to need to format (better sooner than later) so from what I remember, I should:
1. Boot TWRP
2. Format data
3. Full wipe?
4. Adb push ROM, gapps, magisk
5. Flash all of them
I'm just hoping you or someone else can verify. I've got a lot of stuff to transfer over from my old phone but it makes no sense to do that now if I'm going to have to format. Thanks
UPDATE_
I got it. Running Dirty Unicorns now. It was a bit of an adventure. MTP would not work. Had to adb push the zip files. And then it booted back into TWRP asking to allow modifications. I don't remember any of my devices doing that but I swiped yes and the rom booted.
One thing...there was an immediate notification telling me to update TWRP. I'm using the latest codeworks one so not sure if I should update or even if an update will work since I'm not on an official build. Have you encountered anything like this?

KLit75 said:
I now have codeworkx twrp, rooted with magisk. I gotta say I'm pretty impressed with stock but I KNOW I'm gonna want to flash a custom ROM soon and that's not a fast process when you're encrypted.
You said make a nandroid...have you ever restored just data from stock to a custom ROM? I may have but it's been awhile. I'm thinking I might have issues.
If I want to flash ROMs I'm going to need to format (better sooner than later) so from what I remember, I should:
1. Boot TWRP
2. Format data
3. Full wipe?
4. Adb push ROM, gapps, magisk
5. Flash all of them
I'm just hoping you or someone else can verify. I've got a lot of stuff to transfer over from my old phone but it makes no sense to do that now if I'm going to have to format. Thanks
UPDATE_
I got it. Running Dirty Unicorns now. It was a bit of an adventure. MTP would not work. Had to adb push the zip files. And then it booted back into TWRP asking to allow modifications. I don't remember any of my devices doing that but I swiped yes and the rom booted.
One thing...there was an immediate notification telling me to update TWRP. I'm using the latest codeworks one so not sure if I should update or even if an update will work since I'm not on an official build. Have you encountered anything like this?
Click to expand...
Click to collapse
@KLit75
Stock is indeed good ROM. Many people use Beta which is equally good.
Some Custom ROMs do some do not support encryption. You may have to
read a bit in the ROM threads. Some TWRP are better for encryption as
well. Official TWRP perhaps catched up. You may may have to read a bit
in the TWRP threads.
When I went OOS 5.0.4 -> Custom (GZOSP) I had to format data and
become unencrypted.
I then reinstalled phone from scratch but had Titanium backup (for
accounts etc...) and also /data/media/0 backup (for some media).
So no: I never fully restored data from stock to a custom ROM. I did
restore some app data from Titanium backup though.
I have not restored encrypted TWRP stock backup either. I probably
never will, but I had asked around and read about it for all
certainty.
I believe one needs a special step which is to clean via stock
recovery and flash stock. Then one can perhaps restore whatever
encrypted TWRP backup. I hear different versions of ROMS may have
different encryption mechanisms. I am not authoritative on Android
encryption, read other threads.
You will need to search and ask if you want to go back to encrypted.
Perhaps it is easier than I tell here.
Note that I had backups (Titanium media TWRP) copied over to computer
for all certainty. I sometimes also work with OTG stick for copying in
both directions.
I think almost no experience is same for 2 people. That's why we all
tell slightly different stories. Trying to understand and master the
procedures is the challenge, and have many backups, and a way back.
No TWRP ever asked me to upgrade. I allow TWRP to make modifications.
My computer is Linux and I do not use MTP.
You can stay on codeworkx TWRP. Myself I did so but, eventually, since
I am unencrypted, I now am on official twrp-3.2.1-2-dumpling.
Recall also it is advised to always turn off lock screen Security
before taking a TWRP backup.
Good luck and enjoy your 5T.

HTC 10 decryption issue but not before

so I updated my HTC 10 US unlocked to 8.0.. unlocked bootloader, S-ON, twrp 3.3.1 and I was able to decrypt using format data and I installed lineageos 16 and confirmed decryption..later I wanted to try the viper rom. I ended up re flashing stock rom then recovery, and when I went to format data it didn't work. No matter what I try and what sequence...i read as of now tarp can't decrypt. But I've done it before. I even tried older versions of twrp including the one that supposedly fixes this. Any advice would be great thanks

Warwick555 said:
so I updated my HTC 10 US unlocked to 8.0.. unlocked bootloader, S-ON, twrp 3.3.1 and I was able to decrypt using format data and I installed lineageos 16 and confirmed decryption..later I wanted to try the viper rom. I ended up re flashing stock rom then recovery, and when I went to format data it didn't work. No matter what I try and what sequence...i read as of now tarp can't decrypt. But I've done it before. I even tried older versions of twrp including the one that supposedly fixes this. Any advice would be great thanks
Click to expand...
Click to collapse
Read something about Nougat users being able to use twrp 3.2.3 as work around, but not oreo. This from memory, but check CaptainThrowback on Github to be sure. I'd drop a link here but not sure if that's cool?

AiNt said:
Read something about Nougat users being able to use twrp 3.2.3 as work around, but not oreo. This from memory, but check CaptainThrowback on Github to be sure. I'd drop a link here but not sure if that's cool?
Click to expand...
Click to collapse
ok, thanks. i thought about going back to nougat and going with Viper until this gets fixed. i just need to find the RUU zip and not exe, or learn how to extract it on a linux ubuntu which im new at also