Develop Bugs

A few questions regarding install custom ROMs

hi, i recently got an ATT note 2. The phone I got already got Clean ROM 3.5, so I presume it is rooted, with custom recovery (TWRP when I checked). I am thinking of flashing to a diff rom and just want to ask a few questions.
1-do I need to run triangle away every time I flash to a diff rom?
2-since the phone already has a custom rom, I should not have to root it, am I correct?
3-If I want to install custom, ROMs, can I just put the ROM in the external SD and flash it that way (of course with clear cash, davik, etc as states in the rom).
4-I am thinking of playing with the CleanROM 4.2.4 or the ACE version? any issue with either one compare to the 3.5 that I am using now? any recommendation?
5-anything I need ot watch out before I flash it? I have flashed a coupole of time with htc phone and this is my first samsung phone so I don't watn to brick it.
thanks a lot guys, XDA rocks.

PUTALE said:
hi, i recently got an ATT note 2. The phone I got already got Clean ROM 3.5, so I presume it is rooted, with custom recovery (TWRP when I checked). I am thinking of flashing to a diff rom and just want to ask a few questions.
1-do I need to run triangle away every time I flash to a diff rom?
2-since the phone already has a custom rom, I should not have to root it, am I correct?
3-If I want to install custom, ROMs, can I just put the ROM in the external SD and flash it that way (of course with clear cash, davik, etc as states in the rom).
4-I am thinking of playing with the CleanROM 4.2.4 or the ACE version? any issue with either one compare to the 3.5 that I am using now? any recommendation?
5-anything I need ot watch out before I flash it? I have flashed a coupole of time with htc phone and this is my first samsung phone so I don't watn to brick it.
thanks a lot guys, XDA rocks.
Click to expand...
Click to collapse
1. No you do not need to run triangle away usually only have to run it if you are going back to stock and may want to return the phone.
2.Nope it has a Rom you are rooted !
3.That is what I do when installing a new rom factory reset wipe davlik and cache and install you may have to fix permissions with some installs as well after installing.
4.From the bit I played with the new Clean rom it is very stable with minimum if any grief Jedi 9 is also a awesome ROM and my current fave.
5.Just read up lots before you do it follow every step they tell you to take your time it is easy just make sure ya know what you are doing before you start.
6.Enjoy they are a awesome phone !!

Thanks a lot for your prompt reply. It heped a lot. I will definitelycheck the roms. I am using 3.5 and it runs really good and hate to ruin it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

PUTALE said:
Thanks a lot for your prompt reply. It heped a lot. I will definitelycheck the roms. I am using 3.5 and it runs really good and hate to ruin it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
do a backup in twrp before flashing a new one, you can always come back

thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys

