[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A6+/A605

Search This thread

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,080
9,925
@ashyx Can you please answer this? I have the same question.
It seems to be some sort of security measure.For some reason any custom or modified boot image(unsigned) causes the lockscreen settings to be unsaved.
Possibly a patched lockscreen binary is required.
The same issue happens on Gsi's, but a work around was found for that, but this doesn't work on stock Samsung roms.
 
  • Like
Reactions: DJBhardwaj

DJBhardwaj

Inactive Recognized Contributor
Apr 23, 2011
5,055
2,737
29
Delhi
GT-i9020
Google Nexus 4
It seems to be some sort of security measure.For some reason any custom or modified boot image(unsigned) causes the lockscreen settings to be unsaved.
Possibly a patched lockscreen binary is required.
The same issue happens on Gsi's, but a work around was found for that, but this doesn't work on stock Samsung roms.

What about Samsung account?
 

ShaDisNX255

Senior Member
Apr 3, 2014
2,673
1,725
Matamoros
Samsung Galaxy A52 4G
I am not a kernel expert, but I remember on the J6 it had the same problem. Kernel devs acknowledged this as a keystore problem or I forgot the name. They fixed keystore stuff on the kernel and then Samsung account and lockscreen pattern/pin/password worked again
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,080
9,925
I am not a kernel expert, but I remember on the J6 it had the same problem. Kernel devs acknowledged this as a keystore problem or I forgot the name. They fixed keystore stuff on the kernel and then Samsung account and lockscreen pattern/pin/password worked again
I think you maybe getting mixed up with the Bluetooth/WiFi password issue that required patched secure storage binaries to fix.
Unless you can point to a specific thread?
 

ShaDisNX255

Senior Member
Apr 3, 2014
2,673
1,725
Matamoros
Samsung Galaxy A52 4G
I think you maybe getting mixed up with the Bluetooth/WiFi password issue that required patched secure storage binaries to fix.
Unless you can point to a specific thread?

No no, I remember before the J6 had a global launch of Pie I took another country's firmware and made a Pie zip.
I used the same old TWRP, stock kernel and a few edits on system, and I remember I had the exact same problem. Pin/Pattern/Password did not work and you could not log in to Samsung account. I could set up the PIN just fine, but whenever I input it, it would always return as incorrect. I'm going to try to find the commit made to the kernel, let me see if I can find it even though I don't know how much of this works xD

---------- Post added at 11:39 AM ---------- Previous post was at 11:35 AM ----------

Here we go: https://github.com/ananjaser1211/Helios_7870/commit/f1c62423175f5e5f1b4e27efefc0b0befecb5568

Again, I don't know how much of this works but I know, I am pretty sure I remember that ananjaser was helping me with this Pie build and he named this "Keystore bug" or something lol
But since I don't know much about kernels, I really don't know how all this works xD
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,080
9,925
No no, I remember before the J6 had a global launch of Pie I took another country's firmware and made a Pie zip.
I used the same old TWRP, stock kernel and a few edits on system, and I remember I had the exact same problem. Pin/Pattern/Password did not work and you could not log in to Samsung account. I could set up the PIN just fine, but whenever I input it, it would always return as incorrect. I'm going to try to find the commit made to the kernel, let me see if I can find it even though I don't know how much of this works xD

---------- Post added at 11:39 AM ---------- Previous post was at 11:35 AM ----------

Here we go: https://github.com/ananjaser1211/Helios_7870/commit/f1c62423175f5e5f1b4e27efefc0b0befecb5568

Again, I don't know how much of this works but I know, I am pretty sure I remember that ananjaser was helping me with this Pie build and he named this "Keystore bug" or something lol
But since I don't know much about kernels, I really don't know how all this works xD
Great. I'll look into that. Any idea where the original patches came from?
 

DJBhardwaj

Inactive Recognized Contributor
Apr 23, 2011
5,055
2,737
29
Delhi
GT-i9020
Google Nexus 4
Samsung account gets disabled as soon as Knox is tripped.

I didn't know that Samsung Account would be disabled as well. I thought only services like Samsung Pay and Secure Folder were affected once KNOX was tripped.

I also went through the comments below yours. I think what @ShaDisNX255 pointed out is worth looking into. Waiting to hear an update from your end. Many thanks!
 

ShaDisNX255

Senior Member
Apr 3, 2014
2,673
1,725
Matamoros
Samsung Galaxy A52 4G
Just been looking into this, but I see all the changes got reverted. Any idea why? Did the changes actually work or cause another problem?
Well, talking with Anan directly he said because it helped when he was porting Pie to older devices like J5 and J7. But then he noticed it actually did nothing, it seems the keystore issue only affects newer devices that have official Pie, but he wasn't sure exactly why.
 
  • Like
Reactions: DJBhardwaj

pandavova

Senior Member
Feb 9, 2016
121
16
So, there is still no way we can root it on Android 9 with samsung features wotking?

Doesn't look like it, there is prolly a higher chance of Android 10 (which is prolly going to be released 2020) working fine then getting a working method for this problem lol

You could also lurk/join the a605x telegram, there is some talk about gsis etc.
 
  • Like
Reactions: FuTChY

FuTChY

Senior Member
Jun 11, 2012
907
154
Egypt - Cairo
Doesn't look like it, there is prolly a higher chance of Android 10 (which is prolly going to be released 2020) working fine then getting a working method for this problem lol

You could also lurk/join the a605x telegram, there is some talk about gsis etc.

Yeah, that makes sense. I was thinking about that too. Thanks for the Telegram suggestion.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    Unofficial release -TWRP recovery for the Galaxy A6 plus 2018 - SM-A605 MSM8953

    teamwin-recovery-project-twrp-logo.jpg




    TWRP 3.2.3-0 Released
    Aug 6, 2018
    TWRP 3.2.3-0 is out now for most currently supported devices.
    What's new in 3.2.3-0:
    * Fix automatic installing of OTA zips on encrypted devices
    * Remove SuperSU from TWRP
    * Support both md5 and md5sum file extensions when doing MD5 checking for zip files
    Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
    We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
    You can track the progress of builds here





    Update 18/11/2018
    Beta build released.
    Current status - Beta (tested working)
    Treble supported
    Update 14/12/18 - OTG support added.


    You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.

    NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
    Settings -> Developer Options -> OEM unlocking
    AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.



    *****INSTALL INSTRUCTIONS:*****


    Flash with ODIN in the AP slot.

    1. Put your device in DOWNLOAD mode.
    (Hold POWER + VOL DOWN + VOL UP)
    2. Load the file below into the AP slot and hit start.
    twrp_3.2.3-1_sm-a605_141218
    3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
    You should now see TWRP recovery.
    4. Flash the RMM bypass zip
    https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795

    NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.

    5. Reboot to TWRP (Do not boot to the OS yet)



    6. Move on to root instructions below. This is a requirement to get the device to boot.


    *****OREO ROOT INSTRUCTIONS:*****


    1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
    Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
    After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
    PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
    A605_oreo_forced_encryption_disabler

    2. To root I suggest installing Magisk as this is a currently supported project, SuperSu is no longer getting active development.
    https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

    3. Enjoy your rooted device.


    DEVICE TREE: soon


    PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST




    Credits: Me, Teamwin, @nebkas for initial testing, @BlackMesa123 for RMM bypass zip.

    Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.


    FEEDBACK IS APPRECIATED PLEASE.
    THANKS.


    DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

    3
    Ashyx is there a solution to the problem of connection with the pc? mtp application reports error
    I will update the boot image later with a fixed version.
    Alternatively download the stock boot image below.
    Flash it with TWRP then immediately flash the Magisk zip.
    Reboot.

    https://www.androidfilehost.com/?fid=11410963190603856376
    2
    there is a small problem here, i can't change brightness. it won't be darker or brighter.
    I need the path of the brightness file.

    If some one could do:

    ls -R /sys/devices > sdcard/devices.txt

    Then post up the devices.txt file.
    2
    Hi, does the problem of lock screen and fingerprint unlock still exit?
    No they fixed it
    2
    I need device tree, vendor tree, and kernel source
    Could you tell me how did you get those things?
    I want to build a rom
    You need to build a device tree yourself.
    You may be able to use parts from someone elses github as a starting point if you can find a device using the same platform.
    Kernel sources are downloaded from Samsungs open source release Centre.

    TWRP device tree is no good for compiling roms.