How to do full device encryption with custom recovery and 5.0+? - Sprint Samsung Galaxy S III

A while ago I posted a workaround to use custom recovery and full device encryption and it seems like it's STILL needed, meaning I can't use TWRP, unless someone has found a ROM that has working encryption with TWRP? I've tried a few ROMs so far, as well as the latest stock ROM (NJ2 - 4.4.2). TWRP just gives the error "cannot find crypto footer" and the devs have said in the past this is a "wontfix" problem. I'd really, really like to put Marshmallow on here but I need full device encryption and TWRP support. So frustrating.
I don't mind wiping this device and re-encrypting as many times as needed, I just need it working.

Related

Does Encryption NEVER work in ROMS

So I kind of like the fact encryption is turned on automatically by Nextbit (and I did figure out how to get out of my encryption loop)
And I have tried to encrypt the disk with
-Pacman ROM
-Reserrection ROM
-Paranoid Android
and all of them bootloop and never actuall boot up once you press "encrypt".... so is it impossible to encrypt once you have an unlocked bootloader and recovery installed? I get its detrimental to the whole process of flashing incessantly but still
Grrrrrrr
Can sum1 confirm
tlxxxsracer said:
If you unlock the bootloader,that alone won't cause encryption issues. You have to flash a specific boot.img or zip that will disable encryption.
Don't unencrypt and should be fine.
Not sure why you'd want to encrypt if your BL is unlocked. Encryption only hurts performance
Click to expand...
Click to collapse
thanks for the reply
I wanted to encrypt my current ROM to just get the extra protection from theft or lost device.
I really like the current ROM im using and dont need to flash anymore currentlty, so i would be fine locking it down with encryption
But i cant get ANY of the ROMS to encrypt like they normally do say compared to the G3
So there is a solution to this. Basically, when you encrypt the file system on one rom, even when you wipe the data certain things are still tied to the old file system. That's why when you go to encrypt the encryption fails, because the remnant stuff from the other rom is in the way. The solution is to completely reformat the data partition (using TWRP, select format data, or change the data file system to F2FS and then back to ext4.). This will clear the conflicts causing encryption to bootloop. However, this process will need to be repeated every single time you switch roms (updating a rom is fine).
I believe Cyanogenmod supports encryption, though I have never tried it.
yanowman said:
So I kind of like the fact encryption is turned on automatically by Nextbit (and I did figure out how to get out of my encryption loop)
And I have tried to encrypt the disk with
-Pacman ROM
-Reserrection ROM
-Paranoid Android
and all of them bootloop and never actuall boot up once you press "encrypt".... so is it impossible to encrypt once you have an unlocked bootloader and recovery installed? I get its detrimental to the whole process of flashing incessantly but still
Click to expand...
Click to collapse
If you flashed the custom boot image, you CANNOT re encrypt your phone. Won't work.

Fully Wiped my OnePlus5T attempting to update to 5.1.5 - Is it soft bricked?

