[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017)

[AK2H]

Guys I installed Oreo and I can't root my phone, old twrp can't be installed over Odin. can anyone help me to root it?

https://xdaforums.com/samsung-a-ser...ot-install-twrp-samsung-t3747535/post75514974

https://xdaforums.com/android/general/guides-android-8-0-oreo-mods-thread-t3772017/post76397697

 

[Νικολας]

[No message]

 

[ebi02]

Hi.
Please close this post.
No updated post !!!!

 

[Pat750]

Hi.
Please close this post.
No updated post !!!!

I don't see that an update is needed since this TWRP works really good, at least for me. Do you need an update?
Thread should stay open for discussion

 

[folusmile]

Can I use magisk on this device

 

[ebi02]

I don't see that an update is needed since this TWRP works really good, at least for me. Do you need an update?
Thread should stay open for discussion

No I used twrp 3.2.1 created by matt.

 

[zogoibi]

A little question:
I've TWRP'ed my device according to this thread. Afterwards, I've installed a custom ROM. Now, whenever I boot into Recovery, Samsung's splash screen is normal, BUT!: if I boot into System, I get the red message on top left of splash screen: "kernel is not seandroid enforcing".
I know this is not an issue, since we're supposed to get that message when the device detects a non-stock ROM. However, I'm curious why there is no such message if I boot to Recovery?
Someone knows? Thank you.

 

[ashyx]

A little question:
I've TWRP'ed my device according to this thread. Afterwards, I've installed a custom ROM. Now, whenever I boot into Recovery, Samsung's splash screen is normal, BUT!: if I boot into System, I get the red message on top left of splash screen: "recovery is not seandroid enforcing".
I know this is not an issue, since we're supposed to get that message when the device detects a non-stock ROM. However, I'm curious why there is no such message if I boot to Recovery?
Someone knows? Thank you.

Are you sure you're not getting that back to front?
You would get it booting to recovery not system.
Booting to system would say 'kernel is not seandroid enforcing".

 

[zogoibi]

Are you sure you're not getting that back to front?
You would get it booting to recovery not system.
Booting to system would say 'kernel is not seandroid enforcing".

That's correct. But anyways, I get no message when booting to custom recovery. Only to custom ROM. How so? Just curious.

 

[ashyx]

That's correct. But anyways, I get no message when booting to custom recovery. Only to custom ROM. How so? Just curious.

Can you take a screenshot of your device booting to system with this message?
It doesn't make sense.

 

[kaizokan]

@ashyx did you manage to look at the boot.img files that @AK2H posted for the disable forced-encryption patching on Oreo?

 

[AK2H]

@ashyx did you manage to look at the boot.img files that @AK2H posted for the disable forced-encryption patching on Oreo?

I deleted all files from my drive since they were ignored for over 2 months

 

[ashyx]

@ashyx did you manage to look at the boot.img files that @AK2H posted for the disable forced-encryption patching on Oreo?

My bad I forgot to come back to this. I can fix it but give me time as it's not an easy fix.
I need the boot.img from the latest Oreo firmware.

 

[natsousa]

My bad I forgot to come back to this. I can fix it but give me time as it's not an easy fix.
I need the boot.img from the latest Oreo firmware.

This is from the latest Oreo for A320Y

https://drive.google.com/file/d/1lgQIpPk1DZfN2HntOgqyx0LHHEvKfzdp/view?usp=sharing

 

[folusmile]

Anyone with boot. Img of A320f 2017 nougat should drop it here pls

 

[zogoibi]

Hello all.
Suppose my phone has stock Nougat and this TWRP.
Suppose now I want to update to stock Oreo.
Since the phone already has a working bootloader, a working modem and a working recovery with which I'm happy, and since this TWRP can flash .img files, can I simply extract system.img and flash it with TWRP? Would that work? Should I need to flash some other .img files from stock?
Or is this totally wrong?
My idea is to avoid the Odin thing altogether (flash stock, reflash twrp, etc), if possible, while at the same time preserving my data and skipping the risk of getting RMM locked if something goes wrong the Odin way before I can apply the RMM-bypass patch.
Thank you in advance.

 

[Pat750]

Hello all.
Suppose my phone has stock Nougat and this TWRP.
Suppose now I want to update to stock Oreo.
Since the phone already has a working bootloader, a working modem and a working recovery with which I'm happy, and since this TWRP can flash .img files, can I simply extract system.img.lz4 and flash it with TWRP? Would that work? Should I need to flash some other .img.lz4 files from stock?
Or is this totally wrong?
My idea is to avoid the Odin thing altogether (flash stock, reflash twrp, etc), if possible, while at the same time preserving my data and skipping the risk of getting RMM locked if something goes wrong the Odin way before I can apply the RMM-bypass patch.
Thank you in advance.

I really don't know if this would work, but it doesn't sound totally wrong, but it could be...
All I know is that lz4 files are compressed too. To uncompress I used (with PC) 7zip with modern 7zip extension. Then the img file can be flashed with TWRP.
Edit. There is more info about flashing img files in OP first page.

 

[zogoibi]

I really don't know if this would work, but it doesn't sound totally wrong, but it could be...
All I know is that lz4 files are compressed too. To uncompress I used (with PC) 7zip with modern 7zip extension. Then the img file can be flashed with TWRP.
Edit. There is more info about flashing img files in OP first page.

Hi again, @Pat750!

Yes. I've read that info, but I need to know a couple more things, like for instance: what's the meta-data folder for?, do I need it? I can't do anything in TRWP with it, so if it's necessary, then that's the end.

True, I've realized that lz4 files are compressed, but easy to decompress as you point out.

Generally, the idea makes sense to me. The main question here is: can the Oreo system boot off a Nougat bootloader? I.e., does Oreo feature a "bootloader checker" ready to abort the boot process? Likely so. At least, were I the engineer, I'd do it that way.

Anyhow I guess I'll just try. Not much to lose: at worst, I can always enter recovery and flash my nandroid backup.

 

[potyqa]

Hi again, @Pat750!

Yes. I've read that info, but I need to know a couple more things, like for instance: what's the meta-data folder for?, do I need it? I can't do anything in TRWP with it, so if it's necessary, then that's the end.

True, I've realized that lz4 files are compressed, but easy to decompress as you point out.

Generally, the idea makes sense to me. The main question here is: can the Oreo system boot off a Nougat bootloader? I.e., does Oreo feature a "bootloader checker" ready to abort the boot process? Likely so. At least, were I the engineer, I'd do it that way.

Anyhow I guess I'll just try. Not much to lose: at worst, I can always enter recovery and flash my nandroid backup.

I'm happy to tell you that Nougat and Oreo use the same bootloader! And by the way I don't think there's a checker because I've managed to boot stock Marshmallow with the Nougat/Oreo bootloader?

 

[zogoibi]

I'm happy to tell you that Nougat and Oreo use the same bootloader! And by the way I don't think there's a checker because I've managed to boot stock Marshmallow with the Nougat/Oreo bootloader?

Thank you! But that puzzles me: if Nougat and Oreo share bootloaders, then, where has Samsung installed the RMM/FRM lock thingie? Is that in the system itself? In such case, after System I should definitely flash the RMM-bypass, right?