[OFFICIAL][RECOVERY] TWRP 3.5.2_9 for Galaxy J5 (2016)

[Ex novo]

How i van check is it encrypted?

I tried works well for me A11 bliss vanila ...

Were you able to encrypt Jenslody's BlissRoms 14.0? I ask because on the homepage says that one of the ROM bug is encryption and I would like to install an encrypted rom on my phone for security reasons.

 

[Bogdans29]

Were you able to encrypt Jenslody's BlissRoms 14.0? I ask because on the homepage says that one of the ROM bug is encryption and I would like to install an encrypted rom on my phone for security reasons.

Idk whan i go in TWRP im going to encrypt and select

Were you able to encrypt Jenslody's BlissRoms 14.0? I ask because on the homepage says that one of the ROM bug is encryption and I would like to install an encrypted rom on my phone for security reasons.

Oh s.... i doing it wrong.. I will try whan i charche my phone to 100% and report results

 

[Bogdans29]

It does? Ok, thats good. I wonder if its a rom issue for crdroid then

Sorry i was doing it wrong.. i will try again in a 30min and report results

 

[palmbeach05]

Were you able to encrypt Jenslody's BlissRoms 14.0? I ask because on the homepage says that one of the ROM bug is encryption and I would like to install an encrypted rom on my phone for security reasons.

I see what you mean. My j5 is broken, i can't do any testing, but i have an idea on why.

Android 11 brought in new encryption/decryption protocol. Roms were building fine, as was aosp based recovery. Twrp and ofox builds were viewing things as encrypted (file names all jumbled up).

The fix was merged on or about december 16, when the twrp source code was 3.4.0 (later updated to 3.5.0 on dec 28).

Jens's twrp build is 3.3.1, and built on feb 15, 2020, while mine is 3.5.0, and built after the encryption fix was merged.

 

[Bogdans29]

I see what you mean. My j5 is broken, i can't do any testing, but i have an idea on why.

Android 11 brought in new encryption/decryption protocol. Roms were building fine, as was aosp based recovery. Twrp and ofox builds were viewing things as encrypted (file names all jumbled up).

The fix was merged on or about december 16, when the twrp source code was 3.4.0 (later updated to 3.5.0 on dec 28).

Jens's twrp build is 3.3.1, and built on feb 15, 2020, while mine is 3.5.0, and built after the encryption fix was merged.

Encryption does not work bootloop using lastest bliss build and twrp

 

[palmbeach05]

Unfortunately the encryption of the crDroid ROM did not work. The device went into bootloop.

I'm tracing things back, its possible keymaster 4.0 is the issue, as it is not in the official release, but present in my personal test builds. Can anyone confirm if keymaster 4.0 is present on the roms in sbin, either on system, product, or vendor

 

[daywalk3r666]

I'm tracing things back, its possible keymaster 4.0 is the issue, as it is not in the official release, but present in my personal test builds. Can anyone confirm if keymaster 4.0 is present on the roms in sbin, either on system, product, or vendor

do you mean this files?

 

[palmbeach05]

Unfortunately the encryption of the crDroid ROM did not work. The device went into bootloop.

I'm tracing things back, its possible keymaster 4.0 is the issue, as it is not in the official release, but present in my personal test builds. Can anyone confirm if keymaster 4.0 is present

do you mean this files?
View attachment 5218909

Yes that one. For some reason test builds on here have it, and official builds do not. Also, was there any mtp/adb issues?

 

[daywalk3r666]

i will check it later but i don't remember any issues

 

[daywalk3r666]

mtp and adb works without any problems. but i'm not encrypted

 

[palmbeach05]

mtp and adb works without any problems. but i'm not encrypted

Ok, just checking. I had a report come in on mtp failing and i wanted to check around before i did anything major. I do think that its keymaster 4.0 thats causing the issue with encryption. Going back to the test build prior to the screenshots showing encrypted, its present there, but not present in official build.

 

[Bogdans29]

You publishing recovery that is for J5 2015 instead for 2016.
J500 is 2015
J510 is 2016
Your lastest recovery 3.5.1 have error that image is larger than targeted davice..

 

[daywalk3r666]

same here. but i think it was a automatic build from twrp

 

[Bogdans29]

same here. but i think it was a automatic build from twrp

Hmmm i didn't think about that.. it can be..

 

[palmbeach05]

You publishing recovery that is for J5 2015 instead for 2016.
J500 is 2015
J510 is 2016
Your lastest recovery 3.5.1 have error that image is larger than targeted davice..

Agree with @daywalk3r666 it was an automatic build. I didn't even know that they had released an update until the 18th, 4 days after that build was released. I'm looking into it now. also, seems to be a 2016 device issue.

 

[palmbeach05]

try this @Bogdans29 @daywalk3r666

 

[daywalk3r666]

this version works

 

[daywalk3r666]

one question. did you remove some features? twrp doesn't recognize the magisk.apk

 

[palmbeach05]

this version works
View attachment 5258693

Nice, thats good news. I have no idea why 2015 models were normal and 2016 models became bloated, but i'm glad to see that its working now. On a side note, other added changes were made, and i *think* that the encryption issue may be fixed now. But making sure the recovery was the right size was more important.

 

[palmbeach05]

one question. did you remove some features? twrp doesn't recognize the magisk.apk

Bash and nano were removed, i can run a test build and add those in there to see what the size is when i get home. In the meantime you could rename it from apk to zip.