Disclaimer: I am no developer just someone who has done a ton of research in the last day
This may be a long post due to my extensive troubleshooting issues, so here's some background.
OP5T is the first android I've owned and I have had it for about a year. I rooted it right after I received it and haven't updated it since. With the release of Oreo, I entertained the idea of updating my firmware, which I knew meant that I'd need to factory reset my device. Yesterday was the day I decided to do it and man I regret it. Long story short, I fully uninstalled Magisk through the app, attempted to fully remove the root by means of 'full unroot' in the SuperSU app, which failed. I then was stupid enough to fully wipe my device using TWRP (I think I checked the box for every partition in 'advanced wipe'). I was then stuck in a boot loop. Eventually, I managed to use fastboot to boot recovery to TWRP. I have been stuck in this state ever since.
I am currently using 3.2.1-x | blu_spark v8.61 and previously used Magisk.
The main ROM I have been attempting to flash is OnePlus5TOxygen - 5.1.5
- https://www.oneplus.com/support/softwareupgrade/details?code=7
- https://forum.xda-developers.com/oneplus-5/how-to/oxygen-os-5-1-5-signed-zip-t3832336 (not sure how
these are different but their filenames differ so I have tested both
The errors I have received in my troubleshooting process:
- The most infamous: Error 7
- E1001: Failed to update system image
- no file_contexts
- and a host of others I have weeded out using xda as a resource, such as many partition errors, vendor issues,
etc.
- Failed to read command: No error (terminal result when attempting to flash some ROMS through ADB)
The steps I have taken to remedy these errors:
Let me just say I have consulted tons of xda threads regarding error 7, and none work for me. I have attempted to flash using several of the latest versions of TWRP, finding the most success with blu_spark. I have attempted to sideload the ROMS, push them using ADB, and directly place them in the internal storage and no method works. I always get Error 7, with the exception below.
I have attempted to flash stock ROMS for OOS versions 5.1.4, 5.1.5, custom ROMS recommended by xda threads pertaining to the same issue, and many variations of these. Since there are no assert statements in the update_script found in the stock ROMS, which many people mentioned on the forums, I have attempted to approach error 7 from a different angle.
- Each stock ROM starts with this function, which when deleted gets rid of the 'vendor partition is not existed'
error getprop("ro.display.series") == "OnePlus 5T" || abort("E3004: This package is for
"OnePlus 5T" devices; this is a "" + getprop("ro.display.series") + "".");
is_part_existed("/dev/block/bootdevice/by-name/vendor") || abort("vendor partition is not existed, exit
ota!!");
- Even when deleting that, I found there to be two more errors that would appear every time I attempted to
flash, caused by two block_image_update functions that result in errors E1001 and E1002: These both have to do
with updating the system or vendor image.
I have attempted to delete any combination of these. If I don't delete all three functions, I will get an error pertaining to the function I didn't delete. If I do delete them, the ROM will install up to 47% every time and it will cancel (no error). This has happened for all stock ROMS I have flashed, and I have swapped to the latest stock recovery multiple times with no luck.
Additionally, I reformatted data multiple times, set the system partition to ext4, attempted to fix the file system, attempted to mount system in read only to see if that would fix the system update error, all to no avail. I also delete the cache after each ROM flash attempt as well.
I have spent at least 10 hours trying every troubleshoot option I came across on the forums and nothing has helped, which is why I am making this now. I have attempted to flash the current firmware for OP5T with every flash attempt ending with the string '...done' in the terminal, even though nothing has been changed or installed. Every time I try to reboot, it still tells me that I have no OS installed, and I can tell since my internal storage is currently using only around 100MB of usable memory. I have also locked my bootloader, wiped the device, switched to stock recovery, and attempted to clean flash the latest OS with no luck.
In conclusion, it seems that I have deleted my OS so there is nothing to boot to (I go straight to bootloader), there is an error or something missing in my filesystem that is preventing me from fully installing any ROM, and I have tried everything suggested on these forums for similar issues with very limited success. I have done much more than what I mentioned here, and if anything useful comes to mind I will update this post.
(I am also a Computer Science college student that needs a working phone drastically and have already spent so much time diagnosing this issue rather than study that I am ashamed)
I am on the brink of contacting OnePlus, even though I feel as though they wouldn't be much help, or sending this to a repair shop.
Any suggestions/ideas would be greatly appreciated. I will attempt to be as active as possible on this forum as well.
Read my post in this thread, second post. You are fine, as you can still get into TWRP, you are just using a really old version of TWRP, and further complicating things by trying to flash treble ROMs.
Update to the latest version of Bluesparks TWRP which you can flash from your current TWRP, then reflash the full factory ROM. Note it will replace recovery if it is successful.
^^ +1. As long as you can boot into recovery, you are fine. The trick is installing a ROM that is compatible with your TWRP.
I am using codeworkx TWRP 20180822 and running the last Oreo build of Omnirom. First update your TWRP image, then find your OREO rom and install that. You may need to format data with the new TWRP first.

can't encrypt after installing latest TWRP

Hello everyone,
i finally got the unlock code and moved from chinese to xiaomi.eu MIUI 10 rom . I installed lazyflasher, TWRP 3.2.3 and was good to go in a reasonable amount of time but i hit a wall. for work i need to encrypt my phone, it's non-negotiable and has to be done. but when i try to do it, the operation fails. as much as i read it's because newest versions of twrp reserve/lock/enumerate all the blocks of /data and there's not enough space to store encryption files in the /data. There are two ways out of this: either downgrade to an earlier version of TWRP ( 3.1.0 should work) or extend the /data partition. Now the problem is that i have already set up a lot on this phone so a complete wipe will be painful..
So my question is, can i get encrypted without wiping my phone? is there a way to downgrade TWRP or extend /data without formatting / wiping?
I also need an encrypted phone ...
Have you tried this?
https://forum.xda-developers.com/mi...very-twrp-3-2-3-1-nitrogen-t3866084?nocache=1
I still have to wait 255 hours to try this myself ....
ki01 said:
Hello everyone,
i finally got the unlock code and moved from chinese to xiaomi.eu MIUI 10 rom . I installed lazyflasher, TWRP 3.2.3 and was good to go in a reasonable amount of time but i hit a wall. for work i need to encrypt my phone, it's non-negotiable and has to be done. but when i try to do it, the operation fails. as much as i read it's because newest versions of twrp reserve/lock/enumerate all the blocks of /data and there's not enough space to store encryption files in the /data. There are two ways out of this: either downgrade to an earlier version of TWRP ( 3.1.0 should work) or extend the /data partition. Now the problem is that i have already set up a lot on this phone so a complete wipe will be painful..
So my question is, can i get encrypted without wiping my phone? is there a way to downgrade TWRP or extend /data without formatting / wiping?
Click to expand...
Click to collapse
use nijel8's twrp recovery for decryption
just flash recovery image in twrp
i flashed nijel's TWRP and now i can get through that window i was stuck on, but i get a toast with "find device closed unexpectedly" . i disabled find my phone and logged out of the xiaomi account i had on the phone, then rebooted and tried again. same thing. maby i should root and give full rights or something to the location app....

Issue on reinstalling any kind of OS - brick?

Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?

Encryption / Twrp

Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Ms0206 said:
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Click to expand...
Click to collapse
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
kurtn said:
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
Click to expand...
Click to collapse
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Ms0206 said:
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Click to expand...
Click to collapse
Your data Partition is encrypted. Sideload does not touch data partition. Follow the guide
As if I didn't know it before, following the official guides producing the same errors as using Twrp.
I tried so many things...using official recovery does not install OTA automatically.
Sideload producing the same errors as using Twrp - "Magisk addond.d failed, cannot find Magisk binaries, reflash OTA Form decrypted recovery or reflash Magisk".

Categories

Resources