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.
Related
Someone please explain this to me. Idk if it's because I've been out of the rooted/custom rim game for so long or if I've gotten dumber in my old age. Also this is the first ohone I've ever had to even think about it with.
So I:
Boot into TWRP
wipe /data
Boot back into os
Profit?
Or boot back into TWRP
Flash dm-whatever the hell it's called
Boot into os
Profit?
Also, is any if this necessary at all just to flash a different rom? Being encrypted has no bearing on my life, so I don't care if I am or not.
EDIT: I'm currently going back thru old posts so I'll delete if I find my answer before there's a reply.
If you've installed TWRP you can just flash a custom ROM unless the ROM says something about "dm-verity required [disabled/enabled]". Disabled, means no encryption. Enabled is encrypted.
Any time you flash a different ROM you need to Factory Reset. Otherwise CustomROM 1.2 to 1.3 is usually safe to dirty flash (no data wipe).
Ok. Just making sure I wasn't screwing up by flashing like I normally would:
Wipe
Rom
Gapps
Root
Reboot
Verity if it says to in the OP of the rom thread.
How does this dm-verity business work? Whenever I try to flash a later OOS version without a "format" when it boots I always get the encryption failed message. Will flashing the dm-verity .zip fix that?
This phone is a real pain in the backside to flash with. TWRP backups usually fail, encryption issues and all that stuff. On my last phone it was flash and forget. What happened?
TangledAbstact said:
How does this dm-verity business work? Whenever I try to flash a later OOS version without a "format" when it boots I always get the encryption failed message. Will flashing the dm-verity .zip fix that?
This phone is a real pain in the backside to flash with. TWRP backups usually fail, encryption issues and all that stuff. On my last phone it was flash and forget. What happened?
Click to expand...
Click to collapse
You only need to flash no-dm-verity if you want to run an unencrypted rom. All OOS ROMs are encrypted so of course you're going to get encryption failed. Omni has encryption and so does Liquid Remix now, so you don't need the verity file at all, unless you want to stay unencrypted on a ROM that supports it. Since you have been decrypted by flashing the verity file, if you want to go back to OOS, you will now need to format data (at the bottom right in wipe menu) in TWRP after flashing OOS. This will wipe all user data. DO NOT flash no-dm-verity again! If you think this phone's complicated, don't buy an Essential or any device with A/B partitions, it's a nightmare.
Edit: Actually I'm not sure if you can run OOS unencrypted or not (never tried), but if you want to restore factory encryption an flash back to stock, you have to restore the stock recovery. This guide by The Doctor will help you: https://forum.xda-developers.com/oneplus-5t/how-to/how-to-revert-to-oos-oreo-8-1-t3730952/page4
If you just want to run a custom ROM encrypted, formatting data in TWRP should work.
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.
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.
Hey guys and gals!
So I don't wanna keep posting on other ROM threads to be annoying, so I will create a thread of my own. How do one flash the system_ext.img coming from Stock (root) ? I absolutely cannot get any TWRP versions (Chinese or English) to function. I take my passcode off and it's always 0mb. Doesn't matter if I am on a custom ROM or not. It's just something I cannot get to work. ONE time, it seen my storage but it would not flash a ROM. SO how can I flash this image via fastboot?
Global version of OOS. Although, I am currently on EXTENDED. I said Stock because I'll always have a Crash Dump, and need to start over. It's also tiresome to flash YAAP (12-18-20) then use the updater to create the image. Again, some things with this device, I'm getting used to. I'm all for learning and testing everything. I just cannot find a way to flash this image or get TWRP to function.
Have a great day!
So I would suggest you update your fastboot tools, because once you have the partition created assuming you are coming from a rom that has the system ext img it shouldn't be a problem. For example this is what I did, I was on RR remix so twrp chinese was working ( by the way I don't know why it wouldn't work for you if it works for everyone else) from there its just a matter of flashing the zip that contains the img. You can try derp,evox, yaap etc. After that again just flash what ever rom you desire it shouldn't be any issues. Also to keep in mind that a11 with twrp does not work with a pin only with a pattern, even tho I have read you said you have no pin lock. Wouldn't really know why your device would be the case but you can try that out .
lil_kujo said:
So I would suggest you update your fastboot tools, because once you have the partition created assuming you are coming from a rom that has the system ext img it shouldn't be a problem. For example this is what I did, I was on RR remix so twrp chinese was working ( by the way I don't know why it wouldn't work for you if it works for everyone else) from there its just a matter of flashing the zip that contains the img. You can try derp,evox, yaap etc. After that again just flash what ever rom you desire it shouldn't be any issues. Also to keep in mind that a11 with twrp does not work with a pin only with a pattern, even tho I have read you said you have no pin lock. Wouldn't really know why your device would be the case but you can try that out .
Click to expand...
Click to collapse
Sorry for the delay. Wish XDA would alert me, better. So Chinese TWRP is working now, on XTEND. I dunno, sometimes it works and sometimes I get 0mb. I think that point, to go onto a ROM WITH that image, should be fine. Since I always had troubles, I'd only fastboot flash to different ROMs. Trust me, for all my time on Android, this device is making me needy and a big newb. I just waiting for that "then don't bother to flash anything and shut up" LOL! BUT then again, I'm not on r/jailbreak. So once the partition is created, I can go to a ROM without that image? Do you know how I can check? Because I would like to just flash Hydrogen but don't wanna jump to stock. I think I can just flash a ROM with it and reboot back to the bootloader without setting up, right?
draymond1987 said:
Sorry for the delay. Wish XDA would alert me, better. So Chinese TWRP is working now, on XTEND. I dunno, sometimes it works and sometimes I get 0mb. I think that point, to go onto a ROM WITH that image, should be fine. Since I always had troubles, I'd only fastboot flash to different ROMs. Trust me, for all my time on Android, this device is making me needy and a big newb. I just waiting for that "then don't bother to flash anything and shut up" LOL! BUT then again, I'm not on r/jailbreak. So once the partition is created, I can go to a ROM without that image? Do you know how I can check? Because I would like to just flash Hydrogen but don't wanna jump to stock. I think I can just flash a ROM with it and reboot back to the bootloader without setting up, right?
Click to expand...
Click to collapse
That img will always exist is part of android 11 so it will be the norm. Every rom in the future will have it as seen on some custom roms right now, I flashed the h2os from twrp since I was coming from derp. So I didnt go back to stock. When you flash that img a partition will be created so the space will be available for when you flash another rom. So in the case that for example you were on derp and decided to fastboot flash h2os 11 you will not have issues flashing with fastboot commands the system_ext to both slots. ( By the way you need to specify which slot so I recommend you have a custom rom prior on both slots better if it's a11 rom.) The command fastboot flash system_ext_a system_ext.img and system_ext_b system_ext.img is to be used when doing it with fastboot command from fastbootd. If you decide to go with twrp from any custom rom a11 like the ones mentioned before just flash and right after you flash format data. You will lose twrp since the zip has the new recovery from oneplus. Reboot to recovery and again format data reboot enjoy. If you want to use just regular fastboot method you have to flash every img in the zip like 23 or so don't rememeber in order for it to work. So to make it simple for you. Flash a custom a11 rom with twrp if you are on a custom rom already. To both slots. After reboot and have the rom settle by letting it start to home screen. Save the zip of h2os to the phone reboot to recovery flash h2os zip not don't reboot but in twrp go to wipe format data. Then reboot to recovery again it will reboot to stock recovery format data again reboot and enjoy.
You will still have a custom rom in the other slot and if you want to have the stock on both slots just use the ota system update form stock rom local upgrade
There you go it should be simple and quick it took me like ten minutes to set it up and flash yesterday. By the way despite being a beta I really enjoy h2os 11. Do expect some minor bugs since it's a beta build.
I'll leave a link so you can read about system_ext and android new partition going forward. https://source.android.com/devices/bootloader/partitions
lil_kujo said:
I'll leave a link so you can read about system_ext and android new partition going forward. https://source.android.com/devices/bootloader/partitions
Click to expand...
Click to collapse
You're a wealth of information! Thanks for helping me to understand!
Edit: I tried the installing of two ROMs but I couldn't get it. I tried XTEND and Derp. But I had trouble with Xtend not being able to boot after setting up Derp. I had to wipe data for it to boot. Then lost everything. Bleh.
Can I ask you for your recommendation for an A11 ROM to have on a slot?
draymond1987 said:
You're a wealth of information! Thanks for helping me to understand!
Edit: I tried the installing of two ROMs but I couldn't get it. I tried XTEND and Derp. But I had trouble with Xtend not being able to boot after setting up Derp. I had to wipe data for it to boot. Then lost everything. Bleh.
Click to expand...
Click to collapse
So just to give you some more context, when you have to different rom on each slot is normal you have to format data, one : because they might have different data format , example oneplus only supports ext4 while derp is f2fs. So when flashing derp and the other slot is xtended is expected you will have to format in some occasions it might boot but you will have a buggy experience. So now that you have two custom roms and twrp try flashing h2os and again always format data and format data again in stock recovery since that will change the data format to ext4.
draymond1987 said:
Can I ask you for your recommendation for an A11 ROM to have on a slot?
Click to expand...
Click to collapse
Derp works perfect, that is the one I was coming from.
lil_kujo said:
So just to give you some more context, when you have to different rom on each slot is normal you have to format data, one : because they might have different data format , example oneplus only supports ext4 while derp is f2fs. So when flashing derp and the other slot is xtended is expected you will have to format in some occasions it might boot but you will have a buggy experience. So now that you have to custom roms and twrp try flashing h2os and again always format data and format data again in stock recovery since that will change the data format to ext4.
Click to expand...
Click to collapse
So I can have derp AND Hydro running? But like, when I format data, it was a full data wipe. I guess what you're talking about, right? Like I said, both ROMs kinda worked but it force a "fastboot -w". Maybe since I can get TWRP to work, I can wipe data there, and not touch user data?
draymond1987 said:
So I can have derp AND Hydro running? But like, when I format data, it was a full data wipe. I guess what you're talking about, right? Like I said, both ROMs kinda worked but it force a "fastboot -w". Maybe since I can get TWRP to work, I can wipe data there, and not touch user data?
Click to expand...
Click to collapse
On 7t there is no such thing as dual boot you can have of course one rom in one slot and another different slot on the other slot and it would work, also when you fastboot -w you are not erasing the imgs, you are erasing user data. The imgs from the rom will always be there until you change them. There is no way of saving data because of what i mentioned before of the different dat file ext4 and f2fs, when you are on stock it will "make data work for it but not for other roms" because of the decryption issue for one and second because of the format ext4. The only two roms i have tried so far that you can have dual boot are EVO x and Derp because there code is so similar coming from the same dev. SO to answer your question, Yes you can have two different ROMS but the rom that you use for setup that will be the one that will take over, in this case stock will take over data, which means you wont be able to use the other slot till you format data again and get rid of the encryption so that the other rom can use data partition. I know it sounds complicated but it really is very simple.
It is rather simple. I did notice a few people using those ROMs in slots. I mean, it's not a big deal if I can have two ROMs. I do miss the days of dual booting though.
May I ask, and this isn't to make a ROM work with Stock on a slot. Can you convert the file system to F2FS? I stumbled across a ROM that said it was better on this device but I can't find that post.
draymond1987 said:
It is rather simple. I did notice a few people using those ROMs in slots. I mean, it's not a big deal if I can have two ROMs. I do miss the days of dual booting though.
May I ask, and this isn't to make a ROM work with Stock on a slot. Can you convert the file system to F2FS? I stumbled across a ROM that said it was better on this device but I can't find that post.
Click to expand...
Click to collapse
yes you can, it depends, if the rom supports it. the fastboot way is way to complicated so twrp is the best option, when you choose wipe you will see a setting that says advanced, from there you choose data and click the option change format or repair then you will see some options. do note that when you change the type it will erase your data. do note that only data will change your system data will still be ext4.
lil_kujo said:
yes you can, it depends, if the rom supports it. the fastboot way is way to complicated so twrp is the best option, when you choose wipe you will see a setting that says advanced, from there you choose data and click the option change format or repair then you will see some options. do note that when you change the type it will erase your data. do note that only data will change your system data will still be ext4.
Click to expand...
Click to collapse
Ahh okay, I think I understand a little better now. Thanks for everything so far!
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Try going into BOOTLOADER to use fastboot instead of fastboot(d), if at all possible.
force reboot to twrp
then wipe cache, select reboot then select system
Raunaksaha2008 said:
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Click to expand...
Click to collapse
I'm glad you posted this, I did the exact same thing yesterday and had the exact same problem. I'm Normally extremely experienced with this stuff I've even made custom roms. This one caught me off guard because I've only had the phone 2 weeks and this was the 2nd custom rom I flashed. Long story short nothing worked and I had to flash miflash stock firmware. Than I tried it again and it did it again. So I flashed the zip before I was already on and everything worked. I don't understand backups with this phone sometimes they backup but I don't believe they will work to restore.
I have never had to say this, there is nothing you can do. You have to flash stock and go back it sucks and I hate it but it is what it is.
hroen_al said:
force reboot to twrp
then wipe cache, select reboot then select system
Click to expand...
Click to collapse
Tried, didn't work
Raunaksaha2008 said:
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Click to expand...
Click to collapse
now its not booting into recovery. only fastboot. run twrp bat command file is not working with it anymore.
Raunaksaha2008 said:
now its not booting into recovery. only fastboot. run twrp bat command file is not working with it anymore.
Click to expand...
Click to collapse
could boot into recovery. backed up whatever i could. flashed fastboot xiaomi.eu rom without data wipe (upgrade mode). System was showing issues - permissions stopped working, couldnt find refresh rate settings, apps were misbehaving, general lag. Now trying to flash again with data wipe. If nothing else works, have to go back to original stock rom with mi flash.
Raunaksaha2008 said:
could boot into recovery. backed up whatever i could. flashed fastboot xiaomi.eu rom without data wipe (upgrade mode). System was showing issues - permissions stopped working, couldnt find refresh rate settings, apps were misbehaving, general lag. Now trying to flash again with data wipe. If nothing else works, have to go back to original stock rom with mi flash.
Click to expand...
Click to collapse
Well did it work or did you have to go back to stock? I told you nothing works and I'm not lying I'm extremely experienced with this stuff. I root every device I can get my hands on. This phone is beyond difficult to flash roms with. The problem is you really need to go back to stock everytime you flash a custom rom to make sure it works.
I know when I said my first comment your hoping to god that you don't have to start from scratch but I tried a bunch of stuff to I just didn't feel like explaining it all. I flashed both twrps and tried I reflshed the rom and I did format data and still didn't work. It screws up the system partition layout and nothing reads right.
Went back to stock. Android 12 on xiaomi.eu rom doesn't have refresh rate settings and we are stuck on 60Hz. And also backing up, restoring everytime is a pain and waste of time. Will stick to stock for now.
Raunaksaha2008 said:
Went back to stock. Android 12 on xiaomi.eu rom doesn't have refresh rate settings and we are stuck on 60Hz. And also backing up, restoring everytime is a pain and waste of time. Will stick to stock for now.
Click to expand...
Click to collapse
I told you, I will say it again this phone for custom roms kinda sucks. It can be done but it's always you have to start from scratch Everytime and roll the dice and hope it works. Good luck I would still root stock though
The way everything breaks made me worried that the phone would hard brick if I kept trying stuff. Either that or some how wipe out fastboot and than it would be like a hard brick because nothing would work to fix it. It's a scary phone to mess with. The problem comes from the A/B partitions because XDA developers aren't really developers their just people who read online instructions on putting source code together and don't actually know how to code or fix anything. They get way to much credit. Topjohnwu is a real developer and that's why Google bought him
Facing issues again. Netflix app not showing in Play store. Device is not play protect certified even after flashing official Rom via mi flash.
Techguy777 said:
The way everything breaks made me worried that the phone would hard brick if I kept trying stuff. Either that or some how wipe out fastboot and than it would be like a hard brick because nothing would work to fix it. It's a scary phone to mess with. The problem comes from the A/B partitions because XDA developers aren't really developers their just people who read online instructions on putting source code together and don't actually know how to code or fix anything. They get way to much credit. Topjohnwu is a real developer and that's why Google bought him
Click to expand...
Click to collapse
i agree, flashing stock each time and booting once before flashing each custom rom seems the way to go. i know you're experienced - more than i - but in case you don't know... here's a couple of good apps for backing up apps etc that have worked well when moving from rom to rom (just save/copy whole swiftbackup folder with backed up apps to pc/laptop).
after moving rom, i select 'restore' from google backup but deselect apps (that's all done with seperate app below). that restores a fair bit, including some settings depending on the rom before and after flash. then install swift backup on my rooted device, copy swiftbackup folder back onto phone and restore apps with all data etc (+ anything else you have that didn't restore from google backup). swiftbackup can even backup and restore your wallpaper/screensaver, wifi passwords etc. it's so much better than the outdated titanium backup, which i find unreliable these days.
another alternative is alpha backup pro, another paid app but apparently worth it. sometimes it's on offer or free. i got it when it was free but haven't tried it as swift works well for me. alpha backup
note: i am not affiliated with either of these apps, just making you aware of a backup alternative as TWRP data backups, for me and with this phone, are a no go. also note, i don't backup system stuff when moving to a different rom, only installed apps.
like i say, no doubt you are aware of these options but thought i would post just in case.
reg66 said:
i agree, flashing stock each time and booting once before flashing each custom rom seems the way to go. i know you're experienced - more than i - but in case you don't know... here's a couple of good apps for backing up apps etc that have worked well when moving from rom to rom (just save/copy whole swiftbackup folder with backed up apps to pc/laptop).
after moving rom, i select 'restore' from google backup but deselect apps (that's all done with seperate app below). that restores a fair bit, including some settings depending on the rom before and after flash. then install swift backup on my rooted device, copy swiftbackup folder back onto phone and restore apps with all data etc (+ anything else you have that didn't restore from google backup). swiftbackup can even backup and restore your wallpaper/screensaver, wifi passwords etc. it's so much better than the outdated titanium backup, which i find unreliable these days.
another alternative is alpha backup pro, another paid app but apparently worth it. sometimes it's on offer or free. i got it when it was free but haven't tried it as swift works well for me. alpha backup
note: i am not affiliated with either of these apps, just making you aware of a backup alternative as TWRP data backups, for me and with this phone, are a no go. also note, i don't backup system stuff when moving to a different rom, only installed apps.
like i say, no doubt you are aware of these options but thought i would post just in case.
Click to expand...
Click to collapse
I am using swift backup right now actually as I was reading this and yes I do the same thing copy folder to the USB C drive. It's the only app I've bought in a year. Thank you for at least making a comment of some depth. I get burned out at xda because everyone doesn't say anything they just want answers for their problems and don't contribute to xda.
I did not know about the other app so I will be looking into it. Normally I wouldn't say this but buy Swift back and you get cloud storage. I'm like you I restore apps with an app and I will be using Xiaomi cloud now but also Google. Another app is migrate it's the best for flashing roms it restores your apps and data from twrp well not quite once you reboot.
I thanl you again because maybe I didn't know about Swift back it's important people respond.
Is 120Hz working on your mi11x with xiaomi.eu? It doesn't work on mine.
chratoc said:
Is 120Hz working on your mi11x with xiaomi.eu? It doesn't work on mine.
Click to expand...
Click to collapse
Yes it is, on the latest stable but not on the latest Android 12 beta.