PUTALE said:
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
Click to expand...
Click to collapse
This is one of nice features of TWRP... ability to backup/restore individual partitions. Android stores various blocks in different partitions. To name a few, System, Data, Modem, Recovery, Boot, Cache, etc. If you just want to backup your modem for example, just check the "modem" box (and I recommend naming the folder to something significant so down the road you'll know which modem it is). When you restore, that folder will only have your modem.. so you can restore a different modem without having to change your rom, (etc). Kernels are stored in the "boot" partitions.. again, if you want to change kernels, backup the boot partition and name it properly if case you want to reflash that kernel. Generally, after my first flash of a new ROM, kernel, modem, I'll create a "boot" backup, "modem" backup, and ROM (system/data/boot) partition backups. If you look in the TWRP folders themselves, you can see the blocks which are backed up... or will be restored. Hope that helps.

PUTALE said:
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
Click to expand...
Click to collapse
When I back up in TWRP, I usually just go with what is default checked off. You will not mess up your root unless you really really tried to. The last time I ever had to flash back to stock then to a custom was on my Xperia X10a... You should be fine flashing a new rom without having to go back to stock as long as you do a good wipe (Wipe System, Factory Rest, Davlik, and Cache is what I do only because it doesn't hurt... I've read you do not need to do all those steps but I do them nonetheless). Do not use Triangle Away unless you plan on returning your phone or send it in for warranty. Only then should you start asking questions about that tool.
The only issue that may cause SOME confusion (not too much but some) is flashing back and forth between a 4.1.2 and a 4.2.1 since the SD card adjusts to User settings (some folders open up for individual users on 4.2 but as far as my experience goes, I have not had any issues with it, I just needed to study my SD card after each flash).
So you should be fine... just do backups, rename them to make sure you know which rom belongs to which backup, delete the old ones from the RESTORE menu in TWRP in case you are backing up the same rom to save you some space (my backups take around 2 gigs sometimes EACH) and you should be good to go... Enjoy tweaking out on your roms!

DoctorQMM said:
This is one of nice features of TWRP... ability to backup/restore individual partitions. Android stores various blocks in different partitions. To name a few, System, Data, Modem, Recovery, Boot, Cache, etc. If you just want to backup your modem for example, just check the "modem" box (and I recommend naming the folder to something significant so down the road you'll know which modem it is). When you restore, that folder will only have your modem.. so you can restore a different modem without having to change your rom, (etc). Kernels are stored in the "boot" partitions.. again, if you want to change kernels, backup the boot partition and name it properly if case you want to reflash that kernel. Generally, after my first flash of a new ROM, kernel, modem, I'll create a "boot" backup, "modem" backup, and ROM (system/data/boot) partition backups. If you look in the TWRP folders themselves, you can see the blocks which are backed up... or will be restored. Hope that helps.
Click to expand...
Click to collapse
Much appreciated for your detail explanation on the TWRP. I did a quick backup and selected all of the option and now I see the files in my external SD:
modem.emmc.win
data.ext4.win
cache.ext4.win
recovery.emmc.win
boot.emmc.win
efs.ext4.win
data.ext4.win
system.ext4.win
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
[email protected] said:
When I back up in TWRP, I usually just go with what is default checked off. You will not mess up your root unless you really really tried to. The last time I ever had to flash back to stock then to a custom was on my Xperia X10a... You should be fine flashing a new rom without having to go back to stock as long as you do a good wipe (Wipe System, Factory Rest, Davlik, and Cache is what I do only because it doesn't hurt... I've read you do not need to do all those steps but I do them nonetheless). Do not use Triangle Away unless you plan on returning your phone or send it in for warranty. Only then should you start asking questions about that tool.
The only issue that may cause SOME confusion (not too much but some) is flashing back and forth between a 4.1.2 and a 4.2.1 since the SD card adjusts to User settings (some folders open up for individual users on 4.2 but as far as my experience goes, I have not had any issues with it, I just needed to study my SD card after each flash).
So you should be fine... just do backups, rename them to make sure you know which rom belongs to which backup, delete the old ones from the RESTORE menu in TWRP in case you are backing up the same rom to save you some space (my backups take around 2 gigs sometimes EACH) and you should be good to go... Enjoy tweaking out on your roms!
Click to expand...
Click to collapse
thanks for the info/warning on the triangle. I read that it can brick the phone and also needs to be on the stock to use it. Also read that if there's too many counts, it may not work. I guess for now, I just won't touch it.
Since there's no 4.2 roms available (at least not what I have seen and want to play, CleanRom or Jedi as they are highly rated), I guess for now I do not have to worry much on the SD card issue. It will be safer I guess for now just stick with 4.1.2 until the kinks are worked out.
For the wipe system, factory, davlik, cache, do I do that before flashing it?watched a couple of video and instruction and they all have diff answers. Some people said do factory reset, flash, and then wipe davik and cache.
Again, really really appreciate all of the support guys.

PUTALE said:
Much appreciated for your detail explanation on the TWRP. I did a quick backup and selected all of the option and now I see the files in my external SD:
modem.emmc.win
data.ext4.win
cache.ext4.win
recovery.emmc.win
boot.emmc.win
efs.ext4.win
data.ext4.win
system.ext4.win
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
thanks for the info/warning on the triangle. I read that it can brick the phone and also needs to be on the stock to use it. Also read that if there's too many counts, it may not work. I guess for now, I just won't touch it.
Since there's no 4.2 roms available (at least not what I have seen and want to play, CleanRom or Jedi as they are highly rated), I guess for now I do not have to worry much on the SD card issue. It will be safer I guess for now just stick with 4.1.2 until the kinks are worked out.
For the wipe system, factory, davlik, cache, do I do that before flashing it?watched a couple of video and instruction and they all have diff answers. Some people said do factory reset, flash, and then wipe davik and cache.
Again, really really appreciate all of the support guys.
Click to expand...
Click to collapse
Think of your Nandroid (TWRP) backup as a roll back to what you are comfortable with (check everything off so you do not lose a thing if you want) in case you find that the new thing you flashed isn't all that it was cracked up to be for you or something messes up. The Nandroid backup is EVERYONE's friend.
As for flashing a new ROM and having to start all over, I will use this as an example: I have two backups; one for Paranoid Android (4.2.1 AOSPA) and Clean 4.2.5 (4.1.2). When I originally flashed my stock to Clean, I must've gotten lucky by just wiping the system (ROM only and not a factory reset) and all my data transferred over just fine with no issues... but when flashing to PA, I had to do a full wipe then start from scratch (which was not bad if you sync your apps and contacts thru Google). Also, you might want to get another backup system such as Super Backup to back up your contacts and SMS messages (be careful with backing up call logs if you go to 4.2.1 ROMs because for some reason, things went wacky for me). Titanium is a good system to use for power users but sometimes, to keep it as simple as possible, count on Google at first for your app syncing (and if you get Amazon App Store, you will have to get that APK to download the apps from that store).
Anyway, from there (if you want to play with multiple ROMs) you now have a foundation. Dirty flashing (flashing a new version of a ROM you currently have without doing a full wipe... just in case you didn't know... for me, I just wipe System [no factory reset] then flash the upgrade) should be fine... again, I'm typing from experience because there are some people who do run into issues dirty flashing and is usually not supported by the devs unless you do a full wipe and flash. I have not had any issues whatsoever dirty flashing both PA and Clean versions.
As for methods of wiping, honestly they're all right... I just posted what I usually do when I want to do a full wipe. Only if you want to do a dirty flash, you won't have to wipe or do a partial wipe (I partial wipe e.g. Clean 4.0.5 to 4.2.5: Delete last Clean Rom backup through the Restore menu, Nandroid Back Up current working Clean Rom 4.0.5, Wipe System, Install the new 4.2.5, wipe Davlik and Cache (again, I do this just in case but some devs say it's unnecessary), then reboot and wait for the apps to reset... all was where it was when I left 4.0.5.

PUTALE said:
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
Click to expand...
Click to collapse
Yes... if you're retaining your current modem and recovery... to restore a rom just as it was when you backed it up, restore boot (which has the kernel), system and data. One your second question, when restoring a different rom , it's best to always restore system/data/boot together. You can use TiBu to restore your user app DATA, and individual apps usually have their own backup files you can restore (like Nova/Apex launchers [which can restore your widgets], calendar, etc).

much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?

PUTALE said:
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
Click to expand...
Click to collapse
I have never used that rom so I can't say for sure. Try it out and see what happens. If you don't like it, restore your backup.

PUTALE said:
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
Click to expand...
Click to collapse
That rom is one of the most recent 7105 (note2 international) samsung firmware releases... supposedly better battery life than LL7 or LL4. It's the stock MA6 pre rooted (i.e., has SuperSU app and binaries included). No other features added like you would find with CleanROM 4.2.5 for example. It includes rom and kernel... so it will write to your system, data, and boot partitions. Whatever custom recovery you have now and flash this with will not be touched.

thanks again.

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
​So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
​I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.

You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.

Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.

If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?

mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.

tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?

mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.

Wrong password after restore nandroid backup / flashing new rom

I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?

ostvarivanje said:
I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?
Click to expand...
Click to collapse
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.

preference said:
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.
Click to expand...
Click to collapse
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close

ostvarivanje said:
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close
Click to expand...
Click to collapse
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup

preference said:
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup
Click to expand...
Click to collapse
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.

ostvarivanje said:
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.
Click to expand...
Click to collapse
Which twrp are you using? Are you on the latest from codeworkx

preference said:
Which twrp are you using? Are you on the latest from codeworkx
Click to expand...
Click to collapse
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem

ostvarivanje said:
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem
Click to expand...
Click to collapse
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?

preference said:
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?
Click to expand...
Click to collapse
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?

ostvarivanje said:
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?
Click to expand...
Click to collapse
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.

preference said:
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.
Click to expand...
Click to collapse
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.

ostvarivanje said:
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.
Click to expand...
Click to collapse
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.

preference said:
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.
Click to expand...
Click to collapse
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!

ostvarivanje said:
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!
Click to expand...
Click to collapse
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.

preference said:
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.
Click to expand...
Click to collapse
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?

ostvarivanje said:
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?
Click to expand...
Click to collapse
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.

preference said:
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.
Click to expand...
Click to collapse
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.

ostvarivanje said:
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.
Click to expand...
Click to collapse
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)

preference said:
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)
Click to expand...
Click to collapse
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!

ostvarivanje said:
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!
Click to expand...
Click to collapse
You can't use normal wipe, go to wipe then choose the option on the right (I think it says wipe device) and then it will tell you to type "yes". If you type yes then hit enter it will format the phone. That's a true format and it will decrypt your device. You can't just wipe all partitions because it's not a complete format.
So if you typed "yes" in TWRP you have a formatted phone. It will stay decrypted until you flash an encrypted rom.
So if you flash DU, you don't need no verity because the rom is decrypted. If you flash RR 6.0 then your phone will encrypt UNLESS you flash no verity. So the file I gave you is a way to stop encryption on encrypted roms.
You flash RR 6.0, gapps, no verity = RR but no encryption.
You flash DU, gapps = decrypted rom so you don't need no verity zip
Most roms are encrypted, so you flash rom, gapps, no verity to stay decrypted. The zip I gave you should be flashed after flashing rom and gapps on every encrypted rom if you want to stay decrypted.

Stuck with Twrp booting

Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!

Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".

Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse

Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?

lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?

I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.

stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs

blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.

Safe to upgrade to Pie unlocked now?

Hi,
I have read that upgrading to Pie on an unlocked OP3 will wipe the phone - maybe worse, brick it.
I would like to find out:
a) the status on this (is it fixed in newer releases? Is it planned to be "fixed" or not?)
b) What is the process to upgrade safely (if we need to "re-lock" then upgrade, etc.) and what the repercussions would be (e.g. when you re-lock the BL it wipes your phone)
FYI - I have sock bootloader, stock recovery and stock OS image (even un-rooted before last upgrade), so everything is "correct" except the bootloader is unlocked.
I think these 2 questiosn are everything people need to know to make decisions on upgrading.
I've been scared to upgrade, even though it keeps asking me to, because there are a couple things I don't have backed up yet, but I want to upgrade and try the new OS.
Thanks!
--mobrien

If you relock the device, it will wipe anyway. I upgraded my daughter's phone (my old OP3) last night and it required a wipe installing the ROM. A few thing I found:
With an unlocked bootloader, the OTA would not install. The full, stock ROM download would also not install via stock recovery or through adb.
I had to copy the full ROM to the sdcard, then perform manual install through stock recovery option. It installs, but afterwards it makes you wipe the device.
I mean, I'm sure could've flashed twrp and installed, but I was being lazy.
Sent from my Mi MIX 2S using Tapatalk

noobtoob said:
I mean, I'm sure could've flashed twrp and installed, but I was being lazy.
Click to expand...
Click to collapse
I've had great success booting TWRP over USB. Used to root my phone after every OTA and never changed any stock partitions, other than adding SuperSU to root.
So, are you saying you think installing via TWRP may not make you wipe? (I don't think that's what you are saying, just being hopeful - I also think that TWRP flash even requires wipe more than OTAs usually do.

mobrien118 said:
So, are you saying you think installing via TWRP may not make you wipe? (I don't think that's what you are saying, just being hopeful - I also think that TWRP flash even requires wipe more than OTAs usually do.
Click to expand...
Click to collapse
Sorry man, I haven't a clue. Was hoping getting it to install via the stock recovery wouldn't have wiped it, but that turned up to be a wash. I honestly didn't check into it any further cause my daughter doesn't root or anything, just runs stock, so the priority was just that, get it to boot on the new OS. I back everything up myself, so restoring her stuff wasn't an issue.
If you are rooted but still running stock, why don't you use the migrate app from play store? Back up your data, copy to PC, whatever, then upgrade, root, restore via migrate again. App works wonders and saves a ton of time restoring apps and settings.
Sent from my Mi MIX 2S using Tapatalk

noobtoob said:
If you are rooted but still running stock, why don't you use the migrate app from play store? Back up your data, copy to PC, whatever, then upgrade, root, restore via migrate again. App works wonders and saves a ton of time restoring apps and settings.
Click to expand...
Click to collapse
I haven't used the migrate app. I've always used Titanium Backup in the past, but I've decided to not root my new phone (I've been feeling that it isn't necessary as much anymore and:
I am tired of having to keep re-rooting after every patch
I want to use Google Pay
I'm sure I'll have other reasons to want a locked bootloader that I don't know about yet
I want this phone un-rooted and locked, because I'm giving it to my mom and she will not want to deal with any of that - stock all the way is better for her.
I wonder if there is an app that will allow me to restore without root, even though I could still root my phone that I'm backing up *from*. I just want to migrate the apps to my new phone, but I don't want to wipe it, either, and it is not unlocked. Helium does not seem to work to restore to different hardware (or maybe it just doesn't work at all anymore).