Related
Dear all:
I would like to open this Q&A thread as I am experiencing the same behaviour described in this post.
When I select the menu option "Encrypt phone" in the Security menu, confirm the device pin, and confirm that the encryption should start (in all tests, the battery was at 95+ % at this point), the device restarts, briefly displays the twisted Android logo, then the LineageOS boot animation for less than one minute, and then restarts again.
This second restart leads to a boot loop where only the white HTC/powered by Android screen (including the red warning text) is displayed for a few seconds before the device briefly vibrates and restarts. I can break this boot loop only by holding the volume up, volume down, and power buttons until the device enters the bootloader. I can then boot to recovery and restore the backup I had created before attempting to encrypt the device.
This issue has only occurred since I changed from the last available CyanogenMod 13.0 nightly (cm-13.0-20161218-NIGHTLY-himaul) to the first LineageOS 14.1 nightly (lineage-14.1-20170411-nightly-himaul-signed). It also occurs using the latest LineageOS 14.1 nightly (lineage-14.1-20170418-nightly-himaul-signed).
My configuration is as follows:
HTC One M9 (himaul), bootloader unlocked, S-ON
Recovery: TWRP 3.1.0.0 (twrp-3.1.0-0-hima.img)
LineageOS versions affected: lineage-14.1-20170411-nightly-himaul-signed and lineage-14.1-20170418-nightly-himaul-signed
Device PIN: 8 digits, digits only, no other characters
External SD card: present
Prior to upgrading from CyanogenMod 13.0 to LineageOS 14.1, my device was on HTC firmware 3.35.401.32. The recovery was also TWRP 3.1.0.0. TWRP was able to decrypt my data partition.
In preparation for the upgrade from CyanogenMod 13.0 to LineageOS 14.1, I prepared my device as follows:
Full device wipe, including formatting of data partition.
Installation of HTC firmware 4.14.401.7 (through 0PJAIMG.zip, not RUU).
Completion of HTC device setup using HTC firmware.
Successful OTA update to HTC firmware 4.28.401.3.
Installation of TWRP 3.1.0.0.
Full device wipe, including formatting of data partition.
Installation of LineageOS Nightly of 11 April.
Installation of OpenGApps Nano of 11 April.
In order to potentially exclude various factors that I thought might possibly contribute to the error, I tried the following:
Not selecting a lock screen PIN at all.
Using a simple 4-digit lockscreen PIN (1234).
Removing the external SD card prior to encryption.
Trying encryption with and without LineageOS SU addon.
Encrypting the device directly after the first LineageOS boot without any further setup or app installation.
Enabling and not enabling the developer options.
Removing the USB cable during first restart after encryption had begun.
I'm afraid I don't quite know what I could try next. Does anyone have any ideas, or is there some kind of troubleshooting I could attempt to help locate the cause of this behaviour?
I have converted several other devices (not owned by me) to LineageOS 14.1, mostly Samsung Galaxy SIII (GT-I9300) and Samsung Ace 3 LTE (GT-7275R), and none of them have exhibited a similar error.
Since reverting to CynogenMod 13.0 is not a real option, and I am quite uncomfortable leaving the device unencrypted, I would greatly appreciate any help or hint you may have. If you need any further information on my device or setup, please let me know. Thanks very much in advance.
Best regards,
Markus
Have you tried reflashing the rom?. Might be a bug or something.. Have you checked the bugs list?
Beamed in by telepathy.
shivadow said:
Have you tried reflashing the rom?. Might be a bug or something.. Have you checked the bugs list?
Click to expand...
Click to collapse
Yes, I tried reflashing twice. On the bugs list, I could not find an entry that could match this behaviour.
pleuhockle said:
Yes, I tried reflashing twice. On the bugs list, I could not find an entry that could match this behaviour.
Click to expand...
Click to collapse
Would it perhaps be better to open a bug report in jira.lineageos.org? I assume in in this case, it would be a bug report rather than a regression report as the encryption never worked for me in LineageOS 14.1.
pleuhockle said:
Yes, I tried reflashing twice. On the bugs list, I could not find an entry that could match this behaviour.
Click to expand...
Click to collapse
Today, I also tried the following:
I directly flashed the latest HTC firmware and encrypted the phone storage in the HTC firmware using the same PIN I also use in LineageOS. This encryption was successful. I then installed TWRP (TWRP was able to decrypt with the PIN) and restored my latest LineageOS 14.1 backup, using the rm -rf option in TWRP so the partition contents would be removed, but the partitions would not be reformatted. LineageOS then booted to the "Enter PIN to start Android" screen but was unable to decrypt using the PIN I had previously successfully used in TWRP. After this boot attempt, TWRP was also unable to decrypt using the PIN.
I then tried flashing the latest HTC firmware and booting only into the firmware without encrypting the phone. I then restored the backup in TWRP again using the option rm -rf. When I then tried to encrypt my device from LineageOS, the same boot loop resulted.
I will try to gather logcat data next but am concerned that, during the boot loop, the device may not boot far enough to allow for logcat data collection via adb.
pleuhockle said:
I will try to gather logcat data next but am concerned that, during the boot loop, the device may not boot far enough to allow for logcat data collection via adb.
Click to expand...
Click to collapse
I have been able to gather logcat data, however, as I suspected, I cannot gather any data during the boot loop. I was able to copy kernel and recovery log data to the external SD card from TWRP after breaking the boot loop and before restoring the backup. I'm attaching the (redacted) log files - due to the size limitation, I had to ZIP the logcat data.
As soon as the weekly/nightly bug reports open for new submissions again, I will file a bug report, but perhaps there is something in the logs that would give any of you an indication as to what may be the issue?
pleuhockle said:
As soon as the weekly/nightly bug reports open for new submissions again, I will file a bug report, but perhaps there is something in the logs that would give any of you an indication as to what may be the issue?
Click to expand...
Click to collapse
I have now created the bug report.
Have you seen this: https://forums.oneplus.net/threads/twrp-encryption-password.432114/
Beamed in by telepathy.
shivadow said:
Have you seen this: https://forums.oneplus.net/threads/twrp-encryption-password.432114/
Click to expand...
Click to collapse
Yes, I was familiar with these types of issues, and I am aware that earlier versions of TWRP sometimes had issues decrypting the data partition on himaul devices even if the correct password was used. The issue described in this other thread is different from mine, though. Before migrating to LOS 14.1, I was using the last available nightly build of CM 13.0 (18 December 2016) with TWRP 3.1.0. as the recovery. This combination did not cause any encryption issues. I reinstalled CM 13.0 in early January, and after this reinstallation (which involved formatting the data partition as well), I could encrypt the device without any issues, and TWRP was also able to decrypt the data partition using the correct pin.
The encryption issue only occurred after the first installation of the first nightly build of LOS 14.1 (11 April). I do hope the log data will contain some information that could help identify the issue - I'm at a loss as to what else I could try.
building for test
I checked with lukl33t and this issue was eventually resolved by removing hardware cryptography capability entirely. Ive set up a test environment and have a new build of 14.x nightly (unofficial) if anyone wants it.
Im also trying to test adding HW crypto again to see if the issue has been resolved. I believe it may have been caused by protected drivers and firmware on the device between version 6 and 7 of android, as this is when Google began their move from LUKS full disk encryption to a more staged file-based crypto model. For users experiencing this issue, is the phone S-OFF or S-ON?
RUU upgrades to 7 on this phone include a bundle of signed drivers specific to the SOC that may be the key to resolving HW crypto issues.
nimbius said:
I checked with lukl33t and this issue was eventually resolved by removing hardware cryptography capability entirely. Ive set up a test environment and have a new build of 14.x nightly (unofficial) if anyone wants it.
Im also trying to test adding HW crypto again to see if the issue has been resolved. I believe it may have been caused by protected drivers and firmware on the device between version 6 and 7 of android, as this is when Google began their move from LUKS full disk encryption to a more staged file-based crypto model. For users experiencing this issue, is the phone S-OFF or S-ON?
RUU upgrades to 7 on this phone include a bundle of signed drivers specific to the SOC that may be the key to resolving HW crypto issues.
Click to expand...
Click to collapse
Thanks @nimbius for working on this issue. Did you make progress with trying out hardware encryption yet?
And in the meantime, maybe you should ask for re-adding himaul to the list of officially built devices in LineageOS, now that disk encryption (at least software-based) works again? The current situation is a bit unfortunate, with no LinageOS updates for the phone at all.
comolik said:
Thanks @nimbius for working on this issue. Did you make progress with trying out hardware encryption yet?
And in the meantime, maybe you should ask for re-adding himaul to the list of officially built devices in LineageOS, now that disk encryption (at least software-based) works again? The current situation is a bit unfortunate, with no LinageOS updates for the phone at all.
Click to expand...
Click to collapse
HW encryption seems to work on my LOS 15.1 builds, so maybe get it a try. But you'll need to update to TWRP 3.2.2.
Hi,
I try to install LineageOS 14.1 + Magisk 15.0 without encryption on Data, but it always is encrypted after installation again.
Here are the steps I take:
1. Install TWRP 3.2.1-0
2. Boot into TWRP recovery (getting prompted to enter pattern so it can decrypt data)
3. Format Data (forced to type "yes" , so did not only wipe it)
4. Reboot into recovery to proove that I am unencrypted now (not prompted again for the pattern again)
5. Install LineageOS 14.1
6. Install Magisk 15.0
7. Install Google Apps
8. Reboot into system, installing LineageOS, some apps, etc.
The next time I boot into recovery, I get prompted for the pattern so I guess my Data partition is encrypted again.
I tried several variants of install packages, also the "no-enforce-encrypt-no-verify" package (after installing LineageOS), but got no luck so far.
Please could someone tell me what I am doing wrong and what to do to avoid encryption of data again?
Thank you!
fex42
fex42 said:
Hi,
I try to install LineageOS 14.1 + Magisk 15.0 without encryption on Data, but it always is encrypted after installation again.
Here are the steps I take:
1. Install TWRP 3.2.1-0
2. Boot into TWRP recovery (getting prompted to enter pattern so it can decrypt data)
3. Format Data (forced to type "yes" , so did not only wipe it)
4. Reboot into recovery to proove that I am unencrypted now (not prompted again for the pattern again)
5. Install LineageOS 14.1
6. Install Magisk 15.0
7. Install Google Apps
8. Reboot into system, installing LineageOS, some apps, etc.
The next time I boot into recovery, I get prompted for the pattern so I guess my Data partition is encrypted again.
I tried several variants of install packages, also the "no-enforce-encrypt-no-verify" package (after installing LineageOS), but got no luck so far.
Please could someone tell me what I am doing wrong and what to do to avoid encryption of data again?
Thank you!
fex42
Click to expand...
Click to collapse
Use this recovery:
Pendragon2000 said:
Use this recovery:
Click to expand...
Click to collapse
Thank you, but it seems not to be caused by my TWRP version (3.2.1-0). In the meantime I installed LineageOS 15.1 but did format data again just before rebooting and now data stays unencrypted (does not ask me for unlock pattern in TWRP). Even after installing Magisk v15.0 later, is stays unencrypted . But in MagiskManager there's the checkbox set "keep force encryption" - dont know if that does matter? On my Redmi Note 4 this checkbox is not set.
Same problem here with my Redmi K20 Pro. The problem occurred after I reboot my phone to uninstall FDE.AI magisk module. My phone then encrypts itself. Factory reset, format data, repair partition, re-flashing stock ROM doesn't solve the problem. Have you solved it yet?
Hello
I'm currently in a very tricky situation.
I've decided that I want to update my oneplus 3 (non t) to the newest lineageos 17.1 nightly build. I've been running lineageos 15.x before (I havent updated in a very, very long time).
These are the steps I took as best as I remember:
from a working state: boot into TWRP 3.3.0.1 , backup system & boot onto interal storage
then flash stable9.0.6 firmware + modem, flash lineage-17.1-20200615-nightly, flash gapps
then I wiped dalvik cache and cache and booted into system.
The boot process itself went fine, however I was greeted with a "decryption failed" screen which claimed that the decryption password was correct, but the data was corrupt. TWRP also claims that the default decryption password does not work (it has not asked me for any decryption password before) and entering my screen lock pattern according to the /faq/openrecoveryscript.html page on twrp(dot)me does not yield any different result either.
Since I've neglected to copy the backup to any other place other than internal storage, thinking that just a firmware and system flash would be no risk to it, I now have no way of restoring the previous state.
First I tried updating TWRP to the newest version (3.3.1.1) which yielded no difference, I attempted to flash both the old firmware (I know that it was 5.0.x, so I went with 5.0.8) and an old version of lineageos (some unofficial release of lineageos 15.1 from 2017 that I found on xda, since the official releases arent available that long) which resulted in a successful boot, but unsuccessful decryption just as with lineageos 17.
I have also attempted to follow the steps at /r/LineageOS/comments/anivml/ , though the backup fails silently (pc says `Now unlock your device and confirm the backup operation...`, nothing happens on my phone)
I would be thankful for any ideas on how I could recover from this without data loss.
I apologize for the weird links, but I am a new user and cant post external links yet
Lotzisty said:
Hello
I'm currently in a very tricky situation.
I've decided that I want to update my oneplus 3 (non t) to the newest lineageos 17.1 nightly build. I've been running lineageos 15.x before (I havent updated in a very, very long time).
These are the steps I took as best as I remember:
from a working state: boot into TWRP 3.3.0.1 , backup system & boot onto interal storage
then flash stable9.0.6 firmware + modem, flash lineage-17.1-20200615-nightly, flash gapps
then I wiped dalvik cache and cache and booted into system.
The boot process itself went fine, however I was greeted with a "decryption failed" screen which claimed that the decryption password was correct, but the data was corrupt. TWRP also claims that the default decryption password does not work (it has not asked me for any decryption password before) and entering my screen lock pattern according to the /faq/openrecoveryscript.html page on twrp(dot)me does not yield any different result either.
Since I've neglected to copy the backup to any other place other than internal storage, thinking that just a firmware and system flash would be no risk to it, I now have no way of restoring the previous state.
First I tried updating TWRP to the newest version (3.3.1.1) which yielded no difference, I attempted to flash both the old firmware (I know that it was 5.0.x, so I went with 5.0.8) and an old version of lineageos (some unofficial release of lineageos 15.1 from 2017 that I found on xda, since the official releases arent available that long) which resulted in a successful boot, but unsuccessful decryption just as with lineageos 17.
I have also attempted to follow the steps at /r/LineageOS/comments/anivml/ , though the backup fails silently (pc says `Now unlock your device and confirm the backup operation...`, nothing happens on my phone)
I would be thankful for any ideas on how I could recover from this without data loss.
I apologize for the weird links, but I am a new user and cant post external links yet
Click to expand...
Click to collapse
Data on userdata partition is gone (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).
Format (not wipe) the data partition (los recommends ext4).
nvertigo67 said:
Data on userdata partition is gone (for details see: https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).
Format (not wipe) the data partition (los recommends ext4).
Click to expand...
Click to collapse
Well ****.
Thank you for the information
Installation of LineageOS 18.1These are my experiences installing LineageOS on my OnePlus 7T. I come from a Oneplus 3T LineageOS 18.1.
Installation worked smoothly after I found the correct files to download: I used TWRP 3.6 hotdog (not hotdogv2), latest LineageOS build, copy-partitions-20210323_1922.zip, OpenGApps pico.
I was a bit surprised that after I installed LineageOS und rebooted into recovery to flash the GApps, I got into LineageOS recovery instead of TWRP (I guess because it's been installed on A/B partitions).
Restore of my apps and dataMost trouble made the Backup/Restore from my old phone. I made a local backup using SeedVault (Build-in in LineageOS). The final backup was only ~1,5GB in size. To copy the folder to the new phone I had to go through the setup process skipping all other methods to restore the data. Then I copied the files using "adb pull -a /sdcard/.SeedVaultAndroidBackup/ ." on the old phone and "adb push .SeedVaultAndroidBackup/ /sdcard/.SeedVaultAndroidBackup" on the new phone. Then I searched for a method to start the restore process and found this: "Go to your dialer app and type *#*#7378673#*#* or use the vanity number *#*#RESTORE#*#* by typing the letters in your dialer". I was surprised how well all went. Most app data was restored (some not, like sensitive banking app data), but no images or other files which was best considering the size of my data. I copied these files afterwards.
Problem with Google calendar syncUnfortunately, I recognised a few days later that the google calendar sync did not work any more. Using "adb logcat" to find the reason, I got this:
Code:
W GooglePlayServicesUtil: com.google.android.syncadapters.calendar requires the Google Play Store, but it is missing.
E GooglePlayServicesUtil: GooglePlayServices not available due to error 9
So this came as a surprise. I don't know what to make of that. I should have Google's method to transfer the data I suppose. That worked with my wife's phone even from an older android version.
I suspected
1) that it might be a problem with the google play certification and tried to register my phone with google as described here: https://www.lineageos.org/Google-Play-Certification/, but that changed nothing.
2) a problem with the SeedVault data restore.
Any idea what might be the problem and whether a factory reset would fix the problem?
I am also experiencing this problem on my Oneplus 9 running LineageOS 18.1. Last successful sync was on the fifth of march. I think this is a problem introduced in the LineageOS version I flashed on the sixth of march but I am not sure.
I could replicate the problem with a second device. Replication steps: Clean install of LineageOS (older version, so that you can make an update later) with Open GApps. Login to google account during the setup. Activate calendar sync. Update to new version of LOS => calendar sync stops to work.
I did the same with MindTheGApps and it works. So it was my mistake to install the wrong version of the GApps (on the installation page of LineageOS, MindTheGApps is recommended).
Side note: How to make a clean install: Reboot into recovery, do a factory reset, adb sideload LineageOS, reboot into recovery again without booting into the OS and adb sideload the GApps package.
How to switch from Open GApps to MindTheGApps: Do a clean install. I tried to do an installation without a factory reset but that did not fix the problem.
Disclaimer: I'm an end user with IT background. I'm in the process of migrating to LOS on OP7T.
Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but nothing has worked for OOS 12. I am able to extract the OOS 12 stock recovery.img with Payload Dumper, and am able to create a basic TWRP device tree for android 12.1 using the official TWRP 12.1 Github manifest, but I'm not able to find a good guide to create a TWRP-ready device tree from my stock recovery.img I mentioned earlier. I've tried updating to OOS 11, and using the twrp-keep module on the magisk modules github to keep the official TWRP installed. (It support OOS 11, but not OOS 12). I've also tried flashing the unofficial build made by Mauronofrio, but none of the specified methods have worked. Can someone please either make a OOS12-compatible version of TWRP for the OnePlus 7T, or if they can't do that, guide me in a step-by-step process on how to do i myself? Any help would be greatly appreciated.
Oos12 does NOT support twrp nor does A13
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
I just flashed it, and it booted successfully! I'll let you know if I can format /data.
Format /data works.
For confirmation, I flashed the .img of the OOS12 version to the recovery partition.
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
SiegeDaBoss said:
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
Click to expand...
Click to collapse
I just tested the non-OOS Android 13 TWRP file, and it has the same issue.
Can u back up all partitions except data? At least that would be helpful
HueyT said:
Can u back up all partitions except data? At least that would be helpful
Click to expand...
Click to collapse
Nope. Even when I de-select Data, and select everything else, it still fails with the "Failed to mount /data" error.
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
HueyT said:
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
Click to expand...
Click to collapse
I mean, at least both of them boot.
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Thank you for testing the builds and for the feedback . I've been on oos11 for a long time, but today I'm going to flash oos12. Because i would need recovery log files to fix errors.
I don't have no time for some fixes, i will try to fix errors whenever possible.
did you not ttry to use the twrp and the twrp installer builds that are on official twrp site for one plus 7t
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Hi again, i updated my repo and download links.
-OOS12 decryption working.
-Flash zip working . "I installed with zip by the Magisk and copy partititon, i flashed los20 & stock oos12 .)"
-Adb sideload working, i tried stock oos12 flashed successfully.
-Format data working.
-Mtp working.
-Otg working.
-Adb working.
-Vibration working.
* Backup data working, but restore data on oos bootloop
* i use swift backup instead of nandroid backup
When i have free time, i will work on twrp a13 fbev2.
mrk2815 said:
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
Click to expand...
Click to collapse
Every ROM comes built-in with its own recovery. So you'll have to flash the ROM via that recovery's ADB Sideload feature.
lets hope you can get a working twrp going for both andrid 12 and 13 .as my one plus 7t is just been put away in my drawer after seeing that one plus has given up on these older devices. when there is a working twrp i would probably want to flash something down the road. my primary driver unfortunately is a samsung S21 plus .
rabilgic said:
Hi again, i updated my repo and download links.
OOS12 decryption working.
Mtp working.
Adb working.
Vibration working.
I installed with zip by the Magisk and copy partititon.
Backup/restore boot.img working.
I haven't tested: flash rom, format data, needs some testing
When i have free time, i will work on twrp a13 fbev2.
Click to expand...
Click to collapse
All works until I tried to restore. Then it got stuck at red dot going around in circle. When I tried to go back in twrp again to format data, it won't mount data after that. Ended up having to restore all over using msmtool.
It mounted data fine before I tried to restore the data part, then it messed up decryption of data despite not having a lock code, no fingerprint, no pattern-lock, or lock screen enabled.